Summary
-------

A concise description of the proposed change. The description should
be one to two sentences long and written to be reusable in documents
aggregating changes for a release.

Problem
-------

A brief description of the problem, optionally including the
motivation for developing a solution.

Solution
--------

An overview of the solution. Alternative solutions may be discussed;
links to rationale documents or review threads welcome to provide
additional background to reviewers.

Specification
-------------

The detailed changes. Acceptable normative formats include inline
patches, attached webrevs, and attached specdiffs. The names of
attached files are recommended to include a bug id.  References to
external webservers, such as http://cr.openjdk.java.net/, can be
provided as informative supplements for the convenience of reviewers,
but must be accompanied by a normative form of the specification
directly associated with the CSR issue to satisfy archival purposes.