<?xml version='1.0' encoding='utf-8'?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" version="3" category="info" consensus="false" docName="draft-ietf-xml2rfc-template-05" indexInclude="true" ipr="trust200902" prepTime="2020-04-10T09:26:48" scripts="Common,Latin" sortRefs="true" submissionType="IETF" symRefs="true" tocDepth="4" tocInclude="true" xml:lang="en">
  <!-- xml2rfc v2v3 conversion 2.41.0 -->
  
  
  
  <!-- category values: std, bcp, info, exp, and historic
     ipr values: full3667, noModification3667, noDerivatives3667
     you can add the attributes updates="NNNN" and obsoletes="NNNN" 
     they will automatically be output with "(if approved)" -->

  <!-- ***** FRONT MATTER ***** -->

  <front>
    <!-- The abbreviated title is used in the page header - it is only necessary if the 
         full title is longer than 39 characters -->

    <title abbrev="Abbreviated Title">Put Your Internet Draft Title Here</title>
    <seriesInfo name="Internet-Draft" value="draft-ietf-xml2rfc-template-05" stream="IETF"/>
    <!-- add 'role="editor"' below for the editors if appropriate -->

    <!-- Another author who claims to be an editor -->
    <author fullname="Elwyn Davies" initials="E.B." role="editor" surname="Davies">
      <organization showOnFrontPage="true">Folly Consulting</organization>
      <address>
        <postal>
          <street/>
          <!-- Reorder these if your country does things differently -->

          <city>Soham</city>
          <region/>
          <code/>
          <country>UK</country>
        </postal>
        <phone>+44 7889 488 335</phone>
        <email>elwynd@dial.pipex.com</email>
        <!-- uri and facsimile elements may also be added -->
      </address>
    </author>
    <!-- for testing trac #189 -->
    <author fullname="Quintin Zhao" initials="Q." surname="Zhao">
      <organization showOnFrontPage="true">Huawei Technology</organization>
      <address>
        <postal>
          <street>125 Nagog Technology Park</street>
          <city>Acton</city>
          <region>MA</region>
          <code>01719</code>
          <country>US</country>
        </postal>
        <email>quintin.zhao@huawei.com</email>
      </address>
    </author>
    <date month="03" year="2009" day="1"/>
    <!-- If the month and year are both specified and are the current ones, xml2rfc will fill 
         in the current day for you. If only the current year is specified, xml2rfc will fill 
	 in the current day and month for you. If the year is not the current one, it is 
	 necessary to specify at least a month (xml2rfc assumes day="1" if not specified for the 
	 purpose of calculating the expiry date).  With drafts it is normally sufficient to 
	 specify just the year. -->

    <!-- Meta-data Declarations -->

    <area>General</area>
    <workgroup>Internet Engineering Task Force</workgroup>
    <!-- WG name at the upperleft corner of the doc,
         IETF is fine for individual submissions.  
	 If this element is not present, the default is "Network Working Group",
         which is used by the RFC Editor as a nod to the history of the IETF. -->

    <keyword>template</keyword>
    <!-- Keywords will be incorporated into HTML output
         files in a meta tag but they have no effect on text or nroff
         output. If you submit your draft to the RFC Editor, the
         keywords will be used for the search engine. -->

    <abstract pn="section-abstract">
      <t pn="section-abstract-1">Insert an abstract: MANDATORY. This template is for creating an
      Internet Draft.</t>
    </abstract>
    <boilerplate>
      <section anchor="status-of-memo" numbered="false" removeInRFC="false" toc="exclude" pn="section-boilerplate.1">
        <name slugifiedName="name-status-of-this-memo">Status of This Memo</name>
        <t pn="section-boilerplate.1-1">
        This Internet-Draft is submitted in full conformance with the
        provisions of BCP 78 and BCP 79.
        </t>
        <t pn="section-boilerplate.1-2">
        Internet-Drafts are working documents of the Internet Engineering Task
        Force (IETF). Note that other groups may also distribute working
        documents as Internet-Drafts. The list of current Internet-Drafts is
        at <eref target="http://datatracker.ietf.org/drafts/current/" brackets="none"/>.
        </t>
        <t pn="section-boilerplate.1-3">
        Internet-Drafts are draft documents valid for a maximum of six months
        and may be updated, replaced, or obsoleted by other documents at any
        time. It is inappropriate to use Internet-Drafts as reference
        material or to cite them other than as "work in progress."
        </t>
        <t pn="section-boilerplate.1-4">
        This Internet-Draft will expire on 2 September 2009.
        </t>
      </section>
      <section anchor="copyright" numbered="false" removeInRFC="false" toc="exclude" pn="section-boilerplate.2">
        <name slugifiedName="name-copyright-notice">Copyright Notice</name>
        <t pn="section-boilerplate.2-1">
            Copyright (c) 2009 IETF Trust and the persons identified as
            the document authors.  All rights reserved. 
        </t>
        <t pn="section-boilerplate.2-2">
            This document is subject to BCP 78 and the IETF Trust's Legal
            Provisions Relating to IETF Documents in effect on the date of
            publication of this document (http://trustee.ietf.org/license-info).
            Please review these documents carefully, as they describe your rights
            and restrictions with respect to this document.
        </t>
      </section>
    </boilerplate>
    <toc>
      <section anchor="toc" numbered="false" removeInRFC="false" toc="exclude" pn="section-toc.1">
        <name slugifiedName="name-table-of-contents">Table of Contents</name>
        <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1">
          <li pn="section-toc.1-1.1">
            <t keepWithNext="true" pn="section-toc.1-1.1.1"><xref derivedContent="1" format="counter" sectionFormat="of" target="section-1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-introduction">Introduction</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.1.2">
              <li pn="section-toc.1-1.1.2.1">
                <t keepWithNext="true" pn="section-toc.1-1.1.2.1.1"><xref derivedContent="1.1" format="counter" sectionFormat="of" target="section-1.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-requirements-language">Requirements Language</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.2">
            <t keepWithNext="true" pn="section-toc.1-1.2.1"><xref derivedContent="2" format="counter" sectionFormat="of" target="section-2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-simple-list">Simple List</xref></t>
          </li>
          <li pn="section-toc.1-1.3">
            <t pn="section-toc.1-1.3.1"><xref derivedContent="3" format="counter" sectionFormat="of" target="section-3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-figures">Figures</xref></t>
          </li>
          <li pn="section-toc.1-1.4">
            <t pn="section-toc.1-1.4.1"><xref derivedContent="4" format="counter" sectionFormat="of" target="section-4"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-subsections-and-tables">Subsections and Tables</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.4.2">
              <li pn="section-toc.1-1.4.2.1">
                <t pn="section-toc.1-1.4.2.1.1"><xref derivedContent="4.1" format="counter" sectionFormat="of" target="section-4.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-a-subsection">A Subsection</xref></t>
              </li>
              <li pn="section-toc.1-1.4.2.2">
                <t pn="section-toc.1-1.4.2.2.1"><xref derivedContent="4.2" format="counter" sectionFormat="of" target="section-4.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-tables">Tables</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.5">
            <t pn="section-toc.1-1.5.1"><xref derivedContent="5" format="counter" sectionFormat="of" target="section-5"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-more-about-lists">More about Lists</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.5.2">
              <li pn="section-toc.1-1.5.2.1">
                <t pn="section-toc.1-1.5.2.1.1"><xref derivedContent="5.1" format="counter" sectionFormat="of" target="section-5.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-numbering-lists-across-list">Numbering Lists across Lists and Sections</xref></t>
              </li>
              <li pn="section-toc.1-1.5.2.2">
                <t pn="section-toc.1-1.5.2.2.1"><xref derivedContent="5.2" format="counter" sectionFormat="of" target="section-5.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-where-the-list-numbering-co">Where the List Numbering Continues</xref></t>
              </li>
              <li pn="section-toc.1-1.5.2.3">
                <t pn="section-toc.1-1.5.2.3.1"><xref derivedContent="5.3" format="counter" sectionFormat="of" target="section-5.3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-nested-lists">nested lists</xref></t>
              </li>
              <li pn="section-toc.1-1.5.2.4">
                <t pn="section-toc.1-1.5.2.4.1"><xref derivedContent="5.4" format="counter" sectionFormat="of" target="section-5.4"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-list-formats">List Formats</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.6">
            <t pn="section-toc.1-1.6.1"><xref derivedContent="6" format="counter" sectionFormat="of" target="section-6"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-example-of-code-or-mib-modu">Example of Code or MIB Module To Be Extracted</xref></t>
          </li>
          <li pn="section-toc.1-1.7">
            <t pn="section-toc.1-1.7.1"><xref derivedContent="7" format="counter" sectionFormat="of" target="section-7"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-acknowledgements">Acknowledgements</xref></t>
          </li>
          <li pn="section-toc.1-1.8">
            <t pn="section-toc.1-1.8.1"><xref derivedContent="8" format="counter" sectionFormat="of" target="section-8"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-iana-considerations">IANA Considerations</xref></t>
          </li>
          <li pn="section-toc.1-1.9">
            <t pn="section-toc.1-1.9.1"><xref derivedContent="9" format="counter" sectionFormat="of" target="section-9"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-security-considerations">Security Considerations</xref></t>
          </li>
          <li pn="section-toc.1-1.10">
            <t pn="section-toc.1-1.10.1"><xref derivedContent="10" format="counter" sectionFormat="of" target="section-10"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-references">References</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.10.2">
              <li pn="section-toc.1-1.10.2.1">
                <t pn="section-toc.1-1.10.2.1.1"><xref derivedContent="10.1" format="counter" sectionFormat="of" target="section-10.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-normative-references">Normative References</xref></t>
              </li>
              <li pn="section-toc.1-1.10.2.2">
                <t pn="section-toc.1-1.10.2.2.1"><xref derivedContent="10.2" format="counter" sectionFormat="of" target="section-10.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-informative-references">Informative References</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.11">
            <t pn="section-toc.1-1.11.1"><xref derivedContent="Appendix A" format="default" sectionFormat="of" target="section-appendix.a"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-additional-stuff">Additional Stuff</xref></t>
          </li>
          <li pn="section-toc.1-1.12">
            <t pn="section-toc.1-1.12.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.b"/><xref derivedContent="" format="title" sectionFormat="of" target="name-contributors">Contributors</xref></t>
          </li>
          <li pn="section-toc.1-1.13">
            <t pn="section-toc.1-1.13.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.c"/><xref derivedContent="" format="title" sectionFormat="of" target="name-authors-addresses">Authors' Addresses</xref></t>
          </li>
        </ul>
      </section>
    </toc>
  </front>
  <middle>
    <section numbered="true" toc="include" removeInRFC="false" pn="section-1">
      <name slugifiedName="name-introduction">Introduction</name>
      <t pn="section-1-1">The original specification of xml2rfc format is in <xref target="RFC2629" format="default" sectionFormat="of" derivedContent="RFC2629">RFC 2629</xref>.</t>
      <section numbered="true" toc="include" removeInRFC="false" pn="section-1.1">
        <name slugifiedName="name-requirements-language">Requirements Language</name>
        <t pn="section-1.1-1">The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
        "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
        document are to be interpreted as described in <xref target="RFC2119" format="default" sectionFormat="of" derivedContent="RFC2119">RFC 2119</xref>.</t>
      </section>
    </section>
    <section anchor="simple_list" numbered="true" toc="include" removeInRFC="false" pn="section-2">
      <name slugifiedName="name-simple-list">Simple List</name>
      <t pn="section-2-1">List styles: 'empty', 'symbols', 'letters', 'numbers', 'hanging',
      'format'.</t>
      <ul spacing="normal" bare="false" empty="false" pn="section-2-2">
        <li pn="section-2-2.1">First bullet</li>
        <li pn="section-2-2.2">Second bullet</li>
      </ul>
      <t pn="section-2-3"> You can write text here as well.</t>
    </section>
    <section numbered="true" toc="include" removeInRFC="false" pn="section-3">
      <name slugifiedName="name-figures">Figures</name>
      <t pn="section-3-1">Figures should not exceed 69 characters wide to allow for the indent
      of sections.</t>
      <t keepWithNext="true" pn="section-3-2">Preamble text - can be omitted or empty.</t>
      <figure anchor="xml_happy" align="left" suppress-title="false" pn="figure-1">
        <artset pn="section-3-3.1">
          <artwork align="left" name="" type="svg" alt="" pn="section-3-3.1.1" originalSrc="ietf.svg"><svg xmlns="http://www.w3.org/2000/svg" width="175" height="57" viewBox="0 0 175 57">
              <path d="M60,2l12,12l-12,12l-12-12zM88,2l12,12l-12,12l-12-12zM116,2l12,12l-12,12l-12-12zM18,16l12,12l-12,12l-12-12zM46,16l12,12l-12,12l-12-12zM74,16l12,12l-12,12l-12-12zM102,16l12,12l-12,12l-12-12zM130,16l12,12l-12,12l-12-12zM158,16l12,12l-12,12l-12-12zM60,30l12,12l-12,12l-12-12zM88,30l12,12l-12,12l-12-12zM116,30l12,12l-12,12l-12-12z" fill="black"/>
              <path stroke="black" stroke-width="0.5" d="M7,27h26l13,13l14-14l14,14l28-28l14,14l14-14l15,15h26v3h-27l-14-14l-14,14l-14-14l-28,28l-14-14l-14,14l-14-14h-25z" fill="white"/>
              <path d="M3,26h5v5h-5zM168,26h5v5h-5z"/>
            </svg>
          </artwork>
          <artwork align="left" name="" type="ascii-art" alt="" pn="section-3-3.1.2"><![CDATA[
+-----------------------+
| Use XML, be Happy :-) |
|_______________________|
            ]]></artwork>
        </artset>
      </figure>
      <t keepWithPrevious="true" pn="section-3-4">Cross-references allowed in pre- and postamble. <xref target="min_ref" format="default" sectionFormat="of" derivedContent="min_ref"/>.</t>
      <t pn="section-3-5">The CDATA means you don't need to escape meta-characters (especially
      &lt; (&amp;lt;) and &amp; (&amp;amp;)) but is not essential.
      Figures may also have a title attribute but it won't be displayed unless
      there is also an anchor. White space, both horizontal and vertical, is
      significant in figures even if you don't use CDATA.</t>
    </section>
    <!-- This PI places the pagebreak correctly (before the section title) in the text output. -->

    <section numbered="true" toc="include" removeInRFC="false" pn="section-4">
      <name slugifiedName="name-subsections-and-tables">Subsections and Tables</name>
      <section numbered="true" toc="include" removeInRFC="false" pn="section-4.1">
        <name slugifiedName="name-a-subsection">A Subsection</name>
        <t pn="section-4.1-1">By default 3 levels of nesting show in table of contents but that
        can be adjusted with the value of the "tocdepth" processing
        instruction.</t>
      </section>
      <section numbered="true" toc="include" removeInRFC="false" pn="section-4.2">
        <name slugifiedName="name-tables">Tables</name>
        <t pn="section-4.2-1">.. are very similar to figures:</t>
        <t keepWithNext="true" pn="section-4.2-2">Tables use ttcol to define column headers and widths.
          Every cell then has a "c" element for its content.</t>
        <table anchor="table_example" align="center" pn="table-1">
          <name slugifiedName="name-a-very-simple-table">A Very Simple Table</name>
          <thead>
            <tr>
              <th align="center" colspan="1" rowspan="1">ttcol #1</th>
              <th align="center" colspan="1" rowspan="1">ttcol #2</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="center" colspan="1" rowspan="1">c #1</td>
              <td align="center" colspan="1" rowspan="1">c #2</td>
            </tr>
            <tr>
              <td align="center" colspan="1" rowspan="1">c #3</td>
              <td align="center" colspan="1" rowspan="1">c #4</td>
            </tr>
            <tr>
              <td align="center" colspan="1" rowspan="1">c #5</td>
              <td align="center" colspan="1" rowspan="1">c #6</td>
            </tr>
          </tbody>
        </table>
        <t keepWithPrevious="true" pn="section-4.2-4">which is a very simple example.</t>
      </section>
    </section>
    <section anchor="nested_lists" numbered="true" toc="include" removeInRFC="false" pn="section-5">
      <name slugifiedName="name-more-about-lists">More about Lists</name>
      <t pn="section-5-1"><!-- Comment -->Lists with 'hanging labels': the list item is indented the amount of
      the hangIndent: </t>
      <dl newline="true" spacing="normal" indent="8" pn="section-5-2">
        <dt pn="section-5-2.1">short</dt>
        <dd pn="section-5-2.2">With a label shorter than the hangIndent.</dd>
        <dt pn="section-5-2.3">fantastically long label</dt>
        <dd pn="section-5-2.4">With a label longer than the
          hangIndent.</dd>
        <dt pn="section-5-2.5">vspace_trick</dt>
        <dd pn="section-5-2.6">Forces the new
          item to start on a new line.</dd>
      </dl>
      <!-- It would be nice to see the next piece (12 lines) all on one page. -->

      <t pn="section-5-3">Simulating more than one paragraph in a list item using
      &lt;vspace&gt;: </t>
      <ol spacing="normal" type="a" start="1" pn="section-5-4">
        <li pn="section-5-4.1" derivedCounter="a.">First, a short item.</li>
        <li pn="section-5-4.2" derivedCounter="b.">
          <t pn="section-5-4.2.1">Second, a longer list item.</t>
          <t pn="section-5-4.2.2"> And
          something that looks like a separate pararaph..</t>
        </li>
      </ol>
      <t pn="section-5-5">Simple indented paragraph using the "empty" style: </t>
      <ul empty="true" spacing="normal" bare="false" pn="section-5-6">
        <li pn="section-5-6.1">The quick, brown fox jumped over the lazy dog and lived to fool
          many another hunter in the great wood in the west.</li>
      </ul>
      <section numbered="true" toc="include" removeInRFC="false" pn="section-5.1">
        <name slugifiedName="name-numbering-lists-across-list">Numbering Lists across Lists and Sections</name>
        <t pn="section-5.1-1">Numbering items continuously although they are in separate
        &lt;list&gt; elements, maybe in separate sections using the "format"
        style and a "counter" variable.</t>
        <t pn="section-5.1-2">First list: </t>
        <ol group="reqs" spacing="normal" type="R%d" start="1" pn="section-5.1-3">
          <li pn="section-5.1-3.1" derivedCounter="R1">#1</li>
          <li pn="section-5.1-3.2" derivedCounter="R2">#2</li>
          <li pn="section-5.1-3.3" derivedCounter="R3">#3</li>
        </ol>
        <t pn="section-5.1-4"> Specify the indent explicitly so that all the items line up
        nicely.</t>
        <t pn="section-5.1-5">Second list: </t>
        <ol group="reqs" spacing="normal" type="R%d" start="4" pn="section-5.1-6">
          <li pn="section-5.1-6.1" derivedCounter="R4">#4</li>
          <li pn="section-5.1-6.2" derivedCounter="R5">#5</li>
          <li pn="section-5.1-6.3" derivedCounter="R6">#6</li>
        </ol>
      </section>
      <section numbered="true" toc="include" removeInRFC="false" pn="section-5.2">
        <name slugifiedName="name-where-the-list-numbering-co">Where the List Numbering Continues</name>
        <t pn="section-5.2-1">List continues here.</t>
        <t pn="section-5.2-2">Third list: </t>
        <ol group="reqs" spacing="normal" type="R%d" start="7" pn="section-5.2-3">
          <li pn="section-5.2-3.1" derivedCounter="R7">#7</li>
          <li pn="section-5.2-3.2" derivedCounter="R8">#8</li>
          <li pn="section-5.2-3.3" derivedCounter="R9">#9</li>
          <li pn="section-5.2-3.4" derivedCounter="R10">#10</li>
        </ol>
        <t pn="section-5.2-4"> The end of the list.</t>
      </section>
      <section numbered="true" toc="include" removeInRFC="false" pn="section-5.3">
        <name slugifiedName="name-nested-lists">nested lists</name>
        <t pn="section-5.3-1">Simulating more than one paragraph in a list item using
	  &lt;vspace&gt;: 
        </t>
        <ol spacing="normal" type="a" start="1" pn="section-5.3-2">
          <li pn="section-5.3-2.1" derivedCounter="a.">First, a short item.</li>
          <li pn="section-5.3-2.2" derivedCounter="b.">
            <t pn="section-5.3-2.2.1">Second, a longer list item.</t>
            <t pn="section-5.3-2.2.2"> And
	      something that looks like a separate paragraph.</t>
          </li>
          <li pn="section-5.3-2.3" derivedCounter="c.">
            <t pn="section-5.3-2.3.1">and a sublist, also with letters
            </t>
            <ol spacing="normal" type="A" start="1" pn="section-5.3-2.3.2">
              <li pn="section-5.3-2.3.2.1" derivedCounter="A.">first subitem</li>
              <li pn="section-5.3-2.3.2.2" derivedCounter="B.">second subitem</li>
              <li pn="section-5.3-2.3.2.3" derivedCounter="C.">
                <t pn="section-5.3-2.3.2.3.1">and a sub-sublist, also with letters
                </t>
                <ol spacing="normal" type="a" start="1" pn="section-5.3-2.3.2.3.2">
                  <li pn="section-5.3-2.3.2.3.2.1" derivedCounter="a.">first sub-subitem</li>
                  <li pn="section-5.3-2.3.2.3.2.2" derivedCounter="b.">second sub-subitem</li>
                </ol>
              </li>
            </ol>
          </li>
        </ol>
      </section>
      <section numbered="true" toc="include" removeInRFC="false" pn="section-5.4">
        <name slugifiedName="name-list-formats">List Formats</name>
        <t pn="section-5.4-1">many formats
        </t>
        <ol spacing="normal" type="%c" start="1" pn="section-5.4-2">
          <li pn="section-5.4-2.1" derivedCounter="a">first %c-item</li>
          <li pn="section-5.4-2.2" derivedCounter="b">more %c-items</li>
        </ol>
        <ol spacing="normal" type="%C" start="1" pn="section-5.4-3">
          <li pn="section-5.4-3.1" derivedCounter="A">first %C-item</li>
          <li pn="section-5.4-3.2" derivedCounter="B">more %C-items</li>
        </ol>
        <ol spacing="normal" type="%d" start="1" pn="section-5.4-4">
          <li pn="section-5.4-4.1" derivedCounter="1">first %d-item.</li>
          <li pn="section-5.4-4.2" derivedCounter="2">more %d-items.</li>
        </ol>
        <ol spacing="normal" type="%i" start="1" pn="section-5.4-5">
          <li pn="section-5.4-5.1" derivedCounter="i">first %i-item</li>
          <li pn="section-5.4-5.2" derivedCounter="ii">more %i-items</li>
          <li pn="section-5.4-5.3" derivedCounter="iii">more %i-items</li>
          <li pn="section-5.4-5.4" derivedCounter="iv">more %i-items</li>
          <li pn="section-5.4-5.5" derivedCounter="v">more %i-items</li>
          <li pn="section-5.4-5.6" derivedCounter="vi">more %i-items</li>
          <li pn="section-5.4-5.7" derivedCounter="vii">more %i-items</li>
          <li pn="section-5.4-5.8" derivedCounter="viii">more %i-items</li>
          <li pn="section-5.4-5.9" derivedCounter="ix">more %i-items</li>
        </ol>
        <ol spacing="normal" type="%I" start="1" pn="section-5.4-6">
          <li pn="section-5.4-6.1" derivedCounter="I">first %I-item</li>
          <li pn="section-5.4-6.2" derivedCounter="II">more %I-items</li>
          <li pn="section-5.4-6.3" derivedCounter="III">more %I-items</li>
          <li pn="section-5.4-6.4" derivedCounter="IV">more %I-items</li>
          <li pn="section-5.4-6.5" derivedCounter="V">more %I-items</li>
          <li pn="section-5.4-6.6" derivedCounter="VI">more %I-items</li>
          <li pn="section-5.4-6.7" derivedCounter="VII">more %I-items</li>
          <li pn="section-5.4-6.8" derivedCounter="VIII">more %I-items</li>
          <li pn="section-5.4-6.9" derivedCounter="IX">more %I-items</li>
        </ol>
        <ol spacing="normal" type="%o" start="1" pn="section-5.4-7">
          <li pn="section-5.4-7.1" derivedCounter="1">first %o-item</li>
          <li pn="section-5.4-7.2" derivedCounter="2">more %o-items</li>
          <li pn="section-5.4-7.3" derivedCounter="3">more %o-items</li>
          <li pn="section-5.4-7.4" derivedCounter="4">more %o-items</li>
          <li pn="section-5.4-7.5" derivedCounter="5">more %o-items</li>
          <li pn="section-5.4-7.6" derivedCounter="6">more %o-items</li>
          <li pn="section-5.4-7.7" derivedCounter="7">more %o-items</li>
          <li pn="section-5.4-7.8" derivedCounter="10">more %o-items</li>
          <li pn="section-5.4-7.9" derivedCounter="11">more %o-items</li>
        </ol>
        <ol spacing="normal" type="%x" start="1" pn="section-5.4-8">
          <li pn="section-5.4-8.1" derivedCounter="1">first %x-item</li>
          <li pn="section-5.4-8.2" derivedCounter="2">more %x-items</li>
          <li pn="section-5.4-8.3" derivedCounter="3">more %x-items</li>
          <li pn="section-5.4-8.4" derivedCounter="4">more %x-items</li>
          <li pn="section-5.4-8.5" derivedCounter="5">more %x-items</li>
          <li pn="section-5.4-8.6" derivedCounter="6">more %x-items</li>
          <li pn="section-5.4-8.7" derivedCounter="7">more %x-items</li>
          <li pn="section-5.4-8.8" derivedCounter="8">more %x-items</li>
          <li pn="section-5.4-8.9" derivedCounter="9">more %x-items</li>
          <li pn="section-5.4-8.10" derivedCounter="a">more %x-items</li>
          <li pn="section-5.4-8.11" derivedCounter="b">more %x-items</li>
          <li pn="section-5.4-8.12" derivedCounter="c">more %x-items</li>
          <li pn="section-5.4-8.13" derivedCounter="d">more %x-items</li>
          <li pn="section-5.4-8.14" derivedCounter="e">more %x-items</li>
          <li pn="section-5.4-8.15" derivedCounter="f">more %x-items</li>
          <li pn="section-5.4-8.16" derivedCounter="10">more %x-items</li>
          <li pn="section-5.4-8.17" derivedCounter="11">more %x-items</li>
        </ol>
        <ol spacing="normal" type="%X" start="1" pn="section-5.4-9">
          <li pn="section-5.4-9.1" derivedCounter="1">first %X-item</li>
          <li pn="section-5.4-9.2" derivedCounter="2">more %X-items</li>
          <li pn="section-5.4-9.3" derivedCounter="3">more %X-items</li>
          <li pn="section-5.4-9.4" derivedCounter="4">more %X-items</li>
          <li pn="section-5.4-9.5" derivedCounter="5">more %X-items</li>
          <li pn="section-5.4-9.6" derivedCounter="6">more %X-items</li>
          <li pn="section-5.4-9.7" derivedCounter="7">more %X-items</li>
          <li pn="section-5.4-9.8" derivedCounter="8">more %X-items</li>
          <li pn="section-5.4-9.9" derivedCounter="9">more %X-items</li>
          <li pn="section-5.4-9.10" derivedCounter="A">more %X-items</li>
          <li pn="section-5.4-9.11" derivedCounter="B">more %X-items</li>
          <li pn="section-5.4-9.12" derivedCounter="C">more %X-items</li>
          <li pn="section-5.4-9.13" derivedCounter="D">more %X-items</li>
          <li pn="section-5.4-9.14" derivedCounter="E">more %X-items</li>
          <li pn="section-5.4-9.15" derivedCounter="F">more %X-items</li>
          <li pn="section-5.4-9.16" derivedCounter="10">more %X-items</li>
          <li pn="section-5.4-9.17" derivedCounter="11">more %X-items</li>
        </ol>
      </section>
    </section>
    <section anchor="codeExample" numbered="true" toc="include" removeInRFC="false" pn="section-6">
      <name slugifiedName="name-example-of-code-or-mib-modu">Example of Code or MIB Module To Be Extracted</name>
      <t keepWithNext="true" pn="section-6-1">The &lt;artwork&gt; element has a number of extra attributes
        that can be used to substitute a more aesthetically pleasing rendition
        into HTML output while continuing to use the ASCII art version in the
        text and nroff outputs (see the xml2rfc README for details). It also
        has a "type" attribute. This is currently ignored except in the case
        'type="abnf"'. In this case the "artwork" is expected to contain a
        piece of valid Augmented Backus-Naur Format (ABNF) grammar. This will
        be syntax checked by xml2rfc and any errors will cause a fatal error
        if the "strict" processing instruction is set to "yes". The ABNF will
        also be colorized in HTML output to highlight the syntactic
        components. Checking of additional "types" may be provided in future
        versions of xml2rfc.</t>
      <sourcecode name="example.c" type="" markers="true" pn="section-6-2">

