ObsoletedINFORMATIONALIAB stream

RFC 7990: RFC Format Framework

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 9720.

Current version: RFC 9720RFC Formats and Versions

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

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.

Document record

Document ID
RFC7990
Published
December 2016
Authors
H. Flanagan
Status
INFORMATIONAL
Stream
IAB
Area
Pages
16
Also known as
Obsoleted by:
RFC 9720

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/7990-rfc-format-framework