idnits 2.17.1 draft-reschke-hab-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Sep 2009 rather than the newer Notice from 28 Dec 2009. (See https://trustee.ietf.org/license-info/) 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 document seems to lack a Security Considerations section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (December 28, 2009) is 5205 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- -- Obsolete informational reference (is this intentional?): RFC 2629 (Obsoleted by RFC 7749) -- Obsolete informational reference (is this intentional?): RFC 5741 (Obsoleted by RFC 7841) Summary: 3 errors (**), 0 flaws (~~), 1 warning (==), 3 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 Intended status: Informational December 28, 2009 5 Expires: July 1, 2010 7 Test Renditions for new RFC Headers & Boilerplate 8 draft-reschke-hab-04 10 Abstract 12 This document contains test renditions for the new header and 13 boilerplate values specified in RFC 5741, and reports on the 14 implementation status for xml2rfc processors. 16 Status of this Memo 18 This Internet-Draft is submitted to IETF in full conformance with the 19 provisions of BCP 78 and BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF), its areas, and its working groups. Note that 23 other groups may also distribute working documents as Internet- 24 Drafts. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 The list of current Internet-Drafts can be accessed at 32 http://www.ietf.org/ietf/1id-abstracts.txt. 34 The list of Internet-Draft Shadow Directories can be accessed at 35 http://www.ietf.org/shadow.html. 37 This Internet-Draft will expire on July 1, 2010. 39 Copyright Notice 41 Copyright (c) 2009 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 BSD License. 54 Table of Contents 56 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 57 2. Implementation Status for Xml2Rfc . . . . . . . . . . . . . . 3 58 2.1. rfc2629.xslt (XML -> XSLT -> (X)HTML|XSL-FO) . . . . . . . 3 59 2.2. xml2rfc.tcl (XML -> TCL -> TXT|HTML) . . . . . . . . . . . 3 60 3. Test Renditions . . . . . . . . . . . . . . . . . . . . . . . 3 61 3.1. IETF Stream . . . . . . . . . . . . . . . . . . . . . . . 3 62 3.1.1. IETF Standards Track w/ consensus . . . . . . . . . . 3 63 3.1.2. IETF Best Current Practice w/ consensus . . . . . . . 4 64 3.1.3. IETF Experimental w/ consensus . . . . . . . . . . . . 4 65 3.1.4. IETF Experimental w/o consensus . . . . . . . . . . . 5 66 3.1.5. IETF Historic w/ consensus . . . . . . . . . . . . . . 5 67 3.1.6. IETF Historic w/o consensus . . . . . . . . . . . . . 6 68 3.1.7. IETF Informational w/ consensus . . . . . . . . . . . 6 69 3.1.8. IETF Informational w/o consensus . . . . . . . . . . . 7 70 3.2. IAB Stream . . . . . . . . . . . . . . . . . . . . . . . . 8 71 3.2.1. IAB Historic . . . . . . . . . . . . . . . . . . . . . 8 72 3.2.2. IAB Informational . . . . . . . . . . . . . . . . . . 8 73 3.3. IRTF Stream . . . . . . . . . . . . . . . . . . . . . . . 9 74 3.3.1. IRTF Experimental w/ RG consensus . . . . . . . . . . 9 75 3.3.2. IRTF Experimental w/o RG consensus . . . . . . . . . . 9 76 3.3.3. IRTF Experimental (no RG) . . . . . . . . . . . . . . 10 77 3.3.4. IRTF Historic w/ RG consensus . . . . . . . . . . . . 10 78 3.3.5. IRTF Historic w/o RG consensus . . . . . . . . . . . . 11 79 3.3.6. IRTF Historic (No RG) . . . . . . . . . . . . . . . . 12 80 3.3.7. IRTF Informational w/ RG consensus . . . . . . . . . . 12 81 3.3.8. IRTF Informational w/o RG consensus . . . . . . . . . 13 82 3.3.9. IRTF Informational (No RG) . . . . . . . . . . . . . . 13 83 3.4. Independent Stream . . . . . . . . . . . . . . . . . . . . 14 84 3.4.1. Independent Submission Experimental . . . . . . . . . 14 85 3.4.2. Independent Submission Historic . . . . . . . . . . . 15 86 3.4.3. Independent Submission Informational . . . . . . . . . 15 87 4. Informative References . . . . . . . . . . . . . . . . . . . . 16 88 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 16 89 A.1. Since draft-reschke-hab-00 . . . . . . . . . . . . . . . . 16 90 A.2. Since draft-reschke-hab-01 . . . . . . . . . . . . . . . . 16 91 A.3. Since draft-reschke-hab-02 . . . . . . . . . . . . . . . . 16 92 A.4. Since draft-reschke-hab-03 . . . . . . . . . . . . . . . . 16 93 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 16 95 1. Introduction 97 This document contains test renditions for the changes specified in 98 [RFC5741], as generated by an experimental version of rfc2629.xslt 99 (see 100 ). 101 Its purpose is to illustrate the resulting text for all the 102 variations of the various input parameters, and to track the changes 103 applied to the proposal during the RFC-Editor's publication process. 105 2. Implementation Status for Xml2Rfc 107 Please join the xml2rfc mailing list 108 () for 109 discussion of changes to the RFC 2629 vocabulary ([RFC2629]). 111 2.1. rfc2629.xslt (XML -> XSLT -> (X)HTML|XSL-FO) 113 The examples below were generated with an experimental version of 114 rfc2629.xslt (see 115 ). 117 2.2. xml2rfc.tcl (XML -> TCL -> TXT|HTML) 119 At the time of this writing, there was no work scheduled for updating 120 xml2rfc, thus no direct conversion of XML source to TXT files is 121 available (see ). 123 3. Test Renditions 125 3.1. IETF Stream 127 3.1.1. IETF Standards Track w/ consensus 129 3.1.1.1. Header (Left Column) 131 Internet Engineering Task Force (IETF) 132 Request for Comments: 9999 133 Category: Standards Track 134 ISSN: 2070-1721 136 3.1.1.2. Text of 'Status Of This Memo' 138 This is an Internet Standards Track document. 140 This document is a product of the Internet Engineering Task Force 141 (IETF). It represents the consensus of the IETF community. It has 142 received public review and has been approved for publication by the 143 Internet Engineering Steering Group (IESG). Further information on 144 Internet Standards is available in Section 2 of RFC 5741. 146 Information about the current status of this document, any errata, 147 and how to provide feedback on it may be obtained at 148 http://www.rfc-editor.org/info/rfc9999. 150 3.1.2. IETF Best Current Practice w/ consensus 152 3.1.2.1. Header (Left Column) 154 Internet Engineering Task Force (IETF) 155 Request for Comments: 9999 156 Category: Best Current Practice 157 ISSN: 2070-1721 159 3.1.2.2. Text of 'Status Of This Memo' 161 This memo documents an Internet Best Current Practice. 163 This document is a product of the Internet Engineering Task Force 164 (IETF). It represents the consensus of the IETF community. It has 165 received public review and has been approved for publication by the 166 Internet Engineering Steering Group (IESG). Further information on 167 BCPs is available in Section 2 of RFC 5741. 169 Information about the current status of this document, any errata, 170 and how to provide feedback on it may be obtained at 171 http://www.rfc-editor.org/info/rfc9999. 173 3.1.3. IETF Experimental w/ consensus 175 3.1.3.1. Header (Left Column) 177 Internet Engineering Task Force (IETF) 178 Request for Comments: 9999 179 Category: Experimental 180 ISSN: 2070-1721 182 3.1.3.2. Text of 'Status Of This Memo' 184 This document is not an Internet Standards Track specification; it is 185 published for examination, experimental implementation, and 186 evaluation. 188 This document defines an Experimental Protocol for the Internet 189 community. This document is a product of the Internet Engineering 190 Task Force (IETF). It represents the consensus of the IETF 191 community. It has received public review and has been approved for 192 publication by the Internet Engineering Steering Group (IESG). Not 193 all documents approved by the IESG are a candidate for any level of 194 Internet Standard; see Section 2 of RFC 5741. 196 Information about the current status of this document, any errata, 197 and how to provide feedback on it may be obtained at 198 http://www.rfc-editor.org/info/rfc9999. 200 3.1.4. IETF Experimental w/o consensus 202 3.1.4.1. Header (Left Column) 204 Internet Engineering Task Force (IETF) 205 Request for Comments: 9999 206 Category: Experimental 207 ISSN: 2070-1721 209 3.1.4.2. Text of 'Status Of This Memo' 211 This document is not an Internet Standards Track specification; it is 212 published for examination, experimental implementation, and 213 evaluation. 215 This document defines an Experimental Protocol for the Internet 216 community. This document is a product of the Internet Engineering 217 Task Force (IETF). It has been approved for publication by the 218 Internet Engineering Steering Group (IESG). Not all documents 219 approved by the IESG are a candidate for any level of Internet 220 Standard; see Section 2 of RFC 5741. 222 Information about the current status of this document, any errata, 223 and how to provide feedback on it may be obtained at 224 http://www.rfc-editor.org/info/rfc9999. 226 3.1.5. IETF Historic w/ consensus 228 3.1.5.1. Header (Left Column) 230 Internet Engineering Task Force (IETF) 231 Request for Comments: 9999 232 Category: Historic 233 ISSN: 2070-1721 235 3.1.5.2. Text of 'Status Of This Memo' 237 This document is not an Internet Standards Track specification; it is 238 published for the historical record. 240 This document defines a Historic Document for the Internet community. 241 This document is a product of the Internet Engineering Task Force 242 (IETF). It represents the consensus of the IETF community. It has 243 received public review and has been approved for publication by the 244 Internet Engineering Steering Group (IESG). Not all documents 245 approved by the IESG are a candidate for any level of Internet 246 Standard; see Section 2 of RFC 5741. 248 Information about the current status of this document, any errata, 249 and how to provide feedback on it may be obtained at 250 http://www.rfc-editor.org/info/rfc9999. 252 3.1.6. IETF Historic w/o consensus 254 3.1.6.1. Header (Left Column) 256 Internet Engineering Task Force (IETF) 257 Request for Comments: 9999 258 Category: Historic 259 ISSN: 2070-1721 261 3.1.6.2. Text of 'Status Of This Memo' 263 This document is not an Internet Standards Track specification; it is 264 published for the historical record. 266 This document defines a Historic Document for the Internet community. 267 This document is a product of the Internet Engineering Task Force 268 (IETF). It has been approved for publication by the Internet 269 Engineering Steering Group (IESG). Not all documents approved by the 270 IESG are a candidate for any level of Internet Standard; see Section 271 2 of RFC 5741. 273 Information about the current status of this document, any errata, 274 and how to provide feedback on it may be obtained at 275 http://www.rfc-editor.org/info/rfc9999. 277 3.1.7. IETF Informational w/ consensus 278 3.1.7.1. Header (Left Column) 280 Internet Engineering Task Force (IETF) 281 Request for Comments: 9999 282 Category: Informational 283 ISSN: 2070-1721 285 3.1.7.2. Text of 'Status Of This Memo' 287 This document is not an Internet Standards Track specification; it is 288 published for informational purposes. 290 This document is a product of the Internet Engineering Task Force 291 (IETF). It represents the consensus of the IETF community. It has 292 received public review and has been approved for publication by the 293 Internet Engineering Steering Group (IESG). Not all documents 294 approved by the IESG are a candidate for any level of Internet 295 Standard; see Section 2 of RFC 5741. 297 Information about the current status of this document, any errata, 298 and how to provide feedback on it may be obtained at 299 http://www.rfc-editor.org/info/rfc9999. 301 3.1.8. IETF Informational w/o consensus 303 3.1.8.1. Header (Left Column) 305 Internet Engineering Task Force (IETF) 306 Request for Comments: 9999 307 Category: Informational 308 ISSN: 2070-1721 310 3.1.8.2. Text of 'Status Of This Memo' 312 This document is not an Internet Standards Track specification; it is 313 published for informational purposes. 315 This document is a product of the Internet Engineering Task Force 316 (IETF). It has been approved for publication by the Internet 317 Engineering Steering Group (IESG). Not all documents approved by the 318 IESG are a candidate for any level of Internet Standard; see Section 319 2 of RFC 5741. 321 Information about the current status of this document, any errata, 322 and how to provide feedback on it may be obtained at 323 http://www.rfc-editor.org/info/rfc9999. 325 3.2. IAB Stream 327 3.2.1. IAB Historic 329 3.2.1.1. Header (Left Column) 331 Internet Architecture Board (IAB) 332 Request for Comments: 9999 333 Category: Historic 334 ISSN: 2070-1721 336 3.2.1.2. Text of 'Status Of This Memo' 338 This document is not an Internet Standards Track specification; it is 339 published for the historical record. 341 This document defines a Historic Document for the Internet community. 342 This document is a product of the Internet Architecture Board (IAB) 343 and represents information that the IAB has deemed valuable to 344 provide for permanent record. Documents approved for publication by 345 the IAB are not a candidate for any level of Internet Standard; see 346 Section 2 of RFC 5741. 348 Information about the current status of this document, any errata, 349 and how to provide feedback on it may be obtained at 350 http://www.rfc-editor.org/info/rfc9999. 352 3.2.2. IAB Informational 354 3.2.2.1. Header (Left Column) 356 Internet Architecture Board (IAB) 357 Request for Comments: 9999 358 Category: Informational 359 ISSN: 2070-1721 361 3.2.2.2. Text of 'Status Of This Memo' 363 This document is not an Internet Standards Track specification; it is 364 published for informational purposes. 366 This document is a product of the Internet Architecture Board (IAB) 367 and represents information that the IAB has deemed valuable to 368 provide for permanent record. Documents approved for publication by 369 the IAB are not a candidate for any level of Internet Standard; see 370 Section 2 of RFC 5741. 372 Information about the current status of this document, any errata, 373 and how to provide feedback on it may be obtained at 374 http://www.rfc-editor.org/info/rfc9999. 376 3.3. IRTF Stream 378 3.3.1. IRTF Experimental w/ RG consensus 380 3.3.1.1. Header (Left Column) 382 Internet Research Task Force (IRTF) 383 Request for Comments: 9999 384 Category: Experimental 385 ISSN: 2070-1721 387 3.3.1.2. Text of 'Status Of This Memo' 389 This document is not an Internet Standards Track specification; it is 390 published for examination, experimental implementation, and 391 evaluation. 393 This document defines an Experimental Protocol for the Internet 394 community. This document is a product of the Internet Research Task 395 Force (IRTF). The IRTF publishes the results of Internet-related 396 research and development activities. These results might not be 397 suitable for deployment. This RFC represents the consensus of the 398 Research Group of the Internet Research Task Force 399 (IRTF). Documents approved for publication by the IRSG are not a 400 candidate for any level of Internet Standard; see Section 2 of RFC 401 5741. 403 Information about the current status of this document, any errata, 404 and how to provide feedback on it may be obtained at 405 http://www.rfc-editor.org/info/rfc9999. 407 3.3.2. IRTF Experimental w/o RG consensus 409 3.3.2.1. Header (Left Column) 411 Internet Research Task Force (IRTF) 412 Request for Comments: 9999 413 Category: Experimental 414 ISSN: 2070-1721 416 3.3.2.2. Text of 'Status Of This Memo' 418 This document is not an Internet Standards Track specification; it is 419 published for examination, experimental implementation, and 420 evaluation. 422 This document defines an Experimental Protocol for the Internet 423 community. This document is a product of the Internet Research Task 424 Force (IRTF). The IRTF publishes the results of Internet-related 425 research and development activities. These results might not be 426 suitable for deployment. This RFC represents the individual 427 opinion(s) of one or more members of the Research Group 428 of the Internet Research Task Force (IRTF). Documents approved for 429 publication by the IRSG are not a candidate for any level of Internet 430 Standard; see Section 2 of RFC 5741. 432 Information about the current status of this document, any errata, 433 and how to provide feedback on it may be obtained at 434 http://www.rfc-editor.org/info/rfc9999. 436 3.3.3. IRTF Experimental (no RG) 438 3.3.3.1. Header (Left Column) 440 Internet Research Task Force (IRTF) 441 Request for Comments: 9999 442 Category: Experimental 443 ISSN: 2070-1721 445 3.3.3.2. Text of 'Status Of This Memo' 447 This document is not an Internet Standards Track specification; it is 448 published for examination, experimental implementation, and 449 evaluation. 451 This document defines an Experimental Protocol for the Internet 452 community. This document is a product of the Internet Research Task 453 Force (IRTF). The IRTF publishes the results of Internet-related 454 research and development activities. These results might not be 455 suitable for deployment. Documents approved for publication by the 456 IRSG are not a candidate for any level of Internet Standard; see 457 Section 2 of RFC 5741. 459 Information about the current status of this document, any errata, 460 and how to provide feedback on it may be obtained at 461 http://www.rfc-editor.org/info/rfc9999. 463 3.3.4. IRTF Historic w/ RG consensus 464 3.3.4.1. Header (Left Column) 466 Internet Research Task Force (IRTF) 467 Request for Comments: 9999 468 Category: Historic 469 ISSN: 2070-1721 471 3.3.4.2. Text of 'Status Of This Memo' 473 This document is not an Internet Standards Track specification; it is 474 published for the historical record. 476 This document defines a Historic Document for the Internet community. 477 This document is a product of the Internet Research Task Force 478 (IRTF). The IRTF publishes the results of Internet-related research 479 and development activities. These results might not be suitable for 480 deployment. This RFC represents the consensus of the 481 Research Group of the Internet Research Task Force (IRTF). Documents 482 approved for publication by the IRSG are not a candidate for any 483 level of Internet Standard; see Section 2 of RFC 5741. 485 Information about the current status of this document, any errata, 486 and how to provide feedback on it may be obtained at 487 http://www.rfc-editor.org/info/rfc9999. 489 3.3.5. IRTF Historic w/o RG consensus 491 3.3.5.1. Header (Left Column) 493 Internet Research Task Force (IRTF) 494 Request for Comments: 9999 495 Category: Historic 496 ISSN: 2070-1721 498 3.3.5.2. Text of 'Status Of This Memo' 500 This document is not an Internet Standards Track specification; it is 501 published for the historical record. 503 This document defines a Historic Document for the Internet community. 504 This document is a product of the Internet Research Task Force 505 (IRTF). The IRTF publishes the results of Internet-related research 506 and development activities. These results might not be suitable for 507 deployment. This RFC represents the individual opinion(s) of one or 508 more members of the Research Group of the Internet 509 Research Task Force (IRTF). Documents approved for publication by 510 the IRSG are not a candidate for any level of Internet Standard; see 511 Section 2 of RFC 5741. 513 Information about the current status of this document, any errata, 514 and how to provide feedback on it may be obtained at 515 http://www.rfc-editor.org/info/rfc9999. 517 3.3.6. IRTF Historic (No RG) 519 3.3.6.1. Header (Left Column) 521 Internet Research Task Force (IRTF) 522 Request for Comments: 9999 523 Category: Historic 524 ISSN: 2070-1721 526 3.3.6.2. Text of 'Status Of This Memo' 528 This document is not an Internet Standards Track specification; it is 529 published for the historical record. 531 This document defines a Historic Document for the Internet community. 532 This document is a product of the Internet Research Task Force 533 (IRTF). The IRTF publishes the results of Internet-related research 534 and development activities. These results might not be suitable for 535 deployment. Documents approved for publication by the IRSG are not a 536 candidate for any level of Internet Standard; see Section 2 of RFC 537 5741. 539 Information about the current status of this document, any errata, 540 and how to provide feedback on it may be obtained at 541 http://www.rfc-editor.org/info/rfc9999. 543 3.3.7. IRTF Informational w/ RG consensus 545 3.3.7.1. Header (Left Column) 547 Internet Research Task Force (IRTF) 548 Request for Comments: 9999 549 Category: Informational 550 ISSN: 2070-1721 552 3.3.7.2. Text of 'Status Of This Memo' 554 This document is not an Internet Standards Track specification; it is 555 published for informational purposes. 557 This document is a product of the Internet Research Task Force 558 (IRTF). The IRTF publishes the results of Internet-related research 559 and development activities. These results might not be suitable for 560 deployment. This RFC represents the consensus of the 561 Research Group of the Internet Research Task Force (IRTF). Documents 562 approved for publication by the IRSG are not a candidate for any 563 level of Internet Standard; see Section 2 of RFC 5741. 565 Information about the current status of this document, any errata, 566 and how to provide feedback on it may be obtained at 567 http://www.rfc-editor.org/info/rfc9999. 569 3.3.8. IRTF Informational w/o RG consensus 571 3.3.8.1. Header (Left Column) 573 Internet Research Task Force (IRTF) 574 Request for Comments: 9999 575 Category: Informational 576 ISSN: 2070-1721 578 3.3.8.2. Text of 'Status Of This Memo' 580 This document is not an Internet Standards Track specification; it is 581 published for informational purposes. 583 This document is a product of the Internet Research Task Force 584 (IRTF). The IRTF publishes the results of Internet-related research 585 and development activities. These results might not be suitable for 586 deployment. This RFC represents the individual opinion(s) of one or 587 more members of the Research Group of the Internet 588 Research Task Force (IRTF). Documents approved for publication by 589 the IRSG are not a candidate for any level of Internet Standard; see 590 Section 2 of RFC 5741. 592 Information about the current status of this document, any errata, 593 and how to provide feedback on it may be obtained at 594 http://www.rfc-editor.org/info/rfc9999. 596 3.3.9. IRTF Informational (No RG) 598 3.3.9.1. Header (Left Column) 600 Internet Research Task Force (IRTF) 601 Request for Comments: 9999 602 Category: Informational 603 ISSN: 2070-1721 605 3.3.9.2. Text of 'Status Of This Memo' 607 This document is not an Internet Standards Track specification; it is 608 published for informational purposes. 610 This document is a product of the Internet Research Task Force 611 (IRTF). The IRTF publishes the results of Internet-related research 612 and development activities. These results might not be suitable for 613 deployment. Documents approved for publication by the IRSG are not a 614 candidate for any level of Internet Standard; see Section 2 of RFC 615 5741. 617 Information about the current status of this document, any errata, 618 and how to provide feedback on it may be obtained at 619 http://www.rfc-editor.org/info/rfc9999. 621 3.4. Independent Stream 623 3.4.1. Independent Submission Experimental 625 3.4.1.1. Header (Left Column) 627 Independent Submission 628 Request for Comments: 9999 629 Category: Experimental 630 ISSN: 2070-1721 632 3.4.1.2. Text of 'Status Of This Memo' 634 This document is not an Internet Standards Track specification; it is 635 published for examination, experimental implementation, and 636 evaluation. 638 This document defines an Experimental Protocol for the Internet 639 community. This is a contribution to the RFC Series, independently 640 of any other RFC stream. The RFC Editor has chosen to publish this 641 document at its discretion and makes no statement about its value for 642 implementation or deployment. Documents approved for publication by 643 the RFC Editor are not a candidate for any level of Internet 644 Standard; see Section 2 of RFC 5741. 646 Information about the current status of this document, any errata, 647 and how to provide feedback on it may be obtained at 648 http://www.rfc-editor.org/info/rfc9999. 650 3.4.2. Independent Submission Historic 652 3.4.2.1. Header (Left Column) 654 Independent Submission 655 Request for Comments: 9999 656 Category: Historic 657 ISSN: 2070-1721 659 3.4.2.2. Text of 'Status Of This Memo' 661 This document is not an Internet Standards Track specification; it is 662 published for the historical record. 664 This document defines a Historic Document for the Internet community. 665 This is a contribution to the RFC Series, independently of any other 666 RFC stream. The RFC Editor has chosen to publish this document at 667 its discretion and makes no statement about its value for 668 implementation or deployment. Documents approved for publication by 669 the RFC Editor are not a candidate for any level of Internet 670 Standard; see Section 2 of RFC 5741. 672 Information about the current status of this document, any errata, 673 and how to provide feedback on it may be obtained at 674 http://www.rfc-editor.org/info/rfc9999. 676 3.4.3. Independent Submission Informational 678 3.4.3.1. Header (Left Column) 680 Independent Submission 681 Request for Comments: 9999 682 Category: Informational 683 ISSN: 2070-1721 685 3.4.3.2. Text of 'Status Of This Memo' 687 This document is not an Internet Standards Track specification; it is 688 published for informational purposes. 690 This is a contribution to the RFC Series, independently of any other 691 RFC stream. The RFC Editor has chosen to publish this document at 692 its discretion and makes no statement about its value for 693 implementation or deployment. Documents approved for publication by 694 the RFC Editor are not a candidate for any level of Internet 695 Standard; see Section 2 of RFC 5741. 697 Information about the current status of this document, any errata, 698 and how to provide feedback on it may be obtained at 699 http://www.rfc-editor.org/info/rfc9999. 701 4. Informative References 703 [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, 704 June 1999. 706 [RFC5741] Daigle, L. and O. Kolkman, "RFC Streams, Headers, and 707 Boilerplates", RFC 5741, December 2009. 709 Appendix A. Change Log 711 A.1. Since draft-reschke-hab-00 713 Updated to RFC 5741-to-be as of 2009-12-17: (i) expanded submission 714 stream names, (2) replaced "RFC XXXX" by "RFC 5741". 716 A.2. Since draft-reschke-hab-01 718 Fix oversight: "Not all documents approved by the IESG are candidate 719 for any level of Internet Standards" -> "Not all documents approved 720 by the IESG are a candidate for any level of Internet Standard". 722 A.3. Since draft-reschke-hab-02 724 Remove a superfluous comma, and add examples for IRTF documents not 725 coming from a RG. 727 A.4. Since draft-reschke-hab-03 729 Update draft reference to RFC 5741. Add RFC series ISSN number to 730 headers (as implemented by RFC Editor). 732 Author's Address 734 Julian F. Reschke 735 greenbytes GmbH 736 Hafenweg 16 737 Muenster, NW 48155 738 Germany 740 Email: julian.reschke@greenbytes.de 741 URI: http://greenbytes.de/tech/webdav/