idnits 2.17.1 draft-reschke-xml2rfc-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- -- The document has an IETF Trust Provisions (28 Dec 2009) Section 6.c(i) Publication Limitation clause. -- The document has an IETF Trust Provisions (28 Dec 2009) Section 6.c(ii) Publication Limitation clause. If this document is intended for submission to the IESG for publication, this constitutes an error. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- -- The draft header indicates that this document obsoletes RFC2629, but the abstract doesn't seem to mention this, which it should. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to contain a disclaimer for pre-RFC5378 work, but was first submitted on or after 10 November 2008. The disclaimer is usually necessary only for documents that revise or obsolete older RFCs, and that take significant amounts of text from those RFCs. If you can contact all authors of the source material and they are willing to grant the BCP78 rights to the IETF Trust, you can and should remove the disclaimer. Otherwise, the disclaimer is needed and you can ignore this comment. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (January 28, 2014) is 3741 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Possible downref: Non-RFC (?) normative reference: ref. 'XML' -- Obsolete informational reference (is this intentional?): RFC 2629 (Obsoleted by RFC 7749) -- Obsolete informational reference (is this intentional?): RFC 3023 (Obsoleted by RFC 7303) -- Obsolete informational reference (is this intentional?): RFC 5741 (Obsoleted by RFC 7841) Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 8 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group J. Reschke 3 Internet-Draft greenbytes 4 Obsoletes: 2629 (if approved) January 28, 2014 5 Intended status: Standards Track 6 Expires: August 1, 2014 8 The 'XML2RFC' version 2 Vocabulary 9 draft-reschke-xml2rfc-04 11 Abstract 13 This document defines the 'XML2RFC' version 2 vocabulary; an XML- 14 based language used for writing RFCs and Internet-Drafts. 16 Editorial Note (To be removed by RFC Editor) 18 Discussion of this draft takes place on the XML2RFC mailing list 19 (xml2rfc@ietf.org), which has its home page at 20 . 22 Status of This Memo 24 This Internet-Draft is submitted in full conformance with the 25 provisions of BCP 78 and BCP 79. 27 Internet-Drafts are working documents of the Internet Engineering 28 Task Force (IETF). Note that other groups may also distribute 29 working documents as Internet-Drafts. The list of current Internet- 30 Drafts is at http://datatracker.ietf.org/drafts/current/. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet-Drafts as reference 35 material or to cite them other than as "work in progress." 37 This Internet-Draft will expire on August 1, 2014. 39 Copyright Notice 41 Copyright (c) 2014 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents 46 (http://trustee.ietf.org/license-info) in effect on the date of 47 publication of this document. Please review these documents 48 carefully, as they describe your rights and restrictions with respect 49 to this document. Code Components extracted from this document must 50 include Simplified BSD License text as described in Section 4.e of 51 the Trust Legal Provisions and are provided without warranty as 52 described in the Simplified BSD License. 54 Table of Contents 56 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 57 1.1. Syntax Notation . . . . . . . . . . . . . . . . . . . . . 4 58 2. Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 59 2.1. . . . . . . . . . . . . . . . . . . . . . . . . 4 60 2.2.
. . . . . . . . . . . . . . . . . . . . . . . . 5 61 2.3. . . . . . . . . . . . . . . . . . . . . . . . 5 62 2.4. . . . . . . . . . . . . . . . . . . . . . . . . . . 6 63 2.5. . . . . . . . . . . . . . . . . . . . . . . . . 6 64 2.6. . . . . . . . . . . . . . . . . . . . . . . . . . 8 65 2.7. . . . . . . . . . . . . . . . . . . . . . . . . . . 9 66 2.8. . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 67 2.9. . . . . . . . . . . . . . . . . . . . . . . . . . . 10 68 2.10. . . . . . . . . . . . . . . . . . . . . . . . . . . 10 69 2.11. . . . . . . . . . . . . . . . . . . . . . . . . 10 70 2.12. . . . . . . . . . . . . . . . . . . . . . . . . . . 11 71 2.13. . . . . . . . . . . . . . . . . . . . . . . . . . . 11 72 2.14. . . . . . . . . . . . . . . . . . . . . . . . . . 12 73 2.15. . . . . . . . . . . . . . . . . . . . . . . . . . . 12 74 2.16. . . . . . . . . . . . . . . . . . . . . . . . 13 75 2.17.
. . . . . . . . . . . . . . . . . . . . . . . . . 13 76 2.18. . . . . . . . . . . . . . . . . . . . . . . . . . 14 77 2.19. . . . . . . . . . . . . . . . . . . . . . . . . . 15 78 2.20. . . . . . . . . . . . . . . . . . . . . . . . . . . 16 79 2.21. . . . . . . . . . . . . . . . . . . . . . . . . 16 80 2.22. . . . . . . . . . . . . . . . . . . . . . . . . . . 17 81 2.23. . . . . . . . . . . . . . . . . . . . . . . . . . 19 82 2.24. . . . . . . . . . . . . . . . . . . . . . . . . . . 19 83 2.25. . . . . . . . . . . . . . . . . . . . . . . 19 84 2.26. . . . . . . . . . . . . . . . . . . . . . . . . . 20 85 2.27. . . . . . . . . . . . . . . . . . . . . . . . . . 20 86 2.28. . . . . . . . . . . . . . . . . . . . . . . . 21 87 2.29. . . . . . . . . . . . . . . . . . . . . . . . . 21 88 2.30. . . . . . . . . . . . . . . . . . . . . . . . 22 89 2.31. . . . . . . . . . . . . . . . . . . . . . . . 22 90 2.32. . . . . . . . . . . . . . . . . . . . . . . . . . 23 91 2.33. . . . . . . . . . . . . . . . . . . . . . . . . . . 23 92 2.34.
. . . . . . . . . . . . . . . . . . . . . . . . 26 93 2.35. . . . . . . . . . . . . . . . . . . . . . . . 27 94 2.36. . . . . . . . . . . . . . . . . . . . . . . . . . 28 95 2.37. . . . . . . . . . . . . . . . . . . . . . . . . . 28 96 2.38. . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 97 2.39. . . . . . . . . . . . . . . . . . . . . . . . 29 98 2.40. . . . . . . . . . . . . . . . . . . . . . . . . . 31 99 2.41. <ttcol> . . . . . . . . . . . . . . . . . . . . . . . . . 31 100 2.42. <uri> . . . . . . . . . . . . . . . . . . . . . . . . . . 32 101 2.43. <vspace> . . . . . . . . . . . . . . . . . . . . . . . . . 32 102 2.44. <workgroup> . . . . . . . . . . . . . . . . . . . . . . . 32 103 2.45. <xref> . . . . . . . . . . . . . . . . . . . . . . . . . . 33 104 3. Special Unicode Code Points . . . . . . . . . . . . . . . . . 34 105 4. Internationalization Considerations . . . . . . . . . . . . . 34 106 5. Security Considerations . . . . . . . . . . . . . . . . . . . 34 107 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 34 108 6.1. Internet Media Type Registration . . . . . . . . . . . . . 34 109 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 36 110 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 36 111 8.1. Normative References . . . . . . . . . . . . . . . . . . . 36 112 8.2. Informative References . . . . . . . . . . . . . . . . . . 36 113 Appendix A. Front Page Generation . . . . . . . . . . . . . . . . 38 114 A.1. The /rfc/@category Attribute . . . . . . . . . . . . . . . 38 115 A.2. The /rfc/@ipr Attribute . . . . . . . . . . . . . . . . . 38 116 A.2.1. Current Values: '*trust200902' . . . . . . . . . . . . 39 117 A.2.2. Historic Values . . . . . . . . . . . . . . . . . . . 40 118 Appendix B. Changes from RFC 2629 ('v1') . . . . . . . . . . . . 41 119 B.1. Removed Elements . . . . . . . . . . . . . . . . . . . . . 41 120 B.2. Changed Defaults . . . . . . . . . . . . . . . . . . . . . 41 121 B.3. Changed Elements . . . . . . . . . . . . . . . . . . . . . 41 122 B.4. New Elements . . . . . . . . . . . . . . . . . . . . . . . 42 123 Appendix C. Relax NG Schema . . . . . . . . . . . . . . . . . . . 42 124 Appendix D. Proposed Future Changes for 'v3' . . . . . . . . . . 48 125 D.1. Contact Information . . . . . . . . . . . . . . . . . . . 48 126 D.2. Figures . . . . . . . . . . . . . . . . . . . . . . . . . 48 127 D.3. Linking . . . . . . . . . . . . . . . . . . . . . . . . . 49 128 D.4. Lists . . . . . . . . . . . . . . . . . . . . . . . . . . 49 129 D.5. References . . . . . . . . . . . . . . . . . . . . . . . . 49 130 D.6. Archival Considerations . . . . . . . . . . . . . . . . . 50 131 D.7. Document Metadata . . . . . . . . . . . . . . . . . . . . 50 132 D.8. Misc. . . . . . . . . . . . . . . . . . . . . . . . . . . 50 133 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 135 1. Introduction 137 This document describes version 2 ('v2') of the 'XML2RFC' vocabulary; 138 an XML-based language ('Extensible Markup Language', [XML]) used for 139 writing RFCs ([RFCSTYLE]) and Internet-Drafts ([IDGUIDE]). 141 It obsoletes the original version ("v1") [RFC2629], which contained 142 the original language definition, and which was subsequently extended 143 ("v2"). Furthermore, it discusses potential extensions in a future 144 revision ("v3"). 146 Note that the vocabulary contains certain constructs that might not 147 be used when generating the final text; however, they can provide 148 useful data for other uses (such index generation, populating a 149 keyword database, or syntax checks). 151 1.1. Syntax Notation 153 The XML vocabulary here is defined in prose, based on the Relax NG 154 schema ([RNC]) contained in Appendix C (specified in Relax NG Compact 155 Notation, "RNC"). 157 Note that the schema can be used for automated validity checks, but 158 certain constraints are only described in prose (example: the 159 conditionally required presence of the "abbrev" attribute). 161 2. Elements 163 [[anchor2: In the section below, some elements/attributes do not have 164 a prose description yet. This is because this is work-in-progress; 165 feedback with accurate descriptions is appreciated.]] 167 The sections below describe all elements and their attributes. 169 Note that attributes not labeled "mandatory" are optional. 171 2.1. <abstract> 173 Contains the abstract of the document. The abstract ought to be 174 self-contained and thus should not contain references or unexpanded 175 abbreviations. See Section 4.3 of [RFCSTYLE] for more information. 177 This element appears as child element of: <front> (Section 2.19). 179 Content model: 181 One or more <t> elements (Section 2.38) 183 2.2. <address> 185 Provides address information for the author. 187 This element appears as child element of: <author> (Section 2.6). 189 Content model: 191 In this order: 193 1. One optional <postal> element (Section 2.27) 195 2. One optional <phone> element (Section 2.26) 197 3. One optional <facsimile> element (Section 2.16) 199 4. One optional <email> element (Section 2.14) 201 5. One optional <uri> element (Section 2.42) 203 2.3. <annotation> 205 Provides additional prose augmenting a bibliographical reference. 207 For instance: 209 <annotation> 210 Latest version available at <eref 211 target='http://www.w3.org/TR/xml'/>. 212 </annotation> 214 ...will generate the text used in the reference for [XML]. 216 This element appears as child element of: <reference> (Section 2.30). 218 Content model: 220 In any order: 222 o Text 224 o <xref> elements (Section 2.45) 226 o <eref> elements (Section 2.15) 228 o <iref> elements (Section 2.20) 229 o <cref> elements (Section 2.12) 231 o <spanx> elements (Section 2.36) 233 2.4. <area> 235 Provides information about the IETF area this document applies to 236 (currently not used when generating documents). 238 This element appears as child element of: <front> (Section 2.19). 240 Content model: only text content. 242 2.5. <artwork> 244 This element allows the inclusion of "artwork" into the document. 246 <artwork> is the only element in the vocabulary that provides full 247 control of horizontal whitespace and line breaks, and thus is used 248 for a variety of things, such as: 250 o diagrams ("line art"), 252 o source code, 254 o formal languages (such as ABNF or the RNC notation used in this 255 document), 257 o complex tables, or 259 o protocol unit diagrams. 261 Alternatively, the "src" attribute allows referencing an external 262 graphics file, such as a bitmap or a vector drawing. In this case, 263 the textual content acts as fallback for output formats that do not 264 support graphics, and thus ought to contain either a "line art" 265 variant of the graphics, or otherwise prose that describes the 266 included image in sufficient detail. Note that RFCs occasionally are 267 published with enhanced diagrams; a recent example is [RFC5598]. 269 This element appears as child element of: <figure> (Section 2.17). 271 Content model: 273 Text 275 2.5.1. 'align' attribute 277 Controls whether the artwork appears left (default), centered, or 278 right. 280 Allowed values: 282 o "left" (default) 284 o "center" 286 o "right" 288 2.5.2. 'alt' attribute 290 Alternative text description of the artwork (not just the caption). 292 2.5.3. 'height' attribute 294 The suggested height of the graphics included using the "src" 295 attribute. 297 This attribute is format-dependent and ought to be avoided. 299 When generating HTML output, current implementations copy the 300 attribute "as is". For other output formats it is usually ignored. 302 2.5.4. 'name' attribute 304 A filename suitable for the contents (such as for extraction to a 305 local file). 307 This attribute generally isn't used for document generation, but it 308 can be helpful for other kinds of tools (such as automated syntax 309 checkers which work by extracting the source code). 311 2.5.5. 'src' attribute 313 The URI of a graphics file. 315 Note that this can be a "data" URI ([RFC2397]) as well, in which case 316 the graphics file essentially is in-lined. 318 2.5.6. 'type' attribute 320 Specifies the type of the artwork. 322 The value either is a well-known keyword (such as "abnf"), or an 323 Internet Media Type (see [RFC2046]). 325 How it is used depends on context and application. For instance, a 326 formatter can attempt to syntax-highlight code in certain known 327 languages. 329 2.5.7. 'width' attribute 331 The suggested width of the graphics included using the "src" 332 attribute. 334 This attribute is format-dependent and ought to be avoided. 336 When generating HTML output, current implementations copy the 337 attribute "as is". For other output formats it is usually ignored. 339 2.5.8. 'xml:space' attribute 341 Determines whitespace handling. 343 "preserve" is both the default value and the only meaningful setting 344 anyway (because that's what the <artwork> element is for). 346 See also Section 2.10 of [XML]. 348 Allowed values: 350 o "default" 352 o "preserve" (default) 354 2.6. <author> 356 Provides information about a document author. 358 The <author> elements contained within the document's <front> element 359 are used to fill the boilerplate, and also to generate the "Author's 360 Address" section (see Section 4.9 of [RFCSTYLE]). 362 Note that an "author" can also be just an organization (by not 363 specifying any of the name attributes, but adding the <organization> 364 child element). 366 Furthermore, the "role" attribute can be used to mark an author as 367 "editor". This is reflected both on the front page and in 368 bibliographical references. Note that this specification does not 369 define a precise meaning for the term "editor". 371 See Section "Authors vs. Contributors" of [RFCPOLICY] for more 372 information. 374 This element appears as child element of: <front> (Section 2.19). 376 Content model: 378 In this order: 380 1. One optional <organization> element (Section 2.25) 382 2. One optional <address> element (Section 2.2) 384 2.6.1. 'fullname' attribute 386 The full name (used in the automatically generated "Author's Address" 387 section). 389 2.6.2. 'initials' attribute 391 Author initials (used on the front page and in references). 393 Initials should be provided as a whitespace separated list of pairs 394 of a letter and a dot. 396 2.6.3. 'role' attribute 398 Specifies the role the author had in creating the document. 400 Allowed values: 402 o "editor" 404 2.6.4. 'surname' attribute 406 The author's surname. 408 2.7. <back> 410 Contains the "back" part of the document: the references and 411 appendices. 413 This element appears as child element of: <rfc> (Section 2.33). 415 Content model: 417 In this order: 419 1. Optional <references> elements (Section 2.31) 421 2. Optional <section> elements (Section 2.34) 423 2.8. <c> 425 Provides the content of a cell in a table. 427 This element appears as child element of: <texttable> (Section 2.39). 429 Content model: 431 In any order: 433 o Text 435 o <xref> elements (Section 2.45) 437 o <eref> elements (Section 2.15) 439 o <iref> elements (Section 2.20) 441 o <cref> elements (Section 2.12) 443 o <spanx> elements (Section 2.36) 445 2.9. <city> 447 Gives the city name in a postal address. 449 This element appears as child element of: <postal> (Section 2.27). 451 Content model: only text content. 453 2.10. <code> 455 Gives the postal region code. 457 This element appears as child element of: <postal> (Section 2.27). 459 Content model: only text content. 461 2.11. <country> 463 Gives the country in a postal address. 465 This element appears as child element of: <postal> (Section 2.27). 467 Content model: only text content. 469 2.12. <cref> 471 Represents a comment. 473 Comments can be used in a document while it is work-in-progress. 474 They usually appear either visually highlighted, at the end of the 475 document (depending on file format and settings of the formatter), or 476 not at all (when generating an RFC). 478 This element appears as child element of: <annotation> (Section 2.3), 479 <c> (Section 2.8), <postamble> (Section 2.28), <preamble> 480 (Section 2.29), and <t> (Section 2.38). 482 Content model: only text content. 484 2.12.1. 'anchor' attribute 486 [[element.cref.attribute.anchor.missing: attribute description 487 missing]] 489 2.12.2. 'source' attribute 491 Holds the "source" of a comment, such as the name or the initials of 492 the person who made the comment. 494 2.13. <date> 496 Provides information about the publication date. 498 Note that this element is used both for the boilerplate of the 499 document being produced, and also inside bibliographic references. 501 In the first case, it defines the publication date, which, when 502 producing Internet-Drafts, will be used for computing the expiration 503 date (see Section 8 of [IDGUIDE]). When "year", "month" or "day" are 504 left out, the processor will attempt to use the current system date 505 if the attributes that are specified do match the system date. 507 Note that month names need to match the full (English) month name 508 ("January", "February", "March", "April", "May, "June", "July", 509 "August", "September", "October", "November", or "December") in order 510 for expiration calculations to work (some implementations might 511 support additional formats, though). 513 In the second case, the date information will be embedded as-is into 514 the reference text. Therefore, also vague dates ("ca. 2000"), date 515 ranges, and so on, are allowed. 517 This element appears as child element of: <front> (Section 2.19). 519 Content model: this element does not have any contents. 521 2.13.1. 'day' attribute 523 Day of publication. 525 2.13.2. 'month' attribute 527 Month of publication. 529 2.13.3. 'year' attribute 531 Year of publication. 533 2.14. <email> 535 Provides an email address. 537 The value is expected to be the scheme-specific part of a "mailto" 538 URI (so does not include the prefix "mailto:"). See Section 2 of 539 [RFC6068] for details. 541 This element appears as child element of: <address> (Section 2.2). 543 Content model: only text content. 545 2.15. <eref> 547 Represents an "external" link (as specified in the "target" 548 attribute). 550 If the element has text content, that content will be used. 551 Otherwise, the value of the target attribute will be inserted in 552 angle brackets ([RFC3986], Appendix C). 554 This element appears as child element of: <annotation> (Section 2.3), 555 <c> (Section 2.8), <postamble> (Section 2.28), <preamble> 556 (Section 2.29), and <t> (Section 2.38). 558 Content model: only text content. 560 2.15.1. 'target' attribute (mandatory) 562 URI of the link target (see Section 3 of [RFC3986]). 564 2.16. <facsimile> 566 Represents the phone number of a fax machine. 568 The value is expected to be the scheme-specific part of a "tel" URI 569 (so does not include the prefix "tel:"), using the "global numbers" 570 syntax. See Section 3 of [RFC3966] for details. 572 This element appears as child element of: <address> (Section 2.2). 574 Content model: only text content. 576 2.17. <figure> 578 [[element.figure.missing: element description missing]] 580 This element appears as child element of: <section> (Section 2.34), 581 and <t> (Section 2.38). 583 Content model: 585 In this order: 587 1. Optional <iref> elements (Section 2.20) 589 2. One optional <preamble> element (Section 2.29) 591 3. One <artwork> element (Section 2.5) 593 4. One optional <postamble> element (Section 2.28) 595 2.17.1. 'align' attribute 597 Used to change the alignment of <preamble> and <postamble>. 599 Note: does not affect title or <artwork> alignment. 601 Allowed values: 603 o "left" (default) 605 o "center" 606 o "right" 608 2.17.2. 'alt' attribute 610 Duplicates functionality available on <artwork>; avoid it. 612 2.17.3. 'anchor' attribute 614 [[element.figure.attribute.anchor.missing: attribute description 615 missing]] 617 2.17.4. 'height' attribute 619 Duplicates functionality available on <artwork>; avoid it. 621 2.17.5. 'src' attribute 623 Duplicates functionality available on <artwork>; avoid it. 625 2.17.6. 'suppress-title' attribute 627 Figures that have an "anchor" attribute will automatically get an 628 autogenerated title (such as "Figure 1"). Setting this attribute to 629 "false" will prevent this. 631 Allowed values: 633 o "true" 635 o "false" (default) 637 2.17.7. 'title' attribute 639 [[element.figure.attribute.title.missing: attribute description 640 missing]] 642 2.17.8. 'width' attribute 644 Duplicates functionality available on <artwork>; avoid it. 646 2.18. <format> 648 Provides a link to an additional format variant for a reference. 650 Note that these additional links are neither used in published RFCs, 651 nor supported by all tools. If the goal is to provide a single URI 652 for a reference, the "target" attribute on <reference> can be used 653 instead. 655 This element appears as child element of: <reference> (Section 2.30). 657 Content model: this element does not have any contents. 659 2.18.1. 'octets' attribute 661 Octet length of linked-to document. 663 2.18.2. 'target' attribute 665 URI of document. 667 [[anchor3: Why is this optional?]] 669 2.18.3. 'type' attribute (mandatory) 671 The type of the linked-to document, such as "TXT", "HTML", or "PDF". 673 2.19. <front> 675 Represent the "front matter": metadata (such as author information), 676 abstract, and additional notes. 678 This element appears as child element of: <reference> (Section 2.30), 679 and <rfc> (Section 2.33). 681 Content model: 683 In this order: 685 1. One <title> element (Section 2.40) 687 2. One or more <author> elements (Section 2.6) 689 3. One <date> element (Section 2.13) 691 4. Optional <area> elements (Section 2.4) 693 5. Optional <workgroup> elements (Section 2.44) 695 6. Optional <keyword> elements (Section 2.21) 697 7. One optional <abstract> element (Section 2.1) 699 8. Optional <note> elements (Section 2.24) 701 2.20. <iref> 703 Provides terms for the document's index. 705 Index entries can be either single items (when just the "item" 706 attribute is given) or nested items (by specifying "subitem" as 707 well). 709 For instance: 711 <iref item="Grammar" subitem="item"/> 713 will produce an index entry for "Grammar, item". 715 This element appears as child element of: <annotation> (Section 2.3), 716 <c> (Section 2.8), <figure> (Section 2.17), <postamble> 717 (Section 2.28), <preamble> (Section 2.29), <section> (Section 2.34), 718 and <t> (Section 2.38). 720 Content model: this element does not have any contents. 722 2.20.1. 'item' attribute (mandatory) 724 The item to include. 726 2.20.2. 'primary' attribute 728 Setting this to "true" declares the occurrence as "primary", which 729 might cause it to be highlighted in the index. 731 Allowed values: 733 o "true" 735 o "false" (default) 737 2.20.3. 'subitem' attribute 739 The subitem to include. 741 2.21. <keyword> 743 Specifies a keyword applicable to the document. 745 Note that each element should only contain a single keyword; for 746 multiple keywords, the element can simply be repeated. 748 Keywords are used both in the RFC Index and in the metadata of 749 generated document formats. 751 This element appears as child element of: <front> (Section 2.19). 753 Content model: only text content. 755 2.22. <list> 757 Delineates a text list. 759 Each list item is represented by a <t> element. The vocabulary 760 currently does not directly support list items consisting of multiple 761 paragraphs; if this is needed, <vspace> (Section 2.43) can be used as 762 workaround. 764 This element appears as child element of: <t> (Section 2.38). 766 Content model: 768 One or more <t> elements (Section 2.38) 770 2.22.1. 'counter' attribute 772 This attribute holds a token that serves as an identifier for a 773 counter. The intended use is continuation of lists. 775 Note that this attribute functions only when the style attribute is 776 using the "format..." syntax (Section 2.22.3); otherwise, it is 777 ignored. 779 2.22.2. 'hangIndent' attribute 781 For list styles with potentially wide labels, this attribute can 782 override the default indentation level, measured in characters. 784 Note that it only affects style with variable-width labels 785 ("format..." and "hanging", see below), and it may not affect formats 786 in which the list item text appears _below_ the label. 788 2.22.3. 'style' attribute 790 This attribute is used to control the display of a list. 792 The value of this attribute is inherited by any nested lists that do 793 not have this attribute set. It may be set to: 795 "empty" (or not set) 796 For unlabeled list items; it can also be used for indentation 797 purposes (this is the default value). 799 "hanging" 801 For lists where the items are labeled with a piece of text. 803 The label text is specified in the 'hangText' attribute of the <t> 804 element (Section 2.38.2). 806 "letters" 808 For ordered lists using letters as labels (lowercase letters 809 followed by a period; after "z", it rolls over to a two-letter 810 format). For nested lists, processors usually flip between 811 uppercase and lowercase. 813 "numbers" 815 For ordered lists using numbers as labels. 817 "symbols" 819 For unordered (bulleted) lists. 821 The style of the bullets is chosen automatically be the processor 822 (some implementations allow overriding the default using a 823 processing instruction). 825 And, finally: 827 "format ..." 829 For lists with customized labels, consisting of fixed text and an 830 item counter in various formats. 832 The value is a free-form text that allows counter values to be 833 inserted using a "percent-letter" format. For instance, "[REQ%d]" 834 generates labels of the form "[REQ1]", where "%d" inserts the item 835 number as decimal number. 837 The following formats are supported: 839 %c lowercase letters (a, b, c, etc.) 840 %C uppercase letters (A, B, C, etc.) 842 %d decimal numbers (1, 2, 3, etc.) 844 %i lowercase Roman numerals (i, ii, iii, etc.) 846 %I uppercase Roman numerals (I, II, III, etc.) 848 %% represents a percent sign 850 Other formats are reserved for future use. 852 2.23. <middle> 854 Represents the main content of the document. 856 This element appears as child element of: <rfc> (Section 2.33). 858 Content model: 860 One or more <section> elements (Section 2.34) 862 2.24. <note> 864 Creates an unnumbered section that appears after the abstract. 866 It is usually used for additional information to reviewers (working 867 group information, mailing list, ...), or for additional publication 868 information such as "IESG Notes". 870 This element appears as child element of: <front> (Section 2.19). 872 Content model: 874 One or more <t> elements (Section 2.38) 876 2.24.1. 'title' attribute (mandatory) 878 The title of the note. 880 2.25. <organization> 882 Specifies the affiliation of an author. 884 This information appears in both the "Author's Address" section and 885 on the front page ([RFCSTYLE], Section 4.1.2). If the value is long, 886 an abbreviated variant can be specified in the "abbrev" attribute. 888 This element appears as child element of: <author> (Section 2.6). 890 Content model: only text content. 892 2.25.1. 'abbrev' attribute 894 Abbreviated variant. 896 2.26. <phone> 898 Represents a phone number. 900 The value is expected to be the scheme-specific part of a "tel" URI 901 (so does not include the prefix "tel:"), using the "global numbers" 902 syntax. See Section 3 of [RFC3966] for details. 904 This element appears as child element of: <address> (Section 2.2). 906 Content model: only text content. 908 2.27. <postal> 910 Contains child elements providing postal information. 912 This element appears as child element of: <address> (Section 2.2). 914 Content model: 916 In this order: 918 1. One or more <street> elements (Section 2.37) 920 2. In any order: 922 * <city> elements (Section 2.9) 924 * <region> elements (Section 2.32) 926 * <code> elements (Section 2.10) 928 * <country> elements (Section 2.11) 930 2.28. <postamble> 932 Gives text that appears at the bottom of a figure or table. 934 This element appears as child element of: <figure> (Section 2.17), 935 and <texttable> (Section 2.39). 937 Content model: 939 In any order: 941 o Text 943 o <xref> elements (Section 2.45) 945 o <eref> elements (Section 2.15) 947 o <iref> elements (Section 2.20) 949 o <cref> elements (Section 2.12) 951 o <spanx> elements (Section 2.36) 953 2.29. <preamble> 955 Gives text that appears at the top of a figure or table. 957 This element appears as child element of: <figure> (Section 2.17), 958 and <texttable> (Section 2.39). 960 Content model: 962 In any order: 964 o Text 966 o <xref> elements (Section 2.45) 968 o <eref> elements (Section 2.15) 970 o <iref> elements (Section 2.20) 972 o <cref> elements (Section 2.12) 974 o <spanx> elements (Section 2.36) 976 2.30. <reference> 978 Represents a bibliographical reference. 980 This element appears as child element of: <references> 981 (Section 2.31). 983 Content model: 985 In this order: 987 1. One <front> element (Section 2.19) 989 2. Optional <seriesInfo> elements (Section 2.35) 991 3. Optional <format> elements (Section 2.18) 993 4. Optional <annotation> elements (Section 2.3) 995 2.30.1. 'anchor' attribute 997 [[element.reference.attribute.anchor.missing: attribute description 998 missing]] 1000 2.30.2. 'target' attribute 1002 Holds the URI for the reference. 1004 Note that depending on the <seriesInfo> element, a URI might not be 1005 needed, nor desirable, as it can be automatically generated (for 1006 instance, for RFCs). 1008 2.31. <references> 1010 Contains a set of bibliographical references. 1012 In the early days of the RFC series, there was only one "References" 1013 section per RFC. This convention was later changed to group 1014 references into two sets, "Normative" and "Informative"; see item x 1015 of Section 4.8 of [RFCSTYLE]). This vocabulary supports the split 1016 with the "title" attribute. 1018 This element appears as child element of: <back> (Section 2.7). 1020 Content model: 1022 One or more <reference> elements (Section 2.30) 1024 2.31.1. 'title' attribute 1026 Provides the title for the References section (defaulting to 1027 "References"). 1029 In general, the title should be either "Normative References" or 1030 "Informative References". 1032 2.32. <region> 1034 Provides the region name in a postal address. 1036 This element appears as child element of: <postal> (Section 2.27). 1038 Content model: only text content. 1040 2.33. <rfc> 1042 This is the root element of the xml2rfc vocabulary. 1044 Processors distinguish between RFC mode ("number" attribute being 1045 present) and Internet-Draft mode ("docName" attribute being present): 1046 it is invalid to specify both. Setting neither "number" nor 1047 "docName" can be useful for producing other types of document but is 1048 out-of-scope for this specification. 1050 Content model: 1052 In this order: 1054 1. One <front> element (Section 2.19) 1056 2. One <middle> element (Section 2.23) 1058 3. One optional <back> element (Section 2.7) 1060 2.33.1. 'category' attribute 1062 Document category (see Appendix A.1). 1064 Allowed values: 1066 o "std" 1068 o "bcp" 1070 o "info" 1071 o "exp" 1073 o "historic" 1075 2.33.2. 'consensus' attribute 1077 Affects the generated boilerplate. 1079 See [RFC5741] for more information. 1081 Allowed values: 1083 o "no" 1085 o "yes" 1087 2.33.3. 'docName' attribute 1089 For Internet-Drafts, this specifies the draft name (which appears 1090 below the title). 1092 Note that the file extension is not part of the draft, so in general 1093 it should end with the current draft number ("-", plus two digits). 1095 Furthermore, it is good practice to disambiguate current editor 1096 copies from submitted drafts (for instance, by replacing the draft 1097 number with the string "latest"). 1099 See Section 7 of [IDGUIDE] for further information. 1101 2.33.4. 'ipr' attribute 1103 Represents the Intellectual Property status of the document. See 1104 Appendix A.2 for details. 1106 Allowed values: 1108 o "full2026" 1110 o "noDerivativeWorks2026" 1112 o "none" 1114 o "full3667" 1116 o "noModification3667" 1117 o "noDerivatives3667" 1119 o "full3978" 1121 o "noModification3978" 1123 o "noDerivatives3978" 1125 o "trust200811" 1127 o "noModificationTrust200811" 1129 o "noDerivativesTrust200811" 1131 o "trust200902" 1133 o "noModificationTrust200902" 1135 o "noDerivativesTrust200902" 1137 o "pre5378Trust200902" 1139 2.33.5. 'iprExtract' attribute 1141 Identifies a Section within the document for which extraction "as-is" 1142 is explicitly allowed (only relevant for historic values of the "ipr" 1143 attribute). 1145 2.33.6. 'number' attribute 1147 The number of the RFC to be produced. 1149 2.33.7. 'obsoletes' attribute 1151 A comma-separated list of RFC _numbers_ or Internet-Draft names. 1153 2.33.8. 'seriesNo' attribute 1155 When producing a document within document series (such as "STD"): the 1156 number within that series. 1158 2.33.9. 'submissionType' attribute 1160 The document stream. 1162 See Section 2 of [RFC5741] for details. 1164 Allowed values: 1166 o "IETF" (default) 1168 o "IAB" 1170 o "IRTF" 1172 o "independent" 1174 2.33.10. 'updates' attribute 1176 A comma-separated list of RFC _numbers_ or Internet-Draft names. 1178 2.33.11. 'xml:lang' attribute 1180 The natural language used in the document (defaults to "en"). 1182 See Section 2.12 of [XML] for more information. 1184 2.34. <section> 1186 Represents a section (when inside a <middle> element) or an appendix 1187 (when inside a <back> element). 1189 Sub-sections are created by nesting <section> elements inside 1190 <section> elements. 1192 This element appears as child element of: <back> (Section 2.7), 1193 <middle> (Section 2.23), and <section> (Section 2.34). 1195 Content model: 1197 In this order: 1199 1. In any order: 1201 * <t> elements (Section 2.38) 1203 * <figure> elements (Section 2.17) 1205 * <texttable> elements (Section 2.39) 1207 * <iref> elements (Section 2.20) 1209 2. Optional <section> elements (Section 2.34) 1211 2.34.1. 'anchor' attribute 1213 [[element.section.attribute.anchor.missing: attribute description 1214 missing]] 1216 2.34.2. 'title' attribute (mandatory) 1218 The title of the section. 1220 2.34.3. 'toc' attribute 1222 Determines whether the section is included in the Table Of Contents. 1224 [[anchor4: Need to consider inheritance.]] 1226 Allowed values: 1228 o "include" 1230 o "exclude" 1232 o "default" (default) 1234 2.35. <seriesInfo> 1236 Specifies the document series in which this document appears, and 1237 also specifies an identifier within that series. 1239 This element appears as child element of: <reference> (Section 2.30). 1241 Content model: this element does not have any contents. 1243 2.35.1. 'name' attribute (mandatory) 1245 The name of the series. 1247 The following names trigger specific processing (such as for auto- 1248 generating links, and adding descriptions such as "work in 1249 progress"): "BCP", "FYI", "Internet-Draft", "RFC", and "STD". 1251 2.35.2. 'value' attribute (mandatory) 1253 The identifier within the series specified by the "name" attribute. 1255 For BCPs, FYIs, RFCs, and STDs this is the number within the series. 1256 For Internet-Drafts, it is the full draft name (ending with the two- 1257 digit version number). 1259 2.36. <spanx> 1261 Wraps a piece of text, indicating special formatting styles. 1263 When generating plain text, processors usually emulate font changes 1264 using characters such as "*" and "_". 1266 The following styles are defined: 1268 emph Simple emphasis (this is the default). 1270 strong Strong emphasis. 1272 verb "Verbatim" text (usually displayed usign a monospaced font 1273 face). 1275 This element appears as child element of: <annotation> (Section 2.3), 1276 <c> (Section 2.8), <postamble> (Section 2.28), <preamble> 1277 (Section 2.29), and <t> (Section 2.38). 1279 Content model: only text content. 1281 2.36.1. 'style' attribute 1283 The style to be used (defaults to "emph"). 1285 2.36.2. 'xml:space' attribute 1287 Determines whitespace handling. 1289 According to the DTD, the default value is "preserve". Tests however 1290 show that it doesn't have any effect on processing; thus this 1291 attribute will be removed in future versions of the vocabulary. 1293 See also Section 2.10 of [XML]. 1295 Allowed values: 1297 o "default" 1299 o "preserve" (default) 1301 2.37. <street> 1303 Provides a street address. 1305 This element appears as child element of: <postal> (Section 2.27). 1307 Content model: only text content. 1309 2.38. <t> 1311 Contains a paragraph of text. 1313 This element appears as child element of: <abstract> (Section 2.1), 1314 <list> (Section 2.22), <note> (Section 2.24), and <section> 1315 (Section 2.34). 1317 Content model: 1319 In any order: 1321 o Text 1323 o <list> elements (Section 2.22) 1325 o <figure> elements (Section 2.17) 1327 o <xref> elements (Section 2.45) 1329 o <eref> elements (Section 2.15) 1331 o <iref> elements (Section 2.20) 1333 o <cref> elements (Section 2.12) 1335 o <spanx> elements (Section 2.36) 1337 o <vspace> elements (Section 2.43) 1339 2.38.1. 'anchor' attribute 1341 [[element.t.attribute.anchor.missing: attribute description missing]] 1343 2.38.2. 'hangText' attribute 1345 [[element.t.attribute.hangText.missing: attribute description 1346 missing]] 1348 2.39. <texttable> 1350 Contains a table, consisting of an optional preamble, a header line, 1351 rows, and an optional postamble. 1353 The number of columns in the table is determined by the number of 1354 <ttcol> elements. The number of rows in the table is determined by 1355 the number of <c> elements divided by the number of columns. There 1356 is no requirement that the number of <c> elements be evenly divisible 1357 by the number of columns. 1359 This element appears as child element of: <section> (Section 2.34). 1361 Content model: 1363 In this order: 1365 1. One optional <preamble> element (Section 2.29) 1367 2. One or more <ttcol> elements (Section 2.41) 1369 3. Optional <c> elements (Section 2.8) 1371 4. One optional <postamble> element (Section 2.28) 1373 2.39.1. 'align' attribute 1375 Determines the horizontal alignment of the table. 1377 Allowed values: 1379 o "left" 1381 o "center" (default) 1383 o "right" 1385 2.39.2. 'anchor' attribute 1387 [[element.texttable.attribute.anchor.missing: attribute description 1388 missing]] 1390 2.39.3. 'style' attribute 1392 [[element.texttable.attribute.style.missing: attribute description 1393 missing]] 1395 Allowed values: 1397 o "all" 1399 o "none" 1401 o "headers" 1402 o "full" (default) 1404 2.39.4. 'suppress-title' attribute 1406 [[element.texttable.attribute.suppress-title.missing: attribute 1407 description missing]] 1409 Allowed values: 1411 o "true" 1413 o "false" (default) 1415 2.39.5. 'title' attribute 1417 [[element.texttable.attribute.title.missing: attribute description 1418 missing]] 1420 2.40. <title> 1422 Represents the document title. 1424 When this element appears in the <front> element of the current 1425 document, the title might also appear in page headers or footers. If 1426 it's long (~40 characters), the "abbrev" attribute is used to 1427 specified an abbreviated variant. 1429 This element appears as child element of: <front> (Section 2.19). 1431 Content model: only text content. 1433 2.40.1. 'abbrev' attribute 1435 Specifies an abbreviated variant of the document title. 1437 2.41. <ttcol> 1439 Contains a column heading in a table. 1441 This element appears as child element of: <texttable> (Section 2.39). 1443 Content model: only text content. 1445 2.41.1. 'align' attribute 1447 Determines the horizontal alignment within the table column. 1449 Allowed values: 1451 o "left" (default) 1453 o "center" 1455 o "right" 1457 2.41.2. 'width' attribute 1459 [[element.ttcol.attribute.width.missing: attribute description 1460 missing]] 1462 2.42. <uri> 1464 Contains a web address associated with the author. 1466 The contents should be a valid URI (see Section 3 of [RFC3986]). 1468 This element appears as child element of: <address> (Section 2.2). 1470 Content model: only text content. 1472 2.43. <vspace> 1474 [[element.vspace.missing: element description missing]] 1476 This element appears as child element of: <t> (Section 2.38). 1478 Content model: this element does not have any contents. 1480 2.43.1. 'blankLines' attribute 1482 [[element.vspace.attribute.blankLines.missing: attribute description 1483 missing]] 1485 2.44. <workgroup> 1487 This element is used to specify the Working Group the document 1488 originates from, if any. The recommended format is the official name 1489 of the Working Group (with some capitalization). 1491 In Internet-Drafts, this is used in the upper left corner of the 1492 boilerplate, replacing the "Network Working Group" string. 1493 Formatting software can append the words "Working Group" or "Research 1494 Group", depending on the "submissionType" property on the <rfc> 1495 element (Section 2.33.9). 1497 This element appears as child element of: <front> (Section 2.19). 1499 Content model: only text content. 1501 2.45. <xref> 1503 [[element.xref.missing: element description missing]] 1505 This element appears as child element of: <annotation> (Section 2.3), 1506 <c> (Section 2.8), <postamble> (Section 2.28), <preamble> 1507 (Section 2.29), and <t> (Section 2.38). 1509 Content model: only text content. 1511 2.45.1. 'format' attribute 1513 [[element.xref.attribute.format.missing: attribute description 1514 missing]] 1516 Allowed values: 1518 o "counter" 1520 o "title" 1522 o "none" 1524 o "default" (default) 1526 2.45.2. 'pageno' attribute 1528 Unused. 1530 It's unclear what the purpose of this attribute is; processors seem 1531 to ignore it and it never was documented. 1533 Allowed values: 1535 o "true" 1537 o "false" (default) 1539 2.45.3. 'target' attribute (mandatory) 1541 [[element.xref.attribute.target.missing: attribute description 1542 missing]] 1544 3. Special Unicode Code Points 1546 [[anchor5: Explain those code points where the processors implement 1547 something special, such as "nbsp".]] 1549 4. Internationalization Considerations 1551 This format is based on [XML], thus does not have any issues 1552 representing arbitrary Unicode [UNICODE] characters in text content. 1554 However, the current canonical RFC format is restricted to US-ASCII 1555 [USASCII] characters (see Section 3.1 of [RFCSTYLE]). Future 1556 versions are likely to relax this role, and it is expected that the 1557 vocabulary will be extended so that US-ACSII alternatives can be 1558 provided when that makes sense (for instance, in contact 1559 information). 1561 5. Security Considerations 1563 [[anchor6: This section is likely incomplete.]] 1565 The "name" attribute on the <artwork> element (Section 2.5.4) can be 1566 used to derive a filename for saving to a local file system. 1567 Trusting this kind of information without pre-processing is a known 1568 security risk; see Section 4.3 of [RFC6266] for more information. 1570 Furthermore, all security considerations related to XML processing 1571 are relevant as well (see Section 7 of [RFC3470]). 1573 6. IANA Considerations 1575 6.1. Internet Media Type Registration 1577 IANA maintains the registry of Internet media types [BCP13] at 1578 <http://www.iana.org/assignments/media-types>. 1580 This document serves as the specification for the Internet media type 1581 "application/rfc+xml". The following is to be registered with IANA. 1583 Type name: application 1585 Subtype name: rfc+xml 1587 Required parameters: There are no required parameters. 1589 Optional parameters: "charset": This parameter has identical 1590 semantics as the charset parameter of the "application/xml" media 1591 type specified in [RFC3023]. 1593 Encoding considerations: Identical to those of "application/xml" as 1594 described in Section 3.2 of [RFC3023]. 1596 Security considerations: As defined in Section 5. In addition, as 1597 this media type uses the "+xml" convention, it inherits the 1598 security considerations described in Section 10 of [RFC3023]. 1600 Interoperability considerations: N/A 1602 Published specification: This specification. 1604 Applications that use this media type: Applications that either 1605 transform xml2rfc to output formats such as plain text or HTML, 1606 plus additional analysis tools. 1608 Fragment identifier considerations: The "anchor" attribute is used 1609 for assigning document-wide unique identifiers that can be uses as 1610 shorthand pointers, as described in Section 2.8 of [XPOINTER]. 1612 Additional information: 1614 Deprecated alias names for this type: None. 1616 Magic number(s): As specified for "application/xml" in Section 1617 3.2 of [RFC3023]. 1619 File extension(s): .xml 1621 Macintosh file type code(s): TEXT 1623 Person & email address to contact for further information: See 1624 Authors Section. 1626 Intended usage: COMMON 1628 Restrictions on usage: N/A 1630 Author: See Authors Section. 1632 Change controller: RFC Series Editor (rse@rfc-editor.org) 1634 7. Acknowledgments 1636 Thanks to everybody who reviewed this document and provided feedback 1637 and/or specification text, in particular Brian Carpenter, Tony 1638 Hansen, Paul Hoffman, Henrik Levkowetz, Alice Russo, Jim Schaad, and 1639 Nico Williams. 1641 We also thank Marshall T. Rose for both the original design and the 1642 reference implementation of the "xml2rfc" formatter. 1644 8. References 1646 8.1. Normative References 1648 [XML] Maler, E., Yergeau, F., Paoli, J., Sperberg-McQueen, M., 1649 and T. Bray, "Extensible Markup Language (XML) 1.0 1650 (Fifth Edition)", W3C Recommendation REC-xml-20081126, 1651 November 2008, 1652 <http://www.w3.org/TR/2008/REC-xml-20081126/>. 1654 Latest version available at <http://www.w3.org/TR/xml>. 1656 8.2. Informative References 1658 [BCP13] Freed, N., Klensin, J., and T. Hansen, "Media Type 1659 Specifications and Registration Procedures", BCP 13, 1660 RFC 6838, January 2013. 1662 [IDGUIDE] Housley, R., "Guidelines to Authors of Internet-Drafts", 1663 December 2010, 1664 <http://www.ietf.org/id-info/guidelines.html>. 1666 [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 1667 3", BCP 9, RFC 2026, October 1996. 1669 [RFC2046] Freed, N. and N. Borenstein, "Multipurpose Internet Mail 1670 Extensions (MIME) Part Two: Media Types", RFC 2046, 1671 November 1996. 1673 [RFC2397] Masinter, L., "The "data" URL scheme", RFC 2397, 1674 August 1998. 1676 [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, 1677 June 1999. 1679 [RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media 1680 Types", RFC 3023, January 2001. 1682 [RFC3470] Hollenbeck, S., Rose, M., and L. Masinter, "Guidelines 1683 for the Use of Extensible Markup Language (XML) within 1684 IETF Protocols", BCP 70, RFC 3470, January 2003. 1686 [RFC3966] Schulzrinne, H., "The tel URI for Telephone Numbers", 1687 RFC 3966, December 2004. 1689 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 1690 Resource Identifier (URI): Generic Syntax", STD 66, 1691 RFC 3986, January 2005. 1693 [RFC5598] Crocker, D., "Internet Mail Architecture", RFC 5598, 1694 July 2009. 1696 PDF version: <http://www.rfc-editor.org/rfc/rfc5598.pdf> 1698 [RFC5741] Daigle, L. and O. Kolkman, "RFC Streams, Headers, and 1699 Boilerplates", RFC 5741, December 2009. 1701 [RFC6068] Duerst, M., Masinter, L., and J. Zawinski, "The 'mailto' 1702 URI Scheme", RFC 6068, October 2010. 1704 [RFC6266] Reschke, J., "Use of the Content-Disposition Header 1705 Field in the Hypertext Transfer Protocol (HTTP)", 1706 RFC 6266, June 2011. 1708 [RFCPOLICY] RFC Editor, "RFC Editorial Guidelines and Procedures", 1709 February 2012, <http://www.rfc-editor.org/policy.html>. 1711 [RFCSTYLE] Braden, R., Ginoza, S., and A. Hagens, "RFC Document 1712 Style (draft 09)", September 2009, 1713 <http://www.rfc-editor.org/rfc-style-guide/rfc-style>. 1715 [RNC] Clark, J., "RELAX NG Compact Syntax", OASIS , 1716 November 2002, <http://www.oasis-open.org/committees/ 1717 relax-ng/compact-20021121.html>. 1719 [TLP2.0] IETF Trust, "Legal Provisions Relating to IETF 1720 Documents", February 2009, 1721 <http://trustee.ietf.org/license-info/IETF-TLP-2.htm>. 1723 [TLP3.0] IETF Trust, "Legal Provisions Relating to IETF 1724 Documents", September 2009, 1725 <http://trustee.ietf.org/license-info/IETF-TLP-3.htm>. 1727 [TLP4.0] IETF Trust, "Legal Provisions Relating to IETF 1728 Documents", December 2009, 1729 <http://trustee.ietf.org/license-info/IETF-TLP-4.htm>. 1731 [UNICODE] The Unicode Consortium, "The Unicode Standard, Version 1732 6.3.0", September 2013, 1733 <http://www.unicode.org/versions/Unicode6.3.0/>. 1735 [USASCII] American National Standards Institute, "Coded Character 1736 Set -- 7-bit American Standard Code for Information 1737 Interchange", ANSI X3.4, 1986. 1739 [XPOINTER] Grosso, P., Maler, E., Marsh, J., and N. Walsh, 1740 "XPointer Framework", W3C Recommendation REC-xptr- 1741 framework-20030325, March 2003, 1742 <http://www.w3.org/TR/2003/ 1743 REC-xptr-framework-20030325/>. 1745 Latest version available at 1746 <http://www.w3.org/TR/xptr-framework/>. 1748 Appendix A. Front Page Generation 1750 A.1. The /rfc/@category Attribute 1752 For RFCs, the "category" determines the "maturity level" (see Section 1753 4 of [RFC2026]). The allowed values are "std" for "Standards Track", 1754 "bcp" for "BCP", "info" for "Informational", "exp" for 1755 "Experimental", and "historic" for - surprise - "Historic". 1757 For Internet-Drafts, the category attribute is not needed, but will 1758 appear on the front page as "Intended Status". Supplying this 1759 information can be useful to reviewers. 1761 A.2. The /rfc/@ipr Attribute 1763 This attribute value can take a long list of values, each of which 1764 describes an IPR policy for the document. This attribute's values 1765 are not the result of a grand plan, but remain simply for historic 1766 reasons. Of these values, only a few are currently in use; all 1767 others are supported by the various tools for backwards compatibility 1768 with old source files. 1770 Note: some variations of the boilerplate are selected based on the 1771 document's date; therefore it is important to specify the "year", 1772 "month" and "day" attributes of the "<date>" element when 1773 archiving the XML source of an Internet-Draft on the day of 1774 submission. 1776 _Disclaimer: THIS ONLY PROVIDES IMPLEMENTATION INFORMATION. IF YOU 1777 NEED LEGAL ADVICE, PLEASE CONTACT A LAWYER._ For further information, 1778 refer to <http://trustee.ietf.org/docs/IETF-Copyright-FAQ.pdf>. 1780 For the current "Status Of This Memo" text, the "submissionType" 1781 attribute determines whether a statement about "Code Components" is 1782 inserted (which is the case for the value "IETF", which is the 1783 default). Other values, such as "independent", suppress this part of 1784 the text. 1786 A.2.1. Current Values: '*trust200902' 1788 The name for these values refers to the "IETF TRUST Legal Provisions 1789 Relating to IETF Documents", sometimes simply called the "TLP, that 1790 went into effect on February 15, 2009 ([TLP2.0]). Updates to this 1791 document were published on September 12, 2009 ([TLP3.0]) and on 1792 December 28, 2009 ([TLP4.0]), modifying the license for code 1793 components (see <http://trustee.ietf.org/license-info/> for further 1794 information). The actual text is located in Section 6 ("Text To Be 1795 Included in IETF Documents") of these documents. 1797 The tools will automatically produce the "correct" text depending on 1798 the document's date information (see above): 1800 +----------+--------------------------------+ 1801 | TLP | starting with publication date | 1802 +----------+--------------------------------+ 1803 | [TLP3.0] | 2009-11-01 | 1804 | [TLP4.0] | 2010-04-01 | 1805 +----------+--------------------------------+ 1807 A.2.1.1. trust200902 1809 This should be the default, unless one of the more specific 1810 '*trust200902' values is a better fit. It produces the text in 1811 Sections 6.a and 6.b of the TLP. 1813 A.2.1.2. noModificationTrust200902 1815 This produces additional text from Section 6.c.i of the TLP: 1817 This document may not be modified, and derivative works of it may 1818 not be created, except to format it for publication as an RFC or 1819 to translate it into languages other than English. 1821 Note: this clause is incompatible with RFCs that are published on 1822 the Standards Track. 1824 A.2.1.3. noDerivativesTrust200902 1826 This produces the additional text from Section 6.c.ii of the TLP: 1828 This document may not be modified, and derivative works of it may 1829 not be created, and it may not be published except as an Internet- 1830 Draft. 1832 Note: this clause is incompatible with RFCs. 1834 A.2.1.4. pre5378Trust200902 1836 This produces the additional text from Section 6.c.iii of the TLP, 1837 frequently called the "pre-5378 escape clause": 1839 This document may contain material from IETF Documents or IETF 1840 Contributions published or made publicly available before November 1841 10, 2008. The person(s) controlling the copyright in some of this 1842 material may not have granted the IETF Trust the right to allow 1843 modifications of such material outside the IETF Standards Process. 1844 Without obtaining an adequate license from the person(s) 1845 controlling the copyright in such materials, this document may not 1846 be modified outside the IETF Standards Process, and derivative 1847 works of it may not be created outside the IETF Standards Process, 1848 except to format it for publication as an RFC or to translate it 1849 into languages other than English. 1851 See Section 4 of 1852 <http://trustee.ietf.org/docs/IETF-Copyright-FAQ.pdf> for further 1853 information about when to use this value. 1855 Note: this text appears under "Copyright Notice", unless the 1856 document was published before November 2009, in which case it 1857 appears under "Status Of This Memo". 1859 A.2.2. Historic Values 1861 A.2.2.1. Historic Values: '*trust200811' 1863 The attribute values "trust200811", "noModificationTrust200811" and 1864 "noDerivativesTrust200811" are similar to their "trust200902" 1865 counterparts, except that they use text specified in <http:// 1866 trustee.ietf.org/license-info/archive/ 1867 IETF-Trust-License-Policy_11-10-08.pdf>. 1869 A.2.2.2. Historic Values: '*3978' 1871 The attribute values "full3978", "noModification3978" and 1872 "noDerivatives3978" are similar to their counterparts above, except 1873 that they use text specified in RFC 3978 (March 2005). 1875 A.2.2.3. Historic Values: '*3667' 1877 The attribute values "full3667", "noModification3667" and 1878 "noDerivatives3667" are similar to their counterparts above, except 1879 that they use text specified in RFC 3667 (February 2004). 1881 A.2.2.4. Historic Values: '*2026' 1883 The attribute values "full2026" and "noDerivativeWorks2026" are 1884 similar to their counterparts above, except that they use text 1885 specified in RFC 2026 (October 1996). 1887 The special value "none" was also used back then, and denied the IETF 1888 any rights beyond publication as Internet-Draft. 1890 Appendix B. Changes from RFC 2629 ('v1') 1892 [[v1diff: See <http://greenbytes.de/tech/webdav/ 1893 draft-reschke-xml2rfc-02.html#rfc.section.E> for a comparison of the 1894 schemata.]] 1896 B.1. Removed Elements 1898 The <appendix> element has been removed; to generate an appendix, 1899 place a <section> inside <back>. 1901 B.2. Changed Defaults 1903 Many attributes have lost their "default" value; this is to avoid 1904 having document semantics differ based on whether a DTD was specified 1905 and evaluated. Processors will handle absent values the way the 1906 default value was specified before. 1908 B.3. Changed Elements 1910 <artwork>: Has a set of new attributes: "name", "type", "src", 1911 "align", "alt", "width", and "height". (Section 2.5) 1913 <author>: The <organization> element is now optional. The "role" 1914 attribute was added. (Section 2.6) 1916 <country>: The requirement to use ISO 3166 codes was removed. 1918 (Section 2.11) 1920 <date>: All attributes are now optional. (Section 2.13) 1922 <figure>: Has a set of new attributes: "suppress-title", "src", 1923 "align", "alt", "width", and "height". (Section 2.17) 1925 <iref>: Has a new "primary" attribute. (Section 2.20) 1927 <list>: The "style" attribute isn't restricted to a set of enumerated 1928 values anymore. The "hangIndent" and "counter" attributes have been 1929 added. (Section 2.22) 1931 <rfc>: The "ipr" attribute has gained additional values. The 1932 attributes "consensus", "iprExtract", "submissionType", and "xml: 1933 lang" have been added. (Section 2.33) 1935 <reference>: <annotation> allows adding prose to a reference. 1936 (Section 2.30) 1938 <references>: Can now appear multiple times, and carry a "title" 1939 attribute (so that normative and informative references can be 1940 split). (Section 2.31) 1942 <section>: The new "toc" attribute controls whether it will appear in 1943 the Table Of Contents. <iref> can now appear as direct child element. 1944 (Section 2.34) 1946 <t>: The "anchor" attribute can now be used as well, however there 1947 are restrictions on how they can be referred to. (Section 2.38) 1949 B.4. New Elements 1951 The following elements have been added: <annotation> (Section 2.3), 1952 <c> (Section 2.8), <cref> (Section 2.12), <format> (Section 2.18), 1953 <spanx> (Section 2.36), <texttable> (Section 2.39). 1955 Appendix C. Relax NG Schema 1957 namespace a = "http://relaxng.org/ns/compatibility/annotations/1.0" 1959 rfc = 1960 element rfc { 1961 attribute number { text }?, 1962 [ a:defaultValue = "" ] attribute obsoletes { text }?, 1963 [ a:defaultValue = "" ] attribute updates { text }?, 1964 attribute category { "std" | "bcp" | "info" | "exp" | "historic" 1966 }?, 1967 attribute consensus { "no" | "yes" }?, 1968 attribute seriesNo { text }?, 1969 attribute ipr { 1970 "full2026" 1971 | "noDerivativeWorks2026" 1972 | "none" 1973 | "full3667" 1974 | "noModification3667" 1975 | "noDerivatives3667" 1976 | "full3978" 1977 | "noModification3978" 1978 | "noDerivatives3978" 1979 | "trust200811" 1980 | "noModificationTrust200811" 1981 | "noDerivativesTrust200811" 1982 | "trust200902" 1983 | "noModificationTrust200902" 1984 | "noDerivativesTrust200902" 1985 | "pre5378Trust200902" 1986 }?, 1987 attribute iprExtract { xsd:IDREF }?, 1988 [ a:defaultValue = "IETF" ] 1989 attribute submissionType { 1990 "IETF" | "IAB" | "IRTF" | "independent" 1991 }?, 1992 attribute docName { text }?, 1993 [ a:defaultValue = "en" ] attribute xml:lang { text }?, 1994 front, 1995 middle, 1996 back? 1997 } 1998 front = 1999 element front { 2000 title, author+, date, area*, workgroup*, keyword*, abstract?, 2001 note* 2002 } 2003 title = 2004 element title { 2005 attribute abbrev { text }?, 2006 text 2007 } 2008 author = 2009 element author { 2010 attribute initials { text }?, 2011 attribute surname { text }?, 2012 attribute fullname { text }?, 2013 attribute role { "editor" }?, 2014 organization?, 2015 address? 2016 } 2017 organization = 2018 element organization { 2019 attribute abbrev { text }?, 2020 text 2021 } 2022 address = element address { postal?, phone?, facsimile?, email?, 2023 uri? } 2024 postal = element postal { street+, (city | region | code | country)* 2025 } 2026 street = element street { text } 2027 city = element city { text } 2028 region = element region { text } 2029 code = element code { text } 2030 country = element country { text } 2031 phone = element phone { text } 2032 facsimile = element facsimile { text } 2033 email = element email { text } 2034 uri = element uri { text } 2035 date = 2036 element date { 2037 attribute day { text }?, 2038 attribute month { text }?, 2039 attribute year { text }?, 2040 empty 2041 } 2042 area = element area { text } 2043 workgroup = element workgroup { text } 2044 keyword = element keyword { text } 2045 abstract = element abstract { t+ } 2046 note = 2047 element note { 2048 attribute title { text }, 2049 t+ 2050 } 2051 middle = element middle { section+ } 2052 section = 2053 element section { 2054 attribute anchor { xsd:ID }?, 2055 attribute title { text }, 2056 [ a:defaultValue = "default" ] 2057 attribute toc { "include" | "exclude" | "default" }?, 2058 (t | figure | texttable | iref)*, 2059 section* 2060 } 2061 t = 2062 element t { 2063 attribute anchor { xsd:ID }?, 2064 attribute hangText { text }?, 2065 (text 2066 | \list 2067 | figure 2068 | xref 2069 | eref 2070 | iref 2071 | cref 2072 | spanx 2073 | vspace)* 2074 } 2075 \list = 2076 element list { 2077 attribute style { text }?, 2078 attribute hangIndent { text }?, 2079 attribute counter { text }?, 2080 t+ 2081 } 2082 xref = 2083 element xref { 2084 attribute target { xsd:IDREF }, 2085 [ a:defaultValue = "false" ] attribute pageno { "true" | "false" 2086 }?, 2087 [ a:defaultValue = "default" ] 2088 attribute format { "counter" | "title" | "none" | "default" }?, 2089 text 2090 } 2091 eref = 2092 element eref { 2093 attribute target { text }, 2094 text 2095 } 2096 iref = 2097 element iref { 2098 attribute item { text }, 2099 [ a:defaultValue = "" ] attribute subitem { text }?, 2100 [ a:defaultValue = "false" ] 2101 attribute primary { "true" | "false" }?, 2102 empty 2103 } 2104 cref = 2105 element cref { 2106 attribute anchor { xsd:ID }?, 2107 attribute source { text }?, 2108 text 2109 } 2111 spanx = 2112 element spanx { 2113 [ a:defaultValue = "preserve" ] 2114 attribute xml:space { "default" | "preserve" }?, 2115 [ a:defaultValue = "emph" ] attribute style { text }?, 2116 text 2117 } 2118 vspace = 2119 element vspace { 2120 [ a:defaultValue = "0" ] attribute blankLines { text }?, 2121 empty 2122 } 2123 figure = 2124 element figure { 2125 attribute anchor { xsd:ID }?, 2126 [ a:defaultValue = "" ] attribute title { text }?, 2127 [ a:defaultValue = "false" ] 2128 attribute suppress-title { "true" | "false" }?, 2129 attribute src { text }?, 2130 [ a:defaultValue = "left" ] 2131 attribute align { "left" | "center" | "right" }?, 2132 [ a:defaultValue = "" ] attribute alt { text }?, 2133 [ a:defaultValue = "" ] attribute width { text }?, 2134 [ a:defaultValue = "" ] attribute height { text }?, 2135 iref*, 2136 preamble?, 2137 artwork, 2138 postamble? 2139 } 2140 preamble = 2141 element preamble { (text | xref | eref | iref | cref | spanx)* } 2142 artwork = 2143 element artwork { 2144 [ a:defaultValue = "preserve" ] 2145 attribute xml:space { "default" | "preserve" }?, 2146 [ a:defaultValue = "" ] attribute name { text }?, 2147 [ a:defaultValue = "" ] attribute type { text }?, 2148 attribute src { text }?, 2149 [ a:defaultValue = "left" ] 2150 attribute align { "left" | "center" | "right" }?, 2151 [ a:defaultValue = "" ] attribute alt { text }?, 2152 [ a:defaultValue = "" ] attribute width { text }?, 2153 [ a:defaultValue = "" ] attribute height { text }?, 2154 text* 2155 } 2156 postamble = 2157 element postamble { (text | xref | eref | iref | cref | spanx)* } 2158 texttable = 2159 element texttable { 2160 attribute anchor { xsd:ID }?, 2161 [ a:defaultValue = "" ] attribute title { text }?, 2162 [ a:defaultValue = "false" ] 2163 attribute suppress-title { "true" | "false" }?, 2164 [ a:defaultValue = "center" ] 2165 attribute align { "left" | "center" | "right" }?, 2166 [ a:defaultValue = "full" ] 2167 attribute style { "all" | "none" | "headers" | "full" }?, 2168 preamble?, 2169 ttcol+, 2170 c*, 2171 postamble? 2172 } 2173 ttcol = 2174 element ttcol { 2175 attribute width { text }?, 2176 [ a:defaultValue = "left" ] 2177 attribute align { "left" | "center" | "right" }?, 2178 text 2179 } 2180 c = element c { (text | xref | eref | iref | cref | spanx)* } 2181 back = element back { references*, section* } 2182 references = 2183 element references { 2184 [ a:defaultValue = "References" ] attribute title { text }?, 2185 reference+ 2186 } 2187 reference = 2188 element reference { 2189 attribute anchor { xsd:ID }?, 2190 attribute target { text }?, 2191 front, 2192 seriesInfo*, 2193 format*, 2194 annotation* 2195 } 2196 seriesInfo = 2197 element seriesInfo { 2198 attribute name { text }, 2199 attribute value { text }, 2200 empty 2201 } 2202 format = 2203 element format { 2204 attribute target { text }?, 2205 attribute type { text }, 2206 attribute octets { text }?, 2207 empty 2208 } 2209 annotation = 2210 element annotation { (text | xref | eref | iref | cref | spanx)* } 2211 start = rfc 2213 (This schema was derived from version 1.3.6 of the xml2rfc DTD 2214 ('Document Type Definition', [XML], Section 2.8), available from <htt 2215 p://svn.tools.ietf.org/svn/tools/xml2rfc/vocabulary/v2/03/ 2216 xml2rfcv2.dtd>). 2218 Appendix D. Proposed Future Changes for 'v3' 2220 Discussion of "v3" changes takes place on the rfc-interest mailing 2221 list (rfc-interest@rfc-editor.org), which has its home page at 2222 <http://www.rfc-editor.org/mailman/listinfo/rfc-interest>. See also 2223 <https://www.rfc-editor.org/rse/wiki/doku.php?id=design:xml-tags> for 2224 a related Wiki page. 2226 D.1. Contact Information 2228 If contact information is changed to allow non-ASCII characters: add 2229 a place for a ASCII fallback (probably just for the author names). 2231 The content model for <postal> ought to be more strict to allow at 2232 most one of <city>, <region>, <code>, and <country>. 2234 It should be possible to have multiple <email> and <uri> elements 2235 (see also <http://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/36>). 2237 <facsimile> looks outdated, while a container for IM (messaging) URIs 2238 is missing. Maybe this area needs to be aligned with vCard. 2240 Section 4.8 of [RFCSTYLE] hints at a "Contributors" Section that 2241 could supply contact information similar to the one in the auto- 2242 generated "Authors' Address" Section. Consider how to capture 2243 contributor contact information (probably not using <author> to avoid 2244 confusion). Furthermore, consider ways to augment the contact 2245 information section with prose. 2247 D.2. Figures 2249 Cleanup the set of overlapping attributes between <figure> and 2250 <artwork>. 2252 For artwork that consists of a sequence of items (such as messages in 2253 a protocol example), it would be good if a <figure> element could 2254 contain multiple <artwork> elements (to assist code to find good 2255 places for page breaks). 2257 Extend <figure> to support different types of artwork (such as by 2258 specifying certain type attribute values, see <http://greenbytes.de/ 2259 tech/webdav/rfc2629xslt/rfc2629xslt.html#artwork.types>), and also 2260 avoid having to markup code (such as ABNF) as "artwork". 2262 It would be good if "code components" could be marked as such. 2264 Finally, even in preformatted text use of markup could be useful to 2265 support (a) references, or (b) highlighting the important bits (<http 2266 ://greenbytes.de/tech/webdav/rfc2629xslt/ 2267 rfc2629xslt.html#ext-rfc2629.artwork>). 2269 D.3. Linking 2271 Extend <xref> so that subsection/anchors can be specified (see <http: 2272 //greenbytes.de/tech/webdav/rfc2629xslt/ 2273 rfc2629xslt.html#ext-rfc2629.xref>). Remove the "pageno" attribute 2274 which seems to be both undocumented and non-functional. 2276 D.4. Lists 2278 Allow multiple paragraphs in list items; eliminating the need to use 2279 <vspace> -- this could be achieved by adding a list item container 2280 element ("<lt>", see <http://greenbytes.de/tech/webdav/rfc2629xslt/ 2281 rfc2629xslt.html#ext.element.lt> and 2282 <http://www.ietf.org/mail-archive/web/xml2rfc/current/ 2283 msg02010.html>). 2285 Add support for a "dictionary" style; eliminating the need to combine 2286 "hanging" with <vspace> to force new lines (see thread around <http:/ 2287 /www.rfc-editor.org/pipermail/rfc-interest/2013-December/ 2288 005876.html>). 2290 D.5. References 2292 Allow overriding the "anchor" attribute of an included <reference> 2293 element. 2295 Add a way to add prose to a reference that avoids abuse of 2296 <seriesInfo>. 2298 Allow <reference>s that identify a document set such as a BCP. 2300 Deprecate or remove the <format> element; right now it's not used for 2301 the generation of the plain text document anyway. 2303 It is unclear why the "anchor" attribute is optional. 2305 D.6. Archival Considerations 2307 When this vocabulary becomes the canonical RFC format, it will need 2308 to be able to capture all generated information, such as section/ 2309 figure/table numbers, plus any auto-generated boilerplate (copyright 2310 statements etc.). 2312 D.7. Document Metadata 2314 Extend the concept of language tagging to at least examples and 2315 contact information to address potential japanese/chinese font 2316 confusion. 2318 Provide a way to indicate the intended level on the standards track. 2320 Include feedback information in a way so that generated documents can 2321 provide usable feedback links (see <http://greenbytes.de/tech/webdav/ 2322 rfc2629xslt/rfc2629xslt.html#ext.element.feedback>). 2324 D.8. Misc. 2326 Make the <date> element optional; all of its content is optional 2327 already. 2329 <spanx> has both a weird whitespace model ("preserve") and 2330 problematic styling. Consider to deprecate it in favor of elements 2331 such as <b>, <i>, and <tt>. 2333 Indented paragraphs currently can be created by abusing the <list>. 2334 It would be good to have a special element for this purpose. 2336 Provide a special element for inserting block quotes (<http:// 2337 greenbytes.de/tech/webdav/rfc2629xslt/ 2338 rfc2629xslt.html#ext.element.blockquote>). 2340 The content model for <cref> should be extended to allow more flow 2341 elements, such as <xref> and <eref>. 2343 Section titles should really be elements, not attributes (this would 2344 allow them to contain markup). 2346 Text tables are currently very constrained. For instance, it would 2347 be good if alignment of headers and table cells could be de-coupled 2348 <http://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/69>). 2350 Counters are currently restricted to lists, figures, and tables. 2352 Maybe there should be a generic mechanism that is not directly tied 2353 to other elements 2354 <http://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/68>). 2356 Index 2358 A 2359 abbrev attribute 2360 in organization element 20 2361 in title element 31 2362 abstract element 4 2363 inside front 15 2364 address element 5 2365 inside author 9 2366 align attribute 2367 in artwork element 7 2368 in figure element 13 2369 in texttable element 30 2370 in ttcol element 31 2371 alt attribute 2372 in artwork element 7 2373 in figure element 14 2374 anchor attribute 2375 in cref element 11 2376 in figure element 14 2377 in reference element 22 2378 in section element 27 2379 in t element 29 2380 in texttable element 30 2381 annotation element 5 2382 inside reference 22 2383 application/rfc+xml Media Type 34 2384 area element 6 2385 inside front 15 2386 artwork element 6 2387 align attribute 7 2388 alt attribute 7 2389 height attribute 7 2390 inside figure 13 2391 name attribute 7 2392 src attribute 7 2393 type attribute 7 2394 width attribute 8 2395 xml:space attribute 8 2396 Attributes 2397 abbrev 20, 31 2398 align 7, 13, 30-31 2399 alt 7, 14 2400 anchor 11, 14, 22, 27, 29-30 2401 blankLines 32 2402 category 23 2403 consensus 24 2404 counter 17 2405 day 12 2406 docName 24 2407 format 33 2408 fullname 9 2409 hangIndent 17 2410 hangText 29 2411 height 7, 14 2412 initials 9 2413 ipr 24 2414 iprExtract 25 2415 item 16 2416 month 12 2417 name 7, 27 2418 number 25 2419 obsoletes 25 2420 octets 15 2421 pageno 33 2422 primary 16 2423 role 9 2424 seriesNo 25 2425 source 11 2426 src 7, 14 2427 style 17, 28, 30 2428 subitem 16 2429 submissionType 25 2430 suppress-title 14, 31 2431 surname 9 2432 target 13, 15, 22, 33 2433 title 14, 19, 23, 27, 31 2434 toc 27 2435 type 7, 15 2436 updates 26 2437 value 27 2438 width 8, 14, 32 2439 xml:lang 26 2440 xml:space 8, 28 2441 year 12 2442 author element 8 2443 fullname attribute 9 2444 initials attribute 9 2445 inside front 15 2446 role attribute 9 2447 surname attribute 9 2449 B 2450 back element 9 2451 inside rfc 23 2452 blankLines attribute 2453 in vspace element 32 2455 C 2456 c element 10 2457 inside texttable 30 2458 category attribute 2459 in rfc element 23 2460 city element 10 2461 inside postal 20 2462 code element 10 2463 inside postal 20 2464 consensus attribute 2465 in rfc element 24 2466 counter attribute 2467 in list element 17 2468 country element 10 2469 inside postal 20 2470 cref element 11 2471 anchor attribute 11 2472 inside annotation 6 2473 inside c 10 2474 inside postamble 21 2475 inside preamble 21 2476 inside t 29 2477 source attribute 11 2479 D 2480 date element 11 2481 day attribute 12 2482 inside front 15 2483 month attribute 12 2484 year attribute 12 2485 day attribute 2486 in date element 12 2487 docName attribute 2488 in rfc element 24 2490 E 2491 Elements 2492 abstract 4, 15 2493 address 5, 9 2494 annotation 5, 22 2495 area 6, 15 2496 artwork 6, 13 2497 author 8, 15 2498 back 9, 23 2499 c 10, 30 2500 city 10, 20 2501 code 10, 20 2502 country 10, 20 2503 cref 6, 10-11, 21, 29 2504 date 11, 15 2505 email 5, 12 2506 eref 5, 10, 12, 21, 29 2507 facsimile 5, 13 2508 figure 13, 26, 29 2509 format 14, 22 2510 front 15, 22-23 2511 iref 5, 10, 13, 16, 21, 26, 29 2512 keyword 15-16 2513 list 17, 29 2514 middle 19, 23 2515 note 15, 19 2516 organization 9, 19 2517 phone 5, 20 2518 postal 5, 20 2519 postamble 13, 21, 30 2520 preamble 13, 21, 30 2521 reference 22 2522 references 10, 22 2523 region 20, 23 2524 rfc 23 2525 section 10, 19, 26 2526 seriesInfo 22, 27 2527 spanx 6, 10, 21, 28-29 2528 street 20, 28 2529 t 4, 17, 19, 26, 29 2530 texttable 26, 29 2531 title 15, 31 2532 ttcol 30-31 2533 uri 5, 32 2534 vspace 29, 32 2535 workgroup 15, 32 2536 xref 5, 10, 21, 29, 33 2537 email element 12 2538 inside address 5 2539 eref element 12 2540 inside annotation 5 2541 inside c 10 2542 inside postamble 21 2543 inside preamble 21 2544 inside t 29 2545 target attribute 13 2547 F 2548 facsimile element 13 2549 inside address 5 2550 figure element 13 2551 align attribute 13 2552 alt attribute 14 2553 anchor attribute 14 2554 height attribute 14 2555 inside section 26 2556 inside t 29 2557 src attribute 14 2558 suppress-title attribute 14 2559 title attribute 14 2560 width attribute 14 2561 format attribute 2562 in xref element 33 2563 format element 14 2564 inside reference 22 2565 octets attribute 15 2566 target attribute 15 2567 type attribute 15 2568 front element 15 2569 inside reference 22 2570 inside rfc 23 2571 fullname attribute 2572 in author element 9 2574 H 2575 hangIndent attribute 2576 in list element 17 2577 hangText attribute 2578 in t element 29 2579 height attribute 2580 in artwork element 7 2581 in figure element 14 2583 I 2584 initials attribute 2585 in author element 9 2586 ipr attribute 2587 '*2026' 41 2588 '*3667' 41 2589 '*3978' 41 2590 '*trust200811' 40 2591 '*trust200902' 39 2592 'noDerivativesTrust200902' 40 2593 'noModificationTrust200902' 39 2594 'pre5378Trust200902' 40 2595 'trust200902' 39 2596 in rfc element 24 2597 iprExtract attribute 2598 in rfc element 25 2599 iref element 16 2600 inside annotation 5 2601 inside c 10 2602 inside figure 13 2603 inside postamble 21 2604 inside preamble 21 2605 inside section 26 2606 inside t 29 2607 item attribute 16 2608 primary attribute 16 2609 subitem attribute 16 2610 item attribute 2611 in iref element 16 2613 K 2614 keyword element 16 2615 inside front 15 2617 L 2618 list element 17 2619 counter attribute 17 2620 hangIndent attribute 17 2621 inside t 29 2622 style attribute 17 2623 list styles 2624 empty 17 2625 format ... 18 2626 hanging 18 2627 letters 18 2628 numbers 18 2629 symbols 18 2631 M 2632 Media Type 2633 application/rfc+xml 34 2634 middle element 19 2635 inside rfc 23 2636 month attribute 2637 in date element 12 2639 N 2640 name attribute 2641 in artwork element 7 2642 in seriesInfo element 27 2643 note element 19 2644 inside front 15 2645 title attribute 19 2646 number attribute 2647 in rfc element 25 2649 O 2650 obsoletes attribute 2651 in rfc element 25 2652 octets attribute 2653 in format element 15 2654 organization element 19 2655 abbrev attribute 20 2656 inside author 9 2658 P 2659 pageno attribute 2660 in xref element 33 2661 phone element 20 2662 inside address 5 2663 postal element 20 2664 inside address 5 2665 postamble element 21 2666 inside figure 13 2667 inside texttable 30 2668 preamble element 21 2669 inside figure 13 2670 inside texttable 30 2671 primary attribute 2672 in iref element 16 2674 R 2675 reference element 22 2676 anchor attribute 22 2677 inside references 22 2678 target attribute 22 2679 references element 22 2680 inside back 10 2681 title attribute 23 2682 region element 23 2683 inside postal 20 2684 rfc element 23 2685 category attribute 23 2686 consensus attribute 24 2687 docName attribute 24 2688 ipr attribute 24 2689 iprExtract attribute 25 2690 number attribute 25 2691 obsoletes attribute 25 2692 seriesNo attribute 25 2693 submissionType attribute 25 2694 updates attribute 26 2695 xml:lang attribute 26 2696 role attribute 2697 in author element 9 2699 S 2700 section element 26 2701 anchor attribute 27 2702 inside back 10 2703 inside middle 19 2704 inside section 26 2705 title attribute 27 2706 toc attribute 27 2707 seriesInfo element 27 2708 inside reference 22 2709 name attribute 27 2710 value attribute 27 2711 seriesNo attribute 2712 in rfc element 25 2713 source attribute 2714 in cref element 11 2715 spanx element 28 2716 inside annotation 6 2717 inside c 10 2718 inside postamble 21 2719 inside preamble 21 2720 inside t 29 2721 style attribute 28 2722 xml:space attribute 28 2723 src attribute 2724 in artwork element 7 2725 in figure element 14 2726 street element 28 2727 inside postal 20 2728 style attribute 2729 in list element 17 2730 in spanx element 28 2731 in texttable element 30 2732 subitem attribute 2733 in iref element 16 2734 submissionType attribute 2735 in rfc element 25 2736 suppress-title attribute 2737 in figure element 14 2738 in texttable element 31 2739 surname attribute 2740 in author element 9 2742 T 2743 t element 29 2744 anchor attribute 29 2745 hangText attribute 29 2746 inside abstract 4 2747 inside list 17 2748 inside note 19 2749 inside section 26 2750 target attribute 2751 in eref element 13 2752 in format element 15 2753 in reference element 22 2754 in xref element 33 2755 texttable element 29 2756 align attribute 30 2757 anchor attribute 30 2758 inside section 26 2759 style attribute 30 2760 suppress-title attribute 31 2761 title attribute 31 2762 title attribute 2763 in figure element 14 2764 in note element 19 2765 in references element 23 2766 in section element 27 2767 in texttable element 31 2768 title element 31 2769 abbrev attribute 31 2770 inside front 15 2771 toc attribute 2772 in section element 27 2773 ttcol element 31 2774 align attribute 31 2775 inside texttable 30 2776 width attribute 32 2777 type attribute 2778 in artwork element 7 2779 in format element 15 2781 U 2782 updates attribute 2783 in rfc element 26 2784 uri element 32 2785 inside address 5 2787 V 2788 value attribute 2789 in seriesInfo element 27 2790 vspace element 32 2791 blankLines attribute 32 2792 inside t 29 2794 W 2795 width attribute 2796 in artwork element 8 2797 in figure element 14 2798 in ttcol element 32 2799 workgroup element 32 2800 inside front 15 2802 X 2803 xml:lang attribute 2804 in rfc element 26 2805 xml:space attribute 2806 in artwork element 8 2807 in spanx element 28 2808 xref element 33 2809 format attribute 33 2810 inside annotation 5 2811 inside c 10 2812 inside postamble 21 2813 inside preamble 21 2814 inside t 29 2815 pageno attribute 33 2816 target attribute 33 2818 Y 2819 year attribute 2820 in date element 12 2822 Author's Address 2824 Julian F. Reschke 2825 greenbytes GmbH 2826 Hafenweg 16 2827 Muenster, NW 48155 2828 Germany 2830 EMail: julian.reschke@greenbytes.de 2831 URI: http://greenbytes.de/tech/webdav/