<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc compact="yes"?>
<?rfc comments="yes"?>
<?rfc inline="yes"?>
<?rfc subcompact="no"?>
<?rfc toc="yes"?>
<?rfc-ext allow-markup-in-artwork="yes" ?>

<rfc xmlns:x="http://purl.org/net/xml2rfc/ext" xmlns:ed="http://greenbytes.de/2002/rfcedit" ipr="trust200902" docName="draft-reschke-hab-02" category="info" xml:lang="exp">
	<front>
  <title abbrev="Headers &amp; Boilerplate Tests">Test Renditions for new RFC Headers &amp; Boilerplate</title>

  <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke">
    <organization abbrev="greenbytes">greenbytes GmbH</organization>
    <address>
      <postal>
        <street>Hafenweg 16</street>
        <city>Muenster</city><region>NW</region><code>48155</code>
        <country>Germany</country>
      </postal>
      <email>julian.reschke@greenbytes.de</email>	
      <uri>http://greenbytes.de/tech/webdav/</uri>	
    </address>
  </author>

  <date month="December" year="2009" day="22"/>
  
  <abstract>
    <t>
      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.
    </t>
  </abstract>
  
  </front>

  <middle>





<section title="Introduction" anchor="introduction">
<t>
  This document contains test renditions for the changes proposed
  in  <xref target="draft-iab-streams-headers-boilerplates"/>, as generated
  by an experimental version of rfc2629.xslt (see <eref target="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.
</t>
<t>
  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. 
</t>
</section>  

<section title="Implementation Status for Xml2Rfc">
<t>
  Please join the xml2rfc mailing list (<eref target="http://lists.xml.resource.org/mailman/listinfo/xml2rfc"/>)
  for discussion of changes to the RFC 2629 vocabulary (<xref target="RFC2629"/>).
</t>

<section title="rfc2629.xslt (XML -> XSLT -> (X)HTML|XSL-FO)">
<t>
  The examples below were generated with an experimental version of rfc2629.xslt
  (see <eref target="http://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html"/>).
</t>
</section>
<section title="xml2rfc.tcl (XML -> TCL -> TXT|HTML)">
<t>
  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 <eref target="http://xml.resource.org"/>).
</t>
</section>
</section>

