idnits 2.17.1 draft-reschke-hab-02.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 22, 2009) is 5238 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) Summary: 3 errors (**), 0 flaws (~~), 1 warning (==), 2 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 22, 2009 5 Expires: June 25, 2010 7 Test Renditions for new RFC Headers & Boilerplate 8 draft-reschke-hab-02 10 Abstract 12 This document contains test renditions for the new header and 13 boilerplate values proposed in 14 draft-iab-streams-headers-boilerplates, and reports on the 15 implementation status for xml2rfc processors. 17 Status of this Memo 19 This Internet-Draft is submitted to IETF in full conformance with the 20 provisions of BCP 78 and BCP 79. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF), its areas, and its working groups. Note that 24 other groups may also distribute working documents as Internet- 25 Drafts. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as "work in progress." 32 The list of current Internet-Drafts can be accessed at 33 http://www.ietf.org/ietf/1id-abstracts.txt. 35 The list of Internet-Draft Shadow Directories can be accessed at 36 http://www.ietf.org/shadow.html. 38 This Internet-Draft will expire on June 25, 2010. 40 Copyright Notice 42 Copyright (c) 2009 IETF Trust and the persons identified as the 43 document authors. All rights reserved. 45 This document is subject to BCP 78 and the IETF Trust's Legal 46 Provisions Relating to IETF Documents 47 (http://trustee.ietf.org/license-info) in effect on the date of 48 publication of this document. Please review these documents 49 carefully, as they describe your rights and restrictions with respect 50 to this document. Code Components extracted from this document must 51 include Simplified BSD License text as described in Section 4.e of 52 the Trust Legal Provisions and are provided without warranty as 53 described in the BSD License. 55 Table of Contents 57 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 58 2. Implementation Status for Xml2Rfc . . . . . . . . . . . . . . 3 59 2.1. rfc2629.xslt (XML -> XSLT -> (X)HTML|XSL-FO) . . . . . . . 3 60 2.2. xml2rfc.tcl (XML -> TCL -> TXT|HTML) . . . . . . . . . . . 3 61 3. Test Renditions . . . . . . . . . . . . . . . . . . . . . . . 3 62 3.1. IETF Stream . . . . . . . . . . . . . . . . . . . . . . . 3 63 3.1.1. IETF Standards Track w/ consensus . . . . . . . . . . 3 64 3.1.2. IETF Best Current Practice w/ consensus . . . . . . . 4 65 3.1.3. IETF Experimental w/ consensus . . . . . . . . . . . . 4 66 3.1.4. IETF Experimental w/o consensus . . . . . . . . . . . 5 67 3.1.5. IETF Historic w/ consensus . . . . . . . . . . . . . . 5 68 3.1.6. IETF Historic w/o consensus . . . . . . . . . . . . . 6 69 3.1.7. IETF Informational w/ consensus . . . . . . . . . . . 7 70 3.1.8. IETF Informational w/o consensus . . . . . . . . . . . 7 71 3.2. IAB Stream . . . . . . . . . . . . . . . . . . . . . . . . 8 72 3.2.1. IAB Historic . . . . . . . . . . . . . . . . . . . . . 8 73 3.2.2. IAB Informational . . . . . . . . . . . . . . . . . . 8 74 3.3. IRTF Stream . . . . . . . . . . . . . . . . . . . . . . . 9 75 3.3.1. IRTF Experimental w/ RG consensus . . . . . . . . . . 9 76 3.3.2. IRTF Experimental w/o RG consensus . . . . . . . . . . 9 77 3.3.3. IRTF Historic w/ RG consensus . . . . . . . . . . . . 10 78 3.3.4. IRTF Historic w/o RG consensus . . . . . . . . . . . . 10 79 3.3.5. IRTF Informational w/ RG consensus . . . . . . . . . . 11 80 3.3.6. IRTF Informational w/o RG consensus . . . . . . . . . 11 81 3.4. Independent Stream . . . . . . . . . . . . . . . . . . . . 12 82 3.4.1. Independent Submission Experimental . . . . . . . . . 12 83 3.4.2. Independent Submission Historic . . . . . . . . . . . 13 84 3.4.3. Independent Submission Informational . . . . . . . . . 13 85 4. Informative References . . . . . . . . . . . . . . . . . . . . 14 86 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 14 87 A.1. Since draft-reschke-hab-00 . . . . . . . . . . . . . . . . 14 88 A.2. Since draft-reschke-hab-01 . . . . . . . . . . . . . . . . 14 89 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 14 91 1. Introduction 93 This document contains test renditions for the changes proposed in 94 [draft-iab-streams-headers-boilerplates], as generated by an 95 experimental version of rfc2629.xslt (see 96 ). 97 Its purpose is to illustrate the resulting text for all the 98 variations of the various input parameters, and to track the changes 99 applied to the proposal during the RFC-Editor's publication process. 101 This draft has been updated to produce the text proposed by the RFC 102 Editor during the AUTH48 phase for RFC 5741-to-be, as of 2009-12-17. 104 2. Implementation Status for Xml2Rfc 106 Please join the xml2rfc mailing list 107 () for 108 discussion of changes to the RFC 2629 vocabulary ([RFC2629]). 110 2.1. rfc2629.xslt (XML -> XSLT -> (X)HTML|XSL-FO) 112 The examples below were generated with an experimental version of 113 rfc2629.xslt (see 114 ). 116 2.2. xml2rfc.tcl (XML -> TCL -> TXT|HTML) 118 At the time of this writing, there was no work scheduled for updating 119 xml2rfc, thus no direct conversion of XML source to TXT files is 120 available (see ). 122 3. Test Renditions 124 3.1. IETF Stream 126 3.1.1. IETF Standards Track w/ consensus 128 3.1.1.1. Header (Left Column) 130 Internet Engineering Task Force (IETF) 131 Request for Comments: 9999 132 Category: Standards Track 134 3.1.1.2. Text of 'Status Of This Memo' 136 This is an Internet Standards Track document. 138 This document is a product of the Internet Engineering Task Force 139 (IETF). It represents the consensus of the IETF community. It has 140 received public review and has been approved for publication by the 141 Internet Engineering Steering Group (IESG). Further information on 142 Internet Standards is available in Section 2 of RFC 5741. 144 Information about the current status of this document, any errata, 145 and how to provide feedback on it may be obtained at 146 http://www.rfc-editor.org/info/rfc9999. 148 3.1.2. IETF Best Current Practice w/ consensus 150 3.1.2.1. Header (Left Column) 152 Internet Engineering Task Force (IETF) 153 Request for Comments: 9999 154 Category: Best Current Practice 156 3.1.2.2. Text of 'Status Of This Memo' 158 This memo documents an Internet Best Current Practice. 160 This document is a product of the Internet Engineering Task Force 161 (IETF). It represents the consensus of the IETF community. It has 162 received public review and has been approved for publication by the 163 Internet Engineering Steering Group (IESG). Further information on 164 BCPs is available in Section 2 of RFC 5741. 166 Information about the current status of this document, any errata, 167 and how to provide feedback on it may be obtained at 168 http://www.rfc-editor.org/info/rfc9999. 170 3.1.3. IETF Experimental w/ consensus 172 3.1.3.1. Header (Left Column) 174 Internet Engineering Task Force (IETF) 175 Request for Comments: 9999 176 Category: Experimental 178 3.1.3.2. Text of 'Status Of This Memo' 180 This document is not an Internet Standards Track specification; it is 181 published for examination, experimental implementation, and 182 evaluation. 184 This document defines an Experimental Protocol for the Internet 185 community. This document is a product of the Internet Engineering 186 Task Force (IETF). It represents the consensus of the IETF 187 community. It has received public review and has been approved for 188 publication by the Internet Engineering Steering Group (IESG). Not 189 all documents approved by the IESG are a candidate for any level of 190 Internet Standard; see Section 2 of RFC 5741. 192 Information about the current status of this document, any errata, 193 and how to provide feedback on it may be obtained at 194 http://www.rfc-editor.org/info/rfc9999. 196 3.1.4. IETF Experimental w/o consensus 198 3.1.4.1. Header (Left Column) 200 Internet Engineering Task Force (IETF) 201 Request for Comments: 9999 202 Category: Experimental 204 3.1.4.2. Text of 'Status Of This Memo' 206 This document is not an Internet Standards Track specification; it is 207 published for examination, experimental implementation, and 208 evaluation. 210 This document defines an Experimental Protocol for the Internet 211 community. This document is a product of the Internet Engineering 212 Task Force (IETF). It has been approved for publication by the 213 Internet Engineering Steering Group (IESG). Not all documents 214 approved by the IESG are a candidate for any level of Internet 215 Standard; see Section 2 of RFC 5741. 217 Information about the current status of this document, any errata, 218 and how to provide feedback on it may be obtained at 219 http://www.rfc-editor.org/info/rfc9999. 221 3.1.5. IETF Historic w/ consensus 222 3.1.5.1. Header (Left Column) 224 Internet Engineering Task Force (IETF) 225 Request for Comments: 9999 226 Category: Historic 228 3.1.5.2. Text of 'Status Of This Memo' 230 This document is not an Internet Standards Track specification; it is 231 published for the historical record. 233 This document defines a Historic Document for the Internet community. 234 This document is a product of the Internet Engineering Task Force 235 (IETF). It represents the consensus of the IETF community. It has 236 received public review and has been approved for publication by the 237 Internet Engineering Steering Group (IESG). Not all documents 238 approved by the IESG are a candidate for any level of Internet 239 Standard; see Section 2 of RFC 5741. 241 Information about the current status of this document, any errata, 242 and how to provide feedback on it may be obtained at 243 http://www.rfc-editor.org/info/rfc9999. 245 3.1.6. IETF Historic w/o consensus 247 3.1.6.1. Header (Left Column) 249 Internet Engineering Task Force (IETF) 250 Request for Comments: 9999 251 Category: Historic 253 3.1.6.2. Text of 'Status Of This Memo' 255 This document is not an Internet Standards Track specification; it is 256 published for the historical record. 258 This document defines a Historic Document for the Internet community. 259 This document is a product of the Internet Engineering Task Force 260 (IETF). It has been approved for publication by the Internet 261 Engineering Steering Group (IESG). Not all documents approved by the 262 IESG are a candidate for any level of Internet Standard; see Section 263 2 of RFC 5741. 265 Information about the current status of this document, any errata, 266 and how to provide feedback on it may be obtained at 267 http://www.rfc-editor.org/info/rfc9999. 269 3.1.7. IETF Informational w/ consensus 271 3.1.7.1. Header (Left Column) 273 Internet Engineering Task Force (IETF) 274 Request for Comments: 9999 275 Category: Informational 277 3.1.7.2. Text of 'Status Of This Memo' 279 This document is not an Internet Standards Track specification; it is 280 published for informational purposes. 282 This document is a product of the Internet Engineering Task Force 283 (IETF). It represents the consensus of the IETF community. It has 284 received public review and has been approved for publication by the 285 Internet Engineering Steering Group (IESG). Not all documents 286 approved by the IESG are a candidate for any level of Internet 287 Standard; see Section 2 of RFC 5741. 289 Information about the current status of this document, any errata, 290 and how to provide feedback on it may be obtained at 291 http://www.rfc-editor.org/info/rfc9999. 293 3.1.8. IETF Informational w/o consensus 295 3.1.8.1. Header (Left Column) 297 Internet Engineering Task Force (IETF) 298 Request for Comments: 9999 299 Category: Informational 301 3.1.8.2. Text of 'Status Of This Memo' 303 This document is not an Internet Standards Track specification; it is 304 published for informational purposes. 306 This document is a product of the Internet Engineering Task Force 307 (IETF). It has been approved for publication by the Internet 308 Engineering Steering Group (IESG). Not all documents approved by the 309 IESG are a candidate for any level of Internet Standard; see Section 310 2 of RFC 5741. 312 Information about the current status of this document, any errata, 313 and how to provide feedback on it may be obtained at 314 http://www.rfc-editor.org/info/rfc9999. 316 3.2. IAB Stream 318 3.2.1. IAB Historic 320 3.2.1.1. Header (Left Column) 322 Internet Architecture Board (IAB) 323 Request for Comments: 9999 324 Category: Historic 326 3.2.1.2. Text of 'Status Of This Memo' 328 This document is not an Internet Standards Track specification; it is 329 published for the historical record. 331 This document defines a Historic Document for the Internet community. 332 This document is a product of the Internet Architecture Board (IAB), 333 and represents information that the IAB has deemed valuable to 334 provide for permanent record. Documents approved for publication by 335 the IAB are not a candidate for any level of Internet Standard; see 336 Section 2 of RFC 5741. 338 Information about the current status of this document, any errata, 339 and how to provide feedback on it may be obtained at 340 http://www.rfc-editor.org/info/rfc9999. 342 3.2.2. IAB Informational 344 3.2.2.1. Header (Left Column) 346 Internet Architecture Board (IAB) 347 Request for Comments: 9999 348 Category: Informational 350 3.2.2.2. Text of 'Status Of This Memo' 352 This document is not an Internet Standards Track specification; it is 353 published for informational purposes. 355 This document is a product of the Internet Architecture Board (IAB), 356 and represents information that the IAB has deemed valuable to 357 provide for permanent record. Documents approved for publication by 358 the IAB are not a candidate for any level of Internet Standard; see 359 Section 2 of RFC 5741. 361 Information about the current status of this document, any errata, 362 and how to provide feedback on it may be obtained at 363 http://www.rfc-editor.org/info/rfc9999. 365 3.3. IRTF Stream 367 3.3.1. IRTF Experimental w/ RG consensus 369 3.3.1.1. Header (Left Column) 371 Internet Research Task Force (IRTF) 372 Request for Comments: 9999 373 Category: Experimental 375 3.3.1.2. Text of 'Status Of This Memo' 377 This document is not an Internet Standards Track specification; it is 378 published for examination, experimental implementation, and 379 evaluation. 381 This document defines an Experimental Protocol for the Internet 382 community. This document is a product of the Internet Research Task 383 Force (IRTF). The IRTF publishes the results of Internet-related 384 research and development activities. These results might not be 385 suitable for deployment. This RFC represents the consensus of the 386 Research Group of the Internet Research Task Force 387 (IRTF). Documents approved for publication by the IRSG are not a 388 candidate for any level of Internet Standard; see Section 2 of RFC 389 5741. 391 Information about the current status of this document, any errata, 392 and how to provide feedback on it may be obtained at 393 http://www.rfc-editor.org/info/rfc9999. 395 3.3.2. IRTF Experimental w/o RG consensus 397 3.3.2.1. Header (Left Column) 399 Internet Research Task Force (IRTF) 400 Request for Comments: 9999 401 Category: Experimental 403 3.3.2.2. Text of 'Status Of This Memo' 405 This document is not an Internet Standards Track specification; it is 406 published for examination, experimental implementation, and 407 evaluation. 409 This document defines an Experimental Protocol for the Internet 410 community. This document is a product of the Internet Research Task 411 Force (IRTF). The IRTF publishes the results of Internet-related 412 research and development activities. These results might not be 413 suitable for deployment. This RFC represents the individual 414 opinion(s) of one or more members of the Research Group 415 of the Internet Research Task Force (IRTF). Documents approved for 416 publication by the IRSG are not a candidate for any level of Internet 417 Standard; see Section 2 of RFC 5741. 419 Information about the current status of this document, any errata, 420 and how to provide feedback on it may be obtained at 421 http://www.rfc-editor.org/info/rfc9999. 423 3.3.3. IRTF Historic w/ RG consensus 425 3.3.3.1. Header (Left Column) 427 Internet Research Task Force (IRTF) 428 Request for Comments: 9999 429 Category: Historic 431 3.3.3.2. Text of 'Status Of This Memo' 433 This document is not an Internet Standards Track specification; it is 434 published for the historical record. 436 This document defines a Historic Document for the Internet community. 437 This document is a product of the Internet Research Task Force 438 (IRTF). The IRTF publishes the results of Internet-related research 439 and development activities. These results might not be suitable for 440 deployment. This RFC represents the consensus of the 441 Research Group of the Internet Research Task Force (IRTF). Documents 442 approved for publication by the IRSG are not a candidate for any 443 level of Internet Standard; see Section 2 of RFC 5741. 445 Information about the current status of this document, any errata, 446 and how to provide feedback on it may be obtained at 447 http://www.rfc-editor.org/info/rfc9999. 449 3.3.4. IRTF Historic w/o RG consensus 451 3.3.4.1. Header (Left Column) 453 Internet Research Task Force (IRTF) 454 Request for Comments: 9999 455 Category: Historic 457 3.3.4.2. Text of 'Status Of This Memo' 459 This document is not an Internet Standards Track specification; it is 460 published for the historical record. 462 This document defines a Historic Document for the Internet community. 463 This document is a product of the Internet Research Task Force 464 (IRTF). The IRTF publishes the results of Internet-related research 465 and development activities. These results might not be suitable for 466 deployment. This RFC represents the individual opinion(s) of one or 467 more members of the Research Group of the Internet 468 Research Task Force (IRTF). Documents approved for publication by 469 the IRSG are not a candidate for any level of Internet Standard; see 470 Section 2 of RFC 5741. 472 Information about the current status of this document, any errata, 473 and how to provide feedback on it may be obtained at 474 http://www.rfc-editor.org/info/rfc9999. 476 3.3.5. IRTF Informational w/ RG consensus 478 3.3.5.1. Header (Left Column) 480 Internet Research Task Force (IRTF) 481 Request for Comments: 9999 482 Category: Informational 484 3.3.5.2. Text of 'Status Of This Memo' 486 This document is not an Internet Standards Track specification; it is 487 published for informational purposes. 489 This document is a product of the Internet Research Task Force 490 (IRTF). The IRTF publishes the results of Internet-related research 491 and development activities. These results might not be suitable for 492 deployment. This RFC represents the consensus of the 493 Research Group of the Internet Research Task Force (IRTF). Documents 494 approved for publication by the IRSG are not a candidate for any 495 level of Internet Standard; see Section 2 of RFC 5741. 497 Information about the current status of this document, any errata, 498 and how to provide feedback on it may be obtained at 499 http://www.rfc-editor.org/info/rfc9999. 501 3.3.6. IRTF Informational w/o RG consensus 502 3.3.6.1. Header (Left Column) 504 Internet Research Task Force (IRTF) 505 Request for Comments: 9999 506 Category: Informational 508 3.3.6.2. Text of 'Status Of This Memo' 510 This document is not an Internet Standards Track specification; it is 511 published for informational purposes. 513 This document is a product of the Internet Research Task Force 514 (IRTF). The IRTF publishes the results of Internet-related research 515 and development activities. These results might not be suitable for 516 deployment. This RFC represents the individual opinion(s) of one or 517 more members of the Research Group of the Internet 518 Research Task Force (IRTF). Documents approved for publication by 519 the IRSG are not a candidate for any level of Internet Standard; see 520 Section 2 of RFC 5741. 522 Information about the current status of this document, any errata, 523 and how to provide feedback on it may be obtained at 524 http://www.rfc-editor.org/info/rfc9999. 526 3.4. Independent Stream 528 3.4.1. Independent Submission Experimental 530 3.4.1.1. Header (Left Column) 532 Independent Submission 533 Request for Comments: 9999 534 Category: Experimental 536 3.4.1.2. Text of 'Status Of This Memo' 538 This document is not an Internet Standards Track specification; it is 539 published for examination, experimental implementation, and 540 evaluation. 542 This document defines an Experimental Protocol for the Internet 543 community. This is a contribution to the RFC Series, independently 544 of any other RFC stream. The RFC Editor has chosen to publish this 545 document at its discretion and makes no statement about its value for 546 implementation or deployment. Documents approved for publication by 547 the RFC Editor are not a candidate for any level of Internet 548 Standard; see Section 2 of RFC 5741. 550 Information about the current status of this document, any errata, 551 and how to provide feedback on it may be obtained at 552 http://www.rfc-editor.org/info/rfc9999. 554 3.4.2. Independent Submission Historic 556 3.4.2.1. Header (Left Column) 558 Independent Submission 559 Request for Comments: 9999 560 Category: Historic 562 3.4.2.2. Text of 'Status Of This Memo' 564 This document is not an Internet Standards Track specification; it is 565 published for the historical record. 567 This document defines a Historic Document for the Internet community. 568 This is a contribution to the RFC Series, independently of any other 569 RFC stream. The RFC Editor has chosen to publish this document at 570 its discretion and makes no statement about its value for 571 implementation or deployment. Documents approved for publication by 572 the RFC Editor are not a candidate for any level of Internet 573 Standard; see Section 2 of RFC 5741. 575 Information about the current status of this document, any errata, 576 and how to provide feedback on it may be obtained at 577 http://www.rfc-editor.org/info/rfc9999. 579 3.4.3. Independent Submission Informational 581 3.4.3.1. Header (Left Column) 583 Independent Submission 584 Request for Comments: 9999 585 Category: Informational 587 3.4.3.2. Text of 'Status Of This Memo' 589 This document is not an Internet Standards Track specification; it is 590 published for informational purposes. 592 This is a contribution to the RFC Series, independently of any other 593 RFC stream. The RFC Editor has chosen to publish this document at 594 its discretion and makes no statement about its value for 595 implementation or deployment. Documents approved for publication by 596 the RFC Editor are not a candidate for any level of Internet 597 Standard; see Section 2 of RFC 5741. 599 Information about the current status of this document, any errata, 600 and how to provide feedback on it may be obtained at 601 http://www.rfc-editor.org/info/rfc9999. 603 4. Informative References 605 [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, 606 June 1999. 608 [draft-iab-streams-headers-boilerplates] 609 Daigle, L. and O. Kolkman, "On RFC Streams, Headers, and 610 Boilerplates", draft-iab-streams-headers-boilerplates-08 611 (work in progress), April 2009. 613 Appendix A. Change Log 615 A.1. Since draft-reschke-hab-00 617 Updated to RFC 5741-to-be as of 2009-12-17: (i) expanded submission 618 stream names, (2) replaced "RFC XXXX" by "RFC 5741". 620 A.2. Since draft-reschke-hab-01 622 Fix oversight: "Not all documents approved by the IESG are candidate 623 for any level of Internet Standards" -> "Not all documents approved 624 by the IESG are a candidate for any level of Internet Standard". 626 Author's Address 628 Julian F. Reschke 629 greenbytes GmbH 630 Hafenweg 16 631 Muenster, NW 48155 632 Germany 634 Email: julian.reschke@greenbytes.de 635 URI: http://greenbytes.de/tech/webdav/