<?xml version='1.0' encoding='ascii'?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<!-- This template is for creating an Internet Draft using xml2rfc,
     which is available here: http://xml.resource.org. -->
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<!-- used by XSLT processors -->
<!-- For a complete list and description of processing instructions (PIs), 
     please see http://xml.resource.org/authoring/README.html. -->
<!-- Below are generally applicable Processing Instructions (PIs) that most I-Ds might want to use.
     (Here they are set differently than their defaults in xml2rfc v1.32) -->
<?rfc strict="yes" ?>
<!-- give errors regarding ID-nits and DTD validation -->
<!-- control the table of contents (ToC) -->
<?rfc toc="yes"?>
<!-- generate a ToC -->
<?rfc tocdepth="4"?>
<!-- the number of levels of subsections in ToC. default: 3 -->
<!-- control references -->
<?rfc symrefs="yes"?>
<!-- use symbolic references tags, i.e, [RFC2119] instead of [1] -->
<?rfc sortrefs="yes" ?>
<!-- sort the reference entries alphabetically -->
<!-- control vertical white space 
     (using these PIs as follows is recommended by the RFC Editor) -->
<?rfc compact="yes" ?>
<!-- do not start each main section on a new page -->
<?rfc subcompact="no" ?>
<!-- keep one blank line between list items -->
<!-- end of list of popular I-D processing instructions -->
<rfc category="info" docName="draft-ietf-xml2rfc-template-05" ipr="trust200902" obsoletes="" updates="" submissionType="IETF" xml:lang="en">
  <!--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>
    <!--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>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" surname="Quintin Zhao">
      <organization>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="March" year="2007"/>
    <!--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>
      <t>Insert an abstract: MANDATORY. This template is for creating an Internet Draft.</t>
    </abstract>
  </front>
  <middle>
    <section title="Introduction" numbered="true" toc="default">
      <t>The original specification of xml2rfc format is in <xref target="RFC2629" pageno="false" format="default">RFC&#160;2629</xref>.</t>
      <section title="Requirements Language" numbered="true" toc="default">
        <t>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" pageno="false" format="default">RFC 2119</xref>.</t>
      </section>
    </section>
    <section anchor="simple_list" title="Simple List" numbered="true" toc="default">
      <t>List styles: 'empty', 'symbols', 'letters', 'numbers', 'hanging', 'format'.</t>
      <t><list style="symbols"><t>First bullet</t><t>Second bullet</t></list> You can write text here as well.</t>
    </section>
    <section title="Figures" numbered="true" toc="default">
      <t>Figures should not exceed 69 characters wide to allow for the indent of sections.</t>
      <figure align="center" anchor="xml_happy" title="" suppress-title="false" alt="" width="" height="">
        <preamble>Preamble text - can be omitted or empty.</preamble>
        <artwork align="left" xml:space="preserve" name="" type="" alt="" width="" height="">
