draft-iab-rfc-framework-02.txt   draft-iab-rfc-framework-03.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 February 2, 2016
Expires: July 23, 2016 Expires: August 5, 2016
RFC Format Framework RFC Format Framework
draft-iab-rfc-framework-02 draft-iab-rfc-framework-03
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 1, line 47 skipping to change at page 1, line 47
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 23, 2016. This Internet-Draft will expire on August 5, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 8, line 18 skipping to change at page 8, line 18
format. format.
o The body of the document will use a subset of HTML. The documents o The body of the document will use a subset of HTML. The documents
will include CSS for default visual presentation; it can be will include CSS for default visual presentation; it can be
overwritten by a local CSS file. overwritten by a local CSS file.
o SVG is supported and will be included in the HTML file. o SVG is supported and will be included in the HTML file.
o Text will be reflowable. o Text will be reflowable.
o JavaScript will be supported only as an additional option for o JavaScript will be supported on a limited basis. It will not be
presentation of specific publication formats to provide up-to-date permitted to overwrite or change any text present in the rendered
links to post-publication metadata, such as errata or obsoletion. html. It may, on a limited basis, add additional text that
Documents will be complete and readable as at time of publication, provides post-publication metadata or pointers if warranted. All
when JavaScript is disabled. such text will be clearly marked as additional.
7.2. PDF 7.2. PDF
[I-D.hansen-rfc-use-of-pdf] - Describes the tags and profiles that [I-D.iab-rfc-use-of-pdf] - Describes the tags and profiles that will
will be used to create the new PDF format, including both the be used to create the new PDF format, including both the internal
internal structure and the visible layout of the file. A review of structure and the visible layout of the file. A review of the
the different versions of PDF is offered, with a recommendation of different versions of PDF is offered, with a recommendation of what
what PDF standard should apply to RFCs. PDF standard should apply to RFCs.
Key points regarding the PDF output: Key points regarding the PDF output:
o The PDF file will not be derived from the plain-text publication o The PDF file will not be derived from the plain-text publication
format. format.
o The PDF publication format will conform to the PDF/A-3 standard o The PDF publication format will conform to the PDF/A-3 standard
and will embed the canonical XML source. and will embed the canonical XML source.
o The PDF will look more like the HTML publication format than the o The PDF will look more like the HTML publication format than the
skipping to change at page 13, line 15 skipping to change at page 13, line 15
[I-D.iab-xml2rfc] [I-D.iab-xml2rfc]
Hoffman, P., "The "xml2rfc" version 3 Vocabulary", draft- Hoffman, P., "The "xml2rfc" version 3 Vocabulary", draft-
iab-xml2rfc-02 (work in progress), January 2016. iab-xml2rfc-02 (work in progress), January 2016.
[I-D.iab-xml2rfcv2] [I-D.iab-xml2rfcv2]
Reschke, J., "The 'XML2RFC' version 2 Vocabulary", draft- Reschke, J., "The 'XML2RFC' version 2 Vocabulary", draft-
iab-xml2rfcv2-02 (work in progress), September 2015. iab-xml2rfcv2-02 (work in progress), September 2015.
[I-D.iab-svg-rfc] [I-D.iab-svg-rfc]
Brownlee, N., "SVG Drawings for RFCs: SVG 1.2 RFC", draft- Brownlee, N., "SVG Drawings for RFCs: SVG 1.2 RFC", draft-
iab-svg-rfc-00 (work in progress), January 2016. iab-svg-rfc-01 (work in progress), January 2016.
[I-D.iab-html-rfc] [I-D.iab-html-rfc]
Hildebrand, J. and P. Hoffman, "HyperText Markup Language Hildebrand, J. and P. Hoffman, "HyperText Markup Language
Request For Comments Format", draft-iab-html-rfc-01 (work Request For Comments Format", draft-iab-html-rfc-01 (work
in progress), January 2016. in progress), January 2016.
[I-D.hansen-rfc-use-of-pdf] [I-D.iab-rfc-use-of-pdf]
Hansen, T., Masinter, L., and M. Hardy, "PDF for an RFC Hansen, T., Masinter, L., and M. Hardy, "PDF for an RFC
Series Output Document Format", draft-hansen-rfc-use-of- Series Output Document Format", draft-iab-rfc-use-of-
pdf-08 (work in progress), October 2015. pdf-01 (work in progress), January 2016.
[I-D.iab-rfc-plaintext] [I-D.iab-rfc-plaintext]
Flanagan, H., "Requirements for Plain-Text RFCs", draft- Flanagan, H., "Requirements for Plain-Text RFCs", draft-
iab-rfc-plaintext-01 (work in progress), January 2016. iab-rfc-plaintext-01 (work in progress), January 2016.
[I-D.iab-rfc-nonascii] [I-D.iab-rfc-nonascii]
Flanagan, H., "The Use of Non-ASCII Characters in RFCs", Flanagan, H., "The Use of Non-ASCII Characters in RFCs",
draft-iab-rfc-nonascii-00 (work in progress), January draft-iab-rfc-nonascii-00 (work in progress), January
2016. 2016.
 End of changes. 8 change blocks. 
18 lines changed or deleted 18 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/