Internet-Draft Format Framework August 2022
Hoffman Expires 10 February 2023 [Page]
Network Working Group
Intended Status:
Standards Track
P. Hoffman

RFC Format Framework As Implemented


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.

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

This Internet-Draft will expire on 10 February 2023.

Table of Contents

1. Introduction

[RFC7990], 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 [RFC8651], 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 [RFC7991] 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.

2. Multiple XML v3 Vocabularies

The RFC Editor has changed the XML v3 vocabulary used to generate RFCs many times since the publication of [RFC7991]. The XML grammars used are currently cataloged at [[ It would probably be good to move that list and all of the files to ]] 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 [[ It would probably be good to move that document to ]]

3. 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.

4. IANA Considerations

This document has no IANA considerations.

5. Security Considerations

This document introduces no new security considerations.

6. References

6.1. Normative References

Flanagan, H., "RFC Format Framework", RFC 7990, DOI 10.17487/RFC7990, , <>.

6.2. Informative References

Hoffman, P., "The "xml2rfc" Version 3 Vocabulary", RFC 7991, DOI 10.17487/RFC7991, , <>.
Cheng, B., Wiggins, D., and L. Berger, Ed., "Dynamic Link Exchange Protocol (DLEP) Control-Plane-Based Pause Extension", RFC 8651, DOI 10.17487/RFC8651, , <>.

Author's Address

Paul Hoffman