+-----------------------+
| Use XML, be Happy :-) |
|_______________________|
            </artwork>
        <postamble>Cross-references allowed in pre- and postamble. <xref target="min_ref" pageno="false" format="default"/>.</postamble>
      </figure>
      <t>The CDATA means you don't need to escape meta-characters (especially &lt;&#160;(&amp;lt;) and &amp;&#160;(&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. -->
    <?rfc needLines="8" ?>
    <section title="Subsections and Tables" numbered="true" toc="default">
      <section title="A Subsection" numbered="true" toc="default">
        <t>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 title="Tables" numbered="true" toc="default">
        <t>.. are very similar to figures:</t>
        <texttable anchor="table_example" title="A Very Simple Table" suppress-title="false" align="center" style="full">
          <preamble>Tables use ttcol to define column headers and widths.  Every cell then has a "c" element for its content.</preamble>
          <ttcol align="center">ttcol #1</ttcol>
          <ttcol align="center">ttcol #2</ttcol>
          <c>c #1</c>
          <c>c #2</c>
          <c>c #3</c>
          <c>c #4</c>
          <c>c #5</c>
          <c>c #6</c>
          <postamble>which is a very simple example.</postamble>
        </texttable>
      </section>
    </section>
    <section anchor="nested_lists" title="More about Lists" numbered="true" toc="default">
      <t>Lists with 'hanging labels': the list item is indented the amount of the hangIndent: <list hangIndent="8" style="hanging"><t hangText="short">With a label shorter than the hangIndent.</t><t hangText="fantastically long label">With a label longer than the hangIndent.</t><t hangText="vspace_trick"><vspace blankLines="0"/>Forces the new item to start on a new line.</t></list></t>
      <!--It would be nice to see the next piece (12 lines) all on one page. -->
      <?rfc needLines="12" ?>
      <t>Simulating more than one paragraph in a list item using &lt;vspace&gt;: <list style="letters"><t>First, a short item.</t><t>Second, a longer list item.<vspace blankLines="1"/> And something that looks like a separate pararaph..</t></list></t>
      <t>Simple indented paragraph using the "empty" style: <list hangIndent="10" style="empty"><t>The quick, brown fox jumped over the lazy dog and lived to fool many another hunter in the great wood in the west.</t></list></t>
      <section title="Numbering Lists across Lists and Sections" numbered="true" toc="default">
        <t>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>First list: <list counter="reqs" hangIndent="4" style="format R%d"><t>#1</t><t>#2</t><t>#3</t></list> Specify the indent explicitly so that all the items line up nicely.</t>
        <t>Second list: <list counter="reqs" hangIndent="4" style="format R%d"><t>#4</t><t>#5</t><t>#6</t></list></t>
      </section>
      <section title="Where the List Numbering Continues" numbered="true" toc="default">
        <t>List continues here.</t>
        <t>Third list: <list counter="reqs" hangIndent="4" style="format R%d"><t>#7</t><t>#8</t><t>#9</t><t>#10</t></list> The end of the list.</t>
      </section>
      <section title="nested lists" numbered="true" toc="default">
        <t>Simulating more than one paragraph in a list item using &lt;vspace&gt;: <list style="letters"><t>First, a short item.</t><t>Second, a longer list item.<vspace blankLines="1"/> And something that looks like a separate paragraph.</t><t>and a sublist, also with letters <list><t>first subitem</t><t>second subitem</t><t>and a sub-sublist, also with letters <list><t>first sub-subitem</t><t>second sub-subitem</t></list> </t></list> </t></list> </t>
      </section>
      <section title="List Formats" numbered="true" toc="default">
        <t>many formats <list style="format %c"><t>first %c-item</t><t>more %c-items</t></list> <list style="format %C"><t>first %C-item</t><t>more %C-items</t></list> <list style="format %d"><t>first %d-item.</t><t>more %d-items.</t></list> <list style="format %i"><t>first %i-item</t><t>more %i-items</t><t>more %i-items</t><t>more %i-items</t><t>more %i-items</t><t>more %i-items</t><t>more %i-items</t><t>more %i-items</t><t>more %i-items</t></list> <list style="format %I"><t>first %I-item</t><t>more %I-items</t><t>more %I-items</t><t>more %I-items</t><t>more %I-items</t><t>more %I-items</t><t>more %I-items</t><t>more %I-items</t><t>more %I-items</t></list> <list style="format %o"><t>first %o-item</t><t>more %o-items</t><t>more %o-items</t><t>more %o-items</t><t>more %o-items</t><t>more %o-items</t><t>more %o-items</t><t>more %o-items</t><t>more %o-items</t></list> <list style="format %x"><t>first %x-item</t><t>more %x-items</t><t>more %x-items</t><t>more %x-items</t><t>more %x-items</t><t>more %x-items</t><t>more %x-items</t><t>more %x-items</t><t>more %x-items</t><t>more %x-items</t><t>more %x-items</t><t>more %x-items</t><t>more %x-items</t><t>more %x-items</t><t>more %x-items</t><t>more %x-items</t><t>more %x-items</t></list> <list style="format %X"><t>first %X-item</t><t>more %X-items</t><t>more %X-items</t><t>more %X-items</t><t>more %X-items</t><t>more %X-items</t><t>more %X-items</t><t>more %X-items</t><t>more %X-items</t><t>more %X-items</t><t>more %X-items</t><t>more %X-items</t><t>more %X-items</t><t>more %X-items</t><t>more %X-items</t><t>more %X-items</t><t>more %X-items</t></list> </t>
      </section>
    </section>
    <section anchor="codeExample" title="Example of Code or MIB Module To Be Extracted" numbered="true" toc="default">
      <figure title="" suppress-title="false" align="left" alt="" width="" height="">
        <preamble>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.</preamble>
        <artwork xml:space="preserve" name="" type="" align="left" alt="" width="" height="">

&lt;CODE BEGINS&gt; file "example.c"

/**** 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 */

&lt;CODE ENDS&gt;
            </artwork>
      </figure>
    </section>
    <section anchor="Acknowledgements" title="Acknowledgements" numbered="true" toc="default">
      <t>This template was derived from an initial version written by Pekka Savola and contributed by him to the xml2rfc project.</t>
      <t>This document is part of a plan to make xml2rfc indispensable <xref target="DOMINATION" pageno="false" format="default"/>.  This document may be shared as needed <xref target="SHARING" pageno="false" format="default"/>.  </t>
    </section>
    <!--Possibly a 'Contributors' section ... -->
    <section anchor="IANA" title="IANA Considerations" numbered="true" toc="default">
      <t>This memo includes no request to IANA.</t>
      <t>All drafts are required to have an IANA considerations section (see <xref target="I-D.narten-iana-considerations-rfc2434bis" pageno="false" format="default">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" title="Security Considerations" numbered="true" toc="default">
      <t>All drafts are required to have a security considerations section.  See <xref target="RFC3552" pageno="false" format="default">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 title="Normative References"><!--?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml"?--><reference anchor="RFC2119" target="https://www.rfc-editor.org/info/rfc2119" quote-title="true"><front><title>Key words for use in RFCs to Indicate Requirement Levels</title><author initials="S." surname="Bradner" fullname="S. Bradner"><organization/></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><seriesInfo name="BCP" value="14"/><seriesInfo name="RFC" value="2119"/><seriesInfo name="DOI" value="10.17487/RFC2119"/></reference> <reference anchor="min_ref" quote-title="true"><!--the following is the minimum to make xml2rfc happy --><front><title>Minimal Reference</title><author initials="authInitials" surname="authSurName"><organization/></author><date year="2006"/></front></reference></references>
    <references title="Informative References"><!--Here we use entities that we defined at the beginning. --><reference anchor="RFC2629"><front><title>Writing I-Ds and RFCs using XML</title><author initials="M.T." surname="Rose" fullname="Marshall T. Rose"><organization>Invisible Worlds, Inc.</organization><address><postal><street>660 York Street</street><city>San Francisco</city><region>CA</region><code>94110</code><country>US</country></postal><phone>+1 415 695 3975</phone><email>mrose@not.invisible.net</email><uri>http://invisible.net/</uri></address></author><date year="1999" month="June"/><area>General</area><keyword>RFC</keyword><keyword>Request for Comments</keyword><keyword>I-D</keyword><keyword>Internet-Draft</keyword><keyword>XML</keyword><keyword>Extensible Markup Language</keyword><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.</t></abstract></front><seriesInfo name="RFC" value="2629"/><format type="TXT" octets="48677" target="http://www.rfc-editor.org/rfc/rfc2629.txt"/><format type="HTML" octets="72426" target="http://xml.resource.org/public/rfc/html/rfc2629.html"/><format type="XML" octets="53481" target="http://xml.resource.org/public/rfc/xml/rfc2629.xml"/></reference><reference anchor="RFC3552" quote-title="true"><front><title>Guidelines for Writing RFC Text on Security Considerations</title><author initials="E." surname="Rescorla" fullname="E. Rescorla"><organization/></author><author initials="B." surname="Korver" fullname="B. Korver"><organization/></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><seriesInfo name="BCP" value="72"/><seriesInfo name="RFC" value="3552"/><format type="TXT" octets="110393" target="http://www.rfc-editor.org/rfc/rfc3552.txt"/></reference> <reference anchor="I-D.narten-iana-considerations-rfc2434bis" quote-title="true"><front><title>Guidelines for Writing an IANA Considerations Section in RFCs</title><author initials="T" surname="Narten" fullname="Thomas  Narten"><organization/></author><author initials="H" surname="Alvestrand" fullname="Harald Alvestrand"><organization/></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><seriesInfo name="Internet-Draft" value="draft-narten-iana-considerations-rfc2434bis-09"/><format type="TXT" target="http://www.ietf.org/internet-drafts/draft-narten-iana-considerations-rfc2434bis-09.txt"/></reference> <!--A reference written by by an organization not a person. --><reference anchor="DOMINATION" target="http://www.example.com/dominator.html" quote-title="true"><front><title>Ultimate Plan for Taking Over the World</title><author><organization>Mad Dominators, Inc.</organization></author><date year="1984"/></front></reference><reference anchor="SHARING" target="http://www.example.com/sharing.html" quote-title="true"><front><title>I Learned to Share in Kindergarten </title><author><organization>Sesame Street </organization></author><date year="1972"/></front></reference></references>
    <section anchor="app-additional" title="Additional Stuff" numbered="true" toc="default">
      <t>This becomes an Appendix.</t>
    </section>
    <section anchor="contributors" title="Contributors" numbered="no" toc="default">
      <t>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).  -->
  </back>
</rfc>
