RFC Format Framework
draft-flanagan-rfc-framework-08

Document Type Replaced Internet-Draft (individual)
Last updated 2016-01-05 (latest revision 2015-12-09)
Replaced by draft-iab-rfc-framework
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-iab-rfc-framework
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-flanagan-rfc-framework-08.txt

Abstract

The canonical format for the RFC Series has been plain-text, ASCII- encoded for several decades. After extensive community discussion and debate, the RFC Editor will be transitioning to XML as the canonical format, with different publication formats rendered from that base document. These changes are intended to increase the usability of the RFC Series by offering documents that match the needs of a wider variety of stakeholders. With these changes, however, comes an increase in complexity for authors, consumers, and the publisher of RFCs. This document serves as the framework that describes the problems being solved and summarizes the many documents that capture the specific requirements for each aspect of the change in format.

Authors

Heather Flanagan (rse@rfc-editor.org)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)