<?BEGININC hab.xml ?>
<section title="Test Renditions"><section title="IETF Stream"><section title="IETF Standards Track w/ consensus" anchor="IETF-std-cons"><section title="Header (Left Column)"><figure><artwork type="example">
Internet Engineering Task Force (IETF)
Request for Comments: 9999
Category: Standards Track
</artwork></figure></section><section title="Text of 'Status Of This Memo'"><t>This is an Internet Standards Track document.</t><t>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.</t><t>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.</t></section></section><section title="IETF Best Current Practice w/ consensus" anchor="IETF-bcp-cons"><section title="Header (Left Column)"><figure><artwork type="example">
Internet Engineering Task Force (IETF)
Request for Comments: 9999
Category: Best Current Practice
</artwork></figure></section><section title="Text of 'Status Of This Memo'"><t>This memo documents an Internet Best Current Practice.</t><t>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.</t><t>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.</t></section></section><section title="IETF Experimental w/ consensus" anchor="IETF-exp-cons"><section title="Header (Left Column)"><figure><artwork type="example">
Internet Engineering Task Force (IETF)
Request for Comments: 9999
Category: Experimental
</artwork></figure></section><section title="Text of 'Status Of This Memo'"><t>This document is not an Internet Standards Track specification; it is published for examination, experimental implementation, and evaluation.</t><t>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 a candidate for any level of Internet Standard; see Section 2 of RFC 5741.</t><t>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.</t></section></section><section title="IETF Experimental w/o consensus" anchor="IETF-exp"><section title="Header (Left Column)"><figure><artwork type="example">
Internet Engineering Task Force (IETF)
Request for Comments: 9999
Category: Experimental
</artwork></figure></section><section title="Text of 'Status Of This Memo'"><t>This document is not an Internet Standards Track specification; it is published for examination, experimental implementation, and evaluation.</t><t>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 a candidate for any level of Internet Standard; see Section 2 of RFC 5741.</t><t>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.</t></section></section><section title="IETF Historic w/ consensus" anchor="IETF-historic-cons"><section title="Header (Left Column)"><figure><artwork type="example">
Internet Engineering Task Force (IETF)
Request for Comments: 9999
Category: Historic
</artwork></figure></section><section title="Text of 'Status Of This Memo'"><t>This document is not an Internet Standards Track specification; it is published for the historical record.</t><t>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 a candidate for any level of Internet Standard; see Section 2 of RFC 5741.</t><t>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.</t></section></section><section title="IETF Historic w/o consensus" anchor="IETF-historic"><section title="Header (Left Column)"><figure><artwork type="example">
Internet Engineering Task Force (IETF)
Request for Comments: 9999
Category: Historic
</artwork></figure></section><section title="Text of 'Status Of This Memo'"><t>This document is not an Internet Standards Track specification; it is published for the historical record.</t><t>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 a candidate for any level of Internet Standard; see Section 2 of RFC 5741.</t><t>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.</t></section></section><section title="IETF Informational w/ consensus" anchor="IETF-info-cons"><section title="Header (Left Column)"><figure><artwork type="example">
Internet Engineering Task Force (IETF)
Request for Comments: 9999
Category: Informational
</artwork></figure></section><section title="Text of 'Status Of This Memo'"><t>This document is not an Internet Standards Track specification; it is published for informational purposes.</t><t>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 a candidate for any level of Internet Standard; see Section 2 of RFC 5741.</t><t>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.</t></section></section><section title="IETF Informational w/o consensus" anchor="IETF-info"><section title="Header (Left Column)"><figure><artwork type="example">
Internet Engineering Task Force (IETF)
Request for Comments: 9999
Category: Informational
</artwork></figure></section><section title="Text of 'Status Of This Memo'"><t>This document is not an Internet Standards Track specification; it is published for informational purposes.</t><t>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 a candidate for any level of Internet Standard; see Section 2 of RFC 5741.</t><t>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.</t></section></section></section><section title="IAB Stream"><section title="IAB Historic" anchor="IAB-historic"><section title="Header (Left Column)"><figure><artwork type="example">
Internet Architecture Board (IAB)
Request for Comments: 9999
Category: Historic
</artwork></figure></section><section title="Text of 'Status Of This Memo'"><t>This document is not an Internet Standards Track specification; it is published for the historical record.</t><t>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.</t><t>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.</t></section></section><section title="IAB Informational" anchor="IAB-info"><section title="Header (Left Column)"><figure><artwork type="example">
Internet Architecture Board (IAB)
Request for Comments: 9999
Category: Informational
</artwork></figure></section><section title="Text of 'Status Of This Memo'"><t>This document is not an Internet Standards Track specification; it is published for informational purposes.</t><t>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.</t><t>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.</t></section></section></section><section title="IRTF Stream"><section title="IRTF Experimental w/ RG consensus" anchor="IRTF-exp-cons"><section title="Header (Left Column)"><figure><artwork type="example">
Internet Research Task Force (IRTF)
Request for Comments: 9999
Category: Experimental
</artwork></figure></section><section title="Text of 'Status Of This Memo'"><t>This document is not an Internet Standards Track specification; it is published for examination, experimental implementation, and evaluation.</t><t>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 &lt;insert_name&gt; 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.</t><t>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.</t></section></section><section title="IRTF Experimental w/o RG consensus" anchor="IRTF-exp"><section title="Header (Left Column)"><figure><artwork type="example">
Internet Research Task Force (IRTF)
Request for Comments: 9999
Category: Experimental
</artwork></figure></section><section title="Text of 'Status Of This Memo'"><t>This document is not an Internet Standards Track specification; it is published for examination, experimental implementation, and evaluation.</t><t>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 individual opinion(s) of one or more members of the &lt;insert_name&gt; 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.</t><t>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.</t></section></section><section title="IRTF Historic w/ RG consensus" anchor="IRTF-historic-cons"><section title="Header (Left Column)"><figure><artwork type="example">
Internet Research Task Force (IRTF)
Request for Comments: 9999
Category: Historic
</artwork></figure></section><section title="Text of 'Status Of This Memo'"><t>This document is not an Internet Standards Track specification; it is published for the historical record.</t><t>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 &lt;insert_name&gt; 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.</t><t>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.</t></section></section><section title="IRTF Historic w/o RG consensus" anchor="IRTF-historic"><section title="Header (Left Column)"><figure><artwork type="example">
Internet Research Task Force (IRTF)
Request for Comments: 9999
Category: Historic
</artwork></figure></section><section title="Text of 'Status Of This Memo'"><t>This document is not an Internet Standards Track specification; it is published for the historical record.</t><t>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 &lt;insert_name&gt; 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.</t><t>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.</t></section></section><section title="IRTF Informational w/ RG consensus" anchor="IRTF-info-cons"><section title="Header (Left Column)"><figure><artwork type="example">
Internet Research Task Force (IRTF)
Request for Comments: 9999
Category: Informational
</artwork></figure></section><section title="Text of 'Status Of This Memo'"><t>This document is not an Internet Standards Track specification; it is published for informational purposes.</t><t>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 &lt;insert_name&gt; 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.</t><t>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.</t></section></section><section title="IRTF Informational w/o RG consensus" anchor="IRTF-info"><section title="Header (Left Column)"><figure><artwork type="example">
Internet Research Task Force (IRTF)
Request for Comments: 9999
Category: Informational
</artwork></figure></section><section title="Text of 'Status Of This Memo'"><t>This document is not an Internet Standards Track specification; it is published for informational purposes.</t><t>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 &lt;insert_name&gt; 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.</t><t>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.</t></section></section></section><section title="Independent Stream"><section title="Independent Submission Experimental" anchor="independent-exp"><section title="Header (Left Column)"><figure><artwork type="example">
Independent Submission
Request for Comments: 9999
Category: Experimental
</artwork></figure></section><section title="Text of 'Status Of This Memo'"><t>This document is not an Internet Standards Track specification; it is published for examination, experimental implementation, and evaluation.</t><t>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.</t><t>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.</t></section></section><section title="Independent Submission Historic" anchor="independent-historic"><section title="Header (Left Column)"><figure><artwork type="example">
Independent Submission
Request for Comments: 9999
Category: Historic
</artwork></figure></section><section title="Text of 'Status Of This Memo'"><t>This document is not an Internet Standards Track specification; it is published for the historical record.</t><t>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.</t><t>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.</t></section></section><section title="Independent Submission Informational" anchor="independent-info"><section title="Header (Left Column)"><figure><artwork type="example">
Independent Submission
Request for Comments: 9999
Category: Informational
</artwork></figure></section><section title="Text of 'Status Of This Memo'"><t>This document is not an Internet Standards Track specification; it is published for informational purposes.</t><t>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.</t><t>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.</t></section></section></section></section>
<?ENDINC hab.xml ?>

  </middle>
  <back>
  
