draft-iab-rfc5741bis-01.txt   draft-iab-rfc5741bis-02.txt 
Network Working Group J. Halpern, Ed. Network Working Group J. Halpern, Ed.
Internet-Draft Internet-Draft
Obsoletes: 5741 (if approved) L. Daigle, Ed. Obsoletes: 5741 (if approved) L. Daigle, Ed.
Intended status: Informational Intended status: Informational
Expires: June 14, 2016 O. Kolkman, Ed. Expires: August 5, 2016 O. Kolkman, Ed.
Internet Society Internet Society
Internet Architecture Board Internet Architecture Board
(IAB) (IAB)
December 12, 2015 February 2, 2016
On RFC Streams, Headers, and Boilerplates On RFC Streams, Headers, and Boilerplates
draft-iab-rfc5741bis-01 draft-iab-rfc5741bis-02
Abstract Abstract
RFC documents contain a number of fixed elements such as the title RFC documents contain a number of fixed elements such as the title
page header, standard boilerplates and copyright/IPR statements. page header, standard boilerplates and copyright/IPR statements.
This document describes them and introduces some updates to reflect This document describes them and introduces some updates to reflect
current usage and requirements of RFC publication. In particular, current usage and requirements of RFC publication. In particular,
this updated structure is intended to communicate clearly the source this updated structure is intended to communicate clearly the source
of RFC creation and review. This document obsoletes RFC 5741, moving of RFC creation and review. This document obsoletes RFC 5741, moving
detailed content to an IAB web page and preparing for more flexible detailed content to an IAB web page and preparing for more flexible
skipping to change at page 1, line 42 skipping to change at page 1, line 42
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 June 14, 2016. This Internet-Draft will expire on August 5, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. RFC Streams and Internet Standards . . . . . . . . . . . . . 3 2. RFC Streams and Internet Standards . . . . . . . . . . . . . 3
3. RFC Structural Elements . . . . . . . . . . . . . . . . . . . 4 3. RFC Structural Elements . . . . . . . . . . . . . . . . . . . 4
3.1. The title page header . . . . . . . . . . . . . . . . . . 4 3.1. The title page header . . . . . . . . . . . . . . . . . . 4
3.2. The Status of this Memo . . . . . . . . . . . . . . . . . 5 3.2. The Status of this Memo . . . . . . . . . . . . . . . . . 5
3.3. Paragraph 1 . . . . . . . . . . . . . . . . . . . . . . . 5 3.3. Paragraph 1 . . . . . . . . . . . . . . . . . . . . . . . 6
3.4. Paragraph 2 . . . . . . . . . . . . . . . . . . . . . . . 6 3.4. Paragraph 2 . . . . . . . . . . . . . . . . . . . . . . . 6
3.5. Paragraph 3 . . . . . . . . . . . . . . . . . . . . . . . 6 3.5. Paragraph 3 . . . . . . . . . . . . . . . . . . . . . . . 6
3.6. Noteworthy . . . . . . . . . . . . . . . . . . . . . . . 6 3.6. Noteworthy . . . . . . . . . . . . . . . . . . . . . . . 6
4. Additional Notes . . . . . . . . . . . . . . . . . . . . . . 6 4. Additional Notes . . . . . . . . . . . . . . . . . . . . . . 6
5. Other structural information in RFCs . . . . . . . . . . . . 7 5. Other structural information in RFCs . . . . . . . . . . . . 7
6. Security considerations . . . . . . . . . . . . . . . . . . . 7 6. Security considerations . . . . . . . . . . . . . . . . . . . 7
7. IANA considerations . . . . . . . . . . . . . . . . . . . . . 7 7. IANA considerations . . . . . . . . . . . . . . . . . . . . . 7
8. RFC Editor Considerations . . . . . . . . . . . . . . . . . . 7 8. RFC Editor Considerations . . . . . . . . . . . . . . . . . . 7
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
9.1. Normative References . . . . . . . . . . . . . . . . . . 8 9.1. Normative References . . . . . . . . . . . . . . . . . . 8
skipping to change at page 4, line 19 skipping to change at page 4, line 19
3. RFC Structural Elements 3. RFC Structural Elements
This section describes the elements that are commonly found in RFCs This section describes the elements that are commonly found in RFCs
published today. This document specifies information that is published today. This document specifies information that is
required in these publications. Exact specification of the textual required in these publications. Exact specification of the textual
values required therein are provided by an IAB web page values required therein are provided by an IAB web page
(URL to be provided during AUTH48). (URL to be provided during AUTH48).
As noted above, this web page is maintained by the IAB with due As noted above, this web page is maintained by the IAB with due
consultation with the community. Initial proposed text to be used in consultation with the community. Following such consultation, if the
that web page is included in Appendix C. IAB decides to make any changes to this material, the changes will be
announced in a similar fashion to other IAB statements. Initial
proposed text to be used in that web page is included in Appendix C.
3.1. The title page header 3.1. The title page header
The information at the front of the RFC includes the name and The information at the front of the RFC includes the name and
affiliation of the authors as well as the RFC publication month and affiliation of the authors as well as the RFC publication month and
year. year.
There is a set of additional information that is needed at the front There is a set of additional information that is needed at the front
of the RFC. Historically, this has been presented with the of the RFC. Historically, this has been presented with the
information below in a left hand column, and the author related information below in a left hand column, and the author related
skipping to change at page 10, line 24 skipping to change at page 10, line 33
The IAB members at the time this memo was approved were (in The IAB members at the time this memo was approved were (in
alphabetical order): alphabetical order):
Appendix B. Acknowledgements Appendix B. Acknowledgements
Thanks to Bob Braden, Brian Carpenter, Steve Crocker, Sandy Ginoza, Thanks to Bob Braden, Brian Carpenter, Steve Crocker, Sandy Ginoza,
and John Klensin who provided background information and inspiration. and John Klensin who provided background information and inspiration.
Thanks to the members of the RFC Series Oversight Committee (RSOC) Thanks to the members of the RFC Series Oversight Committee (RSOC)
for assistance and review: Alexey Melnikov, Nevil Brownlee, Bob for assistance and review: Alexey Melnikov, Nevil Brownlee, Bob
Hinden, Sarah Banks, Robert Sparks, and Joe Hildebrand. Hinden, Sarah Banks, Robert Sparks, Tony Hansen, and Joe Hildebrand.
Various people have made suggestions that improved the document. Various people have made suggestions that improved the document.
Among them are: Lars Eggert, Alfred Hoenes, and Joe Touch. Among them are: Lars Eggert, Alfred Hoenes, and Joe Touch.
This document was produced using the xml2rfc tool [RFC2629]. This document was produced using the xml2rfc tool [RFC2629].
Appendix C. Initial Formating Details Appendix C. Initial Formating Details
This section provides suggested starting text for the use of the IAB This section provides suggested starting text for the use of the IAB
in order to simplify populating the web page to be used to maintain in order to simplify populating the web page to be used to maintain
 End of changes. 8 change blocks. 
9 lines changed or deleted 11 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/