< draft-flanagan-7322bis-01.txt   draft-flanagan-7322bis-02.txt >
Network Working Group H. Flanagan Network Working Group H. Flanagan
Internet-Draft S. Ginoza Internet-Draft S. Ginoza
Intended status: Informational RFC Editor Intended status: Informational RFC Editor
Expires: January 18, 2018 July 17, 2017 Expires: March 16, 2018 September 12, 2017
RFC Style Guide RFC Style Guide
draft-flanagan-7322bis-01 draft-flanagan-7322bis-02
Abstract Abstract
This document describes the fundamental and unique style conventions This document describes the fundamental and unique style conventions
and editorial policies currently in use for the RFC Series. It and editorial policies currently in use for the RFC Series. It
captures the RFC Editor's basic requirements and offers guidance captures the RFC Editor's basic requirements and offers guidance
regarding the style and structure of an RFC. Additional guidance is regarding the style and structure of an RFC. Additional guidance is
captured on a website that reflects the experimental nature of that captured on a website that reflects the experimental nature of that
guidance and prepares it for future inclusion in the RFC Style Guide. guidance and prepares it for future inclusion in the RFC Style Guide.
This document obsoletes RFC 7322, "RFC Style Guide". This document obsoletes RFC 7322, "RFC Style Guide".
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 https://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 January 18, 2018. This Internet-Draft will expire on March 16, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 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 (https://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 . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
skipping to change at page 2, line 34 skipping to change at page 2, line 34
4.1.3. ISSN: 2070-1721 . . . . . . . . . . . . . . . . . . . 11 4.1.3. ISSN: 2070-1721 . . . . . . . . . . . . . . . . . . . 11
4.1.4. Updates and Obsoletes . . . . . . . . . . . . . . . . 11 4.1.4. Updates and Obsoletes . . . . . . . . . . . . . . . . 11
4.2. Document Title . . . . . . . . . . . . . . . . . . . . . 11 4.2. Document Title . . . . . . . . . . . . . . . . . . . . . 11
4.3. Abstract Section . . . . . . . . . . . . . . . . . . . . 12 4.3. Abstract Section . . . . . . . . . . . . . . . . . . . . 12
4.4. RFC Editor or Stream Notes Section . . . . . . . . . . . 12 4.4. RFC Editor or Stream Notes Section . . . . . . . . . . . 12
4.5. Status of This Memo Section . . . . . . . . . . . . . . . 13 4.5. Status of This Memo Section . . . . . . . . . . . . . . . 13
4.6. Copyright, Licenses, and IPR Boilerplate Section . . . . 13 4.6. Copyright, Licenses, and IPR Boilerplate Section . . . . 13
4.7. Table of Contents Section . . . . . . . . . . . . . . . . 13 4.7. Table of Contents Section . . . . . . . . . . . . . . . . 13
4.8. Body of the Memo . . . . . . . . . . . . . . . . . . . . 13 4.8. Body of the Memo . . . . . . . . . . . . . . . . . . . . 13
4.8.1. Introduction Section . . . . . . . . . . . . . . . . 13 4.8.1. Introduction Section . . . . . . . . . . . . . . . . 13
4.8.2. Requirements Language Section . . . . . . . . . . . . 13 4.8.2. Requirements Language Section . . . . . . . . . . . . 14
4.8.3. IANA Considerations Section . . . . . . . . . . . . . 14 4.8.3. IANA Considerations Section . . . . . . . . . . . . . 14
4.8.4. Internationalization Considerations Section . . . . . 14 4.8.4. Internationalization Considerations Section . . . . . 15
4.8.5. Security Considerations Section . . . . . . . . . . . 15 4.8.5. Security Considerations Section . . . . . . . . . . . 15
4.8.6. References Section . . . . . . . . . . . . . . . . . 15 4.8.6. References Section . . . . . . . . . . . . . . . . . 15
4.9. Appendices Section . . . . . . . . . . . . . . . . . . . 21 4.9. Appendices Section . . . . . . . . . . . . . . . . . . . 21
4.10. Acknowledgements Section . . . . . . . . . . . . . . . . 21 4.10. Acknowledgements Section . . . . . . . . . . . . . . . . 21
4.11. Contributors Section . . . . . . . . . . . . . . . . . . 21 4.11. Contributors Section . . . . . . . . . . . . . . . . . . 21
4.12. Index . . . . . . . . . . . . . . . . . . . . . . . . . . 21 4.12. Index . . . . . . . . . . . . . . . . . . . . . . . . . . 21
4.13. Author's Address or Authors' Addresses Section . . . . . 21 4.13. Author's Address or Authors' Addresses Section . . . . . 21
5. Security Considerations . . . . . . . . . . . . . . . . . . . 22 5. Security Considerations . . . . . . . . . . . . . . . . . . . 22
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22
7. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 22 7. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 22
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 22 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 22
8.1. Normative References . . . . . . . . . . . . . . . . . . 22 8.1. Normative References . . . . . . . . . . . . . . . . . . 22
8.2. Informative References . . . . . . . . . . . . . . . . . 22 8.2. Informative References . . . . . . . . . . . . . . . . . 22
8.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Appendix A. Related Procedures . . . . . . . . . . . . . . . . . 26 Appendix A. Related Procedures . . . . . . . . . . . . . . . . . 26
A.1. Dispute Resolution . . . . . . . . . . . . . . . . . . . 26 A.1. Dispute Resolution . . . . . . . . . . . . . . . . . . . 26
A.2. Returning an I-D to the Document Stream . . . . . . . . . 26 A.2. Returning an I-D to the Document Stream . . . . . . . . . 26
A.3. Revising This Document and Associated Web Pages . . . . . 26 A.3. Revising This Document and Associated Web Pages . . . . . 26
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 27 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 27
1. Introduction 1. Introduction
The ultimate goal of the RFC publication process is to produce The ultimate goal of the RFC publication process is to produce
documents that are readable, clear, and consistent. The basic documents that are readable, clear, and consistent. The basic
skipping to change at page 12, line 21 skipping to change at page 12, line 21
The RFC Editor recommends that documents describing a particular The RFC Editor recommends that documents describing a particular
company's private protocol should bear a title of the form "Foo's ... company's private protocol should bear a title of the form "Foo's ...
Protocol" (where Foo is a company name), to clearly differentiate it Protocol" (where Foo is a company name), to clearly differentiate it
from a protocol of more general applicability. from a protocol of more general applicability.
4.3. Abstract Section 4.3. Abstract Section
Every RFC must have an Abstract that provides a concise and Every RFC must have an Abstract that provides a concise and
comprehensive overview of the purpose and contents of the entire comprehensive overview of the purpose and contents of the entire
document, to give a technically knowledgeable reader a general document, to give a technically knowledgeable reader a general
overview of the function of the document. overview of the function of the document and some context with
regards to its relationship (in particular, whether it updates or
obsoletes) any other RFCs. In addition to its function in the RFC
itself, the Abstract section text will appear in publication
announcements and in the online index of RFCs.
Composing a useful Abstract generally requires thought and care. Composing a useful Abstract generally requires thought and care.
Usually, an Abstract should begin with a phrase like "This memo ..." Usually, an Abstract should begin with a phrase like "This memo ..."
or "This document ..." A satisfactory Abstract can often be or "This document ..." A satisfactory Abstract can often be
constructed in part from material within the Introduction section, constructed in part from material within the Introduction section,
but an effective Abstract may be shorter, less detailed, and perhaps but an effective Abstract may be shorter, less detailed, and perhaps
broader in scope than the Introduction. Simply copying and pasting broader in scope than the Introduction. Simply copying and pasting
the first few paragraphs of the Introduction is allowed, but it may the first few paragraphs of the Introduction is allowed, but it may
result in an Abstract that is both incomplete and redundant. Note result in an Abstract that is overly long, incomplete, and redundant.
also that an Abstract is not a substitute for an Introduction; the
RFC should be self-contained as if there were no Abstract.
Similarly, the Abstract should be complete in itself. It will appear
in isolation in publication announcements and in the online index of
RFCs. Therefore, the Abstract must not contain citations.
If the RFC updates or obsoletes an earlier RFC, that should be An Abstract is not a substitute for an Introduction; the RFC should
mentioned in the abstract as well. be self-contained as if there were no Abstract. Similarly, the
Abstract should be complete in itself. Given that the Abstract will
appear independently in announcements and indices, mentions of other
RFCs within the Abstract should include both an RFC number and either
the full or short title. Any documents that are Updated or Obsoleted
by the RFC must be mentioned in the Abstract. These may be presented
in a list format if that improves readability.
4.4. RFC Editor or Stream Notes Section 4.4. RFC Editor or Stream Notes Section
A stream-approving body may approve the inclusion of an editorial A stream-approving body may approve the inclusion of an editorial
note to explain anything unusual about the process that led to the note to explain anything unusual about the process that led to the
document's publication or to note a correction. In this case, a document's publication or to note a correction. In this case, a
stream note section will contain such a note. stream note section will contain such a note.
Additionally, an RFC Editor Note section may contain a note inserted Additionally, an RFC Editor Note section may contain a note inserted
by the RFC Editor to highlight special circumstances surrounding an by the RFC Editor to highlight special circumstances surrounding an
skipping to change at page 17, line 7 skipping to change at page 17, line 13
legacy RFCs, this may be left blank. legacy RFCs, this may be left blank.
Note the ordering for multiple authors: the format of the name of the Note the ordering for multiple authors: the format of the name of the
last author listed is different than that of all previous authors in last author listed is different than that of all previous authors in
the list. the list.
For one author or editor: For one author or editor:
[RFCXXXX] Last name, First initial., Ed. (if applicable), "RFC [RFCXXXX] Last name, First initial., Ed. (if applicable), "RFC
Title", Stream, Sub-series number (if applicable), RFC number, DOI, Title", Stream, Sub-series number (if applicable), RFC number, DOI,
Date of publication, https://www.rfc-editor.org/info/rfc#. Date of publication, https://www.rfc-editor.org/info/rfc# [1].
Example: Example:
[RFC3080] Rose, M., "The Blocks Extensible Exchange Protocol Core," [RFC3080] Rose, M., "The Blocks Extensible Exchange Protocol Core,"
IETF, RFC 3080, DOI 10.17487/RFC3080, March 2001, https://www.rfc- IETF, RFC 3080, DOI 10.17487/RFC3080, March 2001, https://www.rfc-
editor.org/info/rfc3080. editor.org/info/rfc3080 [2].
[RFC8157] Leymann, N., Heidemann, C., Zhang, M., Sarikaya, B., and M. [RFC8157] Leymann, N., Heidemann, C., Zhang, M., Sarikaya, B., and M.
Cullen, "Huawei's GRE Tunnel Bonding Protocol", independent, RFC Cullen, "Huawei's GRE Tunnel Bonding Protocol", independent, RFC
8157, DOI 10.17487/RFC8157, May 2017, https://www.rfc- 8157, DOI 10.17487/RFC8157, May 2017, https://www.rfc-
editor.org/info/rfc8157. editor.org/info/rfc8157 [3].
For two authors or editors: For two authors or editors:
[RFCXXXX] Last name, First initial., Ed. (if applicable) and First [RFCXXXX] Last name, First initial., Ed. (if applicable) and First
initial. Last name, Ed. (if applicable), "RFC Title", Stream, Sub- initial. Last name, Ed. (if applicable), "RFC Title", Stream, Sub-
series number (if applicable), RFC number, DOI, Date of publication, series number (if applicable), RFC number, DOI, Date of publication,
https://www.rfc-editor.org/info/rfc#. https://www.rfc-editor.org/info/rfc# [4].
Example: Example:
[RFC6323] Renker, G. and G. Fairhurst, "Sender RTT Estimate Option [RFC6323] Renker, G. and G. Fairhurst, "Sender RTT Estimate Option
for the Datagram Congestion Control Protocol (DCCP)", IETF, RFC 6323, for the Datagram Congestion Control Protocol (DCCP)", IETF, RFC 6323,
DOI 10.17487/RFC6323, July 2011, https://www.rfc-editor.org/info/ DOI 10.17487/RFC6323, July 2011, https://www.rfc-editor.org/info/
rfc6323. rfc6323 [5].
For three or more authors or editors: For three or more authors or editors:
[RFCXXXX] Last name, First initial., Ed. (if applicable), Last name, [RFCXXXX] Last name, First initial., Ed. (if applicable), Last name,
First initial., Ed. (if applicable), and First initial. Last name, First initial., Ed. (if applicable), and First initial. Last name,
Ed. (if applicable), "RFC Title", Stream, Sub-series number (if Ed. (if applicable), "RFC Title", Stream, Sub-series number (if
applicable), RFC number, DOI, Date of publication, https://www.rfc- applicable), RFC number, DOI, Date of publication, https://www.rfc-
editor.org/info/rfc#. editor.org/info/rfc# [6].
Example: Example:
[RFC6429] Bashyam, M., Jethanandani, M., and A. Ramaiah, "TCP Sender [RFC6429] Bashyam, M., Jethanandani, M., and A. Ramaiah, "TCP Sender
Clarification for Persist Condition", IETF, RFC 6429, DOI 10.17487/ Clarification for Persist Condition", IETF, RFC 6429, DOI 10.17487/
RFC6429, December 2011, https://www.rfc-editor.org/info/rfc6429. RFC6429, December 2011, https://www.rfc-editor.org/info/rfc6429 [7].
4.8.6.3. Referencing STDs and BCPs 4.8.6.3. Referencing STDs and BCPs
Internet Standards (STDs) and Best Current Practices (BCPs) may Internet Standards (STDs) and Best Current Practices (BCPs) may
consist of a single RFC or multiple RFCs. When an STD or BCP that consist of a single RFC or multiple RFCs. When an STD or BCP that
contains multiple RFCs is referenced, the reference entry should contains multiple RFCs is referenced, the reference entry should
include ALL of the RFCs comprising that sub-series. The authors include ALL of the RFCs comprising that sub-series. The authors
should refer to specific RFC numbers as part of the text (not as should refer to specific RFC numbers as part of the text (not as
citations) and cite the sub-series number. Inclusion of the URI to citations) and cite the sub-series number. Inclusion of the URI to
the STD or BCP info page is recommended. The text should appear as the STD or BCP info page is recommended. The text should appear as
follows: follows:
See RFC 1034 [STD13]. See RFC 1034 [STD13].
For an STD or BCP that contains one RFC: For an STD or BCP that contains one RFC:
[STDXXX] Last name, First initial., Ed. (if applicable), "RFC [STDXXX] Last name, First initial., Ed. (if applicable), "RFC
Title", Stream, Sub-series number, RFC number, DOI, Date of Title", Stream, Sub-series number, RFC number, DOI, Date of
publication, https://www.rfc-editor.org/info/std#. publication, https://www.rfc-editor.org/info/std# [8].
Example: Example:
[STD72] Gellens, R. and J. Klensin, "Message Submission for Mail", [STD72] Gellens, R. and J. Klensin, "Message Submission for Mail",
IETF, STD 72, RFC 6409, DOI 10.17487/RFC6409, November 2011, IETF, STD 72, RFC 6409, DOI 10.17487/RFC6409, November 2011,
https://www.rfc-editor.org/info/std72. https://www.rfc-editor.org/info/std72 [9].
For an STD or BCP that contains two or more RFCs: For an STD or BCP that contains two or more RFCs:
[STDXXX] Last name, First initial., Ed. (if applicable), "RFC [STDXXX] Last name, First initial., Ed. (if applicable), "RFC
Title", Stream, Sub-series number, RFC number, DOI, Date of Title", Stream, Sub-series number, RFC number, DOI, Date of
publication. publication.
Last name, First initial., Ed. (if applicable) Last name, First initial., Ed. (if applicable)
and First initial. Last name, Ed. (if applicable), and First initial. Last name, Ed. (if applicable),
"RFC Title", Stream, Sub-series number, RFC number, DOI, "RFC Title", Stream, Sub-series number, RFC number, DOI,
skipping to change at page 22, line 29 skipping to change at page 22, line 29
6. IANA Considerations 6. IANA Considerations
This document has no IANA considerations. This document has no IANA considerations.
7. Change Log 7. Change Log
This section to be removed before publication. This section to be removed before publication.
-00 to -01: Citation tag requirements more tightly specified; -00 to -01: Citation tag requirements more tightly specified;
index moved; new errata URI added; capitalization of working/ index moved; new errata URI added; capitalization of working/
research group specified research group specified; update Abstract guidance
8. References 8. References
8.1. Normative References 8.1. Normative References
[STYLE-WEB] [STYLE-WEB]
RFC Editor, "Web Portion of the Style Guide", RFC Editor, "Web Portion of the Style Guide",
<https://www.rfc-editor.org/rfc-style-guide/part2.html>. <https://www.rfc-editor.org/rfc-style-guide/part2.html>.
8.2. Informative References 8.2. Informative References
skipping to change at page 23, line 10 skipping to change at page 23, line 10
[BCP18] Alvestrand, H., "IETF Policy on Character Sets and [BCP18] Alvestrand, H., "IETF Policy on Character Sets and
Languages", BCP 18, RFC 2277, January 1998, Languages", BCP 18, RFC 2277, January 1998,
<https://www.rfc-editor.org/info/bcp18>. <https://www.rfc-editor.org/info/bcp18>.
[BCP26] Alvestrand, H. and T. Narten, "Guidelines for Writing an [BCP26] Alvestrand, H. and T. Narten, "Guidelines for Writing an
ANA Considerations Section in RFCs", BCP 26, RFC 5226, May ANA Considerations Section in RFCs", BCP 26, RFC 5226, May
2008, <https://www.rfc-editor.org/info/bcp26>. 2008, <https://www.rfc-editor.org/info/bcp26>.
[BCP32] Eastlake 3rd, D. and A. Panitz, "Reserved Top Level DNS [BCP32] Eastlake 3rd, D. and A. Panitz, "Reserved Top Level DNS
Names", BCP 32, RFC 2606, June 1999, <https://www.rfc- Names", BCP 32, RFC 2606, June 1999,
editor.org/info/bcp32>. <https://www.rfc-editor.org/info/bcp32>.
[BCP72] Rescorla, E. and B. Korver, "Guidelines for Writing RFC [BCP72] Rescorla, E. and B. Korver, "Guidelines for Writing RFC
Text on Security Considerations", BCP 72, RFC 3552, July Text on Security Considerations", BCP 72, RFC 3552, July
2003, <https://www.rfc-editor.org/info/bcp72>. 2003, <https://www.rfc-editor.org/info/bcp72>.
[CLUSTER] RFC Editor, "Clusters in the RFC Editor Queue", [CLUSTER] RFC Editor, "Clusters in the RFC Editor Queue",
<https://www.rfc-editor.org/cluster_def.html>. <https://www.rfc-editor.org/cluster_def.html>.
[CMOS] University of Chicago Press, 2010, "Chicago Manual of [CMOS] University of Chicago Press, 2010, "Chicago Manual of
Style, 16th ed.", 2010. Style, 16th ed.", 2010.
[FYI90] Malkin, G. and J. Reynolds, "FYI on FYI: Introduction to [FYI90] Malkin, G. and J. Reynolds, "FYI on FYI: Introduction to
the FYI Notes", FYI 90, RFC 1150, March 1990, the FYI Notes", FYI 90, RFC 1150, March 1990,
<https://www.rfc-editor.org/info/fyi90>. <https://www.rfc-editor.org/info/fyi90>.
Housley, R., "Conclusion of FYI RFC Sub-Series", RFC 6360, Housley, R., "Conclusion of FYI RFC Sub-Series", RFC 6360,
August 2011. August 2011.
[IAB-FORM] [IAB-FORM]
IAB, "Format for RFCs in the IAB Stream", IAB, "Format for RFCs in the IAB Stream",
<https://www.rfc-editor.org/rfc-style-guide/iab- <https://www.rfc-editor.org/rfc-style-guide/
format.txt>. iab-format.txt>.
[ID-GUIDE] [ID-GUIDE]
IETF, "Guidelines to Authors of Internet Drafts", IETF, "Guidelines to Authors of Internet Drafts",
<https://www.ietf.org/ietf-ftp/1id-guidelines.txt>. <https://www.ietf.org/ietf-ftp/1id-guidelines.txt>.
[IETF-TRUST] [IETF-TRUST]
IETF Trust, "Trust Legal Provisions (TLP)", IETF Trust, "Trust Legal Provisions (TLP)",
<https://trustee.ietf.org/license-info/>. <https://trustee.ietf.org/license-info/>.
[ISO3297] Technical Committee ISO/TC 46, Information and [ISO3297] Technical Committee ISO/TC 46, Information and
skipping to change at page 24, line 10 skipping to change at page 24, line 10
standard serial number (ISSN)", September 2007. standard serial number (ISSN)", September 2007.
[ISO_OBP] ISO, "Online Browsing Platform (OBP)", [ISO_OBP] ISO, "Online Browsing Platform (OBP)",
<https://www.iso.org/obp/ui/>. <https://www.iso.org/obp/ui/>.
[MIB-BOILER] [MIB-BOILER]
IETF OPS Area, "Boilerplate for IETF MIB Documents", IETF OPS Area, "Boilerplate for IETF MIB Documents",
<https://www.ops.ietf.org/mib-boilerplate.html>. <https://www.ops.ietf.org/mib-boilerplate.html>.
[MIB-SEC] IETF OPS Area, "Security Guidelines for IETF MIB Modules", [MIB-SEC] IETF OPS Area, "Security Guidelines for IETF MIB Modules",
<https://trac.tools.ietf.org/area/ops/trac/wiki/mib- <https://trac.tools.ietf.org/area/ops/trac/wiki/
security>. mib-security>.
[REFEXAMPLE] [REFEXAMPLE]
RFC Editor, "Reference Examples", <https://www.rfc- RFC Editor, "Reference Examples",
editor.org/ref-example/>. <https://www.rfc-editor.org/ref-example/>.
[REFS] IESG, "IESG Statement: Normative and Informative", [REFS] IESG, "IESG Statement: Normative and Informative",
<https://www.ietf.org/iesg/statement/normative- <https://www.ietf.org/iesg/statement/
informative.html>. normative-informative.html>.
[RFC1311] Postel, J., "Introduction to the STD Notes", RFC 1311, [RFC1311] Postel, J., "Introduction to the STD Notes", RFC 1311,
DOI 10.17487/RFC1311, March 1992, DOI 10.17487/RFC1311, March 1992,
<http://www.rfc-editor.org/info/rfc1311>. <https://www.rfc-editor.org/info/rfc1311>.
[RFC1818] Postel, J., Li, T., and Y. Rekhter, "Best Current [RFC1818] Postel, J., Li, T., and Y. Rekhter, "Best Current
Practices", RFC 1818, DOI 10.17487/RFC1818, August 1995, Practices", RFC 1818, DOI 10.17487/RFC1818, August 1995,
<http://www.rfc-editor.org/info/rfc1818>. <https://www.rfc-editor.org/info/rfc1818>.
[RFC4844] Daigle, L., Ed. and Internet Architecture Board, "The RFC [RFC4844] Daigle, L., Ed. and Internet Architecture Board, "The RFC
Series and RFC Editor", RFC 4844, DOI 10.17487/RFC4844, Series and RFC Editor", RFC 4844, DOI 10.17487/RFC4844,
July 2007, <http://www.rfc-editor.org/info/rfc4844>. July 2007, <https://www.rfc-editor.org/info/rfc4844>.
[RFC6635] Kolkman, O., Ed., Halpern, J., Ed., and IAB, "RFC Editor [RFC6635] Kolkman, O., Ed., Halpern, J., Ed., and IAB, "RFC Editor
Model (Version 2)", RFC 6635, DOI 10.17487/RFC6635, June Model (Version 2)", RFC 6635, DOI 10.17487/RFC6635, June
2012, <http://www.rfc-editor.org/info/rfc6635>. 2012, <https://www.rfc-editor.org/info/rfc6635>.
[RFC7841] Halpern, J., Ed., Daigle, L., Ed., and O. Kolkman, Ed., [RFC7841] Halpern, J., Ed., Daigle, L., Ed., and O. Kolkman, Ed.,
"RFC Streams, Headers, and Boilerplates", RFC 7841, "RFC Streams, Headers, and Boilerplates", RFC 7841,
DOI 10.17487/RFC7841, May 2016, DOI 10.17487/RFC7841, May 2016,
<http://www.rfc-editor.org/info/rfc7841>. <https://www.rfc-editor.org/info/rfc7841>.
[RFC7990] Flanagan, H., "RFC Format Framework", RFC 7990, [RFC7990] Flanagan, H., "RFC Format Framework", RFC 7990,
DOI 10.17487/RFC7990, December 2016, DOI 10.17487/RFC7990, December 2016,
<http://www.rfc-editor.org/info/rfc7990>. <https://www.rfc-editor.org/info/rfc7990>.
[RFC7996] Brownlee, N., "SVG Drawings for RFCs: SVG 1.2 RFC", [RFC7996] Brownlee, N., "SVG Drawings for RFCs: SVG 1.2 RFC",
RFC 7996, DOI 10.17487/RFC7996, December 2016, RFC 7996, DOI 10.17487/RFC7996, December 2016,
<http://www.rfc-editor.org/info/rfc7996>. <https://www.rfc-editor.org/info/rfc7996>.
[RFC7997] Flanagan, H., Ed., "The Use of Non-ASCII Characters in [RFC7997] Flanagan, H., Ed., "The Use of Non-ASCII Characters in
RFCs", RFC 7997, DOI 10.17487/RFC7997, December 2016, RFCs", RFC 7997, DOI 10.17487/RFC7997, December 2016,
<http://www.rfc-editor.org/info/rfc7997>. <https://www.rfc-editor.org/info/rfc7997>.
[STD66] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform [STD66] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66, Resource Identifier (URI): Generic Syntax", STD 66,
RFC 3986, January 2005, <https://www.rfc-editor.org/info/ RFC 3986, January 2005,
std66>. <https://www.rfc-editor.org/info/std66>.
[TERMS] RFC Editor, "Terms List", <https://www.rfc-editor.org/ [TERMS] RFC Editor, "Terms List",
styleguide.html>. <https://www.rfc-editor.org/styleguide.html>.
[YANG-SEC] [YANG-SEC]
IETF Ops Area, "yang module security considerations", IETF Ops Area, "yang module security considerations",
<https://trac.tools.ietf.org/area/ops/trac/wiki/yang- <https://trac.tools.ietf.org/area/ops/trac/wiki/
security-guidelines>. yang-security-guidelines>.
8.3. URIs
[1] https://www.rfc-editor.org/info/rfc#
[2] https://www.rfc-editor.org/info/rfc3080
[3] https://www.rfc-editor.org/info/rfc8157
[4] https://www.rfc-editor.org/info/rfc#
[5] https://www.rfc-editor.org/info/rfc6323
[6] https://www.rfc-editor.org/info/rfc#
[7] https://www.rfc-editor.org/info/rfc6429
[8] https://www.rfc-editor.org/info/std#
[9] https://www.rfc-editor.org/info/std72
Appendix A. Related Procedures Appendix A. Related Procedures
The following procedures are related to the application and updating The following procedures are related to the application and updating
of the RFC Style Guide. of the RFC Style Guide.
A.1. Dispute Resolution A.1. Dispute Resolution
There are competing rationales for some of the rules described in There are competing rationales for some of the rules described in
this Guide, and the RFC Editor has selected the ones that work best this Guide, and the RFC Editor has selected the ones that work best
 End of changes. 37 change blocks. 
51 lines changed or deleted 76 lines changed or added

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