1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917
|
<?xml version='1.0' encoding='utf-8'?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" version="3" 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" consensus="false" prepTime="2023-10-11T14:23:55" indexInclude="true" scripts="Common,Latin">
<!-- xml2rfc v2v3 conversion 3.18.1 -->
<!-- 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 indent="0" 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 indent="0" pn="section-boilerplate.1-1">
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
</t>
<t indent="0" 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 indent="0" 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 indent="0" 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 indent="0" pn="section-boilerplate.2-1">
Copyright (c) 2009 IETF Trust and the persons identified as
the document authors. All rights reserved.
</t>
<t indent="0" 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 indent="0" 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 indent="0" 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 indent="0" 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 indent="0" 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 indent="0" 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 indent="0" 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 indent="0" 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 indent="0" 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 indent="0" 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 indent="0" 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 indent="0" 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 indent="0" 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 indent="0" 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 indent="0" 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 indent="0" 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 indent="0" 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 indent="0" 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 indent="0" 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 indent="0" 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 indent="0" 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 indent="0" 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 indent="0" 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 indent="0" 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 indent="0" 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 indent="0" pn="section-2-1">List styles: 'empty', 'symbols', 'letters', 'numbers', 'hanging',
'format'.</t>
<ul spacing="normal" bare="false" empty="false" indent="3" pn="section-2-2">
<li pn="section-2-2.1">
<t indent="0" pn="section-2-2.1.1">First bullet</t>
</li>
<li pn="section-2-2.2">
<t indent="0" pn="section-2-2.2.1">Second bullet</t>
</li>
</ul>
<t indent="0" 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 indent="0" pn="section-3-1">Figures should not exceed 69 characters wide to allow for the indent
of sections.</t>
<t keepWithNext="true" indent="0" 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">
+-----------------------+
| Use XML, be Happy :-) |
|_______________________|
</artwork>
</artset>
</figure>
<t keepWithPrevious="true" indent="0" pn="section-3-4">Cross-references allowed in pre- and postamble. <xref target="min_ref" format="default" sectionFormat="of" derivedContent="min_ref"/>.</t>
<t indent="0" pn="section-3-5">The CDATA means you don't need to escape meta-characters (especially
< (&lt;) and & (&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="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 indent="0" 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 indent="0" pn="section-4.2-1">.. are very similar to figures:</t>
<t keepWithNext="true" indent="0" 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" indent="0" 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 indent="0" 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 indent="0" pn="section-5-3">Simulating more than one paragraph in a list item using
<vspace>: </t>
<ol spacing="normal" type="a" indent="adaptive" start="1" pn="section-5-4"><li pn="section-5-4.1" derivedCounter="a.">
<t indent="0" pn="section-5-4.1.1">First, a short item.</t>
</li>
<li pn="section-5-4.2" derivedCounter="b.">
<t indent="0" pn="section-5-4.2.1">Second, a longer list item.</t>
<t indent="0" pn="section-5-4.2.2"> And
something that looks like a separate pararaph..</t>
</li>
</ol>
<t indent="0" pn="section-5-5">Simple indented paragraph using the "empty" style: </t>
<ul empty="true" spacing="normal" bare="false" indent="3" pn="section-5-6">
<li pn="section-5-6.1">
<t indent="0" pn="section-5-6.1.1">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="include" removeInRFC="false" pn="section-5.1">
<name slugifiedName="name-numbering-lists-across-list">Numbering Lists across Lists and Sections</name>
<t indent="0" pn="section-5.1-1">Numbering items continuously although they are in separate
<list> elements, maybe in separate sections using the "format"
style and a "counter" variable.</t>
<t indent="0" pn="section-5.1-2">First list: </t>
<ol group="reqs" spacing="normal" type="R%d" start="1" indent="adaptive" pn="section-5.1-3"><li pn="section-5.1-3.1" derivedCounter="R1">
<t indent="0" pn="section-5.1-3.1.1">#1</t>
</li>
<li pn="section-5.1-3.2" derivedCounter="R2">
<t indent="0" pn="section-5.1-3.2.1">#2</t>
</li>
<li pn="section-5.1-3.3" derivedCounter="R3">
<t indent="0" pn="section-5.1-3.3.1">#3</t>
</li>
</ol>
<t indent="0" pn="section-5.1-4"> Specify the indent explicitly so that all the items line up
nicely.</t>
<t indent="0" pn="section-5.1-5">Second list: </t>
<ol group="reqs" spacing="normal" type="R%d" start="4" indent="adaptive" pn="section-5.1-6"><li pn="section-5.1-6.1" derivedCounter="R4">
<t indent="0" pn="section-5.1-6.1.1">#4</t>
</li>
<li pn="section-5.1-6.2" derivedCounter="R5">
<t indent="0" pn="section-5.1-6.2.1">#5</t>
</li>
<li pn="section-5.1-6.3" derivedCounter="R6">
<t indent="0" pn="section-5.1-6.3.1">#6</t>
</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 indent="0" pn="section-5.2-1">List continues here.</t>
<t indent="0" pn="section-5.2-2">Third list: </t>
<ol group="reqs" spacing="normal" type="R%d" start="7" indent="adaptive" pn="section-5.2-3"><li pn="section-5.2-3.1" derivedCounter="R7">
<t indent="0" pn="section-5.2-3.1.1">#7</t>
</li>
<li pn="section-5.2-3.2" derivedCounter="R8">
<t indent="0" pn="section-5.2-3.2.1">#8</t>
</li>
<li pn="section-5.2-3.3" derivedCounter="R9">
<t indent="0" pn="section-5.2-3.3.1">#9</t>
</li>
<li pn="section-5.2-3.4" derivedCounter="R10">
<t indent="0" pn="section-5.2-3.4.1">#10</t>
</li>
</ol>
<t indent="0" 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 indent="0" pn="section-5.3-1">Simulating more than one paragraph in a list item using
<vspace>:
</t>
<ol spacing="normal" type="a" indent="adaptive" start="1" pn="section-5.3-2"><li pn="section-5.3-2.1" derivedCounter="a.">
<t indent="0" pn="section-5.3-2.1.1">First, a short item.</t>
</li>
<li pn="section-5.3-2.2" derivedCounter="b.">
<t indent="0" pn="section-5.3-2.2.1">Second, a longer list item.</t>
<t indent="0" 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 indent="0" pn="section-5.3-2.3.1">and a sublist, also with letters
</t>
<ol spacing="normal" type="A" indent="adaptive" start="1" pn="section-5.3-2.3.2"><li pn="section-5.3-2.3.2.1" derivedCounter="A.">
<t indent="0" pn="section-5.3-2.3.2.1.1">first subitem</t>
</li>
<li pn="section-5.3-2.3.2.2" derivedCounter="B.">
<t indent="0" pn="section-5.3-2.3.2.2.1">second subitem</t>
</li>
<li pn="section-5.3-2.3.2.3" derivedCounter="C.">
<t indent="0" pn="section-5.3-2.3.2.3.1">and a sub-sublist, also with letters
</t>
<ol spacing="normal" type="a" indent="adaptive" start="1" pn="section-5.3-2.3.2.3.2"><li pn="section-5.3-2.3.2.3.2.1" derivedCounter="a.">
<t indent="0" pn="section-5.3-2.3.2.3.2.1.1">first sub-subitem</t>
</li>
<li pn="section-5.3-2.3.2.3.2.2" derivedCounter="b.">
<t indent="0" pn="section-5.3-2.3.2.3.2.2.1">second sub-subitem</t>
</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 indent="0" pn="section-5.4-1">many formats
</t>
<ol spacing="normal" type="%c" indent="adaptive" start="1" pn="section-5.4-2"><li pn="section-5.4-2.1" derivedCounter="a">
<t indent="0" pn="section-5.4-2.1.1">first %c-item</t>
</li>
<li pn="section-5.4-2.2" derivedCounter="b">
<t indent="0" pn="section-5.4-2.2.1">more %c-items</t>
</li>
</ol>
<ol spacing="normal" type="%C" indent="adaptive" start="1" pn="section-5.4-3"><li pn="section-5.4-3.1" derivedCounter="A">
<t indent="0" pn="section-5.4-3.1.1">first %C-item</t>
</li>
<li pn="section-5.4-3.2" derivedCounter="B">
<t indent="0" pn="section-5.4-3.2.1">more %C-items</t>
</li>
</ol>
<ol spacing="normal" type="%d" indent="adaptive" start="1" pn="section-5.4-4"><li pn="section-5.4-4.1" derivedCounter="1">
<t indent="0" pn="section-5.4-4.1.1">first %d-item.</t>
</li>
<li pn="section-5.4-4.2" derivedCounter="2">
<t indent="0" pn="section-5.4-4.2.1">more %d-items.</t>
</li>
</ol>
<ol spacing="normal" type="%i" indent="adaptive" start="1" pn="section-5.4-5"><li pn="section-5.4-5.1" derivedCounter="i">
<t indent="0" pn="section-5.4-5.1.1">first %i-item</t>
</li>
<li pn="section-5.4-5.2" derivedCounter="ii">
<t indent="0" pn="section-5.4-5.2.1">more %i-items</t>
</li>
<li pn="section-5.4-5.3" derivedCounter="iii">
<t indent="0" pn="section-5.4-5.3.1">more %i-items</t>
</li>
<li pn="section-5.4-5.4" derivedCounter="iv">
<t indent="0" pn="section-5.4-5.4.1">more %i-items</t>
</li>
<li pn="section-5.4-5.5" derivedCounter="v">
<t indent="0" pn="section-5.4-5.5.1">more %i-items</t>
</li>
<li pn="section-5.4-5.6" derivedCounter="vi">
<t indent="0" pn="section-5.4-5.6.1">more %i-items</t>
</li>
<li pn="section-5.4-5.7" derivedCounter="vii">
<t indent="0" pn="section-5.4-5.7.1">more %i-items</t>
</li>
<li pn="section-5.4-5.8" derivedCounter="viii">
<t indent="0" pn="section-5.4-5.8.1">more %i-items</t>
</li>
<li pn="section-5.4-5.9" derivedCounter="ix">
<t indent="0" pn="section-5.4-5.9.1">more %i-items</t>
</li>
</ol>
<ol spacing="normal" type="%I" indent="adaptive" start="1" pn="section-5.4-6"><li pn="section-5.4-6.1" derivedCounter="I">
<t indent="0" pn="section-5.4-6.1.1">first %I-item</t>
</li>
<li pn="section-5.4-6.2" derivedCounter="II">
<t indent="0" pn="section-5.4-6.2.1">more %I-items</t>
</li>
<li pn="section-5.4-6.3" derivedCounter="III">
<t indent="0" pn="section-5.4-6.3.1">more %I-items</t>
</li>
<li pn="section-5.4-6.4" derivedCounter="IV">
<t indent="0" pn="section-5.4-6.4.1">more %I-items</t>
</li>
<li pn="section-5.4-6.5" derivedCounter="V">
<t indent="0" pn="section-5.4-6.5.1">more %I-items</t>
</li>
<li pn="section-5.4-6.6" derivedCounter="VI">
<t indent="0" pn="section-5.4-6.6.1">more %I-items</t>
</li>
<li pn="section-5.4-6.7" derivedCounter="VII">
<t indent="0" pn="section-5.4-6.7.1">more %I-items</t>
</li>
<li pn="section-5.4-6.8" derivedCounter="VIII">
<t indent="0" pn="section-5.4-6.8.1">more %I-items</t>
</li>
<li pn="section-5.4-6.9" derivedCounter="IX">
<t indent="0" pn="section-5.4-6.9.1">more %I-items</t>
</li>
</ol>
<ol spacing="normal" type="%o" indent="adaptive" start="1" pn="section-5.4-7"><li pn="section-5.4-7.1" derivedCounter="1">
<t indent="0" pn="section-5.4-7.1.1">first %o-item</t>
</li>
<li pn="section-5.4-7.2" derivedCounter="2">
<t indent="0" pn="section-5.4-7.2.1">more %o-items</t>
</li>
<li pn="section-5.4-7.3" derivedCounter="3">
<t indent="0" pn="section-5.4-7.3.1">more %o-items</t>
</li>
<li pn="section-5.4-7.4" derivedCounter="4">
<t indent="0" pn="section-5.4-7.4.1">more %o-items</t>
</li>
<li pn="section-5.4-7.5" derivedCounter="5">
<t indent="0" pn="section-5.4-7.5.1">more %o-items</t>
</li>
<li pn="section-5.4-7.6" derivedCounter="6">
<t indent="0" pn="section-5.4-7.6.1">more %o-items</t>
</li>
<li pn="section-5.4-7.7" derivedCounter="7">
<t indent="0" pn="section-5.4-7.7.1">more %o-items</t>
</li>
<li pn="section-5.4-7.8" derivedCounter="10">
<t indent="0" pn="section-5.4-7.8.1">more %o-items</t>
</li>
<li pn="section-5.4-7.9" derivedCounter="11">
<t indent="0" pn="section-5.4-7.9.1">more %o-items</t>
</li>
</ol>
<ol spacing="normal" type="%x" indent="adaptive" start="1" pn="section-5.4-8"><li pn="section-5.4-8.1" derivedCounter="1">
<t indent="0" pn="section-5.4-8.1.1">first %x-item</t>
</li>
<li pn="section-5.4-8.2" derivedCounter="2">
<t indent="0" pn="section-5.4-8.2.1">more %x-items</t>
</li>
<li pn="section-5.4-8.3" derivedCounter="3">
<t indent="0" pn="section-5.4-8.3.1">more %x-items</t>
</li>
<li pn="section-5.4-8.4" derivedCounter="4">
<t indent="0" pn="section-5.4-8.4.1">more %x-items</t>
</li>
<li pn="section-5.4-8.5" derivedCounter="5">
<t indent="0" pn="section-5.4-8.5.1">more %x-items</t>
</li>
<li pn="section-5.4-8.6" derivedCounter="6">
<t indent="0" pn="section-5.4-8.6.1">more %x-items</t>
</li>
<li pn="section-5.4-8.7" derivedCounter="7">
<t indent="0" pn="section-5.4-8.7.1">more %x-items</t>
</li>
<li pn="section-5.4-8.8" derivedCounter="8">
<t indent="0" pn="section-5.4-8.8.1">more %x-items</t>
</li>
<li pn="section-5.4-8.9" derivedCounter="9">
<t indent="0" pn="section-5.4-8.9.1">more %x-items</t>
</li>
<li pn="section-5.4-8.10" derivedCounter="a">
<t indent="0" pn="section-5.4-8.10.1">more %x-items</t>
</li>
<li pn="section-5.4-8.11" derivedCounter="b">
<t indent="0" pn="section-5.4-8.11.1">more %x-items</t>
</li>
<li pn="section-5.4-8.12" derivedCounter="c">
<t indent="0" pn="section-5.4-8.12.1">more %x-items</t>
</li>
<li pn="section-5.4-8.13" derivedCounter="d">
<t indent="0" pn="section-5.4-8.13.1">more %x-items</t>
</li>
<li pn="section-5.4-8.14" derivedCounter="e">
<t indent="0" pn="section-5.4-8.14.1">more %x-items</t>
</li>
<li pn="section-5.4-8.15" derivedCounter="f">
<t indent="0" pn="section-5.4-8.15.1">more %x-items</t>
</li>
<li pn="section-5.4-8.16" derivedCounter="10">
<t indent="0" pn="section-5.4-8.16.1">more %x-items</t>
</li>
<li pn="section-5.4-8.17" derivedCounter="11">
<t indent="0" pn="section-5.4-8.17.1">more %x-items</t>
</li>
</ol>
<ol spacing="normal" type="%X" indent="adaptive" start="1" pn="section-5.4-9"><li pn="section-5.4-9.1" derivedCounter="1">
<t indent="0" pn="section-5.4-9.1.1">first %X-item</t>
</li>
<li pn="section-5.4-9.2" derivedCounter="2">
<t indent="0" pn="section-5.4-9.2.1">more %X-items</t>
</li>
<li pn="section-5.4-9.3" derivedCounter="3">
<t indent="0" pn="section-5.4-9.3.1">more %X-items</t>
</li>
<li pn="section-5.4-9.4" derivedCounter="4">
<t indent="0" pn="section-5.4-9.4.1">more %X-items</t>
</li>
<li pn="section-5.4-9.5" derivedCounter="5">
<t indent="0" pn="section-5.4-9.5.1">more %X-items</t>
</li>
<li pn="section-5.4-9.6" derivedCounter="6">
<t indent="0" pn="section-5.4-9.6.1">more %X-items</t>
</li>
<li pn="section-5.4-9.7" derivedCounter="7">
<t indent="0" pn="section-5.4-9.7.1">more %X-items</t>
</li>
<li pn="section-5.4-9.8" derivedCounter="8">
<t indent="0" pn="section-5.4-9.8.1">more %X-items</t>
</li>
<li pn="section-5.4-9.9" derivedCounter="9">
<t indent="0" pn="section-5.4-9.9.1">more %X-items</t>
</li>
<li pn="section-5.4-9.10" derivedCounter="A">
<t indent="0" pn="section-5.4-9.10.1">more %X-items</t>
</li>
<li pn="section-5.4-9.11" derivedCounter="B">
<t indent="0" pn="section-5.4-9.11.1">more %X-items</t>
</li>
<li pn="section-5.4-9.12" derivedCounter="C">
<t indent="0" pn="section-5.4-9.12.1">more %X-items</t>
</li>
<li pn="section-5.4-9.13" derivedCounter="D">
<t indent="0" pn="section-5.4-9.13.1">more %X-items</t>
</li>
<li pn="section-5.4-9.14" derivedCounter="E">
<t indent="0" pn="section-5.4-9.14.1">more %X-items</t>
</li>
<li pn="section-5.4-9.15" derivedCounter="F">
<t indent="0" pn="section-5.4-9.15.1">more %X-items</t>
</li>
<li pn="section-5.4-9.16" derivedCounter="10">
<t indent="0" pn="section-5.4-9.16.1">more %X-items</t>
</li>
<li pn="section-5.4-9.17" derivedCounter="11">
<t indent="0" pn="section-5.4-9.17.1">more %X-items</t>
</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" indent="0" pn="section-6-1">The <artwork> 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 <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="include" removeInRFC="false" pn="section-7">
<name slugifiedName="name-acknowledgements">Acknowledgements</name>
<t indent="0" 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 indent="0" 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="DOI_10.1145_2975159" format="default" sectionFormat="of" derivedContent="DOI_10.1145_2975159"/>.
</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 indent="0" pn="section-8-1">This memo includes no request to IANA.</t>
<t indent="0" 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 indent="0" 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://bib.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>
<author fullname="S. Bradner" initials="S." surname="Bradner"/>
<date month="March" year="1997"/>
<abstract>
<t indent="0">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>
</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="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" quoteTitle="true" derivedAnchor="DOI_10.1145_2975159">
<front>
<title>Jupiter rising</title>
<author fullname="Arjun Singh" surname="Singh">
<organization showOnFrontPage="true">Google, Inc.</organization>
</author>
<author fullname="Joon Ong" surname="Ong">
<organization showOnFrontPage="true">Google, Inc.</organization>
</author>
<author fullname="Amit Agarwal" surname="Agarwal">
<organization showOnFrontPage="true">Google, Inc.</organization>
</author>
<author fullname="Glen Anderson" surname="Anderson">
<organization showOnFrontPage="true">Google, Inc.</organization>
</author>
<author fullname="Ashby Armistead" surname="Armistead">
<organization showOnFrontPage="true">Google, Inc.</organization>
</author>
<author fullname="Roy Bannon" surname="Bannon">
<organization showOnFrontPage="true">Google, Inc.</organization>
</author>
<author fullname="Seb Boving" surname="Boving">
<organization showOnFrontPage="true">Google, Inc.</organization>
</author>
<author fullname="Gaurav Desai" surname="Desai">
<organization showOnFrontPage="true">Google, Inc.</organization>
</author>
<author fullname="Bob Felderman" surname="Felderman">
<organization showOnFrontPage="true">Google, Inc.</organization>
</author>
<author fullname="Paulie Germano" surname="Germano">
<organization showOnFrontPage="true">Google, Inc.</organization>
</author>
<author fullname="Anand Kanagala" surname="Kanagala">
<organization showOnFrontPage="true">Google, Inc.</organization>
</author>
<author fullname="Hong Liu" surname="Liu">
<organization showOnFrontPage="true">Google, Inc.</organization>
</author>
<author fullname="Jeff Provost" surname="Provost">
<organization showOnFrontPage="true">Google, Inc.</organization>
</author>
<author fullname="Jason Simmons" surname="Simmons">
<organization showOnFrontPage="true">Google, Inc.</organization>
</author>
<author fullname="Eiichi Tanda" surname="Tanda">
<organization showOnFrontPage="true">Google, Inc.</organization>
</author>
<author fullname="Jim Wanderer" surname="Wanderer">
<organization showOnFrontPage="true">Google, Inc.</organization>
</author>
<author fullname="Urs Hölzle" surname="Hölzle">
<organization showOnFrontPage="true">Google, Inc.</organization>
</author>
<author fullname="Stephen Stuart" surname="Stuart">
<organization showOnFrontPage="true">Google, Inc.</organization>
</author>
<author fullname="Amin Vahdat" surname="Vahdat">
<organization showOnFrontPage="true">Google, Inc.</organization>
</author>
<author>
<organization showOnFrontPage="true">Association for Computing Machinery (ACM)</organization>
</author>
<date day="24" month="August" year="2016"/>
<abstract>
<t indent="0">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>
<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" 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" quoteTitle="true" derivedAnchor="I-D.narten-iana-considerations-rfc2434bis">
<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 indent="0">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"/>
<refcontent>Work in Progress</refcontent>
</reference>
<reference anchor="RFC2629" target="https://www.rfc-editor.org/info/rfc2629" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2629.xml" quoteTitle="true" derivedAnchor="RFC2629">
<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 indent="0">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" quoteTitle="true" derivedAnchor="RFC3552">
<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 indent="0">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="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 indent="0" 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 indent="0" pn="section-appendix.b-1">This becomes an unnumbered section</t>
</section>
<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>
|