draft-iab-rfc-framework-01.txt   draft-iab-rfc-framework-02.txt 
Internet Architecture Board H. Flanagan Internet Architecture Board H. Flanagan
Internet-Draft RFC Editor Internet-Draft RFC Editor
Intended status: Informational January 20, 2016 Intended status: Informational January 20, 2016
Expires: July 23, 2016 Expires: July 23, 2016
RFC Format Framework RFC Format Framework
draft-iab-rfc-framework-01 draft-iab-rfc-framework-02
Abstract Abstract
The canonical format for the RFC Series has been plain-text, ASCII- The canonical format for the RFC Series has been plain-text, ASCII-
encoded for several decades. After extensive community discussion encoded for several decades. After extensive community discussion
and debate, the RFC Editor will be transitioning to XML as the and debate, the RFC Editor will be transitioning to XML as the
canonical format using the XML2RFC version 3 vocabulary. Different canonical format using the XML2RFC version 3 vocabulary. Different
publication formats will be rendered from that base document. These publication formats will be rendered from that base document. These
changes are intended to increase the usability of the RFC Series by changes are intended to increase the usability of the RFC Series by
offering documents that match the needs of a wider variety of offering documents that match the needs of a wider variety of
skipping to change at page 2, line 29 skipping to change at page 2, line 29
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Problem Statement . . . . . . . . . . . . . . . . . . . . . . 3 2. Problem Statement . . . . . . . . . . . . . . . . . . . . . . 3
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Overview of the Decision Making Process . . . . . . . . . . . 4 4. Overview of the Decision Making Process . . . . . . . . . . . 4
5. Key Changes . . . . . . . . . . . . . . . . . . . . . . . . . 6 5. Key Changes . . . . . . . . . . . . . . . . . . . . . . . . . 6
6. Canonical Format Documents . . . . . . . . . . . . . . . . . 6 6. Canonical Format Documents . . . . . . . . . . . . . . . . . 6
6.1. XML for RFCs . . . . . . . . . . . . . . . . . . . . . . 6 6.1. XML for RFCs . . . . . . . . . . . . . . . . . . . . . . 6
7. Publication Format Documents . . . . . . . . . . . . . . . . 8 7. Publication Format Documents . . . . . . . . . . . . . . . . 7
7.1. HTML . . . . . . . . . . . . . . . . . . . . . . . . . . 8 7.1. HTML . . . . . . . . . . . . . . . . . . . . . . . . . . 7
7.2. PDF . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 7.2. PDF . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
7.3. Plain Text . . . . . . . . . . . . . . . . . . . . . . . 9 7.3. Plain Text . . . . . . . . . . . . . . . . . . . . . . . 8
7.4. Potential Future Publication Formats . . . . . . . . . . 9 7.4. Potential Future Publication Formats . . . . . . . . . . 9
7.4.1. EPUB . . . . . . . . . . . . . . . . . . . . . . . . 9 7.4.1. EPUB . . . . . . . . . . . . . . . . . . . . . . . . 9
8. Figures and Artwork . . . . . . . . . . . . . . . . . . . . . 9 8. Figures and Artwork . . . . . . . . . . . . . . . . . . . . . 9
8.1. SVG . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 8.1. SVG . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
9. Content and Page Layout . . . . . . . . . . . . . . . . . . . 10 9. Content and Page Layout . . . . . . . . . . . . . . . . . . . 9
9.1. Non-ASCII Characters . . . . . . . . . . . . . . . . . . 10 9.1. Non-ASCII Characters . . . . . . . . . . . . . . . . . . 9
9.2. Style Guide . . . . . . . . . . . . . . . . . . . . . . . 10 9.2. Style Guide . . . . . . . . . . . . . . . . . . . . . . . 10
9.3. CSS Requirements . . . . . . . . . . . . . . . . . . . . 10 9.3. CSS Requirements . . . . . . . . . . . . . . . . . . . . 10
10. Transition Plan . . . . . . . . . . . . . . . . . . . . . . . 10 10. Transition Plan . . . . . . . . . . . . . . . . . . . . . . . 10
10.1. Statement of Work and RFP for Tool Development . . . . . 10 10.1. Statement of Work and RFP for Tool Development . . . . . 10
10.2. Testing and Transition . . . . . . . . . . . . . . . . . 10 10.2. Testing and Transition . . . . . . . . . . . . . . . . . 10
10.3. Completion . . . . . . . . . . . . . . . . . . . . . . . 12 10.3. Completion . . . . . . . . . . . . . . . . . . . . . . . 11
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
12. Security Considerations . . . . . . . . . . . . . . . . . . . 12 12. Security Considerations . . . . . . . . . . . . . . . . . . . 12
13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12
14. Appendix - Change log . . . . . . . . . . . . . . . . . . . . 12 14. Appendix - Change log . . . . . . . . . . . . . . . . . . . . 12
14.1. draft-iab-rfc-framework-00 to -01 . . . . . . . . . . . 12 14.1. draft-iab-rfc-framework-00 to -01 . . . . . . . . . . . 12
15. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 15. References . . . . . . . . . . . . . . . . . . . . . . . . . 12
15.1. Normative References . . . . . . . . . . . . . . . . . . 13 15.1. Normative References . . . . . . . . . . . . . . . . . . 12
15.2. Informative References . . . . . . . . . . . . . . . . . 14 15.2. Informative References . . . . . . . . . . . . . . . . . 13
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 15 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 15
1. Introduction 1. Introduction
[RFC6949], "RFC Series Format Requirements and Future Development," [RFC6949], "RFC Series Format Requirements and Future Development,"
discussed the need for additional features within RFCs such as non- discussed the need for additional features within RFCs such as non-
ASCII characters to respect author names, more advanced artwork than ASCII characters to respect author names, more advanced artwork than
ASCII art, and documents that could display properly on a wide ASCII art, and documents that could display properly on a wide
variety of devices. Based on the discussions with the IETF community variety of devices. Based on the discussions with the IETF community
skipping to change at page 3, line 41 skipping to change at page 3, line 41
The details described in this document are expected to change based The details described in this document are expected to change based
on experience gained in implementing the RFC production center's on experience gained in implementing the RFC production center's
toolset. Revised documents will be published capturing those changes toolset. Revised documents will be published capturing those changes
as the toolset is completed. Other implementers must not expect as the toolset is completed. Other implementers must not expect
those changes to remain backwards-compatible with the details those changes to remain backwards-compatible with the details
described this document. described this document.
2. Problem Statement 2. Problem Statement
When the first RFCs were published 45 years ago, the tools to create There are nearly three billion people connected to the Internet, and
and read RFCs were limited. Distribution was originally on paper via individuals from 45 countries or more regularly attending IETF
postal mail to people living in the United States. meetings over the last 5 years [ISTATS]. The Internet is now global,
and while the world has changed from when the first RFCs were
Today, there are nearly three billion people connected to the published, the Series remains critical to defining protocols,
Internet, and individuals from 45 countries or more regularly standards, best practices, and more for this global network that
attending IETF meetings over the last 5 years [ISTATS]. The Internet continues to grow. In order to make RFCs easily viewable to the
is now global, and while the world has changed from when the first largest number of people possible, across a wide array of devices,
RFCs were published, the Series remains critical to defining and to respect the diversity of authors and reference materials, it
protocols, standards, best practices, and more for this global is time to update the tightly prescribed format of the RFC Series.
network that continues to grow. In order to make RFCs easily
viewable to the largest number of people possible, across a wide
array of devices, and to respect the diversity of authors and
reference materials, it is time to update the tightly prescribed
format of the RFC Series.
All changes to the format of the RFC Series must consider the All changes to the format of the RFC Series must consider the
requirements of a wide set of communities, over an extended length of requirements of a wide set of communities, over an extended length of
time. For example, existing authors and implementers, lawyers that time. For example, existing authors and implementers, lawyers that
argue Intellectual Property Rights (IPR), educators, managers, and argue Intellectual Property Rights (IPR), educators, managers, and
policy-makers that need to know what to list in potential RFPs for policy-makers that need to know what to list in potential RFPs for
their organizations, all have preferences and requirements for their their organizations, all have preferences and requirements for their
specific needs. The immediate needs of today's communities must be specific needs. The immediate needs of today's communities must be
balanced with the needs for long-term archival storage. balanced with the needs for long-term archival storage.
 End of changes. 7 change blocks. 
25 lines changed or deleted 20 lines changed or added

This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/