/**** an example C program */

#include &lt;stdio.h&gt;

void
main(int argc, char *argv[])
{
    int i;

    printf("program arguments are:\n");
    for (i = 0; i &lt; argc; i++) {
        printf("%d: \"%s\"\n", i, argv[i]);
    }

    exit(0);
} /* main */

/* end of file */

</sourcecode>
    </section>
    <section anchor="Acknowledgements" numbered="true" toc="include" removeInRFC="false" pn="section-7">
      <name slugifiedName="name-acknowledgements">Acknowledgements</name>
      <t pn="section-7-1">This template was derived from an initial version written by Pekka
      Savola and contributed by him to the xml2rfc project.</t>
      <t pn="section-7-2">
	This document is part of a plan to make xml2rfc indispensable <xref target="DOMINATION" format="default" sectionFormat="of" derivedContent="DOMINATION"/>.
	This document may be shared as needed <xref target="SHARING" format="default" sectionFormat="of" derivedContent="SHARING"/>.  If necessary, appeal to <xref target="JUPITER" format="default" sectionFormat="of" derivedContent="JUPITER"/>.
      </t>
    </section>
    <!-- Possibly a 'Contributors' section ... -->

    <section anchor="IANA" numbered="true" toc="include" removeInRFC="false" pn="section-8">
      <name slugifiedName="name-iana-considerations">IANA Considerations</name>
      <t pn="section-8-1">This memo includes no request to IANA.</t>
      <t pn="section-8-2">All drafts are required to have an IANA considerations section (see
      <xref target="I-D.narten-iana-considerations-rfc2434bis" format="default" sectionFormat="of" derivedContent="I-D.narten-iana-considerations-rfc2434bis">the update of
      RFC 2434</xref> for a guide). If the draft does not require IANA to do
      anything, the section contains an explicit statement that this is the
      case (as above). If there are no requirements for IANA, the section will
      be removed during conversion into an RFC by the RFC Editor.</t>
    </section>
    <section anchor="Security" numbered="true" toc="include" removeInRFC="false" pn="section-9">
      <name slugifiedName="name-security-considerations">Security Considerations</name>
      <t pn="section-9-1">All drafts are required to have a security considerations section.
      See <xref target="RFC3552" format="default" sectionFormat="of" derivedContent="RFC3552">RFC 3552</xref> for a guide.</t>
    </section>
  </middle>
  <!--  *****BACK MATTER ***** -->

  <back>
    <!-- References split into informative and normative -->

    <!-- There are 2 ways to insert reference entries from the citation libraries:
     1. define an ENTITY at the top, and use "ampersand character"RFC2629; here (as shown)
     2. simply use a PI "less than character"?rfc include="reference.RFC.2119.xml"?> here
        (for I-Ds: include="reference.I-D.narten-iana-considerations-rfc2434bis.xml")

     Both are cited textually in the same manner: by using xref elements.
     If you use the PI option, xml2rfc will, by default, try to find included files in the same
     directory as the including file. You can also define the XML_LIBRARY environment variable
     with a value containing a set of directories to search.  These can be either in the local
     filing system or remote ones accessed by http (http://domain/dir/... ).-->

    <references pn="section-10">
      <name slugifiedName="name-references">References</name>
      <references pn="section-10.1">
        <name slugifiedName="name-normative-references">Normative References</name>
        <!--?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml"?-->
        <reference anchor="min_ref" quoteTitle="true" derivedAnchor="min_ref">
          <!-- the following is the minimum to make xml2rfc happy -->

        <front>
            <title>Minimal Reference</title>
            <author initials="authInitials" surname="authSurName">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2006"/>
          </front>
        </reference>
        <reference anchor="RFC2119" target="https://www.rfc-editor.org/info/rfc2119" xml:base="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml" quoteTitle="true" derivedAnchor="RFC2119">
          <front>
            <title>Key words for use in RFCs to Indicate Requirement Levels</title>
            <seriesInfo name="BCP" value="14"/>
            <seriesInfo name="RFC" value="2119"/>
            <seriesInfo name="DOI" value="10.17487/RFC2119"/>
            <author initials="S." surname="Bradner" fullname="S. Bradner">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="1997" month="March"/>
            <abstract>
              <t>In many standards track documents several words are used to signify the requirements in the specification.  These words are often capitalized. This document defines these words as they should be interpreted in IETF documents.  This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
            </abstract>
          </front>
        </reference>
      </references>
      <references pn="section-10.2">
        <name slugifiedName="name-informative-references">Informative References</name>
        <!-- Here we use entities that we defined at the beginning. -->

      <!-- Reference with query argument -->
      <!-- A reference written by by an organization not a person. -->
        <reference anchor="DOMINATION" target="http://www.example.com/dominator.html" quoteTitle="true" derivedAnchor="DOMINATION">
          <front>
            <title>Ultimate Plan for Taking Over the World</title>
            <author>
              <organization showOnFrontPage="true">Mad Dominators, Inc.</organization>
            </author>
            <date year="1984"/>
          </front>
        </reference>
        <reference anchor="I-D.narten-iana-considerations-rfc2434bis" xml:base="http://xml.resource.org/public/rfc/bibxml3/reference.I-D.narten-iana-considerations-rfc2434bis.xml" target="http://www.ietf.org/internet-drafts/draft-narten-iana-considerations-rfc2434bis-09.txt" quoteTitle="true" derivedAnchor="I-D.narten-iana-considerations-rfc2434bis">
          <front>
            <title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
            <seriesInfo name="Internet-Draft" value="draft-narten-iana-considerations-rfc2434bis-09"/>
            <author initials="T" surname="Narten" fullname="Thomas  Narten">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="H" surname="Alvestrand" fullname="Harald Alvestrand">
              <organization showOnFrontPage="true"/>
            </author>
            <date month="March" day="26" year="2008"/>
            <abstract>
              <t>Many protocols make use of identifiers consisting of constants and other well-known values. Even after a protocol has been defined and deployment has begun, new values may need to be assigned (e.g., for a new option type in DHCP, or a new encryption or authentication transform for IPsec).  To ensure that such quantities have consistent values and interpretations across all implementations, their assignment must be administered by a central authority. For IETF protocols, that role is provided by the Internet Assigned Numbers Authority (IANA).  In order for IANA to manage a given name space prudently, it needs guidelines describing the conditions under which new values can be assigned, or when modifications to existing values can be made. If IANA is expected to play a role in the management of a name space, the IANA must be given clear and concise instructions describing that role.  This document discusses issues that should be considered in formulating a policy for assigning values to a name space and provides guidelines to document authors on the specific text that must be included in documents that place demands on IANA.  This document obsoletes RFC 2434. Contents  Status of this Memo.......................................... 1</t>
            </abstract>
          </front>
          <refcontent>Work in Progress</refcontent>
        </reference>
        <reference anchor="JUPITER" xml:base="https://xml2rfc.tools.ietf.org/public/rfc/bibxml-doi/reference.DOI.10.1145/2975159.xml?anchor=JUPITER" quoteTitle="true" target="https://doi.org/10.1145/2975159" derivedAnchor="JUPITER">
          <front>
            <title>Jupiter rising</title>
            <seriesInfo name="DOI" value="10.1145/2975159"/>
            <seriesInfo name="Communications of the ACM" value="Vol. 59, pp. 88-97"/>
            <author initials="A." surname="Singh" fullname="Arjun Singh">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="P." surname="Germano" fullname="Paulie Germano">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="A." surname="Kanagala" fullname="Anand Kanagala">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="H." surname="Liu" fullname="Hong Liu">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="J." surname="Provost" fullname="Jeff Provost">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="J." surname="Simmons" fullname="Jason Simmons">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="E." surname="Tanda" fullname="Eiichi Tanda">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="J." surname="Wanderer" fullname="Jim Wanderer">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="U." surname="HÃ¶lzle" fullname="Urs HÃ¶lzle">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="S." surname="Stuart" fullname="Stephen Stuart">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="A." surname="Vahdat" fullname="Amin Vahdat">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="J." surname="Ong" fullname="Joon Ong">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="A." surname="Agarwal" fullname="Amit Agarwal">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="G." surname="Anderson" fullname="Glen Anderson">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="A." surname="Armistead" fullname="Ashby Armistead">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="R." surname="Bannon" fullname="Roy Bannon">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="S." surname="Boving" fullname="Seb Boving">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="G." surname="Desai" fullname="Gaurav Desai">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="B." surname="Felderman" fullname="Bob Felderman">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2016" month="August"/>
          </front>
        </reference>
        <reference anchor="RFC2629" target="https://www.rfc-editor.org/info/rfc2629" xml:base="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2629.xml" quoteTitle="true" derivedAnchor="RFC2629">
          <front>
            <title>Writing I-Ds and RFCs using XML</title>
            <seriesInfo name="RFC" value="2629"/>
            <seriesInfo name="DOI" value="10.17487/RFC2629"/>
            <author initials="M." surname="Rose" fullname="M. Rose">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="1999" month="June"/>
            <abstract>
              <t>This memo presents a technique for using XML (Extensible Markup Language) as a source format for documents in the Internet-Drafts (I-Ds) and Request for Comments (RFC) series.  This memo provides information for the Internet community.</t>
            </abstract>
          </front>
        </reference>
        <reference anchor="RFC3552" target="https://www.rfc-editor.org/info/rfc3552" xml:base="http://xml.resource.org/public/rfc/bibxml/reference.RFC.3552.xml" quoteTitle="true" derivedAnchor="RFC3552">
          <front>
            <title>Guidelines for Writing RFC Text on Security Considerations</title>
            <seriesInfo name="BCP" value="72"/>
            <seriesInfo name="RFC" value="3552"/>
            <seriesInfo name="DOI" value="10.17487/RFC3552"/>
            <author initials="E." surname="Rescorla" fullname="E. Rescorla">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="B." surname="Korver" fullname="B. Korver">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2003" month="July"/>
            <abstract>
              <t>All RFCs are required to have a Security Considerations section. Historically, such sections have been relatively weak.  This document provides guidelines to RFC authors on how to write a good Security Considerations section.   This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
            </abstract>
          </front>
        </reference>
        <reference anchor="SHARING" target="http://www.example.com/sharing.html" quoteTitle="true" derivedAnchor="SHARING">
          <front>
            <title>I Learned to Share in Kindergarten</title>
            <author>
              <organization showOnFrontPage="true">Sesame Street</organization>
            </author>
            <date year="1972"/>
          </front>
        </reference>
      </references>
    </references>
    <section anchor="app-additional" numbered="true" toc="include" removeInRFC="false" pn="section-appendix.a">
      <name slugifiedName="name-additional-stuff">Additional Stuff</name>
      <t pn="section-appendix.a-1">This becomes an Appendix.</t>
    </section>
    <section anchor="contributors" numbered="false" toc="include" removeInRFC="false" pn="section-appendix.b">
      <name slugifiedName="name-contributors">Contributors</name>
      <t pn="section-appendix.b-1">This becomes an unnumbered section</t>
    </section>
    <!-- Change Log

v00 2006-03-15  EBD   Initial version

v01 2006-04-03  EBD   Moved PI location back to position 1 -
                      v3.1 of XMLmind is better with them at this location.
v02 2007-03-07  AH    removed extraneous nested_list attribute,
                      other minor corrections
v03 2007-03-09  EBD   Added comments on null IANA sections and fixed heading capitalization.
                      Modified comments around figure to reflect non-implementation of
                      figure indent control.  Put in reference using anchor="DOMINATION".
                      Fixed up the date specification comments to reflect current truth.
v04 2007-03-09 AH     Major changes: shortened discussion of PIs,
                      added discussion of rfc include.
v05 2007-03-10 EBD    Added preamble to C program example to tell about ABNF and alternative 
                      images. Removed meta-characters from comments (causes problems).  -->
  <section anchor="authors-addresses" numbered="false" removeInRFC="false" toc="include" pn="section-appendix.c">
      <name slugifiedName="name-authors-addresses">Authors' Addresses</name>
      <author fullname="Elwyn Davies" initials="E.B." role="editor" surname="Davies">
        <organization showOnFrontPage="true">Folly Consulting</organization>
        <address>
          <postal>
            <street/>
            <!-- Reorder these if your country does things differently -->

          <city>Soham</city>
            <region/>
            <code/>
            <country>UK</country>
          </postal>
          <phone>+44 7889 488 335</phone>
          <email>elwynd@dial.pipex.com</email>
          <!-- uri and facsimile elements may also be added -->
      </address>
      </author>
      <author fullname="Quintin Zhao" initials="Q." surname="Zhao">
        <organization showOnFrontPage="true">Huawei Technology</organization>
        <address>
          <postal>
            <street>125 Nagog Technology Park</street>
            <city>Acton</city>
            <region>MA</region>
            <code>01719</code>
            <country>US</country>
          </postal>
          <email>quintin.zhao@huawei.com</email>
        </address>
      </author>
    </section>
  </back>
</rfc>
