]> ICANN

paul.hoffman@icann.org

Internet-Draft RFC 7990 "serves as the framework that provides the problem statement, lays out a road map of the documents that capture the specific requirements, and describes the transition plan" for the format of RFCs. The eventual implementation of the framework happened somewhat differently than was described in RFC 7990. This document describes how the framework was, and is being, implemented.

Introduction , published in December 2016, defined a framework for how RFCs would be published in the future, including new formats and a new canonical format for archiving RFCs. The first RFC to be published using the framework was , published in October 2019. In the time since then, the new framework has been applied to all published RFCs. The implementation of the framework did not go completely as planned. The canonical format changed many times between the publication of and now, and is expected to change more times in the future. Similarly, the software used to generate the non-canonical HTML, plain text, and PDF formats also changed during that time. This document describes how the RFC format framework was actually implemented.

Multiple XML v3 Vocabularies The RFC Editor has changed the XML v3 vocabulary used to generate RFCs many times since the publication of . The XML grammars used are currently cataloged at https://github.com/rfc-format/v3grammar. [[ It would probably be good to move that list and all of the files to rfc-editor.org ]] This means that different RFCs were published using different XML grammar. In every case so far, the newer grammar has been a superset of the previous grammar so that all of the RFCs published earlier would be valid in the newest grammar. The current vocabulary is published as https://datatracker.ietf.org/doc/draft-irse-draft-irse-xml2rfcv3-implemented/. [[ It would probably be good to move that document to rfc-editor.org ]]

Rendering RFCs in HTML, Plain Text, and PDF The rendering of the non-canonical formats evolved after the initial implementation of the framework. Thus, accessing the files for the non-canonical formats would get different results over time. The rendering is expected to continue to change in the future.

IANA Considerations This document has no IANA considerations.

Security Considerations This document introduces no new security considerations.

In order to improve the readability of RFCs while supporting their archivability, the canonical format of the RFC Series will be transitioning from plain-text ASCII to XML using the xml2rfc version 3 vocabulary; different publication formats will be rendered from that base document. With these changes comes an increase in complexity for authors, consumers, and the publisher of RFCs. This document serves as the framework that provides the problem statement, lays out a road map of the documents that capture the specific requirements, and describes the transition plan. This document defines the "xml2rfc" version 3 vocabulary: an XML-based language used for writing RFCs and Internet-Drafts. It is heavily derived from the version 2 vocabulary that is also under discussion. This document obsoletes the v2 grammar described in RFC 7749. This document defines an extension to the Dynamic Link Exchange Protocol (DLEP) that enables a modem to use DLEP messages to pause and resume data traffic coming from its peer router.