Changeset 2301


Ignore:
Timestamp:
Jul 1, 2013, 1:47:55 AM (7 years ago)
Author:
julian.reschke@…
Message:

bump up document dates; update to latest version of rfc2629.xslt

Files:
22 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis-authscheme-registrations/latest/draft-ietf-httpbis-authscheme-registrations.html

    r2280 r2301  
    413413  }
    414414  @top-right {
    415        content: "June 2013";
     415       content: "July 2013";
    416416  }
    417417  @top-center {
     
    422422  }
    423423  @bottom-center {
    424        content: "Expires December 5, 2013";
     424       content: "Expires January 2, 2014";
    425425  }
    426426  @bottom-right {
     
    449449      <link rel="Appendix" title="A Initial Registry Contents" href="#rfc.section.A">
    450450      <link rel="Appendix" title="B Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.B">
    451       <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.597, 2013/05/27 06:39:42, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
     451      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.598, 2013/06/23 14:11:10, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
    452452      <link rel="schema.dct" href="http://purl.org/dc/terms/">
    453453      <meta name="dct.creator" content="Reschke, J. F.">
    454454      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-authscheme-registrations-latest">
    455       <meta name="dct.issued" scheme="ISO8601" content="2013-06-03">
     455      <meta name="dct.issued" scheme="ISO8601" content="2013-07-01">
    456456      <meta name="dct.abstract" content="This document registers Hypertext Transfer Protocol (HTTP) authentication schemes which have been defined in standards-track RFCs before the IANA HTTP Authentication Scheme Registry was established.">
    457457      <meta name="description" content="This document registers Hypertext Transfer Protocol (HTTP) authentication schemes which have been defined in standards-track RFCs before the IANA HTTP Authentication Scheme Registry was established.">
     
    470470            <tr>
    471471               <td class="left">Intended status: Informational</td>
    472                <td class="right">June 3, 2013</td>
     472               <td class="right">July 1, 2013</td>
    473473            </tr>
    474474            <tr>
    475                <td class="left">Expires: December 5, 2013</td>
     475               <td class="left">Expires: January 2, 2014</td>
    476476               <td class="right"></td>
    477477            </tr>
     
    499499         in progress”.
    500500      </p>
    501       <p>This Internet-Draft will expire on December 5, 2013.</p>
     501      <p>This Internet-Draft will expire on January 2, 2014.</p>
    502502      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    503503      <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    534534      <p id="rfc.section.2.p.1">There are no security considerations related to the registration itself.</p>
    535535      <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a id="iana.considerations" href="#iana.considerations">IANA Considerations</a></h1>
    536       <p id="rfc.section.3.p.1"> <a href="#initial.registry.contents" title="Initial Registry Contents">Appendix&nbsp;A</a> provides initial registrations of HTTP authentication schemes for the IANA HTTP Authentication Scheme registry at &lt;<a href="http://www.iana.org/assignments/http-authschemes">http://www.iana.org/assignments/http-authschemes</a>&gt; (see <a href="draft-ietf-httpbis-p7-auth-22.html#authentication.scheme.registry" title="Authentication Scheme Registry">Section 2.3</a> of <a href="#draft-ietf-httpbis-p7-auth"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[draft-ietf-httpbis-p7-auth]</cite></a>).
     536      <p id="rfc.section.3.p.1"><a href="#initial.registry.contents" title="Initial Registry Contents">Appendix&nbsp;A</a> provides initial registrations of HTTP authentication schemes for the IANA HTTP Authentication Scheme registry at &lt;<a href="http://www.iana.org/assignments/http-authschemes">http://www.iana.org/assignments/http-authschemes</a>&gt; (see <a href="draft-ietf-httpbis-p7-auth-22.html#authentication.scheme.registry" title="Authentication Scheme Registry">Section 2.3</a> of <a href="#draft-ietf-httpbis-p7-auth"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[draft-ietf-httpbis-p7-auth]</cite></a>).
    537537      </p>
    538538      <h1 id="rfc.references"><a href="#rfc.section.4" id="rfc.section.4">4.</a> Normative References
     
    617617      <p id="rfc.section.B.2.p.2">Closed issues: </p>
    618618      <ul>
    619          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/308">http://tools.ietf.org/wg/httpbis/trac/ticket/308</a>&gt;: "need to reserve 'negotiate' as auth scheme name"
     619         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/308">http://tools.ietf.org/wg/httpbis/trac/ticket/308</a>&gt;: "need to reserve 'negotiate' as auth scheme name"
    620620         </li>
    621621      </ul>
     
    627627      <p id="rfc.section.B.5.p.1">Closed issues: </p>
    628628      <ul>
    629          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/382">http://tools.ietf.org/wg/httpbis/trac/ticket/382</a>&gt;: "add OAuth auth scheme to initial registry contents"
     629         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/382">http://tools.ietf.org/wg/httpbis/trac/ticket/382</a>&gt;: "add OAuth auth scheme to initial registry contents"
    630630         </li>
    631631      </ul>
  • draft-ietf-httpbis-authscheme-registrations/latest/draft-ietf-httpbis-authscheme-registrations.xml

    r2280 r2301  
    4242  </author>
    4343
    44   <date month="June" year="2013"/>
     44  <date month="July" year="2013"/>
    4545  <workgroup>HTTPbis Working Group</workgroup>
    4646 
  • draft-ietf-httpbis-method-registrations/latest/draft-ietf-httpbis-method-registrations.html

    r2280 r2301  
    413413  }
    414414  @top-right {
    415        content: "June 2013";
     415       content: "July 2013";
    416416  }
    417417  @top-center {
     
    422422  }
    423423  @bottom-center {
    424        content: "Expires December 5, 2013";
     424       content: "Expires January 2, 2014";
    425425  }
    426426  @bottom-right {
     
    449449      <link rel="Appendix" title="A Initial Registry Contents" href="#rfc.section.A">
    450450      <link rel="Appendix" title="B Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.B">
    451       <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.597, 2013/05/27 06:39:42, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
     451      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.598, 2013/06/23 14:11:10, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
    452452      <link rel="schema.dct" href="http://purl.org/dc/terms/">
    453453      <meta name="dct.creator" content="Reschke, J. F.">
    454454      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-method-registrations-latest">
    455       <meta name="dct.issued" scheme="ISO8601" content="2013-06-03">
     455      <meta name="dct.issued" scheme="ISO8601" content="2013-07-01">
    456456      <meta name="dct.abstract" content="This document registers those Hypertext Transfer Protocol (HTTP) methods which have been defined in standards-track RFCs before the IANA HTTP Method Registry was established.">
    457457      <meta name="description" content="This document registers those Hypertext Transfer Protocol (HTTP) methods which have been defined in standards-track RFCs before the IANA HTTP Method Registry was established.">
     
    470470            <tr>
    471471               <td class="left">Intended status: Informational</td>
    472                <td class="right">June 3, 2013</td>
     472               <td class="right">July 1, 2013</td>
    473473            </tr>
    474474            <tr>
    475                <td class="left">Expires: December 5, 2013</td>
     475               <td class="left">Expires: January 2, 2014</td>
    476476               <td class="right"></td>
    477477            </tr>
     
    499499         in progress”.
    500500      </p>
    501       <p>This Internet-Draft will expire on December 5, 2013.</p>
     501      <p>This Internet-Draft will expire on January 2, 2014.</p>
    502502      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    503503      <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    539539      <p id="rfc.section.2.p.1">There are no security considerations related to the registration itself.</p>
    540540      <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a id="iana.considerations" href="#iana.considerations">IANA Considerations</a></h1>
    541       <p id="rfc.section.3.p.1"> <a href="#updated.registry.contents" title="Initial Registry Contents">Appendix&nbsp;A</a> provides initial registrations of HTTP method names for the IANA HTTP Method registry at &lt;<a href="http://www.iana.org/assignments/http-methods">http://www.iana.org/assignments/http-methods</a>&gt; (see <a href="../../draft-ietf-httpbis/22/p2-semantics.html#method.registry" title="Method Registry">Section 8.1</a> of <a href="#draft-ietf-httpbis-p2-semantics"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[draft-ietf-httpbis-p2-semantics]</cite></a>).
     541      <p id="rfc.section.3.p.1"><a href="#updated.registry.contents" title="Initial Registry Contents">Appendix&nbsp;A</a> provides initial registrations of HTTP method names for the IANA HTTP Method registry at &lt;<a href="http://www.iana.org/assignments/http-methods">http://www.iana.org/assignments/http-methods</a>&gt; (see <a href="../../draft-ietf-httpbis/22/p2-semantics.html#method.registry" title="Method Registry">Section 8.1</a> of <a href="#draft-ietf-httpbis-p2-semantics"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[draft-ietf-httpbis-p2-semantics]</cite></a>).
    542542      </p>
    543543      <h1 id="rfc.references"><a href="#rfc.section.4" id="rfc.section.4">4.</a> Normative References
     
    829829      <p id="rfc.section.B.10.p.1">Closed issues: </p>
    830830      <ul>
    831          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/377">http://tools.ietf.org/wg/httpbis/trac/ticket/377</a>&gt;: "what is the idempotency of LINK and UNLINK?"
     831         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/377">http://tools.ietf.org/wg/httpbis/trac/ticket/377</a>&gt;: "what is the idempotency of LINK and UNLINK?"
    832832         </li>
    833833      </ul>
  • draft-ietf-httpbis-method-registrations/latest/draft-ietf-httpbis-method-registrations.xml

    r2280 r2301  
    4242  </author>
    4343
    44   <date month="June" year="2013"/>
     44  <date month="July" year="2013"/>
    4545  <workgroup>HTTPbis Working Group</workgroup>
    4646 
  • draft-ietf-httpbis/latest/p1-messaging.html

    r2300 r2301  
    440440  }
    441441  @top-right {
    442        content: "June 2013";
     442       content: "July 2013";
    443443  }
    444444  @top-center {
     
    449449  }
    450450  @bottom-center {
    451        content: "Expires December 25, 2013";
     451       content: "Expires January 2, 2014";
    452452  }
    453453  @bottom-right {
     
    486486      <link rel="Appendix" title="D Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.D">
    487487      <link href="p2-semantics.html" rel="next">
    488       <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.597, 2013/05/27 06:39:42, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
     488      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.598, 2013/06/23 14:11:10, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
    489489      <link rel="schema.dct" href="http://purl.org/dc/terms/">
    490490      <meta name="dct.creator" content="Fielding, R.">
    491491      <meta name="dct.creator" content="Reschke, J. F.">
    492492      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest">
    493       <meta name="dct.issued" scheme="ISO8601" content="2013-06-23">
     493      <meta name="dct.issued" scheme="ISO8601" content="2013-07-01">
    494494      <meta name="dct.replaces" content="urn:ietf:rfc:2145">
    495495      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
     
    520520            <tr>
    521521               <td class="left">Intended status: Standards Track</td>
    522                <td class="right">June 23, 2013</td>
     522               <td class="right">July 1, 2013</td>
    523523            </tr>
    524524            <tr>
    525                <td class="left">Expires: December 25, 2013</td>
     525               <td class="left">Expires: January 2, 2014</td>
    526526               <td class="right"></td>
    527527            </tr>
     
    551551         in progress”.
    552552      </p>
    553       <p>This Internet-Draft will expire on December 25, 2013.</p>
     553      <p>This Internet-Draft will expire on January 2, 2014.</p>
    554554      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    555555      <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    775775      </p>
    776776      <div id="core.rules">
    777          <p id="rfc.section.1.2.p.2">                        The following core rules are included by reference, as defined in <a href="#RFC5234" id="rfc.xref.RFC5234.2"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>, <a href="http://tools.ietf.org/html/rfc5234#appendix-B.1">Appendix B.1</a>: ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double quote), HEXDIG
     777         <p id="rfc.section.1.2.p.2">            The following core rules are included by reference, as defined in <a href="#RFC5234" id="rfc.xref.RFC5234.2"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>, <a href="http://tools.ietf.org/html/rfc5234#appendix-B.1">Appendix B.1</a>: ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double quote), HEXDIG
    778778            (hexadecimal 0-9/A-F/a-f), HTAB (horizontal tab), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), and VCHAR
    779779            (any visible <a href="#USASCII" id="rfc.xref.USASCII.1"><cite title="Coded Character Set -- 7-bit American Standard Code for Information Interchange">[USASCII]</cite></a> character).
     
    876876         often based on dynamic configuration for load balancing.
    877877      </p>
    878       <p id="rfc.section.2.3.p.4"> <span id="rfc.iref.u.2"></span><span id="rfc.iref.d.1"></span> <span id="rfc.iref.i.2"></span><span id="rfc.iref.o.2"></span> We use the terms "<dfn>upstream</dfn>" and "<dfn>downstream</dfn>" to describe various requirements in relation to the directional flow of a message: all messages flow from upstream to downstream.
     878      <p id="rfc.section.2.3.p.4"><span id="rfc.iref.u.2"></span><span id="rfc.iref.d.1"></span> <span id="rfc.iref.i.2"></span><span id="rfc.iref.o.2"></span> We use the terms "<dfn>upstream</dfn>" and "<dfn>downstream</dfn>" to describe various requirements in relation to the directional flow of a message: all messages flow from upstream to downstream.
    879879         Likewise, we use the terms inbound and outbound to refer to directions in relation to the request path: "<dfn>inbound</dfn>" means toward the origin server and "<dfn>outbound</dfn>" means toward the user agent.
    880880      </p>
     
    885885         for the sake of security, annotation services, or shared caching.
    886886      </p>
    887       <p id="rfc.section.2.3.p.6"> <span id="rfc.iref.t.1"></span> <span id="rfc.iref.n.1"></span> An HTTP-to-HTTP proxy is called a "<dfn>transforming proxy</dfn>" if it is designed or configured to modify request or response messages in a semantically meaningful way (i.e., modifications,
     887      <p id="rfc.section.2.3.p.6"><span id="rfc.iref.t.1"></span> <span id="rfc.iref.n.1"></span> An HTTP-to-HTTP proxy is called a "<dfn>transforming proxy</dfn>" if it is designed or configured to modify request or response messages in a semantically meaningful way (i.e., modifications,
    888888         beyond those required by normal HTTP processing, that change the message in a way that would be significant to the original
    889889         sender or potentially significant to downstream recipients). For example, a transforming proxy might be acting as a shared
     
    893893         a given message, we use the term "<dfn>non-transforming proxy</dfn>" to target requirements that preserve HTTP message semantics. See <a href="p2-semantics.html#status.203" title="203 Non-Authoritative Information">Section 6.3.4</a> of <a href="#Part2" id="rfc.xref.Part2.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a> and <a href="p6-cache.html#header.warning" title="Warning">Section 7.5</a> of <a href="#Part6" id="rfc.xref.Part6.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a> for status and warning codes related to transformations.
    894894      </p>
    895       <p id="rfc.section.2.3.p.7"><span id="rfc.iref.g.13"></span><span id="rfc.iref.r.4"></span>  <span id="rfc.iref.a.1"></span> A "<dfn>gateway</dfn>" (a.k.a., "<dfn>reverse proxy</dfn>") is an intermediary that acts as an origin server for the outbound connection, but translates received requests and forwards
     895      <p id="rfc.section.2.3.p.7"><span id="rfc.iref.g.13"></span><span id="rfc.iref.r.4"></span> <span id="rfc.iref.a.1"></span> A "<dfn>gateway</dfn>" (a.k.a., "<dfn>reverse proxy</dfn>") is an intermediary that acts as an origin server for the outbound connection, but translates received requests and forwards
    896896         them inbound to another server or servers. Gateways are often used to encapsulate legacy or untrusted information services,
    897897         to improve server performance through "<dfn>accelerator</dfn>" caching, and to enable partitioning or load balancing of HTTP services across multiple machines.
     
    907907         when Transport Layer Security (TLS, <a href="#RFC5246" id="rfc.xref.RFC5246.1"><cite title="The Transport Layer Security (TLS) Protocol Version 1.2">[RFC5246]</cite></a>) is used to establish confidential communication through a shared firewall proxy.
    908908      </p>
    909       <p id="rfc.section.2.3.p.10"><span id="rfc.iref.i.3"></span>  <span id="rfc.iref.t.3"></span> <span id="rfc.iref.c.3"></span> The above categories for intermediary only consider those acting as participants in the HTTP communication. There are also
     909      <p id="rfc.section.2.3.p.10"><span id="rfc.iref.i.3"></span> <span id="rfc.iref.t.3"></span> <span id="rfc.iref.c.3"></span> The above categories for intermediary only consider those acting as participants in the HTTP communication. There are also
    910910         intermediaries that can act on lower layers of the network protocol stack, filtering or redirecting HTTP traffic without the
    911911         knowledge or permission of message senders. Network intermediaries often introduce security flaws or interoperability problems
     
    12411241         of the combined field value; a proxy <em class="bcp14">MUST NOT</em> change the order of these field values when forwarding a message.
    12421242      </p>
    1243       <div class="note" id="rfc.section.3.2.2.p.4"> 
    1244          <p> <b>Note:</b> In practice, the "Set-Cookie" header field (<a href="#RFC6265" id="rfc.xref.RFC6265.2"><cite title="HTTP State Management Mechanism">[RFC6265]</cite></a>) often appears multiple times in a response message and does not use the list syntax, violating the above requirements on
     1243      <div class="note" id="rfc.section.3.2.2.p.4">
     1244         <p><b>Note:</b> In practice, the "Set-Cookie" header field (<a href="#RFC6265" id="rfc.xref.RFC6265.2"><cite title="HTTP State Management Mechanism">[RFC6265]</cite></a>) often appears multiple times in a response message and does not use the list syntax, violating the above requirements on
    12451245            multiple header fields with the same name. Since it cannot be combined into a single field-value, recipients ought to handle
    12461246            "Set-Cookie" as a special case while processing header fields. (See Appendix A.2.3 of <a href="#Kri2001" id="rfc.xref.Kri2001.1"><cite title="HTTP Cookies: Standards, Privacy, and Politics">[Kri2001]</cite></a> for details.)
     
    12671267      </div>
    12681268      <div id="rule.whitespace">
    1269          <p id="rfc.section.3.2.3.p.5">      </p>
     1269         <p id="rfc.section.3.2.3.p.5">   </p>
    12701270      </div>
    12711271      <div id="rfc.figure.u.19"></div><pre class="inline"><span id="rfc.iref.g.40"></span><span id="rfc.iref.g.41"></span><span id="rfc.iref.g.42"></span>  <a href="#rule.whitespace" class="smpl">OWS</a>            = *( <a href="#core.rules" class="smpl">SP</a> / <a href="#core.rules" class="smpl">HTAB</a> )
     
    13101310      <h3 id="rfc.section.3.2.6"><a href="#rfc.section.3.2.6">3.2.6</a>&nbsp;<a id="field.components" href="#field.components">Field value components</a></h3>
    13111311      <div id="rule.token.separators">
    1312          <p id="rfc.section.3.2.6.p.1">        Many HTTP header field values consist of words (token or quoted-string) separated by whitespace or special characters. These
     1312         <p id="rfc.section.3.2.6.p.1">    Many HTTP header field values consist of words (token or quoted-string) separated by whitespace or special characters. These
    13131313            special characters <em class="bcp14">MUST</em> be in a quoted string to be used within a parameter value (as defined in <a href="#transfer.codings" title="Transfer Codings">Section&nbsp;4</a>).
    13141314         </p>
     
    13271327                 / "]" / "?" / "=" / "{" / "}"
    13281328</pre><div id="rule.quoted-string">
    1329          <p id="rfc.section.3.2.6.p.3">      A string of text is parsed as a single word if it is quoted using double-quote marks.</p>
     1329         <p id="rfc.section.3.2.6.p.3">   A string of text is parsed as a single word if it is quoted using double-quote marks.</p>
    13301330      </div>
    13311331      <div id="rfc.figure.u.21"></div><pre class="inline"><span id="rfc.iref.g.47"></span><span id="rfc.iref.g.48"></span><span id="rfc.iref.g.49"></span>  <a href="#rule.quoted-string" class="smpl">quoted-string</a>  = <a href="#core.rules" class="smpl">DQUOTE</a> *( <a href="#rule.quoted-string" class="smpl">qdtext</a> / <a href="#rule.quoted-pair" class="smpl">quoted-pair</a> ) <a href="#core.rules" class="smpl">DQUOTE</a>
     
    13331333  <a href="#rule.quoted-string" class="smpl">obs-text</a>       = %x80-FF
    13341334</pre><div id="rule.quoted-pair">
    1335          <p id="rfc.section.3.2.6.p.5">  The backslash octet ("\") can be used as a single-octet quoting mechanism within quoted-string constructs:</p>
     1335         <p id="rfc.section.3.2.6.p.5"> The backslash octet ("\") can be used as a single-octet quoting mechanism within quoted-string constructs:</p>
    13361336      </div>
    13371337      <div id="rfc.figure.u.22"></div><pre class="inline"><span id="rfc.iref.g.50"></span>  <a href="#rule.quoted-pair" class="smpl">quoted-pair</a>    = "\" ( <a href="#core.rules" class="smpl">HTAB</a> / <a href="#core.rules" class="smpl">SP</a> / <a href="#core.rules" class="smpl">VCHAR</a> / <a href="#rule.quoted-string" class="smpl">obs-text</a> )
     
    13421342      </p>
    13431343      <div id="rule.comment">
    1344          <p id="rfc.section.3.2.6.p.9">    Comments can be included in some HTTP header fields by surrounding the comment text with parentheses. Comments are only allowed
     1344         <p id="rfc.section.3.2.6.p.9">  Comments can be included in some HTTP header fields by surrounding the comment text with parentheses. Comments are only allowed
    13451345            in fields containing "comment" as part of their field value definition.
    13461346         </p>
     
    13491349  <a href="#rule.comment" class="smpl">ctext</a>          = <a href="#core.rules" class="smpl">HTAB</a> / <a href="#core.rules" class="smpl">SP</a> / %x21-27 / %x2A-5B / %x5D-7E / <a href="#rule.quoted-string" class="smpl">obs-text</a>
    13501350</pre><div id="rule.quoted-cpair">
    1351          <p id="rfc.section.3.2.6.p.11">  The backslash octet ("\") can be used as a single-octet quoting mechanism within comment constructs:</p>
     1351         <p id="rfc.section.3.2.6.p.11"> The backslash octet ("\") can be used as a single-octet quoting mechanism within comment constructs:</p>
    13521352      </div>
    13531353      <div id="rfc.figure.u.24"></div><pre class="inline"><span id="rfc.iref.g.53"></span>  <a href="#rule.quoted-cpair" class="smpl">quoted-cpair</a>   = "\" ( <a href="#core.rules" class="smpl">HTAB</a> / <a href="#core.rules" class="smpl">SP</a> / <a href="#core.rules" class="smpl">VCHAR</a> / <a href="#rule.quoted-string" class="smpl">obs-text</a> )
     
    14411441         that decimal value prior to determining the message body length.
    14421442      </p>
    1443       <div class="note" id="rfc.section.3.3.2.p.13"> 
    1444          <p> <b>Note:</b> HTTP's use of Content-Length for message framing differs significantly from the same field's use in MIME, where it is an optional
     1443      <div class="note" id="rfc.section.3.3.2.p.13">
     1444         <p><b>Note:</b> HTTP's use of Content-Length for message framing differs significantly from the same field's use in MIME, where it is an optional
    14451445            field used only within the "message/external-body" media-type.
    14461446         </p>
     
    14491449      <h3 id="rfc.section.3.3.3"><a href="#rfc.section.3.3.3">3.3.3</a>&nbsp;<a id="message.body.length" href="#message.body.length">Message Body Length</a></h3>
    14501450      <p id="rfc.section.3.3.3.p.1">The length of a message body is determined by one of the following (in order of precedence):</p>
    1451       <p id="rfc.section.3.3.3.p.2"> </p>
     1451      <p id="rfc.section.3.3.3.p.2"></p>
    14521452      <ol>
    14531453         <li>
     
    15571557  <a href="#transfer.codings" class="smpl">transfer-extension</a> = <a href="#rule.token.separators" class="smpl">token</a> *( <a href="#rule.whitespace" class="smpl">OWS</a> ";" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#rule.parameter" class="smpl">transfer-parameter</a> )
    15581558</pre><div id="rule.parameter">
    1559          <p id="rfc.section.4.p.3">      Parameters are in the form of attribute/value pairs.</p>
     1559         <p id="rfc.section.4.p.3">   Parameters are in the form of attribute/value pairs.</p>
    15601560      </div>
    15611561      <div id="rfc.figure.u.31"></div><pre class="inline"><span id="rfc.iref.g.59"></span><span id="rfc.iref.g.60"></span><span id="rfc.iref.g.61"></span><span id="rfc.iref.g.62"></span><span id="rfc.iref.g.63"></span>  <a href="#rule.parameter" class="smpl">transfer-parameter</a> = <a href="#rule.parameter" class="smpl">attribute</a> <a href="#rule.whitespace" class="smpl">BWS</a> "=" <a href="#rule.whitespace" class="smpl">BWS</a> <a href="#rule.parameter" class="smpl">value</a>
     
    16531653      <p id="rfc.section.4.2.2.p.1">The "deflate" coding is a "zlib" data format <a href="#RFC1950" id="rfc.xref.RFC1950.1"><cite title="ZLIB Compressed Data Format Specification version 3.3">[RFC1950]</cite></a> containing a "deflate" compressed data stream <a href="#RFC1951" id="rfc.xref.RFC1951.1"><cite title="DEFLATE Compressed Data Format Specification version 1.3">[RFC1951]</cite></a> that uses a combination of the Lempel-Ziv (LZ77) compression algorithm and Huffman coding.
    16541654      </p>
    1655       <div class="note" id="rfc.section.4.2.2.p.2"> 
    1656          <p> <b>Note:</b> Some incorrect implementations send the "deflate" compressed data without the zlib wrapper.
     1655      <div class="note" id="rfc.section.4.2.2.p.2">
     1656         <p><b>Note:</b> Some incorrect implementations send the "deflate" compressed data without the zlib wrapper.
    16571657         </p>
    16581658      </div>
     
    17411741  <a href="#asterisk-form" class="smpl">asterisk-form</a>  = "*"
    17421742</pre><div id="origin-form">
    1743          <p id="rfc.section.5.3.p.3"><span id="rfc.iref.o.3"></span>  <b>origin-form</b>
     1743         <p id="rfc.section.5.3.p.3"><span id="rfc.iref.o.3"></span> <b>origin-form</b>
    17441744         </p>
    17451745      </div>
     
    17571757</pre><p id="rfc.section.5.3.p.9">followed by the remainder of the request message.</p>
    17581758      <div id="absolute-form">
    1759          <p id="rfc.section.5.3.p.10"><span id="rfc.iref.a.2"></span>  <b>absolute-form</b>
     1759         <p id="rfc.section.5.3.p.10"><span id="rfc.iref.a.2"></span> <b>absolute-form</b>
    17601760         </p>
    17611761      </div>
     
    17691769      </p>
    17701770      <div id="authority-form">
    1771          <p id="rfc.section.5.3.p.15"><span id="rfc.iref.a.3"></span>  <b>authority-form</b>
     1771         <p id="rfc.section.5.3.p.15"><span id="rfc.iref.a.3"></span> <b>authority-form</b>
    17721772         </p>
    17731773      </div>
     
    17761776      <div id="rfc.figure.u.41"></div><pre class="text2">CONNECT www.example.com:80 HTTP/1.1
    17771777</pre><div id="asterisk-form">
    1778          <p id="rfc.section.5.3.p.18"><span id="rfc.iref.a.4"></span>  <b>asterisk-form</b>
     1778         <p id="rfc.section.5.3.p.18"><span id="rfc.iref.a.4"></span> <b>asterisk-form</b>
    17791779         </p>
    17801780      </div>
     
    19961996</pre><p id="rfc.section.6.1.p.12">in either the request or the response header fields indicates that the connection <em class="bcp14">MUST</em> be closed after the current request/response is complete (<a href="#persistent.tear-down" id="rfc.xref.persistent.tear-down.1" title="Tear-down">Section&nbsp;6.6</a>).
    19971997      </p>
    1998       <p id="rfc.section.6.1.p.13">A client that does not support <a href="#persistent.connections" class="smpl">persistent connections</a>  <em class="bcp14">MUST</em> send the "close" connection option in every request message.
    1999       </p>
    2000       <p id="rfc.section.6.1.p.14">A server that does not support <a href="#persistent.connections" class="smpl">persistent connections</a>  <em class="bcp14">MUST</em> send the "close" connection option in every response message that does not have a <a href="p2-semantics.html#status.1xx" class="smpl">1xx (Informational)</a> status code.
     1998      <p id="rfc.section.6.1.p.13">A client that does not support <a href="#persistent.connections" class="smpl">persistent connections</a> <em class="bcp14">MUST</em> send the "close" connection option in every request message.
     1999      </p>
     2000      <p id="rfc.section.6.1.p.14">A server that does not support <a href="#persistent.connections" class="smpl">persistent connections</a> <em class="bcp14">MUST</em> send the "close" connection option in every response message that does not have a <a href="p2-semantics.html#status.1xx" class="smpl">1xx (Informational)</a> status code.
    20012001      </p>
    20022002      <h2 id="rfc.section.6.2"><a href="#rfc.section.6.2">6.2</a>&nbsp;<a id="persistent.establishment" href="#persistent.establishment">Establishment</a></h2>
     
    21952195                  <td class="left">http</td>
    21962196                  <td class="left">standard</td>
    2197                   <td class="left"> <a href="#header.connection" id="rfc.xref.header.connection.7" title="Connection">Section&nbsp;6.1</a>
     2197                  <td class="left"><a href="#header.connection" id="rfc.xref.header.connection.7" title="Connection">Section&nbsp;6.1</a>
    21982198                  </td>
    21992199               </tr>
     
    22022202                  <td class="left">http</td>
    22032203                  <td class="left">standard</td>
    2204                   <td class="left"> <a href="#header.content-length" id="rfc.xref.header.content-length.1" title="Content-Length">Section&nbsp;3.3.2</a>
     2204                  <td class="left"><a href="#header.content-length" id="rfc.xref.header.content-length.1" title="Content-Length">Section&nbsp;3.3.2</a>
    22052205                  </td>
    22062206               </tr>
     
    22092209                  <td class="left">http</td>
    22102210                  <td class="left">standard</td>
    2211                   <td class="left"> <a href="#header.host" id="rfc.xref.header.host.2" title="Host">Section&nbsp;5.4</a>
     2211                  <td class="left"><a href="#header.host" id="rfc.xref.header.host.2" title="Host">Section&nbsp;5.4</a>
    22122212                  </td>
    22132213               </tr>
     
    22162216                  <td class="left">http</td>
    22172217                  <td class="left">standard</td>
    2218                   <td class="left"> <a href="#header.te" id="rfc.xref.header.te.3" title="TE">Section&nbsp;4.3</a>
     2218                  <td class="left"><a href="#header.te" id="rfc.xref.header.te.3" title="TE">Section&nbsp;4.3</a>
    22192219                  </td>
    22202220               </tr>
     
    22232223                  <td class="left">http</td>
    22242224                  <td class="left">standard</td>
    2225                   <td class="left"> <a href="#header.trailer" id="rfc.xref.header.trailer.1" title="Trailer">Section&nbsp;4.1.1</a>
     2225                  <td class="left"><a href="#header.trailer" id="rfc.xref.header.trailer.1" title="Trailer">Section&nbsp;4.1.1</a>
    22262226                  </td>
    22272227               </tr>
     
    22302230                  <td class="left">http</td>
    22312231                  <td class="left">standard</td>
    2232                   <td class="left"> <a href="#header.transfer-encoding" id="rfc.xref.header.transfer-encoding.3" title="Transfer-Encoding">Section&nbsp;3.3.1</a>
     2232                  <td class="left"><a href="#header.transfer-encoding" id="rfc.xref.header.transfer-encoding.3" title="Transfer-Encoding">Section&nbsp;3.3.1</a>
    22332233                  </td>
    22342234               </tr>
     
    22372237                  <td class="left">http</td>
    22382238                  <td class="left">standard</td>
    2239                   <td class="left"> <a href="#header.upgrade" id="rfc.xref.header.upgrade.2" title="Upgrade">Section&nbsp;6.7</a>
     2239                  <td class="left"><a href="#header.upgrade" id="rfc.xref.header.upgrade.2" title="Upgrade">Section&nbsp;6.7</a>
    22402240                  </td>
    22412241               </tr>
     
    22442244                  <td class="left">http</td>
    22452245                  <td class="left">standard</td>
    2246                   <td class="left"> <a href="#header.via" id="rfc.xref.header.via.1" title="Via">Section&nbsp;5.7.1</a>
     2246                  <td class="left"><a href="#header.via" id="rfc.xref.header.via.1" title="Via">Section&nbsp;5.7.1</a>
    22472247                  </td>
    22482248               </tr>
     
    22682268                  <td class="left">http</td>
    22692269                  <td class="left">reserved</td>
    2270                   <td class="left"> <a href="#header.field.registration" title="Header Field Registration">Section&nbsp;7.1</a>
     2270                  <td class="left"><a href="#header.field.registration" title="Header Field Registration">Section&nbsp;7.1</a>
    22712271                  </td>
    22722272               </tr>
     
    23142314         for all "message" types regarding line length and encodings.
    23152315      </p>
    2316       <p id="rfc.section.7.3.1.p.2"> </p>
     2316      <p id="rfc.section.7.3.1.p.2"></p>
    23172317      <dl>
    23182318         <dt>Type name:</dt>
     
    23442344         <dt>Applications that use this media type:</dt>
    23452345         <dt>Additional information:</dt>
    2346          <dd> 
     2346         <dd>
    23472347            <dl>
    23482348               <dt>Magic number(s):</dt>
     
    23692369      <h3 id="rfc.section.7.3.2"><a href="#rfc.section.7.3.2">7.3.2</a>&nbsp;<a id="internet.media.type.application.http" href="#internet.media.type.application.http">Internet Media Type application/http</a></h3>
    23702370      <p id="rfc.section.7.3.2.p.1">The application/http type can be used to enclose a pipeline of one or more HTTP request or response messages (not intermixed).</p>
    2371       <p id="rfc.section.7.3.2.p.2"> </p>
     2371      <p id="rfc.section.7.3.2.p.2"></p>
    23722372      <dl>
    23732373         <dt>Type name:</dt>
     
    24012401         <dt>Applications that use this media type:</dt>
    24022402         <dt>Additional information:</dt>
    2403          <dd> 
     2403         <dd>
    24042404            <dl>
    24052405               <dt>Magic number(s):</dt>
     
    24542454                  <td class="left">chunked</td>
    24552455                  <td class="left">Transfer in a series of chunks</td>
    2456                   <td class="left"> <a href="#chunked.encoding" title="Chunked Transfer Coding">Section&nbsp;4.1</a>
     2456                  <td class="left"><a href="#chunked.encoding" title="Chunked Transfer Coding">Section&nbsp;4.1</a>
    24572457                  </td>
    24582458               </tr>
     
    24602460                  <td class="left">compress</td>
    24612461                  <td class="left">UNIX "compress" data format <a href="#Welch" id="rfc.xref.Welch.2"><cite title="A Technique for High Performance Data Compression">[Welch]</cite></a></td>
    2462                   <td class="left"> <a href="#compress.coding" title="Compress Coding">Section&nbsp;4.2.1</a>
     2462                  <td class="left"><a href="#compress.coding" title="Compress Coding">Section&nbsp;4.2.1</a>
    24632463                  </td>
    24642464               </tr>
     
    24672467                  <td class="left">"deflate" compressed data (<a href="#RFC1951" id="rfc.xref.RFC1951.2"><cite title="DEFLATE Compressed Data Format Specification version 1.3">[RFC1951]</cite></a>) inside the "zlib" data format (<a href="#RFC1950" id="rfc.xref.RFC1950.2"><cite title="ZLIB Compressed Data Format Specification version 3.3">[RFC1950]</cite></a>)
    24682468                  </td>
    2469                   <td class="left"> <a href="#deflate.coding" title="Deflate Coding">Section&nbsp;4.2.2</a>
     2469                  <td class="left"><a href="#deflate.coding" title="Deflate Coding">Section&nbsp;4.2.2</a>
    24702470                  </td>
    24712471               </tr>
     
    24732473                  <td class="left">gzip</td>
    24742474                  <td class="left">GZIP file format <a href="#RFC1952" id="rfc.xref.RFC1952.2"><cite title="GZIP file format specification version 4.3">[RFC1952]</cite></a></td>
    2475                   <td class="left"> <a href="#gzip.coding" title="Gzip Coding">Section&nbsp;4.2.3</a>
     2475                  <td class="left"><a href="#gzip.coding" title="Gzip Coding">Section&nbsp;4.2.3</a>
    24762476                  </td>
    24772477               </tr>
     
    24792479                  <td class="left">x-compress</td>
    24802480                  <td class="left">Deprecated (alias for compress)</td>
    2481                   <td class="left"> <a href="#compress.coding" title="Compress Coding">Section&nbsp;4.2.1</a>
     2481                  <td class="left"><a href="#compress.coding" title="Compress Coding">Section&nbsp;4.2.1</a>
    24822482                  </td>
    24832483               </tr>
     
    24852485                  <td class="left">x-gzip</td>
    24862486                  <td class="left">Deprecated (alias for gzip)</td>
    2487                   <td class="left"> <a href="#gzip.coding" title="Gzip Coding">Section&nbsp;4.2.3</a>
     2487                  <td class="left"><a href="#gzip.coding" title="Gzip Coding">Section&nbsp;4.2.3</a>
    24882488                  </td>
    24892489               </tr>
     
    26572657         <tr>
    26582658            <td class="reference"><b id="Part2">[Part2]</b></td>
    2659             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p2-semantics-latest (work in progress), June&nbsp;2013.
     2659            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p2-semantics-latest (work in progress), July&nbsp;2013.
    26602660            </td>
    26612661         </tr>
    26622662         <tr>
    26632663            <td class="reference"><b id="Part4">[Part4]</b></td>
    2664             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-latest (work in progress), June&nbsp;2013.
     2664            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-latest (work in progress), July&nbsp;2013.
    26652665            </td>
    26662666         </tr>
    26672667         <tr>
    26682668            <td class="reference"><b id="Part5">[Part5]</b></td>
    2669             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">Hypertext Transfer Protocol (HTTP/1.1): Range Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-latest (work in progress), June&nbsp;2013.
     2669            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">Hypertext Transfer Protocol (HTTP/1.1): Range Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-latest (work in progress), July&nbsp;2013.
    26702670            </td>
    26712671         </tr>
    26722672         <tr>
    26732673            <td class="reference"><b id="Part6">[Part6]</b></td>
    2674             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:mnot@mnot.net" title="Akamai">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">Hypertext Transfer Protocol (HTTP/1.1): Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-latest (work in progress), June&nbsp;2013.
     2674            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:mnot@mnot.net" title="Akamai">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">Hypertext Transfer Protocol (HTTP/1.1): Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-latest (work in progress), July&nbsp;2013.
    26752675            </td>
    26762676         </tr>
    26772677         <tr>
    26782678            <td class="reference"><b id="Part7">[Part7]</b></td>
    2679             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-latest">Hypertext Transfer Protocol (HTTP/1.1): Authentication</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p7-auth-latest (work in progress), June&nbsp;2013.
     2679            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-latest">Hypertext Transfer Protocol (HTTP/1.1): Authentication</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p7-auth-latest (work in progress), July&nbsp;2013.
    26802680            </td>
    26812681         </tr>
     
    30143014  ","
    30153015  ",   ,"
    3016 </pre><p id="rfc.section.B.p.15"> <a href="#collected.abnf" title="Collected ABNF">Appendix&nbsp;C</a> shows the collected ABNF, with the list rules expanded as explained above.
     3016</pre><p id="rfc.section.B.p.15"><a href="#collected.abnf" title="Collected ABNF">Appendix&nbsp;C</a> shows the collected ABNF, with the list rules expanded as explained above.
    30173017      </p>
    30183018      <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
     
    31473147      <p id="rfc.section.D.2.p.1">Closed issues: </p>
    31483148      <ul>
    3149          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/128">http://tools.ietf.org/wg/httpbis/trac/ticket/128</a>&gt;: "Cite HTTPS URI scheme definition" (the spec now includes the HTTPs scheme definition and thus updates RFC 2818)
    3150          </li>
    3151          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/389">http://tools.ietf.org/wg/httpbis/trac/ticket/389</a>&gt;: "mention of 'proxies' in section about caches"
    3152          </li>
    3153          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/390">http://tools.ietf.org/wg/httpbis/trac/ticket/390</a>&gt;: "use of ABNF terms from RFC 3986"
    3154          </li>
    3155          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/391">http://tools.ietf.org/wg/httpbis/trac/ticket/391</a>&gt;: "transferring URIs with userinfo in payload"
    3156          </li>
    3157          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/392">http://tools.ietf.org/wg/httpbis/trac/ticket/392</a>&gt;: "editorial improvements to message length definition"
    3158          </li>
    3159          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/395">http://tools.ietf.org/wg/httpbis/trac/ticket/395</a>&gt;: "Connection header field MUST vs SHOULD"
    3160          </li>
    3161          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/396">http://tools.ietf.org/wg/httpbis/trac/ticket/396</a>&gt;: "editorial improvements to persistent connections section"
    3162          </li>
    3163          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/397">http://tools.ietf.org/wg/httpbis/trac/ticket/397</a>&gt;: "URI normalization vs empty path"
    3164          </li>
    3165          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/408">http://tools.ietf.org/wg/httpbis/trac/ticket/408</a>&gt;: "p1 feedback"
    3166          </li>
    3167          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/409">http://tools.ietf.org/wg/httpbis/trac/ticket/409</a>&gt;: "is parsing OBS-FOLD mandatory?"
    3168          </li>
    3169          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/410">http://tools.ietf.org/wg/httpbis/trac/ticket/410</a>&gt;: "HTTPS and Shared Caching"
    3170          </li>
    3171          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/411">http://tools.ietf.org/wg/httpbis/trac/ticket/411</a>&gt;: "Requirements for recipients of ws between start-line and first header field"
    3172          </li>
    3173          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/412">http://tools.ietf.org/wg/httpbis/trac/ticket/412</a>&gt;: "SP and HT when being tolerant"
    3174          </li>
    3175          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/414">http://tools.ietf.org/wg/httpbis/trac/ticket/414</a>&gt;: "Message Parsing Strictness"
    3176          </li>
    3177          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/415">http://tools.ietf.org/wg/httpbis/trac/ticket/415</a>&gt;: "'Render'"
    3178          </li>
    3179          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/418">http://tools.ietf.org/wg/httpbis/trac/ticket/418</a>&gt;: "No-Transform"
    3180          </li>
    3181          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/419">http://tools.ietf.org/wg/httpbis/trac/ticket/419</a>&gt;: "p2 editorial feedback"
    3182          </li>
    3183          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/420">http://tools.ietf.org/wg/httpbis/trac/ticket/420</a>&gt;: "Content-Length SHOULD be sent"
    3184          </li>
    3185          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/431">http://tools.ietf.org/wg/httpbis/trac/ticket/431</a>&gt;: "origin-form does not allow path starting with "//""
    3186          </li>
    3187          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/433">http://tools.ietf.org/wg/httpbis/trac/ticket/433</a>&gt;: "ambiguity in part 1 example"
     3149         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/128">http://tools.ietf.org/wg/httpbis/trac/ticket/128</a>&gt;: "Cite HTTPS URI scheme definition" (the spec now includes the HTTPs scheme definition and thus updates RFC 2818)
     3150         </li>
     3151         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/389">http://tools.ietf.org/wg/httpbis/trac/ticket/389</a>&gt;: "mention of 'proxies' in section about caches"
     3152         </li>
     3153         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/390">http://tools.ietf.org/wg/httpbis/trac/ticket/390</a>&gt;: "use of ABNF terms from RFC 3986"
     3154         </li>
     3155         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/391">http://tools.ietf.org/wg/httpbis/trac/ticket/391</a>&gt;: "transferring URIs with userinfo in payload"
     3156         </li>
     3157         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/392">http://tools.ietf.org/wg/httpbis/trac/ticket/392</a>&gt;: "editorial improvements to message length definition"
     3158         </li>
     3159         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/395">http://tools.ietf.org/wg/httpbis/trac/ticket/395</a>&gt;: "Connection header field MUST vs SHOULD"
     3160         </li>
     3161         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/396">http://tools.ietf.org/wg/httpbis/trac/ticket/396</a>&gt;: "editorial improvements to persistent connections section"
     3162         </li>
     3163         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/397">http://tools.ietf.org/wg/httpbis/trac/ticket/397</a>&gt;: "URI normalization vs empty path"
     3164         </li>
     3165         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/408">http://tools.ietf.org/wg/httpbis/trac/ticket/408</a>&gt;: "p1 feedback"
     3166         </li>
     3167         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/409">http://tools.ietf.org/wg/httpbis/trac/ticket/409</a>&gt;: "is parsing OBS-FOLD mandatory?"
     3168         </li>
     3169         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/410">http://tools.ietf.org/wg/httpbis/trac/ticket/410</a>&gt;: "HTTPS and Shared Caching"
     3170         </li>
     3171         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/411">http://tools.ietf.org/wg/httpbis/trac/ticket/411</a>&gt;: "Requirements for recipients of ws between start-line and first header field"
     3172         </li>
     3173         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/412">http://tools.ietf.org/wg/httpbis/trac/ticket/412</a>&gt;: "SP and HT when being tolerant"
     3174         </li>
     3175         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/414">http://tools.ietf.org/wg/httpbis/trac/ticket/414</a>&gt;: "Message Parsing Strictness"
     3176         </li>
     3177         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/415">http://tools.ietf.org/wg/httpbis/trac/ticket/415</a>&gt;: "'Render'"
     3178         </li>
     3179         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/418">http://tools.ietf.org/wg/httpbis/trac/ticket/418</a>&gt;: "No-Transform"
     3180         </li>
     3181         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/419">http://tools.ietf.org/wg/httpbis/trac/ticket/419</a>&gt;: "p2 editorial feedback"
     3182         </li>
     3183         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/420">http://tools.ietf.org/wg/httpbis/trac/ticket/420</a>&gt;: "Content-Length SHOULD be sent"
     3184         </li>
     3185         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/431">http://tools.ietf.org/wg/httpbis/trac/ticket/431</a>&gt;: "origin-form does not allow path starting with "//""
     3186         </li>
     3187         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/433">http://tools.ietf.org/wg/httpbis/trac/ticket/433</a>&gt;: "ambiguity in part 1 example"
    31883188         </li>
    31893189      </ul>
     
    31913191      <p id="rfc.section.D.3.p.1">Closed issues: </p>
    31923192      <ul>
    3193          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/435">http://tools.ietf.org/wg/httpbis/trac/ticket/435</a>&gt;: "Part1 should have a reference to TCP (RFC 793)"
    3194          </li>
    3195          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/438">http://tools.ietf.org/wg/httpbis/trac/ticket/438</a>&gt;: "media type registration template issues"
    3196          </li>
    3197          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/442">http://tools.ietf.org/wg/httpbis/trac/ticket/442</a>&gt;: "BWS" (vs conformance)
    3198          </li>
    3199          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/444">http://tools.ietf.org/wg/httpbis/trac/ticket/444</a>&gt;: "obs-fold language"
    3200          </li>
    3201          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/445">http://tools.ietf.org/wg/httpbis/trac/ticket/445</a>&gt;: "Ordering in Upgrade"
    3202          </li>
    3203          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/446">http://tools.ietf.org/wg/httpbis/trac/ticket/446</a>&gt;: "p1 editorial feedback"
    3204          </li>
    3205          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/447">http://tools.ietf.org/wg/httpbis/trac/ticket/447</a>&gt;: "HTTP and TCP name delegation"
    3206          </li>
    3207          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/449">http://tools.ietf.org/wg/httpbis/trac/ticket/449</a>&gt;: "Receiving a higher minor HTTP version number"
    3208          </li>
    3209          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/451">http://tools.ietf.org/wg/httpbis/trac/ticket/451</a>&gt;: "HTTP(S) URIs and fragids"
    3210          </li>
    3211          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/457">http://tools.ietf.org/wg/httpbis/trac/ticket/457</a>&gt;: "Registering x-gzip and x-deflate"
    3212          </li>
    3213          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/460">http://tools.ietf.org/wg/httpbis/trac/ticket/460</a>&gt;: "Via and gateways"
    3214          </li>
    3215          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/465">http://tools.ietf.org/wg/httpbis/trac/ticket/465</a>&gt;: "Mention 203 Non-Authoritative Information in p1"
    3216          </li>
    3217          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/476">http://tools.ietf.org/wg/httpbis/trac/ticket/476</a>&gt;: "SHOULD and conformance"
    3218          </li>
    3219          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/477">http://tools.ietf.org/wg/httpbis/trac/ticket/477</a>&gt;: "Pipelining language"
    3220          </li>
    3221          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/482">http://tools.ietf.org/wg/httpbis/trac/ticket/482</a>&gt;: "proxy handling of a really bad Content-Length"
     3193         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/435">http://tools.ietf.org/wg/httpbis/trac/ticket/435</a>&gt;: "Part1 should have a reference to TCP (RFC 793)"
     3194         </li>
     3195         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/438">http://tools.ietf.org/wg/httpbis/trac/ticket/438</a>&gt;: "media type registration template issues"
     3196         </li>
     3197         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/442">http://tools.ietf.org/wg/httpbis/trac/ticket/442</a>&gt;: "BWS" (vs conformance)
     3198         </li>
     3199         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/444">http://tools.ietf.org/wg/httpbis/trac/ticket/444</a>&gt;: "obs-fold language"
     3200         </li>
     3201         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/445">http://tools.ietf.org/wg/httpbis/trac/ticket/445</a>&gt;: "Ordering in Upgrade"
     3202         </li>
     3203         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/446">http://tools.ietf.org/wg/httpbis/trac/ticket/446</a>&gt;: "p1 editorial feedback"
     3204         </li>
     3205         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/447">http://tools.ietf.org/wg/httpbis/trac/ticket/447</a>&gt;: "HTTP and TCP name delegation"
     3206         </li>
     3207         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/449">http://tools.ietf.org/wg/httpbis/trac/ticket/449</a>&gt;: "Receiving a higher minor HTTP version number"
     3208         </li>
     3209         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/451">http://tools.ietf.org/wg/httpbis/trac/ticket/451</a>&gt;: "HTTP(S) URIs and fragids"
     3210         </li>
     3211         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/457">http://tools.ietf.org/wg/httpbis/trac/ticket/457</a>&gt;: "Registering x-gzip and x-deflate"
     3212         </li>
     3213         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/460">http://tools.ietf.org/wg/httpbis/trac/ticket/460</a>&gt;: "Via and gateways"
     3214         </li>
     3215         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/465">http://tools.ietf.org/wg/httpbis/trac/ticket/465</a>&gt;: "Mention 203 Non-Authoritative Information in p1"
     3216         </li>
     3217         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/476">http://tools.ietf.org/wg/httpbis/trac/ticket/476</a>&gt;: "SHOULD and conformance"
     3218         </li>
     3219         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/477">http://tools.ietf.org/wg/httpbis/trac/ticket/477</a>&gt;: "Pipelining language"
     3220         </li>
     3221         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/482">http://tools.ietf.org/wg/httpbis/trac/ticket/482</a>&gt;: "proxy handling of a really bad Content-Length"
    32223222         </li>
    32233223      </ul>
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r2300 r2301  
    1313  <!ENTITY SHOULD-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHOULD NOT</bcp14>">
    1414  <!ENTITY ID-VERSION "latest">
    15   <!ENTITY ID-MONTH "June">
     15  <!ENTITY ID-MONTH "July">
    1616  <!ENTITY ID-YEAR "2013">
    1717  <!ENTITY mdash "&#8212;">
  • draft-ietf-httpbis/latest/p2-semantics.html

    r2294 r2301  
    440440  }
    441441  @top-right {
    442        content: "June 2013";
     442       content: "July 2013";
    443443  }
    444444  @top-center {
     
    449449  }
    450450  @bottom-center {
    451        content: "Expires December 18, 2013";
     451       content: "Expires January 2, 2014";
    452452  }
    453453  @bottom-right {
     
    489489      <link href="p1-messaging.html" rel="prev">
    490490      <link href="p4-conditional.html" rel="next">
    491       <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.597, 2013/05/27 06:39:42, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
     491      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.598, 2013/06/23 14:11:10, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
    492492      <link rel="schema.dct" href="http://purl.org/dc/terms/">
    493493      <meta name="dct.creator" content="Fielding, R.">
    494494      <meta name="dct.creator" content="Reschke, J. F.">
    495495      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
    496       <meta name="dct.issued" scheme="ISO8601" content="2013-06-16">
     496      <meta name="dct.issued" scheme="ISO8601" content="2013-07-01">
    497497      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    498498      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines the semantics of HTTP/1.1 messages, as expressed by request methods, request header fields, response status codes, and response header fields, along with the payload of messages (metadata and body content) and mechanisms for content negotiation.">
     
    522522            <tr>
    523523               <td class="left">Intended status: Standards Track</td>
    524                <td class="right">June 16, 2013</td>
     524               <td class="right">July 1, 2013</td>
    525525            </tr>
    526526            <tr>
    527                <td class="left">Expires: December 18, 2013</td>
     527               <td class="left">Expires: January 2, 2014</td>
    528528               <td class="right"></td>
    529529            </tr>
     
    553553         in progress”.
    554554      </p>
    555       <p>This Internet-Draft will expire on December 18, 2013.</p>
     555      <p>This Internet-Draft will expire on January 2, 2014.</p>
    556556      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    557557      <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    896896  <a href="#media.type" class="smpl">subtype</a>    = <a href="#imported.abnf" class="smpl">token</a>
    897897</pre><div id="rule.parameter">
    898          <p id="rfc.section.3.1.1.1.p.3">      The type/subtype <em class="bcp14">MAY</em> be followed by parameters in the form of attribute/value pairs.
     898         <p id="rfc.section.3.1.1.1.p.3">   The type/subtype <em class="bcp14">MAY</em> be followed by parameters in the form of attribute/value pairs.
    899899         </p>
    900900      </div>
     
    915915</pre><p id="rfc.section.3.1.1.1.p.8">Internet media types ought to be registered with IANA according to the procedures defined in <a href="#BCP13" id="rfc.xref.BCP13.1"><cite title="Media Type Specifications and Registration Procedures">[BCP13]</cite></a>.
    916916      </p>
    917       <div class="note" id="rfc.section.3.1.1.1.p.9"> 
    918          <p> <b>Note:</b> Unlike some similar constructs in other header fields, media type parameters do not allow whitespace (even "bad" whitespace)
     917      <div class="note" id="rfc.section.3.1.1.1.p.9">
     918         <p><b>Note:</b> Unlike some similar constructs in other header fields, media type parameters do not allow whitespace (even "bad" whitespace)
    919919            around the "=" character.
    920920         </p>
     
    10271027         other human beings. Computer languages are explicitly excluded. HTTP uses language tags within the <a href="#header.accept-language" class="smpl">Accept-Language</a> and <a href="#header.content-language" class="smpl">Content-Language</a> header fields.
    10281028      </p>
    1029       <p id="rfc.section.3.1.3.1.p.2"> <a href="#header.accept-language" class="smpl">Accept-Language</a> uses the looser language-range production defined in <a href="#header.accept-language" id="rfc.xref.header.accept-language.1" title="Accept-Language">Section&nbsp;5.3.5</a>, whereas <a href="#header.content-language" class="smpl">Content-Language</a> uses the stricter language-tag production defined below.
     1029      <p id="rfc.section.3.1.3.1.p.2"><a href="#header.accept-language" class="smpl">Accept-Language</a> uses the looser language-range production defined in <a href="#header.accept-language" id="rfc.xref.header.accept-language.1" title="Accept-Language">Section&nbsp;5.3.5</a>, whereas <a href="#header.content-language" class="smpl">Content-Language</a> uses the stricter language-tag production defined below.
    10301030      </p>
    10311031      <div id="rfc.figure.u.10"></div><pre class="inline"><span id="rfc.iref.g.12"></span>  <a href="#language.tags" class="smpl">language-tag</a> = &lt;Language-Tag, defined in <a href="#RFC5646" id="rfc.xref.RFC5646.2"><cite title="Tags for Identifying Languages">[RFC5646]</cite></a>, <a href="http://tools.ietf.org/html/rfc5646#section-2.1">Section 2.1</a>&gt;
     
    16881688      <h4 id="rfc.section.5.1.1.1"><a href="#rfc.section.5.1.1.1">5.1.1.1</a>&nbsp;<a id="use.of.the.100.status" href="#use.of.the.100.status">Use of the 100 (Continue) Status</a></h4>
    16891689      <p id="rfc.section.5.1.1.1.p.1">The only expectation defined by this specification is:</p>
    1690       <p id="rfc.section.5.1.1.1.p.2"> <dfn>100-continue</dfn>
     1690      <p id="rfc.section.5.1.1.1.p.2"><dfn>100-continue</dfn>
    16911691      </p>
    16921692      <ul class="empty">
     
    18621862         since it acts as a separator between the two parameter sets.
    18631863      </p>
    1864       <div class="note" id="rfc.section.5.3.2.p.5"> 
    1865          <p> <b>Note:</b> Use of the "q" parameter name to separate media type parameters from Accept extension parameters is due to historical practice.
     1864      <div class="note" id="rfc.section.5.3.2.p.5">
     1865         <p><b>Note:</b> Use of the "q" parameter name to separate media type parameters from Accept extension parameters is due to historical practice.
    18661866            Although this prevents any media type parameter named "q" from being used with a media range, such an event is believed to
    18671867            be unlikely given the lack of any "q" parameters in the IANA media type registry and the rare usage of any media type parameters
     
    18711871      <p id="rfc.section.5.3.2.p.6">The example</p>
    18721872      <div id="rfc.figure.u.24"></div><pre class="text">  Accept: audio/*; q=0.2, audio/basic
    1873 </pre><p id="rfc.section.5.3.2.p.8"> <em class="bcp14">SHOULD</em> be interpreted as "I prefer audio/basic, but send me any audio type if it is the best available after an 80% mark-down in
     1873</pre><p id="rfc.section.5.3.2.p.8"><em class="bcp14">SHOULD</em> be interpreted as "I prefer audio/basic, but send me any audio type if it is the best available after an 80% mark-down in
    18741874         quality".
    18751875      </p>
     
    19371937         </table>
    19381938      </div>
    1939       <p id="rfc.section.5.3.2.p.19"> <b>Note:</b> A user agent might be provided with a default set of quality values for certain media ranges. However, unless the user agent
     1939      <p id="rfc.section.5.3.2.p.19"><b>Note:</b> A user agent might be provided with a default set of quality values for certain media ranges. However, unless the user agent
    19401940         is a closed system that cannot interact with other rendering agents, this default set ought to be configurable by the user.
    19411941      </p>
     
    19961996         response have a content-coding that is listed as acceptable, the origin server <em class="bcp14">SHOULD</em> send a response without any content-coding.
    19971997      </p>
    1998       <div class="note" id="rfc.section.5.3.4.p.9"> 
    1999          <p> <b>Note:</b> Most HTTP/1.0 applications do not recognize or obey qvalues associated with content-codings. This means that qvalues might
     1998      <div class="note" id="rfc.section.5.3.4.p.9">
     1999         <p><b>Note:</b> Most HTTP/1.0 applications do not recognize or obey qvalues associated with content-codings. This means that qvalues might
    20002000            not work and are not permitted with x-gzip or x-compress.
    20012001         </p>
     
    20342034         preference. A user agent that does not provide such control to the user <em class="bcp14">MUST NOT</em> send an Accept-Language header field.
    20352035      </p>
    2036       <div class="note" id="rfc.section.5.3.5.p.11"> 
    2037          <p> <b>Note:</b> User agents ought to provide guidance to users when setting a preference, since users are rarely familiar with the details
     2036      <div class="note" id="rfc.section.5.3.5.p.11">
     2037         <p><b>Note:</b> User agents ought to provide guidance to users when setting a preference, since users are rarely familiar with the details
    20382038            of language matching as described above. For example, users might assume that on selecting "en-gb", they will be served any
    20392039            kind of English document if British English is not available. A user agent might suggest, in such a case, to add "en" to the
     
    21772177      </p>
    21782178      <ul>
    2179          <li> <a href="#status.1xx" class="smpl">1xx (Informational)</a>: The request was received, continuing process
    2180          </li>
    2181          <li> <a href="#status.2xx" class="smpl">2xx (Successful)</a>: The request was successfully received, understood, and accepted
    2182          </li>
    2183          <li> <a href="#status.3xx" class="smpl">3xx (Redirection)</a>: Further action needs to be taken in order to complete the request
    2184          </li>
    2185          <li> <a href="#status.4xx" class="smpl">4xx (Client Error)</a>: The request contains bad syntax or cannot be fulfilled
    2186          </li>
    2187          <li> <a href="#status.5xx" class="smpl">5xx (Server Error)</a>: The server failed to fulfill an apparently valid request
     2179         <li><a href="#status.1xx" class="smpl">1xx (Informational)</a>: The request was received, continuing process
     2180         </li>
     2181         <li><a href="#status.2xx" class="smpl">2xx (Successful)</a>: The request was successfully received, understood, and accepted
     2182         </li>
     2183         <li><a href="#status.3xx" class="smpl">3xx (Redirection)</a>: Further action needs to be taken in order to complete the request
     2184         </li>
     2185         <li><a href="#status.4xx" class="smpl">4xx (Client Error)</a>: The request contains bad syntax or cannot be fulfilled
     2186         </li>
     2187         <li><a href="#status.5xx" class="smpl">5xx (Server Error)</a>: The server failed to fulfill an apparently valid request
    21882188         </li>
    21892189      </ul>
     
    25642564         </li>
    25652565      </ol>
    2566       <div class="note" id="rfc.section.6.4.p.3"> 
    2567          <p> <b>Note:</b> In HTTP/1.0, the status codes <a href="#status.301" class="smpl">301 (Moved Permanently)</a> and <a href="#status.302" class="smpl">302 (Found)</a> were defined for the first type of redirect (<a href="#RFC1945" id="rfc.xref.RFC1945.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.0">[RFC1945]</cite></a>, <a href="http://tools.ietf.org/html/rfc1945#section-9.3">Section 9.3</a>). Early user agents split on whether the method applied to the redirect target would be the same as the original request
     2566      <div class="note" id="rfc.section.6.4.p.3">
     2567         <p><b>Note:</b> In HTTP/1.0, the status codes <a href="#status.301" class="smpl">301 (Moved Permanently)</a> and <a href="#status.302" class="smpl">302 (Found)</a> were defined for the first type of redirect (<a href="#RFC1945" id="rfc.xref.RFC1945.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.0">[RFC1945]</cite></a>, <a href="http://tools.ietf.org/html/rfc1945#section-9.3">Section 9.3</a>). Early user agents split on whether the method applied to the redirect target would be the same as the original request
    25682568            or would be rewritten as GET. Although HTTP originally defined the former semantics for <a href="#status.301" class="smpl">301</a> and <a href="#status.302" class="smpl">302</a> (to match its original implementation at CERN), and defined <a href="#status.303" class="smpl">303 (See Other)</a> to match the latter semantics, prevailing practice gradually converged on the latter semantics for <a href="#status.301" class="smpl">301</a> and <a href="#status.302" class="smpl">302</a> as well. The first revision of HTTP/1.1 added <a href="#status.307" class="smpl">307 (Temporary Redirect)</a> to indicate the former semantics without being impacted by divergent practice. Over 10 years later, most user agents still
    25692569            do method rewriting for <a href="#status.301" class="smpl">301</a> and <a href="#status.302" class="smpl">302</a>; therefore, this specification makes that behavior conformant when the original request is POST.
     
    25722572      <p id="rfc.section.6.4.p.4">Clients <em class="bcp14">SHOULD</em> detect and intervene in cyclical redirections (i.e., "infinite" redirection loops).
    25732573      </p>
    2574       <div class="note" id="rfc.section.6.4.p.5"> 
    2575          <p> <b>Note:</b> An earlier version of this specification recommended a maximum of five redirections (<a href="#RFC2068" id="rfc.xref.RFC2068.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>, <a href="http://tools.ietf.org/html/rfc2068#section-10.3">Section 10.3</a>). Content developers need to be aware that some clients might implement such a fixed limitation.
     2574      <div class="note" id="rfc.section.6.4.p.5">
     2575         <p><b>Note:</b> An earlier version of this specification recommended a maximum of five redirections (<a href="#RFC2068" id="rfc.xref.RFC2068.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>, <a href="http://tools.ietf.org/html/rfc2068#section-10.3">Section 10.3</a>). Content developers need to be aware that some clients might implement such a fixed limitation.
    25762576         </p>
    25772577      </div>
     
    25912591      <p id="rfc.section.6.4.1.p.4">A 300 response is cacheable unless otherwise indicated by the method definition or explicit cache controls (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.15"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
    25922592      </p>
    2593       <div class="note" id="rfc.section.6.4.1.p.5"> 
    2594          <p> <b>Note:</b> The original proposal for 300 defined the URI header field as providing a list of alternative representations, such that it
     2593      <div class="note" id="rfc.section.6.4.1.p.5">
     2594         <p><b>Note:</b> The original proposal for 300 defined the URI header field as providing a list of alternative representations, such that it
    25952595            would be usable for 200, 300, and 406 responses and be transferred in responses to the HEAD method. However, lack of deployment
    25962596            and disagreement over syntax led to both URI and Alternates (a subsequent proposal) being dropped from this specification.
     
    26072607         with a hyperlink to the new URI(s).
    26082608      </p>
    2609       <div class="note" id="rfc.section.6.4.2.p.3"> 
    2610          <p> <b>Note:</b> For historic reasons, user agents <em class="bcp14">MAY</em> change the request method from POST to GET for the subsequent request. If this behavior is undesired, status code <a href="#status.307" class="smpl">307 (Temporary Redirect)</a> can be used instead.
     2609      <div class="note" id="rfc.section.6.4.2.p.3">
     2610         <p><b>Note:</b> For historic reasons, user agents <em class="bcp14">MAY</em> change the request method from POST to GET for the subsequent request. If this behavior is undesired, status code <a href="#status.307" class="smpl">307 (Temporary Redirect)</a> can be used instead.
    26112611         </p>
    26122612      </div>
     
    26212621         with a hyperlink to the different URI(s).
    26222622      </p>
    2623       <div class="note" id="rfc.section.6.4.3.p.3"> 
    2624          <p> <b>Note:</b> For historic reasons, user agents <em class="bcp14">MAY</em> change the request method from POST to GET for the subsequent request. If this behavior is undesired, status code <a href="#status.307" class="smpl">307 (Temporary Redirect)</a> can be used instead.
     2623      <div class="note" id="rfc.section.6.4.3.p.3">
     2624         <p><b>Note:</b> For historic reasons, user agents <em class="bcp14">MAY</em> change the request method from POST to GET for the subsequent request. If this behavior is undesired, status code <a href="#status.307" class="smpl">307 (Temporary Redirect)</a> can be used instead.
    26252625         </p>
    26262626      </div>
     
    26592659         with a hyperlink to the different URI(s).
    26602660      </p>
    2661       <div class="note" id="rfc.section.6.4.7.p.3"> 
    2662          <p> <b>Note:</b> This status code is similar to <a href="#status.302" class="smpl">302 (Found)</a>, except that it does not allow changing the request method from POST to GET. This specification defines no equivalent counterpart
     2661      <div class="note" id="rfc.section.6.4.7.p.3">
     2662         <p><b>Note:</b> This status code is similar to <a href="#status.302" class="smpl">302 (Found)</a>, except that it does not allow changing the request method from POST to GET. This specification defines no equivalent counterpart
    26632663            for <a href="#status.301" class="smpl">301 (Moved
    26642664               Permanently)</a> (<a href="#status-308" id="rfc.xref.status-308.1"><cite title="The Hypertext Transfer Protocol (HTTP) Status Code 308 (Permanent Redirect)">[status-308]</cite></a>, however, defines the status code 308 (Permanent Redirect) for this purpose).
     
    26872687      <p id="rfc.section.6.5.3.p.2">If authentication credentials were provided in the request, the server considers them insufficient to grant access. The client <em class="bcp14">SHOULD NOT</em> repeat the request with the same credentials. The client <em class="bcp14">MAY</em> repeat the request with new or different credentials. However, a request might be forbidden for reasons unrelated to the credentials.
    26882688      </p>
    2689       <p id="rfc.section.6.5.3.p.3">An origin server that wishes to "hide" the current existence of a forbidden <a href="#resources" class="smpl">target resource</a>  <em class="bcp14">MAY</em> instead respond with a status code of <a href="#status.404" class="smpl">404 (Not Found)</a>.
     2689      <p id="rfc.section.6.5.3.p.3">An origin server that wishes to "hide" the current existence of a forbidden <a href="#resources" class="smpl">target resource</a> <em class="bcp14">MAY</em> instead respond with a status code of <a href="#status.404" class="smpl">404 (Not Found)</a>.
    26902690      </p>
    26912691      <div id="rfc.iref.76"></div>
     
    28112811         which will likely be alleviated after some delay. The server <em class="bcp14">MAY</em> send a <a href="#header.retry-after" class="smpl">Retry-After</a> header field (<a href="#header.retry-after" id="rfc.xref.header.retry-after.1" title="Retry-After">Section&nbsp;7.1.3</a>) to suggest an appropriate amount of time for the client to wait before retrying the request.
    28122812      </p>
    2813       <div class="note" id="rfc.section.6.6.4.p.2"> 
    2814          <p> <b>Note:</b> The existence of the 503 status code does not imply that a server has to use it when becoming overloaded. Some servers might
     2813      <div class="note" id="rfc.section.6.6.4.p.2">
     2814         <p><b>Note:</b> The existence of the 503 status code does not imply that a server has to use it when becoming overloaded. Some servers might
    28152815            simply refuse the connection.
    28162816         </p>
     
    29022902      </p>
    29032903      <div id="preferred.date.format">
    2904          <p id="rfc.section.7.1.1.1.p.7">                    Preferred format:</p>
     2904         <p id="rfc.section.7.1.1.1.p.7">          Preferred format:</p>
    29052905      </div>
    29062906      <div id="rfc.figure.u.45"></div><pre class="inline"><span id="rfc.iref.g.40"></span><span id="rfc.iref.g.41"></span><span id="rfc.iref.g.42"></span><span id="rfc.iref.g.43"></span><span id="rfc.iref.g.44"></span><span id="rfc.iref.g.45"></span><span id="rfc.iref.g.46"></span><span id="rfc.iref.g.47"></span><span id="rfc.iref.g.48"></span><span id="rfc.iref.g.49"></span><span id="rfc.iref.g.50"></span><span id="rfc.iref.g.51"></span>  <a href="#preferred.date.format" class="smpl">IMF-fixdate</a>  = <a href="#preferred.date.format" class="smpl">day-name</a> "," <a href="#imported.abnf" class="smpl">SP</a> date1 <a href="#imported.abnf" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">time-of-day</a> <a href="#imported.abnf" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">GMT</a>
     
    29432943  <a href="#preferred.date.format" class="smpl">second</a>       = 2<a href="#imported.abnf" class="smpl">DIGIT</a>               
    29442944</pre><div id="obsolete.date.formats">
    2945          <p id="rfc.section.7.1.1.1.p.9">              Obsolete formats:</p>
     2945         <p id="rfc.section.7.1.1.1.p.9">       Obsolete formats:</p>
    29462946      </div>
    29472947      <div id="rfc.figure.u.46"></div><pre class="inline"><span id="rfc.iref.g.52"></span>  <a href="#obsolete.date.formats" class="smpl">obs-date</a>     = <a href="#obsolete.date.formats" class="smpl">rfc850-date</a> / <a href="#obsolete.date.formats" class="smpl">asctime-date</a>
     
    29692969         date and time specifications defined by the Internet Message Format.
    29702970      </p>
    2971       <div class="note" id="rfc.section.7.1.1.1.p.16"> 
    2972          <p> <b>Note:</b> HTTP requirements for the date/time stamp format apply only to their usage within the protocol stream. Implementations are
     2971      <div class="note" id="rfc.section.7.1.1.1.p.16">
     2972         <p><b>Note:</b> HTTP requirements for the date/time stamp format apply only to their usage within the protocol stream. Implementations are
    29732973            not required to use these formats for user presentation, request logging, etc.
    29742974         </p>
     
    30233023         header field in a <a href="#status.201" class="smpl">201 (Created)</a> response is supposed to provide a URI that is specific to the created resource.
    30243024      </p>
    3025       <div class="note" id="rfc.section.7.1.2.p.9"> 
    3026          <p> <b>Note:</b> Some recipients attempt to recover from Location fields that are not valid URI references. This specification does not mandate
     3025      <div class="note" id="rfc.section.7.1.2.p.9">
     3026         <p><b>Note:</b> Some recipients attempt to recover from Location fields that are not valid URI references. This specification does not mandate
    30273027            or define such processing, but does allow it for the sake of robustness.
    30283028         </p>
    30293029      </div>
    3030       <div class="note" id="rfc.section.7.1.2.p.10"> 
    3031          <p> <b>Note:</b> The <a href="#header.content-location" class="smpl">Content-Location</a> header field (<a href="#header.content-location" id="rfc.xref.header.content-location.3" title="Content-Location">Section&nbsp;3.1.4.2</a>) differs from Location in that the Content-Location refers to the most specific resource corresponding to the enclosed representation.
     3030      <div class="note" id="rfc.section.7.1.2.p.10">
     3031         <p><b>Note:</b> The <a href="#header.content-location" class="smpl">Content-Location</a> header field (<a href="#header.content-location" id="rfc.xref.header.content-location.3" title="Content-Location">Section&nbsp;3.1.4.2</a>) differs from Location in that the Content-Location refers to the most specific resource corresponding to the enclosed representation.
    30323032            It is therefore possible for a response to contain both the Location and Content-Location header fields.
    30333033         </p>
     
    30413041      <div id="rfc.figure.u.54"></div><pre class="inline"><span id="rfc.iref.g.57"></span>  <a href="#header.retry-after" class="smpl">Retry-After</a> = <a href="#http.date" class="smpl">HTTP-date</a> / <a href="#rule.delta-seconds" class="smpl">delta-seconds</a>
    30423042</pre><div id="rule.delta-seconds">
    3043          <p id="rfc.section.7.1.3.p.4">  Time spans are non-negative decimal integers, representing time in seconds.</p>
     3043         <p id="rfc.section.7.1.3.p.4"> Time spans are non-negative decimal integers, representing time in seconds.</p>
    30443044      </div>
    30453045      <div id="rfc.figure.u.55"></div><pre class="inline"><span id="rfc.iref.g.58"></span>  <a href="#rule.delta-seconds" class="smpl">delta-seconds</a>  = 1*<a href="#imported.abnf" class="smpl">DIGIT</a>
     
    32323232         response semantics (<a href="#Part5" id="rfc.xref.Part5.11"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a>), it ought to document this too.
    32333233      </p>
    3234       <div class="note" id="rfc.section.8.1.2.p.4"> 
    3235          <p> <b>Note:</b> Avoid defining a method name that starts with "M-", since that prefix might be misinterpreted as having the semantics assigned
     3234      <div class="note" id="rfc.section.8.1.2.p.4">
     3235         <p><b>Note:</b> Avoid defining a method name that starts with "M-", since that prefix might be misinterpreted as having the semantics assigned
    32363236            to it by <a href="#RFC2774" id="rfc.xref.RFC2774.1"><cite title="An HTTP Extension Framework">[RFC2774]</cite></a>.
    32373237         </p>
     
    32553255                  <td class="left">no</td>
    32563256                  <td class="left">no</td>
    3257                   <td class="left"> <a href="#CONNECT" id="rfc.xref.CONNECT.2" title="CONNECT">Section&nbsp;4.3.6</a>
     3257                  <td class="left"><a href="#CONNECT" id="rfc.xref.CONNECT.2" title="CONNECT">Section&nbsp;4.3.6</a>
    32583258                  </td>
    32593259               </tr>
     
    32623262                  <td class="left">no</td>
    32633263                  <td class="left">yes</td>
    3264                   <td class="left"> <a href="#DELETE" id="rfc.xref.DELETE.2" title="DELETE">Section&nbsp;4.3.5</a>
     3264                  <td class="left"><a href="#DELETE" id="rfc.xref.DELETE.2" title="DELETE">Section&nbsp;4.3.5</a>
    32653265                  </td>
    32663266               </tr>
     
    32693269                  <td class="left">yes</td>
    32703270                  <td class="left">yes</td>
    3271                   <td class="left"> <a href="#GET" id="rfc.xref.GET.4" title="GET">Section&nbsp;4.3.1</a>
     3271                  <td class="left"><a href="#GET" id="rfc.xref.GET.4" title="GET">Section&nbsp;4.3.1</a>
    32723272                  </td>
    32733273               </tr>
     
    32763276                  <td class="left">yes</td>
    32773277                  <td class="left">yes</td>
    3278                   <td class="left"> <a href="#HEAD" id="rfc.xref.HEAD.2" title="HEAD">Section&nbsp;4.3.2</a>
     3278                  <td class="left"><a href="#HEAD" id="rfc.xref.HEAD.2" title="HEAD">Section&nbsp;4.3.2</a>
    32793279                  </td>
    32803280               </tr>
     
    32833283                  <td class="left">yes</td>
    32843284                  <td class="left">yes</td>
    3285                   <td class="left"> <a href="#OPTIONS" id="rfc.xref.OPTIONS.3" title="OPTIONS">Section&nbsp;4.3.7</a>
     3285                  <td class="left"><a href="#OPTIONS" id="rfc.xref.OPTIONS.3" title="OPTIONS">Section&nbsp;4.3.7</a>
    32863286                  </td>
    32873287               </tr>
     
    32903290                  <td class="left">no</td>
    32913291                  <td class="left">no</td>
    3292                   <td class="left"> <a href="#POST" id="rfc.xref.POST.3" title="POST">Section&nbsp;4.3.3</a>
     3292                  <td class="left"><a href="#POST" id="rfc.xref.POST.3" title="POST">Section&nbsp;4.3.3</a>
    32933293                  </td>
    32943294               </tr>
     
    32973297                  <td class="left">no</td>
    32983298                  <td class="left">yes</td>
    3299                   <td class="left"> <a href="#PUT" id="rfc.xref.PUT.3" title="PUT">Section&nbsp;4.3.4</a>
     3299                  <td class="left"><a href="#PUT" id="rfc.xref.PUT.3" title="PUT">Section&nbsp;4.3.4</a>
    33003300                  </td>
    33013301               </tr>
     
    33043304                  <td class="left">yes</td>
    33053305                  <td class="left">yes</td>
    3306                   <td class="left"> <a href="#TRACE" id="rfc.xref.TRACE.3" title="TRACE">Section&nbsp;4.3.8</a>
     3306                  <td class="left"><a href="#TRACE" id="rfc.xref.TRACE.3" title="TRACE">Section&nbsp;4.3.8</a>
    33073307                  </td>
    33083308               </tr>
     
    33673367                  <td class="left">100</td>
    33683368                  <td class="left">Continue</td>
    3369                   <td class="left"> <a href="#status.100" id="rfc.xref.status.100.4" title="100 Continue">Section&nbsp;6.2.1</a>
     3369                  <td class="left"><a href="#status.100" id="rfc.xref.status.100.4" title="100 Continue">Section&nbsp;6.2.1</a>
    33703370                  </td>
    33713371               </tr>
     
    33733373                  <td class="left">101</td>
    33743374                  <td class="left">Switching Protocols</td>
    3375                   <td class="left"> <a href="#status.101" id="rfc.xref.status.101.2" title="101 Switching Protocols">Section&nbsp;6.2.2</a>
     3375                  <td class="left"><a href="#status.101" id="rfc.xref.status.101.2" title="101 Switching Protocols">Section&nbsp;6.2.2</a>
    33763376                  </td>
    33773377               </tr>
     
    33793379                  <td class="left">200</td>
    33803380                  <td class="left">OK</td>
    3381                   <td class="left"> <a href="#status.200" id="rfc.xref.status.200.2" title="200 OK">Section&nbsp;6.3.1</a>
     3381                  <td class="left"><a href="#status.200" id="rfc.xref.status.200.2" title="200 OK">Section&nbsp;6.3.1</a>
    33823382                  </td>
    33833383               </tr>
     
    33853385                  <td class="left">201</td>
    33863386                  <td class="left">Created</td>
    3387                   <td class="left"> <a href="#status.201" id="rfc.xref.status.201.2" title="201 Created">Section&nbsp;6.3.2</a>
     3387                  <td class="left"><a href="#status.201" id="rfc.xref.status.201.2" title="201 Created">Section&nbsp;6.3.2</a>
    33883388                  </td>
    33893389               </tr>
     
    33913391                  <td class="left">202</td>
    33923392                  <td class="left">Accepted</td>
    3393                   <td class="left"> <a href="#status.202" id="rfc.xref.status.202.2" title="202 Accepted">Section&nbsp;6.3.3</a>
     3393                  <td class="left"><a href="#status.202" id="rfc.xref.status.202.2" title="202 Accepted">Section&nbsp;6.3.3</a>
    33943394                  </td>
    33953395               </tr>
     
    33973397                  <td class="left">203</td>
    33983398                  <td class="left">Non-Authoritative Information</td>
    3399                   <td class="left"> <a href="#status.203" id="rfc.xref.status.203.2" title="203 Non-Authoritative Information">Section&nbsp;6.3.4</a>
     3399                  <td class="left"><a href="#status.203" id="rfc.xref.status.203.2" title="203 Non-Authoritative Information">Section&nbsp;6.3.4</a>
    34003400                  </td>
    34013401               </tr>
     
    34033403                  <td class="left">204</td>
    34043404                  <td class="left">No Content</td>
    3405                   <td class="left"> <a href="#status.204" id="rfc.xref.status.204.2" title="204 No Content">Section&nbsp;6.3.5</a>
     3405                  <td class="left"><a href="#status.204" id="rfc.xref.status.204.2" title="204 No Content">Section&nbsp;6.3.5</a>
    34063406                  </td>
    34073407               </tr>
     
    34093409                  <td class="left">205</td>
    34103410                  <td class="left">Reset Content</td>
    3411                   <td class="left"> <a href="#status.205" id="rfc.xref.status.205.2" title="205 Reset Content">Section&nbsp;6.3.6</a>
     3411                  <td class="left"><a href="#status.205" id="rfc.xref.status.205.2" title="205 Reset Content">Section&nbsp;6.3.6</a>
    34123412                  </td>
    34133413               </tr>
     
    34153415                  <td class="left">300</td>
    34163416                  <td class="left">Multiple Choices</td>
    3417                   <td class="left"> <a href="#status.300" id="rfc.xref.status.300.3" title="300 Multiple Choices">Section&nbsp;6.4.1</a>
     3417                  <td class="left"><a href="#status.300" id="rfc.xref.status.300.3" title="300 Multiple Choices">Section&nbsp;6.4.1</a>
    34183418                  </td>
    34193419               </tr>
     
    34213421                  <td class="left">301</td>
    34223422                  <td class="left">Moved Permanently</td>
    3423                   <td class="left"> <a href="#status.301" id="rfc.xref.status.301.2" title="301 Moved Permanently">Section&nbsp;6.4.2</a>
     3423                  <td class="left"><a href="#status.301" id="rfc.xref.status.301.2" title="301 Moved Permanently">Section&nbsp;6.4.2</a>
    34243424                  </td>
    34253425               </tr>
     
    34273427                  <td class="left">302</td>
    34283428                  <td class="left">Found</td>
    3429                   <td class="left"> <a href="#status.302" id="rfc.xref.status.302.2" title="302 Found">Section&nbsp;6.4.3</a>
     3429                  <td class="left"><a href="#status.302" id="rfc.xref.status.302.2" title="302 Found">Section&nbsp;6.4.3</a>
    34303430                  </td>
    34313431               </tr>
     
    34333433                  <td class="left">303</td>
    34343434                  <td class="left">See Other</td>
    3435                   <td class="left"> <a href="#status.303" id="rfc.xref.status.303.2" title="303 See Other">Section&nbsp;6.4.4</a>
     3435                  <td class="left"><a href="#status.303" id="rfc.xref.status.303.2" title="303 See Other">Section&nbsp;6.4.4</a>
    34363436                  </td>
    34373437               </tr>
     
    34393439                  <td class="left">305</td>
    34403440                  <td class="left">Use Proxy</td>
    3441                   <td class="left"> <a href="#status.305" id="rfc.xref.status.305.2" title="305 Use Proxy">Section&nbsp;6.4.5</a>
     3441                  <td class="left"><a href="#status.305" id="rfc.xref.status.305.2" title="305 Use Proxy">Section&nbsp;6.4.5</a>
    34423442                  </td>
    34433443               </tr>
     
    34453445                  <td class="left">306</td>
    34463446                  <td class="left">(Unused)</td>
    3447                   <td class="left"> <a href="#status.306" id="rfc.xref.status.306.1" title="306 (Unused)">Section&nbsp;6.4.6</a>
     3447                  <td class="left"><a href="#status.306" id="rfc.xref.status.306.1" title="306 (Unused)">Section&nbsp;6.4.6</a>
    34483448                  </td>
    34493449               </tr>
     
    34513451                  <td class="left">307</td>
    34523452                  <td class="left">Temporary Redirect</td>
    3453                   <td class="left"> <a href="#status.307" id="rfc.xref.status.307.2" title="307 Temporary Redirect">Section&nbsp;6.4.7</a>
     3453                  <td class="left"><a href="#status.307" id="rfc.xref.status.307.2" title="307 Temporary Redirect">Section&nbsp;6.4.7</a>
    34543454                  </td>
    34553455               </tr>
     
    34573457                  <td class="left">400</td>
    34583458                  <td class="left">Bad Request</td>
    3459                   <td class="left"> <a href="#status.400" id="rfc.xref.status.400.2" title="400 Bad Request">Section&nbsp;6.5.1</a>
     3459                  <td class="left"><a href="#status.400" id="rfc.xref.status.400.2" title="400 Bad Request">Section&nbsp;6.5.1</a>
    34603460                  </td>
    34613461               </tr>
     
    34633463                  <td class="left">402</td>
    34643464                  <td class="left">Payment Required</td>
    3465                   <td class="left"> <a href="#status.402" id="rfc.xref.status.402.2" title="402 Payment Required">Section&nbsp;6.5.2</a>
     3465                  <td class="left"><a href="#status.402" id="rfc.xref.status.402.2" title="402 Payment Required">Section&nbsp;6.5.2</a>
    34663466                  </td>
    34673467               </tr>
     
    34693469                  <td class="left">403</td>
    34703470                  <td class="left">Forbidden</td>
    3471                   <td class="left"> <a href="#status.403" id="rfc.xref.status.403.2" title="403 Forbidden">Section&nbsp;6.5.3</a>
     3471                  <td class="left"><a href="#status.403" id="rfc.xref.status.403.2" title="403 Forbidden">Section&nbsp;6.5.3</a>
    34723472                  </td>
    34733473               </tr>
     
    34753475                  <td class="left">404</td>
    34763476                  <td class="left">Not Found</td>
    3477                   <td class="left"> <a href="#status.404" id="rfc.xref.status.404.2" title="404 Not Found">Section&nbsp;6.5.4</a>
     3477                  <td class="left"><a href="#status.404" id="rfc.xref.status.404.2" title="404 Not Found">Section&nbsp;6.5.4</a>
    34783478                  </td>
    34793479               </tr>
     
    34813481                  <td class="left">405</td>
    34823482                  <td class="left">Method Not Allowed</td>
    3483                   <td class="left"> <a href="#status.405" id="rfc.xref.status.405.2" title="405 Method Not Allowed">Section&nbsp;6.5.5</a>
     3483                  <td class="left"><a href="#status.405" id="rfc.xref.status.405.2" title="405 Method Not Allowed">Section&nbsp;6.5.5</a>
    34843484                  </td>
    34853485               </tr>
     
    34873487                  <td class="left">406</td>
    34883488                  <td class="left">Not Acceptable</td>
    3489                   <td class="left"> <a href="#status.406" id="rfc.xref.status.406.2" title="406 Not Acceptable">Section&nbsp;6.5.6</a>
     3489                  <td class="left"><a href="#status.406" id="rfc.xref.status.406.2" title="406 Not Acceptable">Section&nbsp;6.5.6</a>
    34903490                  </td>
    34913491               </tr>
     
    34933493                  <td class="left">408</td>
    34943494                  <td class="left">Request Timeout</td>
    3495                   <td class="left"> <a href="#status.408" id="rfc.xref.status.408.2" title="408 Request Timeout">Section&nbsp;6.5.7</a>
     3495                  <td class="left"><a href="#status.408" id="rfc.xref.status.408.2" title="408 Request Timeout">Section&nbsp;6.5.7</a>
    34963496                  </td>
    34973497               </tr>
     
    34993499                  <td class="left">409</td>
    35003500                  <td class="left">Conflict</td>
    3501                   <td class="left"> <a href="#status.409" id="rfc.xref.status.409.2" title="409 Conflict">Section&nbsp;6.5.8</a>
     3501                  <td class="left"><a href="#status.409" id="rfc.xref.status.409.2" title="409 Conflict">Section&nbsp;6.5.8</a>
    35023502                  </td>
    35033503               </tr>
     
    35053505                  <td class="left">410</td>
    35063506                  <td class="left">Gone</td>
    3507                   <td class="left"> <a href="#status.410" id="rfc.xref.status.410.2" title="410 Gone">Section&nbsp;6.5.9</a>
     3507                  <td class="left"><a href="#status.410" id="rfc.xref.status.410.2" title="410 Gone">Section&nbsp;6.5.9</a>
    35083508                  </td>
    35093509               </tr>
     
    35113511                  <td class="left">411</td>
    35123512                  <td class="left">Length Required</td>
    3513                   <td class="left"> <a href="#status.411" id="rfc.xref.status.411.2" title="411 Length Required">Section&nbsp;6.5.10</a>
     3513                  <td class="left"><a href="#status.411" id="rfc.xref.status.411.2" title="411 Length Required">Section&nbsp;6.5.10</a>
    35143514                  </td>
    35153515               </tr>
     
    35173517                  <td class="left">413</td>
    35183518                  <td class="left">Payload Too Large</td>
    3519                   <td class="left"> <a href="#status.413" id="rfc.xref.status.413.2" title="413 Payload Too Large">Section&nbsp;6.5.11</a>
     3519                  <td class="left"><a href="#status.413" id="rfc.xref.status.413.2" title="413 Payload Too Large">Section&nbsp;6.5.11</a>
    35203520                  </td>
    35213521               </tr>
     
    35233523                  <td class="left">414</td>
    35243524                  <td class="left">URI Too Long</td>
    3525                   <td class="left"> <a href="#status.414" id="rfc.xref.status.414.2" title="414 URI Too Long">Section&nbsp;6.5.12</a>
     3525                  <td class="left"><a href="#status.414" id="rfc.xref.status.414.2" title="414 URI Too Long">Section&nbsp;6.5.12</a>
    35263526                  </td>
    35273527               </tr>
     
    35293529                  <td class="left">415</td>
    35303530                  <td class="left">Unsupported Media Type</td>
    3531                   <td class="left"> <a href="#status.415" id="rfc.xref.status.415.2" title="415 Unsupported Media Type">Section&nbsp;6.5.13</a>
     3531                  <td class="left"><a href="#status.415" id="rfc.xref.status.415.2" title="415 Unsupported Media Type">Section&nbsp;6.5.13</a>
    35323532                  </td>
    35333533               </tr>
     
    35353535                  <td class="left">417</td>
    35363536                  <td class="left">Expectation Failed</td>
    3537                   <td class="left"> <a href="#status.417" id="rfc.xref.status.417.2" title="417 Expectation Failed">Section&nbsp;6.5.14</a>
     3537                  <td class="left"><a href="#status.417" id="rfc.xref.status.417.2" title="417 Expectation Failed">Section&nbsp;6.5.14</a>
    35383538                  </td>
    35393539               </tr>
     
    35413541                  <td class="left">426</td>
    35423542                  <td class="left">Upgrade Required</td>
    3543                   <td class="left"> <a href="#status.426" id="rfc.xref.status.426.2" title="426 Upgrade Required">Section&nbsp;6.5.15</a>
     3543                  <td class="left"><a href="#status.426" id="rfc.xref.status.426.2" title="426 Upgrade Required">Section&nbsp;6.5.15</a>
    35443544                  </td>
    35453545               </tr>
     
    35473547                  <td class="left">500</td>
    35483548                  <td class="left">Internal Server Error</td>
    3549                   <td class="left"> <a href="#status.500" id="rfc.xref.status.500.2" title="500 Internal Server Error">Section&nbsp;6.6.1</a>
     3549                  <td class="left"><a href="#status.500" id="rfc.xref.status.500.2" title="500 Internal Server Error">Section&nbsp;6.6.1</a>
    35503550                  </td>
    35513551               </tr>
     
    35533553                  <td class="left">501</td>
    35543554                  <td class="left">Not Implemented</td>
    3555                   <td class="left"> <a href="#status.501" id="rfc.xref.status.501.2" title="501 Not Implemented">Section&nbsp;6.6.2</a>
     3555                  <td class="left"><a href="#status.501" id="rfc.xref.status.501.2" title="501 Not Implemented">Section&nbsp;6.6.2</a>
    35563556                  </td>
    35573557               </tr>
     
    35593559                  <td class="left">502</td>
    35603560                  <td class="left">Bad Gateway</td>
    3561                   <td class="left"> <a href="#status.502" id="rfc.xref.status.502.2" title="502 Bad Gateway">Section&nbsp;6.6.3</a>
     3561                  <td class="left"><a href="#status.502" id="rfc.xref.status.502.2" title="502 Bad Gateway">Section&nbsp;6.6.3</a>
    35623562                  </td>
    35633563               </tr>
     
    35653565                  <td class="left">503</td>
    35663566                  <td class="left">Service Unavailable</td>
    3567                   <td class="left"> <a href="#status.503" id="rfc.xref.status.503.2" title="503 Service Unavailable">Section&nbsp;6.6.4</a>
     3567                  <td class="left"><a href="#status.503" id="rfc.xref.status.503.2" title="503 Service Unavailable">Section&nbsp;6.6.4</a>
    35683568                  </td>
    35693569               </tr>
     
    35713571                  <td class="left">504</td>
    35723572                  <td class="left">Gateway Timeout</td>
    3573                   <td class="left"> <a href="#status.504" id="rfc.xref.status.504.2" title="504 Gateway Timeout">Section&nbsp;6.6.5</a>
     3573                  <td class="left"><a href="#status.504" id="rfc.xref.status.504.2" title="504 Gateway Timeout">Section&nbsp;6.6.5</a>
    35743574                  </td>
    35753575               </tr>
     
    35773577                  <td class="left">505</td>
    35783578                  <td class="left">HTTP Version Not Supported</td>
    3579                   <td class="left"> <a href="#status.505" id="rfc.xref.status.505.2" title="505 HTTP Version Not Supported">Section&nbsp;6.6.6</a>
     3579                  <td class="left"><a href="#status.505" id="rfc.xref.status.505.2" title="505 HTTP Version Not Supported">Section&nbsp;6.6.6</a>
    35803580                  </td>
    35813581               </tr>
     
    36803680                  <td class="left">http</td>
    36813681                  <td class="left">standard</td>
    3682                   <td class="left"> <a href="#header.accept" id="rfc.xref.header.accept.3" title="Accept">Section&nbsp;5.3.2</a>
     3682                  <td class="left"><a href="#header.accept" id="rfc.xref.header.accept.3" title="Accept">Section&nbsp;5.3.2</a>
    36833683                  </td>
    36843684               </tr>
     
    36873687                  <td class="left">http</td>
    36883688                  <td class="left">standard</td>
    3689                   <td class="left"> <a href="#header.accept-charset" id="rfc.xref.header.accept-charset.2" title="Accept-Charset">Section&nbsp;5.3.3</a>
     3689                  <td class="left"><a href="#header.accept-charset" id="rfc.xref.header.accept-charset.2" title="Accept-Charset">Section&nbsp;5.3.3</a>
    36903690                  </td>
    36913691               </tr>
     
    36943694                  <td class="left">http</td>
    36953695                  <td class="left">standard</td>
    3696                   <td class="left"> <a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.3" title="Accept-Encoding">Section&nbsp;5.3.4</a>
     3696                  <td class="left"><a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.3" title="Accept-Encoding">Section&nbsp;5.3.4</a>
    36973697                  </td>
    36983698               </tr>
     
    37013701                  <td class="left">http</td>
    37023702                  <td class="left">standard</td>
    3703                   <td class="left"> <a href="#header.accept-language" id="rfc.xref.header.accept-language.3" title="Accept-Language">Section&nbsp;5.3.5</a>
     3703                  <td class="left"><a href="#header.accept-language" id="rfc.xref.header.accept-language.3" title="Accept-Language">Section&nbsp;5.3.5</a>
    37043704                  </td>
    37053705               </tr>
     
    37083708                  <td class="left">http</td>
    37093709                  <td class="left">standard</td>
    3710                   <td class="left"> <a href="#header.allow" id="rfc.xref.header.allow.3" title="Allow">Section&nbsp;7.4.1</a>
     3710                  <td class="left"><a href="#header.allow" id="rfc.xref.header.allow.3" title="Allow">Section&nbsp;7.4.1</a>
    37113711                  </td>
    37123712               </tr>
     
    37153715                  <td class="left">http</td>
    37163716                  <td class="left">standard</td>
    3717                   <td class="left"> <a href="#header.content-encoding" id="rfc.xref.header.content-encoding.3" title="Content-Encoding">Section&nbsp;3.1.2.2</a>
     3717                  <td class="left"><a href="#header.content-encoding" id="rfc.xref.header.content-encoding.3" title="Content-Encoding">Section&nbsp;3.1.2.2</a>
    37183718                  </td>
    37193719               </tr>
     
    37223722                  <td class="left">http</td>
    37233723                  <td class="left">standard</td>
    3724                   <td class="left"> <a href="#header.content-language" id="rfc.xref.header.content-language.2" title="Content-Language">Section&nbsp;3.1.3.2</a>
     3724                  <td class="left"><a href="#header.content-language" id="rfc.xref.header.content-language.2" title="Content-Language">Section&nbsp;3.1.3.2</a>
    37253725                  </td>
    37263726               </tr>
     
    37293729                  <td class="left">http</td>
    37303730                  <td class="left">standard</td>
    3731                   <td class="left"> <a href="#header.content-location" id="rfc.xref.header.content-location.4" title="Content-Location">Section&nbsp;3.1.4.2</a>
     3731                  <td class="left"><a href="#header.content-location" id="rfc.xref.header.content-location.4" title="Content-Location">Section&nbsp;3.1.4.2</a>
    37323732                  </td>
    37333733               </tr>
     
    37363736                  <td class="left">http</td>
    37373737                  <td class="left">standard</td>
    3738                   <td class="left"> <a href="#header.content-type" id="rfc.xref.header.content-type.4" title="Content-Type">Section&nbsp;3.1.1.5</a>
     3738                  <td class="left"><a href="#header.content-type" id="rfc.xref.header.content-type.4" title="Content-Type">Section&nbsp;3.1.1.5</a>
    37393739                  </td>
    37403740               </tr>
     
    37433743                  <td class="left">http</td>
    37443744                  <td class="left">standard</td>
    3745                   <td class="left"> <a href="#header.date" id="rfc.xref.header.date.3" title="Date">Section&nbsp;7.1.1.2</a>
     3745                  <td class="left"><a href="#header.date" id="rfc.xref.header.date.3" title="Date">Section&nbsp;7.1.1.2</a>
    37463746                  </td>
    37473747               </tr>
     
    37503750                  <td class="left">http</td>
    37513751                  <td class="left">standard</td>
    3752                   <td class="left"> <a href="#header.expect" id="rfc.xref.header.expect.3" title="Expect">Section&nbsp;5.1.1</a>
     3752                  <td class="left"><a href="#header.expect" id="rfc.xref.header.expect.3" title="Expect">Section&nbsp;5.1.1</a>
    37533753                  </td>
    37543754               </tr>
     
    37573757                  <td class="left">http</td>
    37583758                  <td class="left">standard</td>
    3759                   <td class="left"> <a href="#header.from" id="rfc.xref.header.from.2" title="From">Section&nbsp;5.5.1</a>
     3759                  <td class="left"><a href="#header.from" id="rfc.xref.header.from.2" title="From">Section&nbsp;5.5.1</a>
    37603760                  </td>
    37613761               </tr>
     
    37643764                  <td class="left">http</td>
    37653765                  <td class="left">standard</td>
    3766                   <td class="left"> <a href="#header.location" id="rfc.xref.header.location.4" title="Location">Section&nbsp;7.1.2</a>
     3766                  <td class="left"><a href="#header.location" id="rfc.xref.header.location.4" title="Location">Section&nbsp;7.1.2</a>
    37673767                  </td>
    37683768               </tr>
     
    37713771                  <td class="left">http</td>
    37723772                  <td class="left">standard</td>
    3773                   <td class="left"> <a href="#mime-version" id="rfc.xref.mime-version.1" title="MIME-Version">Appendix&nbsp;A.1</a>
     3773                  <td class="left"><a href="#mime-version" id="rfc.xref.mime-version.1" title="MIME-Version">Appendix&nbsp;A.1</a>
    37743774                  </td>
    37753775               </tr>
     
    37783778                  <td class="left">http</td>
    37793779                  <td class="left">standard</td>
    3780                   <td class="left"> <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.4" title="Max-Forwards">Section&nbsp;5.1.2</a>
     3780                  <td class="left"><a href="#header.max-forwards" id="rfc.xref.header.max-forwards.4" title="Max-Forwards">Section&nbsp;5.1.2</a>
    37813781                  </td>
    37823782               </tr>
     
    37853785                  <td class="left">http</td>
    37863786                  <td class="left">standard</td>
    3787                   <td class="left"> <a href="#header.referer" id="rfc.xref.header.referer.2" title="Referer">Section&nbsp;5.5.2</a>
     3787                  <td class="left"><a href="#header.referer" id="rfc.xref.header.referer.2" title="Referer">Section&nbsp;5.5.2</a>
    37883788                  </td>
    37893789               </tr>
     
    37923792                  <td class="left">http</td>
    37933793                  <td class="left">standard</td>
    3794                   <td class="left"> <a href="#header.retry-after" id="rfc.xref.header.retry-after.3" title="Retry-After">Section&nbsp;7.1.3</a>
     3794                  <td class="left"><a href="#header.retry-after" id="rfc.xref.header.retry-after.3" title="Retry-After">Section&nbsp;7.1.3</a>
    37953795                  </td>
    37963796               </tr>
     
    37993799                  <td class="left">http</td>
    38003800                  <td class="left">standard</td>
    3801                   <td class="left"> <a href="#header.server" id="rfc.xref.header.server.2" title="Server">Section&nbsp;7.4.2</a>
     3801                  <td class="left"><a href="#header.server" id="rfc.xref.header.server.2" title="Server">Section&nbsp;7.4.2</a>
    38023802                  </td>
    38033803               </tr>
     
    38063806                  <td class="left">http</td>
    38073807                  <td class="left">standard</td>
    3808                   <td class="left"> <a href="#header.user-agent" id="rfc.xref.header.user-agent.3" title="User-Agent">Section&nbsp;5.5.3</a>
     3808                  <td class="left"><a href="#header.user-agent" id="rfc.xref.header.user-agent.3" title="User-Agent">Section&nbsp;5.5.3</a>
    38093809                  </td>
    38103810               </tr>
     
    38133813                  <td class="left">http</td>
    38143814                  <td class="left">standard</td>
    3815                   <td class="left"> <a href="#header.vary" id="rfc.xref.header.vary.4" title="Vary">Section&nbsp;7.1.4</a>
     3815                  <td class="left"><a href="#header.vary" id="rfc.xref.header.vary.4" title="Vary">Section&nbsp;7.1.4</a>
    38163816                  </td>
    38173817               </tr>
     
    38513851                  <td class="left">compress</td>
    38523852                  <td class="left">UNIX "compress" data format <a href="#Welch" id="rfc.xref.Welch.1"><cite title="A Technique for High Performance Data Compression">[Welch]</cite></a></td>
    3853                   <td class="left"> <a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 4.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.41"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>
     3853                  <td class="left"><a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 4.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.41"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>
    38543854                  </td>
    38553855               </tr>
     
    38583858                  <td class="left">"deflate" compressed data (<a href="#RFC1951" id="rfc.xref.RFC1951.1"><cite title="DEFLATE Compressed Data Format Specification version 1.3">[RFC1951]</cite></a>) inside the "zlib" data format (<a href="#RFC1950" id="rfc.xref.RFC1950.1"><cite title="ZLIB Compressed Data Format Specification version 3.3">[RFC1950]</cite></a>)
    38593859                  </td>
    3860                   <td class="left"> <a href="p1-messaging.html#deflate.coding" title="Deflate Coding">Section 4.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.42"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>
     3860                  <td class="left"><a href="p1-messaging.html#deflate.coding" title="Deflate Coding">Section 4.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.42"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>
    38613861                  </td>
    38623862               </tr>
     
    38643864                  <td class="left">gzip</td>
    38653865                  <td class="left">GZIP file format <a href="#RFC1952" id="rfc.xref.RFC1952.1"><cite title="GZIP file format specification version 4.3">[RFC1952]</cite></a></td>
    3866                   <td class="left"> <a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 4.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.43"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>
     3866                  <td class="left"><a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 4.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.43"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>
    38673867                  </td>
    38683868               </tr>
     
    38713871                  <td class="left">Reserved (synonym for "no encoding" in <a href="#header.accept-encoding" class="smpl">Accept-Encoding</a>)
    38723872                  </td>
    3873                   <td class="left"> <a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.4" title="Accept-Encoding">Section&nbsp;5.3.4</a>
     3873                  <td class="left"><a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.4" title="Accept-Encoding">Section&nbsp;5.3.4</a>
    38743874                  </td>
    38753875               </tr>
     
    38773877                  <td class="left">x-compress</td>
    38783878                  <td class="left">Deprecated (alias for compress)</td>
    3879                   <td class="left"> <a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 4.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.44"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>
     3879                  <td class="left"><a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 4.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.44"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>
    38803880                  </td>
    38813881               </tr>
     
    38833883                  <td class="left">x-gzip</td>
    38843884                  <td class="left">Deprecated (alias for gzip)</td>
    3885                   <td class="left"> <a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 4.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.45"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>
     3885                  <td class="left"><a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 4.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.45"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>
    38863886                  </td>
    38873887               </tr>
     
    39793979         <tr>
    39803980            <td class="reference"><b id="Part1">[Part1]</b></td>
    3981             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-latest (work in progress), June&nbsp;2013.
     3981            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-latest (work in progress), July&nbsp;2013.
    39823982            </td>
    39833983         </tr>
    39843984         <tr>
    39853985            <td class="reference"><b id="Part4">[Part4]</b></td>
    3986             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-latest (work in progress), June&nbsp;2013.
     3986            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-latest (work in progress), July&nbsp;2013.
    39873987            </td>
    39883988         </tr>
    39893989         <tr>
    39903990            <td class="reference"><b id="Part5">[Part5]</b></td>
    3991             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">Hypertext Transfer Protocol (HTTP/1.1): Range Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-latest (work in progress), June&nbsp;2013.
     3991            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">Hypertext Transfer Protocol (HTTP/1.1): Range Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-latest (work in progress), July&nbsp;2013.
    39923992            </td>
    39933993         </tr>
    39943994         <tr>
    39953995            <td class="reference"><b id="Part6">[Part6]</b></td>
    3996             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:mnot@mnot.net" title="Akamai">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">Hypertext Transfer Protocol (HTTP/1.1): Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-latest (work in progress), June&nbsp;2013.
     3996            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:mnot@mnot.net" title="Akamai">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">Hypertext Transfer Protocol (HTTP/1.1): Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-latest (work in progress), July&nbsp;2013.
    39973997            </td>
    39983998         </tr>
    39993999         <tr>
    40004000            <td class="reference"><b id="Part7">[Part7]</b></td>
    4001             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-latest">Hypertext Transfer Protocol (HTTP/1.1): Authentication</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p7-auth-latest (work in progress), June&nbsp;2013.
     4001            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-latest">Hypertext Transfer Protocol (HTTP/1.1): Authentication</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p7-auth-latest (work in progress), July&nbsp;2013.
    40024002            </td>
    40034003         </tr>
     
    42944294         information present): 204, 404, 405, 414, 501.
    42954295      </p>
    4296       <p id="rfc.section.B.p.24"> <a href="#header.allow" class="smpl">Allow</a> has been reclassified as a response header field, removing the option to specify it in a PUT request. Requirements relating
     4296      <p id="rfc.section.B.p.24"><a href="#header.allow" class="smpl">Allow</a> has been reclassified as a response header field, removing the option to specify it in a PUT request. Requirements relating
    42974297         to the content of Allow have been relaxed; correspondingly, clients are not required to always trust its value (<a href="#header.allow" id="rfc.xref.header.allow.4" title="Allow">Section&nbsp;7.4.1</a>).
    42984298      </p>
     
    44754475      <p id="rfc.section.E.2.p.1">Closed issues: </p>
    44764476      <ul>
    4477          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/22">http://tools.ietf.org/wg/httpbis/trac/ticket/22</a>&gt;: "ETag (and other metadata) in status messages"
    4478          </li>
    4479          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/96">http://tools.ietf.org/wg/httpbis/trac/ticket/96</a>&gt;: "Conditional GET text"
    4480          </li>
    4481          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/146">http://tools.ietf.org/wg/httpbis/trac/ticket/146</a>&gt;: "Clarify description of 405 (Not Allowed)"
    4482          </li>
    4483          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/223">http://tools.ietf.org/wg/httpbis/trac/ticket/223</a>&gt;: "Allowing heuristic caching for new status codes"
    4484          </li>
    4485          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/315">http://tools.ietf.org/wg/httpbis/trac/ticket/315</a>&gt;: "method semantics: retrieval/representation"
    4486          </li>
    4487          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/388">http://tools.ietf.org/wg/httpbis/trac/ticket/388</a>&gt;: "User confirmation for unsafe methods"
    4488          </li>
    4489          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/404">http://tools.ietf.org/wg/httpbis/trac/ticket/404</a>&gt;: "Tentative Status Codes"
    4490          </li>
    4491          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/418">http://tools.ietf.org/wg/httpbis/trac/ticket/418</a>&gt;: "No-Transform"
    4492          </li>
    4493          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/419">http://tools.ietf.org/wg/httpbis/trac/ticket/419</a>&gt;: "p2 editorial feedback"
    4494          </li>
    4495          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/424">http://tools.ietf.org/wg/httpbis/trac/ticket/424</a>&gt;: "Absence of Accept-Encoding"
    4496          </li>
    4497          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/428">http://tools.ietf.org/wg/httpbis/trac/ticket/428</a>&gt;: "Accept-Language ordering for identical qvalues"
    4498          </li>
    4499          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/432">http://tools.ietf.org/wg/httpbis/trac/ticket/432</a>&gt;: "Identify additional status codes as cacheable by default"
    4500          </li>
    4501          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/434">http://tools.ietf.org/wg/httpbis/trac/ticket/434</a>&gt;: "mention in header field considerations that leading/trailing WS is lossy"
     4477         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/22">http://tools.ietf.org/wg/httpbis/trac/ticket/22</a>&gt;: "ETag (and other metadata) in status messages"
     4478         </li>
     4479         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/96">http://tools.ietf.org/wg/httpbis/trac/ticket/96</a>&gt;: "Conditional GET text"
     4480         </li>
     4481         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/146">http://tools.ietf.org/wg/httpbis/trac/ticket/146</a>&gt;: "Clarify description of 405 (Not Allowed)"
     4482         </li>
     4483         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/223">http://tools.ietf.org/wg/httpbis/trac/ticket/223</a>&gt;: "Allowing heuristic caching for new status codes"
     4484         </li>
     4485         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/315">http://tools.ietf.org/wg/httpbis/trac/ticket/315</a>&gt;: "method semantics: retrieval/representation"
     4486         </li>
     4487         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/388">http://tools.ietf.org/wg/httpbis/trac/ticket/388</a>&gt;: "User confirmation for unsafe methods"
     4488         </li>
     4489         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/404">http://tools.ietf.org/wg/httpbis/trac/ticket/404</a>&gt;: "Tentative Status Codes"
     4490         </li>
     4491         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/418">http://tools.ietf.org/wg/httpbis/trac/ticket/418</a>&gt;: "No-Transform"
     4492         </li>
     4493         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/419">http://tools.ietf.org/wg/httpbis/trac/ticket/419</a>&gt;: "p2 editorial feedback"
     4494         </li>
     4495         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/424">http://tools.ietf.org/wg/httpbis/trac/ticket/424</a>&gt;: "Absence of Accept-Encoding"
     4496         </li>
     4497         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/428">http://tools.ietf.org/wg/httpbis/trac/ticket/428</a>&gt;: "Accept-Language ordering for identical qvalues"
     4498         </li>
     4499         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/432">http://tools.ietf.org/wg/httpbis/trac/ticket/432</a>&gt;: "Identify additional status codes as cacheable by default"
     4500         </li>
     4501         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/434">http://tools.ietf.org/wg/httpbis/trac/ticket/434</a>&gt;: "mention in header field considerations that leading/trailing WS is lossy"
    45024502         </li>
    45034503      </ul>
     
    45054505      <p id="rfc.section.E.3.p.1">Closed issues: </p>
    45064506      <ul>
    4507          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/436">http://tools.ietf.org/wg/httpbis/trac/ticket/436</a>&gt;: "explain list expansion in ABNF appendices"
    4508          </li>
    4509          <li> &lt;<a href="http://trac.tools.ietf.org/wg/httpbis/trac/ticket/448">http://trac.tools.ietf.org/wg/httpbis/trac/ticket/448</a>&gt;: "Fallback for Accept-Language"
    4510          </li>
    4511          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/449">http://tools.ietf.org/wg/httpbis/trac/ticket/449</a>&gt;: "Receiving a higher minor HTTP version number"
    4512          </li>
    4513          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/456">http://tools.ietf.org/wg/httpbis/trac/ticket/456</a>&gt;: "Language-tag vs. language-range"
    4514          </li>
    4515          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/457">http://tools.ietf.org/wg/httpbis/trac/ticket/457</a>&gt;: "Registering x-gzip and x-deflate"
    4516          </li>
    4517          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/459">http://tools.ietf.org/wg/httpbis/trac/ticket/459</a>&gt;: "RFC2774 and method registrations"
    4518          </li>
    4519          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/488">http://tools.ietf.org/wg/httpbis/trac/ticket/488</a>&gt;: "Selection based upon request target"
     4507         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/436">http://tools.ietf.org/wg/httpbis/trac/ticket/436</a>&gt;: "explain list expansion in ABNF appendices"
     4508         </li>
     4509         <li>&lt;<a href="http://trac.tools.ietf.org/wg/httpbis/trac/ticket/448">http://trac.tools.ietf.org/wg/httpbis/trac/ticket/448</a>&gt;: "Fallback for Accept-Language"
     4510         </li>
     4511         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/449">http://tools.ietf.org/wg/httpbis/trac/ticket/449</a>&gt;: "Receiving a higher minor HTTP version number"
     4512         </li>
     4513         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/456">http://tools.ietf.org/wg/httpbis/trac/ticket/456</a>&gt;: "Language-tag vs. language-range"
     4514         </li>
     4515         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/457">http://tools.ietf.org/wg/httpbis/trac/ticket/457</a>&gt;: "Registering x-gzip and x-deflate"
     4516         </li>
     4517         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/459">http://tools.ietf.org/wg/httpbis/trac/ticket/459</a>&gt;: "RFC2774 and method registrations"
     4518         </li>
     4519         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/488">http://tools.ietf.org/wg/httpbis/trac/ticket/488</a>&gt;: "Selection based upon request target"
    45204520         </li>
    45214521      </ul>
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r2294 r2301  
    1313  <!ENTITY SHOULD-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHOULD NOT</bcp14>">
    1414  <!ENTITY ID-VERSION "latest">
    15   <!ENTITY ID-MONTH "June">
     15  <!ENTITY ID-MONTH "July">
    1616  <!ENTITY ID-YEAR "2013">
    1717  <!ENTITY mdash "&#8212;">
  • draft-ietf-httpbis/latest/p4-conditional.html

    r2280 r2301  
    440440  }
    441441  @top-right {
    442        content: "June 2013";
     442       content: "July 2013";
    443443  }
    444444  @top-center {
     
    449449  }
    450450  @bottom-center {
    451        content: "Expires December 5, 2013";
     451       content: "Expires January 2, 2014";
    452452  }
    453453  @bottom-right {
     
    486486      <link href="p2-semantics.html" rel="prev">
    487487      <link href="p5-range.html" rel="next">
    488       <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.597, 2013/05/27 06:39:42, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
     488      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.598, 2013/06/23 14:11:10, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
    489489      <link rel="schema.dct" href="http://purl.org/dc/terms/">
    490490      <meta name="dct.creator" content="Fielding, R.">
    491491      <meta name="dct.creator" content="Reschke, J. F.">
    492492      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p4-conditional-latest">
    493       <meta name="dct.issued" scheme="ISO8601" content="2013-06-03">
     493      <meta name="dct.issued" scheme="ISO8601" content="2013-07-01">
    494494      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    495495      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines HTTP/1.1 conditional requests, including metadata header fields for indicating state changes, request header fields for making preconditions on such state, and rules for constructing the responses to a conditional request when one or more preconditions evaluate to false.">
     
    517517            </tr>
    518518            <tr>
    519                <td class="left">Expires: December 5, 2013</td>
    520                <td class="right">June 3, 2013</td>
     519               <td class="left">Expires: January 2, 2014</td>
     520               <td class="right">July 1, 2013</td>
    521521            </tr>
    522522         </tbody>
     
    545545         in progress”.
    546546      </p>
    547       <p>This Internet-Draft will expire on December 5, 2013.</p>
     547      <p>This Internet-Draft will expire on January 2, 2014.</p>
    548548      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    549549      <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    783783  <a href="#header.etag" class="smpl">etagc</a>      = %x21 / %x23-7E / <a href="#imported.abnf" class="smpl">obs-text</a>
    784784             ; <a href="#imported.abnf" class="smpl">VCHAR</a> except double quotes, plus obs-text
    785 </pre><div class="note" id="rfc.section.2.3.p.3"> 
    786          <p> <b>Note:</b> Previously, opaque-tag was defined to be a quoted-string (<a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, <a href="http://tools.ietf.org/html/rfc2616#section-3.11">Section 3.11</a>), thus some recipients might perform backslash unescaping. Servers therefore ought to avoid backslash characters in entity
     785</pre><div class="note" id="rfc.section.2.3.p.3">
     786         <p><b>Note:</b> Previously, opaque-tag was defined to be a quoted-string (<a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, <a href="http://tools.ietf.org/html/rfc2616#section-3.11">Section 3.11</a>), thus some recipients might perform backslash unescaping. Servers therefore ought to avoid backslash characters in entity
    787787            tags.
    788788         </p>
     
    897897Content-Encoding: gzip
    898898
    899 <em>...binary data...</em></pre><div class="note" id="rfc.section.2.3.3.p.7"> 
    900          <p> <b>Note:</b> Content codings are a property of the representation, so therefore an entity-tag of an encoded representation has to be distinct
     899<em>...binary data...</em></pre><div class="note" id="rfc.section.2.3.3.p.7">
     900         <p><b>Note:</b> Content codings are a property of the representation, so therefore an entity-tag of an encoded representation has to be distinct
    901901            from an unencoded representation to prevent conflicts during cache updates and range requests. In contrast, transfer codings
    902902            (<a href="p1-messaging.html#transfer.codings" title="Transfer Codings">Section 4</a> of <a href="#Part1" id="rfc.xref.Part1.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) apply only during message transfer and do not require distinct entity-tags.
     
    10231023         selected representation's <a href="#header.last-modified" class="smpl">Last-Modified</a> field will not be able to help the user agent limit its data transfers to only those changed during the specified window.
    10241024      </p>
    1025       <div class="note" id="rfc.section.3.3.p.9"> 
    1026          <p> <b>Note:</b> If a client uses an arbitrary date in the If-Modified-Since header field instead of a date taken from a <a href="#header.last-modified" class="smpl">Last-Modified</a> or <a href="p2-semantics.html#header.date" class="smpl">Date</a> header field from the origin server, the client ought to be aware that its date will be interpreted according to the server's
     1025      <div class="note" id="rfc.section.3.3.p.9">
     1026         <p><b>Note:</b> If a client uses an arbitrary date in the If-Modified-Since header field instead of a date taken from a <a href="#header.last-modified" class="smpl">Last-Modified</a> or <a href="p2-semantics.html#header.date" class="smpl">Date</a> header field from the origin server, the client ought to be aware that its date will be interpreted according to the server's
    10271027            understanding of time.
    10281028         </p>
     
    11231123         <li id="precedence5">When the method is GET and both <a href="p5-range.html#header.range" class="smpl">Range</a> and <a href="p5-range.html#header.if-range" class="smpl">If-Range</a> are present, evaluate If-Range:
    11241124            <ul>
    1125                <li>if the validator matches and the Range specification is applicable to the selected representation, respond <a href="p5-range.html#status.206" class="smpl">206 (Partial Content)</a>  <a href="#Part5" id="rfc.xref.Part5.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a></li>
     1125               <li>if the validator matches and the Range specification is applicable to the selected representation, respond <a href="p5-range.html#status.206" class="smpl">206 (Partial Content)</a> <a href="#Part5" id="rfc.xref.Part5.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a></li>
    11261126            </ul>
    11271127         </li>
     
    11541154                  <td class="left">304</td>
    11551155                  <td class="left">Not Modified</td>
    1156                   <td class="left"> <a href="#status.304" id="rfc.xref.status.304.1" title="304 Not Modified">Section&nbsp;4.1</a>
     1156                  <td class="left"><a href="#status.304" id="rfc.xref.status.304.1" title="304 Not Modified">Section&nbsp;4.1</a>
    11571157                  </td>
    11581158               </tr>
     
    11601160                  <td class="left">412</td>
    11611161                  <td class="left">Precondition Failed</td>
    1162                   <td class="left"> <a href="#status.412" id="rfc.xref.status.412.1" title="412 Precondition Failed">Section&nbsp;4.2</a>
     1162                  <td class="left"><a href="#status.412" id="rfc.xref.status.412.1" title="412 Precondition Failed">Section&nbsp;4.2</a>
    11631163                  </td>
    11641164               </tr>
     
    11881188                  <td class="left">http</td>
    11891189                  <td class="left">standard</td>
    1190                   <td class="left"> <a href="#header.etag" id="rfc.xref.header.etag.2" title="ETag">Section&nbsp;2.3</a>
     1190                  <td class="left"><a href="#header.etag" id="rfc.xref.header.etag.2" title="ETag">Section&nbsp;2.3</a>
    11911191                  </td>
    11921192               </tr>
     
    11951195                  <td class="left">http</td>
    11961196                  <td class="left">standard</td>
    1197                   <td class="left"> <a href="#header.if-match" id="rfc.xref.header.if-match.1" title="If-Match">Section&nbsp;3.1</a>
     1197                  <td class="left"><a href="#header.if-match" id="rfc.xref.header.if-match.1" title="If-Match">Section&nbsp;3.1</a>
    11981198                  </td>
    11991199               </tr>
     
    12021202                  <td class="left">http</td>
    12031203                  <td class="left">standard</td>
    1204                   <td class="left"> <a href="#header.if-modified-since" id="rfc.xref.header.if-modified-since.1" title="If-Modified-Since">Section&nbsp;3.3</a>
     1204                  <td class="left"><a href="#header.if-modified-since" id="rfc.xref.header.if-modified-since.1" title="If-Modified-Since">Section&nbsp;3.3</a>
    12051205                  </td>
    12061206               </tr>
     
    12091209                  <td class="left">http</td>
    12101210                  <td class="left">standard</td>
    1211                   <td class="left"> <a href="#header.if-none-match" id="rfc.xref.header.if-none-match.1" title="If-None-Match">Section&nbsp;3.2</a>
     1211                  <td class="left"><a href="#header.if-none-match" id="rfc.xref.header.if-none-match.1" title="If-None-Match">Section&nbsp;3.2</a>
    12121212                  </td>
    12131213               </tr>
     
    12161216                  <td class="left">http</td>
    12171217                  <td class="left">standard</td>
    1218                   <td class="left"> <a href="#header.if-unmodified-since" id="rfc.xref.header.if-unmodified-since.1" title="If-Unmodified-Since">Section&nbsp;3.4</a>
     1218                  <td class="left"><a href="#header.if-unmodified-since" id="rfc.xref.header.if-unmodified-since.1" title="If-Unmodified-Since">Section&nbsp;3.4</a>
    12191219                  </td>
    12201220               </tr>
     
    12231223                  <td class="left">http</td>
    12241224                  <td class="left">standard</td>
    1225                   <td class="left"> <a href="#header.last-modified" id="rfc.xref.header.last-modified.2" title="Last-Modified">Section&nbsp;2.2</a>
     1225                  <td class="left"><a href="#header.last-modified" id="rfc.xref.header.last-modified.2" title="Last-Modified">Section&nbsp;2.2</a>
    12261226                  </td>
    12271227               </tr>
     
    12561256         <tr>
    12571257            <td class="reference"><b id="Part1">[Part1]</b></td>
    1258             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-latest (work in progress), June&nbsp;2013.
     1258            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-latest (work in progress), July&nbsp;2013.
    12591259            </td>
    12601260         </tr>
    12611261         <tr>
    12621262            <td class="reference"><b id="Part2">[Part2]</b></td>
    1263             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p2-semantics-latest (work in progress), June&nbsp;2013.
     1263            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p2-semantics-latest (work in progress), July&nbsp;2013.
    12641264            </td>
    12651265         </tr>
    12661266         <tr>
    12671267            <td class="reference"><b id="Part5">[Part5]</b></td>
    1268             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">Hypertext Transfer Protocol (HTTP/1.1): Range Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-latest (work in progress), June&nbsp;2013.
     1268            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">Hypertext Transfer Protocol (HTTP/1.1): Range Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-latest (work in progress), July&nbsp;2013.
    12691269            </td>
    12701270         </tr>
    12711271         <tr>
    12721272            <td class="reference"><b id="Part6">[Part6]</b></td>
    1273             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:mnot@mnot.net" title="Akamai">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">Hypertext Transfer Protocol (HTTP/1.1): Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-latest (work in progress), June&nbsp;2013.
     1273            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:mnot@mnot.net" title="Akamai">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">Hypertext Transfer Protocol (HTTP/1.1): Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-latest (work in progress), July&nbsp;2013.
    12741274            </td>
    12751275         </tr>
     
    13681368      <p id="rfc.section.D.1.p.1">Closed issues: </p>
    13691369      <ul>
    1370          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/241">http://tools.ietf.org/wg/httpbis/trac/ticket/241</a>&gt;: "Need to clarify eval order/interaction of conditional headers"
    1371          </li>
    1372          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/345">http://tools.ietf.org/wg/httpbis/trac/ticket/345</a>&gt;: "Required headers on 304 and 206"
    1373          </li>
    1374          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/350">http://tools.ietf.org/wg/httpbis/trac/ticket/350</a>&gt;: "Optionality of Conditional Request Support"
    1375          </li>
    1376          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/354">http://tools.ietf.org/wg/httpbis/trac/ticket/354</a>&gt;: "ETags and Conditional Requests"
    1377          </li>
    1378          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/361">http://tools.ietf.org/wg/httpbis/trac/ticket/361</a>&gt;: "ABNF requirements for recipients"
    1379          </li>
    1380          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/363">http://tools.ietf.org/wg/httpbis/trac/ticket/363</a>&gt;: "Rare cases"
    1381          </li>
    1382          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/365">http://tools.ietf.org/wg/httpbis/trac/ticket/365</a>&gt;: "Conditional Request Security Considerations"
    1383          </li>
    1384          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/371">http://tools.ietf.org/wg/httpbis/trac/ticket/371</a>&gt;: "If-Modified-Since lacks definition for method != GET"
    1385          </li>
    1386          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/372">http://tools.ietf.org/wg/httpbis/trac/ticket/372</a>&gt;: "refactor conditional header field descriptions"
     1370         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/241">http://tools.ietf.org/wg/httpbis/trac/ticket/241</a>&gt;: "Need to clarify eval order/interaction of conditional headers"
     1371         </li>
     1372         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/345">http://tools.ietf.org/wg/httpbis/trac/ticket/345</a>&gt;: "Required headers on 304 and 206"
     1373         </li>
     1374         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/350">http://tools.ietf.org/wg/httpbis/trac/ticket/350</a>&gt;: "Optionality of Conditional Request Support"
     1375         </li>
     1376         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/354">http://tools.ietf.org/wg/httpbis/trac/ticket/354</a>&gt;: "ETags and Conditional Requests"
     1377         </li>
     1378         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/361">http://tools.ietf.org/wg/httpbis/trac/ticket/361</a>&gt;: "ABNF requirements for recipients"
     1379         </li>
     1380         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/363">http://tools.ietf.org/wg/httpbis/trac/ticket/363</a>&gt;: "Rare cases"
     1381         </li>
     1382         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/365">http://tools.ietf.org/wg/httpbis/trac/ticket/365</a>&gt;: "Conditional Request Security Considerations"
     1383         </li>
     1384         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/371">http://tools.ietf.org/wg/httpbis/trac/ticket/371</a>&gt;: "If-Modified-Since lacks definition for method != GET"
     1385         </li>
     1386         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/372">http://tools.ietf.org/wg/httpbis/trac/ticket/372</a>&gt;: "refactor conditional header field descriptions"
    13871387         </li>
    13881388      </ul>
    13891389      <h2 id="rfc.section.D.2"><a href="#rfc.section.D.2">D.2</a>&nbsp;<a id="changes.since.20" href="#changes.since.20">Since draft-ietf-httpbis-p4-conditional-20</a></h2>
    1390       <p id="rfc.section.D.2.p.1"> </p>
     1390      <p id="rfc.section.D.2.p.1"></p>
    13911391      <ul>
    13921392         <li>Conformance criteria and considerations regarding error handling are now defined in Part 1.</li>
     
    13951395      <p id="rfc.section.D.3.p.1">Closed issues: </p>
    13961396      <ul>
    1397          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/96">http://tools.ietf.org/wg/httpbis/trac/ticket/96</a>&gt;: "Conditional GET text"
    1398          </li>
    1399          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/350">http://tools.ietf.org/wg/httpbis/trac/ticket/350</a>&gt;: "Optionality of Conditional Request Support"
    1400          </li>
    1401          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/384">http://tools.ietf.org/wg/httpbis/trac/ticket/384</a>&gt;: "unclear prose in definition of 304"
    1402          </li>
    1403          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/401">http://tools.ietf.org/wg/httpbis/trac/ticket/401</a>&gt;: "ETags and Conneg"
    1404          </li>
    1405          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/402">http://tools.ietf.org/wg/httpbis/trac/ticket/402</a>&gt;: "Comparison function for If-Match and If-None-Match"
    1406          </li>
    1407          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/406">http://tools.ietf.org/wg/httpbis/trac/ticket/406</a>&gt;: "304 without validator"
    1408          </li>
    1409          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/427">http://tools.ietf.org/wg/httpbis/trac/ticket/427</a>&gt;: "If-Match and 428"
     1397         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/96">http://tools.ietf.org/wg/httpbis/trac/ticket/96</a>&gt;: "Conditional GET text"
     1398         </li>
     1399         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/350">http://tools.ietf.org/wg/httpbis/trac/ticket/350</a>&gt;: "Optionality of Conditional Request Support"
     1400         </li>
     1401         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/384">http://tools.ietf.org/wg/httpbis/trac/ticket/384</a>&gt;: "unclear prose in definition of 304"
     1402         </li>
     1403         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/401">http://tools.ietf.org/wg/httpbis/trac/ticket/401</a>&gt;: "ETags and Conneg"
     1404         </li>
     1405         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/402">http://tools.ietf.org/wg/httpbis/trac/ticket/402</a>&gt;: "Comparison function for If-Match and If-None-Match"
     1406         </li>
     1407         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/406">http://tools.ietf.org/wg/httpbis/trac/ticket/406</a>&gt;: "304 without validator"
     1408         </li>
     1409         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/427">http://tools.ietf.org/wg/httpbis/trac/ticket/427</a>&gt;: "If-Match and 428"
    14101410         </li>
    14111411      </ul>
     
    14131413      <p id="rfc.section.D.4.p.1">Closed issues: </p>
    14141414      <ul>
    1415          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/436">http://tools.ietf.org/wg/httpbis/trac/ticket/436</a>&gt;: "explain list expansion in ABNF appendices"
    1416          </li>
    1417          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/437">http://tools.ietf.org/wg/httpbis/trac/ticket/437</a>&gt;: "incorrect example dates"
     1415         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/436">http://tools.ietf.org/wg/httpbis/trac/ticket/436</a>&gt;: "explain list expansion in ABNF appendices"
     1416         </li>
     1417         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/437">http://tools.ietf.org/wg/httpbis/trac/ticket/437</a>&gt;: "incorrect example dates"
    14181418         </li>
    14191419      </ul>
    14201420      <p id="rfc.section.D.4.p.2">Partly resolved issues: </p>
    14211421      <ul>
    1422          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/461">http://tools.ietf.org/wg/httpbis/trac/ticket/461</a>&gt;: "Editorial suggestions"
     1422         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/461">http://tools.ietf.org/wg/httpbis/trac/ticket/461</a>&gt;: "Editorial suggestions"
    14231423         </li>
    14241424      </ul>
  • draft-ietf-httpbis/latest/p4-conditional.xml

    r2280 r2301  
    1313  <!ENTITY SHOULD-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHOULD NOT</bcp14>">
    1414  <!ENTITY ID-VERSION "latest">
    15   <!ENTITY ID-MONTH "June">
     15  <!ENTITY ID-MONTH "July">
    1616  <!ENTITY ID-YEAR "2013">
    1717  <!ENTITY Note "<x:h xmlns:x='http://purl.org/net/xml2rfc/ext'>Note:</x:h>">
  • draft-ietf-httpbis/latest/p5-range.html

    r2299 r2301  
    440440  }
    441441  @top-right {
    442        content: "June 2013";
     442       content: "July 2013";
    443443  }
    444444  @top-center {
     
    449449  }
    450450  @bottom-center {
    451        content: "Expires December 22, 2013";
     451       content: "Expires January 2, 2014";
    452452  }
    453453  @bottom-right {
     
    486486      <link href="p4-conditional.html" rel="prev">
    487487      <link href="p6-cache.html" rel="next">
    488       <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.597, 2013/05/27 06:39:42, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
     488      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.598, 2013/06/23 14:11:10, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
    489489      <link rel="schema.dct" href="http://purl.org/dc/terms/">
    490490      <meta name="dct.creator" content="Fielding, R.">
     
    492492      <meta name="dct.creator" content="Reschke, J. F.">
    493493      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest">
    494       <meta name="dct.issued" scheme="ISO8601" content="2013-06-20">
     494      <meta name="dct.issued" scheme="ISO8601" content="2013-07-01">
    495495      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    496496      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines range requests and the rules for constructing and combining responses to those requests.">
     
    518518            </tr>
    519519            <tr>
    520                <td class="left">Expires: December 22, 2013</td>
     520               <td class="left">Expires: January 2, 2014</td>
    521521               <td class="right">J. Reschke, Editor</td>
    522522            </tr>
     
    527527            <tr>
    528528               <td class="left"></td>
    529                <td class="right">June 20, 2013</td>
     529               <td class="right">July 1, 2013</td>
    530530            </tr>
    531531         </tbody>
     
    552552         in progress”.
    553553      </p>
    554       <p>This Internet-Draft will expire on December 22, 2013.</p>
     554      <p>This Internet-Draft will expire on January 2, 2014.</p>
    555555      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    556556      <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    662662      <div id="rfc.figure.u.2"></div><pre class="inline"><span id="rfc.iref.g.4"></span>  <a href="#byte.ranges" class="smpl">bytes-unit</a>       = "bytes"
    663663</pre><div id="rule.ranges-specifier">
    664          <p id="rfc.section.2.1.p.3">                A byte range request can specify a single range of bytes, or a set of ranges within a single representation.</p>
     664         <p id="rfc.section.2.1.p.3">        A byte range request can specify a single range of bytes, or a set of ranges within a single representation.</p>
    665665      </div>
    666666      <div id="rfc.figure.u.3"></div><pre class="inline"><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span><span id="rfc.iref.g.10"></span>  <a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a> = <a href="#byte.ranges" class="smpl">bytes-unit</a> "=" <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a>
     
    878878</pre><p id="rfc.section.4.2.p.7">and this second example illustrates when the complete length is unknown:</p>
    879879      <div id="rfc.figure.u.21"></div><pre class="text">  Content-Range: bytes 42-1233/*
    880 </pre><p id="rfc.section.4.2.p.9">A Content-Range field value is invalid if it contains a <a href="#header.content-range" class="smpl">byte-range-resp</a> that has a <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> value less than its <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> value, or a <a href="#header.content-range" class="smpl">complete-length</a> value less than or equal to its <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> value. The recipient of an invalid <a href="#header.content-range" class="smpl">Content-Range</a>  <em class="bcp14">MUST NOT</em> attempt to recombine the received content with a stored representation.
     880</pre><p id="rfc.section.4.2.p.9">A Content-Range field value is invalid if it contains a <a href="#header.content-range" class="smpl">byte-range-resp</a> that has a <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> value less than its <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> value, or a <a href="#header.content-range" class="smpl">complete-length</a> value less than or equal to its <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> value. The recipient of an invalid <a href="#header.content-range" class="smpl">Content-Range</a> <em class="bcp14">MUST NOT</em> attempt to recombine the received content with a stored representation.
    881881      </p>
    882882      <p id="rfc.section.4.2.p.10">A server generating a <a href="#status.416" class="smpl">416 (Range Not Satisfiable)</a> response to a byte range request <em class="bcp14">SHOULD</em> send a Content-Range header field with an <a href="#header.content-range" class="smpl">unsatisfied-range</a> value, as in the following example:
     
    932932Date: Fri, 20 Jan 2012 15:41:54 GMT
    933933Content-Range: bytes */47022
    934 </pre><div class="note" id="rfc.section.4.4.p.4"> 
    935          <p> <b>Note:</b> Because servers are free to ignore <a href="#header.range" class="smpl">Range</a>, many implementations will simply respond with the entire selected representation in a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response. That is partly because most clients are prepared to receive a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> to complete the task (albeit less efficiently) and partly because clients might not stop making an invalid partial request
     934</pre><div class="note" id="rfc.section.4.4.p.4">
     935         <p><b>Note:</b> Because servers are free to ignore <a href="#header.range" class="smpl">Range</a>, many implementations will simply respond with the entire selected representation in a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response. That is partly because most clients are prepared to receive a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> to complete the task (albeit less efficiently) and partly because clients might not stop making an invalid partial request
    936936            until they have received a complete representation. Thus, clients cannot depend on receiving a <a href="#status.416" class="smpl">416 (Range Not Satisfiable)</a> response even when it is most appropriate.
    937937         </p>
     
    996996                  <td class="left">206</td>
    997997                  <td class="left">Partial Content</td>
    998                   <td class="left"> <a href="#status.206" id="rfc.xref.status.206.1" title="206 Partial Content">Section&nbsp;4.1</a>
     998                  <td class="left"><a href="#status.206" id="rfc.xref.status.206.1" title="206 Partial Content">Section&nbsp;4.1</a>
    999999                  </td>
    10001000               </tr>
     
    10021002                  <td class="left">416</td>
    10031003                  <td class="left">Range Not Satisfiable</td>
    1004                   <td class="left"> <a href="#status.416" id="rfc.xref.status.416.1" title="416 Range Not Satisfiable">Section&nbsp;4.4</a>
     1004                  <td class="left"><a href="#status.416" id="rfc.xref.status.416.1" title="416 Range Not Satisfiable">Section&nbsp;4.4</a>
    10051005                  </td>
    10061006               </tr>
     
    10301030                  <td class="left">http</td>
    10311031                  <td class="left">standard</td>
    1032                   <td class="left"> <a href="#header.accept-ranges" id="rfc.xref.header.accept-ranges.3" title="Accept-Ranges">Section&nbsp;2.3</a>
     1032                  <td class="left"><a href="#header.accept-ranges" id="rfc.xref.header.accept-ranges.3" title="Accept-Ranges">Section&nbsp;2.3</a>
    10331033                  </td>
    10341034               </tr>
     
    10371037                  <td class="left">http</td>
    10381038                  <td class="left">standard</td>
    1039                   <td class="left"> <a href="#header.content-range" id="rfc.xref.header.content-range.3" title="Content-Range">Section&nbsp;4.2</a>
     1039                  <td class="left"><a href="#header.content-range" id="rfc.xref.header.content-range.3" title="Content-Range">Section&nbsp;4.2</a>
    10401040                  </td>
    10411041               </tr>
     
    10441044                  <td class="left">http</td>
    10451045                  <td class="left">standard</td>
    1046                   <td class="left"> <a href="#header.if-range" id="rfc.xref.header.if-range.2" title="If-Range">Section&nbsp;3.2</a>
     1046                  <td class="left"><a href="#header.if-range" id="rfc.xref.header.if-range.2" title="If-Range">Section&nbsp;3.2</a>
    10471047                  </td>
    10481048               </tr>
     
    10511051                  <td class="left">http</td>
    10521052                  <td class="left">standard</td>
    1053                   <td class="left"> <a href="#header.range" id="rfc.xref.header.range.4" title="Range">Section&nbsp;3.1</a>
     1053                  <td class="left"><a href="#header.range" id="rfc.xref.header.range.4" title="Range">Section&nbsp;3.1</a>
    10541054                  </td>
    10551055               </tr>
     
    10791079         <tr>
    10801080            <td class="reference"><b id="Part1">[Part1]</b></td>
    1081             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-latest (work in progress), June&nbsp;2013.
     1081            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-latest (work in progress), July&nbsp;2013.
    10821082            </td>
    10831083         </tr>
    10841084         <tr>
    10851085            <td class="reference"><b id="Part2">[Part2]</b></td>
    1086             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p2-semantics-latest (work in progress), June&nbsp;2013.
     1086            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p2-semantics-latest (work in progress), July&nbsp;2013.
    10871087            </td>
    10881088         </tr>
    10891089         <tr>
    10901090            <td class="reference"><b id="Part4">[Part4]</b></td>
    1091             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-latest (work in progress), June&nbsp;2013.
     1091            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-latest (work in progress), July&nbsp;2013.
    10921092            </td>
    10931093         </tr>
    10941094         <tr>
    10951095            <td class="reference"><b id="Part6">[Part6]</b></td>
    1096             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:mnot@mnot.net" title="Akamai">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">Hypertext Transfer Protocol (HTTP/1.1): Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-latest (work in progress), June&nbsp;2013.
     1096            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:mnot@mnot.net" title="Akamai">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">Hypertext Transfer Protocol (HTTP/1.1): Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-latest (work in progress), July&nbsp;2013.
    10971097            </td>
    10981098         </tr>
     
    11561156      <p id="rfc.section.A.p.2">The multipart/byteranges media type includes one or more body parts, each with its own <a href="p2-semantics.html#header.content-type" class="smpl">Content-Type</a> and <a href="#header.content-range" class="smpl">Content-Range</a> fields. The required boundary parameter specifies the boundary string used to separate each body part.
    11571157      </p>
    1158       <p id="rfc.section.A.p.3"> </p>
     1158      <p id="rfc.section.A.p.3"></p>
    11591159      <dl>
    11601160         <dt>Type name:</dt>
     
    11781178         <dd>HTTP components supporting multiple ranges in a single request.</dd>
    11791179         <dt>Additional information:</dt>
    1180          <dd> 
     1180         <dd>
    11811181            <dl>
    11821182               <dt>Magic number(s):</dt>
     
    13101310      <p id="rfc.section.E.1.p.1">Closed issues: </p>
    13111311      <ul>
    1312          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/358">http://tools.ietf.org/wg/httpbis/trac/ticket/358</a>&gt;: "ABNF list expansion code problem"
    1313          </li>
    1314          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/361">http://tools.ietf.org/wg/httpbis/trac/ticket/361</a>&gt;: "ABNF requirements for recipients"
    1315          </li>
    1316          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/367">http://tools.ietf.org/wg/httpbis/trac/ticket/367</a>&gt;: "reserve 'none' as byte range unit"
    1317          </li>
    1318          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/368">http://tools.ietf.org/wg/httpbis/trac/ticket/368</a>&gt;: "note introduction of new IANA registries as normative changes"
    1319          </li>
    1320          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/369">http://tools.ietf.org/wg/httpbis/trac/ticket/369</a>&gt;: "range units vs leading zeroes vs size"
     1312         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/358">http://tools.ietf.org/wg/httpbis/trac/ticket/358</a>&gt;: "ABNF list expansion code problem"
     1313         </li>
     1314         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/361">http://tools.ietf.org/wg/httpbis/trac/ticket/361</a>&gt;: "ABNF requirements for recipients"
     1315         </li>
     1316         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/367">http://tools.ietf.org/wg/httpbis/trac/ticket/367</a>&gt;: "reserve 'none' as byte range unit"
     1317         </li>
     1318         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/368">http://tools.ietf.org/wg/httpbis/trac/ticket/368</a>&gt;: "note introduction of new IANA registries as normative changes"
     1319         </li>
     1320         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/369">http://tools.ietf.org/wg/httpbis/trac/ticket/369</a>&gt;: "range units vs leading zeroes vs size"
    13211321         </li>
    13221322      </ul>
    13231323      <h2 id="rfc.section.E.2"><a href="#rfc.section.E.2">E.2</a>&nbsp;<a id="changes.since.20" href="#changes.since.20">Since draft-ietf-httpbis-p5-range-20</a></h2>
    1324       <p id="rfc.section.E.2.p.1"> </p>
     1324      <p id="rfc.section.E.2.p.1"></p>
    13251325      <ul>
    13261326         <li>Conformance criteria and considerations regarding error handling are now defined in Part 1.</li>
     
    13291329      <p id="rfc.section.E.3.p.1">Closed issues: </p>
    13301330      <ul>
    1331          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/175">http://tools.ietf.org/wg/httpbis/trac/ticket/175</a>&gt;: "Security consideration: range flooding"
    1332          </li>
    1333          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/223">http://tools.ietf.org/wg/httpbis/trac/ticket/223</a>&gt;: "Allowing heuristic caching for new status codes"
    1334          </li>
    1335          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/311">http://tools.ietf.org/wg/httpbis/trac/ticket/311</a>&gt;: "Add limitations to Range to reduce its use as a denial-of-service tool"
    1336          </li>
    1337          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/407">http://tools.ietf.org/wg/httpbis/trac/ticket/407</a>&gt;: "416 and multipart/byteranges"
     1331         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/175">http://tools.ietf.org/wg/httpbis/trac/ticket/175</a>&gt;: "Security consideration: range flooding"
     1332         </li>
     1333         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/223">http://tools.ietf.org/wg/httpbis/trac/ticket/223</a>&gt;: "Allowing heuristic caching for new status codes"
     1334         </li>
     1335         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/311">http://tools.ietf.org/wg/httpbis/trac/ticket/311</a>&gt;: "Add limitations to Range to reduce its use as a denial-of-service tool"
     1336         </li>
     1337         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/407">http://tools.ietf.org/wg/httpbis/trac/ticket/407</a>&gt;: "416 and multipart/byteranges"
    13381338         </li>
    13391339      </ul>
     
    13411341      <p id="rfc.section.E.4.p.1">Closed issues: </p>
    13421342      <ul>
    1343          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/436">http://tools.ietf.org/wg/httpbis/trac/ticket/436</a>&gt;: "explain list expansion in ABNF appendices"
    1344          </li>
    1345          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/437">http://tools.ietf.org/wg/httpbis/trac/ticket/437</a>&gt;: "incorrect example dates"
    1346          </li>
    1347          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/438">http://tools.ietf.org/wg/httpbis/trac/ticket/438</a>&gt;: "media type registration template issues"
    1348          </li>
    1349          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/462">http://tools.ietf.org/wg/httpbis/trac/ticket/462</a>&gt;: "Editorial suggestions"
    1350          </li>
    1351          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/485">http://tools.ietf.org/wg/httpbis/trac/ticket/485</a>&gt;: "MUSTs and other feedback"
     1343         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/436">http://tools.ietf.org/wg/httpbis/trac/ticket/436</a>&gt;: "explain list expansion in ABNF appendices"
     1344         </li>
     1345         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/437">http://tools.ietf.org/wg/httpbis/trac/ticket/437</a>&gt;: "incorrect example dates"
     1346         </li>
     1347         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/438">http://tools.ietf.org/wg/httpbis/trac/ticket/438</a>&gt;: "media type registration template issues"
     1348         </li>
     1349         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/462">http://tools.ietf.org/wg/httpbis/trac/ticket/462</a>&gt;: "Editorial suggestions"
     1350         </li>
     1351         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/485">http://tools.ietf.org/wg/httpbis/trac/ticket/485</a>&gt;: "MUSTs and other feedback"
    13521352         </li>
    13531353      </ul>
  • draft-ietf-httpbis/latest/p5-range.xml

    r2299 r2301  
    1313  <!ENTITY SHOULD-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHOULD NOT</bcp14>">
    1414  <!ENTITY ID-VERSION "latest">
    15   <!ENTITY ID-MONTH "June">
     15  <!ENTITY ID-MONTH "July">
    1616  <!ENTITY ID-YEAR "2013">
    1717  <!ENTITY Note "<x:h xmlns:x='http://purl.org/net/xml2rfc/ext'>Note:</x:h>">
  • draft-ietf-httpbis/latest/p6-cache.html

    r2283 r2301  
    443443  }
    444444  @top-right {
    445        content: "June 2013";
     445       content: "July 2013";
    446446  }
    447447  @top-center {
     
    452452  }
    453453  @bottom-center {
    454        content: "Expires December 6, 2013";
     454       content: "Expires January 2, 2014";
    455455  }
    456456  @bottom-right {
     
    492492      <link href="p5-range.html" rel="prev">
    493493      <link href="p7-auth.html" rel="next">
    494       <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.597, 2013/05/27 06:39:42, XSLT vendor: SAXON 9.1.0.8 from Saxonica http://www.saxonica.com/">
     494      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.598, 2013/06/23 14:11:10, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
    495495      <link rel="schema.dct" href="http://purl.org/dc/terms/">
    496496      <meta name="dct.creator" content="Fielding, R.">
     
    498498      <meta name="dct.creator" content="Reschke, J. F.">
    499499      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest">
    500       <meta name="dct.issued" scheme="ISO8601" content="2013-06-04">
     500      <meta name="dct.issued" scheme="ISO8601" content="2013-07-01">
    501501      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    502502      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages.">
     
    524524            </tr>
    525525            <tr>
    526                <td class="left">Expires: December 6, 2013</td>
     526               <td class="left">Expires: January 2, 2014</td>
    527527               <td class="right">J. Reschke, Editor</td>
    528528            </tr>
     
    533533            <tr>
    534534               <td class="left"></td>
    535                <td class="right">June 4, 2013</td>
     535               <td class="right">July 1, 2013</td>
    536536            </tr>
    537537         </tbody>
     
    559559         in progress”.
    560560      </p>
    561       <p>This Internet-Draft will expire on December 6, 2013.</p>
     561      <p>This Internet-Draft will expire on January 2, 2014.</p>
    562562      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    563563      <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    886886      </p>
    887887      <p id="rfc.section.4.1.p.11">When calculating freshness, to avoid common problems in date parsing:</p>
    888       <p id="rfc.section.4.1.p.12"> </p>
     888      <p id="rfc.section.4.1.p.12"></p>
    889889      <ul>
    890890         <li>Although all date formats are specified to be case-sensitive, cache recipients <em class="bcp14">SHOULD</em> match day, week and timezone names case-insensitively.
     
    932932         present.
    933933      </p>
    934       <div class="note" id="rfc.section.4.1.2.p.5"> 
    935          <p> <b>Note:</b> <a href="http://tools.ietf.org/html/rfc2616#section-13.9">Section 13.9</a> of <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a> prohibited caches from calculating heuristic freshness for URIs with query components (i.e., those containing '?'). In practice,
     934      <div class="note" id="rfc.section.4.1.2.p.5">
     935         <p><b>Note:</b> <a href="http://tools.ietf.org/html/rfc2616#section-13.9">Section 13.9</a> of <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a> prohibited caches from calculating heuristic freshness for URIs with query components (i.e., those containing '?'). In practice,
    936936            this has not been widely implemented. Therefore, origin servers are encouraged to send explicit directives (e.g., Cache-Control:
    937937            no-cache) if they wish to preclude caching.
     
    945945      </p>
    946946      <p id="rfc.section.4.1.3.p.2">The following data is used for the age calculation:</p>
    947       <p id="rfc.section.4.1.3.p.3"> <dfn>age_value</dfn>
     947      <p id="rfc.section.4.1.3.p.3"><dfn>age_value</dfn>
    948948      </p>
    949949      <ul class="empty">
     
    951951         </li>
    952952      </ul>
    953       <p id="rfc.section.4.1.3.p.4"> <dfn>date_value</dfn>
     953      <p id="rfc.section.4.1.3.p.4"><dfn>date_value</dfn>
    954954      </p>
    955955      <ul class="empty">
     
    957957         </li>
    958958      </ul>
    959       <p id="rfc.section.4.1.3.p.5"> <dfn>now</dfn>
     959      <p id="rfc.section.4.1.3.p.5"><dfn>now</dfn>
    960960      </p>
    961961      <ul class="empty">
     
    963963         </li>
    964964      </ul>
    965       <p id="rfc.section.4.1.3.p.6"> <dfn>request_time</dfn>
     965      <p id="rfc.section.4.1.3.p.6"><dfn>request_time</dfn>
    966966      </p>
    967967      <ul class="empty">
    968968         <li>The current value of the clock at the host at the time the request resulting in the stored response was made.</li>
    969969      </ul>
    970       <p id="rfc.section.4.1.3.p.7"> <dfn>response_time</dfn>
     970      <p id="rfc.section.4.1.3.p.7"><dfn>response_time</dfn>
    971971      </p>
    972972      <ul class="empty">
     
    10271027      </p>
    10281028      <p id="rfc.section.4.2.p.5">Cache handling of a response to a conditional request is dependent upon its status code:</p>
    1029       <p id="rfc.section.4.2.p.6"> </p>
     1029      <p id="rfc.section.4.2.p.6"></p>
    10301030      <ul>
    10311031         <li>A <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a> response status code indicates that the stored response can be updated and reused; see <a href="#freshening.responses" title="Freshening Stored Responses upon Validation">Section&nbsp;4.2.1</a>.
     
    11491149      <p id="rfc.section.7.2.p.2">A cache <em class="bcp14">MUST</em> obey the requirements of the Cache-Control directives defined in this section. See <a href="#cache.control.extensions" title="Cache Control Extensions">Section&nbsp;7.2.3</a> for information about how Cache-Control directives defined elsewhere are handled.
    11501150      </p>
    1151       <div class="note" id="rfc.section.7.2.p.3"> 
    1152          <p> <b>Note:</b> Some HTTP/1.0 caches might not implement Cache-Control.
     1151      <div class="note" id="rfc.section.7.2.p.3">
     1152         <p><b>Note:</b> Some HTTP/1.0 caches might not implement Cache-Control.
    11531153         </p>
    11541154      </div>
     
    11701170      <p id="rfc.section.7.2.1.1.p.1">Argument syntax: </p>
    11711171      <ul class="empty">
    1172          <li> <a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.2.1</a>)
     1172         <li><a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.2.1</a>)
    11731173         </li>
    11741174      </ul>
     
    11771177         stale response.
    11781178      </p>
    1179       <p id="rfc.section.7.2.1.1.p.3"> <b>Note:</b> This directive uses the token form of the argument syntax; e.g., 'max-age=5', not 'max-age="5"'. Senders <em class="bcp14">SHOULD NOT</em> use the quoted-string form.
     1179      <p id="rfc.section.7.2.1.1.p.3"><b>Note:</b> This directive uses the token form of the argument syntax; e.g., 'max-age=5', not 'max-age="5"'. Senders <em class="bcp14">SHOULD NOT</em> use the quoted-string form.
    11801180      </p>
    11811181      <div id="rfc.iref.m.2"></div>
     
    11831183      <p id="rfc.section.7.2.1.2.p.1">Argument syntax: </p>
    11841184      <ul class="empty">
    1185          <li> <a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.2.1</a>)
     1185         <li><a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.2.1</a>)
    11861186         </li>
    11871187      </ul>
     
    11911191         to accept a stale response of any age.
    11921192      </p>
    1193       <p id="rfc.section.7.2.1.2.p.3"> <b>Note:</b> This directive uses the token form of the argument syntax; e.g., 'max-stale=10', not 'max-stale="10"'. Senders <em class="bcp14">SHOULD NOT</em> use the quoted-string form.
     1193      <p id="rfc.section.7.2.1.2.p.3"><b>Note:</b> This directive uses the token form of the argument syntax; e.g., 'max-stale=10', not 'max-stale="10"'. Senders <em class="bcp14">SHOULD NOT</em> use the quoted-string form.
    11941194      </p>
    11951195      <div id="rfc.iref.m.3"></div>
     
    11971197      <p id="rfc.section.7.2.1.3.p.1">Argument syntax: </p>
    11981198      <ul class="empty">
    1199          <li> <a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.2.1</a>)
     1199         <li><a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.2.1</a>)
    12001200         </li>
    12011201      </ul>
     
    12041204         for at least the specified number of seconds.
    12051205      </p>
    1206       <p id="rfc.section.7.2.1.3.p.3"> <b>Note:</b> This directive uses the token form of the argument syntax; e.g., 'min-fresh=20', not 'min-fresh="20"'. Senders <em class="bcp14">SHOULD NOT</em> use the quoted-string form.
     1206      <p id="rfc.section.7.2.1.3.p.3"><b>Note:</b> This directive uses the token form of the argument syntax; e.g., 'min-fresh=20', not 'min-fresh="20"'. Senders <em class="bcp14">SHOULD NOT</em> use the quoted-string form.
    12071207      </p>
    12081208      <div id="rfc.iref.n.1"></div>
     
    12571257      </p>
    12581258      <p id="rfc.section.7.2.2.2.p.4">The field-names given are not limited to the set of header fields defined by this specification. Field names are case-insensitive.</p>
    1259       <p id="rfc.section.7.2.2.2.p.5"> <b>Note:</b> Although it has been back-ported to many implementations, some HTTP/1.0 caches will not recognize or obey this directive.
     1259      <p id="rfc.section.7.2.2.2.p.5"><b>Note:</b> Although it has been back-ported to many implementations, some HTTP/1.0 caches will not recognize or obey this directive.
    12601260         Also, no-cache response directives with field-names are often handled by caches as if an unqualified no-cache directive was
    12611261         received; i.e., the special handling for the qualified form is not widely implemented.
    12621262      </p>
    1263       <p id="rfc.section.7.2.2.2.p.6"> <b>Note:</b> This directive uses the quoted-string form of the argument syntax. Senders <em class="bcp14">SHOULD NOT</em> use the token form (even if quoting appears not to be needed for single-entry lists).
     1263      <p id="rfc.section.7.2.2.2.p.6"><b>Note:</b> This directive uses the quoted-string form of the argument syntax. Senders <em class="bcp14">SHOULD NOT</em> use the token form (even if quoting appears not to be needed for single-entry lists).
    12641264      </p>
    12651265      <div id="rfc.iref.n.5"></div>
     
    12921292      </p>
    12931293      <p id="rfc.section.7.2.2.6.p.4">The field-names given are not limited to the set of header fields defined by this specification. Field names are case-insensitive.</p>
    1294       <p id="rfc.section.7.2.2.6.p.5"> <b>Note:</b> This usage of the word "private" only controls where the response can be stored; it cannot ensure the privacy of the message
     1294      <p id="rfc.section.7.2.2.6.p.5"><b>Note:</b> This usage of the word "private" only controls where the response can be stored; it cannot ensure the privacy of the message
    12951295         content. Also, private response directives with field-names are often handled by caches as if an unqualified private directive
    12961296         was received; i.e., the special handling for the qualified form is not widely implemented.
    12971297      </p>
    1298       <p id="rfc.section.7.2.2.6.p.6"> <b>Note:</b> This directive uses the quoted-string form of the argument syntax. Senders <em class="bcp14">SHOULD NOT</em> use the token form (even if quoting appears not to be needed for single-entry lists).
     1298      <p id="rfc.section.7.2.2.6.p.6"><b>Note:</b> This directive uses the quoted-string form of the argument syntax. Senders <em class="bcp14">SHOULD NOT</em> use the token form (even if quoting appears not to be needed for single-entry lists).
    12991299      </p>
    13001300      <div id="rfc.iref.p.4"></div>
     
    13071307      <p id="rfc.section.7.2.2.8.p.1">Argument syntax: </p>
    13081308      <ul class="empty">
    1309          <li> <a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.2.1</a>)
     1309         <li><a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.2.1</a>)
    13101310         </li>
    13111311      </ul>
     
    13131313         number of seconds.
    13141314      </p>
    1315       <p id="rfc.section.7.2.2.8.p.3"> <b>Note:</b> This directive uses the token form of the argument syntax; e.g., 'max-age=5', not 'max-age="5"'. Senders <em class="bcp14">SHOULD NOT</em> use the quoted-string form.
     1315      <p id="rfc.section.7.2.2.8.p.3"><b>Note:</b> This directive uses the token form of the argument syntax; e.g., 'max-age=5', not 'max-age="5"'. Senders <em class="bcp14">SHOULD NOT</em> use the quoted-string form.
    13161316      </p>
    13171317      <div id="rfc.iref.s.4"></div>
     
    13191319      <p id="rfc.section.7.2.2.9.p.1">Argument syntax: </p>
    13201320      <ul class="empty">
    1321          <li> <a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.2.1</a>)
     1321         <li><a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.2.1</a>)
    13221322         </li>
    13231323      </ul>
     
    13251325         the maximum age specified by either the max-age directive or the <a href="#header.expires" class="smpl">Expires</a> header field. The s-maxage directive also implies the semantics of the proxy-revalidate response directive.
    13261326      </p>
    1327       <p id="rfc.section.7.2.2.9.p.3"> <b>Note:</b> This directive uses the token form of the argument syntax; e.g., 's-maxage=10', not 's-maxage="10"'. Senders <em class="bcp14">SHOULD NOT</em> use the quoted-string form.
     1327      <p id="rfc.section.7.2.2.9.p.3"><b>Note:</b> This directive uses the token form of the argument syntax; e.g., 's-maxage=10', not 's-maxage="10"'. Senders <em class="bcp14">SHOULD NOT</em> use the quoted-string form.
    13281328      </p>
    13291329      <h3 id="rfc.section.7.2.3"><a href="#rfc.section.7.2.3">7.2.3</a>&nbsp;<a id="cache.control.extensions" href="#cache.control.extensions">Cache Control Extensions</a></h3>
     
    14041404         understand <a href="#header.cache-control" class="smpl">Cache-Control</a> from serving a cached response.
    14051405      </p>
    1406       <div class="note" id="rfc.section.7.4.p.8"> 
    1407          <p> <b>Note:</b> Because the meaning of "Pragma: no-cache" in responses is not specified, it does not provide a reliable replacement for "Cache-Control:
     1406      <div class="note" id="rfc.section.7.4.p.8">
     1407         <p><b>Note:</b> Because the meaning of "Pragma: no-cache" in responses is not specified, it does not provide a reliable replacement for "Cache-Control:
    14081408            no-cache" in them.
    14091409         </p>
     
    14831483      <div id="rfc.iref.50"></div>
    14841484      <h3 id="rfc.section.7.5.6"><a href="#rfc.section.7.5.6">7.5.6</a>&nbsp;<a id="warn.214" href="#warn.214">214 Transformation Applied</a></h3>
    1485       <p id="rfc.section.7.5.6.p.1"> <em class="bcp14">MUST</em> be added by a proxy if it applies any transformation to the representation, such as changing the content-coding, media-type,
     1485      <p id="rfc.section.7.5.6.p.1"><em class="bcp14">MUST</em> be added by a proxy if it applies any transformation to the representation, such as changing the content-coding, media-type,
    14861486         or modifying the representation data, unless this Warning code already appears in the response.
    14871487      </p>
     
    15181518      <h3 id="rfc.section.9.1.2"><a href="#rfc.section.9.1.2">9.1.2</a>&nbsp;<a id="cache.directive.considerations" href="#cache.directive.considerations">Considerations for New Cache Control Directives</a></h3>
    15191519      <p id="rfc.section.9.1.2.p.1">New extension directives ought to consider defining:</p>
    1520       <p id="rfc.section.9.1.2.p.2"> </p>
     1520      <p id="rfc.section.9.1.2.p.2"></p>
    15211521      <ul>
    15221522         <li>What it means for a directive to be specified multiple times,</li>
     
    15411541               <tr>
    15421542                  <td class="left">max-age</td>
    1543                   <td class="left"> <a href="#cache-request-directive.max-age" title="max-age">Section&nbsp;7.2.1.1</a>, <a href="#cache-response-directive.max-age" title="max-age">Section&nbsp;7.2.2.8</a>
     1543                  <td class="left"><a href="#cache-request-directive.max-age" title="max-age">Section&nbsp;7.2.1.1</a>, <a href="#cache-response-directive.max-age" title="max-age">Section&nbsp;7.2.2.8</a>
    15441544                  </td>
    15451545               </tr>
    15461546               <tr>
    15471547                  <td class="left">max-stale</td>
    1548                   <td class="left"> <a href="#cache-request-directive.max-stale" title="max-stale">Section&nbsp;7.2.1.2</a>
     1548                  <td class="left"><a href="#cache-request-directive.max-stale" title="max-stale">Section&nbsp;7.2.1.2</a>
    15491549                  </td>
    15501550               </tr>
    15511551               <tr>
    15521552                  <td class="left">min-fresh</td>
    1553                   <td class="left"> <a href="#cache-request-directive.min-fresh" title="min-fresh">Section&nbsp;7.2.1.3</a>
     1553                  <td class="left"><a href="#cache-request-directive.min-fresh" title="min-fresh">Section&nbsp;7.2.1.3</a>
    15541554                  </td>
    15551555               </tr>
    15561556               <tr>
    15571557                  <td class="left">must-revalidate</td>
    1558                   <td class="left"> <a href="#cache-response-directive.must-revalidate" title="must-revalidate">Section&nbsp;7.2.2.1</a>
     1558                  <td class="left"><a href="#cache-response-directive.must-revalidate" title="must-revalidate">Section&nbsp;7.2.2.1</a>
    15591559                  </td>
    15601560               </tr>
    15611561               <tr>
    15621562                  <td class="left">no-cache</td>
    1563                   <td class="left"> <a href="#cache-request-directive.no-cache" title="no-cache">Section&nbsp;7.2.1.4</a>, <a href="#cache-response-directive.no-cache" title="no-cache">Section&nbsp;7.2.2.2</a>
     1563                  <td class="left"><a href="#cache-request-directive.no-cache" title="no-cache">Section&nbsp;7.2.1.4</a>, <a href="#cache-response-directive.no-cache" title="no-cache">Section&nbsp;7.2.2.2</a>
    15641564                  </td>
    15651565               </tr>
    15661566               <tr>
    15671567                  <td class="left">no-store</td>
    1568                   <td class="left"> <a href="#cache-request-directive.no-store" title="no-store">Section&nbsp;7.2.1.5</a>, <a href="#cache-response-directive.no-store" title="no-store">Section&nbsp;7.2.2.3</a>
     1568                  <td class="left"><a href="#cache-request-directive.no-store" title="no-store">Section&nbsp;7.2.1.5</a>, <a href="#cache-response-directive.no-store" title="no-store">Section&nbsp;7.2.2.3</a>
    15691569                  </td>
    15701570               </tr>
    15711571               <tr>
    15721572                  <td class="left">no-transform</td>
    1573                   <td class="left"> <a href="#cache-request-directive.no-transform" title="no-transform">Section&nbsp;7.2.1.6</a>, <a href="#cache-response-directive.no-transform" title="no-transform">Section&nbsp;7.2.2.4</a>
     1573                  <td class="left"><a href="#cache-request-directive.no-transform" title="no-transform">Section&nbsp;7.2.1.6</a>, <a href="#cache-response-directive.no-transform" title="no-transform">Section&nbsp;7.2.2.4</a>
    15741574                  </td>
    15751575               </tr>
    15761576               <tr>
    15771577                  <td class="left">only-if-cached</td>
    1578                   <td class="left"> <a href="#cache-request-directive.only-if-cached" title="only-if-cached">Section&nbsp;7.2.1.7</a>
     1578                  <td class="left"><a href="#cache-request-directive.only-if-cached" title="only-if-cached">Section&nbsp;7.2.1.7</a>
    15791579                  </td>
    15801580               </tr>
    15811581               <tr>
    15821582                  <td class="left">private</td>
    1583                   <td class="left"> <a href="#cache-response-directive.private" title="private">Section&nbsp;7.2.2.6</a>
     1583                  <td class="left"><a href="#cache-response-directive.private" title="private">Section&nbsp;7.2.2.6</a>
    15841584                  </td>
    15851585               </tr>
    15861586               <tr>
    15871587                  <td class="left">proxy-revalidate</td>
    1588                   <td class="left"> <a href="#cache-response-directive.proxy-revalidate" title="proxy-revalidate">Section&nbsp;7.2.2.7</a>
     1588                  <td class="left"><a href="#cache-response-directive.proxy-revalidate" title="proxy-revalidate">Section&nbsp;7.2.2.7</a>
    15891589                  </td>
    15901590               </tr>
    15911591               <tr>
    15921592                  <td class="left">public</td>
    1593                   <td class="left"> <a href="#cache-response-directive.public" title="public">Section&nbsp;7.2.2.5</a>
     1593                  <td class="left"><a href="#cache-response-directive.public" title="public">Section&nbsp;7.2.2.5</a>
    15941594                  </td>
    15951595               </tr>
    15961596               <tr>
    15971597                  <td class="left">s-maxage</td>
    1598                   <td class="left"> <a href="#cache-response-directive.s-maxage" title="s-maxage">Section&nbsp;7.2.2.9</a>
     1598                  <td class="left"><a href="#cache-response-directive.s-maxage" title="s-maxage">Section&nbsp;7.2.2.9</a>
    15991599                  </td>
    16001600               </tr>
    16011601               <tr>
    16021602                  <td class="left">stale-if-error</td>
    1603                   <td class="left"> <a href="#RFC5861" id="rfc.xref.RFC5861.1"><cite title="HTTP Cache-Control Extensions for Stale Content">[RFC5861]</cite></a>, <a href="http://tools.ietf.org/html/rfc5861#section-4">Section 4</a>
     1603                  <td class="left"><a href="#RFC5861" id="rfc.xref.RFC5861.1"><cite title="HTTP Cache-Control Extensions for Stale Content">[RFC5861]</cite></a>, <a href="http://tools.ietf.org/html/rfc5861#section-4">Section 4</a>
    16041604                  </td>
    16051605               </tr>
    16061606               <tr>
    16071607                  <td class="left">stale-while-revalidate</td>
    1608                   <td class="left"> <a href="#RFC5861" id="rfc.xref.RFC5861.2"><cite title="HTTP Cache-Control Extensions for Stale Content">[RFC5861]</cite></a>, <a href="http://tools.ietf.org/html/rfc5861#section-3">Section 3</a>
     1608                  <td class="left"><a href="#RFC5861" id="rfc.xref.RFC5861.2"><cite title="HTTP Cache-Control Extensions for Stale Content">[RFC5861]</cite></a>, <a href="http://tools.ietf.org/html/rfc5861#section-3">Section 3</a>
    16091609                  </td>
    16101610               </tr>
     
    16411641                  <td class="left">110</td>
    16421642                  <td class="left">Response is Stale</td>
    1643                   <td class="left"> <a href="#warn.110" id="rfc.xref.warn.110.1" title="110 Response is Stale">Section&nbsp;7.5.1</a>
     1643                  <td class="left"><a href="#warn.110" id="rfc.xref.warn.110.1" title="110 Response is Stale">Section&nbsp;7.5.1</a>
    16441644                  </td>
    16451645               </tr>
     
    16471647                  <td class="left">111</td>
    16481648                  <td class="left">Revalidation Failed</td>
    1649                   <td class="left"> <a href="#warn.111" id="rfc.xref.warn.111.1" title="111 Revalidation Failed">Section&nbsp;7.5.2</a>
     1649                  <td class="left"><a href="#warn.111" id="rfc.xref.warn.111.1" title="111 Revalidation Failed">Section&nbsp;7.5.2</a>
    16501650                  </td>
    16511651               </tr>
     
    16531653                  <td class="left">112</td>
    16541654                  <td class="left">Disconnected Operation</td>
    1655                   <td class="left"> <a href="#warn.112" id="rfc.xref.warn.112.1" title="112 Disconnected Operation">Section&nbsp;7.5.3</a>
     1655                  <td class="left"><a href="#warn.112" id="rfc.xref.warn.112.1" title="112 Disconnected Operation">Section&nbsp;7.5.3</a>
    16561656                  </td>
    16571657               </tr>
     
    16591659                  <td class="left">113</td>
    16601660                  <td class="left">Heuristic Expiration</td>
    1661                   <td class="left"> <a href="#warn.113" id="rfc.xref.warn.113.1" title="113 Heuristic Expiration">Section&nbsp;7.5.4</a>
     1661                  <td class="left"><a href="#warn.113" id="rfc.xref.warn.113.1" title="113 Heuristic Expiration">Section&nbsp;7.5.4</a>
    16621662                  </td>
    16631663               </tr>
     
    16651665                  <td class="left">199</td>
    16661666                  <td class="left">Miscellaneous Warning</td>
    1667                   <td class="left"> <a href="#warn.199" id="rfc.xref.warn.199.1" title="199 Miscellaneous Warning">Section&nbsp;7.5.5</a>
     1667                  <td class="left"><a href="#warn.199" id="rfc.xref.warn.199.1" title="199 Miscellaneous Warning">Section&nbsp;7.5.5</a>
    16681668                  </td>
    16691669               </tr>
     
    16711671                  <td class="left">214</td>
    16721672                  <td class="left">Transformation Applied</td>
    1673                   <td class="left"> <a href="#warn.214" id="rfc.xref.warn.214.1" title="214 Transformation Applied">Section&nbsp;7.5.6</a>
     1673                  <td class="left"><a href="#warn.214" id="rfc.xref.warn.214.1" title="214 Transformation Applied">Section&nbsp;7.5.6</a>
    16741674                  </td>
    16751675               </tr>
     
    16771677                  <td class="left">299</td>
    16781678                  <td class="left">Miscellaneous Persistent Warning</td>
    1679                   <td class="left"> <a href="#warn.299" id="rfc.xref.warn.299.1" title="299 Miscellaneous Persistent Warning">Section&nbsp;7.5.7</a>
     1679                  <td class="left"><a href="#warn.299" id="rfc.xref.warn.299.1" title="299 Miscellaneous Persistent Warning">Section&nbsp;7.5.7</a>
    16801680                  </td>
    16811681               </tr>
     
    17051705                  <td class="left">http</td>
    17061706                  <td class="left">standard</td>
    1707                   <td class="left"> <a href="#header.age" id="rfc.xref.header.age.3" title="Age">Section&nbsp;7.1</a>
     1707                  <td class="left"><a href="#header.age" id="rfc.xref.header.age.3" title="Age">Section&nbsp;7.1</a>
    17081708                  </td>
    17091709               </tr>
     
    17121712                  <td class="left">http</td>
    17131713                  <td class="left">standard</td>
    1714                   <td class="left"> <a href="#header.cache-control" id="rfc.xref.header.cache-control.2" title="Cache-Control">Section&nbsp;7.2</a>
     1714                  <td class="left"><a href="#header.cache-control" id="rfc.xref.header.cache-control.2" title="Cache-Control">Section&nbsp;7.2</a>
    17151715                  </td>
    17161716               </tr>
     
    17191719                  <td class="left">http</td>
    17201720                  <td class="left">standard</td>
    1721                   <td class="left"> <a href="#header.expires" id="rfc.xref.header.expires.4" title="Expires">Section&nbsp;7.3</a>
     1721                  <td class="left"><a href="#header.expires" id="rfc.xref.header.expires.4" title="Expires">Section&nbsp;7.3</a>
    17221722                  </td>
    17231723               </tr>
     
    17261726                  <td class="left">http</td>
    17271727                  <td class="left">standard</td>
    1728                   <td class="left"> <a href="#header.pragma" id="rfc.xref.header.pragma.2" title="Pragma">Section&nbsp;7.4</a>
     1728                  <td class="left"><a href="#header.pragma" id="rfc.xref.header.pragma.2" title="Pragma">Section&nbsp;7.4</a>
    17291729                  </td>
    17301730               </tr>
     
    17331733                  <td class="left">http</td>
    17341734                  <td class="left">standard</td>
    1735                   <td class="left"> <a href="#header.warning" id="rfc.xref.header.warning.5" title="Warning">Section&nbsp;7.5</a>
     1735                  <td class="left"><a href="#header.warning" id="rfc.xref.header.warning.5" title="Warning">Section&nbsp;7.5</a>
    17361736                  </td>
    17371737               </tr>
     
    17731773         <tr>
    17741774            <td class="reference"><b id="Part1">[Part1]</b></td>
    1775             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-latest (work in progress), June&nbsp;2013.
     1775            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-latest (work in progress), July&nbsp;2013.
    17761776            </td>
    17771777         </tr>
    17781778         <tr>
    17791779            <td class="reference"><b id="Part2">[Part2]</b></td>
    1780             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p2-semantics-latest (work in progress), June&nbsp;2013.
     1780            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p2-semantics-latest (work in progress), July&nbsp;2013.
    17811781            </td>
    17821782         </tr>
    17831783         <tr>
    17841784            <td class="reference"><b id="Part4">[Part4]</b></td>
    1785             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-latest (work in progress), June&nbsp;2013.
     1785            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-latest (work in progress), July&nbsp;2013.
    17861786            </td>
    17871787         </tr>
    17881788         <tr>
    17891789            <td class="reference"><b id="Part5">[Part5]</b></td>
    1790             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">Hypertext Transfer Protocol (HTTP/1.1): Range Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-latest (work in progress), June&nbsp;2013.
     1790            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">Hypertext Transfer Protocol (HTTP/1.1): Range Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-latest (work in progress), July&nbsp;2013.
    17911791            </td>
    17921792         </tr>
    17931793         <tr>
    17941794            <td class="reference"><b id="Part7">[Part7]</b></td>
    1795             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-latest">Hypertext Transfer Protocol (HTTP/1.1): Authentication</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p7-auth-latest (work in progress), June&nbsp;2013.
     1795            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-latest">Hypertext Transfer Protocol (HTTP/1.1): Authentication</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p7-auth-latest (work in progress), July&nbsp;2013.
    17961796            </td>
    17971797         </tr>
     
    19651965      <p id="rfc.section.D.1.p.1">Closed issues: </p>
    19661966      <ul>
    1967          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/307">http://tools.ietf.org/wg/httpbis/trac/ticket/307</a>&gt;: "untangle Cache-Control ABNF"
    1968          </li>
    1969          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/353">http://tools.ietf.org/wg/httpbis/trac/ticket/353</a>&gt;: "Multiple values in Cache-Control header fields"
    1970          </li>
    1971          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/355">http://tools.ietf.org/wg/httpbis/trac/ticket/355</a>&gt;: "Case sensitivity of header fields in CC values"
    1972          </li>
    1973          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/356">http://tools.ietf.org/wg/httpbis/trac/ticket/356</a>&gt;: "Spurious 'MAYs'"
    1974          </li>
    1975          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/360">http://tools.ietf.org/wg/httpbis/trac/ticket/360</a>&gt;: "enhance considerations for new cache control directives"
    1976          </li>
    1977          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/361">http://tools.ietf.org/wg/httpbis/trac/ticket/361</a>&gt;: "ABNF requirements for recipients"
    1978          </li>
    1979          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/368">http://tools.ietf.org/wg/httpbis/trac/ticket/368</a>&gt;: "note introduction of new IANA registries as normative changes"
    1980          </li>
    1981          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/373">http://tools.ietf.org/wg/httpbis/trac/ticket/373</a>&gt;: "broken prose in description of 'Vary'"
     1967         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/307">http://tools.ietf.org/wg/httpbis/trac/ticket/307</a>&gt;: "untangle Cache-Control ABNF"
     1968         </li>
     1969         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/353">http://tools.ietf.org/wg/httpbis/trac/ticket/353</a>&gt;: "Multiple values in Cache-Control header fields"
     1970         </li>
     1971         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/355">http://tools.ietf.org/wg/httpbis/trac/ticket/355</a>&gt;: "Case sensitivity of header fields in CC values"
     1972         </li>
     1973         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/356">http://tools.ietf.org/wg/httpbis/trac/ticket/356</a>&gt;: "Spurious 'MAYs'"
     1974         </li>
     1975         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/360">http://tools.ietf.org/wg/httpbis/trac/ticket/360</a>&gt;: "enhance considerations for new cache control directives"
     1976         </li>
     1977         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/361">http://tools.ietf.org/wg/httpbis/trac/ticket/361</a>&gt;: "ABNF requirements for recipients"
     1978         </li>
     1979         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/368">http://tools.ietf.org/wg/httpbis/trac/ticket/368</a>&gt;: "note introduction of new IANA registries as normative changes"
     1980         </li>
     1981         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/373">http://tools.ietf.org/wg/httpbis/trac/ticket/373</a>&gt;: "broken prose in description of 'Vary'"
    19821982         </li>
    19831983      </ul>
     
    19851985      <p id="rfc.section.D.2.p.1">Closed issues: </p>
    19861986      <ul>
    1987          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/375">http://tools.ietf.org/wg/httpbis/trac/ticket/375</a>&gt;: "'Most Conservative'"
     1987         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/375">http://tools.ietf.org/wg/httpbis/trac/ticket/375</a>&gt;: "'Most Conservative'"
    19881988         </li>
    19891989      </ul>
     
    19971997      <p id="rfc.section.D.3.p.1">Closed issues: </p>
    19981998      <ul>
    1999          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/223">http://tools.ietf.org/wg/httpbis/trac/ticket/223</a>&gt;: "Allowing heuristic caching for new status codes"
    2000          </li>
    2001          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/406">http://tools.ietf.org/wg/httpbis/trac/ticket/406</a>&gt;: "304 without validator"
    2002          </li>
    2003          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/418">http://tools.ietf.org/wg/httpbis/trac/ticket/418</a>&gt;: "No-Transform"
    2004          </li>
    2005          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/430">http://tools.ietf.org/wg/httpbis/trac/ticket/430</a>&gt;: "Revert prior change to the meaning of the public cache response directive.
     1999         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/223">http://tools.ietf.org/wg/httpbis/trac/ticket/223</a>&gt;: "Allowing heuristic caching for new status codes"
     2000         </li>
     2001         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/406">http://tools.ietf.org/wg/httpbis/trac/ticket/406</a>&gt;: "304 without validator"
     2002         </li>
     2003         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/418">http://tools.ietf.org/wg/httpbis/trac/ticket/418</a>&gt;: "No-Transform"
     2004         </li>
     2005         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/430">http://tools.ietf.org/wg/httpbis/trac/ticket/430</a>&gt;: "Revert prior change to the meaning of the public cache response directive.
    20062006         </li>
    20072007      </ul>
     
    20092009      <p id="rfc.section.D.4.p.1">Closed issues: </p>
    20102010      <ul>
    2011          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/436">http://tools.ietf.org/wg/httpbis/trac/ticket/436</a>&gt;: "explain list expansion in ABNF appendices"
    2012          </li>
    2013          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/453">http://tools.ietf.org/wg/httpbis/trac/ticket/453</a>&gt;: "Returning the freshest response"
    2014          </li>
    2015          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/464">http://tools.ietf.org/wg/httpbis/trac/ticket/464</a>&gt;: "placement of extension point considerations"
    2016          </li>
    2017          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/469">http://tools.ietf.org/wg/httpbis/trac/ticket/469</a>&gt;: "Editorial notes for p6"
    2018          </li>
    2019          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/471">http://tools.ietf.org/wg/httpbis/trac/ticket/471</a>&gt;: "Vary and future requests"
     2011         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/436">http://tools.ietf.org/wg/httpbis/trac/ticket/436</a>&gt;: "explain list expansion in ABNF appendices"
     2012         </li>
     2013         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/453">http://tools.ietf.org/wg/httpbis/trac/ticket/453</a>&gt;: "Returning the freshest response"
     2014         </li>
     2015         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/464">http://tools.ietf.org/wg/httpbis/trac/ticket/464</a>&gt;: "placement of extension point considerations"
     2016         </li>
     2017         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/469">http://tools.ietf.org/wg/httpbis/trac/ticket/469</a>&gt;: "Editorial notes for p6"
     2018         </li>
     2019         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/471">http://tools.ietf.org/wg/httpbis/trac/ticket/471</a>&gt;: "Vary and future requests"
    20202020         </li>
    20212021      </ul>
  • draft-ietf-httpbis/latest/p6-cache.xml

    r2283 r2301  
    1313  <!ENTITY SHOULD-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHOULD NOT</bcp14>">
    1414  <!ENTITY ID-VERSION "latest">
    15   <!ENTITY ID-MONTH "June">
     15  <!ENTITY ID-MONTH "July">
    1616  <!ENTITY ID-YEAR "2013">
    1717  <!ENTITY mdash "&#8212;">
  • draft-ietf-httpbis/latest/p7-auth.html

    r2289 r2301  
    440440  }
    441441  @top-right {
    442        content: "June 2013";
     442       content: "July 2013";
    443443  }
    444444  @top-center {
     
    449449  }
    450450  @bottom-center {
    451        content: "Expires December 11, 2013";
     451       content: "Expires January 2, 2014";
    452452  }
    453453  @bottom-right {
     
    484484      <link rel="Appendix" title="D Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.D">
    485485      <link href="p6-cache.html" rel="prev">
    486       <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.597, 2013/05/27 06:39:42, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
     486      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.598, 2013/06/23 14:11:10, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
    487487      <link rel="schema.dct" href="http://purl.org/dc/terms/">
    488488      <meta name="dct.creator" content="Fielding, R.">
    489489      <meta name="dct.creator" content="Reschke, J. F.">
    490490      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p7-auth-latest">
    491       <meta name="dct.issued" scheme="ISO8601" content="2013-06-09">
     491      <meta name="dct.issued" scheme="ISO8601" content="2013-07-01">
    492492      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    493493      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. This document defines the HTTP Authentication framework.">
     
    517517            <tr>
    518518               <td class="left">Intended status: Standards Track</td>
    519                <td class="right">June 9, 2013</td>
     519               <td class="right">July 1, 2013</td>
    520520            </tr>
    521521            <tr>
    522                <td class="left">Expires: December 11, 2013</td>
     522               <td class="left">Expires: January 2, 2014</td>
    523523               <td class="right"></td>
    524524            </tr>
     
    546546         in progress”.
    547547      </p>
    548       <p>This Internet-Draft will expire on December 11, 2013.</p>
     548      <p>This Internet-Draft will expire on January 2, 2014.</p>
    549549      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    550550      <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    659659      </p>
    660660      <div id="rfc.figure.u.2"></div><pre class="inline"><span id="rfc.iref.g.4"></span>  <a href="#challenge.and.response" class="smpl">challenge</a>   = <a href="#challenge.and.response" class="smpl">auth-scheme</a> [ 1*<a href="#imported.abnf" class="smpl">SP</a> ( <a href="#challenge.and.response" class="smpl">token68</a> / #<a href="#challenge.and.response" class="smpl">auth-param</a> ) ]
    661 </pre><div class="note" id="rfc.section.2.1.p.8"> 
    662          <p> <b>Note:</b> User agents will need to take special care in parsing the <a href="#header.www-authenticate" class="smpl">WWW-Authenticate</a> and <a href="#header.proxy-authenticate" class="smpl">Proxy-Authenticate</a> header field values because they can contain more than one challenge, or if more than one of each is provided, since the contents
     661</pre><div class="note" id="rfc.section.2.1.p.8">
     662         <p><b>Note:</b> User agents will need to take special care in parsing the <a href="#header.www-authenticate" class="smpl">WWW-Authenticate</a> and <a href="#header.proxy-authenticate" class="smpl">Proxy-Authenticate</a> header field values because they can contain more than one challenge, or if more than one of each is provided, since the contents
    663663            of a challenge can itself contain a comma-separated list of authentication parameters.
    664664         </p>
    665665      </div>
    666       <div class="note" id="rfc.section.2.1.p.9"> 
    667          <p> <b>Note:</b> Many clients fail to parse challenges containing unknown schemes. A workaround for this problem is to list well-supported
     666      <div class="note" id="rfc.section.2.1.p.9">
     667         <p><b>Note:</b> Many clients fail to parse challenges containing unknown schemes. A workaround for this problem is to list well-supported
    668668            schemes (such as "basic") first.
    669669         </p>
     
    779779         "type" and "title", and another one for the "Basic" scheme with a realm value of "simple".
    780780      </p>
    781       <div class="note" id="rfc.section.4.4.p.6"> 
    782          <p> <b>Note:</b> The challenge grammar production uses the list syntax as well. Therefore, a sequence of comma, whitespace, and comma can be
     781      <div class="note" id="rfc.section.4.4.p.6">
     782         <p><b>Note:</b> The challenge grammar production uses the list syntax as well. Therefore, a sequence of comma, whitespace, and comma can be
    783783            considered both as applying to the preceding challenge, or to be an empty entry in the list of challenges. In practice, this
    784784            ambiguity does not affect the semantics of the header field value and thus is harmless.
     
    804804         work:
    805805      </p>
    806       <p id="rfc.section.5.1.2.p.2"> </p>
     806      <p id="rfc.section.5.1.2.p.2"></p>
    807807      <ul>
    808808         <li>
     
    828828               can use a generic parser that applies to all authentication schemes.
    829829            </p>
    830             <p> <b>Note:</b> The fact that the value syntax for the "realm" parameter is restricted to quoted-string was a bad design choice not to be
     830            <p><b>Note:</b> The fact that the value syntax for the "realm" parameter is restricted to quoted-string was a bad design choice not to be
    831831               repeated for new parameters.
    832832            </p>
     
    869869                  <td class="left">401</td>
    870870                  <td class="left">Unauthorized</td>
    871                   <td class="left"> <a href="#status.401" id="rfc.xref.status.401.1" title="401 Unauthorized">Section&nbsp;3.1</a>
     871                  <td class="left"><a href="#status.401" id="rfc.xref.status.401.1" title="401 Unauthorized">Section&nbsp;3.1</a>
    872872                  </td>
    873873               </tr>
     
    875875                  <td class="left">407</td>
    876876                  <td class="left">Proxy Authentication Required</td>
    877                   <td class="left"> <a href="#status.407" id="rfc.xref.status.407.1" title="407 Proxy Authentication Required">Section&nbsp;3.2</a>
     877                  <td class="left"><a href="#status.407" id="rfc.xref.status.407.1" title="407 Proxy Authentication Required">Section&nbsp;3.2</a>
    878878                  </td>
    879879               </tr>
     
    903903                  <td class="left">http</td>
    904904                  <td class="left">standard</td>
    905                   <td class="left"> <a href="#header.authorization" id="rfc.xref.header.authorization.3" title="Authorization">Section&nbsp;4.1</a>
     905                  <td class="left"><a href="#header.authorization" id="rfc.xref.header.authorization.3" title="Authorization">Section&nbsp;4.1</a>
    906906                  </td>
    907907               </tr>
     
    910910                  <td class="left">http</td>
    911911                  <td class="left">standard</td>
    912                   <td class="left"> <a href="#header.proxy-authenticate" id="rfc.xref.header.proxy-authenticate.2" title="Proxy-Authenticate">Section&nbsp;4.2</a>
     912                  <td class="left"><a href="#header.proxy-authenticate" id="rfc.xref.header.proxy-authenticate.2" title="Proxy-Authenticate">Section&nbsp;4.2</a>
    913913                  </td>
    914914               </tr>
     
    917917                  <td class="left">http</td>
    918918                  <td class="left">standard</td>
    919                   <td class="left"> <a href="#header.proxy-authorization" id="rfc.xref.header.proxy-authorization.2" title="Proxy-Authorization">Section&nbsp;4.3</a>
     919                  <td class="left"><a href="#header.proxy-authorization" id="rfc.xref.header.proxy-authorization.2" title="Proxy-Authorization">Section&nbsp;4.3</a>
    920920                  </td>
    921921               </tr>
     
    924924                  <td class="left">http</td>
    925925                  <td class="left">standard</td>
    926                   <td class="left"> <a href="#header.www-authenticate" id="rfc.xref.header.www-authenticate.3" title="WWW-Authenticate">Section&nbsp;4.4</a>
     926                  <td class="left"><a href="#header.www-authenticate" id="rfc.xref.header.www-authenticate.3" title="WWW-Authenticate">Section&nbsp;4.4</a>
    927927                  </td>
    928928               </tr>
     
    978978         <tr>
    979979            <td class="reference"><b id="Part1">[Part1]</b></td>
    980             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-latest (work in progress), June&nbsp;2013.
     980            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-latest (work in progress), July&nbsp;2013.
    981981            </td>
    982982         </tr>
    983983         <tr>
    984984            <td class="reference"><b id="Part2">[Part2]</b></td>
    985             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p2-semantics-latest (work in progress), June&nbsp;2013.
     985            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p2-semantics-latest (work in progress), July&nbsp;2013.
    986986            </td>
    987987         </tr>
    988988         <tr>
    989989            <td class="reference"><b id="Part6">[Part6]</b></td>
    990             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:mnot@mnot.net" title="Akamai">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">Hypertext Transfer Protocol (HTTP/1.1): Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-latest (work in progress), June&nbsp;2013.
     990            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:mnot@mnot.net" title="Akamai">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">Hypertext Transfer Protocol (HTTP/1.1): Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-latest (work in progress), July&nbsp;2013.
    991991            </td>
    992992         </tr>
     
    11021102      <p id="rfc.section.D.1.p.1">Closed issues: </p>
    11031103      <ul>
    1104          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/348">http://tools.ietf.org/wg/httpbis/trac/ticket/348</a>&gt;: "Realms and scope"
    1105          </li>
    1106          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/349">http://tools.ietf.org/wg/httpbis/trac/ticket/349</a>&gt;: "Strength"
    1107          </li>
    1108          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/357">http://tools.ietf.org/wg/httpbis/trac/ticket/357</a>&gt;: "Authentication exchanges"
    1109          </li>
    1110          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/361">http://tools.ietf.org/wg/httpbis/trac/ticket/361</a>&gt;: "ABNF requirements for recipients"
    1111          </li>
    1112          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/368">http://tools.ietf.org/wg/httpbis/trac/ticket/368</a>&gt;: "note introduction of new IANA registries as normative changes"
     1104         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/348">http://tools.ietf.org/wg/httpbis/trac/ticket/348</a>&gt;: "Realms and scope"
     1105         </li>
     1106         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/349">http://tools.ietf.org/wg/httpbis/trac/ticket/349</a>&gt;: "Strength"
     1107         </li>
     1108         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/357">http://tools.ietf.org/wg/httpbis/trac/ticket/357</a>&gt;: "Authentication exchanges"
     1109         </li>
     1110         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/361">http://tools.ietf.org/wg/httpbis/trac/ticket/361</a>&gt;: "ABNF requirements for recipients"
     1111         </li>
     1112         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/368">http://tools.ietf.org/wg/httpbis/trac/ticket/368</a>&gt;: "note introduction of new IANA registries as normative changes"
    11131113         </li>
    11141114      </ul>
     
    11161116      <p id="rfc.section.D.2.p.1">Closed issues: </p>
    11171117      <ul>
    1118          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/376">http://tools.ietf.org/wg/httpbis/trac/ticket/376</a>&gt;: "rename b64token for clarity"
     1118         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/376">http://tools.ietf.org/wg/httpbis/trac/ticket/376</a>&gt;: "rename b64token for clarity"
    11191119         </li>
    11201120      </ul>
     
    11261126      <p id="rfc.section.D.3.p.1">Closed issues: </p>
    11271127      <ul>
    1128          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/403">http://tools.ietf.org/wg/httpbis/trac/ticket/403</a>&gt;: "Authentication and caching - max-age"
     1128         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/403">http://tools.ietf.org/wg/httpbis/trac/ticket/403</a>&gt;: "Authentication and caching - max-age"
    11291129         </li>
    11301130      </ul>
     
    11321132      <p id="rfc.section.D.4.p.1">Closed issues: </p>
    11331133      <ul>
    1134          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/436">http://tools.ietf.org/wg/httpbis/trac/ticket/436</a>&gt;: "explain list expansion in ABNF appendices"
    1135          </li>
    1136          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/439">http://tools.ietf.org/wg/httpbis/trac/ticket/439</a>&gt;: "terminology: mechanism vs framework vs scheme"
    1137          </li>
    1138          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/463">http://tools.ietf.org/wg/httpbis/trac/ticket/463</a>&gt;: "Editorial suggestions"
    1139          </li>
    1140          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/464">http://tools.ietf.org/wg/httpbis/trac/ticket/464</a>&gt;: "placement of extension point considerations"
     1134         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/436">http://tools.ietf.org/wg/httpbis/trac/ticket/436</a>&gt;: "explain list expansion in ABNF appendices"
     1135         </li>
     1136         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/439">http://tools.ietf.org/wg/httpbis/trac/ticket/439</a>&gt;: "terminology: mechanism vs framework vs scheme"
     1137         </li>
     1138         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/463">http://tools.ietf.org/wg/httpbis/trac/ticket/463</a>&gt;: "Editorial suggestions"
     1139         </li>
     1140         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/464">http://tools.ietf.org/wg/httpbis/trac/ticket/464</a>&gt;: "placement of extension point considerations"
    11411141         </li>
    11421142      </ul>
  • draft-ietf-httpbis/latest/p7-auth.xml

    r2289 r2301  
    1313  <!ENTITY SHOULD-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHOULD NOT</bcp14>">
    1414  <!ENTITY ID-VERSION "latest">
    15   <!ENTITY ID-MONTH "June">
     15  <!ENTITY ID-MONTH "July">
    1616  <!ENTITY ID-YEAR "2013">
    1717  <!ENTITY mdash "&#8212;">
  • rfc2629xslt/rfc2629.xslt

    r2280 r2301  
    600600<xsl:template match="text()[not(ancestor::artwork)]">
    601601  <xsl:variable name="ws" select="'&#9;&#10;&#13;&#32;'"/>
    602   <xsl:variable name="starts-with-ws" select="translate(substring(.,1,1),$ws,'')"/>
    603   <xsl:variable name="ends-with-ws" select="translate(substring(.,string-length(.),1),$ws,'')"/>
     602  <xsl:variable name="starts-with-ws" select="'' = translate(substring(.,1,1),$ws,'')"/>
     603  <xsl:variable name="ends-with-ws" select="'' = translate(substring(.,string-length(.),1),$ws,'')"/>
     604  <xsl:variable name="normalized" select="normalize-space(.)"/>
    604605  <!--<xsl:message> Orig: "<xsl:value-of select="."/>"</xsl:message>
    605606  <xsl:message>Start: "<xsl:value-of select="$starts-with-ws"/>"</xsl:message>
    606607  <xsl:message>  End: "<xsl:value-of select="$ends-with-ws"/>"</xsl:message> -->
    607   <xsl:if test="$starts-with-ws='' and preceding-sibling::node() | parent::ed:ins | parent::ed:del">
     608  <xsl:if test="$starts-with-ws and (preceding-sibling::node() | parent::ed:ins | parent::ed:del)">
    608609    <xsl:text> </xsl:text>
    609610  </xsl:if>
    610   <xsl:value-of select="normalize-space(.)"/>
    611   <xsl:if test="$ends-with-ws='' and following-sibling::node() | parent::ed:ins | parent::ed:del">
     611  <xsl:value-of select="$normalized"/>
     612  <xsl:if test="$ends-with-ws and $normalized!='' and (following-sibling::node() | parent::ed:ins | parent::ed:del)">
    612613    <xsl:text> </xsl:text>
    613614  </xsl:if>
     
    67116712    <xsl:text>http://greenbytes.de/tech/webdav/rfc2629.xslt, </xsl:text>
    67126713    <!-- when RCS keyword substitution in place, add version info -->
    6713     <xsl:if test="contains('$Revision: 1.597 $',':')">
    6714       <xsl:value-of select="concat('Revision ',normalize-space(translate(substring-after('$Revision: 1.597 $', 'Revision: '),'$','')),', ')" />
     6714    <xsl:if test="contains('$Revision: 1.598 $',':')">
     6715      <xsl:value-of select="concat('Revision ',normalize-space(translate(substring-after('$Revision: 1.598 $', 'Revision: '),'$','')),', ')" />
    67156716    </xsl:if>
    6716     <xsl:if test="contains('$Date: 2013/05/27 06:39:42 $',':')">
    6717       <xsl:value-of select="concat(normalize-space(translate(substring-after('$Date: 2013/05/27 06:39:42 $', 'Date: '),'$','')),', ')" />
     6717    <xsl:if test="contains('$Date: 2013/06/23 14:11:10 $',':')">
     6718      <xsl:value-of select="concat(normalize-space(translate(substring-after('$Date: 2013/06/23 14:11:10 $', 'Date: '),'$','')),', ')" />
    67186719    </xsl:if>
    67196720    <xsl:value-of select="concat('XSLT vendor: ',system-property('xsl:vendor'),' ',system-property('xsl:vendor-url'))" />
  • rfc2629xslt/rfc2629toXHTML.xslt

    r2280 r2301  
    468468<xsl:template match="text()[not(ancestor::artwork)]">
    469469  <xsl:variable name="ws" select="'&#x9;&#xA;&#xD; '"/>
    470   <xsl:variable name="starts-with-ws" select="translate(substring(.,1,1),$ws,'')"/>
    471   <xsl:variable name="ends-with-ws" select="translate(substring(.,string-length(.),1),$ws,'')"/>
     470  <xsl:variable name="starts-with-ws" select="'' = translate(substring(.,1,1),$ws,'')"/>
     471  <xsl:variable name="ends-with-ws" select="'' = translate(substring(.,string-length(.),1),$ws,'')"/>
     472  <xsl:variable name="normalized" select="normalize-space(.)"/>
    472473  <!--<xsl:message> Orig: "<xsl:value-of select="."/>"</xsl:message>
    473474  <xsl:message>Start: "<xsl:value-of select="$starts-with-ws"/>"</xsl:message>
    474475  <xsl:message>  End: "<xsl:value-of select="$ends-with-ws"/>"</xsl:message> -->
    475   <xsl:if test="$starts-with-ws='' and preceding-sibling::node() | parent::ed:ins | parent::ed:del">
     476  <xsl:if test="$starts-with-ws and (preceding-sibling::node() | parent::ed:ins | parent::ed:del)">
    476477    <xsl:text> </xsl:text>
    477478  </xsl:if>
    478   <xsl:value-of select="normalize-space(.)"/>
    479   <xsl:if test="$ends-with-ws='' and following-sibling::node() | parent::ed:ins | parent::ed:del">
     479  <xsl:value-of select="$normalized"/>
     480  <xsl:if test="$ends-with-ws and $normalized!='' and (following-sibling::node() | parent::ed:ins | parent::ed:del)">
    480481    <xsl:text> </xsl:text>
    481482  </xsl:if>
     
    65686569    <xsl:text>http://greenbytes.de/tech/webdav/rfc2629.xslt, </xsl:text>
    65696570    <!-- when RCS keyword substitution in place, add version info -->
    6570     <xsl:if test="contains('$Revision: 1.597 $',':')">
    6571       <xsl:value-of select="concat('Revision ',normalize-space(translate(substring-after('$Revision: 1.597 $', 'Revision: '),'$','')),', ')"/>
     6571    <xsl:if test="contains('$Revision: 1.598 $',':')">
     6572      <xsl:value-of select="concat('Revision ',normalize-space(translate(substring-after('$Revision: 1.598 $', 'Revision: '),'$','')),', ')"/>
    65726573    </xsl:if>
    6573     <xsl:if test="contains('$Date: 2013/05/27 06:39:42 $',':')">
    6574       <xsl:value-of select="concat(normalize-space(translate(substring-after('$Date: 2013/05/27 06:39:42 $', 'Date: '),'$','')),', ')"/>
     6574    <xsl:if test="contains('$Date: 2013/06/23 14:11:10 $',':')">
     6575      <xsl:value-of select="concat(normalize-space(translate(substring-after('$Date: 2013/06/23 14:11:10 $', 'Date: '),'$','')),', ')"/>
    65756576    </xsl:if>
    65766577    <xsl:value-of select="concat('XSLT vendor: ',system-property('xsl:vendor'),' ',system-property('xsl:vendor-url'))"/>
  • rfc2629xslt/rfc2629xslt.html

    r2280 r2301  
    372372    }
    373373}
    374 </style><link rel="Contents" href="#rfc.toc"><link rel="Author" href="#rfc.authors"><link rel="Index" href="#rfc.index"><link rel="Chapter" title="1 Introduction" href="#rfc.section.1"><link rel="Chapter" title="2 Supported RFC2629 elements" href="#rfc.section.2"><link rel="Chapter" title="3 Processing Instructions" href="#rfc.section.3"><link rel="Chapter" title="4 Anchors" href="#rfc.section.4"><link rel="Chapter" title="5 Supported XSLT engines" href="#rfc.section.5"><link rel="Chapter" title="6 Transforming to HTML" href="#rfc.section.6"><link rel="Chapter" title="7 Transforming to XHTML" href="#rfc.section.7"><link rel="Chapter" title="8 Transforming to CHM (Microsoft Compiled Help)" href="#rfc.section.8"><link rel="Chapter" title="9 Transforming to PDF" href="#rfc.section.9"><link rel="Chapter" title="10 Transforming to ePub" href="#rfc.section.10"><link rel="Chapter" title="11 Generic Extensions" href="#rfc.section.11"><link rel="Chapter" title="12 Utilities" href="#rfc.section.12"><link rel="Chapter" href="#rfc.section.13" title="13 Informative References"><link rel="Appendix" title="A RELAX NG Compact Schema" href="#rfc.section.A"><link rel="Appendix" title="B Implementation Notes" href="#rfc.section.B"><link rel="Appendix" title="C Examples" href="#rfc.section.C"><link rel="Appendix" title="D Producing the IETF 'Boilerplate'" href="#rfc.section.D"><link rel="Appendix" title="E License" href="#rfc.section.E"><link rel="Appendix" title="F Change Logs" href="#rfc.section.F"><meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.597, 2013/05/27 06:39:42, XSLT vendor: SAXON 6.5.5 from Michael Kay http://saxon.sf.net/"><meta name="keywords" content="RFC2629, xml2rfc, XSLT, hCard, XSL-FO, PDF, GRDDL, epub, Dublin Core"><link rel="schema.dct" href="http://purl.org/dc/terms/"><meta name="dct.creator" content="Reschke, J. F."></head><body><table class="header"><tbody><tr><td class="left">RFC2629 through XSLT</td><td class="right">J. Reschke</td></tr><tr><td class="left"></td><td class="right">greenbytes</td></tr><tr><td class="left"></td><td class="right">November 2012</td></tr></tbody></table><p class="title">Transforming RFC2629-formatted XML through XSLT</p><hr class="noprint"><h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1><ul class="toc"><li><a href="#rfc.section.1">1.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.1">Introduction</a></li><li><a href="#rfc.section.2">2.</a>&nbsp;&nbsp;&nbsp;<a href="#supported.elements">Supported RFC2629 elements</a><ul><li><a href="#rfc.section.2.1">2.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.2.1">Extension elements</a></li></ul></li><li><a href="#rfc.section.3">3.</a>&nbsp;&nbsp;&nbsp;<a href="#processing.instructions">Processing Instructions</a><ul><li><a href="#rfc.section.3.1">3.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.3.1">Supported xml2rfc-compatible PIs</a></li><li><a href="#rfc.section.3.2">3.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.3.2">Unsupported xml2rfc-compatible PIs</a></li><li><a href="#rfc.section.3.3">3.3</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.3.3">Extension PIs</a></li></ul></li><li><a href="#rfc.section.4">4.</a>&nbsp;&nbsp;&nbsp;<a href="#anchors">Anchors</a></li><li><a href="#rfc.section.5">5.</a>&nbsp;&nbsp;&nbsp;<a href="#xslt.engines">Supported XSLT engines</a><ul><li><a href="#rfc.section.5.1">5.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.5.1">Standalone Engines</a></li><li><a href="#rfc.section.5.2">5.2</a>&nbsp;&nbsp;&nbsp;<a href="#xslt.engines.browser">In-Browser Engines</a></li></ul></li><li><a href="#rfc.section.6">6.</a>&nbsp;&nbsp;&nbsp;<a href="#output.html">Transforming to HTML</a><ul><li><a href="#rfc.section.6.1">6.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.6.1">HTML compliance</a></li><li><a href="#rfc.section.6.2">6.2</a>&nbsp;&nbsp;&nbsp;<a href="#html.link">Standard HTML LINK elements</a></li><li><a href="#rfc.section.6.3">6.3</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.6.3">Standard HTML metadata</a></li><li><a href="#rfc.section.6.4">6.4</a>&nbsp;&nbsp;&nbsp;<a href="#rfc2731.properties">Dublin Core (RFC2731) metadata</a></li><li><a href="#rfc.section.6.5">6.5</a>&nbsp;&nbsp;&nbsp;<a href="#hcard">Experimental hCard support</a></li></ul></li><li><a href="#rfc.section.7">7.</a>&nbsp;&nbsp;&nbsp;<a href="#output.xhtml">Transforming to XHTML</a></li><li><a href="#rfc.section.8">8.</a>&nbsp;&nbsp;&nbsp;<a href="#output.chm">Transforming to CHM (Microsoft Compiled Help)</a></li><li><a href="#rfc.section.9">9.</a>&nbsp;&nbsp;&nbsp;<a href="#output.pdf">Transforming to PDF</a><ul><li><a href="#rfc.section.9.1">9.1</a>&nbsp;&nbsp;&nbsp;<a href="#output.pdf.fop">Via XSL-FO</a><ul><li><a href="#rfc.section.9.1.1">9.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.9.1.1">Extension feature matrix</a></li><li><a href="#rfc.section.9.1.2">9.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.9.1.2">Example: producing output for Apache FOP</a></li></ul></li><li><a href="#rfc.section.9.2">9.2</a>&nbsp;&nbsp;&nbsp;<a href="#output.pdf.html">Via X(HTML)</a></li></ul></li><li><a href="#rfc.section.10">10.</a>&nbsp;&nbsp;&nbsp;<a href="#output.epub">Transforming to ePub</a></li><li><a href="#rfc.section.11">11.</a>&nbsp;&nbsp;&nbsp;<a href="#extensions">Generic Extensions</a><ul><li><a href="#rfc.section.11.1">11.1</a>&nbsp;&nbsp;&nbsp;<a href="#ext.element.abnf-char-sequence">&lt;abnf-char-sequence&gt; element</a></li><li><a href="#rfc.section.11.2">11.2</a>&nbsp;&nbsp;&nbsp;<a href="#ext.element.anchor-alias">&lt;anchor-alias&gt; element</a></li><li><a href="#rfc.section.11.3">11.3</a>&nbsp;&nbsp;&nbsp;<a href="#ext.element.bcp14">&lt;bcp14&gt; element</a></li><li><a href="#rfc.section.11.4">11.4</a>&nbsp;&nbsp;&nbsp;<a href="#ext.element.bb">&lt;bb&gt; element</a></li><li><a href="#rfc.section.11.5">11.5</a>&nbsp;&nbsp;&nbsp;<a href="#ext.element.bc">&lt;bc&gt; element</a></li><li><a href="#rfc.section.11.6">11.6</a>&nbsp;&nbsp;&nbsp;<a href="#ext.element.blockquote">&lt;blockquote&gt; element</a></li><li><a href="#rfc.section.11.7">11.7</a>&nbsp;&nbsp;&nbsp;<a href="#ext.element.boilerplate">&lt;boilerplate&gt; element</a></li><li><a href="#rfc.section.11.8">11.8</a>&nbsp;&nbsp;&nbsp;<a href="#ext.element.bt">&lt;bt&gt; element</a></li><li><a href="#rfc.section.11.9">11.9</a>&nbsp;&nbsp;&nbsp;<a href="#ext.element.dfn">&lt;dfn&gt; element</a></li><li><a href="#rfc.section.11.10">11.10</a>&nbsp;&nbsp;&nbsp;<a href="#ext.element.feedback">&lt;feedback&gt; element</a></li><li><a href="#rfc.section.11.11">11.11</a>&nbsp;&nbsp;&nbsp;<a href="#ext.element.h">&lt;h&gt; element</a></li><li><a href="#rfc.section.11.12">11.12</a>&nbsp;&nbsp;&nbsp;<a href="#ext.element.highlight">&lt;highlight&gt; element</a></li><li><a href="#rfc.section.11.13">11.13</a>&nbsp;&nbsp;&nbsp;<a href="#ext.element.length-of">&lt;length-of&gt; element</a></li><li><a href="#rfc.section.11.14">11.14</a>&nbsp;&nbsp;&nbsp;<a href="#ext.element.link">&lt;link&gt; element</a></li><li><a href="#rfc.section.11.15">11.15</a>&nbsp;&nbsp;&nbsp;<a href="#ext.element.lt">&lt;lt&gt; element</a></li><li><a href="#rfc.section.11.16">11.16</a>&nbsp;&nbsp;&nbsp;<a href="#ext.element.note">&lt;note&gt; element</a></li><li><a href="#rfc.section.11.17">11.17</a>&nbsp;&nbsp;&nbsp;<a href="#ext.element.parse-xml">&lt;parse-xml&gt; element</a></li><li><a href="#rfc.section.11.18">11.18</a>&nbsp;&nbsp;&nbsp;<a href="#ext.element.prose">&lt;prose&gt; element</a></li><li><a href="#rfc.section.11.19">11.19</a>&nbsp;&nbsp;&nbsp;<a href="#ext.element.q">&lt;q&gt; element</a></li><li><a href="#rfc.section.11.20">11.20</a>&nbsp;&nbsp;&nbsp;<a href="#ext.element.ref">&lt;ref&gt; element</a></li><li><a href="#rfc.section.11.21">11.21</a>&nbsp;&nbsp;&nbsp;<a href="#ext.element.source">&lt;source&gt; element</a></li><li><a href="#rfc.section.11.22">11.22</a>&nbsp;&nbsp;&nbsp;<a href="#ext.element.sup">&lt;sup&gt; element</a></li><li><a href="#rfc.section.11.23">11.23</a>&nbsp;&nbsp;&nbsp;<a href="#ext-rfc2629.artwork">Extensions to Xml2rfc &lt;artwork&gt; element</a></li><li><a href="#rfc.section.11.24">11.24</a>&nbsp;&nbsp;&nbsp;<a href="#ext-rfc2629.iref">Extensions to Xml2rfc &lt;iref&gt; element</a></li><li><a href="#rfc.section.11.25">11.25</a>&nbsp;&nbsp;&nbsp;<a href="#ext-rfc2629.list">Extensions to Xml2rfc &lt;list&gt; element</a></li><li><a href="#rfc.section.11.26">11.26</a>&nbsp;&nbsp;&nbsp;<a href="#ext-rfc2629.rfc">Extensions to Xml2rfc &lt;rfc&gt; element</a></li><li><a href="#rfc.section.11.27">11.27</a>&nbsp;&nbsp;&nbsp;<a href="#ext-rfc2629.section">Extensions to Xml2rfc &lt;section&gt; element</a></li><li><a href="#rfc.section.11.28">11.28</a>&nbsp;&nbsp;&nbsp;<a href="#ext-rfc2629.xref">Extensions to Xml2rfc &lt;xref&gt; element</a></li></ul></li><li><a href="#rfc.section.12">12.</a>&nbsp;&nbsp;&nbsp;<a href="#utilities">Utilities</a><ul><li><a href="#rfc.section.12.1">12.1</a>&nbsp;&nbsp;&nbsp;<a href="#checking-references">Checking References</a></li><li><a href="#rfc.section.12.2">12.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.12.2">Generating Graphs from References</a></li><li><a href="#rfc.section.12.3">12.3</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.12.3">Producing reference entries for books</a></li><li><a href="#rfc.section.12.4">12.4</a>&nbsp;&nbsp;&nbsp;<a href="#clean-for-dtd">Down-converting to RFC2629bis DTD</a></li><li><a href="#rfc.section.12.5">12.5</a>&nbsp;&nbsp;&nbsp;<a href="#extract-artwork">Extracting artwork</a></li><li><a href="#rfc.section.12.6">12.6</a>&nbsp;&nbsp;&nbsp;<a href="#grddl">GRRDL</a></li></ul></li><li><a href="#rfc.section.13">13.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references">Informative References</a></li><li><a href="#rfc.authors">Author's Address</a></li><li><a href="#rfc.section.A">A.</a>&nbsp;&nbsp;&nbsp;<a href="#grammar">RELAX NG Compact Schema</a></li><li><a href="#rfc.section.B">B.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.B">Implementation Notes</a><ul><li><a href="#rfc.section.B.1">B.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.B.1">Recognized type attributes for &lt;artwork&gt; element</a></li></ul></li><li><a href="#rfc.section.C">C.</a>&nbsp;&nbsp;&nbsp;<a href="#examples">Examples</a><ul><li><a href="#rfc.section.C.1">C.1</a>&nbsp;&nbsp;&nbsp;<a href="#examples.internalsubset">Using the 'Internal Subset'</a></li><li><a href="#rfc.section.C.2">C.2</a>&nbsp;&nbsp;&nbsp;<a href="#examples.customizing">Customization</a></li></ul></li><li><a href="#rfc.section.D">D.</a>&nbsp;&nbsp;&nbsp;<a href="#boilerplate">Producing the IETF 'Boilerplate'</a><ul><li><a href="#rfc.section.D.1">D.1</a>&nbsp;&nbsp;&nbsp;<a href="#attribute-ipr">The /rfc/@ipr Attribute</a><ul><li><a href="#rfc.section.D.1.1">D.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#attribute-ipr-current">Current Values: '*trust200902'</a><ul><li><a href="#rfc.section.D.1.1.1">D.1.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#attribute-ipr-trust200902">trust200902</a></li><li><a href="#rfc.section.D.1.1.2">D.1.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#attribute-ipr-noModificationTrust200902">noModificationTrust200902</a></li><li><a href="#rfc.section.D.1.1.3">D.1.1.3</a>&nbsp;&nbsp;&nbsp;<a href="#attribute-ipr-noDerivativesTrust200902">noDerivativesTrust200902</a></li><li><a href="#rfc.section.D.1.1.4">D.1.1.4</a>&nbsp;&nbsp;&nbsp;<a href="#attribute-ipr-pre5378Trust200902">pre5378Trust200902</a></li></ul></li><li><a href="#rfc.section.D.1.2">D.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#attribute-ipr-historic">Historic Values</a><ul><li><a href="#rfc.section.D.1.2.1">D.1.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#attribute-ipr-200811">Historic Values: '*trust200811'</a></li><li><a href="#rfc.section.D.1.2.2">D.1.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#attribute-ipr-3978">Historic Values: '*3978'</a></li><li><a href="#rfc.section.D.1.2.3">D.1.2.3</a>&nbsp;&nbsp;&nbsp;<a href="#attribute-ipr-3667">Historic Values: '*3667'</a></li><li><a href="#rfc.section.D.1.2.4">D.1.2.4</a>&nbsp;&nbsp;&nbsp;<a href="#attribute-ipr-2026">Historic Values: '*2026'</a></li></ul></li></ul></li><li><a href="#rfc.section.D.2">D.2</a>&nbsp;&nbsp;&nbsp;<a href="#attribute-category">The /rfc/@category Attribute</a></li><li><a href="#rfc.section.D.3">D.3</a>&nbsp;&nbsp;&nbsp;<a href="#attribute-submissiontype">The /rfc/@submissionType Attribute</a></li><li><a href="#rfc.section.D.4">D.4</a>&nbsp;&nbsp;&nbsp;<a href="#attribute-consensus">The /rfc/@consensus Attribute</a></li><li><a href="#rfc.section.D.5">D.5</a>&nbsp;&nbsp;&nbsp;<a href="#attribute-number">The /rfc/@number Attribute</a></li><li><a href="#rfc.section.D.6">D.6</a>&nbsp;&nbsp;&nbsp;<a href="#attribute-docname">The /rfc/@docName Attribute</a></li><li><a href="#rfc.section.D.7">D.7</a>&nbsp;&nbsp;&nbsp;<a href="#attribute-obsoletes">The /rfc/@obsoletes Attribute</a></li><li><a href="#rfc.section.D.8">D.8</a>&nbsp;&nbsp;&nbsp;<a href="#attribute-updates">The /rfc/@updates Attribute</a></li></ul></li><li><a href="#rfc.section.E">E.</a>&nbsp;&nbsp;&nbsp;<a href="#license">License</a></li><li><a href="#rfc.section.F">F.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.F">Change Logs</a><ul><li><a href="#rfc.section.F.1">F.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.F.1">Package</a></li><li><a href="#rfc.section.F.2">F.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.F.2">amazon-asin.xslt</a></li><li><a href="#rfc.section.F.3">F.3</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.F.3">check-references.xslt</a></li><li><a href="#rfc.section.F.4">F.4</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.F.4">gen-reference-graph.xslt</a></li><li><a href="#rfc.section.F.5">F.5</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.F.5">rfc2629.xslt</a></li><li><a href="#rfc.section.F.6">F.6</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.F.6">rfc2629toFO.xslt</a></li><li><a href="#rfc.section.F.7">F.7</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.F.7">xsl11toAn.xslt</a></li><li><a href="#rfc.section.F.8">F.8</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.F.8">xsl11toFop.xslt</a></li><li><a href="#rfc.section.F.9">F.9</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.F.9">xsl11toXep.xslt</a></li></ul></li><li><a href="#rfc.index">Index</a></li></ul><hr class="noprint"><h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;Introduction</h1><p id="rfc.section.1.p.1">This document describes a set of XSLT transformations that can be used to transform RFC2629-compliant XML (see <a href="#RFC2629" id="rfc.xref.RFC2629.1"><cite title="Writing I-Ds and RFCs using XML">[RFC2629]</cite></a>) to various output formats, such as HTML and PDF. The main topics are </p><ul><li>compliance to the xml2rfc XML element set (<a href="#supported.elements" title="Supported RFC2629 elements">Section&nbsp;2</a>),</li><li>support for xml2rfc processing instructions (<a href="#processing.instructions" title="Processing Instructions">Section&nbsp;3</a>),</li><li>the names of anchor elements generated in HTML and PDF output (<a href="#anchors" title="Anchors">Section&nbsp;4</a>),</li><li>various XSLT engines that can be used (<a href="#xslt.engines" title="Supported XSLT engines">Section&nbsp;5</a>),</li><li>outputting HTML (<a href="#output.html" title="Transforming to HTML">Section&nbsp;6</a>) and XHTML (<a href="#output.xhtml" title="Transforming to XHTML">Section&nbsp;7</a>),</li><li>outputting CHM (Compiled Microsoft Help, <a href="#output.chm" title="Transforming to CHM (Microsoft Compiled Help)">Section&nbsp;8</a>),</li><li>outputting PDF (<a href="#output.pdf" title="Transforming to PDF">Section&nbsp;9</a>),</li><li>outputting ePub (<a href="#output.epub" title="Transforming to ePub">Section&nbsp;10</a>),</li><li>extensions to the xml2rfc vocabulary (<a href="#extensions" title="Generic Extensions">Section&nbsp;11</a>).</li><li>various utilities (<a href="#utilities" title="Utilities">Section&nbsp;12</a>).</li></ul><p id="rfc.section.1.p.2">The full distribution is available at &lt;<a href="http://greenbytes.de/tech/webdav/rfc2629xslt.zip">http://greenbytes.de/tech/webdav/rfc2629xslt.zip</a>&gt;.</p><hr class="noprint"><h1 id="rfc.section.2" class="np"><a href="#rfc.section.2">2.</a>&nbsp;<a id="supported.elements" href="#supported.elements">Supported RFC2629 elements</a></h1><p id="rfc.section.2.p.1"> <samp>rfc2629.xslt</samp> supports both all RFC2629 grammar elements and the extensions implemented in xml2rfc 1.36.</p><h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;Extension elements</h2><p id="rfc.section.2.1.p.1"> <samp>rfc2629.xslt</samp> supports two kind of extension elements, using different XML namespaces.</p><p id="rfc.section.2.1.p.2">The first set contains (hopefully) generally useful extensions, see <a href="#extensions" title="Generic Extensions">Section&nbsp;11</a>.</p><p id="rfc.section.2.1.p.3">The second set is used for change and issue tracking and currently is not documented here. Please email the author in case you're interested in using these extensions.</p><hr class="noprint"><h1 id="rfc.section.3" class="np"><a href="#rfc.section.3">3.</a>&nbsp;<a id="processing.instructions" href="#processing.instructions">Processing Instructions</a></h1><p id="rfc.section.3.p.1">All PIs can be set as XSLT parameter as well, overriding any value that is found in the source file to be transformed.</p><div id="rfc.figure.u.1"></div><p>Using processing instructions:</p><pre class="text">&lt;?rfc toc="yes"?&gt;
     374</style><link rel="Contents" href="#rfc.toc"><link rel="Author" href="#rfc.authors"><link rel="Index" href="#rfc.index"><link rel="Chapter" title="1 Introduction" href="#rfc.section.1"><link rel="Chapter" title="2 Supported RFC2629 elements" href="#rfc.section.2"><link rel="Chapter" title="3 Processing Instructions" href="#rfc.section.3"><link rel="Chapter" title="4 Anchors" href="#rfc.section.4"><link rel="Chapter" title="5 Supported XSLT engines" href="#rfc.section.5"><link rel="Chapter" title="6 Transforming to HTML" href="#rfc.section.6"><link rel="Chapter" title="7 Transforming to XHTML" href="#rfc.section.7"><link rel="Chapter" title="8 Transforming to CHM (Microsoft Compiled Help)" href="#rfc.section.8"><link rel="Chapter" title="9 Transforming to PDF" href="#rfc.section.9"><link rel="Chapter" title="10 Transforming to ePub" href="#rfc.section.10"><link rel="Chapter" title="11 Generic Extensions" href="#rfc.section.11"><link rel="Chapter" title="12 Utilities" href="#rfc.section.12"><link rel="Chapter" href="#rfc.section.13" title="13 Informative References"><link rel="Appendix" title="A RELAX NG Compact Schema" href="#rfc.section.A"><link rel="Appendix" title="B Implementation Notes" href="#rfc.section.B"><link rel="Appendix" title="C Examples" href="#rfc.section.C"><link rel="Appendix" title="D Producing the IETF 'Boilerplate'" href="#rfc.section.D"><link rel="Appendix" title="E License" href="#rfc.section.E"><link rel="Appendix" title="F Change Logs" href="#rfc.section.F"><meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.598, 2013/06/23 14:11:10, XSLT vendor: SAXON 6.5.5 from Michael Kay http://saxon.sf.net/"><meta name="keywords" content="RFC2629, xml2rfc, XSLT, hCard, XSL-FO, PDF, GRDDL, epub, Dublin Core"><link rel="schema.dct" href="http://purl.org/dc/terms/"><meta name="dct.creator" content="Reschke, J. F."></head><body><table class="header"><tbody><tr><td class="left">RFC2629 through XSLT</td><td class="right">J. Reschke</td></tr><tr><td class="left"></td><td class="right">greenbytes</td></tr><tr><td class="left"></td><td class="right">November 2012</td></tr></tbody></table><p class="title">Transforming RFC2629-formatted XML through XSLT</p><hr class="noprint"><h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1><ul class="toc"><li><a href="#rfc.section.1">1.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.1">Introduction</a></li><li><a href="#rfc.section.2">2.</a>&nbsp;&nbsp;&nbsp;<a href="#supported.elements">Supported RFC2629 elements</a><ul><li><a href="#rfc.section.2.1">2.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.2.1">Extension elements</a></li></ul></li><li><a href="#rfc.section.3">3.</a>&nbsp;&nbsp;&nbsp;<a href="#processing.instructions">Processing Instructions</a><ul><li><a href="#rfc.section.3.1">3.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.3.1">Supported xml2rfc-compatible PIs</a></li><li><a href="#rfc.section.3.2">3.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.3.2">Unsupported xml2rfc-compatible PIs</a></li><li><a href="#rfc.section.3.3">3.3</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.3.3">Extension PIs</a></li></ul></li><li><a href="#rfc.section.4">4.</a>&nbsp;&nbsp;&nbsp;<a href="#anchors">Anchors</a></li><li><a href="#rfc.section.5">5.</a>&nbsp;&nbsp;&nbsp;<a href="#xslt.engines">Supported XSLT engines</a><ul><li><a href="#rfc.section.5.1">5.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.5.1">Standalone Engines</a></li><li><a href="#rfc.section.5.2">5.2</a>&nbsp;&nbsp;&nbsp;<a href="#xslt.engines.browser">In-Browser Engines</a></li></ul></li><li><a href="#rfc.section.6">6.</a>&nbsp;&nbsp;&nbsp;<a href="#output.html">Transforming to HTML</a><ul><li><a href="#rfc.section.6.1">6.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.6.1">HTML compliance</a></li><li><a href="#rfc.section.6.2">6.2</a>&nbsp;&nbsp;&nbsp;<a href="#html.link">Standard HTML LINK elements</a></li><li><a href="#rfc.section.6.3">6.3</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.6.3">Standard HTML metadata</a></li><li><a href="#rfc.section.6.4">6.4</a>&nbsp;&nbsp;&nbsp;<a href="#rfc2731.properties">Dublin Core (RFC2731) metadata</a></li><li><a href="#rfc.section.6.5">6.5</a>&nbsp;&nbsp;&nbsp;<a href="#hcard">Experimental hCard support</a></li></ul></li><li><a href="#rfc.section.7">7.</a>&nbsp;&nbsp;&nbsp;<a href="#output.xhtml">Transforming to XHTML</a></li><li><a href="#rfc.section.8">8.</a>&nbsp;&nbsp;&nbsp;<a href="#output.chm">Transforming to CHM (Microsoft Compiled Help)</a></li><li><a href="#rfc.section.9">9.</a>&nbsp;&nbsp;&nbsp;<a href="#output.pdf">Transforming to PDF</a><ul><li><a href="#rfc.section.9.1">9.1</a>&nbsp;&nbsp;&nbsp;<a href="#output.pdf.fop">Via XSL-FO</a><ul><li><a href="#rfc.section.9.1.1">9.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.9.1.1">Extension feature matrix</a></li><li><a href="#rfc.section.9.1.2">9.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.9.1.2">Example: producing output for Apache FOP</a></li></ul></li><li><a href="#rfc.section.9.2">9.2</a>&nbsp;&nbsp;&nbsp;<a href="#output.pdf.html">Via X(HTML)</a></li></ul></li><li><a href="#rfc.section.10">10.</a>&nbsp;&nbsp;&nbsp;<a href="#output.epub">Transforming to ePub</a></li><li><a href="#rfc.section.11">11.</a>&nbsp;&nbsp;&nbsp;<a href="#extensions">Generic Extensions</a><ul><li><a href="#rfc.section.11.1">11.1</a>&nbsp;&nbsp;&nbsp;<a href="#ext.element.abnf-char-sequence">&lt;abnf-char-sequence&gt; element</a></li><li><a href="#rfc.section.11.2">11.2</a>&nbsp;&nbsp;&nbsp;<a href="#ext.element.anchor-alias">&lt;anchor-alias&gt; element</a></li><li><a href="#rfc.section.11.3">11.3</a>&nbsp;&nbsp;&nbsp;<a href="#ext.element.bcp14">&lt;bcp14&gt; element</a></li><li><a href="#rfc.section.11.4">11.4</a>&nbsp;&nbsp;&nbsp;<a href="#ext.element.bb">&lt;bb&gt; element</a></li><li><a href="#rfc.section.11.5">11.5</a>&nbsp;&nbsp;&nbsp;<a href="#ext.element.bc">&lt;bc&gt; element</a></li><li><a href="#rfc.section.11.6">11.6</a>&nbsp;&nbsp;&nbsp;<a href="#ext.element.blockquote">&lt;blockquote&gt; element</a></li><li><a href="#rfc.section.11.7">11.7</a>&nbsp;&nbsp;&nbsp;<a href="#ext.element.boilerplate">&lt;boilerplate&gt; element</a></li><li><a href="#rfc.section.11.8">11.8</a>&nbsp;&nbsp;&nbsp;<a href="#ext.element.bt">&lt;bt&gt; element</a></li><li><a href="#rfc.section.11.9">11.9</a>&nbsp;&nbsp;&nbsp;<a href="#ext.element.dfn">&lt;dfn&gt; element</a></li><li><a href="#rfc.section.11.10">11.10</a>&nbsp;&nbsp;&nbsp;<a href="#ext.element.feedback">&lt;feedback&gt; element</a></li><li><a href="#rfc.section.11.11">11.11</a>&nbsp;&nbsp;&nbsp;<a href="#ext.element.h">&lt;h&gt; element</a></li><li><a href="#rfc.section.11.12">11.12</a>&nbsp;&nbsp;&nbsp;<a href="#ext.element.highlight">&lt;highlight&gt; element</a></li><li><a href="#rfc.section.11.13">11.13</a>&nbsp;&nbsp;&nbsp;<a href="#ext.element.length-of">&lt;length-of&gt; element</a></li><li><a href="#rfc.section.11.14">11.14</a>&nbsp;&nbsp;&nbsp;<a href="#ext.element.link">&lt;link&gt; element</a></li><li><a href="#rfc.section.11.15">11.15</a>&nbsp;&nbsp;&nbsp;<a href="#ext.element.lt">&lt;lt&gt; element</a></li><li><a href="#rfc.section.11.16">11.16</a>&nbsp;&nbsp;&nbsp;<a href="#ext.element.note">&lt;note&gt; element</a></li><li><a href="#rfc.section.11.17">11.17</a>&nbsp;&nbsp;&nbsp;<a href="#ext.element.parse-xml">&lt;parse-xml&gt; element</a></li><li><a href="#rfc.section.11.18">11.18</a>&nbsp;&nbsp;&nbsp;<a href="#ext.element.prose">&lt;prose&gt; element</a></li><li><a href="#rfc.section.11.19">11.19</a>&nbsp;&nbsp;&nbsp;<a href="#ext.element.q">&lt;q&gt; element</a></li><li><a href="#rfc.section.11.20">11.20</a>&nbsp;&nbsp;&nbsp;<a href="#ext.element.ref">&lt;ref&gt; element</a></li><li><a href="#rfc.section.11.21">11.21</a>&nbsp;&nbsp;&nbsp;<a href="#ext.element.source">&lt;source&gt; element</a></li><li><a href="#rfc.section.11.22">11.22</a>&nbsp;&nbsp;&nbsp;<a href="#ext.element.sup">&lt;sup&gt; element</a></li><li><a href="#rfc.section.11.23">11.23</a>&nbsp;&nbsp;&nbsp;<a href="#ext-rfc2629.artwork">Extensions to Xml2rfc &lt;artwork&gt; element</a></li><li><a href="#rfc.section.11.24">11.24</a>&nbsp;&nbsp;&nbsp;<a href="#ext-rfc2629.iref">Extensions to Xml2rfc &lt;iref&gt; element</a></li><li><a href="#rfc.section.11.25">11.25</a>&nbsp;&nbsp;&nbsp;<a href="#ext-rfc2629.list">Extensions to Xml2rfc &lt;list&gt; element</a></li><li><a href="#rfc.section.11.26">11.26</a>&nbsp;&nbsp;&nbsp;<a href="#ext-rfc2629.rfc">Extensions to Xml2rfc &lt;rfc&gt; element</a></li><li><a href="#rfc.section.11.27">11.27</a>&nbsp;&nbsp;&nbsp;<a href="#ext-rfc2629.section">Extensions to Xml2rfc &lt;section&gt; element</a></li><li><a href="#rfc.section.11.28">11.28</a>&nbsp;&nbsp;&nbsp;<a href="#ext-rfc2629.xref">Extensions to Xml2rfc &lt;xref&gt; element</a></li></ul></li><li><a href="#rfc.section.12">12.</a>&nbsp;&nbsp;&nbsp;<a href="#utilities">Utilities</a><ul><li><a href="#rfc.section.12.1">12.1</a>&nbsp;&nbsp;&nbsp;<a href="#checking-references">Checking References</a></li><li><a href="#rfc.section.12.2">12.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.12.2">Generating Graphs from References</a></li><li><a href="#rfc.section.12.3">12.3</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.12.3">Producing reference entries for books</a></li><li><a href="#rfc.section.12.4">12.4</a>&nbsp;&nbsp;&nbsp;<a href="#clean-for-dtd">Down-converting to RFC2629bis DTD</a></li><li><a href="#rfc.section.12.5">12.5</a>&nbsp;&nbsp;&nbsp;<a href="#extract-artwork">Extracting artwork</a></li><li><a href="#rfc.section.12.6">12.6</a>&nbsp;&nbsp;&nbsp;<a href="#grddl">GRRDL</a></li></ul></li><li><a href="#rfc.section.13">13.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references">Informative References</a></li><li><a href="#rfc.authors">Author's Address</a></li><li><a href="#rfc.section.A">A.</a>&nbsp;&nbsp;&nbsp;<a href="#grammar">RELAX NG Compact Schema</a></li><li><a href="#rfc.section.B">B.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.B">Implementation Notes</a><ul><li><a href="#rfc.section.B.1">B.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.B.1">Recognized type attributes for &lt;artwork&gt; element</a></li></ul></li><li><a href="#rfc.section.C">C.</a>&nbsp;&nbsp;&nbsp;<a href="#examples">Examples</a><ul><li><a href="#rfc.section.C.1">C.1</a>&nbsp;&nbsp;&nbsp;<a href="#examples.internalsubset">Using the 'Internal Subset'</a></li><li><a href="#rfc.section.C.2">C.2</a>&nbsp;&nbsp;&nbsp;<a href="#examples.customizing">Customization</a></li></ul></li><li><a href="#rfc.section.D">D.</a>&nbsp;&nbsp;&nbsp;<a href="#boilerplate">Producing the IETF 'Boilerplate'</a><ul><li><a href="#rfc.section.D.1">D.1</a>&nbsp;&nbsp;&nbsp;<a href="#attribute-ipr">The /rfc/@ipr Attribute</a><ul><li><a href="#rfc.section.D.1.1">D.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#attribute-ipr-current">Current Values: '*trust200902'</a><ul><li><a href="#rfc.section.D.1.1.1">D.1.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#attribute-ipr-trust200902">trust200902</a></li><li><a href="#rfc.section.D.1.1.2">D.1.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#attribute-ipr-noModificationTrust200902">noModificationTrust200902</a></li><li><a href="#rfc.section.D.1.1.3">D.1.1.3</a>&nbsp;&nbsp;&nbsp;<a href="#attribute-ipr-noDerivativesTrust200902">noDerivativesTrust200902</a></li><li><a href="#rfc.section.D.1.1.4">D.1.1.4</a>&nbsp;&nbsp;&nbsp;<a href="#attribute-ipr-pre5378Trust200902">pre5378Trust200902</a></li></ul></li><li><a href="#rfc.section.D.1.2">D.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#attribute-ipr-historic">Historic Values</a><ul><li><a href="#rfc.section.D.1.2.1">D.1.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#attribute-ipr-200811">Historic Values: '*trust200811'</a></li><li><a href="#rfc.section.D.1.2.2">D.1.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#attribute-ipr-3978">Historic Values: '*3978'</a></li><li><a href="#rfc.section.D.1.2.3">D.1.2.3</a>&nbsp;&nbsp;&nbsp;<a href="#attribute-ipr-3667">Historic Values: '*3667'</a></li><li><a href="#rfc.section.D.1.2.4">D.1.2.4</a>&nbsp;&nbsp;&nbsp;<a href="#attribute-ipr-2026">Historic Values: '*2026'</a></li></ul></li></ul></li><li><a href="#rfc.section.D.2">D.2</a>&nbsp;&nbsp;&nbsp;<a href="#attribute-category">The /rfc/@category Attribute</a></li><li><a href="#rfc.section.D.3">D.3</a>&nbsp;&nbsp;&nbsp;<a href="#attribute-submissiontype">The /rfc/@submissionType Attribute</a></li><li><a href="#rfc.section.D.4">D.4</a>&nbsp;&nbsp;&nbsp;<a href="#attribute-consensus">The /rfc/@consensus Attribute</a></li><li><a href="#rfc.section.D.5">D.5</a>&nbsp;&nbsp;&nbsp;<a href="#attribute-number">The /rfc/@number Attribute</a></li><li><a href="#rfc.section.D.6">D.6</a>&nbsp;&nbsp;&nbsp;<a href="#attribute-docname">The /rfc/@docName Attribute</a></li><li><a href="#rfc.section.D.7">D.7</a>&nbsp;&nbsp;&nbsp;<a href="#attribute-obsoletes">The /rfc/@obsoletes Attribute</a></li><li><a href="#rfc.section.D.8">D.8</a>&nbsp;&nbsp;&nbsp;<a href="#attribute-updates">The /rfc/@updates Attribute</a></li></ul></li><li><a href="#rfc.section.E">E.</a>&nbsp;&nbsp;&nbsp;<a href="#license">License</a></li><li><a href="#rfc.section.F">F.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.F">Change Logs</a><ul><li><a href="#rfc.section.F.1">F.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.F.1">Package</a></li><li><a href="#rfc.section.F.2">F.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.F.2">amazon-asin.xslt</a></li><li><a href="#rfc.section.F.3">F.3</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.F.3">check-references.xslt</a></li><li><a href="#rfc.section.F.4">F.4</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.F.4">gen-reference-graph.xslt</a></li><li><a href="#rfc.section.F.5">F.5</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.F.5">rfc2629.xslt</a></li><li><a href="#rfc.section.F.6">F.6</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.F.6">rfc2629toFO.xslt</a></li><li><a href="#rfc.section.F.7">F.7</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.F.7">xsl11toAn.xslt</a></li><li><a href="#rfc.section.F.8">F.8</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.F.8">xsl11toFop.xslt</a></li><li><a href="#rfc.section.F.9">F.9</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.F.9">xsl11toXep.xslt</a></li></ul></li><li><a href="#rfc.index">Index</a></li></ul><hr class="noprint"><h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;Introduction</h1><p id="rfc.section.1.p.1">This document describes a set of XSLT transformations that can be used to transform RFC2629-compliant XML (see <a href="#RFC2629" id="rfc.xref.RFC2629.1"><cite title="Writing I-Ds and RFCs using XML">[RFC2629]</cite></a>) to various output formats, such as HTML and PDF. The main topics are </p><ul><li>compliance to the xml2rfc XML element set (<a href="#supported.elements" title="Supported RFC2629 elements">Section&nbsp;2</a>),</li><li>support for xml2rfc processing instructions (<a href="#processing.instructions" title="Processing Instructions">Section&nbsp;3</a>),</li><li>the names of anchor elements generated in HTML and PDF output (<a href="#anchors" title="Anchors">Section&nbsp;4</a>),</li><li>various XSLT engines that can be used (<a href="#xslt.engines" title="Supported XSLT engines">Section&nbsp;5</a>),</li><li>outputting HTML (<a href="#output.html" title="Transforming to HTML">Section&nbsp;6</a>) and XHTML (<a href="#output.xhtml" title="Transforming to XHTML">Section&nbsp;7</a>),</li><li>outputting CHM (Compiled Microsoft Help, <a href="#output.chm" title="Transforming to CHM (Microsoft Compiled Help)">Section&nbsp;8</a>),</li><li>outputting PDF (<a href="#output.pdf" title="Transforming to PDF">Section&nbsp;9</a>),</li><li>outputting ePub (<a href="#output.epub" title="Transforming to ePub">Section&nbsp;10</a>),</li><li>extensions to the xml2rfc vocabulary (<a href="#extensions" title="Generic Extensions">Section&nbsp;11</a>).</li><li>various utilities (<a href="#utilities" title="Utilities">Section&nbsp;12</a>).</li></ul><p id="rfc.section.1.p.2">The full distribution is available at &lt;<a href="http://greenbytes.de/tech/webdav/rfc2629xslt.zip">http://greenbytes.de/tech/webdav/rfc2629xslt.zip</a>&gt;.</p><hr class="noprint"><h1 id="rfc.section.2" class="np"><a href="#rfc.section.2">2.</a>&nbsp;<a id="supported.elements" href="#supported.elements">Supported RFC2629 elements</a></h1><p id="rfc.section.2.p.1"><samp>rfc2629.xslt</samp> supports both all RFC2629 grammar elements and the extensions implemented in xml2rfc 1.36.</p><h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;Extension elements</h2><p id="rfc.section.2.1.p.1"><samp>rfc2629.xslt</samp> supports two kind of extension elements, using different XML namespaces.</p><p id="rfc.section.2.1.p.2">The first set contains (hopefully) generally useful extensions, see <a href="#extensions" title="Generic Extensions">Section&nbsp;11</a>.</p><p id="rfc.section.2.1.p.3">The second set is used for change and issue tracking and currently is not documented here. Please email the author in case you're interested in using these extensions.</p><hr class="noprint"><h1 id="rfc.section.3" class="np"><a href="#rfc.section.3">3.</a>&nbsp;<a id="processing.instructions" href="#processing.instructions">Processing Instructions</a></h1><p id="rfc.section.3.p.1">All PIs can be set as XSLT parameter as well, overriding any value that is found in the source file to be transformed.</p><div id="rfc.figure.u.1"></div><p>Using processing instructions:</p><pre class="text">&lt;?rfc toc="yes"?&gt;
    375375&lt;?rfc-ext support-rfc2731="no"?&gt;
    376376</pre><div id="rfc.figure.u.2"></div><p>Using XSLT parameters (Saxon):</p><pre class="text">java -cp saxon.jar com.icl.saxon.StyleSheet source.xml rfc2629.xslt \
     
    379379   --param xml2rfc-ext-support-rfc2731 '"no"' \
    380380   rfc2629.xslt source.xml &gt; result.html
    381 </pre><p>(note the required quoting of string parameters)<span id="rfc.iref.x.1"></span></p><h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;Supported xml2rfc-compatible PIs</h2><div id="rfc.table.u.1"><table class="tt full center" cellpadding="3" cellspacing="0"><thead><tr><th>PI target</th><th>PI pseudo-attribute</th><th>XSLT parameter name</th><th>default</th><th>comment</th></tr></thead><tbody><tr><td class="left">rfc</td><td class="left">background<div id="rfc.iref.b.1"></div><div id="rfc.iref.p.1"></div></td><td class="left">xml2rfc-background<div id="rfc.iref.x.2"></div>  <div id="rfc.iref.p.2"></div></td><td class="left">(not set)</td><td class="left"></td></tr><tr><td class="left">rfc</td><td class="left">compact<div id="rfc.iref.c.1"></div><div id="rfc.iref.p.3"></div></td><td class="left">xml2rfc-compact<div id="rfc.iref.x.3"></div>  <div id="rfc.iref.p.4"></div></td><td class="left">"no"</td><td class="left">only applies to HTML output method when printing</td></tr><tr><td class="left">rfc</td><td class="left">comments<div id="rfc.iref.c.2"></div><div id="rfc.iref.p.5"></div></td><td class="left">xml2rfc-comments<div id="rfc.iref.x.4"></div>  <div id="rfc.iref.p.6"></div></td><td class="left">(not set)</td><td class="left"></td></tr><tr><td class="left">rfc</td><td class="left">editing<div id="rfc.iref.e.1"></div><div id="rfc.iref.p.7"></div></td><td class="left">xml2rfc-editing<div id="rfc.iref.x.5"></div>  <div id="rfc.iref.p.8"></div></td><td class="left">"no"</td><td class="left"></td></tr><tr><td class="left">rfc</td><td class="left">footer<div id="rfc.iref.f.1"></div><div id="rfc.iref.p.9"></div></td><td class="left">xml2rfc-footer<div id="rfc.iref.x.6"></div>  <div id="rfc.iref.p.10"></div></td><td class="left">(not set)</td><td class="left"></td></tr><tr><td class="left">rfc</td><td class="left">header<div id="rfc.iref.h.1"></div><div id="rfc.iref.p.11"></div></td><td class="left">xml2rfc-header<div id="rfc.iref.x.7"></div>  <div id="rfc.iref.p.12"></div></td><td class="left">(not set)</td><td class="left"></td></tr><tr><td class="left">rfc</td><td class="left">inline<div id="rfc.iref.i.1"></div><div id="rfc.iref.p.13"></div></td><td class="left">xml2rfc-inline<div id="rfc.iref.x.8"></div>  <div id="rfc.iref.p.14"></div></td><td class="left">(not set)</td><td class="left"></td></tr><tr><td class="left">rfc</td><td class="left">iprnotified<div id="rfc.iref.i.2"></div><div id="rfc.iref.p.15"></div></td><td class="left">xml2rfc-iprnotified<div id="rfc.iref.x.9"></div>  <div id="rfc.iref.p.16"></div></td><td class="left">"no"</td><td class="left"></td></tr><tr><td class="left">rfc</td><td class="left">linkmailto<div id="rfc.iref.l.1"></div><div id="rfc.iref.p.17"></div></td><td class="left">xml2rfc-linkmailto<div id="rfc.iref.x.10"></div>  <div id="rfc.iref.p.18"></div></td><td class="left">"yes"</td><td class="left"></td></tr><tr><td class="left">rfc</td><td class="left">private<div id="rfc.iref.p.19"></div><div id="rfc.iref.p.20"></div></td><td class="left">xml2rfc-private<div id="rfc.iref.x.11"></div>  <div id="rfc.iref.p.21"></div></td><td class="left">(not set)</td><td class="left"></td></tr><tr><td class="left">rfc</td><td class="left">refparent<div id="rfc.iref.r.1"></div><div id="rfc.iref.p.22"></div></td><td class="left">xml2rfc-private<div id="rfc.iref.x.12"></div>  <div id="rfc.iref.p.23"></div></td><td class="left">"References"</td><td class="left">Title for References sections when automatically inserted</td></tr><tr><td class="left">rfc</td><td class="left">rfcedstyle<div id="rfc.iref.r.2"></div><div id="rfc.iref.p.24"></div></td><td class="left">xml2rfc-rfcedstyle<div id="rfc.iref.x.13"></div>  <div id="rfc.iref.p.25"></div></td><td class="left">(not set)</td><td class="left">(limited support)</td></tr><tr><td class="left">rfc</td><td class="left">sortrefs<div id="rfc.iref.s.1"></div><div id="rfc.iref.p.26"></div></td><td class="left">xml2rfc-sortrefs<div id="rfc.iref.x.14"></div>  <div id="rfc.iref.p.27"></div></td><td class="left">"no"</td><td class="left"></td></tr><tr><td class="left">rfc</td><td class="left">symrefs<div id="rfc.iref.s.2"></div><div id="rfc.iref.p.28"></div></td><td class="left">xml2rfc-symrefs<div id="rfc.iref.x.15"></div>  <div id="rfc.iref.p.29"></div></td><td class="left">"yes"</td><td class="left">The default has changed from "no" to "yes" as of June 6, 2007 and xml2rfc 1.33pre4.</td></tr><tr><td class="left">rfc</td><td class="left">toc<div id="rfc.iref.t.1"></div><div id="rfc.iref.p.30"></div></td><td class="left">xml2rfc-toc<div id="rfc.iref.x.16"></div>  <div id="rfc.iref.p.31"></div></td><td class="left">"no"</td><td class="left"></td></tr><tr><td class="left">rfc</td><td class="left">tocdepth<div id="rfc.iref.t.2"></div><div id="rfc.iref.p.32"></div></td><td class="left">xml2rfc-tocdepth<div id="rfc.iref.x.17"></div>  <div id="rfc.iref.p.33"></div></td><td class="left">99</td><td class="left"></td></tr><tr><td class="left">rfc</td><td class="left">topblock<div id="rfc.iref.t.3"></div><div id="rfc.iref.p.34"></div></td><td class="left">xml2rfc-topblock<div id="rfc.iref.x.18"></div>  <div id="rfc.iref.p.35"></div></td><td class="left">"yes"</td><td class="left"></td></tr></tbody></table></div><h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;Unsupported xml2rfc-compatible PIs</h2><div id="rfc.table.u.2"><table class="tt full center" cellpadding="3" cellspacing="0"><thead><tr><th>PI target</th><th>PI pseudo-attribute</th><th>comment</th></tr></thead><tbody><tr><td class="left">rfc</td><td class="left">include<div id="rfc.iref.i.3"></div><div id="rfc.iref.p.36"></div></td><td class="left">incompatible with XML/XSLT processing model, please use external entities instead</td></tr><tr><td class="left">rfc</td><td class="left">needLines<div id="rfc.iref.n.1"></div><div id="rfc.iref.p.37"></div></td><td class="left"></td></tr><tr><td class="left">rfc</td><td class="left">slides<div id="rfc.iref.s.3"></div><div id="rfc.iref.p.38"></div></td><td class="left"></td></tr><tr><td class="left">rfc</td><td class="left">strict<div id="rfc.iref.s.4"></div><div id="rfc.iref.p.39"></div></td><td class="left"></td></tr><tr><td class="left">rfc</td><td class="left">subcompact<div id="rfc.iref.s.5"></div><div id="rfc.iref.p.40"></div></td><td class="left"></td></tr><tr><td class="left">rfc</td><td class="left">tocindent<div id="rfc.iref.t.4"></div><div id="rfc.iref.p.41"></div></td><td class="left">(defaults to "yes")</td></tr><tr><td class="left">rfc</td><td class="left">tocompact<div id="rfc.iref.t.5"></div><div id="rfc.iref.p.42"></div></td><td class="left"></td></tr></tbody></table></div><h2 id="rfc.section.3.3"><a href="#rfc.section.3.3">3.3</a>&nbsp;Extension PIs</h2><div id="rfc.table.u.3"><table class="tt full center" cellpadding="3" cellspacing="0"><thead><tr><th>PI target</th><th>PI pseudo-attribute</th><th>XSLT parameter name</th><th>default</th><th>description</th></tr></thead><tbody><tr><td class="left">rfc-ext</td><td class="left">allow-markup-in-artwork<div id="rfc.iref.a.1"></div><div id="rfc.iref.p.43"></div></td><td class="left">xml2rfc-allow-markup-in-artwork<div id="rfc.iref.x.19"></div>  <div id="rfc.iref.p.44"></div></td><td class="left">"no"</td><td class="left">Enables support for specific elements inside abstract elements (using this extension makes the document incompatible to the RFC2629bis DTD; see description of conversion XSLT in <a href="#clean-for-dtd" title="Down-converting to RFC2629bis DTD">Section&nbsp;12.4</a>).</td></tr><tr><td class="left">rfc-ext</td><td class="left">authors-section<div id="rfc.iref.a.2"></div><div id="rfc.iref.p.45"></div></td><td class="left">xml2rfc-ext-authors-section<div id="rfc.iref.x.20"></div>  <div id="rfc.iref.p.46"></div></td><td class="left"></td><td class="left">When "end", place the authors section at the end (just before the copyright statements). This seems to be the preferred order in the newest RFCs.</td></tr><tr><td class="left">rfc-ext</td><td class="left">duplex<div id="rfc.iref.d.1"></div><div id="rfc.iref.p.47"></div></td><td class="left">xml2rfc-ext-duplex<div id="rfc.iref.x.21"></div>  <div id="rfc.iref.p.48"></div></td><td class="left">no</td><td class="left">When set to "yes", format the PDF output for doublesided printing.</td></tr><tr><td class="left">rfc-ext</td><td class="left">include-index<div id="rfc.iref.i.4"></div><div id="rfc.iref.p.49"></div></td><td class="left">xml2rfc-ext-include-index<div id="rfc.iref.x.22"></div>  <div id="rfc.iref.p.50"></div></td><td class="left">"yes"</td><td class="left">When set to "no", no index will be generated.</td></tr><tr><td class="left">rfc-ext</td><td class="left">include-references-in-index<div id="rfc.iref.i.5"></div><div id="rfc.iref.p.51"></div></td><td class="left">xml2rfc-ext-include-references-in-index<div id="rfc.iref.x.23"></div>  <div id="rfc.iref.p.52"></div></td><td class="left"></td><td class="left">When set to "yes", index entries are generated for all references.</td></tr><tr><td class="left">rfc-ext</td><td class="left">justification<div id="rfc.iref.j.1"></div><div id="rfc.iref.p.53"></div></td><td class="left">xml2rfc-ext-justification<div id="rfc.iref.x.24"></div>  <div id="rfc.iref.p.54"></div></td><td class="left">"never"</td><td class="left">"never": never emit justified text, "always": always emit justified text, "print": only emit justified text for print media.</td></tr><tr><td class="left">rfc-ext</td><td class="left">parse-xml-in-artwork<div id="rfc.iref.p.55"></div><div id="rfc.iref.p.56"></div></td><td class="left">xml2rfc-parse-xml-in-artwork<div id="rfc.iref.x.25"></div>  <div id="rfc.iref.p.57"></div></td><td class="left">"no"</td><td class="left">May be used to enable parsing of XML content in figures (MSXML only).</td></tr><tr><td class="left">rfc-ext</td><td class="left">support-rfc2731<div id="rfc.iref.s.6"></div><div id="rfc.iref.p.58"></div></td><td class="left">xml2rfc-ext-support-rfc2731<div id="rfc.iref.x.26"></div>  <div id="rfc.iref.p.59"></div></td><td class="left">"yes"</td><td class="left">Decides whether the HTML transformation should generate META tags according <a href="#rfc2731.properties" title="Dublin Core (RFC2731) metadata">Section&nbsp;6.4</a>.</td></tr><tr><td class="left">rfc-ext</td><td class="left">sec-no-trailing-dots<div id="rfc.iref.s.7"></div><div id="rfc.iref.p.60"></div></td><td class="left">xml2rfc-ext-sec-no-trailing-dots<div id="rfc.iref.x.27"></div>  <div id="rfc.iref.p.61"></div></td><td class="left"></td><td class="left">When set to "yes", add trailing dots to section numbers. This seems to be the preferred format in the newest RFCs.</td></tr></tbody></table></div><hr class="noprint"><h1 id="rfc.section.4" class="np"><a href="#rfc.section.4">4.</a>&nbsp;<a id="anchors" href="#anchors">Anchors</a></h1><p id="rfc.section.4.p.1">The transformation automatically generates anchors that are supposed to be stable and predictable and that can be used to identify specific parts of the document. Anchors are generated both in HTML and XSL-FO content (but the latter will only be used for PDF output when the XSL-FO engine supports producing PDF anchors).</p><div id="rfc.table.u.4"><p>The following anchors get auto-generated:</p><table class="tt full center" cellpadding="3" cellspacing="0"><thead><tr><th>Anchor name</th><th>Description</th></tr></thead><tbody><tr><td class="left">rfc.abstract <div id="rfc.iref.r.3"></div><div id="rfc.iref.a.3"></div></td><td class="left">Abstract</td></tr><tr><td class="left">rfc.authors <div id="rfc.iref.r.4"></div><div id="rfc.iref.a.4"></div></td><td class="left">Authors section</td></tr><tr><td class="left">rfc.copyright <div id="rfc.iref.r.5"></div><div id="rfc.iref.a.5"></div></td><td class="left">Copyright section</td></tr><tr><td class="left">rfc.copyrightnotice <div id="rfc.iref.r.6"></div><div id="rfc.iref.a.6"></div></td><td class="left">Copyright notice</td></tr><tr><td class="left">rfc.figure.<em>n</em>  <div id="rfc.iref.r.7"></div><div id="rfc.iref.a.7"></div></td><td class="left">Figures (titled)</td></tr><tr><td class="left">rfc.figure.u.<em>n</em>  <div id="rfc.iref.r.8"></div><div id="rfc.iref.a.8"></div></td><td class="left">Figures (untitled)</td></tr><tr><td class="left">rfc.index <div id="rfc.iref.r.9"></div><div id="rfc.iref.a.9"></div></td><td class="left">Index</td></tr><tr><td class="left">rfc.ipr <div id="rfc.iref.r.10"></div><div id="rfc.iref.a.10"></div></td><td class="left">Intellectual Property</td></tr><tr><td class="left">rfc.iref.<em>n</em>  <div id="rfc.iref.r.11"></div><div id="rfc.iref.a.11"></div></td><td class="left">Internal references</td></tr><tr><td class="left">rfc.note.<em>n</em>  <div id="rfc.iref.r.12"></div><div id="rfc.iref.a.12"></div></td><td class="left">Notes (from front section)</td></tr><tr><td class="left">rfc.references <div id="rfc.iref.r.13"></div><div id="rfc.iref.a.13"></div></td><td class="left">References</td></tr><tr><td class="left">rfc.references.<em>n</em>  <div id="rfc.iref.r.14"></div><div id="rfc.iref.a.14"></div></td><td class="left">Additional references</td></tr><tr><td class="left">rfc.section.<em>n</em>  <div id="rfc.iref.r.15"></div><div id="rfc.iref.a.15"></div></td><td class="left">Section <em>n</em></td></tr><tr><td class="left">rfc.section.<em>n</em>.p.<em>m</em>  <div id="rfc.iref.r.16"></div><div id="rfc.iref.a.16"></div></td><td class="left">Section <em>n</em>, paragraph <em>m</em></td></tr><tr><td class="left">rfc.status <div id="rfc.iref.r.17"></div><div id="rfc.iref.a.17"></div></td><td class="left">Status of memo</td></tr><tr><td class="left">rfc.table.<em>n</em>  <div id="rfc.iref.r.18"></div><div id="rfc.iref.a.18"></div></td><td class="left">Tables (titled)</td></tr><tr><td class="left">rfc.table.u.<em>n</em>  <div id="rfc.iref.r.19"></div><div id="rfc.iref.a.19"></div></td><td class="left">Tables (untitled)</td></tr><tr><td class="left">rfc.toc <div id="rfc.iref.r.20"></div><div id="rfc.iref.a.20"></div></td><td class="left">Table of contents</td></tr><tr><td class="left">rfc.xref.<em>name</em>.<em>n</em>  <div id="rfc.iref.r.21"></div><div id="rfc.iref.a.21"></div></td><td class="left">References to reference <em>n</em> to <em>name</em></td></tr></tbody></table></div><hr class="noprint"><h1 id="rfc.section.5" class="np"><a href="#rfc.section.5">5.</a>&nbsp;<a id="xslt.engines" href="#xslt.engines">Supported XSLT engines</a></h1><p id="rfc.section.5.p.1">The transformation requires a non-standard extension function (see <a href="http://www.exslt.org/exsl/functions/node-set/index.html">exsl:node-set</a>) which is however widely available. XSLT processors that do not support this extension (or a functional equivalent, such as msxsl:node-set) currently are not supported.</p><div id="exsl-date-time"><p id="rfc.section.5.p.2">Input documents do not always specify the date completely. In this case, the transformation attempts to let the XSLT engine to compute the system date, using either scripting in Microsoft's XSLT engine, or the <a href="http://www.exslt.org/date/functions/date-time/">exsl:date-time</a> extension function.</p></div><h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;Standalone Engines</h2><p id="rfc.section.5.1.p.1">The following XSLT engines are believed to work well: </p><ul><li>Windows: <span id="rfc.iref.m.1"></span><span id="rfc.iref.m.2"></span>MSXML3 and MSXML4 (&lt;<a href="http://msdn.microsoft.com/xml">http://msdn.microsoft.com/xml</a>&gt;; command line processor "msxsl" is available from <a href="http://www.microsoft.com/downloads/details.aspx?FamilyID=2FB55371-C94E-4373-B0E9-DB4816552E41">Microsoft Download Center</a>)</li><li>Java: <span id="rfc.iref.s.8"></span>Saxon (&lt;<a href="http://saxon.sourceforge.net/">http://saxon.sourceforge.net/</a>&gt;)</li><li>Java: <span id="rfc.iref.x.28"></span>Xalan (&lt;<a href="http://xml.apache.org/xalan-j/">http://xml.apache.org/xalan-j/</a>&gt;)</li><li>C/C++: <span id="rfc.iref.x.29"></span>xsltproc (libxslt) (&lt;<a href="http://xmlsoft.org/XSLT/">http://xmlsoft.org/XSLT/</a>&gt;, make sure that you have a current version)</li></ul><h2 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a>&nbsp;<a id="xslt.engines.browser" href="#xslt.engines.browser">In-Browser Engines</a></h2><p id="rfc.section.5.2.p.1">The following browsers seem to work fine: </p><ul><li><p><span id="rfc.iref.i.6"></span>Internet Explorer 5.5 (Windows version, if MSXML3 is installed)</p></li><li><p><span id="rfc.iref.i.7"></span><span id="rfc.iref.i.8"></span><span id="rfc.iref.i.9"></span><span id="rfc.iref.i.10"></span>Internet Explorer 6 and newer</p></li><li><div id="firefox3"><p><span id="rfc.iref.m.3"></span><span id="rfc.iref.f.2"></span>Firefox 3.0 and newer</p></div><p> </p><ul><li>Be aware that XSLT execution can be suppressed using <span id="rfc.iref.n.2"></span><a href="https://addons.mozilla.org/de/firefox/addon/722">NoScript</a></li><li>Firefox does not load external DTDs nor external entities, see <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=22942">Mozilla Bug 22942</a>, thus entities like &amp;nbsp; need to be declared in the internal subset (<a href="#examples.internalsubset" title="Using the 'Internal Subset'">Appendix&nbsp;C.1</a>)</li><li>There seems to be a new problem in Firefox 4 where it occasionally does the initial rendering with the wrong width (people who can reproduce this problem please comment on &lt;<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=640390">https://bugzilla.mozilla.org/show_bug.cgi?id=640390</a>&gt;.</li><li>Date computation is available in Firefox starting with Firefox 6 (see &lt;<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=603159">https://bugzilla.mozilla.org/show_bug.cgi?id=603159</a>&gt;)</li></ul></li><li><p><span id="rfc.iref.s.9"></span><span id="rfc.iref.s.10"></span>Safari 3 (starting with version 3.0.4)</p><p> </p><ul><li>Date computation not available (see &lt;<a href="https://bugs.webkit.org/show_bug.cgi?id=4079">https://bugs.webkit.org/show_bug.cgi?id=4079</a>&gt;)</li></ul></li><li><p><span id="rfc.iref.g.1"></span>Google Chrome</p><p> </p><ul><li>Date computation not available (see &lt;<a href="https://bugs.webkit.org/show_bug.cgi?id=4079">https://bugs.webkit.org/show_bug.cgi?id=4079</a>&gt;)</li></ul></li><li><p><span id="rfc.iref.o.1"></span>Opera (starting with version 10)</p><p> </p><ul><li>Date computation not available</li></ul></li></ul><p id="rfc.section.5.2.p.2">The following browsers are known not to work properly: </p><ul><li><div id="firefox12"><p><span id="rfc.iref.m.4"></span><span id="rfc.iref.f.3"></span>Firefox 1.*/2.*: (missing extension function - see change request at Mozilla BugZilla <a href="http://bugzilla.mozilla.org/show_bug.cgi?id=193678">193678</a>)</p></div></li><li><div id="opera"><p><span id="rfc.iref.o.2"></span>Opera 9.21: execution fails, potentially to a somewhat complex XPath expression (reported to Opera as bug 245725).</p></div></li><li><p>Opera 9.5 and 9.6: transformation appears to work, but CSS isn't getting applied (reported to Opera as bug 337388 on 2008-06-12).</p></li><li><div id="safari"><p><span id="rfc.iref.s.11"></span>Safari 2.* supports client-side XSLT as of MacOS X 10.4, but misses required extension functions. A problem with stylesheets producing non-ASCII output (such as NBSP characters) has been fixed as of OSX 10.4.4. Both problems have been reported through Apple's bug tracking system, see &lt;<a href="http://drakken.dbc.mtview.ca.us/pipermail/xml2rfc/2005-May/002073.html">http://drakken.dbc.mtview.ca.us/pipermail/xml2rfc/2005-May/002073.html</a>&gt; and &lt;<a href="http://bugs.webkit.org/show_bug.cgi?id=4079">http://bugs.webkit.org/show_bug.cgi?id=4079</a>&gt;.</p></div></li></ul><hr class="noprint"><h1 id="rfc.section.6" class="np"><a href="#rfc.section.6">6.</a>&nbsp;<a id="output.html" href="#output.html">Transforming to HTML</a></h1><p id="rfc.section.6.p.1">Transformation to HTML can be done inside the browser if it supports XSLT. To enable this, add the following processing instruction to the start of the source file:</p><div id="rfc.iref.x.30"></div><div id="rfc.figure.u.4"></div><pre class="text">  &lt;?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?&gt;
    382 </pre><p id="rfc.section.6.p.3">(and ensure that <samp>rfc2629.xslt</samp> is present).</p><h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a>&nbsp;HTML compliance</h2><p id="rfc.section.6.1.p.1">The transformation result is supposed to conform to the HTML 4.01 strict DTD <a href="#HTML" id="rfc.xref.HTML.1"><cite title="HTML 4.01 Specification">[HTML]</cite></a>. This can be checked using the W3C's online validator at &lt;<a href="http://validator.w3.org">http://validator.w3.org</a>&gt;<span id="rfc.iref.h.2"></span>.</p><h2 id="rfc.section.6.2"><a href="#rfc.section.6.2">6.2</a>&nbsp;<a id="html.link" href="#html.link">Standard HTML LINK elements</a></h2><p id="rfc.section.6.2.p.1">LINK elements exist since HTML 2.0. They can be used to embed content-independant links inside the document. Unfortunately, only few user agents support this element. Firefox users may want to check the <a href="https://addons.mozilla.org/firefox/2933/">Link Widgets</a> extension.</p><div id="rfc.table.u.5"><p>The following LINK elements are produced:</p><table class="tt full center" cellpadding="3" cellspacing="0"><thead><tr><th>LINK type</th><th>description</th></tr></thead><tbody><tr><td class="left">alternate<div id="rfc.iref.a.22"></div><div id="rfc.iref.h.3"></div></td><td class="left">for RFCs, a link to the authorative ASCII version on the IETF web site</td></tr><tr><td class="left">appendic<div id="rfc.iref.a.23"></div><div id="rfc.iref.h.4"></div></td><td class="left">pointer to all top-level appendics</td></tr><tr><td class="left">author<div id="rfc.iref.a.24"></div><div id="rfc.iref.h.5"></div></td><td class="left">pointer to "authors" section</td></tr><tr><td class="left">chapter<div id="rfc.iref.c.3"></div><div id="rfc.iref.h.6"></div></td><td class="left">pointer to all top-level sections</td></tr><tr><td class="left">contents<div id="rfc.iref.c.4"></div><div id="rfc.iref.h.7"></div></td><td class="left">pointer to table of contents</td></tr><tr><td class="left">copyright<div id="rfc.iref.c.5"></div><div id="rfc.iref.h.8"></div></td><td class="left">pointer to copyright statement</td></tr><tr><td class="left">index<div id="rfc.iref.i.11"></div><div id="rfc.iref.h.9"></div></td><td class="left">pointer to index</td></tr></tbody></table></div><div id="rfc.figure.u.5"></div><p>The figure below shows how Mozilla Firefox 1.0 displays the Site Navigation Bar for rfc2396.xml.</p><p><img src="rfc2629xslt-fig1.png" alt="&#xA;(LINK elements displayed in Mozilla Firefox for RFC2396.xml)&#xA;" width="509" height="235"></p><h2 id="rfc.section.6.3"><a href="#rfc.section.6.3">6.3</a>&nbsp;Standard HTML metadata</h2><div id="rfc.table.u.6"><p>The following standard HTML META elements are produced:</p><table class="tt full center" cellpadding="3" cellspacing="0"><thead><tr><th>META name</th><th>description</th></tr></thead><tbody><tr><td class="left">generator<div id="rfc.iref.g.2"></div><div id="rfc.iref.h.10"></div></td><td class="left">from XSLT engine version and stylesheet version</td></tr><tr><td class="left">keywords<div id="rfc.iref.k.1"></div><div id="rfc.iref.h.11"></div></td><td class="left">from keyword elements in front section</td></tr></tbody></table></div><h2 id="rfc.section.6.4"><a href="#rfc.section.6.4">6.4</a>&nbsp;<a id="rfc2731.properties" href="#rfc2731.properties">Dublin Core (RFC2731) metadata</a></h2><p id="rfc.section.6.4.p.1">Unless turned off using the "rfc-ext support-rfc2731" processing instruction, the transformation will generate metadata according to <a href="#RFC2731" id="rfc.xref.RFC2731.1"><cite title="Encoding Dublin Core Metadata in HTML">[RFC2731]</cite></a> and <a href="#DC-HTML" id="rfc.xref.DC-HTML.1"><cite title="Expressing Dublin Core metadata using HTML/XHTML meta and link elements">[DC-HTML]</cite></a>.</p><div id="rfc.table.u.7"><p>The following DCMI properties are produced:</p><table class="tt full center" cellpadding="3" cellspacing="0"><thead><tr><th>META name</th><th>description</th></tr></thead><tbody><tr><td class="left">DC.Creator<div id="rfc.iref.c.6"></div><div id="rfc.iref.d.2"></div></td><td class="left">from author information in front section</td></tr><tr><td class="left">DC.Date.Issued<div id="rfc.iref.d.3"></div><div id="rfc.iref.d.4"></div></td><td class="left">from date information in front section</td></tr><tr><td class="left">DC.Description.Abstract<div id="rfc.iref.d.5"></div><div id="rfc.iref.d.6"></div></td><td class="left">from abstract</td></tr><tr><td class="left">DC.Identifier<div id="rfc.iref.i.12"></div><div id="rfc.iref.d.7"></div></td><td class="left">document URN <a href="#RFC2648" id="rfc.xref.RFC2648.1"><cite title="A URN Namespace for IETF Documents">[RFC2648]</cite></a> from "docName" attribute</td></tr><tr><td class="left">DC.isPartOf<div id="rfc.iref.i.13"></div><div id="rfc.iref.d.8"></div></td><td class="left">RFC ISSN (for RFCs)</td></tr><tr><td class="left">DC.Relation.Replaces<div id="rfc.iref.r.22"></div><div id="rfc.iref.d.9"></div></td><td class="left">from "obsoletes" attribute</td></tr></tbody></table></div><h2 id="rfc.section.6.5"><a href="#rfc.section.6.5">6.5</a>&nbsp;<a id="hcard" href="#hcard">Experimental hCard support</a></h2><p id="rfc.section.6.5.p.1">The generated author information is formatted in <a href="http://microformats.org/wiki/hcard">hCard</a> format.</p><hr class="noprint"><h1 id="rfc.section.7" class="np"><a href="#rfc.section.7">7.</a>&nbsp;<a id="output.xhtml" href="#output.xhtml">Transforming to XHTML</a></h1><p id="rfc.section.7.p.1">Transforming to XHTML requires slightly different XSLT output options and is implemented by the derived transformation script <samp>rfc2629toXHTML.xslt</samp>.</p><ul class="empty"><li> <b>Note:</b> Microsoft Internet Explorer does <em>not</em> support XHTML. Therefore it usually makes more sense to generate plain old HTML.</li></ul><hr class="noprint"><h1 id="rfc.section.8" class="np"><a href="#rfc.section.8">8.</a>&nbsp;<a id="output.chm" href="#output.chm">Transforming to CHM (Microsoft Compiled Help)</a></h1><p id="rfc.section.8.p.1"> <span id="rfc.iref.c.7"></span> <span id="rfc.iref.m.5"></span> To generate a CHM file using Microsoft's HTML Help Compiler (hhc), three files are required in addition to the HTML file. </p><ol><li>hhc - table of contents file (HTML)</li><li>hhk - index file (HTML)</li><li>hhp - project file (plain text)</li></ol><p id="rfc.section.8.p.2">The three files are generated with three specific transformations, each requiring the additional XSLT parameter "basename" to specify the filename prefix.</p><div id="rfc.figure.u.6"></div><p>Example:</p><pre class="text">saxon rfc2616.xml rfc2629toHhp.xslt basename=rfc2616  &gt; rfc2616.hhp
     381</pre><p>(note the required quoting of string parameters)<span id="rfc.iref.x.1"></span></p><h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;Supported xml2rfc-compatible PIs</h2><div id="rfc.table.u.1"><table class="tt full center" cellpadding="3" cellspacing="0"><thead><tr><th>PI target</th><th>PI pseudo-attribute</th><th>XSLT parameter name</th><th>default</th><th>comment</th></tr></thead><tbody><tr><td class="left">rfc</td><td class="left">background<div id="rfc.iref.b.1"></div><div id="rfc.iref.p.1"></div></td><td class="left">xml2rfc-background<div id="rfc.iref.x.2"></div> <div id="rfc.iref.p.2"></div></td><td class="left">(not set)</td><td class="left"></td></tr><tr><td class="left">rfc</td><td class="left">compact<div id="rfc.iref.c.1"></div><div id="rfc.iref.p.3"></div></td><td class="left">xml2rfc-compact<div id="rfc.iref.x.3"></div> <div id="rfc.iref.p.4"></div></td><td class="left">"no"</td><td class="left">only applies to HTML output method when printing</td></tr><tr><td class="left">rfc</td><td class="left">comments<div id="rfc.iref.c.2"></div><div id="rfc.iref.p.5"></div></td><td class="left">xml2rfc-comments<div id="rfc.iref.x.4"></div> <div id="rfc.iref.p.6"></div></td><td class="left">(not set)</td><td class="left"></td></tr><tr><td class="left">rfc</td><td class="left">editing<div id="rfc.iref.e.1"></div><div id="rfc.iref.p.7"></div></td><td class="left">xml2rfc-editing<div id="rfc.iref.x.5"></div> <div id="rfc.iref.p.8"></div></td><td class="left">"no"</td><td class="left"></td></tr><tr><td class="left">rfc</td><td class="left">footer<div id="rfc.iref.f.1"></div><div id="rfc.iref.p.9"></div></td><td class="left">xml2rfc-footer<div id="rfc.iref.x.6"></div> <div id="rfc.iref.p.10"></div></td><td class="left">(not set)</td><td class="left"></td></tr><tr><td class="left">rfc</td><td class="left">header<div id="rfc.iref.h.1"></div><div id="rfc.iref.p.11"></div></td><td class="left">xml2rfc-header<div id="rfc.iref.x.7"></div> <div id="rfc.iref.p.12"></div></td><td class="left">(not set)</td><td class="left"></td></tr><tr><td class="left">rfc</td><td class="left">inline<div id="rfc.iref.i.1"></div><div id="rfc.iref.p.13"></div></td><td class="left">xml2rfc-inline<div id="rfc.iref.x.8"></div> <div id="rfc.iref.p.14"></div></td><td class="left">(not set)</td><td class="left"></td></tr><tr><td class="left">rfc</td><td class="left">iprnotified<div id="rfc.iref.i.2"></div><div id="rfc.iref.p.15"></div></td><td class="left">xml2rfc-iprnotified<div id="rfc.iref.x.9"></div> <div id="rfc.iref.p.16"></div></td><td class="left">"no"</td><td class="left"></td></tr><tr><td class="left">rfc</td><td class="left">linkmailto<div id="rfc.iref.l.1"></div><div id="rfc.iref.p.17"></div></td><td class="left">xml2rfc-linkmailto<div id="rfc.iref.x.10"></div> <div id="rfc.iref.p.18"></div></td><td class="left">"yes"</td><td class="left"></td></tr><tr><td class="left">rfc</td><td class="left">private<div id="rfc.iref.p.19"></div><div id="rfc.iref.p.20"></div></td><td class="left">xml2rfc-private<div id="rfc.iref.x.11"></div> <div id="rfc.iref.p.21"></div></td><td class="left">(not set)</td><td class="left"></td></tr><tr><td class="left">rfc</td><td class="left">refparent<div id="rfc.iref.r.1"></div><div id="rfc.iref.p.22"></div></td><td class="left">xml2rfc-private<div id="rfc.iref.x.12"></div> <div id="rfc.iref.p.23"></div></td><td class="left">"References"</td><td class="left">Title for References sections when automatically inserted</td></tr><tr><td class="left">rfc</td><td class="left">rfcedstyle<div id="rfc.iref.r.2"></div><div id="rfc.iref.p.24"></div></td><td class="left">xml2rfc-rfcedstyle<div id="rfc.iref.x.13"></div> <div id="rfc.iref.p.25"></div></td><td class="left">(not set)</td><td class="left">(limited support)</td></tr><tr><td class="left">rfc</td><td class="left">sortrefs<div id="rfc.iref.s.1"></div><div id="rfc.iref.p.26"></div></td><td class="left">xml2rfc-sortrefs<div id="rfc.iref.x.14"></div> <div id="rfc.iref.p.27"></div></td><td class="left">"no"</td><td class="left"></td></tr><tr><td class="left">rfc</td><td class="left">symrefs<div id="rfc.iref.s.2"></div><div id="rfc.iref.p.28"></div></td><td class="left">xml2rfc-symrefs<div id="rfc.iref.x.15"></div> <div id="rfc.iref.p.29"></div></td><td class="left">"yes"</td><td class="left">The default has changed from "no" to "yes" as of June 6, 2007 and xml2rfc 1.33pre4.</td></tr><tr><td class="left">rfc</td><td class="left">toc<div id="rfc.iref.t.1"></div><div id="rfc.iref.p.30"></div></td><td class="left">xml2rfc-toc<div id="rfc.iref.x.16"></div> <div id="rfc.iref.p.31"></div></td><td class="left">"no"</td><td class="left"></td></tr><tr><td class="left">rfc</td><td class="left">tocdepth<div id="rfc.iref.t.2"></div><div id="rfc.iref.p.32"></div></td><td class="left">xml2rfc-tocdepth<div id="rfc.iref.x.17"></div> <div id="rfc.iref.p.33"></div></td><td class="left">99</td><td class="left"></td></tr><tr><td class="left">rfc</td><td class="left">topblock<div id="rfc.iref.t.3"></div><div id="rfc.iref.p.34"></div></td><td class="left">xml2rfc-topblock<div id="rfc.iref.x.18"></div> <div id="rfc.iref.p.35"></div></td><td class="left">"yes"</td><td class="left"></td></tr></tbody></table></div><h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;Unsupported xml2rfc-compatible PIs</h2><div id="rfc.table.u.2"><table class="tt full center" cellpadding="3" cellspacing="0"><thead><tr><th>PI target</th><th>PI pseudo-attribute</th><th>comment</th></tr></thead><tbody><tr><td class="left">rfc</td><td class="left">include<div id="rfc.iref.i.3"></div><div id="rfc.iref.p.36"></div></td><td class="left">incompatible with XML/XSLT processing model, please use external entities instead</td></tr><tr><td class="left">rfc</td><td class="left">needLines<div id="rfc.iref.n.1"></div><div id="rfc.iref.p.37"></div></td><td class="left"></td></tr><tr><td class="left">rfc</td><td class="left">slides<div id="rfc.iref.s.3"></div><div id="rfc.iref.p.38"></div></td><td class="left"></td></tr><tr><td class="left">rfc</td><td class="left">strict<div id="rfc.iref.s.4"></div><div id="rfc.iref.p.39"></div></td><td class="left"></td></tr><tr><td class="left">rfc</td><td class="left">subcompact<div id="rfc.iref.s.5"></div><div id="rfc.iref.p.40"></div></td><td class="left"></td></tr><tr><td class="left">rfc</td><td class="left">tocindent<div id="rfc.iref.t.4"></div><div id="rfc.iref.p.41"></div></td><td class="left">(defaults to "yes")</td></tr><tr><td class="left">rfc</td><td class="left">tocompact<div id="rfc.iref.t.5"></div><div id="rfc.iref.p.42"></div></td><td class="left"></td></tr></tbody></table></div><h2 id="rfc.section.3.3"><a href="#rfc.section.3.3">3.3</a>&nbsp;Extension PIs</h2><div id="rfc.table.u.3"><table class="tt full center" cellpadding="3" cellspacing="0"><thead><tr><th>PI target</th><th>PI pseudo-attribute</th><th>XSLT parameter name</th><th>default</th><th>description</th></tr></thead><tbody><tr><td class="left">rfc-ext</td><td class="left">allow-markup-in-artwork<div id="rfc.iref.a.1"></div><div id="rfc.iref.p.43"></div></td><td class="left">xml2rfc-allow-markup-in-artwork<div id="rfc.iref.x.19"></div> <div id="rfc.iref.p.44"></div></td><td class="left">"no"</td><td class="left">Enables support for specific elements inside abstract elements (using this extension makes the document incompatible to the RFC2629bis DTD; see description of conversion XSLT in <a href="#clean-for-dtd" title="Down-converting to RFC2629bis DTD">Section&nbsp;12.4</a>).</td></tr><tr><td class="left">rfc-ext</td><td class="left">authors-section<div id="rfc.iref.a.2"></div><div id="rfc.iref.p.45"></div></td><td class="left">xml2rfc-ext-authors-section<div id="rfc.iref.x.20"></div> <div id="rfc.iref.p.46"></div></td><td class="left"></td><td class="left">When "end", place the authors section at the end (just before the copyright statements). This seems to be the preferred order in the newest RFCs.</td></tr><tr><td class="left">rfc-ext</td><td class="left">duplex<div id="rfc.iref.d.1"></div><div id="rfc.iref.p.47"></div></td><td class="left">xml2rfc-ext-duplex<div id="rfc.iref.x.21"></div> <div id="rfc.iref.p.48"></div></td><td class="left">no</td><td class="left">When set to "yes", format the PDF output for doublesided printing.</td></tr><tr><td class="left">rfc-ext</td><td class="left">include-index<div id="rfc.iref.i.4"></div><div id="rfc.iref.p.49"></div></td><td class="left">xml2rfc-ext-include-index<div id="rfc.iref.x.22"></div> <div id="rfc.iref.p.50"></div></td><td class="left">"yes"</td><td class="left">When set to "no", no index will be generated.</td></tr><tr><td class="left">rfc-ext</td><td class="left">include-references-in-index<div id="rfc.iref.i.5"></div><div id="rfc.iref.p.51"></div></td><td class="left">xml2rfc-ext-include-references-in-index<div id="rfc.iref.x.23"></div> <div id="rfc.iref.p.52"></div></td><td class="left"></td><td class="left">When set to "yes", index entries are generated for all references.</td></tr><tr><td class="left">rfc-ext</td><td class="left">justification<div id="rfc.iref.j.1"></div><div id="rfc.iref.p.53"></div></td><td class="left">xml2rfc-ext-justification<div id="rfc.iref.x.24"></div> <div id="rfc.iref.p.54"></div></td><td class="left">"never"</td><td class="left">"never": never emit justified text, "always": always emit justified text, "print": only emit justified text for print media.</td></tr><tr><td class="left">rfc-ext</td><td class="left">parse-xml-in-artwork<div id="rfc.iref.p.55"></div><div id="rfc.iref.p.56"></div></td><td class="left">xml2rfc-parse-xml-in-artwork<div id="rfc.iref.x.25"></div> <div id="rfc.iref.p.57"></div></td><td class="left">"no"</td><td class="left">May be used to enable parsing of XML content in figures (MSXML only).</td></tr><tr><td class="left">rfc-ext</td><td class="left">support-rfc2731<div id="rfc.iref.s.6"></div><div id="rfc.iref.p.58"></div></td><td class="left">xml2rfc-ext-support-rfc2731<div id="rfc.iref.x.26"></div> <div id="rfc.iref.p.59"></div></td><td class="left">"yes"</td><td class="left">Decides whether the HTML transformation should generate META tags according <a href="#rfc2731.properties" title="Dublin Core (RFC2731) metadata">Section&nbsp;6.4</a>.</td></tr><tr><td class="left">rfc-ext</td><td class="left">sec-no-trailing-dots<div id="rfc.iref.s.7"></div><div id="rfc.iref.p.60"></div></td><td class="left">xml2rfc-ext-sec-no-trailing-dots<div id="rfc.iref.x.27"></div> <div id="rfc.iref.p.61"></div></td><td class="left"></td><td class="left">When set to "yes", add trailing dots to section numbers. This seems to be the preferred format in the newest RFCs.</td></tr></tbody></table></div><hr class="noprint"><h1 id="rfc.section.4" class="np"><a href="#rfc.section.4">4.</a>&nbsp;<a id="anchors" href="#anchors">Anchors</a></h1><p id="rfc.section.4.p.1">The transformation automatically generates anchors that are supposed to be stable and predictable and that can be used to identify specific parts of the document. Anchors are generated both in HTML and XSL-FO content (but the latter will only be used for PDF output when the XSL-FO engine supports producing PDF anchors).</p><div id="rfc.table.u.4"><p>The following anchors get auto-generated:</p><table class="tt full center" cellpadding="3" cellspacing="0"><thead><tr><th>Anchor name</th><th>Description</th></tr></thead><tbody><tr><td class="left">rfc.abstract <div id="rfc.iref.r.3"></div><div id="rfc.iref.a.3"></div></td><td class="left">Abstract</td></tr><tr><td class="left">rfc.authors <div id="rfc.iref.r.4"></div><div id="rfc.iref.a.4"></div></td><td class="left">Authors section</td></tr><tr><td class="left">rfc.copyright <div id="rfc.iref.r.5"></div><div id="rfc.iref.a.5"></div></td><td class="left">Copyright section</td></tr><tr><td class="left">rfc.copyrightnotice <div id="rfc.iref.r.6"></div><div id="rfc.iref.a.6"></div></td><td class="left">Copyright notice</td></tr><tr><td class="left">rfc.figure.<em>n</em> <div id="rfc.iref.r.7"></div><div id="rfc.iref.a.7"></div></td><td class="left">Figures (titled)</td></tr><tr><td class="left">rfc.figure.u.<em>n</em> <div id="rfc.iref.r.8"></div><div id="rfc.iref.a.8"></div></td><td class="left">Figures (untitled)</td></tr><tr><td class="left">rfc.index <div id="rfc.iref.r.9"></div><div id="rfc.iref.a.9"></div></td><td class="left">Index</td></tr><tr><td class="left">rfc.ipr <div id="rfc.iref.r.10"></div><div id="rfc.iref.a.10"></div></td><td class="left">Intellectual Property</td></tr><tr><td class="left">rfc.iref.<em>n</em> <div id="rfc.iref.r.11"></div><div id="rfc.iref.a.11"></div></td><td class="left">Internal references</td></tr><tr><td class="left">rfc.note.<em>n</em> <div id="rfc.iref.r.12"></div><div id="rfc.iref.a.12"></div></td><td class="left">Notes (from front section)</td></tr><tr><td class="left">rfc.references <div id="rfc.iref.r.13"></div><div id="rfc.iref.a.13"></div></td><td class="left">References</td></tr><tr><td class="left">rfc.references.<em>n</em> <div id="rfc.iref.r.14"></div><div id="rfc.iref.a.14"></div></td><td class="left">Additional references</td></tr><tr><td class="left">rfc.section.<em>n</em> <div id="rfc.iref.r.15"></div><div id="rfc.iref.a.15"></div></td><td class="left">Section <em>n</em></td></tr><tr><td class="left">rfc.section.<em>n</em>.p.<em>m</em> <div id="rfc.iref.r.16"></div><div id="rfc.iref.a.16"></div></td><td class="left">Section <em>n</em>, paragraph <em>m</em></td></tr><tr><td class="left">rfc.status <div id="rfc.iref.r.17"></div><div id="rfc.iref.a.17"></div></td><td class="left">Status of memo</td></tr><tr><td class="left">rfc.table.<em>n</em> <div id="rfc.iref.r.18"></div><div id="rfc.iref.a.18"></div></td><td class="left">Tables (titled)</td></tr><tr><td class="left">rfc.table.u.<em>n</em> <div id="rfc.iref.r.19"></div><div id="rfc.iref.a.19"></div></td><td class="left">Tables (untitled)</td></tr><tr><td class="left">rfc.toc <div id="rfc.iref.r.20"></div><div id="rfc.iref.a.20"></div></td><td class="left">Table of contents</td></tr><tr><td class="left">rfc.xref.<em>name</em>.<em>n</em> <div id="rfc.iref.r.21"></div><div id="rfc.iref.a.21"></div></td><td class="left">References to reference <em>n</em> to <em>name</em></td></tr></tbody></table></div><hr class="noprint"><h1 id="rfc.section.5" class="np"><a href="#rfc.section.5">5.</a>&nbsp;<a id="xslt.engines" href="#xslt.engines">Supported XSLT engines</a></h1><p id="rfc.section.5.p.1">The transformation requires a non-standard extension function (see <a href="http://www.exslt.org/exsl/functions/node-set/index.html">exsl:node-set</a>) which is however widely available. XSLT processors that do not support this extension (or a functional equivalent, such as msxsl:node-set) currently are not supported.</p><div id="exsl-date-time"><p id="rfc.section.5.p.2">Input documents do not always specify the date completely. In this case, the transformation attempts to let the XSLT engine to compute the system date, using either scripting in Microsoft's XSLT engine, or the <a href="http://www.exslt.org/date/functions/date-time/">exsl:date-time</a> extension function.</p></div><h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;Standalone Engines</h2><p id="rfc.section.5.1.p.1">The following XSLT engines are believed to work well: </p><ul><li>Windows: <span id="rfc.iref.m.1"></span><span id="rfc.iref.m.2"></span>MSXML3 and MSXML4 (&lt;<a href="http://msdn.microsoft.com/xml">http://msdn.microsoft.com/xml</a>&gt;; command line processor "msxsl" is available from <a href="http://www.microsoft.com/downloads/details.aspx?FamilyID=2FB55371-C94E-4373-B0E9-DB4816552E41">Microsoft Download Center</a>)</li><li>Java: <span id="rfc.iref.s.8"></span>Saxon (&lt;<a href="http://saxon.sourceforge.net/">http://saxon.sourceforge.net/</a>&gt;)</li><li>Java: <span id="rfc.iref.x.28"></span>Xalan (&lt;<a href="http://xml.apache.org/xalan-j/">http://xml.apache.org/xalan-j/</a>&gt;)</li><li>C/C++: <span id="rfc.iref.x.29"></span>xsltproc (libxslt) (&lt;<a href="http://xmlsoft.org/XSLT/">http://xmlsoft.org/XSLT/</a>&gt;, make sure that you have a current version)</li></ul><h2 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a>&nbsp;<a id="xslt.engines.browser" href="#xslt.engines.browser">In-Browser Engines</a></h2><p id="rfc.section.5.2.p.1">The following browsers seem to work fine: </p><ul><li><p><span id="rfc.iref.i.6"></span>Internet Explorer 5.5 (Windows version, if MSXML3 is installed)</p></li><li><p><span id="rfc.iref.i.7"></span><span id="rfc.iref.i.8"></span><span id="rfc.iref.i.9"></span><span id="rfc.iref.i.10"></span>Internet Explorer 6 and newer</p></li><li><div id="firefox3"><p><span id="rfc.iref.m.3"></span><span id="rfc.iref.f.2"></span>Firefox 3.0 and newer</p></div><p></p><ul><li>Be aware that XSLT execution can be suppressed using <span id="rfc.iref.n.2"></span><a href="https://addons.mozilla.org/de/firefox/addon/722">NoScript</a></li><li>Firefox does not load external DTDs nor external entities, see <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=22942">Mozilla Bug 22942</a>, thus entities like &amp;nbsp; need to be declared in the internal subset (<a href="#examples.internalsubset" title="Using the 'Internal Subset'">Appendix&nbsp;C.1</a>)</li><li>There seems to be a new problem in Firefox 4 where it occasionally does the initial rendering with the wrong width (people who can reproduce this problem please comment on &lt;<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=640390">https://bugzilla.mozilla.org/show_bug.cgi?id=640390</a>&gt;.</li><li>Date computation is available in Firefox starting with Firefox 6 (see &lt;<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=603159">https://bugzilla.mozilla.org/show_bug.cgi?id=603159</a>&gt;)</li></ul></li><li><p><span id="rfc.iref.s.9"></span><span id="rfc.iref.s.10"></span>Safari 3 (starting with version 3.0.4)</p><p></p><ul><li>Date computation not available (see &lt;<a href="https://bugs.webkit.org/show_bug.cgi?id=4079">https://bugs.webkit.org/show_bug.cgi?id=4079</a>&gt;)</li></ul></li><li><p><span id="rfc.iref.g.1"></span>Google Chrome</p><p></p><ul><li>Date computation not available (see &lt;<a href="https://bugs.webkit.org/show_bug.cgi?id=4079">https://bugs.webkit.org/show_bug.cgi?id=4079</a>&gt;)</li></ul></li><li><p><span id="rfc.iref.o.1"></span>Opera (starting with version 10)</p><p></p><ul><li>Date computation not available</li></ul></li></ul><p id="rfc.section.5.2.p.2">The following browsers are known not to work properly: </p><ul><li><div id="firefox12"><p><span id="rfc.iref.m.4"></span><span id="rfc.iref.f.3"></span>Firefox 1.*/2.*: (missing extension function - see change request at Mozilla BugZilla <a href="http://bugzilla.mozilla.org/show_bug.cgi?id=193678">193678</a>)</p></div></li><li><div id="opera"><p><span id="rfc.iref.o.2"></span>Opera 9.21: execution fails, potentially to a somewhat complex XPath expression (reported to Opera as bug 245725).</p></div></li><li><p>Opera 9.5 and 9.6: transformation appears to work, but CSS isn't getting applied (reported to Opera as bug 337388 on 2008-06-12).</p></li><li><div id="safari"><p><span id="rfc.iref.s.11"></span>Safari 2.* supports client-side XSLT as of MacOS X 10.4, but misses required extension functions. A problem with stylesheets producing non-ASCII output (such as NBSP characters) has been fixed as of OSX 10.4.4. Both problems have been reported through Apple's bug tracking system, see &lt;<a href="http://drakken.dbc.mtview.ca.us/pipermail/xml2rfc/2005-May/002073.html">http://drakken.dbc.mtview.ca.us/pipermail/xml2rfc/2005-May/002073.html</a>&gt; and &lt;<a href="http://bugs.webkit.org/show_bug.cgi?id=4079">http://bugs.webkit.org/show_bug.cgi?id=4079</a>&gt;.</p></div></li></ul><hr class="noprint"><h1 id="rfc.section.6" class="np"><a href="#rfc.section.6">6.</a>&nbsp;<a id="output.html" href="#output.html">Transforming to HTML</a></h1><p id="rfc.section.6.p.1">Transformation to HTML can be done inside the browser if it supports XSLT. To enable this, add the following processing instruction to the start of the source file:</p><div id="rfc.iref.x.30"></div><div id="rfc.figure.u.4"></div><pre class="text">  &lt;?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?&gt;
     382</pre><p id="rfc.section.6.p.3">(and ensure that <samp>rfc2629.xslt</samp> is present).</p><h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a>&nbsp;HTML compliance</h2><p id="rfc.section.6.1.p.1">The transformation result is supposed to conform to the HTML 4.01 strict DTD <a href="#HTML" id="rfc.xref.HTML.1"><cite title="HTML 4.01 Specification">[HTML]</cite></a>. This can be checked using the W3C's online validator at &lt;<a href="http://validator.w3.org">http://validator.w3.org</a>&gt;<span id="rfc.iref.h.2"></span>.</p><h2 id="rfc.section.6.2"><a href="#rfc.section.6.2">6.2</a>&nbsp;<a id="html.link" href="#html.link">Standard HTML LINK elements</a></h2><p id="rfc.section.6.2.p.1">LINK elements exist since HTML 2.0. They can be used to embed content-independant links inside the document. Unfortunately, only few user agents support this element. Firefox users may want to check the <a href="https://addons.mozilla.org/firefox/2933/">Link Widgets</a> extension.</p><div id="rfc.table.u.5"><p>The following LINK elements are produced:</p><table class="tt full center" cellpadding="3" cellspacing="0"><thead><tr><th>LINK type</th><th>description</th></tr></thead><tbody><tr><td class="left">alternate<div id="rfc.iref.a.22"></div><div id="rfc.iref.h.3"></div></td><td class="left">for RFCs, a link to the authorative ASCII version on the IETF web site</td></tr><tr><td class="left">appendic<div id="rfc.iref.a.23"></div><div id="rfc.iref.h.4"></div></td><td class="left">pointer to all top-level appendics</td></tr><tr><td class="left">author<div id="rfc.iref.a.24"></div><div id="rfc.iref.h.5"></div></td><td class="left">pointer to "authors" section</td></tr><tr><td class="left">chapter<div id="rfc.iref.c.3"></div><div id="rfc.iref.h.6"></div></td><td class="left">pointer to all top-level sections</td></tr><tr><td class="left">contents<div id="rfc.iref.c.4"></div><div id="rfc.iref.h.7"></div></td><td class="left">pointer to table of contents</td></tr><tr><td class="left">copyright<div id="rfc.iref.c.5"></div><div id="rfc.iref.h.8"></div></td><td class="left">pointer to copyright statement</td></tr><tr><td class="left">index<div id="rfc.iref.i.11"></div><div id="rfc.iref.h.9"></div></td><td class="left">pointer to index</td></tr></tbody></table></div><div id="rfc.figure.u.5"></div><p>The figure below shows how Mozilla Firefox 1.0 displays the Site Navigation Bar for rfc2396.xml.</p><p><img src="rfc2629xslt-fig1.png" alt="&#xA;(LINK elements displayed in Mozilla Firefox for RFC2396.xml)&#xA;" width="509" height="235"></p><h2 id="rfc.section.6.3"><a href="#rfc.section.6.3">6.3</a>&nbsp;Standard HTML metadata</h2><div id="rfc.table.u.6"><p>The following standard HTML META elements are produced:</p><table class="tt full center" cellpadding="3" cellspacing="0"><thead><tr><th>META name</th><th>description</th></tr></thead><tbody><tr><td class="left">generator<div id="rfc.iref.g.2"></div><div id="rfc.iref.h.10"></div></td><td class="left">from XSLT engine version and stylesheet version</td></tr><tr><td class="left">keywords<div id="rfc.iref.k.1"></div><div id="rfc.iref.h.11"></div></td><td class="left">from keyword elements in front section</td></tr></tbody></table></div><h2 id="rfc.section.6.4"><a href="#rfc.section.6.4">6.4</a>&nbsp;<a id="rfc2731.properties" href="#rfc2731.properties">Dublin Core (RFC2731) metadata</a></h2><p id="rfc.section.6.4.p.1">Unless turned off using the "rfc-ext support-rfc2731" processing instruction, the transformation will generate metadata according to <a href="#RFC2731" id="rfc.xref.RFC2731.1"><cite title="Encoding Dublin Core Metadata in HTML">[RFC2731]</cite></a> and <a href="#DC-HTML" id="rfc.xref.DC-HTML.1"><cite title="Expressing Dublin Core metadata using HTML/XHTML meta and link elements">[DC-HTML]</cite></a>.</p><div id="rfc.table.u.7"><p>The following DCMI properties are produced:</p><table class="tt full center" cellpadding="3" cellspacing="0"><thead><tr><th>META name</th><th>description</th></tr></thead><tbody><tr><td class="left">DC.Creator<div id="rfc.iref.c.6"></div><div id="rfc.iref.d.2"></div></td><td class="left">from author information in front section</td></tr><tr><td class="left">DC.Date.Issued<div id="rfc.iref.d.3"></div><div id="rfc.iref.d.4"></div></td><td class="left">from date information in front section</td></tr><tr><td class="left">DC.Description.Abstract<div id="rfc.iref.d.5"></div><div id="rfc.iref.d.6"></div></td><td class="left">from abstract</td></tr><tr><td class="left">DC.Identifier<div id="rfc.iref.i.12"></div><div id="rfc.iref.d.7"></div></td><td class="left">document URN <a href="#RFC2648" id="rfc.xref.RFC2648.1"><cite title="A URN Namespace for IETF Documents">[RFC2648]</cite></a> from "docName" attribute</td></tr><tr><td class="left">DC.isPartOf<div id="rfc.iref.i.13"></div><div id="rfc.iref.d.8"></div></td><td class="left">RFC ISSN (for RFCs)</td></tr><tr><td class="left">DC.Relation.Replaces<div id="rfc.iref.r.22"></div><div id="rfc.iref.d.9"></div></td><td class="left">from "obsoletes" attribute</td></tr></tbody></table></div><h2 id="rfc.section.6.5"><a href="#rfc.section.6.5">6.5</a>&nbsp;<a id="hcard" href="#hcard">Experimental hCard support</a></h2><p id="rfc.section.6.5.p.1">The generated author information is formatted in <a href="http://microformats.org/wiki/hcard">hCard</a> format.</p><hr class="noprint"><h1 id="rfc.section.7" class="np"><a href="#rfc.section.7">7.</a>&nbsp;<a id="output.xhtml" href="#output.xhtml">Transforming to XHTML</a></h1><p id="rfc.section.7.p.1">Transforming to XHTML requires slightly different XSLT output options and is implemented by the derived transformation script <samp>rfc2629toXHTML.xslt</samp>.</p><ul class="empty"><li><b>Note:</b> Microsoft Internet Explorer does <em>not</em> support XHTML. Therefore it usually makes more sense to generate plain old HTML.</li></ul><hr class="noprint"><h1 id="rfc.section.8" class="np"><a href="#rfc.section.8">8.</a>&nbsp;<a id="output.chm" href="#output.chm">Transforming to CHM (Microsoft Compiled Help)</a></h1><p id="rfc.section.8.p.1"><span id="rfc.iref.c.7"></span> <span id="rfc.iref.m.5"></span> To generate a CHM file using Microsoft's HTML Help Compiler (hhc), three files are required in addition to the HTML file. </p><ol><li>hhc - table of contents file (HTML)</li><li>hhk - index file (HTML)</li><li>hhp - project file (plain text)</li></ol><p id="rfc.section.8.p.2">The three files are generated with three specific transformations, each requiring the additional XSLT parameter "basename" to specify the filename prefix.</p><div id="rfc.figure.u.6"></div><p>Example:</p><pre class="text">saxon rfc2616.xml rfc2629toHhp.xslt basename=rfc2616  &gt; rfc2616.hhp
    383383saxon rfc2616.xml rfc2629toHhc.xslt basename=rfc2616  &gt; rfc2616.hhc
    384384saxon rfc2616.xml rfc2629toHhk.xslt basename=rfc2616  &gt; rfc2616.hhk
    385385hhc rfc2616.hhp
    386 </pre><hr class="noprint"><h1 id="rfc.section.9" class="np"><a href="#rfc.section.9">9.</a>&nbsp;<a id="output.pdf" href="#output.pdf">Transforming to PDF</a></h1><h2 id="rfc.section.9.1"><a href="#rfc.section.9.1">9.1</a>&nbsp;<a id="output.pdf.fop" href="#output.pdf.fop">Via XSL-FO</a></h2><p id="rfc.section.9.1.p.1">Transformation to XSL-FO <a href="#XSL-FO" id="rfc.xref.XSL-FO.1"><cite title="Extensible Stylesheet Language (XSL) Version 1.1">[XSL-FO]</cite></a> format is available through <samp>rfc2629toFO.xslt</samp> (which includes <samp>rfc2629.xslt</samp>, so keep both in the same folder).</p><p id="rfc.section.9.1.p.2">Compared to HTML user agents, XSL-FO engines unfortunately either come as open source (for instance, <span id="rfc.iref.a.25"></span>Apache FOP) or feature-complete (for instance, <span id="rfc.iref.a.26"></span> AntennaHouse XSL Formatter), but not both at the same time.</p><p id="rfc.section.9.1.p.3">As Apache FOP needs special workarounds (index generation), and some popular extensions aren't standardized yet, the translation produces a generic output (hopefully) conforming to <a href="#XSL-FO" id="rfc.xref.XSL-FO.2"><cite title="Extensible Stylesheet Language (XSL) Version 1.1">[XSL-FO]</cite></a>. Specific backends (<samp>xsl11toFop.xslt</samp>, <samp>xsl11toXep.xslt</samp>, <samp>xsl11toAn.xslt</samp>) then provide post-processing for the individual processors.</p><div class="note" id="rfc.section.9.1.p.4"> <p> <b>Note:</b> the output is currently targeted at Apache FOP 1.0.</p> </div><h3 id="rfc.section.9.1.1"><a href="#rfc.section.9.1.1">9.1.1</a>&nbsp;Extension feature matrix</h3><div id="rfc.table.u.8"><table class="tt full center" cellpadding="3" cellspacing="0"><thead><tr><th></th><th class="center" style="width: 20%;">PDF anchors</th><th class="center" style="width: 20%;">PDF bookmarks</th><th class="center" style="width: 20%;">PDF document information</th><th class="center" style="width: 20%;">Index cleanup</th></tr></thead><tbody><tr><td class="left"><a href="http://www.w3.org/TR/2003/WD-xsl11-20031217/">XSL 1.1 WD</a></td><td class="center">no, but can be auto-generated from "id" attributes</td><td class="center"><a href="http://www.w3.org/TR/2003/WD-xsl11-20031217/#d0e12873">yes</a></td><td class="center">no, but uses XEP output extensions</td><td class="center"><a href="http://www.w3.org/TR/2003/WD-xsl11-20031217/#d0e12534">yes</a></td></tr><tr><td class="left"><a href="http://www.antennahouse.com/">Antenna House XSL formatter</a></td><td class="center">no</td><td class="center"><a href="http://www.antennahouse.com/XSL20/axf-extension.htm">yes</a> (from XSL 1.1 bookmarks)</td><td class="center"><a href="http://www.antennahouse.com/XSL20/axf-extension.htm">yes</a> (from XEP document info)</td><td class="center"><a href="http://www.antennahouse.com/XSL20/axf-extension.htm">yes</a> (just page duplicate elimination, from XSL 1.1 page index)</td></tr><tr><td class="left"><a href="http://xml.apache.org/fop/">Apache FOP</a></td><td class="center"><a href="http://xml.apache.org/fop/extensions.html#named-destinations">yes</a></td><td class="center"><a href="http://xml.apache.org/fop/extensions.html#bookmarks">yes</a> (from XSL 1.1 bookmarks)</td><td class="center"><a href="http://xmlgraphics.apache.org/fop/0.95/metadata.html#xmp-in-fo">yes</a></td><td class="center">no</td></tr><tr><td class="left"><a href="http://xep.xattic.com/">RenderX XEP</a></td><td class="center">no</td><td class="center"><a href="http://xep.xattic.com/xep/spec.html">yes</a> (from XSL 1.1 bookmarks)</td><td class="center"><a href="http://xep.xattic.com/xep/spec.html">yes</a></td><td class="center"><a href="http://xep.xattic.com/xep/spec.html">yes</a> (from XSL 1.1 page index)</td></tr></tbody></table></div><h3 id="rfc.section.9.1.2"><a href="#rfc.section.9.1.2">9.1.2</a>&nbsp;Example: producing output for Apache FOP</h3><div id="rfc.figure.u.7"></div><p>Example:</p><pre class="text">saxon rfc2616.xml rfc2629toFo.xslt &gt; tmp.fo
     386</pre><hr class="noprint"><h1 id="rfc.section.9" class="np"><a href="#rfc.section.9">9.</a>&nbsp;<a id="output.pdf" href="#output.pdf">Transforming to PDF</a></h1><h2 id="rfc.section.9.1"><a href="#rfc.section.9.1">9.1</a>&nbsp;<a id="output.pdf.fop" href="#output.pdf.fop">Via XSL-FO</a></h2><p id="rfc.section.9.1.p.1">Transformation to XSL-FO <a href="#XSL-FO" id="rfc.xref.XSL-FO.1"><cite title="Extensible Stylesheet Language (XSL) Version 1.1">[XSL-FO]</cite></a> format is available through <samp>rfc2629toFO.xslt</samp> (which includes <samp>rfc2629.xslt</samp>, so keep both in the same folder).</p><p id="rfc.section.9.1.p.2">Compared to HTML user agents, XSL-FO engines unfortunately either come as open source (for instance, <span id="rfc.iref.a.25"></span>Apache FOP) or feature-complete (for instance, <span id="rfc.iref.a.26"></span> AntennaHouse XSL Formatter), but not both at the same time.</p><p id="rfc.section.9.1.p.3">As Apache FOP needs special workarounds (index generation), and some popular extensions aren't standardized yet, the translation produces a generic output (hopefully) conforming to <a href="#XSL-FO" id="rfc.xref.XSL-FO.2"><cite title="Extensible Stylesheet Language (XSL) Version 1.1">[XSL-FO]</cite></a>. Specific backends (<samp>xsl11toFop.xslt</samp>, <samp>xsl11toXep.xslt</samp>, <samp>xsl11toAn.xslt</samp>) then provide post-processing for the individual processors.</p><div class="note" id="rfc.section.9.1.p.4"><p><b>Note:</b> the output is currently targeted at Apache FOP 1.0.</p> </div><h3 id="rfc.section.9.1.1"><a href="#rfc.section.9.1.1">9.1.1</a>&nbsp;Extension feature matrix</h3><div id="rfc.table.u.8"><table class="tt full center" cellpadding="3" cellspacing="0"><thead><tr><th></th><th class="center" style="width: 20%;">PDF anchors</th><th class="center" style="width: 20%;">PDF bookmarks</th><th class="center" style="width: 20%;">PDF document information</th><th class="center" style="width: 20%;">Index cleanup</th></tr></thead><tbody><tr><td class="left"><a href="http://www.w3.org/TR/2003/WD-xsl11-20031217/">XSL 1.1 WD</a></td><td class="center">no, but can be auto-generated from "id" attributes</td><td class="center"><a href="http://www.w3.org/TR/2003/WD-xsl11-20031217/#d0e12873">yes</a></td><td class="center">no, but uses XEP output extensions</td><td class="center"><a href="http://www.w3.org/TR/2003/WD-xsl11-20031217/#d0e12534">yes</a></td></tr><tr><td class="left"><a href="http://www.antennahouse.com/">Antenna House XSL formatter</a></td><td class="center">no</td><td class="center"><a href="http://www.antennahouse.com/XSL20/axf-extension.htm">yes</a> (from XSL 1.1 bookmarks)</td><td class="center"><a href="http://www.antennahouse.com/XSL20/axf-extension.htm">yes</a> (from XEP document info)</td><td class="center"><a href="http://www.antennahouse.com/XSL20/axf-extension.htm">yes</a> (just page duplicate elimination, from XSL 1.1 page index)</td></tr><tr><td class="left"><a href="http://xml.apache.org/fop/">Apache FOP</a></td><td class="center"><a href="http://xml.apache.org/fop/extensions.html#named-destinations">yes</a></td><td class="center"><a href="http://xml.apache.org/fop/extensions.html#bookmarks">yes</a> (from XSL 1.1 bookmarks)</td><td class="center"><a href="http://xmlgraphics.apache.org/fop/0.95/metadata.html#xmp-in-fo">yes</a></td><td class="center">no</td></tr><tr><td class="left"><a href="http://xep.xattic.com/">RenderX XEP</a></td><td class="center">no</td><td class="center"><a href="http://xep.xattic.com/xep/spec.html">yes</a> (from XSL 1.1 bookmarks)</td><td class="center"><a href="http://xep.xattic.com/xep/spec.html">yes</a></td><td class="center"><a href="http://xep.xattic.com/xep/spec.html">yes</a> (from XSL 1.1 page index)</td></tr></tbody></table></div><h3 id="rfc.section.9.1.2"><a href="#rfc.section.9.1.2">9.1.2</a>&nbsp;Example: producing output for Apache FOP</h3><div id="rfc.figure.u.7"></div><p>Example:</p><pre class="text">saxon rfc2616.xml rfc2629toFo.xslt &gt; tmp.fo
    387387saxon tmp.fo xsl11toFop.xslt &gt; rfc2629.fo
    388388</pre><h2 id="rfc.section.9.2"><a href="#rfc.section.9.2">9.2</a>&nbsp;<a id="output.pdf.html" href="#output.pdf.html">Via X(HTML)</a></h2><p id="rfc.section.9.2.p.1">PDF output can also be produced directly from (X)HTML. One simple approach is to rely on the browser's printing function, and to use a printer driver that produces PDF. Depending on the brower's CSS capabilities, the output will behave properly with respect to table breaks etc.</p><p id="rfc.section.9.2.p.2">An alternative is PrinceXML (see &lt;<a href="http://www.princexml.com/">http://www.princexml.com/</a>&gt;), which can produce PDF directly from (X)HTML input, based on the CSS printing information.</p><div id="rfc.figure.u.8"></div><p>For instance, PDF output with text justification turned on can be produced with:</p><pre class="text">saxon input.xml rfc2629toXHTML.xslt xml2rfc-ext-justification=print \
     
    409409   &gt;SHOULD&lt;/bcp14&gt;"&gt;
    410410 &lt;!ENTITY SHOULD-NOT "&lt;bcp14 xmlns='http://purl.org/net/xml2rfc/ext'
    411    &gt;SHOULD NOT&lt;/bcp14&gt;"&gt;]&gt;</pre><div id="rfc.iref.e.5"></div><div id="rfc.iref.b.3"></div><h2 id="rfc.section.11.4"><a href="#rfc.section.11.4">11.4</a>&nbsp;<a id="ext.element.bb" href="#ext.element.bb">&lt;bb&gt; element</a></h2><p id="rfc.section.11.4.p.1">Marking up a string as &lt;bb&gt; indicates that it represents the bottom line of a box drawing, replacing the "+" and "-" characters accordingly.</p><div id="rfc.iref.e.6"></div><div id="rfc.iref.b.4"></div><h2 id="rfc.section.11.5"><a href="#rfc.section.11.5">11.5</a>&nbsp;<a id="ext.element.bc" href="#ext.element.bc">&lt;bc&gt; element</a></h2><p id="rfc.section.11.5.p.1">Marking up a string as &lt;bc&gt; indicates that it represents a center line of a box drawing, replacing the "|" character accordingly.</p><div id="rfc.iref.e.7"></div><div id="rfc.iref.b.5"></div><h2 id="rfc.section.11.6"><a href="#rfc.section.11.6">11.6</a>&nbsp;<a id="ext.element.blockquote" href="#ext.element.blockquote">&lt;blockquote&gt; element</a></h2><p id="rfc.section.11.6.p.1">This element is like the "<a href="http://www.w3.org/TR/html401/struct/text.html#edef-BLOCKQUOTE">blockquote</a>" element in <a href="#HTML" id="rfc.xref.HTML.2"><cite title="HTML 4.01 Specification">[HTML]</cite></a> (note this is a block-level element!). It should contain one or more &lt;t&gt; child elements.</p><div id="rfc.iref.e.8"></div><div id="rfc.iref.b.6"></div><h2 id="rfc.section.11.7"><a href="#rfc.section.11.7">11.7</a>&nbsp;<a id="ext.element.boilerplate" href="#ext.element.boilerplate">&lt;boilerplate&gt; element</a></h2><p id="rfc.section.11.7.p.1">Can be used to include boilerplate (status, copyright, ...) into the front or back section. &lt;section&gt; elements within &lt;x:boilerplate&gt; appear as unnumbered sections in the output.</p><p id="rfc.section.11.7.p.2"> <em>This element currently can not be "down-translated" for use in xml2rfc!</em> </p><div id="rfc.iref.e.9"></div><div id="rfc.iref.b.7"></div><h2 id="rfc.section.11.8"><a href="#rfc.section.11.8">11.8</a>&nbsp;<a id="ext.element.bt" href="#ext.element.bt">&lt;bt&gt; element</a></h2><p id="rfc.section.11.8.p.1">Marking up a string as &lt;bt&gt; indicates that it represents the top line of a box drawing, replacing the "+" and "-" characters accordingly.</p><div id="rfc.iref.e.10"></div><div id="rfc.iref.d.10"></div><h2 id="rfc.section.11.9"><a href="#rfc.section.11.9">11.9</a>&nbsp;<a id="ext.element.dfn" href="#ext.element.dfn">&lt;dfn&gt; element</a></h2><p id="rfc.section.11.9.p.1">This element is like the "<a href="http://www.w3.org/TR/html401/struct/text.html#edef-DFN">dfn</a>" element in <a href="#HTML" id="rfc.xref.HTML.3"><cite title="HTML 4.01 Specification">[HTML]</cite></a>.</p><div id="rfc.iref.e.11"></div><div id="rfc.iref.f.4"></div><h2 id="rfc.section.11.10"><a href="#rfc.section.11.10">11.10</a>&nbsp;<a id="ext.element.feedback" href="#ext.element.feedback">&lt;feedback&gt; element</a></h2><p id="rfc.section.11.10.p.1">This elements allows declaring a feedback link for document reviewers. The template string takes the form of a URI template, such as:</p><div id="rfc.figure.u.11"></div><pre class="text">&lt;x:feedback template="mailto:ietf-http-wg@w3.org?subject={docname},%20%22{section}%22&amp;amp;body=&amp;lt;{ref}&amp;gt;:"/&gt;
    412 </pre><p id="rfc.section.11.10.p.3">where "docname" is substituted by the document name, "section" is substituted by section title (number and name), and "ref" is substituted by a URI pointing to the section being referenced.</p><div id="rfc.iref.e.12"></div><div id="rfc.iref.h.12"></div><h2 id="rfc.section.11.11"><a href="#rfc.section.11.11">11.11</a>&nbsp;<a id="ext.element.h" href="#ext.element.h">&lt;h&gt; element</a></h2><p id="rfc.section.11.11.p.1">This element is like the "<a href="http://www.w3.org/TR/2006/WD-xhtml2-20060726/mod-structural.html#edef_structural_h">h</a>" element in <a href="#XHTML2" id="rfc.xref.XHTML2.1"><cite title="XHTML&#8482; 2.0">[XHTML2]</cite></a>.</p><div id="rfc.iref.e.13"></div><div id="rfc.iref.h.13"></div><h2 id="rfc.section.11.12"><a href="#rfc.section.11.12">11.12</a>&nbsp;<a id="ext.element.highlight" href="#ext.element.highlight">&lt;highlight&gt; element</a></h2><p id="rfc.section.11.12.p.1">Used to highlight text passages, currently only allowed in &lt;artwork&gt;.</p><p id="rfc.section.11.12.p.2"> <b>Note:</b> this is stripped when generating input for xml2rfc, so please use with care.</p><div id="rfc.iref.e.14"></div><div id="rfc.iref.l.2"></div><h2 id="rfc.section.11.13"><a href="#rfc.section.11.13">11.13</a>&nbsp;<a id="ext.element.length-of" href="#ext.element.length-of">&lt;length-of&gt; element</a></h2><p id="rfc.section.11.13.p.1">This element can be used to insert the length of another formatted section (in decimal).</p><div id="rfc.figure.u.12"></div><p>Example: computing the Content-Length header value</p><pre class="text">&lt;artwork&gt;
     411   &gt;SHOULD NOT&lt;/bcp14&gt;"&gt;]&gt;</pre><div id="rfc.iref.e.5"></div><div id="rfc.iref.b.3"></div><h2 id="rfc.section.11.4"><a href="#rfc.section.11.4">11.4</a>&nbsp;<a id="ext.element.bb" href="#ext.element.bb">&lt;bb&gt; element</a></h2><p id="rfc.section.11.4.p.1">Marking up a string as &lt;bb&gt; indicates that it represents the bottom line of a box drawing, replacing the "+" and "-" characters accordingly.</p><div id="rfc.iref.e.6"></div><div id="rfc.iref.b.4"></div><h2 id="rfc.section.11.5"><a href="#rfc.section.11.5">11.5</a>&nbsp;<a id="ext.element.bc" href="#ext.element.bc">&lt;bc&gt; element</a></h2><p id="rfc.section.11.5.p.1">Marking up a string as &lt;bc&gt; indicates that it represents a center line of a box drawing, replacing the "|" character accordingly.</p><div id="rfc.iref.e.7"></div><div id="rfc.iref.b.5"></div><h2 id="rfc.section.11.6"><a href="#rfc.section.11.6">11.6</a>&nbsp;<a id="ext.element.blockquote" href="#ext.element.blockquote">&lt;blockquote&gt; element</a></h2><p id="rfc.section.11.6.p.1">This element is like the "<a href="http://www.w3.org/TR/html401/struct/text.html#edef-BLOCKQUOTE">blockquote</a>" element in <a href="#HTML" id="rfc.xref.HTML.2"><cite title="HTML 4.01 Specification">[HTML]</cite></a> (note this is a block-level element!). It should contain one or more &lt;t&gt; child elements.</p><div id="rfc.iref.e.8"></div><div id="rfc.iref.b.6"></div><h2 id="rfc.section.11.7"><a href="#rfc.section.11.7">11.7</a>&nbsp;<a id="ext.element.boilerplate" href="#ext.element.boilerplate">&lt;boilerplate&gt; element</a></h2><p id="rfc.section.11.7.p.1">Can be used to include boilerplate (status, copyright, ...) into the front or back section. &lt;section&gt; elements within &lt;x:boilerplate&gt; appear as unnumbered sections in the output.</p><p id="rfc.section.11.7.p.2"><em>This element currently can not be "down-translated" for use in xml2rfc!</em> </p><div id="rfc.iref.e.9"></div><div id="rfc.iref.b.7"></div><h2 id="rfc.section.11.8"><a href="#rfc.section.11.8">11.8</a>&nbsp;<a id="ext.element.bt" href="#ext.element.bt">&lt;bt&gt; element</a></h2><p id="rfc.section.11.8.p.1">Marking up a string as &lt;bt&gt; indicates that it represents the top line of a box drawing, replacing the "+" and "-" characters accordingly.</p><div id="rfc.iref.e.10"></div><div id="rfc.iref.d.10"></div><h2 id="rfc.section.11.9"><a href="#rfc.section.11.9">11.9</a>&nbsp;<a id="ext.element.dfn" href="#ext.element.dfn">&lt;dfn&gt; element</a></h2><p id="rfc.section.11.9.p.1">This element is like the "<a href="http://www.w3.org/TR/html401/struct/text.html#edef-DFN">dfn</a>" element in <a href="#HTML" id="rfc.xref.HTML.3"><cite title="HTML 4.01 Specification">[HTML]</cite></a>.</p><div id="rfc.iref.e.11"></div><div id="rfc.iref.f.4"></div><h2 id="rfc.section.11.10"><a href="#rfc.section.11.10">11.10</a>&nbsp;<a id="ext.element.feedback" href="#ext.element.feedback">&lt;feedback&gt; element</a></h2><p id="rfc.section.11.10.p.1">This elements allows declaring a feedback link for document reviewers. The template string takes the form of a URI template, such as:</p><div id="rfc.figure.u.11"></div><pre class="text">&lt;x:feedback template="mailto:ietf-http-wg@w3.org?subject={docname},%20%22{section}%22&amp;amp;body=&amp;lt;{ref}&amp;gt;:"/&gt;
     412</pre><p id="rfc.section.11.10.p.3">where "docname" is substituted by the document name, "section" is substituted by section title (number and name), and "ref" is substituted by a URI pointing to the section being referenced.</p><div id="rfc.iref.e.12"></div><div id="rfc.iref.h.12"></div><h2 id="rfc.section.11.11"><a href="#rfc.section.11.11">11.11</a>&nbsp;<a id="ext.element.h" href="#ext.element.h">&lt;h&gt; element</a></h2><p id="rfc.section.11.11.p.1">This element is like the "<a href="http://www.w3.org/TR/2006/WD-xhtml2-20060726/mod-structural.html#edef_structural_h">h</a>" element in <a href="#XHTML2" id="rfc.xref.XHTML2.1"><cite title="XHTML&#8482; 2.0">[XHTML2]</cite></a>.</p><div id="rfc.iref.e.13"></div><div id="rfc.iref.h.13"></div><h2 id="rfc.section.11.12"><a href="#rfc.section.11.12">11.12</a>&nbsp;<a id="ext.element.highlight" href="#ext.element.highlight">&lt;highlight&gt; element</a></h2><p id="rfc.section.11.12.p.1">Used to highlight text passages, currently only allowed in &lt;artwork&gt;.</p><p id="rfc.section.11.12.p.2"><b>Note:</b> this is stripped when generating input for xml2rfc, so please use with care.</p><div id="rfc.iref.e.14"></div><div id="rfc.iref.l.2"></div><h2 id="rfc.section.11.13"><a href="#rfc.section.11.13">11.13</a>&nbsp;<a id="ext.element.length-of" href="#ext.element.length-of">&lt;length-of&gt; element</a></h2><p id="rfc.section.11.13.p.1">This element can be used to insert the length of another formatted section (in decimal).</p><div id="rfc.figure.u.12"></div><p>Example: computing the Content-Length header value</p><pre class="text">&lt;artwork&gt;
    413413...
    414414Content-Length: &lt;x:length-of target="req"/&gt;
     
    438438        &lt;x:source href="rfc2616.xml"/&gt;
    439439        ...
    440     </pre><div id="rfc.iref.e.23"></div><div id="rfc.iref.s.13"></div><h2 id="rfc.section.11.22"><a href="#rfc.section.11.22">11.22</a>&nbsp;<a id="ext.element.sup" href="#ext.element.sup">&lt;sup&gt; element</a></h2><p id="rfc.section.11.22.p.1">This element is like the "<a href="http://www.w3.org/TR/html401/struct/text.html#edef-SUP">sup</a>" element in <a href="#HTML" id="rfc.xref.HTML.5"><cite title="HTML 4.01 Specification">[HTML]</cite></a>.</p><p id="rfc.section.11.22.p.2">Note: the down conversion to RFC2629 format replaces "x<sup>y</sup>" by "x^y".</p><h2 id="rfc.section.11.23"><a href="#rfc.section.11.23">11.23</a>&nbsp;<a id="ext-rfc2629.artwork" href="#ext-rfc2629.artwork">Extensions to Xml2rfc &lt;artwork&gt; element</a></h2><p id="rfc.section.11.23.p.1">Sometimes, artwork occurs inside lists. To get it indent properly in xml2rfc's text output, it needs to be indented in the source. This is sub-optimal, as this whitespace will also appear in the HTML output, where it's already indented due to HTML's semantics.</p><p id="rfc.section.11.23.p.2">As a workaround, a "x:indent-with" attribute can be specified, containing a string that will be prepended to each line when <samp>clean-for-DTD.xslt</samp> is run (see <a href="#clean-for-dtd" title="Down-converting to RFC2629bis DTD">Section&nbsp;12.4</a>).</p><h2 id="rfc.section.11.24"><a href="#rfc.section.11.24">11.24</a>&nbsp;<a id="ext-rfc2629.iref" href="#ext-rfc2629.iref">Extensions to Xml2rfc &lt;iref&gt; element</a></h2><p id="rfc.section.11.24.p.1">The extension attribute below is allowed on the standard &lt;iref&gt; element: </p><ul><li>x:for-anchor specifies that the &lt;iref&gt; will also be automatically inserted whenever the specified anchor is cross-referenced -- this may save entering lots of &lt;iref&gt; instances. As a special case, a value of "" (empty string) refers to the anchor attribute of the closest ancestor.</li></ul><h2 id="rfc.section.11.25"><a href="#rfc.section.11.25">11.25</a>&nbsp;<a id="ext-rfc2629.list" href="#ext-rfc2629.list">Extensions to Xml2rfc &lt;list&gt; element</a></h2><p id="rfc.section.11.25.p.1">The extension attribute below is allowed on the standard &lt;list&gt; element: </p><ul><li>x:indent specifies the amount of indentation for list items in hanging lists. This can be useful when the output format, such as XSL-FO, does not support automatical formatting. The value takes an XSL-FO width, such as "5em". The default is <em>length of longest label in characters</em> times <em>0.8em</em>.</li></ul><p id="rfc.section.11.25.p.2">Also, the &lt;list&gt; element can take &lt;x:<a href="#ext.element.lt" class="smpl">lt</a>&gt; child elements instead of &lt;t&gt;, allowing to insert multiple paragraphs into a single list item.</p><h2 id="rfc.section.11.26"><a href="#rfc.section.11.26">11.26</a>&nbsp;<a id="ext-rfc2629.rfc" href="#ext-rfc2629.rfc">Extensions to Xml2rfc &lt;rfc&gt; element</a></h2><p id="rfc.section.11.26.p.1">The extension attributes below are allowed on the standard &lt;rfc&gt; element: </p><ul><li>grddl:transformation can be used to reference a GRDDL transform.</li><li>x:maturity-level can be used to specify the IETF Standards Track Maturity Level of "proposed", "draft" or "internet" (see <a href="http://tools.ietf.org/html/rfc2026#section-4.1">Section 4.1</a> of <a href="#RFC2026" id="rfc.xref.RFC2026.1"><cite title="The Internet Standards Process -- Revision 3">[RFC2026]</cite></a>).</li></ul><h2 id="rfc.section.11.27"><a href="#rfc.section.11.27">11.27</a>&nbsp;<a id="ext-rfc2629.section" href="#ext-rfc2629.section">Extensions to Xml2rfc &lt;section&gt; element</a></h2><p id="rfc.section.11.27.p.1">The extension attribute below is allowed on the standard &lt;list&gt; element: </p><ul><li>x:fixed-section-number can be used to specify a fixed section number. This can be useful when formatting historic documents that used a different numbering style.</li></ul><h2 id="rfc.section.11.28"><a href="#rfc.section.11.28">11.28</a>&nbsp;<a id="ext-rfc2629.xref" href="#ext-rfc2629.xref">Extensions to Xml2rfc &lt;xref&gt; element</a></h2><p id="rfc.section.11.28.p.1">Three extension attributes are allowed on the standard &lt;xref&gt; element: </p><ol><li>x:sec can be specified to point to a specific section of the referenced document,</li><li>x:rel may specify a relative reference to use when linking into the referenced document (if linking by section number is not available),</li><li>x:fmt defines the text format to be used.</li></ol><p id="rfc.section.11.28.p.2">The following formats are defined for the x:fmt attribute: </p><dl><dt>, (Comma)</dt><dd>[<em>reference</em>], Section <em>sec</em> </dd><dt>()</dt><dd>[<em>reference</em>] (Section <em>sec</em>)</dd><dt>anchor</dt><dd>Like the default format, but without brackets.</dd><dt>of</dt><dd>Section <em>sec</em> of [<em>reference</em>]</dd><dt>number</dt><dd> <em>sec</em> </dd><dt>none</dt><dd>No output (can be used to have xrefs to references without having them rendered as such)</dd><dt>sec</dt><dd>Section <em>sec</em> </dd></dl><p id="rfc.section.11.28.p.3">These extensions are currently only supported for &lt;xref&gt; elements without child nodes.</p><p id="rfc.section.11.28.p.4">If the processor knows how to reference the target section, it will generate a link directly to the target section, such as in <a href="#RFC2119" id="rfc.xref.RFC2119.2"><cite title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</cite></a>, <a href="http://tools.ietf.org/html/rfc2119#section-5">Section 5</a>.</p><hr class="noprint"><h1 id="rfc.section.12" class="np"><a href="#rfc.section.12">12.</a>&nbsp;<a id="utilities" href="#utilities">Utilities</a></h1><h2 id="rfc.section.12.1"><a href="#rfc.section.12.1">12.1</a>&nbsp;<a id="checking-references" href="#checking-references">Checking References</a></h2><p id="rfc.section.12.1.p.1"> <samp>check-references.xslt</samp> can be used to check all references to RFC- and ID-series IETF publications and to W3C publications (note this script requires local copies of &lt;<a href="ftp://ftp.isi.edu/in-notes/rfc-index.xml">ftp://ftp.isi.edu/in-notes/rfc-index.xml</a>&gt; and &lt;<a href="http://www.w3.org/2002/01/tr-automation/tr.rdf">http://www.w3.org/2002/01/tr-automation/tr.rdf</a>&gt; and will use the XML status information provided at &lt;<a href="http://tools.ietf.org/">http://tools.ietf.org/</a>&gt;).</p><p id="rfc.section.12.1.p.2">If the document is supposed to be published on the IETF standards track, the desired level can be specified using the parameter <samp>intended-level</samp> as 'proposed', 'draft' or 'internet'. Alternatively, it can be specified inside the document using the attribute x:maturity-level on the &lt;rfc&gt; element (see <a href="#ext-rfc2629.rfc" title="Extensions to Xml2rfc <rfc&gt; element">Section&nbsp;11.26</a>).</p><p id="rfc.section.12.1.p.3"> <b>Note:</b> Downward references should be annotated using the &lt;annotate&gt; element, containing an &lt;xref&gt; to <a href="#BCP97" id="rfc.xref.BCP97.1"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>.</p><p id="rfc.section.12.1.p.4">When an XSLT 2.0 processor is used, links in the document can be checked as well using the <samp>link-check</samp> parameter ('yes' or 'no'). Note that this only works for http links to documents of type text/*.</p><div id="rfc.figure.u.19"></div><p>For instance, as of 2008-07-12, the script produces for &lt;<a href="http://greenbytes.de/tech/webdav/rfc2518.xml">http://greenbytes.de/tech/webdav/rfc2518.xml</a>&gt;:</p><pre class="text">&gt; saxon rfc2518.xml check-references.xslt intended-status=PROPOSED \
     440    </pre><div id="rfc.iref.e.23"></div><div id="rfc.iref.s.13"></div><h2 id="rfc.section.11.22"><a href="#rfc.section.11.22">11.22</a>&nbsp;<a id="ext.element.sup" href="#ext.element.sup">&lt;sup&gt; element</a></h2><p id="rfc.section.11.22.p.1">This element is like the "<a href="http://www.w3.org/TR/html401/struct/text.html#edef-SUP">sup</a>" element in <a href="#HTML" id="rfc.xref.HTML.5"><cite title="HTML 4.01 Specification">[HTML]</cite></a>.</p><p id="rfc.section.11.22.p.2">Note: the down conversion to RFC2629 format replaces "x<sup>y</sup>" by "x^y".</p><h2 id="rfc.section.11.23"><a href="#rfc.section.11.23">11.23</a>&nbsp;<a id="ext-rfc2629.artwork" href="#ext-rfc2629.artwork">Extensions to Xml2rfc &lt;artwork&gt; element</a></h2><p id="rfc.section.11.23.p.1">Sometimes, artwork occurs inside lists. To get it indent properly in xml2rfc's text output, it needs to be indented in the source. This is sub-optimal, as this whitespace will also appear in the HTML output, where it's already indented due to HTML's semantics.</p><p id="rfc.section.11.23.p.2">As a workaround, a "x:indent-with" attribute can be specified, containing a string that will be prepended to each line when <samp>clean-for-DTD.xslt</samp> is run (see <a href="#clean-for-dtd" title="Down-converting to RFC2629bis DTD">Section&nbsp;12.4</a>).</p><h2 id="rfc.section.11.24"><a href="#rfc.section.11.24">11.24</a>&nbsp;<a id="ext-rfc2629.iref" href="#ext-rfc2629.iref">Extensions to Xml2rfc &lt;iref&gt; element</a></h2><p id="rfc.section.11.24.p.1">The extension attribute below is allowed on the standard &lt;iref&gt; element: </p><ul><li>x:for-anchor specifies that the &lt;iref&gt; will also be automatically inserted whenever the specified anchor is cross-referenced -- this may save entering lots of &lt;iref&gt; instances. As a special case, a value of "" (empty string) refers to the anchor attribute of the closest ancestor.</li></ul><h2 id="rfc.section.11.25"><a href="#rfc.section.11.25">11.25</a>&nbsp;<a id="ext-rfc2629.list" href="#ext-rfc2629.list">Extensions to Xml2rfc &lt;list&gt; element</a></h2><p id="rfc.section.11.25.p.1">The extension attribute below is allowed on the standard &lt;list&gt; element: </p><ul><li>x:indent specifies the amount of indentation for list items in hanging lists. This can be useful when the output format, such as XSL-FO, does not support automatical formatting. The value takes an XSL-FO width, such as "5em". The default is <em>length of longest label in characters</em> times <em>0.8em</em>.</li></ul><p id="rfc.section.11.25.p.2">Also, the &lt;list&gt; element can take &lt;x:<a href="#ext.element.lt" class="smpl">lt</a>&gt; child elements instead of &lt;t&gt;, allowing to insert multiple paragraphs into a single list item.</p><h2 id="rfc.section.11.26"><a href="#rfc.section.11.26">11.26</a>&nbsp;<a id="ext-rfc2629.rfc" href="#ext-rfc2629.rfc">Extensions to Xml2rfc &lt;rfc&gt; element</a></h2><p id="rfc.section.11.26.p.1">The extension attributes below are allowed on the standard &lt;rfc&gt; element: </p><ul><li>grddl:transformation can be used to reference a GRDDL transform.</li><li>x:maturity-level can be used to specify the IETF Standards Track Maturity Level of "proposed", "draft" or "internet" (see <a href="http://tools.ietf.org/html/rfc2026#section-4.1">Section 4.1</a> of <a href="#RFC2026" id="rfc.xref.RFC2026.1"><cite title="The Internet Standards Process -- Revision 3">[RFC2026]</cite></a>).</li></ul><h2 id="rfc.section.11.27"><a href="#rfc.section.11.27">11.27</a>&nbsp;<a id="ext-rfc2629.section" href="#ext-rfc2629.section">Extensions to Xml2rfc &lt;section&gt; element</a></h2><p id="rfc.section.11.27.p.1">The extension attribute below is allowed on the standard &lt;list&gt; element: </p><ul><li>x:fixed-section-number can be used to specify a fixed section number. This can be useful when formatting historic documents that used a different numbering style.</li></ul><h2 id="rfc.section.11.28"><a href="#rfc.section.11.28">11.28</a>&nbsp;<a id="ext-rfc2629.xref" href="#ext-rfc2629.xref">Extensions to Xml2rfc &lt;xref&gt; element</a></h2><p id="rfc.section.11.28.p.1">Three extension attributes are allowed on the standard &lt;xref&gt; element: </p><ol><li>x:sec can be specified to point to a specific section of the referenced document,</li><li>x:rel may specify a relative reference to use when linking into the referenced document (if linking by section number is not available),</li><li>x:fmt defines the text format to be used.</li></ol><p id="rfc.section.11.28.p.2">The following formats are defined for the x:fmt attribute: </p><dl><dt>, (Comma)</dt><dd>[<em>reference</em>], Section <em>sec</em> </dd><dt>()</dt><dd>[<em>reference</em>] (Section <em>sec</em>)</dd><dt>anchor</dt><dd>Like the default format, but without brackets.</dd><dt>of</dt><dd>Section <em>sec</em> of [<em>reference</em>]</dd><dt>number</dt><dd><em>sec</em> </dd><dt>none</dt><dd>No output (can be used to have xrefs to references without having them rendered as such)</dd><dt>sec</dt><dd>Section <em>sec</em> </dd></dl><p id="rfc.section.11.28.p.3">These extensions are currently only supported for &lt;xref&gt; elements without child nodes.</p><p id="rfc.section.11.28.p.4">If the processor knows how to reference the target section, it will generate a link directly to the target section, such as in <a href="#RFC2119" id="rfc.xref.RFC2119.2"><cite title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</cite></a>, <a href="http://tools.ietf.org/html/rfc2119#section-5">Section 5</a>.</p><hr class="noprint"><h1 id="rfc.section.12" class="np"><a href="#rfc.section.12">12.</a>&nbsp;<a id="utilities" href="#utilities">Utilities</a></h1><h2 id="rfc.section.12.1"><a href="#rfc.section.12.1">12.1</a>&nbsp;<a id="checking-references" href="#checking-references">Checking References</a></h2><p id="rfc.section.12.1.p.1"><samp>check-references.xslt</samp> can be used to check all references to RFC- and ID-series IETF publications and to W3C publications (note this script requires local copies of &lt;<a href="ftp://ftp.isi.edu/in-notes/rfc-index.xml">ftp://ftp.isi.edu/in-notes/rfc-index.xml</a>&gt; and &lt;<a href="http://www.w3.org/2002/01/tr-automation/tr.rdf">http://www.w3.org/2002/01/tr-automation/tr.rdf</a>&gt; and will use the XML status information provided at &lt;<a href="http://tools.ietf.org/">http://tools.ietf.org/</a>&gt;).</p><p id="rfc.section.12.1.p.2">If the document is supposed to be published on the IETF standards track, the desired level can be specified using the parameter <samp>intended-level</samp> as 'proposed', 'draft' or 'internet'. Alternatively, it can be specified inside the document using the attribute x:maturity-level on the &lt;rfc&gt; element (see <a href="#ext-rfc2629.rfc" title="Extensions to Xml2rfc <rfc&gt; element">Section&nbsp;11.26</a>).</p><p id="rfc.section.12.1.p.3"><b>Note:</b> Downward references should be annotated using the &lt;annotate&gt; element, containing an &lt;xref&gt; to <a href="#BCP97" id="rfc.xref.BCP97.1"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>.</p><p id="rfc.section.12.1.p.4">When an XSLT 2.0 processor is used, links in the document can be checked as well using the <samp>link-check</samp> parameter ('yes' or 'no'). Note that this only works for http links to documents of type text/*.</p><div id="rfc.figure.u.19"></div><p>For instance, as of 2008-07-12, the script produces for &lt;<a href="http://greenbytes.de/tech/webdav/rfc2518.xml">http://greenbytes.de/tech/webdav/rfc2518.xml</a>&gt;:</p><pre class="text">&gt; saxon rfc2518.xml check-references.xslt intended-status=PROPOSED \
    441441  link-check=yes
    442442
     
    472472&lt;http://www.dlib.org/dlib/july96/lagoze/07lagoze.html&gt;: ok
    473473&lt;http://www.w3.org/pub/WWW/TR/REC-PICS-labels-961031.html&gt;: ok
    474 </pre><p id="rfc.section.12.1.p.6">Recognized formats in the &lt;seriesInfo&gt; element are: </p><ul><li>for RFCs, the name attribute must be "RFC", and the value attribute must be the number of the RFC,</li><li>for Internet Drafs, the name attribute must be "ID" or "Internet-Draft", and the value attribute must be the file name of the draft (including the two-digit running number, but excluding a file extension),</li><li>for W3C documents, the name attribute must be "W3C", must start with "W3C&nbsp;", or must start with "World Wide Web Consortium&nbsp;", and the value attribute must be the "shorthand" name of the specification, such as "REC-xml-19980210".</li></ul><div class="note" id="rfc.section.12.1.p.7"> <p> <b>Note:</b> this stylesheet will need network access to check links and status of Internet Drafts. When running a Java-based XSLT engine, you may have to supply Java system properties specifying the HTTP proxy to be used, such as "-Dhttp.proxyHost=hostname -Dhttp.proxyPort=80".</p> </div><h2 id="rfc.section.12.2"><a href="#rfc.section.12.2">12.2</a>&nbsp;Generating Graphs from References</h2><p id="rfc.section.12.2.p.1"> <samp>gen-reference-graph.xslt</samp> generates a graph of RFC dependencies, using the same base data as in <samp>check-references.xslt</samp> (see <a href="#checking-references" title="Checking References">Section&nbsp;12.1</a>). Its output is a "dot" file, to be processed by GraphViz (see &lt;<a href="http://www.graphviz.org/">http://www.graphviz.org/</a>&gt;).</p><div id="rfc.figure.u.20"></div><p>The picture below shows the RFC dependencies in RFC2629.</p><p><img src="rfc2629xslt-fig2.png" alt="&#xA;(PNG output obtained from GraphViz)&#xA;"></p><h2 id="rfc.section.12.3"><a href="#rfc.section.12.3">12.3</a>&nbsp;Producing reference entries for books</h2><p id="rfc.section.12.3.p.1"> <samp>amazon-asin.xslt</samp> uses the Amazon web services to generate a &lt;reference&gt; element for a given ASIN (ISBN).</p><div id="rfc.figure.u.21"></div><p>For instance:</p><pre class="text">&lt;?xml version="1.0" encoding="utf-8"?&gt;
     474</pre><p id="rfc.section.12.1.p.6">Recognized formats in the &lt;seriesInfo&gt; element are: </p><ul><li>for RFCs, the name attribute must be "RFC", and the value attribute must be the number of the RFC,</li><li>for Internet Drafs, the name attribute must be "ID" or "Internet-Draft", and the value attribute must be the file name of the draft (including the two-digit running number, but excluding a file extension),</li><li>for W3C documents, the name attribute must be "W3C", must start with "W3C&nbsp;", or must start with "World Wide Web Consortium&nbsp;", and the value attribute must be the "shorthand" name of the specification, such as "REC-xml-19980210".</li></ul><div class="note" id="rfc.section.12.1.p.7"><p><b>Note:</b> this stylesheet will need network access to check links and status of Internet Drafts. When running a Java-based XSLT engine, you may have to supply Java system properties specifying the HTTP proxy to be used, such as "-Dhttp.proxyHost=hostname -Dhttp.proxyPort=80".</p> </div><h2 id="rfc.section.12.2"><a href="#rfc.section.12.2">12.2</a>&nbsp;Generating Graphs from References</h2><p id="rfc.section.12.2.p.1"><samp>gen-reference-graph.xslt</samp> generates a graph of RFC dependencies, using the same base data as in <samp>check-references.xslt</samp> (see <a href="#checking-references" title="Checking References">Section&nbsp;12.1</a>). Its output is a "dot" file, to be processed by GraphViz (see &lt;<a href="http://www.graphviz.org/">http://www.graphviz.org/</a>&gt;).</p><div id="rfc.figure.u.20"></div><p>The picture below shows the RFC dependencies in RFC2629.</p><p><img src="rfc2629xslt-fig2.png" alt="&#xA;(PNG output obtained from GraphViz)&#xA;"></p><h2 id="rfc.section.12.3"><a href="#rfc.section.12.3">12.3</a>&nbsp;Producing reference entries for books</h2><p id="rfc.section.12.3.p.1"><samp>amazon-asin.xslt</samp> uses the Amazon web services to generate a &lt;reference&gt; element for a given ASIN (ISBN).</p><div id="rfc.figure.u.21"></div><p>For instance:</p><pre class="text">&lt;?xml version="1.0" encoding="utf-8"?&gt;
    475475&lt;references&gt;
    476476 &lt;reference target="urn:isbn:0134516591"&gt;
     
    491491 &lt;/reference&gt;
    492492&lt;/references&gt;
    493 </pre><p id="rfc.section.12.3.p.3">Note that the resulting XML usually requires checking, in this case Amazon's database is playing tricks with Marshall's name...</p><h2 id="rfc.section.12.4"><a href="#rfc.section.12.4">12.4</a>&nbsp;<a id="clean-for-dtd" href="#clean-for-dtd">Down-converting to RFC2629bis DTD</a></h2><p id="rfc.section.12.4.p.1"> <samp>clean-for-DTD.xslt</samp> can be used to down-convert some extensions to a format that is supported by the base xml2rfc distribution. Note that these extensions are experimental (feedback appreciated).</p><p id="rfc.section.12.4.p.2">The following mappings are done: </p><ul><li>&lt;iref&gt; elements inside &lt;artwork&gt; elements are moved in front of the enclosing &lt;figure&gt; element.</li><li>&lt;xref&gt; elements inside &lt;artwork&gt; are expanded just like in regular text (that is, the markup is stripped, but the element is replaced by the applicable replacement text).</li><li>&lt;x:<a href="#ext.element.anchor-alias" class="smpl">anchor-alias</a>&gt; elements get stripped.</li><li>&lt;x:<a href="#ext.element.bcp14" class="smpl">bcp14</a>&gt; elements get stripped.</li><li>&lt;x:<a href="#ext.element.bb" class="smpl">bb</a>&gt;, &lt;x:<a href="#ext.element.bc" class="smpl">bc</a>&gt; and &lt;x:<a href="#ext.element.bt" class="smpl">bt</a>&gt; elements get stripped.</li><li>&lt;x:<a href="#ext.element.blockquote" class="smpl">blockquote</a>&gt; elements get converted to indented text (through a &lt;list&gt; element).</li><li>&lt;x:<a href="#ext.element.dfn" class="smpl">dfn</a>&gt; elements get stripped.</li><li>&lt;x:<a href="#ext.element.h" class="smpl">h</a>&gt; elements get stripped.</li><li>&lt;x:<a href="#ext.element.link" class="smpl">link</a>&gt; elements get stripped.</li><li>&lt;x:<a href="#ext.element.lt" class="smpl">lt</a>&gt; elements get collapsed into a single &lt;lt&gt; element with added &lt;vspace&gt; added to simulate paragraph breaks.</li><li>&lt;x:<a href="#ext.element.note" class="smpl">note</a>&gt; elements get converted to indented text (through a &lt;list&gt; element).</li><li>&lt;x:<a href="#ext.element.q" class="smpl">q</a>&gt; elements get stripped, with apostrophes added around the text.</li><li>&lt;x:<a href="#ext.element.prose" class="smpl">prose</a>&gt; elements are transformed into &lt;seriesInfo&gt; elements (which is an abuse of the element and only a workaround until xml2rfc gets a matching extension).</li><li>&lt;x:<a href="#ext.element.ref" class="smpl">ref</a>&gt; elements get replaced by &lt;xref&gt; elements, targetting either the anchor or another anchor with matching &lt;x:<a href="#ext.element.anchor-alias" class="smpl">anchor-alias</a>&gt; child element.</li></ul><h2 id="rfc.section.12.5"><a href="#rfc.section.12.5">12.5</a>&nbsp;<a id="extract-artwork" href="#extract-artwork">Extracting artwork</a></h2><p id="rfc.section.12.5.p.1">With <samp>extract-artwork.xslt</samp>, artwork elements named through the "name" attribute can be extracted. This can be used to automatically check their syntax (for instance, when ABNFs appear within a figure element).</p><div id="rfc.figure.u.22"></div><p>For instance:</p><pre class="text">saxon rfc3986.xml extract-artwork.xslt name=uri.abnf
     493</pre><p id="rfc.section.12.3.p.3">Note that the resulting XML usually requires checking, in this case Amazon's database is playing tricks with Marshall's name...</p><h2 id="rfc.section.12.4"><a href="#rfc.section.12.4">12.4</a>&nbsp;<a id="clean-for-dtd" href="#clean-for-dtd">Down-converting to RFC2629bis DTD</a></h2><p id="rfc.section.12.4.p.1"><samp>clean-for-DTD.xslt</samp> can be used to down-convert some extensions to a format that is supported by the base xml2rfc distribution. Note that these extensions are experimental (feedback appreciated).</p><p id="rfc.section.12.4.p.2">The following mappings are done: </p><ul><li>&lt;iref&gt; elements inside &lt;artwork&gt; elements are moved in front of the enclosing &lt;figure&gt; element.</li><li>&lt;xref&gt; elements inside &lt;artwork&gt; are expanded just like in regular text (that is, the markup is stripped, but the element is replaced by the applicable replacement text).</li><li>&lt;x:<a href="#ext.element.anchor-alias" class="smpl">anchor-alias</a>&gt; elements get stripped.</li><li>&lt;x:<a href="#ext.element.bcp14" class="smpl">bcp14</a>&gt; elements get stripped.</li><li>&lt;x:<a href="#ext.element.bb" class="smpl">bb</a>&gt;, &lt;x:<a href="#ext.element.bc" class="smpl">bc</a>&gt; and &lt;x:<a href="#ext.element.bt" class="smpl">bt</a>&gt; elements get stripped.</li><li>&lt;x:<a href="#ext.element.blockquote" class="smpl">blockquote</a>&gt; elements get converted to indented text (through a &lt;list&gt; element).</li><li>&lt;x:<a href="#ext.element.dfn" class="smpl">dfn</a>&gt; elements get stripped.</li><li>&lt;x:<a href="#ext.element.h" class="smpl">h</a>&gt; elements get stripped.</li><li>&lt;x:<a href="#ext.element.link" class="smpl">link</a>&gt; elements get stripped.</li><li>&lt;x:<a href="#ext.element.lt" class="smpl">lt</a>&gt; elements get collapsed into a single &lt;lt&gt; element with added &lt;vspace&gt; added to simulate paragraph breaks.</li><li>&lt;x:<a href="#ext.element.note" class="smpl">note</a>&gt; elements get converted to indented text (through a &lt;list&gt; element).</li><li>&lt;x:<a href="#ext.element.q" class="smpl">q</a>&gt; elements get stripped, with apostrophes added around the text.</li><li>&lt;x:<a href="#ext.element.prose" class="smpl">prose</a>&gt; elements are transformed into &lt;seriesInfo&gt; elements (which is an abuse of the element and only a workaround until xml2rfc gets a matching extension).</li><li>&lt;x:<a href="#ext.element.ref" class="smpl">ref</a>&gt; elements get replaced by &lt;xref&gt; elements, targetting either the anchor or another anchor with matching &lt;x:<a href="#ext.element.anchor-alias" class="smpl">anchor-alias</a>&gt; child element.</li></ul><h2 id="rfc.section.12.5"><a href="#rfc.section.12.5">12.5</a>&nbsp;<a id="extract-artwork" href="#extract-artwork">Extracting artwork</a></h2><p id="rfc.section.12.5.p.1">With <samp>extract-artwork.xslt</samp>, artwork elements named through the "name" attribute can be extracted. This can be used to automatically check their syntax (for instance, when ABNFs appear within a figure element).</p><div id="rfc.figure.u.22"></div><p>For instance:</p><pre class="text">saxon rfc3986.xml extract-artwork.xslt name=uri.abnf
    494494</pre><p id="rfc.section.12.5.p.3">In addition, artwork of a specific type can be extracted, such as with:</p><div id="rfc.figure.u.23"></div><pre class="text">saxon rfc3986.xml extract-artwork.xslt type=abnf
    495495</pre><p id="rfc.section.12.5.p.5">When extracting by type, artwork elements with a specified name can be excluded; this can be handy when the document uses some kind of schema language, and an appendix contains the collected schema, repeating definitions from earlier on. Example:</p><div id="rfc.figure.u.24"></div><pre class="text">saxon rfc3986.xml extract-artwork.xslt type=abnf except-name=clschm
    496 </pre><h2 id="rfc.section.12.6"><a href="#rfc.section.12.6">12.6</a>&nbsp;<a id="grddl" href="#grddl">GRRDL</a></h2><p id="rfc.section.12.6.p.1"> <samp>rfc2629grddl.xslt</samp> extracts RDF information. This is experimental work-in-progress. See &lt;<a href="http://www.w3.org/TR/grddl/">http://www.w3.org/TR/grddl/</a>&gt; for more information.</p><h1 class="np" id="rfc.references"><a href="#rfc.section.13" id="rfc.section.13">13.</a> Informative References</h1><table><tr><td class="reference"><b id="BCP97">[BCP97]</b></td><td class="top"><a href="mailto:klensin+ietf@jck.com">Klensin, J.</a> and <a href="mailto:hartmans-ietf@mit.edu" title="MIT">S. Hartman</a>, &#8220;<a href="http://tools.ietf.org/html/rfc4897">Handling Normative References to Standards-Track Documents</a>&#8221;, BCP&nbsp;97, RFC&nbsp;4897, June&nbsp;2007.</td></tr><tr><td class="reference"><b id="DC-HTML">[DC-HTML]</b></td><td class="top"><a href="mailto:pete.johnston@eduserv.org.uk" title="Eduserv Foundation">Johnston, P.</a> and <a href="mailto:andy.powell@eduserv.org.uk" title="Eduserv Foundation">A. Powell</a>, &#8220;<a href="http://dublincore.org/documents/2008/08/04/dc-html/">Expressing Dublin Core metadata using HTML/XHTML meta and link elements</a>&#8221;, Dublin Core Metadata Initiative, August&nbsp;2008, &lt;<a href="http://dublincore.org/documents/2008/08/04/dc-html/">http://dublincore.org/documents/2008/08/04/dc-html/</a>&gt;.</td></tr><tr><td class="reference"><b id="HTML">[HTML]</b></td><td class="top"><a href="mailto:dsr@w3.org" title="W3C">Raggett, D.</a>, Hors, A., and I. Jacobs, &#8220;<a href="http://www.w3.org/TR/html401/">HTML 4.01 Specification</a>&#8221;, W3C&nbsp;REC-html401-19991224, December&nbsp;1999, &lt;<a href="http://www.w3.org/TR/html401/">http://www.w3.org/TR/html401/</a>&gt;.</td></tr><tr><td class="reference"><b id="RFC2026">[RFC2026]</b></td><td class="top"><a href="mailto:sob@harvard.edu" title="Harvard University">Bradner, S.</a>, &#8220;<a href="http://tools.ietf.org/html/rfc2026">The Internet Standards Process -- Revision 3</a>&#8221;, BCP&nbsp;9, RFC&nbsp;2026, October&nbsp;1996.</td></tr><tr><td class="reference"><b id="RFC2119">[RFC2119]</b></td><td class="top"><a href="mailto:sob@harvard.edu" title="Harvard University">Bradner, S.</a>, &#8220;<a href="http://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>&#8221;, BCP&nbsp;14, RFC&nbsp;2119, March&nbsp;1997.</td></tr><tr><td class="reference"><b id="RFC2616">[RFC2616]</b></td><td class="top"><a href="mailto: