<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>
<?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 -->
<!-- permit multiple author initials -->
<?rfc multiple-initials="yes" ?>
<!-- end of list of popular I-D processing instructions -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" category="info" docName="draft-ietf-xml2rfc-template-05" ipr="trust200902" obsoletes="" updates="" submissionType="IETF" xml:lang="en" tocInclude="true" tocDepth="4" symRefs="true" sortRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.18.1 -->
  <?v3xml2rfc silence=".*[Pp]ostal address" ?>
  <?v3xml2rfc silence="The document date .*? is more than 3 days away from today's date" ?>
  <?v3xml2rfc silence="Found SVG with width or height specified" ?>
  <!-- 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"/>
    <!-- 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" initials="Q." surname="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="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>
      <t>Insert an abstract: MANDATORY. This template is for creating an
      Internet Draft.</t>
    </abstract>
  </front>
  <middle>
    <section numbered="true" toc="default">
      <name>Introduction</name>
      <t>The original specification of xml2rfc format is in <xref target="RFC2629" format="default">RFC 2629</xref>.</t>
      <section numbered="true" toc="default">
        <name>Requirements Language</name>
        <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" format="default">RFC 2119</xref>.</t>
      </section>
    </section>
    <section anchor="simple_list" numbered="true" toc="default">
      <name>Simple List</name>
      <t>List styles: 'empty', 'symbols', 'letters', 'numbers', 'hanging',
      'format'.</t>
      <ul spacing="normal">
        <li>
          <t>First bullet</t>
        </li>
        <li>
          <t>Second bullet</t>
        </li>
      </ul>
      <t> You can write text here as well.</t>
    </section>
    <section numbered="true" toc="default">
      <name>Figures</name>
      <t>Figures should not exceed 69 characters wide to allow for the indent
      of sections.</t>
      <t keepWithNext="true">Preamble text - can be omitted or empty.</t>
      <figure anchor="xml_happy">
        <artset>
          <artwork align="left" src="ietf.svg" name="" type="svg" alt=""/>
          <artwork align="left" name="" type="ascii-art" alt=""><![CDATA[
+-----------------------+
| Use XML, be Happy :-) |
|_______________________|
            ]]></artwork>
        </artset>
      </figure>
      <t keepWithPrevious="true">Cross-references allowed in pre- and postamble. <xref target="min_ref" format="default"/>.</t>
      <t>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
      <em>significant</em> 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="default">
      <name>Subsections and Tables</name>
      <section numbered="true" toc="default">
        <name>A Subsection</name>
        <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 numbered="true" toc="default">
        <name>Tables</name>
        <t>.. are very similar to figures:</t>
        <t keepWithNext="true">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">
          <name>A Very Simple Table</name>
          <thead>
            <tr>
              <th align="center">ttcol #1</th>
              <th align="center">ttcol #2</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="center">c #1</td>
              <td align="center">c #2</td>
            </tr>
            <tr>
              <td align="center">c #3</td>
              <td align="center">c #4</td>
            </tr>
            <tr>
              <td align="center">c #5</td>
              <td align="center">c #6</td>
            </tr>
          </tbody>
        </table>
        <t keepWithPrevious="true">which is a very simple example.</t>
      </section>
    </section>
    <section anchor="nested_lists" numbered="true" toc="default">
      <name>More about Lists</name>
      <t><!-- Comment -->Lists with 'hanging labels': the list item is indented the amount of
      the hangIndent: </t>
      <dl newline="true" spacing="normal" indent="8">
        <dt>short</dt>
        <dd>With a label shorter than the hangIndent.</dd>
        <dt>fantastically long label</dt>
        <dd>With a label longer than the
          hangIndent.</dd>
        <dt>vspace_trick</dt>
        <dd>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>Simulating more than one paragraph in a list item using
      &lt;vspace&gt;: </t>
      <ol spacing="normal" type="a"><li>
          <t>First, a short item.</t>
        </li>
        <li>
          <t>Second, a longer list item.</t>
          <t> And
          something that looks like a separate pararaph..</t>
        </li>
      </ol>
      <t>Simple indented paragraph using the "empty" style: </t>
      <ul empty="true" spacing="normal">
        <li>
          <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>
        </li>
      </ul>
      <section numbered="true" toc="default">
        <name>Numbering Lists across Lists and Sections</name>
        <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: </t>
        <ol group="reqs" spacing="normal" type="R%d"><li>
            <t>#1</t>
          </li>
          <li>
            <t>#2</t>
          </li>
          <li>
            <t>#3</t>
          </li>
        </ol>
        <t> Specify the indent explicitly so that all the items line up
        nicely.</t>
        <t>Second list: </t>
        <ol group="reqs" spacing="normal" type="R%d"><li>
            <t>#4</t>
          </li>
          <li>
            <t>#5</t>
          </li>
          <li>
            <t>#6</t>
          </li>
        </ol>
      </section>
      <section numbered="true" toc="default">
        <name>Where the List Numbering Continues</name>
        <t>List continues here.</t>
        <t>Third list: </t>
        <ol group="reqs" spacing="normal" type="R%d"><li>
            <t>#7</t>
          </li>
          <li>
            <t>#8</t>
          </li>
          <li>
            <t>#9</t>
          </li>
          <li>
            <t>#10</t>
          </li>
        </ol>
        <t> The end of the list.</t>
      </section>
      <section numbered="true" toc="default">
        <name>nested lists</name>
        <t>Simulating more than one paragraph in a list item using
	  &lt;vspace&gt;: 
        </t>
        <ol spacing="normal" type="a"><li>
            <t>First, a short item.</t>
          </li>
          <li>
            <t>Second, a longer list item.</t>
            <t> And
	      something that looks like a separate paragraph.</t>
          </li>
          <li>
            <t>and a sublist, also with letters
            </t>
            <ol spacing="normal" type="A"><li>
                <t>first subitem</t>
              </li>
              <li>
                <t>second subitem</t>
              </li>
              <li>
                <t>and a sub-sublist, also with letters
                </t>
                <ol spacing="normal" type="a"><li>
                    <t>first sub-subitem</t>
                  </li>
                  <li>
                    <t>second sub-subitem</t>
                  </li>
                </ol>
              </li>
            </ol>
          </li>
        </ol>
      </section>
      <section numbered="true" toc="default">
        <name>List Formats</name>
        <t>many formats
        </t>
        <ol spacing="normal" type="%c"><li>
            <t>first %c-item</t>
          </li>
          <li>
            <t>more %c-items</t>
          </li>
        </ol>
        <ol spacing="normal" type="%C"><li>
            <t>first %C-item</t>
          </li>
          <li>
            <t>more %C-items</t>
          </li>
        </ol>
        <ol spacing="normal" type="%d"><li>
            <t>first %d-item.</t>
          </li>
          <li>
            <t>more %d-items.</t>
          </li>
        </ol>
        <ol spacing="normal" type="%i"><li>
            <t>first %i-item</t>
          </li>
          <li>
            <t>more %i-items</t>
          </li>
          <li>
            <t>more %i-items</t>
          </li>
          <li>
            <t>more %i-items</t>
          </li>
          <li>
            <t>more %i-items</t>
          </li>
          <li>
            <t>more %i-items</t>
          </li>
          <li>
            <t>more %i-items</t>
          </li>
          <li>
            <t>more %i-items</t>
          </li>
          <li>
            <t>more %i-items</t>
          </li>
        </ol>
        <ol spacing="normal" type="%I"><li>
            <t>first %I-item</t>
          </li>
          <li>
            <t>more %I-items</t>
          </li>
          <li>
            <t>more %I-items</t>
          </li>
          <li>
            <t>more %I-items</t>
          </li>
          <li>
            <t>more %I-items</t>
          </li>
          <li>
            <t>more %I-items</t>
          </li>
          <li>
            <t>more %I-items</t>
          </li>
          <li>
            <t>more %I-items</t>
          </li>
          <li>
            <t>more %I-items</t>
          </li>
        </ol>
        <ol spacing="normal" type="%o"><li>
            <t>first %o-item</t>
          </li>
          <li>
            <t>more %o-items</t>
          </li>
          <li>
            <t>more %o-items</t>
          </li>
          <li>
            <t>more %o-items</t>
          </li>
          <li>
            <t>more %o-items</t>
          </li>
          <li>
            <t>more %o-items</t>
          </li>
          <li>
            <t>more %o-items</t>
          </li>
          <li>
            <t>more %o-items</t>
          </li>
          <li>
            <t>more %o-items</t>
          </li>
        </ol>
        <ol spacing="normal" type="%x"><li>
            <t>first %x-item</t>
          </li>
          <li>
            <t>more %x-items</t>
          </li>
          <li>
            <t>more %x-items</t>
          </li>
          <li>
            <t>more %x-items</t>
          </li>
          <li>
            <t>more %x-items</t>
          </li>
          <li>
            <t>more %x-items</t>
          </li>
          <li>
            <t>more %x-items</t>
          </li>
          <li>
            <t>more %x-items</t>
          </li>
          <li>
            <t>more %x-items</t>
          </li>
          <li>
            <t>more %x-items</t>
          </li>
          <li>
            <t>more %x-items</t>
          </li>
          <li>
            <t>more %x-items</t>
          </li>
          <li>
            <t>more %x-items</t>
          </li>
          <li>
            <t>more %x-items</t>
          </li>
          <li>
            <t>more %x-items</t>
          </li>
          <li>
            <t>more %x-items</t>
          </li>
          <li>
            <t>more %x-items</t>
          </li>
        </ol>
        <ol spacing="normal" type="%X"><li>
            <t>first %X-item</t>
          </li>
          <li>
            <t>more %X-items</t>
          </li>
          <li>
            <t>more %X-items</t>
          </li>
          <li>
            <t>more %X-items</t>
          </li>
          <li>
            <t>more %X-items</t>
          </li>
          <li>
            <t>more %X-items</t>
          </li>
          <li>
            <t>more %X-items</t>
          </li>
          <li>
            <t>more %X-items</t>
          </li>
          <li>
            <t>more %X-items</t>
          </li>
          <li>
            <t>more %X-items</t>
          </li>
          <li>
            <t>more %X-items</t>
          </li>
          <li>
            <t>more %X-items</t>
          </li>
          <li>
            <t>more %X-items</t>
          </li>
          <li>
            <t>more %X-items</t>
          </li>
          <li>
            <t>more %X-items</t>
          </li>
          <li>
            <t>more %X-items</t>
          </li>
          <li>
            <t>more %X-items</t>
          </li>
        </ol>
      </section>
    </section>
    <section anchor="codeExample" numbered="true" toc="default">
      <name>Example of Code or MIB Module To Be Extracted</name>
      <t keepWithNext="true">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"><![CDATA[

/**** an example C program */

#include <stdio.h>

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

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

    exit(0);
} /* main */

/* end of file */

]]></sourcecode>
    </section>
    <section anchor="Acknowledgements" numbered="true" toc="default">
      <name>Acknowledgements</name>
      <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" format="default"/>.
	This document may be shared as needed <xref target="SHARING" format="default"/>.  If necessary, appeal to <xref target="DOI_10.1145_2975159" format="default"/>.
      </t>
    </section>
    <!-- Possibly a 'Contributors' section ... -->

    <section anchor="IANA" numbered="true" toc="default">
      <name>IANA Considerations</name>
      <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" 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" numbered="true" toc="default">
      <name>Security Considerations</name>
      <t>All drafts are required to have a security considerations section.
      See <xref target="RFC3552" 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>
      <name>References</name>
      <references>
        <name>Normative References</name>
        <!--?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml"?-->
      <reference anchor="RFC2119" target="https://www.rfc-editor.org/info/rfc2119" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml">
          <front>
            <title>Key words for use in RFCs to Indicate Requirement Levels</title>
            <author fullname="S. Bradner" initials="S." surname="Bradner"/>
            <date month="March" year="1997"/>
            <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">
          <!-- 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>
        <name>Informative References</name>
        <!-- Here we use entities that we defined at the beginning. -->

      <reference anchor="RFC2629" target="https://www.rfc-editor.org/info/rfc2629" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2629.xml">
          <front>
            <title>Writing I-Ds and RFCs using XML</title>
            <author fullname="M. Rose" initials="M." surname="Rose"/>
            <date month="June" year="1999"/>
            <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>
          <seriesInfo name="RFC" value="2629"/>
          <seriesInfo name="DOI" value="10.17487/RFC2629"/>
        </reference>
        <reference anchor="RFC3552" target="https://www.rfc-editor.org/info/rfc3552" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3552.xml">
          <front>
            <title>Guidelines for Writing RFC Text on Security Considerations</title>
            <author fullname="E. Rescorla" initials="E." surname="Rescorla"/>
            <author fullname="B. Korver" initials="B." surname="Korver"/>
            <date month="July" year="2003"/>
            <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"/>
          <seriesInfo name="DOI" value="10.17487/RFC3552"/>
        </reference>
        <reference anchor="I-D.narten-iana-considerations-rfc2434bis" target="https://www.ietf.org/archive/id/draft-narten-iana-considerations-rfc2434bis-09.txt" xml:base="https://bib.ietf.org/public/rfc/bibxml3/reference.I-D.narten-iana-considerations-rfc2434bis.xml">
          <front>
            <title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
            <author fullname="Dr. Thomas Narten" initials="T." surname="Narten"/>
            <author fullname="Harald T. Alvestrand" initials="H. T." surname="Alvestrand"/>
            <date day="26" month="March" 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 namespace 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 namespace, 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 namespace and provides guidelines for authors on the specific text that must be included in documents that place demands on IANA. This document obsoletes RFC 2434. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-narten-iana-considerations-rfc2434bis-09"/>
        </reference>
        <!-- Reference with query argument -->
      <reference anchor="DOI_10.1145_2975159" target="https://doi.org/10.1145/2975159" xml:base="https://bib.ietf.org/public/rfc/bibxml-doi/reference.DOI.10.1145/2975159.xml">
          <front>
            <title>Jupiter rising</title>
            <author fullname="Arjun Singh" surname="Singh">
              <organization>Google, Inc.</organization>
            </author>
            <author fullname="Joon Ong" surname="Ong">
              <organization>Google, Inc.</organization>
            </author>
            <author fullname="Amit Agarwal" surname="Agarwal">
              <organization>Google, Inc.</organization>
            </author>
            <author fullname="Glen Anderson" surname="Anderson">
              <organization>Google, Inc.</organization>
            </author>
            <author fullname="Ashby Armistead" surname="Armistead">
              <organization>Google, Inc.</organization>
            </author>
            <author fullname="Roy Bannon" surname="Bannon">
              <organization>Google, Inc.</organization>
            </author>
            <author fullname="Seb Boving" surname="Boving">
              <organization>Google, Inc.</organization>
            </author>
            <author fullname="Gaurav Desai" surname="Desai">
              <organization>Google, Inc.</organization>
            </author>
            <author fullname="Bob Felderman" surname="Felderman">
              <organization>Google, Inc.</organization>
            </author>
            <author fullname="Paulie Germano" surname="Germano">
              <organization>Google, Inc.</organization>
            </author>
            <author fullname="Anand Kanagala" surname="Kanagala">
              <organization>Google, Inc.</organization>
            </author>
            <author fullname="Hong Liu" surname="Liu">
              <organization>Google, Inc.</organization>
            </author>
            <author fullname="Jeff Provost" surname="Provost">
              <organization>Google, Inc.</organization>
            </author>
            <author fullname="Jason Simmons" surname="Simmons">
              <organization>Google, Inc.</organization>
            </author>
            <author fullname="Eiichi Tanda" surname="Tanda">
              <organization>Google, Inc.</organization>
            </author>
            <author fullname="Jim Wanderer" surname="Wanderer">
              <organization>Google, Inc.</organization>
            </author>
            <author fullname="Urs Hölzle" surname="Hölzle">
              <organization>Google, Inc.</organization>
            </author>
            <author fullname="Stephen Stuart" surname="Stuart">
              <organization>Google, Inc.</organization>
            </author>
            <author fullname="Amin Vahdat" surname="Vahdat">
              <organization>Google, Inc.</organization>
            </author>
            <author>
              <organization>Association for Computing Machinery (ACM)</organization>
            </author>
            <date day="24" month="August" year="2016"/>
            <abstract>
              <t>We present our approach for overcoming the cost, operational complexity, and limited scale endemic to datacenter networks a decade ago. Three themes unify the five generations of datacenter networks detailed in this paper. First, multi-stage Clos topologies built from commodity switch silicon can support cost-effective deployment of building-scale networks. Second, much of the general, but complex, decentralized network routing and management protocols supporting arbitrary deployment scenarios were overkill for single-operator, pre-planned datacenter networks. We built a centralized control mechanism based on a global configuration pushed to all datacenter switches. Third, modular hardware design coupled with simple, robust software allowed our design to also support inter-cluster and wide-area networks. Our datacenter networks run at dozens of sites across the planet, scaling in capacity by 100x over 10 years to more than 1 Pbps of bisection bandwidth. A more detailed version of this paper is available at Ref.</t>
            </abstract>
          </front>
          <refcontent>Communications of the ACM, vol. 59, no. 9, pp. 88-97</refcontent>
          <seriesInfo name="DOI" value="10.1145/2975159"/>
        </reference>
        <!-- A reference written by by an organization not a person. -->

      <reference anchor="DOMINATION" target="http://www.example.com/dominator.html">
          <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">
          <front>
            <title>
		I Learned to Share in Kindergarten
            </title>
            <author>
              <organization>
		Sesame Street
              </organization>
            </author>
            <date year="1972"/>
          </front>
        </reference>
      </references>
    </references>
    <section anchor="app-additional" numbered="true" toc="default">
      <name>Additional Stuff</name>
      <t>This becomes an Appendix.</t>
    </section>
    <section anchor="contributors" numbered="false" toc="default">
      <name>Contributors</name>
      <t>This becomes an unnumbered section</t>
    </section>
  </back>
</rfc>
