<pre>Internet Architecture Board (IAB)                            H. Flanagan
Request for Comments: 6949                             RFC Series Editor
Updates: <a href="./rfc2223">2223</a>                                                N. Brownlee
Category: Informational                   Independent Submissions Editor
ISSN: 2070-1721                                                 May 2013


         <span class="h1">RFC Series Format Requirements and Future Development</span>

Abstract

   This document describes the current requirements and requests for
   enhancements for the format of the canonical version of RFCs.  Terms
   are defined to help clarify exactly which stages of document
   production are under discussion for format changes.  The requirements
   described in this document will determine what changes will be made
   to RFC format.  This document updates <a href="./rfc2223">RFC 2223</a>.

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for informational purposes.

   This document is a product of the Internet Architecture Board (IAB)
   and represents information that the IAB has deemed valuable to
   provide for permanent record.  It represents the consensus of the
   Internet Architecture Board (IAB).  Documents approved for
   publication by the IAB are not a candidate for any level of Internet
   Standard; see <a href="./rfc5741#section-2">Section&nbsp;2 of RFC 5741</a>.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   <a href="http://www.rfc-editor.org/info/rfc6949">http://www.rfc-editor.org/info/rfc6949</a>.

Copyright Notice

   Copyright (c) 2013 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.






<span class="grey">Brownlee &amp; Flanagan           Informational                     [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc6949">RFC 6949</a>             RFC Series Format Requirements             May 2013</span>


Table of Contents

   <a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
      <a href="#section-1.1">1.1</a>. Terminology ................................................<a href="#page-3">3</a>
   <a href="#section-2">2</a>. History and Goals ...............................................<a href="#page-4">4</a>
      <a href="#section-2.1">2.1</a>. Issues Driving Change ......................................<a href="#page-5">5</a>
           <a href="#section-2.1.1">2.1.1</a>. ASCII Art ...........................................<a href="#page-5">5</a>
           <a href="#section-2.1.2">2.1.2</a>. Character Encoding ..................................<a href="#page-6">6</a>
           <a href="#section-2.1.3">2.1.3</a>. Pagination ..........................................<a href="#page-7">7</a>
           <a href="#section-2.1.4">2.1.4</a>. Reflowable Text .....................................<a href="#page-8">8</a>
           <a href="#section-2.1.5">2.1.5</a>. Metadata and Tagging ................................<a href="#page-8">8</a>
      <a href="#section-2.2">2.2</a>. Further Considerations .....................................<a href="#page-9">9</a>
           <a href="#section-2.2.1">2.2.1</a>. Creation and Use of RFC-Specific Tools ..............<a href="#page-9">9</a>
           <a href="#section-2.2.2">2.2.2</a>. Markup Language ....................................<a href="#page-10">10</a>
      <a href="#section-2.3">2.3</a>. RFC Editor Goals ..........................................<a href="#page-10">10</a>
   <a href="#section-3">3</a>. Format Requirements ............................................<a href="#page-10">10</a>
      <a href="#section-3.1">3.1</a>. Original Requirements to Be Retained ......................<a href="#page-10">10</a>
      <a href="#section-3.2">3.2</a>. Requirements to Be Added ..................................<a href="#page-11">11</a>
      <a href="#section-3.3">3.3</a>. Requirements to Be Retired ................................<a href="#page-12">12</a>
   <a href="#section-4">4</a>. Security Considerations ........................................<a href="#page-13">13</a>
   <a href="#section-5">5</a>. Informative References .........................................<a href="#page-13">13</a>
   <a href="#section-6">6</a>. Acknowledgements ...............................................<a href="#page-13">13</a>

<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>  Introduction</span>

   Over 40 years ago, the RFC Series began as a collection of memos in
   an environment that included handwritten RFCs, typewritten RFCs, RFCs
   produced on mainframes with complicated layout tools, and more.  As
   the tools changed and some of the source formats became unreadable,
   the core individuals behind the Series realized that a common format
   that could be read, revised, and archived long in the future was
   required.  US-ASCII was chosen for the encoding of characters, and
   after a period of variability, a well-defined presentation format was
   settled upon.  That format has proved to be persistent and reliable
   across a large variety of devices, operating systems, and editing
   tools.  That stability has been a continuing strength of the Series.
   However, as new technology, such as small devices and advances in
   display technology, comes into common usage, there is a growing
   desire to see the format of the RFC Series adapt to take advantage of
   these different ways to communicate information.

   Since the format stabilized, authors and readers have suggested
   enhancements to the format.  However, no suggestion developed clear
   consensus in the Internet technical community.  As always, some
   individuals see no need for change, while others press strongly for
   specific enhancements.





<span class="grey">Brownlee &amp; Flanagan           Informational                     [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc6949">RFC 6949</a>             RFC Series Format Requirements             May 2013</span>


   This document takes a look at the current requirements for RFCs as
   described in <a href="./rfc2223">RFC 2223</a> [<a href="./rfc2223" title="&quot;Instructions to RFC Authors&quot;">RFC2223</a>] and more recently in 2223bis
   [<a href="#ref-2223bis" title="&quot;Instructions to Request for Comments (RFC) Authors&quot;">2223bis</a>].  <a href="#section-2">Section 2</a> reviews recent requests for enhancements as
   understood from community discussion and various proposals for new
   formats including HTML, XML, PDF, and EPUB.  The actual requirements
   are then captured in <a href="#section-3">Section 3</a>.  The focus of this document is on the
   Canonical format of RFCs, but some mention of other phases in the RFC
   publication process and the document formats associated with these
   phases is also included.  Terms are defined to help clarify exactly
   which stages of document production are under discussion for format
   changes.

<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>  Terminology</span>

   ASCII: Coded Character Set -- 7-bit American Standard Code for
   Information Interchange, ANSI X3.4-1986 [<a href="#ref-ASCII" title="March 26">ASCII</a>]

   Canonical format: the authorized, recognized, accepted, and archived
   version of the document
      *  Currently: formatted plain text

   Metadata: information associated with a document so as to provide,
   for example, definitions of its structure, or of elements within the
   document such as its topic or author

   Publication format: display and distribution format as it may be read
   or printed after the publication process has completed
      *  Currently published by the RFC Editor: formatted plain text,
         PDF of the formatted plain text, PDF that contains figures
         (rare)
      *  Currently made available by other sites: HTML, PDF, others

   Reflowable text: text that automatically wraps to the next line in a
   document as the user moves the margins of the text, either by
   resizing the window or changing the font size

   Revisable format: the format that will provide the information for
   conversion into a Publication format; it is used or created by the
   RFC Editor (see <a href="#section-2.3">Section 2.3</a> for an explanation of current practice)
      *  Currently: XML (optional), nroff (required)

   Submission format: the format submitted to the RFC Editor for
   editorial revision and publication
      * Currently: formatted plain text (required), XML (optional),
         nroff (optional)






<span class="grey">Brownlee &amp; Flanagan           Informational                     [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc6949">RFC 6949</a>             RFC Series Format Requirements             May 2013</span>


<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>.  History and Goals</span>

   Below are the current RFC format rules as defined in [<a href="./rfc2223" title="&quot;Instructions to RFC Authors&quot;">RFC2223</a>] and
   clarified in 2223bis.

      *  The character codes are ASCII.

      *  Each page must be limited to 58 lines followed by a form feed
         on a line by
            itself.

      *  Each line must be limited to 72 characters followed by carriage
         return and line feed.

      *  No overstriking (or underlining) is allowed.

      *  These "height" and "width" constraints include any headers,
         footers, page numbers, or left-side indenting.

      *  Do not fill the text with extra spaces to provide a straight
         right margin.

      *  Do not do hyphenation of words at the right margin.

      *  Do not use footnotes.  If such notes are necessary, put them at
         the end of a section, or at the end of the document.

      *  Use single spaced text within a paragraph, and one blank line
         between paragraphs.

      *  Note that the number of pages in a document and the page
         numbers on which various sections fall will likely change with
         reformatting.  Thus, cross-references in the text by section
         number usually are easier to keep consistent than cross-
         references by page number.

      *  RFCs in plain ASCII text may be submitted to the RFC Editor in
         e-mail messages (or as online files) in either the finished
         Publication format or in nroff.  If you plan to submit a
         document in nroff please consult the RFC Editor first.

   The precedent for additional formats, specifically PostScript, is
   described in <a href="./rfc2223">RFC 2223</a> and has been used for a small number of RFCs:

      Note that since the ASCII text version of the RFC is the primary
      version, the PostScript version must match the text version.  The
      RFC Editor must decide if the PostScript version is "the same as"
      the ASCII version before the PostScript version can be published.



<span class="grey">Brownlee &amp; Flanagan           Informational                     [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc6949">RFC 6949</a>             RFC Series Format Requirements             May 2013</span>


   Neither <a href="./rfc2223">RFC 2223</a> nor 2223bis uses the term 'metadata', though the RFC
   Editor currently refers to components of the text such as the Stream,
   Status (e.g., Updates, Obsoletes), Category, and ISSN as 'metadata'.

<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>.  Issues Driving Change</span>

   While some authors and readers of RFCs report that they find the
   strict limits of character encoding, line limits, and so on to be
   acceptable, others claim to find those limitations a significant
   obstacle to their desire to communicate and read the information via
   an RFC.  With a broader community of authors currently producing RFCs
   and a wider range of presentation devices in use, the issues being
   reported by the community indicate limitations of the current
   Canonical format that must be reviewed and potentially addressed in
   the Canonical RFC format.

   While the specific points of concern vary, the main issues discussed
   are:

      *  ASCII art

      *  Character encoding

      *  Pagination

      *  Reflowable text

      *  Metadata

   Each area of concern has people in favor of change and people opposed
   to it, all with reasonable concerns and requirements.  Below is a
   summary of the arguments for and against each major issue.  These
   points are not part of the list of requirements; they are the inputs
   that informed the requirements discussed in <a href="#section-3">Section 3</a> of this
   document.

<span class="h4"><a class="selflink" id="section-2.1.1" href="#section-2.1.1">2.1.1</a>.  ASCII Art</span>

   Arguments in favor of limiting all diagrams, equations, tables, and
   charts to ASCII art depictions only include:

      *  Dependence on advanced diagrams (or any diagrams) causes
         accessibility issues.

      *  Requiring ASCII art results in people often relying more on
         clear written descriptions rather than just the diagram itself.





<span class="grey">Brownlee &amp; Flanagan           Informational                     [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc6949">RFC 6949</a>             RFC Series Format Requirements             May 2013</span>


      *  Use of the ASCII character set forces design of diagrams that
         are simple and concise.

   Arguments in favor of allowing the use of more complex diagrams in
   place of the current use of ASCII art include:

      *  State diagrams with multiple arrows in different directions and
         labels on the lines will be more understandable.

      *  Protocol flow diagrams in which each step needs multiple lines
         of description will be clearer.

      *  Scenario descriptions that involve three or more parties with
         communication flows between them will be clearer.

      *  Given the difficulties in expressing complex equations with
         common mathematical notation, allowing graphic art would allow
         equations to be displayed properly.

      *  Complex art could allow for grayscale or color to be introduced
         into the diagrams.

   Two suggestions have been proposed regarding how graphics should be
   included: one that would have graphic art referenced as a separate
   document to the Publication format, and one that would allow embedded
   graphics in the Publication format.

<span class="h4"><a class="selflink" id="section-2.1.2" href="#section-2.1.2">2.1.2</a>.  Character Encoding</span>

   For most of the history of the RFC Series, the character encoding for
   RFCs has been ASCII.  Below are arguments for keeping ASCII as well
   as arguments for expanding to UTF-8.

   Arguments for retaining the ASCII-only requirement:

      *  It is the most easy to search and display across a variety of
         platforms.

      *  In extreme cases of having to retype or scan hard copies of
         documents (it has been required in the past), ASCII is
         significantly easier to work with for rescanning and retaining
         all of the original information.  There can be no loss of
         descriptive metadata such as keywords or content tags.








<span class="grey">Brownlee &amp; Flanagan           Informational                     [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc6949">RFC 6949</a>             RFC Series Format Requirements             May 2013</span>


      *  If we expand beyond ASCII, it will be difficult to know where
         to draw the line on which characters are and are not allowed.
         There will be issues with dependencies on local file systems
         and processors being configured to recognize any other
         character set.

      *  The IETF works in ASCII (and English).  The Internet research,
         design, and development communities function almost entirely in
         English.  That strongly suggests that an ASCII document can be
         properly rendered and read by everyone in the communities and
         audiences of interest.

   Arguments for expanding to allow UTF-8:

      *  In discussions of internationalization, actually being able to
         illustrate the issue is rather helpful, and you can't
         illustrate a Unicode code point with "U+nnnn".

      *  It will provide the ability to denote protocol examples using
         the character sets those examples support.

      *  It will allow better support for international character sets,
         in particular, allowing authors to spell their names in their
         native character sets.

      *  Certain special characters in equations or quoted from other
         texts could be allowed.

      *  Citations of web pages using more international characters are
         possible.

   Arguments for strictly prescribed UTF-8 use:

      *  In order to keep documents as searchable as possible, ASCII-
         only should be required for the main text of the document, and
         some broader UTF-8 character set allowed under clearly
         prescribed circumstances (e.g., author names and references).

<span class="h4"><a class="selflink" id="section-2.1.3" href="#section-2.1.3">2.1.3</a>.  Pagination</span>

   Arguments for continuing the use of discrete pages within RFCs:

      *  Ease of reference and printing; referring to section numbers is
         too coarse a method.







<span class="grey">Brownlee &amp; Flanagan           Informational                     [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc6949">RFC 6949</a>             RFC Series Format Requirements             May 2013</span>


   Arguments for removing the pagination requirement:

      *  Removing pagination will allow for a smoother reading
         experience on a wider variety of devices, platforms, and
         browsers.

      *  Removing pagination results in people often using subsections
         rather than page number for reference purposes, forcing what
         would otherwise be long sections to be broken into subsections.
         This would encourage documents that are better organized and
         simpler.

<span class="h4"><a class="selflink" id="section-2.1.4" href="#section-2.1.4">2.1.4</a>.  Reflowable Text</span>

   Arguments against requiring text to be reflowable:

      *  Reflowable text may impact the usability of graphics and tables
         within a document.

   Arguments for requiring text to be reflowable:

      *  RFCs are more readable on a wider variety of devices and
         platforms, including mobile devices and assorted screen
         layouts.

<span class="h4"><a class="selflink" id="section-2.1.5" href="#section-2.1.5">2.1.5</a>.  Metadata and Tagging</span>

   While metadata requirements are not part of <a href="./rfc2223">RFC 2223</a>, there is a
   request that descriptive metadata tags be added as part of a revision
   of the Canonical RFC format.  These tags would allow for enhanced
   content by embedding information such as links, tags, or quick
   translations and could help control the look and feel of the
   Publication format.  While the lack of metadata in the current RFCs
   does not impact an RFC's accessibility or readability, several
   individuals have indicated that allowing metadata within the RFCs
   would make their reading of the documents more efficient.

   Arguments for allowing metadata in the Canonical and Publication
   formats:

      *  Metadata potentially allows readers to get more detail out of a
         document.  For example, if non-ASCII characters are allowed in
         the Author's Address and Reference sections, metadata must
         include translations of that information.







<span class="grey">Brownlee &amp; Flanagan           Informational                     [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc6949">RFC 6949</a>             RFC Series Format Requirements             May 2013</span>


   Arguments against metadata in the final Canonical and Publication
   formats:

      *  Metadata adds additional overhead to the overall process of
         creating RFCs and may complicate future usability as a result
         of requiring backward compatibility for metadata tags.

<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>.  Further Considerations</span>

   Some of the discussion beyond the issues described above went into a
   review of potential solutions.  Those solutions and the debate around
   them added a few more points to the list of potential requirements
   for a change in RFC Format.  In particular, the discussion of tools
   introduced the idea of whether a change in format should also include
   the creation and ongoing support of specific RFC authoring and/or
   rendering tools and whether the Canonical format should be a format
   that must go through a rendering agent to be readable.

<span class="h4"><a class="selflink" id="section-2.2.1" href="#section-2.2.1">2.2.1</a>.  Creation and Use of RFC-Specific Tools</span>

   Arguments in support of community-supported RFC-specific tools:

      *  Given the community that would be creating and supporting these
         tools, there would be greater control and flexibility over the
         tools and how they implement the RFC format requirements.

      *  Community-supported tools currently exist and are in extensive
         use within the community, so it would be most efficient to
         build on that base.

   Arguments against community-supported RFC-specific tools:

      *  We cannot be so unique in our needs that we can't use
         commercial tools.

      *  Ongoing support for these tools adds a greater level of
         instability to the ongoing availability of the RFC Series
         through the decades.

      *  The community that would support these tools cannot be relied
         on to be as stable and persistent as the Series itself.










<span class="grey">Brownlee &amp; Flanagan           Informational                     [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc6949">RFC 6949</a>             RFC Series Format Requirements             May 2013</span>


<span class="h4"><a class="selflink" id="section-2.2.2" href="#section-2.2.2">2.2.2</a>.  Markup Language</span>

   Arguments in support of a markup language as the Revisable format:

      *  Having a markup language such as XML or HTML allows for greater
         flexibility in creating a variety of Publication formats, with
         a greater likelihood of similarity between them.

   Arguments against a markup language as the Revisable format:

      *  Having the Revisable format be in a markup language instead of
         in a simple text-formatting structure ties us in to specific
         tools and/or tool support going forward.

<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>.  RFC Editor Goals</span>

   Currently, each RFC has an nroff file created prior to publication.
   For RFCs revised using an XML file, the nroff file is created by
   converting XML to nroff at the final step.  As more documents are
   submitted with an XML file (of the RFCs published in 2012,
   approximately 65% were submitted with an XML file), this conversion
   is problematic in terms of time spent and data lost from XML.  Making
   the publication process for the RFC Editor more efficient is strongly
   desired.

<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>.  Format Requirements</span>

   Understanding the major pain points and balancing them with the
   expectation of long-term viability of the documents brings us to a
   review of what must be kept of the original requirements, what new
   requirements may be added, and what requirements may be retired.
   Detailed rules regarding how these changes will be implemented will
   be documented in a future RFC.

<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>.  Original Requirements to Be Retained</span>

   Several components of the original format requirements must be
   retained to ensure the ongoing continuity, reliability, and
   readability of the Series:

      1.  The content of an RFC must not change, regardless of format,
          once published.

      2.  The Canonical format must be persistent and reliable across a
          large variety of devices, operating systems, and editing tools
          for the indefinite future.  This means the format must be both
          readable and editable across commonly used devices, operating
          systems, and platforms for the foreseeable future.



<span class="grey">Brownlee &amp; Flanagan           Informational                    [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc6949">RFC 6949</a>             RFC Series Format Requirements             May 2013</span>


      3.  While several Publication formats must be allowed, in order to
          continue support for the most basic reading and search tools
          and to provide continuity for the Series, at least one
          Publication format must be plain text.

      4.  The boilerplate and overall structure of the RFC must be in
          accordance with current RFC and Style Guide requirements (see
          [<a href="./rfc5741" title="&quot;RFC Streams, Headers, and Boilerplates&quot;">RFC5741</a>]).

   Issues such as overstriking, page justification, hyphenation, and
   spacing will be defined in the RFC Style Guide [<a href="#ref-Style" title="&quot;RFC Style Guide&quot;">Style</a>].

<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>.  Requirements to Be Added</span>

   In addition to those continuing requirements, discussions with
   various members of the wider Internet community have yielded the
   following general requirements for the RFC Series.

      5.  The documents must be made accessible to people with visual
          disabilities through such means as including alternative text
          for images and limiting the use of color.  See the W3C's
          accessibility documents [<a href="#ref-WCAG20" title="&quot;Web Content Accessibility Guidelines (WCAG) 2.0&quot;">WCAG20</a>] and the United Nations
          "Convention on the Rights of Persons with Disabilities"
          [<a href="#ref-UN2006" title="&quot;Convention on the Rights of Persons with Disabilities&quot;">UN2006</a>] for guidance.  Appropriate authoring tools are highly
          desirable but focus on the creation of Internet-Drafts, a
          topic outside the scope of the RFC Editor.

      6.  The official language of the RFC Series is English.  ASCII is
          required for all text that must be read to understand or
          implement the technology described in the RFC.  Use of non-
          ASCII characters, expressed in a standard Unicode Encoding
          Form (such as UTF-8), must receive explicit approval from the
          document stream manager and will be allowed after the rules
          for the common use cases are defined in the Style Guide.

      7.  The Submission and Publication formats need to permit
          extending the set of metadata tags, for the addition of
          labeled metadata.  A predefined set of metadata tags must be
          created to make use of metadata tags consistent for the life
          of the Series.

      8.  Graphics may include ASCII art and a more complex form to be
          defined, such as SVG line art [<a href="#ref-SVG" title="&quot;Scalable Vector Graphics (SVG) 1.1 (Second Edition)&quot;">SVG</a>].  Color and grayscale will
          not be accepted.  RFCs must correctly display in monochromatic
          black-and-white to allow for monochrome displays, black-and-
          white printing, and support for visual disabilities.





<span class="grey">Brownlee &amp; Flanagan           Informational                    [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc6949">RFC 6949</a>             RFC Series Format Requirements             May 2013</span>


      9.  The Canonical format must be renderable into self-contained
          Publication formats in order to be easily downloaded and read
          offline.

      10. Fixed-width fonts and non-reflowable text are required for
          ASCII-art sections, source code examples, and other places
          where strict alignment is required.

      11. At least one Publication format must support readable print to
          standard paper sizes.

      12. The Canonical format should be structured to enable easy
          program identification and parsing of code or specifications,
          such as MIB modules and ABNF.

   The requirements of the RFC Editor regarding RFC format and the
   publication process include:

      13. The final conversion of all submitted documents to nroff
          should be replaced by using an accepted Revisable format
          throughout the process.

      14. In order to maintain an efficient publication process, the RFC
          Editor must work with the minimal number of files required for
          each submission (not a tar ball of several discrete
          components).

      15. In order to maintain the focus of the RFC Editor on editing
          for clarity and consistency rather than document layout
          details, the number of Publication formats produced by the RFC
          editor must be limited.

      16. Tools must support error checking against document layout
          issues as well as other format details (diagrams, line breaks,
          variable- and fixed-width fonts).

<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>.  Requirements to Be Retired</span>

   Some of the original requirements will be removed from consideration,
   but detailed rules regarding how these changes will be implemented
   will be documented in a future RFC.

      *  Pagination ("Each page must be limited to 58 lines followed by
         a form feed on a line by itself.")

      *  Maximum line length ("Each line must be limited to 72
         characters followed by carriage return and line feed.")




<span class="grey">Brownlee &amp; Flanagan           Informational                    [Page 12]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
<span class="grey"><a href="./rfc6949">RFC 6949</a>             RFC Series Format Requirements             May 2013</span>


      *  Limitation to 100% ASCII text ("The character codes are
         ASCII.")

<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>.  Security Considerations</span>

   This document sets out requirements for RFCs in their various
   formats; it does not concern interactions between Internet hosts.
   Therefore, it does not have any specific security considerations.

<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>.  Informative References</span>

   [<a id="ref-RFC2223">RFC2223</a>]  Postel, J. and J. Reynolds, "Instructions to RFC Authors",
              <a href="./rfc2223">RFC 2223</a>, October 1997.

   [<a id="ref-RFC5741">RFC5741</a>]  Daigle, L., Ed., Kolkman, O., Ed., and IAB, "RFC Streams,
              Headers, and Boilerplates", <a href="./rfc5741">RFC 5741</a>, December 2009.

   [<a id="ref-ASCII">ASCII</a>]    American National Standard for Information Systems - Coded
              Character Sets - 7-Bit American National Standard Code for
              Information Interchange (7-Bit ASCII), ANSI X3.4-1986,
              American National Standards Institute, Inc., March 26,
              1986.

   [<a id="ref-2223bis">2223bis</a>]  Reynolds, J. and R. Braden, "Instructions to Request for
              Comments (RFC) Authors", Work in Progress, August 2004.

   [<a id="ref-Style">Style</a>]    Flanagan, H. and S. Ginoza, <a style="text-decoration: none" href='https://www.google.com/search?sitesearch=datatracker.ietf.org%2Fdoc%2Fhtml%2F&amp;q=inurl:draft-+%22RFC+Style+Guide%22'>"RFC Style Guide"</a>, Work in
              Progress, October 2012.

   [<a id="ref-SVG">SVG</a>]      Dahlstrom, E., Dengler, P., Grasso, A., Lilley, C.,
              McCormack, C., Schepers, D., and J. Watt, "Scalable Vector
              Graphics (SVG) 1.1 (Second Edition)", W3C Recommendation,
              16 August 2011, &lt;<a href="http://www.w3.org/TR/SVG11/">http://www.w3.org/TR/SVG11/</a>&gt;.

   [<a id="ref-WCAG20">WCAG20</a>]   Caldwell, B., Cooper, M., Reid, L., and G. Vanderheiden,
              "Web Content Accessibility Guidelines (WCAG) 2.0", 11
              December 2008, &lt;<a href="http://www.w3.org/TR/WCAG20/">http://www.w3.org/TR/WCAG20/</a>&gt;.

   [<a id="ref-UN2006">UN2006</a>]   United Nations, "Convention on the Rights of Persons with
              Disabilities", December 2006.

<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>.  Acknowledgements</span>

   The authors received a great deal of helpful input from the community
   in pulling together these requirements and wish to particularly
   acknowledge the help of Joe Hildebrand, Paul Hoffman, and John
   Klensin, who each published an Internet-Draft on the topic of
   potential format options before the IETF 84 BOF.



<span class="grey">Brownlee &amp; Flanagan           Informational                    [Page 13]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
<span class="grey"><a href="./rfc6949">RFC 6949</a>             RFC Series Format Requirements             May 2013</span>


Authors' Addresses

   Heather Flanagan
   RFC Series Editor

   EMail: rse@rfc-editor.org


   Nevil Brownlee
   Independent Submissions Editor

   EMail rfc-ise@rfc-editor.org







































Brownlee &amp; Flanagan           Informational                    [Page 14]
</pre>