Network Working Group J. Reschke
Internet-Draft greenbytes
Intended status: Informational December 17, 2009
Expires: June 20, 2010
Test Renditions for new RFC Headers & Boilerplate
draft-reschke-hab-01
Abstract
This document contains test renditions for the new header and
boilerplate values proposed in
draft-iab-streams-headers-boilerplates, and reports on the
implementation status for xml2rfc processors.
Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on June 20, 2010.
Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
Reschke Expires June 20, 2010 [Page 1]
Internet-Draft Headers & Boilerplate Tests December 2009
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Implementation Status for Xml2Rfc . . . . . . . . . . . . . . 3
2.1. rfc2629.xslt (XML -> XSLT -> (X)HTML|XSL-FO) . . . . . . . 3
2.2. xml2rfc.tcl (XML -> TCL -> TXT|HTML) . . . . . . . . . . . 3
3. Test Renditions . . . . . . . . . . . . . . . . . . . . . . . 3
3.1. IETF Stream . . . . . . . . . . . . . . . . . . . . . . . 3
3.1.1. IETF Standards Track w/ consensus . . . . . . . . . . 3
3.1.2. IETF Best Current Practice w/ consensus . . . . . . . 4
3.1.3. IETF Experimental w/ consensus . . . . . . . . . . . . 4
3.1.4. IETF Experimental w/o consensus . . . . . . . . . . . 5
3.1.5. IETF Historic w/ consensus . . . . . . . . . . . . . . 5
3.1.6. IETF Historic w/o consensus . . . . . . . . . . . . . 6
3.1.7. IETF Informational w/ consensus . . . . . . . . . . . 7
3.1.8. IETF Informational w/o consensus . . . . . . . . . . . 7
3.2. IAB Stream . . . . . . . . . . . . . . . . . . . . . . . . 8
3.2.1. IAB Historic . . . . . . . . . . . . . . . . . . . . . 8
3.2.2. IAB Informational . . . . . . . . . . . . . . . . . . 8
3.3. IRTF Stream . . . . . . . . . . . . . . . . . . . . . . . 9
3.3.1. IRTF Experimental w/ RG consensus . . . . . . . . . . 9
3.3.2. IRTF Experimental w/o RG consensus . . . . . . . . . . 9
3.3.3. IRTF Historic w/ RG consensus . . . . . . . . . . . . 10
3.3.4. IRTF Historic w/o RG consensus . . . . . . . . . . . . 10
3.3.5. IRTF Informational w/ RG consensus . . . . . . . . . . 11
3.3.6. IRTF Informational w/o RG consensus . . . . . . . . . 11
3.4. Independent Stream . . . . . . . . . . . . . . . . . . . . 12
3.4.1. Independent Submission Experimental . . . . . . . . . 12
3.4.2. Independent Submission Historic . . . . . . . . . . . 13
3.4.3. Independent Submission Informational . . . . . . . . . 13
4. Informative References . . . . . . . . . . . . . . . . . . . . 14
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 14
A.1. Since draft-reschke-hab-00 . . . . . . . . . . . . . . . . 14
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 14
Reschke Expires June 20, 2010 [Page 2]
Internet-Draft Headers & Boilerplate Tests December 2009
1. Introduction
This document contains test renditions for the changes proposed in
[draft-iab-streams-headers-boilerplates], as generated by an
experimental version of rfc2629.xslt (see
<http://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html>).
Its purpose is to illustrate the resulting text for all the
variations of the various input parameters, and to track the changes
applied to the proposal during the RFC-Editor's publication process.
This draft has been updated to produce the text proposed by the RFC
Editor during the AUTH48 phase for RFC 5741-to-be, as of 2009-12-17.
2. Implementation Status for Xml2Rfc
Please join the xml2rfc mailing list
(<http://lists.xml.resource.org/mailman/listinfo/xml2rfc>) for
discussion of changes to the RFC 2629 vocabulary ([RFC2629]).
2.1. rfc2629.xslt (XML -> XSLT -> (X)HTML|XSL-FO)
The examples below were generated with an experimental version of
rfc2629.xslt (see
<http://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html>).
2.2. xml2rfc.tcl (XML -> TCL -> TXT|HTML)
At the time of this writing, there was no work scheduled for updating
xml2rfc, thus no direct conversion of XML source to TXT files is
available (see <http://xml.resource.org>).
3. Test Renditions
3.1. IETF Stream
3.1.1. IETF Standards Track w/ consensus
3.1.1.1. Header (Left Column)
Internet Engineering Task Force (IETF)
Request for Comments: 9999
Category: Standards Track
Reschke Expires June 20, 2010 [Page 3]
Internet-Draft Headers & Boilerplate Tests December 2009
3.1.1.2. Text of 'Status Of This Memo'
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc9999.
3.1.2. IETF Best Current Practice w/ consensus
3.1.2.1. Header (Left Column)
Internet Engineering Task Force (IETF)
Request for Comments: 9999
Category: Best Current Practice
3.1.2.2. Text of 'Status Of This Memo'
This memo documents an Internet Best Current Practice.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
BCPs is available in Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc9999.
3.1.3. IETF Experimental w/ consensus
3.1.3.1. Header (Left Column)
Internet Engineering Task Force (IETF)
Request for Comments: 9999
Category: Experimental
Reschke Expires June 20, 2010 [Page 4]
Internet-Draft Headers & Boilerplate Tests December 2009
3.1.3.2. Text of 'Status Of This Memo'
This document is not an Internet Standards Track specification; it is
published for examination, experimental implementation, and
evaluation.
This document defines an Experimental Protocol for the Internet
community. This document is a product of the Internet Engineering
Task Force (IETF). It represents the consensus of the IETF
community. It has received public review and has been approved for
publication by the Internet Engineering Steering Group (IESG). Not
all documents approved by the IESG are candidate for any level of
Internet Standards; see Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc9999.
3.1.4. IETF Experimental w/o consensus
3.1.4.1. Header (Left Column)
Internet Engineering Task Force (IETF)
Request for Comments: 9999
Category: Experimental
3.1.4.2. Text of 'Status Of This Memo'
This document is not an Internet Standards Track specification; it is
published for examination, experimental implementation, and
evaluation.
This document defines an Experimental Protocol for the Internet
community. This document is a product of the Internet Engineering
Task Force (IETF). It has been approved for publication by the
Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are candidate for any level of Internet
Standards; see Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc9999.
3.1.5. IETF Historic w/ consensus
Reschke Expires June 20, 2010 [Page 5]
Internet-Draft Headers & Boilerplate Tests December 2009
3.1.5.1. Header (Left Column)
Internet Engineering Task Force (IETF)
Request for Comments: 9999
Category: Historic
3.1.5.2. Text of 'Status Of This Memo'
This document is not an Internet Standards Track specification; it is
published for the historical record.
This document defines a Historic Document for the Internet community.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are candidate for any level of Internet
Standards; see Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc9999.
3.1.6. IETF Historic w/o consensus
3.1.6.1. Header (Left Column)
Internet Engineering Task Force (IETF)
Request for Comments: 9999
Category: Historic
3.1.6.2. Text of 'Status Of This Memo'
This document is not an Internet Standards Track specification; it is
published for the historical record.
This document defines a Historic Document for the Internet community.
This document is a product of the Internet Engineering Task Force
(IETF). It has been approved for publication by the Internet
Engineering Steering Group (IESG). Not all documents approved by the
IESG are candidate for any level of Internet Standards; see Section 2
of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc9999.
Reschke Expires June 20, 2010 [Page 6]
Internet-Draft Headers & Boilerplate Tests December 2009
3.1.7. IETF Informational w/ consensus
3.1.7.1. Header (Left Column)
Internet Engineering Task Force (IETF)
Request for Comments: 9999
Category: Informational
3.1.7.2. Text of 'Status Of This Memo'
This document is not an Internet Standards Track specification; it is
published for informational purposes.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are candidate for any level of Internet
Standards; see Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc9999.
3.1.8. IETF Informational w/o consensus
3.1.8.1. Header (Left Column)
Internet Engineering Task Force (IETF)
Request for Comments: 9999
Category: Informational
3.1.8.2. Text of 'Status Of This Memo'
This document is not an Internet Standards Track specification; it is
published for informational purposes.
This document is a product of the Internet Engineering Task Force
(IETF). It has been approved for publication by the Internet
Engineering Steering Group (IESG). Not all documents approved by the
IESG are candidate for any level of Internet Standards; see Section 2
of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc9999.
Reschke Expires June 20, 2010 [Page 7]
Internet-Draft Headers & Boilerplate Tests December 2009
3.2. IAB Stream
3.2.1. IAB Historic
3.2.1.1. Header (Left Column)
Internet Architecture Board (IAB)
Request for Comments: 9999
Category: Historic
3.2.1.2. Text of 'Status Of This Memo'
This document is not an Internet Standards Track specification; it is
published for the historical record.
This document defines a Historic Document for the Internet community.
This document is a product of the Internet Architecture Board (IAB),
and represents information that the IAB has deemed valuable to
provide for permanent record. Documents approved for publication by
the IAB are not a candidate for any level of Internet Standard; see
Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc9999.
3.2.2. IAB Informational
3.2.2.1. Header (Left Column)
Internet Architecture Board (IAB)
Request for Comments: 9999
Category: Informational
3.2.2.2. Text of 'Status Of This Memo'
This document is not an Internet Standards Track specification; it is
published for informational purposes.
This document is a product of the Internet Architecture Board (IAB),
and represents information that the IAB has deemed valuable to
provide for permanent record. Documents approved for publication by
the IAB are not a candidate for any level of Internet Standard; see
Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc9999.
Reschke Expires June 20, 2010 [Page 8]
Internet-Draft Headers & Boilerplate Tests December 2009
3.3. IRTF Stream
3.3.1. IRTF Experimental w/ RG consensus
3.3.1.1. Header (Left Column)
Internet Research Task Force (IRTF)
Request for Comments: 9999
Category: Experimental
3.3.1.2. Text of 'Status Of This Memo'
This document is not an Internet Standards Track specification; it is
published for examination, experimental implementation, and
evaluation.
This document defines an Experimental Protocol for the Internet
community. This document is a product of the Internet Research Task
Force (IRTF). The IRTF publishes the results of Internet-related
research and development activities. These results might not be
suitable for deployment. This RFC represents the consensus of the
<insert_name> Research Group of the Internet Research Task Force
(IRTF). Documents approved for publication by the IRSG are not a
candidate for any level of Internet Standard; see Section 2 of RFC
5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc9999.
3.3.2. IRTF Experimental w/o RG consensus
3.3.2.1. Header (Left Column)
Internet Research Task Force (IRTF)
Request for Comments: 9999
Category: Experimental
3.3.2.2. Text of 'Status Of This Memo'
This document is not an Internet Standards Track specification; it is
published for examination, experimental implementation, and
evaluation.
This document defines an Experimental Protocol for the Internet
community. This document is a product of the Internet Research Task
Force (IRTF). The IRTF publishes the results of Internet-related
research and development activities. These results might not be
Reschke Expires June 20, 2010 [Page 9]
Internet-Draft Headers & Boilerplate Tests December 2009
suitable for deployment. This RFC represents the individual
opinion(s) of one or more members of the <insert_name> Research Group
of the Internet Research Task Force (IRTF). Documents approved for
publication by the IRSG are not a candidate for any level of Internet
Standard; see Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc9999.
3.3.3. IRTF Historic w/ RG consensus
3.3.3.1. Header (Left Column)
Internet Research Task Force (IRTF)
Request for Comments: 9999
Category: Historic
3.3.3.2. Text of 'Status Of This Memo'
This document is not an Internet Standards Track specification; it is
published for the historical record.
This document defines a Historic Document for the Internet community.
This document is a product of the Internet Research Task Force
(IRTF). The IRTF publishes the results of Internet-related research
and development activities. These results might not be suitable for
deployment. This RFC represents the consensus of the <insert_name>
Research Group of the Internet Research Task Force (IRTF). Documents
approved for publication by the IRSG are not a candidate for any
level of Internet Standard; see Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc9999.
3.3.4. IRTF Historic w/o RG consensus
3.3.4.1. Header (Left Column)
Internet Research Task Force (IRTF)
Request for Comments: 9999
Category: Historic
Reschke Expires June 20, 2010 [Page 10]
Internet-Draft Headers & Boilerplate Tests December 2009
3.3.4.2. Text of 'Status Of This Memo'
This document is not an Internet Standards Track specification; it is
published for the historical record.
This document defines a Historic Document for the Internet community.
This document is a product of the Internet Research Task Force
(IRTF). The IRTF publishes the results of Internet-related research
and development activities. These results might not be suitable for
deployment. This RFC represents the individual opinion(s) of one or
more members of the <insert_name> Research Group of the Internet
Research Task Force (IRTF). Documents approved for publication by
the IRSG are not a candidate for any level of Internet Standard; see
Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc9999.
3.3.5. IRTF Informational w/ RG consensus
3.3.5.1. Header (Left Column)
Internet Research Task Force (IRTF)
Request for Comments: 9999
Category: Informational
3.3.5.2. Text of 'Status Of This Memo'
This document is not an Internet Standards Track specification; it is
published for informational purposes.
This document is a product of the Internet Research Task Force
(IRTF). The IRTF publishes the results of Internet-related research
and development activities. These results might not be suitable for
deployment. This RFC represents the consensus of the <insert_name>
Research Group of the Internet Research Task Force (IRTF). Documents
approved for publication by the IRSG are not a candidate for any
level of Internet Standard; see Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc9999.
3.3.6. IRTF Informational w/o RG consensus
Reschke Expires June 20, 2010 [Page 11]
Internet-Draft Headers & Boilerplate Tests December 2009
3.3.6.1. Header (Left Column)
Internet Research Task Force (IRTF)
Request for Comments: 9999
Category: Informational
3.3.6.2. Text of 'Status Of This Memo'
This document is not an Internet Standards Track specification; it is
published for informational purposes.
This document is a product of the Internet Research Task Force
(IRTF). The IRTF publishes the results of Internet-related research
and development activities. These results might not be suitable for
deployment. This RFC represents the individual opinion(s) of one or
more members of the <insert_name> Research Group of the Internet
Research Task Force (IRTF). Documents approved for publication by
the IRSG are not a candidate for any level of Internet Standard; see
Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc9999.
3.4. Independent Stream
3.4.1. Independent Submission Experimental
3.4.1.1. Header (Left Column)
Independent Submission
Request for Comments: 9999
Category: Experimental
3.4.1.2. Text of 'Status Of This Memo'
This document is not an Internet Standards Track specification; it is
published for examination, experimental implementation, and
evaluation.
This document defines an Experimental Protocol for the Internet
community. This is a contribution to the RFC Series, independently
of any other RFC stream. The RFC Editor has chosen to publish this
document at its discretion and makes no statement about its value for
implementation or deployment. Documents approved for publication by
the RFC Editor are not a candidate for any level of Internet
Standard; see Section 2 of RFC 5741.
Reschke Expires June 20, 2010 [Page 12]
Internet-Draft Headers & Boilerplate Tests December 2009
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc9999.
3.4.2. Independent Submission Historic
3.4.2.1. Header (Left Column)
Independent Submission
Request for Comments: 9999
Category: Historic
3.4.2.2. Text of 'Status Of This Memo'
This document is not an Internet Standards Track specification; it is
published for the historical record.
This document defines a Historic Document for the Internet community.
This is a contribution to the RFC Series, independently of any other
RFC stream. The RFC Editor has chosen to publish this document at
its discretion and makes no statement about its value for
implementation or deployment. Documents approved for publication by
the RFC Editor are not a candidate for any level of Internet
Standard; see Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc9999.
3.4.3. Independent Submission Informational
3.4.3.1. Header (Left Column)
Independent Submission
Request for Comments: 9999
Category: Informational
3.4.3.2. Text of 'Status Of This Memo'
This document is not an Internet Standards Track specification; it is
published for informational purposes.
This is a contribution to the RFC Series, independently of any other
RFC stream. The RFC Editor has chosen to publish this document at
its discretion and makes no statement about its value for
implementation or deployment. Documents approved for publication by
the RFC Editor are not a candidate for any level of Internet
Standard; see Section 2 of RFC 5741.
Reschke Expires June 20, 2010 [Page 13]
Internet-Draft Headers & Boilerplate Tests December 2009
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc9999.
4. Informative References
[RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629,
June 1999.
[draft-iab-streams-headers-boilerplates]
Daigle, L. and O. Kolkman, "On RFC Streams, Headers, and
Boilerplates", draft-iab-streams-headers-boilerplates-08
(work in progress), April 2009.
Appendix A. Change Log
A.1. Since draft-reschke-hab-00
Updated to RFC 5741-to-be as of 2009-12-17: (i) expanded submission
stream names, (2) replaced "RFC XXXX" by "RFC 5741".
Author's Address
Julian F. Reschke
greenbytes GmbH
Hafenweg 16
Muenster, NW 48155
Germany
Email: julian.reschke@greenbytes.de
URI: http://greenbytes.de/tech/webdav/
Reschke Expires June 20, 2010 [Page 14]