idnits 2.17.1 draft-reschke-hab-01.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 17, 2009) is 5216 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 17, 2009 5 Expires: June 20, 2010 7 Test Renditions for new RFC Headers & Boilerplate 8 draft-reschke-hab-01 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 20, 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 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 14 90 1. Introduction 92 This document contains test renditions for the changes proposed in 93 [draft-iab-streams-headers-boilerplates], as generated by an 94 experimental version of rfc2629.xslt (see 95 ). 96 Its purpose is to illustrate the resulting text for all the 97 variations of the various input parameters, and to track the changes 98 applied to the proposal during the RFC-Editor's publication process. 100 This draft has been updated to produce the text proposed by the RFC 101 Editor during the AUTH48 phase for RFC 5741-to-be, as of 2009-12-17. 103 2. Implementation Status for Xml2Rfc 105 Please join the xml2rfc mailing list 106 () for 107 discussion of changes to the RFC 2629 vocabulary ([RFC2629]). 109 2.1. rfc2629.xslt (XML -> XSLT -> (X)HTML|XSL-FO) 111 The examples below were generated with an experimental version of 112 rfc2629.xslt (see 113 ). 115 2.2. xml2rfc.tcl (XML -> TCL -> TXT|HTML) 117 At the time of this writing, there was no work scheduled for updating 118 xml2rfc, thus no direct conversion of XML source to TXT files is 119 available (see ). 121 3. Test Renditions 123 3.1. IETF Stream 125 3.1.1. IETF Standards Track w/ consensus 127 3.1.1.1. Header (Left Column) 129 Internet Engineering Task Force (IETF) 130 Request for Comments: 9999 131 Category: Standards Track 133 3.1.1.2. Text of 'Status Of This Memo' 135 This is an Internet Standards Track document. 137 This document is a product of the Internet Engineering Task Force 138 (IETF). It represents the consensus of the IETF community. It has 139 received public review and has been approved for publication by the 140 Internet Engineering Steering Group (IESG). Further information on 141 Internet Standards is available in Section 2 of RFC 5741. 143 Information about the current status of this document, any errata, 144 and how to provide feedback on it may be obtained at 145 http://www.rfc-editor.org/info/rfc9999. 147 3.1.2. IETF Best Current Practice w/ consensus 149 3.1.2.1. Header (Left Column) 151 Internet Engineering Task Force (IETF) 152 Request for Comments: 9999 153 Category: Best Current Practice 155 3.1.2.2. Text of 'Status Of This Memo' 157 This memo documents an Internet Best Current Practice. 159 This document is a product of the Internet Engineering Task Force 160 (IETF). It represents the consensus of the IETF community. It has 161 received public review and has been approved for publication by the 162 Internet Engineering Steering Group (IESG). Further information on 163 BCPs is available in Section 2 of RFC 5741. 165 Information about the current status of this document, any errata, 166 and how to provide feedback on it may be obtained at 167 http://www.rfc-editor.org/info/rfc9999. 169 3.1.3. IETF Experimental w/ consensus 171 3.1.3.1. Header (Left Column) 173 Internet Engineering Task Force (IETF) 174 Request for Comments: 9999 175 Category: Experimental 177 3.1.3.2. Text of 'Status Of This Memo' 179 This document is not an Internet Standards Track specification; it is 180 published for examination, experimental implementation, and 181 evaluation. 183 This document defines an Experimental Protocol for the Internet 184 community. This document is a product of the Internet Engineering 185 Task Force (IETF). It represents the consensus of the IETF 186 community. It has received public review and has been approved for 187 publication by the Internet Engineering Steering Group (IESG). Not 188 all documents approved by the IESG are candidate for any level of 189 Internet Standards; see Section 2 of RFC 5741. 191 Information about the current status of this document, any errata, 192 and how to provide feedback on it may be obtained at 193 http://www.rfc-editor.org/info/rfc9999. 195 3.1.4. IETF Experimental w/o consensus 197 3.1.4.1. Header (Left Column) 199 Internet Engineering Task Force (IETF) 200 Request for Comments: 9999 201 Category: Experimental 203 3.1.4.2. Text of 'Status Of This Memo' 205 This document is not an Internet Standards Track specification; it is 206 published for examination, experimental implementation, and 207 evaluation. 209 This document defines an Experimental Protocol for the Internet 210 community. This document is a product of the Internet Engineering 211 Task Force (IETF). It has been approved for publication by the 212 Internet Engineering Steering Group (IESG). Not all documents 213 approved by the IESG are candidate for any level of Internet 214 Standards; see Section 2 of RFC 5741. 216 Information about the current status of this document, any errata, 217 and how to provide feedback on it may be obtained at 218 http://www.rfc-editor.org/info/rfc9999. 220 3.1.5. IETF Historic w/ consensus 221 3.1.5.1. Header (Left Column) 223 Internet Engineering Task Force (IETF) 224 Request for Comments: 9999 225 Category: Historic 227 3.1.5.2. Text of 'Status Of This Memo' 229 This document is not an Internet Standards Track specification; it is 230 published for the historical record. 232 This document defines a Historic Document for the Internet community. 233 This document is a product of the Internet Engineering Task Force 234 (IETF). It represents the consensus of the IETF community. It has 235 received public review and has been approved for publication by the 236 Internet Engineering Steering Group (IESG). Not all documents 237 approved by the IESG are candidate for any level of Internet 238 Standards; see Section 2 of RFC 5741. 240 Information about the current status of this document, any errata, 241 and how to provide feedback on it may be obtained at 242 http://www.rfc-editor.org/info/rfc9999. 244 3.1.6. IETF Historic w/o consensus 246 3.1.6.1. Header (Left Column) 248 Internet Engineering Task Force (IETF) 249 Request for Comments: 9999 250 Category: Historic 252 3.1.6.2. Text of 'Status Of This Memo' 254 This document is not an Internet Standards Track specification; it is 255 published for the historical record. 257 This document defines a Historic Document for the Internet community. 258 This document is a product of the Internet Engineering Task Force 259 (IETF). It has been approved for publication by the Internet 260 Engineering Steering Group (IESG). Not all documents approved by the 261 IESG are candidate for any level of Internet Standards; see Section 2 262 of RFC 5741. 264 Information about the current status of this document, any errata, 265 and how to provide feedback on it may be obtained at 266 http://www.rfc-editor.org/info/rfc9999. 268 3.1.7. IETF Informational w/ consensus 270 3.1.7.1. Header (Left Column) 272 Internet Engineering Task Force (IETF) 273 Request for Comments: 9999 274 Category: Informational 276 3.1.7.2. Text of 'Status Of This Memo' 278 This document is not an Internet Standards Track specification; it is 279 published for informational purposes. 281 This document is a product of the Internet Engineering Task Force 282 (IETF). It represents the consensus of the IETF community. It has 283 received public review and has been approved for publication by the 284 Internet Engineering Steering Group (IESG). Not all documents 285 approved by the IESG are candidate for any level of Internet 286 Standards; see Section 2 of RFC 5741. 288 Information about the current status of this document, any errata, 289 and how to provide feedback on it may be obtained at 290 http://www.rfc-editor.org/info/rfc9999. 292 3.1.8. IETF Informational w/o consensus 294 3.1.8.1. Header (Left Column) 296 Internet Engineering Task Force (IETF) 297 Request for Comments: 9999 298 Category: Informational 300 3.1.8.2. Text of 'Status Of This Memo' 302 This document is not an Internet Standards Track specification; it is 303 published for informational purposes. 305 This document is a product of the Internet Engineering Task Force 306 (IETF). It has been approved for publication by the Internet 307 Engineering Steering Group (IESG). Not all documents approved by the 308 IESG are candidate for any level of Internet Standards; see Section 2 309 of RFC 5741. 311 Information about the current status of this document, any errata, 312 and how to provide feedback on it may be obtained at 313 http://www.rfc-editor.org/info/rfc9999. 315 3.2. IAB Stream 317 3.2.1. IAB Historic 319 3.2.1.1. Header (Left Column) 321 Internet Architecture Board (IAB) 322 Request for Comments: 9999 323 Category: Historic 325 3.2.1.2. Text of 'Status Of This Memo' 327 This document is not an Internet Standards Track specification; it is 328 published for the historical record. 330 This document defines a Historic Document for the Internet community. 331 This document is a product of the Internet Architecture Board (IAB), 332 and represents information that the IAB has deemed valuable to 333 provide for permanent record. Documents approved for publication by 334 the IAB are not a candidate for any level of Internet Standard; see 335 Section 2 of RFC 5741. 337 Information about the current status of this document, any errata, 338 and how to provide feedback on it may be obtained at 339 http://www.rfc-editor.org/info/rfc9999. 341 3.2.2. IAB Informational 343 3.2.2.1. Header (Left Column) 345 Internet Architecture Board (IAB) 346 Request for Comments: 9999 347 Category: Informational 349 3.2.2.2. Text of 'Status Of This Memo' 351 This document is not an Internet Standards Track specification; it is 352 published for informational purposes. 354 This document is a product of the Internet Architecture Board (IAB), 355 and represents information that the IAB has deemed valuable to 356 provide for permanent record. Documents approved for publication by 357 the IAB are not a candidate for any level of Internet Standard; see 358 Section 2 of RFC 5741. 360 Information about the current status of this document, any errata, 361 and how to provide feedback on it may be obtained at 362 http://www.rfc-editor.org/info/rfc9999. 364 3.3. IRTF Stream 366 3.3.1. IRTF Experimental w/ RG consensus 368 3.3.1.1. Header (Left Column) 370 Internet Research Task Force (IRTF) 371 Request for Comments: 9999 372 Category: Experimental 374 3.3.1.2. Text of 'Status Of This Memo' 376 This document is not an Internet Standards Track specification; it is 377 published for examination, experimental implementation, and 378 evaluation. 380 This document defines an Experimental Protocol for the Internet 381 community. This document is a product of the Internet Research Task 382 Force (IRTF). The IRTF publishes the results of Internet-related 383 research and development activities. These results might not be 384 suitable for deployment. This RFC represents the consensus of the 385 Research Group of the Internet Research Task Force 386 (IRTF). Documents approved for publication by the IRSG are not a 387 candidate for any level of Internet Standard; see Section 2 of RFC 388 5741. 390 Information about the current status of this document, any errata, 391 and how to provide feedback on it may be obtained at 392 http://www.rfc-editor.org/info/rfc9999. 394 3.3.2. IRTF Experimental w/o RG consensus 396 3.3.2.1. Header (Left Column) 398 Internet Research Task Force (IRTF) 399 Request for Comments: 9999 400 Category: Experimental 402 3.3.2.2. Text of 'Status Of This Memo' 404 This document is not an Internet Standards Track specification; it is 405 published for examination, experimental implementation, and 406 evaluation. 408 This document defines an Experimental Protocol for the Internet 409 community. This document is a product of the Internet Research Task 410 Force (IRTF). The IRTF publishes the results of Internet-related 411 research and development activities. These results might not be 412 suitable for deployment. This RFC represents the individual 413 opinion(s) of one or more members of the Research Group 414 of the Internet Research Task Force (IRTF). Documents approved for 415 publication by the IRSG are not a candidate for any level of Internet 416 Standard; see Section 2 of RFC 5741. 418 Information about the current status of this document, any errata, 419 and how to provide feedback on it may be obtained at 420 http://www.rfc-editor.org/info/rfc9999. 422 3.3.3. IRTF Historic w/ RG consensus 424 3.3.3.1. Header (Left Column) 426 Internet Research Task Force (IRTF) 427 Request for Comments: 9999 428 Category: Historic 430 3.3.3.2. Text of 'Status Of This Memo' 432 This document is not an Internet Standards Track specification; it is 433 published for the historical record. 435 This document defines a Historic Document for the Internet community. 436 This document is a product of the Internet Research Task Force 437 (IRTF). The IRTF publishes the results of Internet-related research 438 and development activities. These results might not be suitable for 439 deployment. This RFC represents the consensus of the 440 Research Group of the Internet Research Task Force (IRTF). Documents 441 approved for publication by the IRSG are not a candidate for any 442 level of Internet Standard; see Section 2 of RFC 5741. 444 Information about the current status of this document, any errata, 445 and how to provide feedback on it may be obtained at 446 http://www.rfc-editor.org/info/rfc9999. 448 3.3.4. IRTF Historic w/o RG consensus 450 3.3.4.1. Header (Left Column) 452 Internet Research Task Force (IRTF) 453 Request for Comments: 9999 454 Category: Historic 456 3.3.4.2. Text of 'Status Of This Memo' 458 This document is not an Internet Standards Track specification; it is 459 published for the historical record. 461 This document defines a Historic Document for the Internet community. 462 This document is a product of the Internet Research Task Force 463 (IRTF). The IRTF publishes the results of Internet-related research 464 and development activities. These results might not be suitable for 465 deployment. This RFC represents the individual opinion(s) of one or 466 more members of the Research Group of the Internet 467 Research Task Force (IRTF). Documents approved for publication by 468 the IRSG are not a candidate for any level of Internet Standard; see 469 Section 2 of RFC 5741. 471 Information about the current status of this document, any errata, 472 and how to provide feedback on it may be obtained at 473 http://www.rfc-editor.org/info/rfc9999. 475 3.3.5. IRTF Informational w/ RG consensus 477 3.3.5.1. Header (Left Column) 479 Internet Research Task Force (IRTF) 480 Request for Comments: 9999 481 Category: Informational 483 3.3.5.2. Text of 'Status Of This Memo' 485 This document is not an Internet Standards Track specification; it is 486 published for informational purposes. 488 This document is a product of the Internet Research Task Force 489 (IRTF). The IRTF publishes the results of Internet-related research 490 and development activities. These results might not be suitable for 491 deployment. This RFC represents the consensus of the 492 Research Group of the Internet Research Task Force (IRTF). Documents 493 approved for publication by the IRSG are not a candidate for any 494 level of Internet Standard; see Section 2 of RFC 5741. 496 Information about the current status of this document, any errata, 497 and how to provide feedback on it may be obtained at 498 http://www.rfc-editor.org/info/rfc9999. 500 3.3.6. IRTF Informational w/o RG consensus 501 3.3.6.1. Header (Left Column) 503 Internet Research Task Force (IRTF) 504 Request for Comments: 9999 505 Category: Informational 507 3.3.6.2. Text of 'Status Of This Memo' 509 This document is not an Internet Standards Track specification; it is 510 published for informational purposes. 512 This document is a product of the Internet Research Task Force 513 (IRTF). The IRTF publishes the results of Internet-related research 514 and development activities. These results might not be suitable for 515 deployment. This RFC represents the individual opinion(s) of one or 516 more members of the Research Group of the Internet 517 Research Task Force (IRTF). Documents approved for publication by 518 the IRSG are not a candidate for any level of Internet Standard; see 519 Section 2 of RFC 5741. 521 Information about the current status of this document, any errata, 522 and how to provide feedback on it may be obtained at 523 http://www.rfc-editor.org/info/rfc9999. 525 3.4. Independent Stream 527 3.4.1. Independent Submission Experimental 529 3.4.1.1. Header (Left Column) 531 Independent Submission 532 Request for Comments: 9999 533 Category: Experimental 535 3.4.1.2. Text of 'Status Of This Memo' 537 This document is not an Internet Standards Track specification; it is 538 published for examination, experimental implementation, and 539 evaluation. 541 This document defines an Experimental Protocol for the Internet 542 community. This is a contribution to the RFC Series, independently 543 of any other RFC stream. The RFC Editor has chosen to publish this 544 document at its discretion and makes no statement about its value for 545 implementation or deployment. Documents approved for publication by 546 the RFC Editor are not a candidate for any level of Internet 547 Standard; see Section 2 of RFC 5741. 549 Information about the current status of this document, any errata, 550 and how to provide feedback on it may be obtained at 551 http://www.rfc-editor.org/info/rfc9999. 553 3.4.2. Independent Submission Historic 555 3.4.2.1. Header (Left Column) 557 Independent Submission 558 Request for Comments: 9999 559 Category: Historic 561 3.4.2.2. Text of 'Status Of This Memo' 563 This document is not an Internet Standards Track specification; it is 564 published for the historical record. 566 This document defines a Historic Document for the Internet community. 567 This is a contribution to the RFC Series, independently of any other 568 RFC stream. The RFC Editor has chosen to publish this document at 569 its discretion and makes no statement about its value for 570 implementation or deployment. Documents approved for publication by 571 the RFC Editor are not a candidate for any level of Internet 572 Standard; see Section 2 of RFC 5741. 574 Information about the current status of this document, any errata, 575 and how to provide feedback on it may be obtained at 576 http://www.rfc-editor.org/info/rfc9999. 578 3.4.3. Independent Submission Informational 580 3.4.3.1. Header (Left Column) 582 Independent Submission 583 Request for Comments: 9999 584 Category: Informational 586 3.4.3.2. Text of 'Status Of This Memo' 588 This document is not an Internet Standards Track specification; it is 589 published for informational purposes. 591 This is a contribution to the RFC Series, independently of any other 592 RFC stream. The RFC Editor has chosen to publish this document at 593 its discretion and makes no statement about its value for 594 implementation or deployment. Documents approved for publication by 595 the RFC Editor are not a candidate for any level of Internet 596 Standard; see Section 2 of RFC 5741. 598 Information about the current status of this document, any errata, 599 and how to provide feedback on it may be obtained at 600 http://www.rfc-editor.org/info/rfc9999. 602 4. Informative References 604 [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, 605 June 1999. 607 [draft-iab-streams-headers-boilerplates] 608 Daigle, L. and O. Kolkman, "On RFC Streams, Headers, and 609 Boilerplates", draft-iab-streams-headers-boilerplates-08 610 (work in progress), April 2009. 612 Appendix A. Change Log 614 A.1. Since draft-reschke-hab-00 616 Updated to RFC 5741-to-be as of 2009-12-17: (i) expanded submission 617 stream names, (2) replaced "RFC XXXX" by "RFC 5741". 619 Author's Address 621 Julian F. Reschke 622 greenbytes GmbH 623 Hafenweg 16 624 Muenster, NW 48155 625 Germany 627 Email: julian.reschke@greenbytes.de 628 URI: http://greenbytes.de/tech/webdav/