<references title="Informative References">
  <reference anchor='draft-iab-streams-headers-boilerplates'>
    <front>
      <title>On RFC Streams, Headers, and Boilerplates</title>
      <author initials='L' surname='Daigle' fullname='Leslie Daigle'/>
      <author initials='O' surname='Kolkman' fullname='Olaf Kolkman'/>
      <date month='April' day='22' year='2009' />
    </front>
    <seriesInfo name='Internet-Draft' value='draft-iab-streams-headers-boilerplates-08' />
  </reference>

  <reference anchor='RFC2629'>
    <front>
      <title>Writing I-Ds and RFCs using XML</title>
      <author initials='M.T.' surname='Rose' fullname='Marshall T. Rose'>
        <organization>Invisible Worlds, Inc.</organization>
        <address>
          <email>mrose@not.invisible.net</email>
        </address>
      </author>
      <date year='1999' month='June' />
    </front>
    <seriesInfo name='RFC' value='2629' />
  </reference>

</references>

<section title="Change Log">
<section title="Since draft-reschke-hab-00">
<t>
  Updated to RFC 5741-to-be as of 2009-12-17: (i) expanded submission stream
  names, (2) replaced "RFC XXXX" by "RFC 5741".
</t>
</section>
<section title="Since draft-reschke-hab-01">
<t>
  Fix oversight: "Not all documents approved by the IESG are candidate
  for any level of Internet Standards" -> "Not all documents approved
  by the IESG are a candidate for any level of Internet
  Standard".
</t>
</section>
</section>
  
  </back>

</rfc>
