"Introduction Previously@ RFCs (e.g.@ [RFC4844]) contained a number of elements that were there for historical@ practical@ and legal reasons. They also contained boilerplate material to clearly indicate the status of the document and possibly contained ""Notes"" to indicate how the document interacts with IETF Standards Track documents. As the RFC Series has evolved over the years@ there has been increasing concern over appropriate labeling of the publications to make clear the status of each RFC and the status of the work it describes. Chiefly@ there is a requirement that RFCs published as part of the IETF's review process not be easily confused with RFCs that may have had a very different review and approval process. Various adjustments have been made over the years@ including evolving text of ""Notes"" included in the published RFC. With the definition of the different RFC streams [RFC4844]@ it is appropriate to formalize the definition of the various pieces of standard RFC boilerplate and introduce some adjustments to ensure better clarity of expression of document status@ aligned with the review and approval processes defined for each stream. This memo identifies and describes the common elements of RFC boilerplate structure@ and provides a comprehensive approach to updating and using those elements to communicate@ with clarity@ RFC document and content status. Most of the historical structure information is collected from [RFC2223]. The changes introduced by this memo should be implemented as soon as practically possible after the document has been approved for publication."