metasystema.org
UpdatedINFORMATIONALIAB stream

RFC 7994: Requirements for Plain-Text RFCs

Still current, but amended. Parts of this document are changed or extended by RFC 9920. Read both.

In plain English — editorial summary, not part of the RFC

In 2013, after a great deal of community discussion, the decision was made to shift from the plain-text, ASCII-only canonical format for RFCs to XML as the canonical format with more human-readable formats rendered from that XML. The high-level requirements that informed this change were defined in RFC 6949, "RFC Series Format Requirements and Future Development". Plain text remains an important format for many in the IETF community, and it will be one of the publication formats rendered from the XML. This document outlines the rendering requirements for the plain-text RFC publication format. These requirements do not apply to plain-text RFCs published before the format transition.

Document record

Document ID
RFC7994
Published
December 2016
Authors
H. Flanagan
Status
INFORMATIONAL
Stream
IAB
Area
—
Pages
8
Also known as
—
Updated by:
RFC 9920

Topics

Referenced by

One later RFC formally updates or obsoletes part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/7994-requirements-for-plain-text-rfcs