Changeset 2301 for draft-ietf-httpbis/latest

Timestamp:

01/07/13 08:47:55 (7 years ago)

Author:

julian.reschke@…

Message:

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

Location:

draft-ietf-httpbis/latest

Files:

• p1-messaging.html (modified) (49 diffs)
• p1-messaging.xml (modified) (1 diff)
• p2-semantics.html (modified) (103 diffs)
• p2-semantics.xml (modified) (1 diff)
• p4-conditional.html (modified) (21 diffs)
• p4-conditional.xml (modified) (1 diff)
• p5-range.html (modified) (22 diffs)
• p5-range.xml (modified) (1 diff)
• p6-cache.html (modified) (48 diffs)
• p6-cache.xml (modified) (1 diff)
• p7-auth.html (modified) (20 diffs)
• p7-auth.xml (modified) (1 diff)

draft-ietf-httpbis/latest/p1-messaging.html

@@ -440 +440 @@
   }
   @top-right {
-       content: "June 2013";
+       content: "July 2013";
   }
   @top-center {
@@ -449 +449 @@
   }
   @bottom-center {
-       content: "Expires December 25, 2013";
+       content: "Expires January 2, 2014";
   }
   @bottom-right {
@@ -486 +486 @@
       <link rel="Appendix" title="D Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.D">
       <link href="p2-semantics.html" rel="next">
-      <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/">
+      <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/">
       <link rel="schema.dct" href="http://purl.org/dc/terms/">
       <meta name="dct.creator" content="Fielding, R.">
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2013-06-23">
+      <meta name="dct.issued" scheme="ISO8601" content="2013-07-01">
       <meta name="dct.replaces" content="urn:ietf:rfc:2145">
       <meta name="dct.replaces" content="urn:ietf:rfc:2616">
@@ -520 +520 @@
             <tr>
                <td class="left">Intended status: Standards Track</td>
-               <td class="right">June 23, 2013</td>
+               <td class="right">July 1, 2013</td>
             </tr>
             <tr>
-               <td class="left">Expires: December 25, 2013</td>
+               <td class="left">Expires: January 2, 2014</td>
                <td class="right"></td>
             </tr>
@@ -551 +551 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on December 25, 2013.</p>
+      <p>This Internet-Draft will expire on January 2, 2014.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
@@ -775 +775 @@
       </p>
       <div id="core.rules">
-         <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
+         <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
             (hexadecimal 0-9/A-F/a-f), HTAB (horizontal tab), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), and VCHAR
             (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).
@@ -876 +876 @@
          often based on dynamic configuration for load balancing.
       </p>
-      <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.
+      <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.
          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.
       </p>
@@ -885 +885 @@
          for the sake of security, annotation services, or shared caching.
       </p>
-      <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,
+      <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,
          beyond those required by normal HTTP processing, that change the message in a way that would be significant to the original
          sender or potentially significant to downstream recipients). For example, a transforming proxy might be acting as a shared
@@ -893 +893 @@
          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.
       </p>
-      <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
+      <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
          them inbound to another server or servers. Gateways are often used to encapsulate legacy or untrusted information services,
          to improve server performance through "<dfn>accelerator</dfn>" caching, and to enable partitioning or load balancing of HTTP services across multiple machines.
@@ -907 +907 @@
          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.
       </p>
-      <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
+      <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
          intermediaries that can act on lower layers of the network protocol stack, filtering or redirecting HTTP traffic without the
          knowledge or permission of message senders. Network intermediaries often introduce security flaws or interoperability problems
@@ -1241 +1241 @@
          of the combined field value; a proxy <em class="bcp14">MUST NOT</em> change the order of these field values when forwarding a message.
       </p>
-      <div class="note" id="rfc.section.3.2.2.p.4"> 
-         <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
+      <div class="note" id="rfc.section.3.2.2.p.4">
+         <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
             multiple header fields with the same name. Since it cannot be combined into a single field-value, recipients ought to handle
             "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.)
@@ -1267 +1267 @@
       </div>
       <div id="rule.whitespace">
-         <p id="rfc.section.3.2.3.p.5">      </p>
+         <p id="rfc.section.3.2.3.p.5">   </p>
       </div>
       <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> )
@@ -1310 +1310 @@
       <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>
       <div id="rule.token.separators">
-         <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
+         <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
             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>).
          </p>
@@ -1327 +1327 @@
                  / "]" / "?" / "=" / "{" / "}"
 </pre><div id="rule.quoted-string">
-         <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>
+         <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>
       </div>
       <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>
@@ -1333 +1333 @@
   <a href="#rule.quoted-string" class="smpl">obs-text</a>       = %x80-FF
 </pre><div id="rule.quoted-pair">
-         <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>
+         <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>
       </div>
       <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> ) 
@@ -1342 +1342 @@
       </p>
       <div id="rule.comment">
-         <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
+         <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
             in fields containing "comment" as part of their field value definition.
          </p>
@@ -1349 +1349 @@
   <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>
 </pre><div id="rule.quoted-cpair">
-         <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>
+         <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>
       </div>
       <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> ) 
@@ -1441 +1441 @@
          that decimal value prior to determining the message body length.
       </p>
-      <div class="note" id="rfc.section.3.3.2.p.13"> 
-         <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
+      <div class="note" id="rfc.section.3.3.2.p.13">
+         <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
             field used only within the "message/external-body" media-type.
          </p> 
@@ -1449 +1449 @@
       <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>
       <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>
-      <p id="rfc.section.3.3.3.p.2"> </p>
+      <p id="rfc.section.3.3.3.p.2"></p>
       <ol>
          <li>
@@ -1557 +1557 @@
   <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> )
 </pre><div id="rule.parameter">
-         <p id="rfc.section.4.p.3">      Parameters are in the form of attribute/value pairs.</p>
+         <p id="rfc.section.4.p.3">   Parameters are in the form of attribute/value pairs.</p>
       </div>
       <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>
@@ -1653 +1653 @@
       <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.
       </p>
-      <div class="note" id="rfc.section.4.2.2.p.2"> 
-         <p> <b>Note:</b> Some incorrect implementations send the "deflate" compressed data without the zlib wrapper.
+      <div class="note" id="rfc.section.4.2.2.p.2">
+         <p><b>Note:</b> Some incorrect implementations send the "deflate" compressed data without the zlib wrapper.
          </p> 
       </div>
@@ -1741 +1741 @@
   <a href="#asterisk-form" class="smpl">asterisk-form</a>  = "*"
 </pre><div id="origin-form">
-         <p id="rfc.section.5.3.p.3"><span id="rfc.iref.o.3"></span>  <b>origin-form</b> 
+         <p id="rfc.section.5.3.p.3"><span id="rfc.iref.o.3"></span> <b>origin-form</b> 
          </p>
       </div>
@@ -1757 +1757 @@
 </pre><p id="rfc.section.5.3.p.9">followed by the remainder of the request message.</p>
       <div id="absolute-form">
-         <p id="rfc.section.5.3.p.10"><span id="rfc.iref.a.2"></span>  <b>absolute-form</b> 
+         <p id="rfc.section.5.3.p.10"><span id="rfc.iref.a.2"></span> <b>absolute-form</b> 
          </p>
       </div>
@@ -1769 +1769 @@
       </p>
       <div id="authority-form">
-         <p id="rfc.section.5.3.p.15"><span id="rfc.iref.a.3"></span>  <b>authority-form</b> 
+         <p id="rfc.section.5.3.p.15"><span id="rfc.iref.a.3"></span> <b>authority-form</b> 
          </p>
       </div>
@@ -1776 +1776 @@
       <div id="rfc.figure.u.41"></div><pre class="text2">CONNECT www.example.com:80 HTTP/1.1
 </pre><div id="asterisk-form">
-         <p id="rfc.section.5.3.p.18"><span id="rfc.iref.a.4"></span>  <b>asterisk-form</b> 
+         <p id="rfc.section.5.3.p.18"><span id="rfc.iref.a.4"></span> <b>asterisk-form</b> 
          </p>
       </div>
@@ -1996 +1996 @@
 </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>).
       </p>
-      <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.
-      </p>
-      <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.
+      <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.
+      </p>
+      <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.
       </p>
       <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>
@@ -2195 +2195 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <td class="left"> <a href="#header.connection" id="rfc.xref.header.connection.7" title="Connection">Section&nbsp;6.1</a> 
+                  <td class="left"><a href="#header.connection" id="rfc.xref.header.connection.7" title="Connection">Section&nbsp;6.1</a> 
                   </td>
                </tr>
@@ -2202 +2202 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <td class="left"> <a href="#header.content-length" id="rfc.xref.header.content-length.1" title="Content-Length">Section&nbsp;3.3.2</a> 
+                  <td class="left"><a href="#header.content-length" id="rfc.xref.header.content-length.1" title="Content-Length">Section&nbsp;3.3.2</a> 
                   </td>
                </tr>
@@ -2209 +2209 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <td class="left"> <a href="#header.host" id="rfc.xref.header.host.2" title="Host">Section&nbsp;5.4</a> 
+                  <td class="left"><a href="#header.host" id="rfc.xref.header.host.2" title="Host">Section&nbsp;5.4</a> 
                   </td>
                </tr>
@@ -2216 +2216 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <td class="left"> <a href="#header.te" id="rfc.xref.header.te.3" title="TE">Section&nbsp;4.3</a> 
+                  <td class="left"><a href="#header.te" id="rfc.xref.header.te.3" title="TE">Section&nbsp;4.3</a> 
                   </td>
                </tr>
@@ -2223 +2223 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <td class="left"> <a href="#header.trailer" id="rfc.xref.header.trailer.1" title="Trailer">Section&nbsp;4.1.1</a> 
+                  <td class="left"><a href="#header.trailer" id="rfc.xref.header.trailer.1" title="Trailer">Section&nbsp;4.1.1</a> 
                   </td>
                </tr>
@@ -2230 +2230 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <td class="left"> <a href="#header.transfer-encoding" id="rfc.xref.header.transfer-encoding.3" title="Transfer-Encoding">Section&nbsp;3.3.1</a> 
+                  <td class="left"><a href="#header.transfer-encoding" id="rfc.xref.header.transfer-encoding.3" title="Transfer-Encoding">Section&nbsp;3.3.1</a> 
                   </td>
                </tr>
@@ -2237 +2237 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <td class="left"> <a href="#header.upgrade" id="rfc.xref.header.upgrade.2" title="Upgrade">Section&nbsp;6.7</a> 
+                  <td class="left"><a href="#header.upgrade" id="rfc.xref.header.upgrade.2" title="Upgrade">Section&nbsp;6.7</a> 
                   </td>
                </tr>
@@ -2244 +2244 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <td class="left"> <a href="#header.via" id="rfc.xref.header.via.1" title="Via">Section&nbsp;5.7.1</a> 
+                  <td class="left"><a href="#header.via" id="rfc.xref.header.via.1" title="Via">Section&nbsp;5.7.1</a> 
                   </td>
                </tr>
@@ -2268 +2268 @@
                   <td class="left">http</td>
                   <td class="left">reserved</td>
-                  <td class="left"> <a href="#header.field.registration" title="Header Field Registration">Section&nbsp;7.1</a> 
+                  <td class="left"><a href="#header.field.registration" title="Header Field Registration">Section&nbsp;7.1</a> 
                   </td>
                </tr>
@@ -2314 +2314 @@
          for all "message" types regarding line length and encodings.
       </p>
-      <p id="rfc.section.7.3.1.p.2"> </p>
+      <p id="rfc.section.7.3.1.p.2"></p>
       <dl>
          <dt>Type name:</dt>
@@ -2344 +2344 @@
          <dt>Applications that use this media type:</dt>
          <dt>Additional information:</dt>
-         <dd> 
+         <dd>
             <dl>
                <dt>Magic number(s):</dt>
@@ -2369 +2369 @@
       <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>
       <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>
-      <p id="rfc.section.7.3.2.p.2"> </p>
+      <p id="rfc.section.7.3.2.p.2"></p>
       <dl>
          <dt>Type name:</dt>
@@ -2401 +2401 @@
          <dt>Applications that use this media type:</dt>
          <dt>Additional information:</dt>
-         <dd> 
+         <dd>
             <dl>
                <dt>Magic number(s):</dt>
@@ -2454 +2454 @@
                   <td class="left">chunked</td>
                   <td class="left">Transfer in a series of chunks</td>
-                  <td class="left"> <a href="#chunked.encoding" title="Chunked Transfer Coding">Section&nbsp;4.1</a> 
+                  <td class="left"><a href="#chunked.encoding" title="Chunked Transfer Coding">Section&nbsp;4.1</a> 
                   </td>
                </tr>
@@ -2460 +2460 @@
                   <td class="left">compress</td>
                   <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>
-                  <td class="left"> <a href="#compress.coding" title="Compress Coding">Section&nbsp;4.2.1</a> 
+                  <td class="left"><a href="#compress.coding" title="Compress Coding">Section&nbsp;4.2.1</a> 
                   </td>
                </tr>
@@ -2467 +2467 @@
                   <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>)
                   </td>
-                  <td class="left"> <a href="#deflate.coding" title="Deflate Coding">Section&nbsp;4.2.2</a> 
+                  <td class="left"><a href="#deflate.coding" title="Deflate Coding">Section&nbsp;4.2.2</a> 
                   </td>
                </tr>
@@ -2473 +2473 @@
                   <td class="left">gzip</td>
                   <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>
-                  <td class="left"> <a href="#gzip.coding" title="Gzip Coding">Section&nbsp;4.2.3</a> 
+                  <td class="left"><a href="#gzip.coding" title="Gzip Coding">Section&nbsp;4.2.3</a> 
                   </td>
                </tr>
@@ -2479 +2479 @@
                   <td class="left">x-compress</td>
                   <td class="left">Deprecated (alias for compress)</td>
-                  <td class="left"> <a href="#compress.coding" title="Compress Coding">Section&nbsp;4.2.1</a> 
+                  <td class="left"><a href="#compress.coding" title="Compress Coding">Section&nbsp;4.2.1</a> 
                   </td>
                </tr>
@@ -2485 +2485 @@
                   <td class="left">x-gzip</td>
                   <td class="left">Deprecated (alias for gzip)</td>
-                  <td class="left"> <a href="#gzip.coding" title="Gzip Coding">Section&nbsp;4.2.3</a> 
+                  <td class="left"><a href="#gzip.coding" title="Gzip Coding">Section&nbsp;4.2.3</a> 
                   </td>
                </tr>
@@ -2657 +2657 @@
          <tr>
             <td class="reference"><b id="Part2">[Part2]</b></td>
-            <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.
+            <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.
             </td>
          </tr>
          <tr>
             <td class="reference"><b id="Part4">[Part4]</b></td>
-            <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.
+            <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.
             </td>
          </tr>
          <tr>
             <td class="reference"><b id="Part5">[Part5]</b></td>
-            <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.
+            <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.
             </td>
          </tr>
          <tr>
             <td class="reference"><b id="Part6">[Part6]</b></td>
-            <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.
+            <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.
             </td>
          </tr>
          <tr>
             <td class="reference"><b id="Part7">[Part7]</b></td>
-            <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.
+            <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.
             </td>
          </tr>
@@ -3014 +3014 @@
   ","
   ",   ,"
-</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.
+</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.
       </p>
       <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
@@ -3147 +3147 @@
       <p id="rfc.section.D.2.p.1">Closed issues: </p>
       <ul>
-         <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)
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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?"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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'"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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 "//""
-         </li>
-         <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"
+         <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)
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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?"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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'"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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 "//""
+         </li>
+         <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"
          </li>
       </ul>
@@ -3191 +3191 @@
       <p id="rfc.section.D.3.p.1">Closed issues: </p>
       <ul>
-         <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)"
-         </li>
-         <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"
-         </li>
-         <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)
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
+         <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)"
+         </li>
+         <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"
+         </li>
+         <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)
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
          </li>
       </ul>

draft-ietf-httpbis/latest/p1-messaging.xml

@@ -13 +13 @@
   <!ENTITY SHOULD-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHOULD NOT</bcp14>">
   <!ENTITY ID-VERSION "latest">
-  <!ENTITY ID-MONTH "June">
+  <!ENTITY ID-MONTH "July">
   <!ENTITY ID-YEAR "2013">
   <!ENTITY mdash "&#8212;">

draft-ietf-httpbis/latest/p2-semantics.html

@@ -440 +440 @@
   }
   @top-right {
-       content: "June 2013";
+       content: "July 2013";
   }
   @top-center {
@@ -449 +449 @@
   }
   @bottom-center {
-       content: "Expires December 18, 2013";
+       content: "Expires January 2, 2014";
   }
   @bottom-right {
@@ -489 +489 @@
       <link href="p1-messaging.html" rel="prev">
       <link href="p4-conditional.html" rel="next">
-      <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/">
+      <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/">
       <link rel="schema.dct" href="http://purl.org/dc/terms/">
       <meta name="dct.creator" content="Fielding, R.">
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2013-06-16">
+      <meta name="dct.issued" scheme="ISO8601" content="2013-07-01">
       <meta name="dct.replaces" content="urn:ietf:rfc:2616">
       <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.">
@@ -522 +522 @@
             <tr>
                <td class="left">Intended status: Standards Track</td>
-               <td class="right">June 16, 2013</td>
+               <td class="right">July 1, 2013</td>
             </tr>
             <tr>
-               <td class="left">Expires: December 18, 2013</td>
+               <td class="left">Expires: January 2, 2014</td>
                <td class="right"></td>
             </tr>
@@ -553 +553 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on December 18, 2013.</p>
+      <p>This Internet-Draft will expire on January 2, 2014.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
@@ -896 +896 @@
   <a href="#media.type" class="smpl">subtype</a>    = <a href="#imported.abnf" class="smpl">token</a>
 </pre><div id="rule.parameter">
-         <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.
+         <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.
          </p>
       </div>
@@ -915 +915 @@
 </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>.
       </p>
-      <div class="note" id="rfc.section.3.1.1.1.p.9"> 
-         <p> <b>Note:</b> Unlike some similar constructs in other header fields, media type parameters do not allow whitespace (even "bad" whitespace)
+      <div class="note" id="rfc.section.3.1.1.1.p.9">
+         <p><b>Note:</b> Unlike some similar constructs in other header fields, media type parameters do not allow whitespace (even "bad" whitespace)
             around the "=" character.
          </p> 
@@ -1027 +1027 @@
          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.
       </p>
-      <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.
+      <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.
       </p>
       <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;
@@ -1688 +1688 @@
       <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>
       <p id="rfc.section.5.1.1.1.p.1">The only expectation defined by this specification is:</p>
-      <p id="rfc.section.5.1.1.1.p.2"> <dfn>100-continue</dfn>  
+      <p id="rfc.section.5.1.1.1.p.2"><dfn>100-continue</dfn> 
       </p>
       <ul class="empty">
@@ -1862 +1862 @@
          since it acts as a separator between the two parameter sets.
       </p>
-      <div class="note" id="rfc.section.5.3.2.p.5"> 
-         <p> <b>Note:</b> Use of the "q" parameter name to separate media type parameters from Accept extension parameters is due to historical practice.
+      <div class="note" id="rfc.section.5.3.2.p.5">
+         <p><b>Note:</b> Use of the "q" parameter name to separate media type parameters from Accept extension parameters is due to historical practice.
             Although this prevents any media type parameter named "q" from being used with a media range, such an event is believed to
             be unlikely given the lack of any "q" parameters in the IANA media type registry and the rare usage of any media type parameters
@@ -1871 +1871 @@
       <p id="rfc.section.5.3.2.p.6">The example</p>
       <div id="rfc.figure.u.24"></div><pre class="text">  Accept: audio/*; q=0.2, audio/basic
-</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
+</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
          quality".
       </p>
@@ -1937 +1937 @@
          </table>
       </div>
-      <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
+      <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
          is a closed system that cannot interact with other rendering agents, this default set ought to be configurable by the user.
       </p>
@@ -1996 +1996 @@
          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.
       </p>
-      <div class="note" id="rfc.section.5.3.4.p.9"> 
-         <p> <b>Note:</b> Most HTTP/1.0 applications do not recognize or obey qvalues associated with content-codings. This means that qvalues might
+      <div class="note" id="rfc.section.5.3.4.p.9">
+         <p><b>Note:</b> Most HTTP/1.0 applications do not recognize or obey qvalues associated with content-codings. This means that qvalues might
             not work and are not permitted with x-gzip or x-compress.
          </p> 
@@ -2034 +2034 @@
          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.
       </p>
-      <div class="note" id="rfc.section.5.3.5.p.11"> 
-         <p> <b>Note:</b> User agents ought to provide guidance to users when setting a preference, since users are rarely familiar with the details
+      <div class="note" id="rfc.section.5.3.5.p.11">
+         <p><b>Note:</b> User agents ought to provide guidance to users when setting a preference, since users are rarely familiar with the details
             of language matching as described above. For example, users might assume that on selecting "en-gb", they will be served any
             kind of English document if British English is not available. A user agent might suggest, in such a case, to add "en" to the
@@ -2177 +2177 @@
       </p>
       <ul>
-         <li> <a href="#status.1xx" class="smpl">1xx (Informational)</a>: The request was received, continuing process
-         </li>
-         <li> <a href="#status.2xx" class="smpl">2xx (Successful)</a>: The request was successfully received, understood, and accepted
-         </li>
-         <li> <a href="#status.3xx" class="smpl">3xx (Redirection)</a>: Further action needs to be taken in order to complete the request
-         </li>
-         <li> <a href="#status.4xx" class="smpl">4xx (Client Error)</a>: The request contains bad syntax or cannot be fulfilled
-         </li>
-         <li> <a href="#status.5xx" class="smpl">5xx (Server Error)</a>: The server failed to fulfill an apparently valid request
+         <li><a href="#status.1xx" class="smpl">1xx (Informational)</a>: The request was received, continuing process
+         </li>
+         <li><a href="#status.2xx" class="smpl">2xx (Successful)</a>: The request was successfully received, understood, and accepted
+         </li>
+         <li><a href="#status.3xx" class="smpl">3xx (Redirection)</a>: Further action needs to be taken in order to complete the request
+         </li>
+         <li><a href="#status.4xx" class="smpl">4xx (Client Error)</a>: The request contains bad syntax or cannot be fulfilled
+         </li>
+         <li><a href="#status.5xx" class="smpl">5xx (Server Error)</a>: The server failed to fulfill an apparently valid request
          </li>
       </ul>
@@ -2564 +2564 @@
          </li>
       </ol>
-      <div class="note" id="rfc.section.6.4.p.3"> 
-         <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
+      <div class="note" id="rfc.section.6.4.p.3">
+         <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
             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
             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.
@@ -2572 +2572 @@
       <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).
       </p>
-      <div class="note" id="rfc.section.6.4.p.5"> 
-         <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.
+      <div class="note" id="rfc.section.6.4.p.5">
+         <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.
          </p> 
       </div>
@@ -2591 +2591 @@
       <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>).
       </p>
-      <div class="note" id="rfc.section.6.4.1.p.5"> 
-         <p> <b>Note:</b> The original proposal for 300 defined the URI header field as providing a list of alternative representations, such that it
+      <div class="note" id="rfc.section.6.4.1.p.5">
+         <p><b>Note:</b> The original proposal for 300 defined the URI header field as providing a list of alternative representations, such that it
             would be usable for 200, 300, and 406 responses and be transferred in responses to the HEAD method. However, lack of deployment
             and disagreement over syntax led to both URI and Alternates (a subsequent proposal) being dropped from this specification.
@@ -2607 +2607 @@
          with a hyperlink to the new URI(s).
       </p>
-      <div class="note" id="rfc.section.6.4.2.p.3"> 
-         <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.
+      <div class="note" id="rfc.section.6.4.2.p.3">
+         <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.
          </p> 
       </div>
@@ -2621 +2621 @@
          with a hyperlink to the different URI(s).
       </p>
-      <div class="note" id="rfc.section.6.4.3.p.3"> 
-         <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.
+      <div class="note" id="rfc.section.6.4.3.p.3">
+         <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.
          </p> 
       </div>
@@ -2659 +2659 @@
          with a hyperlink to the different URI(s).
       </p>
-      <div class="note" id="rfc.section.6.4.7.p.3"> 
-         <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
+      <div class="note" id="rfc.section.6.4.7.p.3">
+         <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
             for <a href="#status.301" class="smpl">301 (Moved
                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).
@@ -2687 +2687 @@
       <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.
       </p>
-      <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>.
+      <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>.
       </p>
       <div id="rfc.iref.76"></div>
@@ -2811 +2811 @@
          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.
       </p>
-      <div class="note" id="rfc.section.6.6.4.p.2"> 
-         <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
+      <div class="note" id="rfc.section.6.6.4.p.2">
+         <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
             simply refuse the connection.
          </p> 
@@ -2902 +2902 @@
       </p>
       <div id="preferred.date.format">
-         <p id="rfc.section.7.1.1.1.p.7">                    Preferred format:</p>
+         <p id="rfc.section.7.1.1.1.p.7">          Preferred format:</p>
       </div>
       <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>
@@ -2943 +2943 @@
   <a href="#preferred.date.format" class="smpl">second</a>       = 2<a href="#imported.abnf" class="smpl">DIGIT</a>               
 </pre><div id="obsolete.date.formats">
-         <p id="rfc.section.7.1.1.1.p.9">              Obsolete formats:</p>
+         <p id="rfc.section.7.1.1.1.p.9">       Obsolete formats:</p>
       </div>
       <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> 
@@ -2969 +2969 @@
          date and time specifications defined by the Internet Message Format.
       </p>
-      <div class="note" id="rfc.section.7.1.1.1.p.16"> 
-         <p> <b>Note:</b> HTTP requirements for the date/time stamp format apply only to their usage within the protocol stream. Implementations are
+      <div class="note" id="rfc.section.7.1.1.1.p.16">
+         <p><b>Note:</b> HTTP requirements for the date/time stamp format apply only to their usage within the protocol stream. Implementations are
             not required to use these formats for user presentation, request logging, etc.
          </p> 
@@ -3023 +3023 @@
          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.
       </p>
-      <div class="note" id="rfc.section.7.1.2.p.9"> 
-         <p> <b>Note:</b> Some recipients attempt to recover from Location fields that are not valid URI references. This specification does not mandate
+      <div class="note" id="rfc.section.7.1.2.p.9">
+         <p><b>Note:</b> Some recipients attempt to recover from Location fields that are not valid URI references. This specification does not mandate
             or define such processing, but does allow it for the sake of robustness.
          </p> 
       </div>
-      <div class="note" id="rfc.section.7.1.2.p.10"> 
-         <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.
+      <div class="note" id="rfc.section.7.1.2.p.10">
+         <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.
             It is therefore possible for a response to contain both the Location and Content-Location header fields.
          </p> 
@@ -3041 +3041 @@
       <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>
 </pre><div id="rule.delta-seconds">
-         <p id="rfc.section.7.1.3.p.4">  Time spans are non-negative decimal integers, representing time in seconds.</p>
+         <p id="rfc.section.7.1.3.p.4"> Time spans are non-negative decimal integers, representing time in seconds.</p>
       </div>
       <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>
@@ -3232 +3232 @@
          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.
       </p>
-      <div class="note" id="rfc.section.8.1.2.p.4"> 
-         <p> <b>Note:</b> Avoid defining a method name that starts with "M-", since that prefix might be misinterpreted as having the semantics assigned
+      <div class="note" id="rfc.section.8.1.2.p.4">
+         <p><b>Note:</b> Avoid defining a method name that starts with "M-", since that prefix might be misinterpreted as having the semantics assigned
             to it by <a href="#RFC2774" id="rfc.xref.RFC2774.1"><cite title="An HTTP Extension Framework">[RFC2774]</cite></a>.
          </p> 
@@ -3255 +3255 @@
                   <td class="left">no</td>
                   <td class="left">no</td>
-                  <td class="left"> <a href="#CONNECT" id="rfc.xref.CONNECT.2" title="CONNECT">Section&nbsp;4.3.6</a> 
+                  <td class="left"><a href="#CONNECT" id="rfc.xref.CONNECT.2" title="CONNECT">Section&nbsp;4.3.6</a> 
                   </td>
                </tr>
@@ -3262 +3262 @@
                   <td class="left">no</td>
                   <td class="left">yes</td>
-                  <td class="left"> <a href="#DELETE" id="rfc.xref.DELETE.2" title="DELETE">Section&nbsp;4.3.5</a> 
+                  <td class="left"><a href="#DELETE" id="rfc.xref.DELETE.2" title="DELETE">Section&nbsp;4.3.5</a> 
                   </td>
                </tr>
@@ -3269 +3269 @@
                   <td class="left">yes</td>
                   <td class="left">yes</td>
-                  <td class="left"> <a href="#GET" id="rfc.xref.GET.4" title="GET">Section&nbsp;4.3.1</a> 
+                  <td class="left"><a href="#GET" id="rfc.xref.GET.4" title="GET">Section&nbsp;4.3.1</a> 
                   </td>
                </tr>
@@ -3276 +3276 @@
                   <td class="left">yes</td>
                   <td class="left">yes</td>
-                  <td class="left"> <a href="#HEAD" id="rfc.xref.HEAD.2" title="HEAD">Section&nbsp;4.3.2</a> 
+                  <td class="left"><a href="#HEAD" id="rfc.xref.HEAD.2" title="HEAD">Section&nbsp;4.3.2</a> 
                   </td>
                </tr>
@@ -3283 +3283 @@
                   <td class="left">yes</td>
                   <td class="left">yes</td>
-                  <td class="left"> <a href="#OPTIONS" id="rfc.xref.OPTIONS.3" title="OPTIONS">Section&nbsp;4.3.7</a> 
+                  <td class="left"><a href="#OPTIONS" id="rfc.xref.OPTIONS.3" title="OPTIONS">Section&nbsp;4.3.7</a> 
                   </td>
                </tr>
@@ -3290 +3290 @@
                   <td class="left">no</td>
                   <td class="left">no</td>
-                  <td class="left"> <a href="#POST" id="rfc.xref.POST.3" title="POST">Section&nbsp;4.3.3</a> 
+                  <td class="left"><a href="#POST" id="rfc.xref.POST.3" title="POST">Section&nbsp;4.3.3</a> 
                   </td>
                </tr>
@@ -3297 +3297 @@
                   <td class="left">no</td>
                   <td class="left">yes</td>
-                  <td class="left"> <a href="#PUT" id="rfc.xref.PUT.3" title="PUT">Section&nbsp;4.3.4</a> 
+                  <td class="left"><a href="#PUT" id="rfc.xref.PUT.3" title="PUT">Section&nbsp;4.3.4</a> 
                   </td>
                </tr>
@@ -3304 +3304 @@
                   <td class="left">yes</td>
                   <td class="left">yes</td>
-                  <td class="left"> <a href="#TRACE" id="rfc.xref.TRACE.3" title="TRACE">Section&nbsp;4.3.8</a> 
+                  <td class="left"><a href="#TRACE" id="rfc.xref.TRACE.3" title="TRACE">Section&nbsp;4.3.8</a> 
                   </td>
                </tr>
@@ -3367 +3367 @@
                   <td class="left">100</td>
                   <td class="left">Continue</td>
-                  <td class="left"> <a href="#status.100" id="rfc.xref.status.100.4" title="100 Continue">Section&nbsp;6.2.1</a> 
+                  <td class="left"><a href="#status.100" id="rfc.xref.status.100.4" title="100 Continue">Section&nbsp;6.2.1</a> 
                   </td>
                </tr>
@@ -3373 +3373 @@
                   <td class="left">101</td>
                   <td class="left">Switching Protocols</td>
-                  <td class="left"> <a href="#status.101" id="rfc.xref.status.101.2" title="101 Switching Protocols">Section&nbsp;6.2.2</a> 
+                  <td class="left"><a href="#status.101" id="rfc.xref.status.101.2" title="101 Switching Protocols">Section&nbsp;6.2.2</a> 
                   </td>
                </tr>
@@ -3379 +3379 @@
                   <td class="left">200</td>
                   <td class="left">OK</td>
-                  <td class="left"> <a href="#status.200" id="rfc.xref.status.200.2" title="200 OK">Section&nbsp;6.3.1</a> 
+                  <td class="left"><a href="#status.200" id="rfc.xref.status.200.2" title="200 OK">Section&nbsp;6.3.1</a> 
                   </td>
                </tr>
@@ -3385 +3385 @@
                   <td class="left">201</td>
                   <td class="left">Created</td>
-                  <td class="left"> <a href="#status.201" id="rfc.xref.status.201.2" title="201 Created">Section&nbsp;6.3.2</a> 
+                  <td class="left"><a href="#status.201" id="rfc.xref.status.201.2" title="201 Created">Section&nbsp;6.3.2</a> 
                   </td>
                </tr>
@@ -3391 +3391 @@
                   <td class="left">202</td>
                   <td class="left">Accepted</td>
-                  <td class="left"> <a href="#status.202" id="rfc.xref.status.202.2" title="202 Accepted">Section&nbsp;6.3.3</a> 
+                  <td class="left"><a href="#status.202" id="rfc.xref.status.202.2" title="202 Accepted">Section&nbsp;6.3.3</a> 
                   </td>
                </tr>
@@ -3397 +3397 @@
                   <td class="left">203</td>
                   <td class="left">Non-Authoritative Information</td>
-                  <td class="left"> <a href="#status.203" id="rfc.xref.status.203.2" title="203 Non-Authoritative Information">Section&nbsp;6.3.4</a> 
+                  <td class="left"><a href="#status.203" id="rfc.xref.status.203.2" title="203 Non-Authoritative Information">Section&nbsp;6.3.4</a> 
                   </td>
                </tr>
@@ -3403 +3403 @@
                   <td class="left">204</td>
                   <td class="left">No Content</td>
-                  <td class="left"> <a href="#status.204" id="rfc.xref.status.204.2" title="204 No Content">Section&nbsp;6.3.5</a> 
+                  <td class="left"><a href="#status.204" id="rfc.xref.status.204.2" title="204 No Content">Section&nbsp;6.3.5</a> 
                   </td>
                </tr>
@@ -3409 +3409 @@
                   <td class="left">205</td>
                   <td class="left">Reset Content</td>
-                  <td class="left"> <a href="#status.205" id="rfc.xref.status.205.2" title="205 Reset Content">Section&nbsp;6.3.6</a> 
+                  <td class="left"><a href="#status.205" id="rfc.xref.status.205.2" title="205 Reset Content">Section&nbsp;6.3.6</a> 
                   </td>
                </tr>
@@ -3415 +3415 @@
                   <td class="left">300</td>
                   <td class="left">Multiple Choices</td>
-                  <td class="left"> <a href="#status.300" id="rfc.xref.status.300.3" title="300 Multiple Choices">Section&nbsp;6.4.1</a> 
+                  <td class="left"><a href="#status.300" id="rfc.xref.status.300.3" title="300 Multiple Choices">Section&nbsp;6.4.1</a> 
                   </td>
                </tr>
@@ -3421 +3421 @@
                   <td class="left">301</td>
                   <td class="left">Moved Permanently</td>
-                  <td class="left"> <a href="#status.301" id="rfc.xref.status.301.2" title="301 Moved Permanently">Section&nbsp;6.4.2</a> 
+                  <td class="left"><a href="#status.301" id="rfc.xref.status.301.2" title="301 Moved Permanently">Section&nbsp;6.4.2</a> 
                   </td>
                </tr>
@@ -3427 +3427 @@
                   <td class="left">302</td>
                   <td class="left">Found</td>
-                  <td class="left"> <a href="#status.302" id="rfc.xref.status.302.2" title="302 Found">Section&nbsp;6.4.3</a> 
+                  <td class="left"><a href="#status.302" id="rfc.xref.status.302.2" title="302 Found">Section&nbsp;6.4.3</a> 
                   </td>
                </tr>
@@ -3433 +3433 @@
                   <td class="left">303</td>
                   <td class="left">See Other</td>
-                  <td class="left"> <a href="#status.303" id="rfc.xref.status.303.2" title="303 See Other">Section&nbsp;6.4.4</a> 
+                  <td class="left"><a href="#status.303" id="rfc.xref.status.303.2" title="303 See Other">Section&nbsp;6.4.4</a> 
                   </td>
                </tr>
@@ -3439 +3439 @@
                   <td class="left">305</td>
                   <td class="left">Use Proxy</td>
-                  <td class="left"> <a href="#status.305" id="rfc.xref.status.305.2" title="305 Use Proxy">Section&nbsp;6.4.5</a> 
+                  <td class="left"><a href="#status.305" id="rfc.xref.status.305.2" title="305 Use Proxy">Section&nbsp;6.4.5</a> 
                   </td>
                </tr>
@@ -3445 +3445 @@
                   <td class="left">306</td>
                   <td class="left">(Unused)</td>
-                  <td class="left"> <a href="#status.306" id="rfc.xref.status.306.1" title="306 (Unused)">Section&nbsp;6.4.6</a> 
+                  <td class="left"><a href="#status.306" id="rfc.xref.status.306.1" title="306 (Unused)">Section&nbsp;6.4.6</a> 
                   </td>
                </tr>
@@ -3451 +3451 @@
                   <td class="left">307</td>
                   <td class="left">Temporary Redirect</td>
-                  <td class="left"> <a href="#status.307" id="rfc.xref.status.307.2" title="307 Temporary Redirect">Section&nbsp;6.4.7</a> 
+                  <td class="left"><a href="#status.307" id="rfc.xref.status.307.2" title="307 Temporary Redirect">Section&nbsp;6.4.7</a> 
                   </td>
                </tr>
@@ -3457 +3457 @@
                   <td class="left">400</td>
                   <td class="left">Bad Request</td>
-                  <td class="left"> <a href="#status.400" id="rfc.xref.status.400.2" title="400 Bad Request">Section&nbsp;6.5.1</a> 
+                  <td class="left"><a href="#status.400" id="rfc.xref.status.400.2" title="400 Bad Request">Section&nbsp;6.5.1</a> 
                   </td>
                </tr>
@@ -3463 +3463 @@
                   <td class="left">402</td>
                   <td class="left">Payment Required</td>
-                  <td class="left"> <a href="#status.402" id="rfc.xref.status.402.2" title="402 Payment Required">Section&nbsp;6.5.2</a> 
+                  <td class="left"><a href="#status.402" id="rfc.xref.status.402.2" title="402 Payment Required">Section&nbsp;6.5.2</a> 
                   </td>
                </tr>
@@ -3469 +3469 @@
                   <td class="left">403</td>
                   <td class="left">Forbidden</td>
-                  <td class="left"> <a href="#status.403" id="rfc.xref.status.403.2" title="403 Forbidden">Section&nbsp;6.5.3</a> 
+                  <td class="left"><a href="#status.403" id="rfc.xref.status.403.2" title="403 Forbidden">Section&nbsp;6.5.3</a> 
                   </td>
                </tr>
@@ -3475 +3475 @@
                   <td class="left">404</td>
                   <td class="left">Not Found</td>
-                  <td class="left"> <a href="#status.404" id="rfc.xref.status.404.2" title="404 Not Found">Section&nbsp;6.5.4</a> 
+                  <td class="left"><a href="#status.404" id="rfc.xref.status.404.2" title="404 Not Found">Section&nbsp;6.5.4</a> 
                   </td>
                </tr>
@@ -3481 +3481 @@
                   <td class="left">405</td>
                   <td class="left">Method Not Allowed</td>
-                  <td class="left"> <a href="#status.405" id="rfc.xref.status.405.2" title="405 Method Not Allowed">Section&nbsp;6.5.5</a> 
+                  <td class="left"><a href="#status.405" id="rfc.xref.status.405.2" title="405 Method Not Allowed">Section&nbsp;6.5.5</a> 
                   </td>
                </tr>
@@ -3487 +3487 @@
                   <td class="left">406</td>
                   <td class="left">Not Acceptable</td>
-                  <td class="left"> <a href="#status.406" id="rfc.xref.status.406.2" title="406 Not Acceptable">Section&nbsp;6.5.6</a> 
+                  <td class="left"><a href="#status.406" id="rfc.xref.status.406.2" title="406 Not Acceptable">Section&nbsp;6.5.6</a> 
                   </td>
                </tr>
@@ -3493 +3493 @@
                   <td class="left">408</td>
                   <td class="left">Request Timeout</td>
-                  <td class="left"> <a href="#status.408" id="rfc.xref.status.408.2" title="408 Request Timeout">Section&nbsp;6.5.7</a> 
+                  <td class="left"><a href="#status.408" id="rfc.xref.status.408.2" title="408 Request Timeout">Section&nbsp;6.5.7</a> 
                   </td>
                </tr>
@@ -3499 +3499 @@
                   <td class="left">409</td>
                   <td class="left">Conflict</td>
-                  <td class="left"> <a href="#status.409" id="rfc.xref.status.409.2" title="409 Conflict">Section&nbsp;6.5.8</a> 
+                  <td class="left"><a href="#status.409" id="rfc.xref.status.409.2" title="409 Conflict">Section&nbsp;6.5.8</a> 
                   </td>
                </tr>
@@ -3505 +3505 @@
                   <td class="left">410</td>
                   <td class="left">Gone</td>
-                  <td class="left"> <a href="#status.410" id="rfc.xref.status.410.2" title="410 Gone">Section&nbsp;6.5.9</a> 
+                  <td class="left"><a href="#status.410" id="rfc.xref.status.410.2" title="410 Gone">Section&nbsp;6.5.9</a> 
                   </td>
                </tr>
@@ -3511 +3511 @@
                   <td class="left">411</td>
                   <td class="left">Length Required</td>
-                  <td class="left"> <a href="#status.411" id="rfc.xref.status.411.2" title="411 Length Required">Section&nbsp;6.5.10</a> 
+                  <td class="left"><a href="#status.411" id="rfc.xref.status.411.2" title="411 Length Required">Section&nbsp;6.5.10</a> 
                   </td>
                </tr>
@@ -3517 +3517 @@
                   <td class="left">413</td>
                   <td class="left">Payload Too Large</td>
-                  <td class="left"> <a href="#status.413" id="rfc.xref.status.413.2" title="413 Payload Too Large">Section&nbsp;6.5.11</a> 
+                  <td class="left"><a href="#status.413" id="rfc.xref.status.413.2" title="413 Payload Too Large">Section&nbsp;6.5.11</a> 
                   </td>
                </tr>
@@ -3523 +3523 @@
                   <td class="left">414</td>
                   <td class="left">URI Too Long</td>
-                  <td class="left"> <a href="#status.414" id="rfc.xref.status.414.2" title="414 URI Too Long">Section&nbsp;6.5.12</a> 
+                  <td class="left"><a href="#status.414" id="rfc.xref.status.414.2" title="414 URI Too Long">Section&nbsp;6.5.12</a> 
                   </td>
                </tr>
@@ -3529 +3529 @@
                   <td class="left">415</td>
                   <td class="left">Unsupported Media Type</td>
-                  <td class="left"> <a href="#status.415" id="rfc.xref.status.415.2" title="415 Unsupported Media Type">Section&nbsp;6.5.13</a> 
+                  <td class="left"><a href="#status.415" id="rfc.xref.status.415.2" title="415 Unsupported Media Type">Section&nbsp;6.5.13</a> 
                   </td>
                </tr>
@@ -3535 +3535 @@
                   <td class="left">417</td>
                   <td class="left">Expectation Failed</td>
-                  <td class="left"> <a href="#status.417" id="rfc.xref.status.417.2" title="417 Expectation Failed">Section&nbsp;6.5.14</a> 
+                  <td class="left"><a href="#status.417" id="rfc.xref.status.417.2" title="417 Expectation Failed">Section&nbsp;6.5.14</a> 
                   </td>
                </tr>
@@ -3541 +3541 @@
                   <td class="left">426</td>
                   <td class="left">Upgrade Required</td>
-                  <td class="left"> <a href="#status.426" id="rfc.xref.status.426.2" title="426 Upgrade Required">Section&nbsp;6.5.15</a> 
+                  <td class="left"><a href="#status.426" id="rfc.xref.status.426.2" title="426 Upgrade Required">Section&nbsp;6.5.15</a> 
                   </td>
                </tr>
@@ -3547 +3547 @@
                   <td class="left">500</td>
                   <td class="left">Internal Server Error</td>
-                  <td class="left"> <a href="#status.500" id="rfc.xref.status.500.2" title="500 Internal Server Error">Section&nbsp;6.6.1</a> 
+                  <td class="left"><a href="#status.500" id="rfc.xref.status.500.2" title="500 Internal Server Error">Section&nbsp;6.6.1</a> 
                   </td>
                </tr>
@@ -3553 +3553 @@
                   <td class="left">501</td>
                   <td class="left">Not Implemented</td>
-                  <td class="left"> <a href="#status.501" id="rfc.xref.status.501.2" title="501 Not Implemented">Section&nbsp;6.6.2</a> 
+                  <td class="left"><a href="#status.501" id="rfc.xref.status.501.2" title="501 Not Implemented">Section&nbsp;6.6.2</a> 
                   </td>
                </tr>
@@ -3559 +3559 @@
                   <td class="left">502</td>
                   <td class="left">Bad Gateway</td>
-                  <td class="left"> <a href="#status.502" id="rfc.xref.status.502.2" title="502 Bad Gateway">Section&nbsp;6.6.3</a> 
+                  <td class="left"><a href="#status.502" id="rfc.xref.status.502.2" title="502 Bad Gateway">Section&nbsp;6.6.3</a> 
                   </td>
                </tr>
@@ -3565 +3565 @@
                   <td class="left">503</td>
                   <td class="left">Service Unavailable</td>
-                  <td class="left"> <a href="#status.503" id="rfc.xref.status.503.2" title="503 Service Unavailable">Section&nbsp;6.6.4</a> 
+                  <td class="left"><a href="#status.503" id="rfc.xref.status.503.2" title="503 Service Unavailable">Section&nbsp;6.6.4</a> 
                   </td>
                </tr>
@@ -3571 +3571 @@
                   <td class="left">504</td>
                   <td class="left">Gateway Timeout</td>
-                  <td class="left"> <a href="#status.504" id="rfc.xref.status.504.2" title="504 Gateway Timeout">Section&nbsp;6.6.5</a> 
+                  <td class="left"><a href="#status.504" id="rfc.xref.status.504.2" title="504 Gateway Timeout">Section&nbsp;6.6.5</a> 
                   </td>
                </tr>
@@ -3577 +3577 @@
                   <td class="left">505</td>
                   <td class="left">HTTP Version Not Supported</td>
-                  <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> 
+                  <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> 
                   </td>
                </tr>
@@ -3680 +3680 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <td class="left"> <a href="#header.accept" id="rfc.xref.header.accept.3" title="Accept">Section&nbsp;5.3.2</a> 
+                  <td class="left"><a href="#header.accept" id="rfc.xref.header.accept.3" title="Accept">Section&nbsp;5.3.2</a> 
                   </td>
                </tr>
@@ -3687 +3687 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <td class="left"> <a href="#header.accept-charset" id="rfc.xref.header.accept-charset.2" title="Accept-Charset">Section&nbsp;5.3.3</a> 
+                  <td class="left"><a href="#header.accept-charset" id="rfc.xref.header.accept-charset.2" title="Accept-Charset">Section&nbsp;5.3.3</a> 
                   </td>
                </tr>
@@ -3694 +3694 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <td class="left"> <a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.3" title="Accept-Encoding">Section&nbsp;5.3.4</a> 
+                  <td class="left"><a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.3" title="Accept-Encoding">Section&nbsp;5.3.4</a> 
                   </td>
                </tr>
@@ -3701 +3701 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <td class="left"> <a href="#header.accept-language" id="rfc.xref.header.accept-language.3" title="Accept-Language">Section&nbsp;5.3.5</a> 
+                  <td class="left"><a href="#header.accept-language" id="rfc.xref.header.accept-language.3" title="Accept-Language">Section&nbsp;5.3.5</a> 
                   </td>
                </tr>
@@ -3708 +3708 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <td class="left"> <a href="#header.allow" id="rfc.xref.header.allow.3" title="Allow">Section&nbsp;7.4.1</a> 
+                  <td class="left"><a href="#header.allow" id="rfc.xref.header.allow.3" title="Allow">Section&nbsp;7.4.1</a> 
                   </td>
                </tr>
@@ -3715 +3715 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <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> 
+                  <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> 
                   </td>
                </tr>
@@ -3722 +3722 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <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> 
+                  <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> 
                   </td>
                </tr>
@@ -3729 +3729 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <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> 
+                  <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> 
                   </td>
                </tr>
@@ -3736 +3736 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <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> 
+                  <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> 
                   </td>
                </tr>
@@ -3743 +3743 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <td class="left"> <a href="#header.date" id="rfc.xref.header.date.3" title="Date">Section&nbsp;7.1.1.2</a> 
+                  <td class="left"><a href="#header.date" id="rfc.xref.header.date.3" title="Date">Section&nbsp;7.1.1.2</a> 
                   </td>
                </tr>
@@ -3750 +3750 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <td class="left"> <a href="#header.expect" id="rfc.xref.header.expect.3" title="Expect">Section&nbsp;5.1.1</a> 
+                  <td class="left"><a href="#header.expect" id="rfc.xref.header.expect.3" title="Expect">Section&nbsp;5.1.1</a> 
                   </td>
                </tr>
@@ -3757 +3757 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <td class="left"> <a href="#header.from" id="rfc.xref.header.from.2" title="From">Section&nbsp;5.5.1</a> 
+                  <td class="left"><a href="#header.from" id="rfc.xref.header.from.2" title="From">Section&nbsp;5.5.1</a> 
                   </td>
                </tr>
@@ -3764 +3764 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <td class="left"> <a href="#header.location" id="rfc.xref.header.location.4" title="Location">Section&nbsp;7.1.2</a> 
+                  <td class="left"><a href="#header.location" id="rfc.xref.header.location.4" title="Location">Section&nbsp;7.1.2</a> 
                   </td>
                </tr>
@@ -3771 +3771 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <td class="left"> <a href="#mime-version" id="rfc.xref.mime-version.1" title="MIME-Version">Appendix&nbsp;A.1</a> 
+                  <td class="left"><a href="#mime-version" id="rfc.xref.mime-version.1" title="MIME-Version">Appendix&nbsp;A.1</a> 
                   </td>
                </tr>
@@ -3778 +3778 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <td class="left"> <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.4" title="Max-Forwards">Section&nbsp;5.1.2</a> 
+                  <td class="left"><a href="#header.max-forwards" id="rfc.xref.header.max-forwards.4" title="Max-Forwards">Section&nbsp;5.1.2</a> 
                   </td>
                </tr>
@@ -3785 +3785 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <td class="left"> <a href="#header.referer" id="rfc.xref.header.referer.2" title="Referer">Section&nbsp;5.5.2</a> 
+                  <td class="left"><a href="#header.referer" id="rfc.xref.header.referer.2" title="Referer">Section&nbsp;5.5.2</a> 
                   </td>
                </tr>
@@ -3792 +3792 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <td class="left"> <a href="#header.retry-after" id="rfc.xref.header.retry-after.3" title="Retry-After">Section&nbsp;7.1.3</a> 
+                  <td class="left"><a href="#header.retry-after" id="rfc.xref.header.retry-after.3" title="Retry-After">Section&nbsp;7.1.3</a> 
                   </td>
                </tr>
@@ -3799 +3799 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <td class="left"> <a href="#header.server" id="rfc.xref.header.server.2" title="Server">Section&nbsp;7.4.2</a> 
+                  <td class="left"><a href="#header.server" id="rfc.xref.header.server.2" title="Server">Section&nbsp;7.4.2</a> 
                   </td>
                </tr>
@@ -3806 +3806 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <td class="left"> <a href="#header.user-agent" id="rfc.xref.header.user-agent.3" title="User-Agent">Section&nbsp;5.5.3</a> 
+                  <td class="left"><a href="#header.user-agent" id="rfc.xref.header.user-agent.3" title="User-Agent">Section&nbsp;5.5.3</a> 
                   </td>
                </tr>
@@ -3813 +3813 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <td class="left"> <a href="#header.vary" id="rfc.xref.header.vary.4" title="Vary">Section&nbsp;7.1.4</a> 
+                  <td class="left"><a href="#header.vary" id="rfc.xref.header.vary.4" title="Vary">Section&nbsp;7.1.4</a> 
                   </td>
                </tr>
@@ -3851 +3851 @@
                   <td class="left">compress</td>
                   <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>
-                  <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> 
+                  <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> 
                   </td>
                </tr>
@@ -3858 +3858 @@
                   <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>)
                   </td>
-                  <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> 
+                  <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> 
                   </td>
                </tr>
@@ -3864 +3864 @@
                   <td class="left">gzip</td>
                   <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>
-                  <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> 
+                  <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> 
                   </td>
                </tr>
@@ -3871 +3871 @@
                   <td class="left">Reserved (synonym for "no encoding" in <a href="#header.accept-encoding" class="smpl">Accept-Encoding</a>)
                   </td>
-                  <td class="left"> <a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.4" title="Accept-Encoding">Section&nbsp;5.3.4</a> 
+                  <td class="left"><a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.4" title="Accept-Encoding">Section&nbsp;5.3.4</a> 
                   </td>
                </tr>
@@ -3877 +3877 @@
                   <td class="left">x-compress</td>
                   <td class="left">Deprecated (alias for compress)</td>
-                  <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> 
+                  <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> 
                   </td>
                </tr>
@@ -3883 +3883 @@
                   <td class="left">x-gzip</td>
                   <td class="left">Deprecated (alias for gzip)</td>
-                  <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> 
+                  <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> 
                   </td>
                </tr>
@@ -3979 +3979 @@
          <tr>
             <td class="reference"><b id="Part1">[Part1]</b></td>
-            <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.
+            <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.
             </td>
          </tr>
          <tr>
             <td class="reference"><b id="Part4">[Part4]</b></td>
-            <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.
+            <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.
             </td>
          </tr>
          <tr>
             <td class="reference"><b id="Part5">[Part5]</b></td>
-            <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.
+            <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.
             </td>
          </tr>
          <tr>
             <td class="reference"><b id="Part6">[Part6]</b></td>
-            <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.
+            <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.
             </td>
          </tr>
          <tr>
             <td class="reference"><b id="Part7">[Part7]</b></td>
-            <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.
+            <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.
             </td>
          </tr>
@@ -4294 +4294 @@
          information present): 204, 404, 405, 414, 501.
       </p>
-      <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
+      <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
          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>).
       </p>
@@ -4475 +4475 @@
       <p id="rfc.section.E.2.p.1">Closed issues: </p>
       <ul>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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)"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
+         <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"
+         </li>
+         <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"
+         </li>
+         <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)"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
          </li>
       </ul>
@@ -4505 +4505 @@
       <p id="rfc.section.E.3.p.1">Closed issues: </p>
       <ul>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
          </li>
       </ul>

draft-ietf-httpbis/latest/p2-semantics.xml

@@ -13 +13 @@
   <!ENTITY SHOULD-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHOULD NOT</bcp14>">
   <!ENTITY ID-VERSION "latest">
-  <!ENTITY ID-MONTH "June">
+  <!ENTITY ID-MONTH "July">
   <!ENTITY ID-YEAR "2013">
   <!ENTITY mdash "&#8212;">

draft-ietf-httpbis/latest/p4-conditional.html

@@ -440 +440 @@
   }
   @top-right {
-       content: "June 2013";
+       content: "July 2013";
   }
   @top-center {
@@ -449 +449 @@
   }
   @bottom-center {
-       content: "Expires December 5, 2013";
+       content: "Expires January 2, 2014";
   }
   @bottom-right {
@@ -486 +486 @@
       <link href="p2-semantics.html" rel="prev">
       <link href="p5-range.html" rel="next">
-      <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/">
+      <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/">
       <link rel="schema.dct" href="http://purl.org/dc/terms/">
       <meta name="dct.creator" content="Fielding, R.">
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p4-conditional-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2013-06-03">
+      <meta name="dct.issued" scheme="ISO8601" content="2013-07-01">
       <meta name="dct.replaces" content="urn:ietf:rfc:2616">
       <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.">
@@ -517 +517 @@
             </tr>
             <tr>
-               <td class="left">Expires: December 5, 2013</td>
-               <td class="right">June 3, 2013</td>
+               <td class="left">Expires: January 2, 2014</td>
+               <td class="right">July 1, 2013</td>
             </tr>
          </tbody>
@@ -545 +545 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on December 5, 2013.</p>
+      <p>This Internet-Draft will expire on January 2, 2014.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
@@ -783 +783 @@
   <a href="#header.etag" class="smpl">etagc</a>      = %x21 / %x23-7E / <a href="#imported.abnf" class="smpl">obs-text</a>
              ; <a href="#imported.abnf" class="smpl">VCHAR</a> except double quotes, plus obs-text
-</pre><div class="note" id="rfc.section.2.3.p.3"> 
-         <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
+</pre><div class="note" id="rfc.section.2.3.p.3">
+         <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
             tags.
          </p> 
@@ -897 +897 @@
 Content-Encoding: gzip
 
-<em>...binary data...</em></pre><div class="note" id="rfc.section.2.3.3.p.7"> 
-         <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
+<em>...binary data...</em></pre><div class="note" id="rfc.section.2.3.3.p.7">
+         <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
             from an unencoded representation to prevent conflicts during cache updates and range requests. In contrast, transfer codings
             (<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.
@@ -1023 +1023 @@
          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.
       </p>
-      <div class="note" id="rfc.section.3.3.p.9"> 
-         <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
+      <div class="note" id="rfc.section.3.3.p.9">
+         <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
             understanding of time.
          </p> 
@@ -1123 +1123 @@
          <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: 
             <ul>
-               <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>
+               <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>
             </ul> 
          </li>
@@ -1154 +1154 @@
                   <td class="left">304</td>
                   <td class="left">Not Modified</td>
-                  <td class="left"> <a href="#status.304" id="rfc.xref.status.304.1" title="304 Not Modified">Section&nbsp;4.1</a> 
+                  <td class="left"><a href="#status.304" id="rfc.xref.status.304.1" title="304 Not Modified">Section&nbsp;4.1</a> 
                   </td>
                </tr>
@@ -1160 +1160 @@
                   <td class="left">412</td>
                   <td class="left">Precondition Failed</td>
-                  <td class="left"> <a href="#status.412" id="rfc.xref.status.412.1" title="412 Precondition Failed">Section&nbsp;4.2</a> 
+                  <td class="left"><a href="#status.412" id="rfc.xref.status.412.1" title="412 Precondition Failed">Section&nbsp;4.2</a> 
                   </td>
                </tr>
@@ -1188 +1188 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <td class="left"> <a href="#header.etag" id="rfc.xref.header.etag.2" title="ETag">Section&nbsp;2.3</a> 
+                  <td class="left"><a href="#header.etag" id="rfc.xref.header.etag.2" title="ETag">Section&nbsp;2.3</a> 
                   </td>
                </tr>
@@ -1195 +1195 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <td class="left"> <a href="#header.if-match" id="rfc.xref.header.if-match.1" title="If-Match">Section&nbsp;3.1</a> 
+                  <td class="left"><a href="#header.if-match" id="rfc.xref.header.if-match.1" title="If-Match">Section&nbsp;3.1</a> 
                   </td>
                </tr>
@@ -1202 +1202 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <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> 
+                  <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> 
                   </td>
                </tr>
@@ -1209 +1209 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <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> 
+                  <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> 
                   </td>
                </tr>
@@ -1216 +1216 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <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> 
+                  <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> 
                   </td>
                </tr>
@@ -1223 +1223 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <td class="left"> <a href="#header.last-modified" id="rfc.xref.header.last-modified.2" title="Last-Modified">Section&nbsp;2.2</a> 
+                  <td class="left"><a href="#header.last-modified" id="rfc.xref.header.last-modified.2" title="Last-Modified">Section&nbsp;2.2</a> 
                   </td>
                </tr>
@@ -1256 +1256 @@
          <tr>
             <td class="reference"><b id="Part1">[Part1]</b></td>
-            <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.
+            <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.
             </td>
          </tr>
          <tr>
             <td class="reference"><b id="Part2">[Part2]</b></td>
-            <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.
+            <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.
             </td>
          </tr>
          <tr>
             <td class="reference"><b id="Part5">[Part5]</b></td>
-            <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.
+            <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.
             </td>
          </tr>
          <tr>
             <td class="reference"><b id="Part6">[Part6]</b></td>
-            <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.
+            <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.
             </td>
          </tr>
@@ -1368 +1368 @@
       <p id="rfc.section.D.1.p.1">Closed issues: </p>
       <ul>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
          </li>
       </ul>
       <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>
-      <p id="rfc.section.D.2.p.1"> </p>
+      <p id="rfc.section.D.2.p.1"></p>
       <ul>
          <li>Conformance criteria and considerations regarding error handling are now defined in Part 1.</li>
@@ -1395 +1395 @@
       <p id="rfc.section.D.3.p.1">Closed issues: </p>
       <ul>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
          </li>
       </ul>
@@ -1413 +1413 @@
       <p id="rfc.section.D.4.p.1">Closed issues: </p>
       <ul>
-         <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"
-         </li>
-         <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"
+         <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"
+         </li>
+         <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"
          </li>
       </ul>
       <p id="rfc.section.D.4.p.2">Partly resolved issues: </p>
       <ul>
-         <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"
+         <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"
          </li>
       </ul>

draft-ietf-httpbis/latest/p4-conditional.xml

@@ -13 +13 @@
   <!ENTITY SHOULD-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHOULD NOT</bcp14>">
   <!ENTITY ID-VERSION "latest">
-  <!ENTITY ID-MONTH "June">
+  <!ENTITY ID-MONTH "July">
   <!ENTITY ID-YEAR "2013">
   <!ENTITY Note "<x:h xmlns:x='http://purl.org/net/xml2rfc/ext'>Note:</x:h>">

draft-ietf-httpbis/latest/p5-range.html

@@ -440 +440 @@
   }
   @top-right {
-       content: "June 2013";
+       content: "July 2013";
   }
   @top-center {
@@ -449 +449 @@
   }
   @bottom-center {
-       content: "Expires December 22, 2013";
+       content: "Expires January 2, 2014";
   }
   @bottom-right {
@@ -486 +486 @@
       <link href="p4-conditional.html" rel="prev">
       <link href="p6-cache.html" rel="next">
-      <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/">
+      <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/">
       <link rel="schema.dct" href="http://purl.org/dc/terms/">
       <meta name="dct.creator" content="Fielding, R.">
@@ -492 +492 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2013-06-20">
+      <meta name="dct.issued" scheme="ISO8601" content="2013-07-01">
       <meta name="dct.replaces" content="urn:ietf:rfc:2616">
       <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.">
@@ -518 +518 @@
             </tr>
             <tr>
-               <td class="left">Expires: December 22, 2013</td>
+               <td class="left">Expires: January 2, 2014</td>
                <td class="right">J. Reschke, Editor</td>
             </tr>
@@ -527 +527 @@
             <tr>
                <td class="left"></td>
-               <td class="right">June 20, 2013</td>
+               <td class="right">July 1, 2013</td>
             </tr>
          </tbody>
@@ -552 +552 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on December 22, 2013.</p>
+      <p>This Internet-Draft will expire on January 2, 2014.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
@@ -662 +662 @@
       <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"
 </pre><div id="rule.ranges-specifier">
-         <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>
+         <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>
       </div>
       <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>
@@ -878 +878 @@
 </pre><p id="rfc.section.4.2.p.7">and this second example illustrates when the complete length is unknown:</p>
       <div id="rfc.figure.u.21"></div><pre class="text">  Content-Range: bytes 42-1233/*
-</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.
+</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.
       </p>
       <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:
@@ -932 +932 @@
 Date: Fri, 20 Jan 2012 15:41:54 GMT
 Content-Range: bytes */47022
-</pre><div class="note" id="rfc.section.4.4.p.4"> 
-         <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
+</pre><div class="note" id="rfc.section.4.4.p.4">
+         <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
             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.
          </p> 
@@ -996 +996 @@
                   <td class="left">206</td>
                   <td class="left">Partial Content</td>
-                  <td class="left"> <a href="#status.206" id="rfc.xref.status.206.1" title="206 Partial Content">Section&nbsp;4.1</a> 
+                  <td class="left"><a href="#status.206" id="rfc.xref.status.206.1" title="206 Partial Content">Section&nbsp;4.1</a> 
                   </td>
                </tr>
@@ -1002 +1002 @@
                   <td class="left">416</td>
                   <td class="left">Range Not Satisfiable</td>
-                  <td class="left"> <a href="#status.416" id="rfc.xref.status.416.1" title="416 Range Not Satisfiable">Section&nbsp;4.4</a> 
+                  <td class="left"><a href="#status.416" id="rfc.xref.status.416.1" title="416 Range Not Satisfiable">Section&nbsp;4.4</a> 
                   </td>
                </tr>
@@ -1030 +1030 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <td class="left"> <a href="#header.accept-ranges" id="rfc.xref.header.accept-ranges.3" title="Accept-Ranges">Section&nbsp;2.3</a> 
+                  <td class="left"><a href="#header.accept-ranges" id="rfc.xref.header.accept-ranges.3" title="Accept-Ranges">Section&nbsp;2.3</a> 
                   </td>
                </tr>
@@ -1037 +1037 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <td class="left"> <a href="#header.content-range" id="rfc.xref.header.content-range.3" title="Content-Range">Section&nbsp;4.2</a> 
+                  <td class="left"><a href="#header.content-range" id="rfc.xref.header.content-range.3" title="Content-Range">Section&nbsp;4.2</a> 
                   </td>
                </tr>
@@ -1044 +1044 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <td class="left"> <a href="#header.if-range" id="rfc.xref.header.if-range.2" title="If-Range">Section&nbsp;3.2</a> 
+                  <td class="left"><a href="#header.if-range" id="rfc.xref.header.if-range.2" title="If-Range">Section&nbsp;3.2</a> 
                   </td>
                </tr>
@@ -1051 +1051 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <td class="left"> <a href="#header.range" id="rfc.xref.header.range.4" title="Range">Section&nbsp;3.1</a> 
+                  <td class="left"><a href="#header.range" id="rfc.xref.header.range.4" title="Range">Section&nbsp;3.1</a> 
                   </td>
                </tr>
@@ -1079 +1079 @@
          <tr>
             <td class="reference"><b id="Part1">[Part1]</b></td>
-            <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.
+            <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.
             </td>
          </tr>
          <tr>
             <td class="reference"><b id="Part2">[Part2]</b></td>
-            <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.
+            <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.
             </td>
          </tr>
          <tr>
             <td class="reference"><b id="Part4">[Part4]</b></td>
-            <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.
+            <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.
             </td>
          </tr>
          <tr>
             <td class="reference"><b id="Part6">[Part6]</b></td>
-            <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.
+            <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.
             </td>
          </tr>
@@ -1156 +1156 @@
       <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.
       </p>
-      <p id="rfc.section.A.p.3"> </p>
+      <p id="rfc.section.A.p.3"></p>
       <dl>
          <dt>Type name:</dt>
@@ -1178 +1178 @@
          <dd>HTTP components supporting multiple ranges in a single request.</dd>
          <dt>Additional information:</dt>
-         <dd> 
+         <dd>
             <dl>
                <dt>Magic number(s):</dt>
@@ -1310 +1310 @@
       <p id="rfc.section.E.1.p.1">Closed issues: </p>
       <ul>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
          </li>
       </ul>
       <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>
-      <p id="rfc.section.E.2.p.1"> </p>
+      <p id="rfc.section.E.2.p.1"></p>
       <ul>
          <li>Conformance criteria and considerations regarding error handling are now defined in Part 1.</li>
@@ -1329 +1329 @@
       <p id="rfc.section.E.3.p.1">Closed issues: </p>
       <ul>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
          </li>
       </ul>
@@ -1341 +1341 @@
       <p id="rfc.section.E.4.p.1">Closed issues: </p>
       <ul>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
          </li>
       </ul>

draft-ietf-httpbis/latest/p5-range.xml

@@ -13 +13 @@
   <!ENTITY SHOULD-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHOULD NOT</bcp14>">
   <!ENTITY ID-VERSION "latest">
-  <!ENTITY ID-MONTH "June">
+  <!ENTITY ID-MONTH "July">
   <!ENTITY ID-YEAR "2013">
   <!ENTITY Note "<x:h xmlns:x='http://purl.org/net/xml2rfc/ext'>Note:</x:h>">

draft-ietf-httpbis/latest/p6-cache.html

@@ -443 +443 @@
   }
   @top-right {
-       content: "June 2013";
+       content: "July 2013";
   }
   @top-center {
@@ -452 +452 @@
   }
   @bottom-center {
-       content: "Expires December 6, 2013";
+       content: "Expires January 2, 2014";
   }
   @bottom-right {
@@ -492 +492 @@
       <link href="p5-range.html" rel="prev">
       <link href="p7-auth.html" rel="next">
-      <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/">
+      <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/">
       <link rel="schema.dct" href="http://purl.org/dc/terms/">
       <meta name="dct.creator" content="Fielding, R.">
@@ -498 +498 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2013-06-04">
+      <meta name="dct.issued" scheme="ISO8601" content="2013-07-01">
       <meta name="dct.replaces" content="urn:ietf:rfc:2616">
       <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.">
@@ -524 +524 @@
             </tr>
             <tr>
-               <td class="left">Expires: December 6, 2013</td>
+               <td class="left">Expires: January 2, 2014</td>
                <td class="right">J. Reschke, Editor</td>
             </tr>
@@ -533 +533 @@
             <tr>
                <td class="left"></td>
-               <td class="right">June 4, 2013</td>
+               <td class="right">July 1, 2013</td>
             </tr>
          </tbody>
@@ -559 +559 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on December 6, 2013.</p>
+      <p>This Internet-Draft will expire on January 2, 2014.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
@@ -886 +886 @@
       </p>
       <p id="rfc.section.4.1.p.11">When calculating freshness, to avoid common problems in date parsing:</p>
-      <p id="rfc.section.4.1.p.12"> </p>
+      <p id="rfc.section.4.1.p.12"></p>
       <ul>
          <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.
@@ -932 +932 @@
          present.
       </p>
-      <div class="note" id="rfc.section.4.1.2.p.5"> 
-         <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,
+      <div class="note" id="rfc.section.4.1.2.p.5">
+         <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,
             this has not been widely implemented. Therefore, origin servers are encouraged to send explicit directives (e.g., Cache-Control:
             no-cache) if they wish to preclude caching.
@@ -945 +945 @@
       </p>
       <p id="rfc.section.4.1.3.p.2">The following data is used for the age calculation:</p>
-      <p id="rfc.section.4.1.3.p.3"> <dfn>age_value</dfn>  
+      <p id="rfc.section.4.1.3.p.3"><dfn>age_value</dfn> 
       </p>
       <ul class="empty">
@@ -951 +951 @@
          </li>
       </ul>
-      <p id="rfc.section.4.1.3.p.4"> <dfn>date_value</dfn>  
+      <p id="rfc.section.4.1.3.p.4"><dfn>date_value</dfn> 
       </p>
       <ul class="empty">
@@ -957 +957 @@
          </li>
       </ul>
-      <p id="rfc.section.4.1.3.p.5"> <dfn>now</dfn>  
+      <p id="rfc.section.4.1.3.p.5"><dfn>now</dfn> 
       </p>
       <ul class="empty">
@@ -963 +963 @@
          </li>
       </ul>
-      <p id="rfc.section.4.1.3.p.6"> <dfn>request_time</dfn>  
+      <p id="rfc.section.4.1.3.p.6"><dfn>request_time</dfn> 
       </p>
       <ul class="empty">
          <li>The current value of the clock at the host at the time the request resulting in the stored response was made.</li>
       </ul>
-      <p id="rfc.section.4.1.3.p.7"> <dfn>response_time</dfn>  
+      <p id="rfc.section.4.1.3.p.7"><dfn>response_time</dfn> 
       </p>
       <ul class="empty">
@@ -1027 +1027 @@
       </p>
       <p id="rfc.section.4.2.p.5">Cache handling of a response to a conditional request is dependent upon its status code:</p>
-      <p id="rfc.section.4.2.p.6"> </p>
+      <p id="rfc.section.4.2.p.6"></p>
       <ul>
          <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>.
@@ -1149 +1149 @@
       <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.
       </p>
-      <div class="note" id="rfc.section.7.2.p.3"> 
-         <p> <b>Note:</b> Some HTTP/1.0 caches might not implement Cache-Control.
+      <div class="note" id="rfc.section.7.2.p.3">
+         <p><b>Note:</b> Some HTTP/1.0 caches might not implement Cache-Control.
          </p> 
       </div>
@@ -1170 +1170 @@
       <p id="rfc.section.7.2.1.1.p.1">Argument syntax: </p>
       <ul class="empty">
-         <li> <a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.2.1</a>)
+         <li><a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.2.1</a>)
          </li>
       </ul>
@@ -1177 +1177 @@
          stale response.
       </p>
-      <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.
+      <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.
       </p>
       <div id="rfc.iref.m.2"></div>
@@ -1183 +1183 @@
       <p id="rfc.section.7.2.1.2.p.1">Argument syntax: </p>
       <ul class="empty">
-         <li> <a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.2.1</a>)
+         <li><a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.2.1</a>)
          </li>
       </ul>
@@ -1191 +1191 @@
          to accept a stale response of any age.
       </p>
-      <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.
+      <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.
       </p>
       <div id="rfc.iref.m.3"></div>
@@ -1197 +1197 @@
       <p id="rfc.section.7.2.1.3.p.1">Argument syntax: </p>
       <ul class="empty">
-         <li> <a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.2.1</a>)
+         <li><a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.2.1</a>)
          </li>
       </ul>
@@ -1204 +1204 @@
          for at least the specified number of seconds.
       </p>
-      <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.
+      <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.
       </p>
       <div id="rfc.iref.n.1"></div>
@@ -1257 +1257 @@
       </p>
       <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>
-      <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.
+      <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.
          Also, no-cache response directives with field-names are often handled by caches as if an unqualified no-cache directive was
          received; i.e., the special handling for the qualified form is not widely implemented.
       </p>
-      <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).
+      <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).
       </p>
       <div id="rfc.iref.n.5"></div>
@@ -1292 +1292 @@
       </p>
       <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>
-      <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
+      <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
          content. Also, private response directives with field-names are often handled by caches as if an unqualified private directive
          was received; i.e., the special handling for the qualified form is not widely implemented.
       </p>
-      <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).
+      <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).
       </p>
       <div id="rfc.iref.p.4"></div>
@@ -1307 +1307 @@
       <p id="rfc.section.7.2.2.8.p.1">Argument syntax: </p>
       <ul class="empty">
-         <li> <a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.2.1</a>)
+         <li><a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.2.1</a>)
          </li>
       </ul>
@@ -1313 +1313 @@
          number of seconds.
       </p>
-      <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.
+      <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.
       </p>
       <div id="rfc.iref.s.4"></div>
@@ -1319 +1319 @@
       <p id="rfc.section.7.2.2.9.p.1">Argument syntax: </p>
       <ul class="empty">
-         <li> <a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.2.1</a>)
+         <li><a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.2.1</a>)
          </li>
       </ul>
@@ -1325 +1325 @@
          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.
       </p>
-      <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.
+      <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.
       </p>
       <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>
@@ -1404 +1404 @@
          understand <a href="#header.cache-control" class="smpl">Cache-Control</a> from serving a cached response.
       </p>
-      <div class="note" id="rfc.section.7.4.p.8"> 
-         <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:
+      <div class="note" id="rfc.section.7.4.p.8">
+         <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:
             no-cache" in them.
          </p> 
@@ -1483 +1483 @@
       <div id="rfc.iref.50"></div>
       <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>
-      <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,
+      <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,
          or modifying the representation data, unless this Warning code already appears in the response.
       </p>
@@ -1518 +1518 @@
       <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>
       <p id="rfc.section.9.1.2.p.1">New extension directives ought to consider defining:</p>
-      <p id="rfc.section.9.1.2.p.2"> </p>
+      <p id="rfc.section.9.1.2.p.2"></p>
       <ul>
          <li>What it means for a directive to be specified multiple times,</li>
@@ -1541 +1541 @@
                <tr>
                   <td class="left">max-age</td>
-                  <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> 
+                  <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> 
                   </td>
                </tr>
                <tr>
                   <td class="left">max-stale</td>
-                  <td class="left"> <a href="#cache-request-directive.max-stale" title="max-stale">Section&nbsp;7.2.1.2</a> 
+                  <td class="left"><a href="#cache-request-directive.max-stale" title="max-stale">Section&nbsp;7.2.1.2</a> 
                   </td>
                </tr>
                <tr>
                   <td class="left">min-fresh</td>
-                  <td class="left"> <a href="#cache-request-directive.min-fresh" title="min-fresh">Section&nbsp;7.2.1.3</a> 
+                  <td class="left"><a href="#cache-request-directive.min-fresh" title="min-fresh">Section&nbsp;7.2.1.3</a> 
                   </td>
                </tr>
                <tr>
                   <td class="left">must-revalidate</td>
-                  <td class="left"> <a href="#cache-response-directive.must-revalidate" title="must-revalidate">Section&nbsp;7.2.2.1</a> 
+                  <td class="left"><a href="#cache-response-directive.must-revalidate" title="must-revalidate">Section&nbsp;7.2.2.1</a> 
                   </td>
                </tr>
                <tr>
                   <td class="left">no-cache</td>
-                  <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> 
+                  <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> 
                   </td>
                </tr>
                <tr>
                   <td class="left">no-store</td>
-                  <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> 
+                  <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> 
                   </td>
                </tr>
                <tr>
                   <td class="left">no-transform</td>
-                  <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> 
+                  <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> 
                   </td>
                </tr>
                <tr>
                   <td class="left">only-if-cached</td>
-                  <td class="left"> <a href="#cache-request-directive.only-if-cached" title="only-if-cached">Section&nbsp;7.2.1.7</a> 
+                  <td class="left"><a href="#cache-request-directive.only-if-cached" title="only-if-cached">Section&nbsp;7.2.1.7</a> 
                   </td>
                </tr>
                <tr>
                   <td class="left">private</td>
-                  <td class="left"> <a href="#cache-response-directive.private" title="private">Section&nbsp;7.2.2.6</a> 
+                  <td class="left"><a href="#cache-response-directive.private" title="private">Section&nbsp;7.2.2.6</a> 
                   </td>
                </tr>
                <tr>
                   <td class="left">proxy-revalidate</td>
-                  <td class="left"> <a href="#cache-response-directive.proxy-revalidate" title="proxy-revalidate">Section&nbsp;7.2.2.7</a> 
+                  <td class="left"><a href="#cache-response-directive.proxy-revalidate" title="proxy-revalidate">Section&nbsp;7.2.2.7</a> 
                   </td>
                </tr>
                <tr>
                   <td class="left">public</td>
-                  <td class="left"> <a href="#cache-response-directive.public" title="public">Section&nbsp;7.2.2.5</a> 
+                  <td class="left"><a href="#cache-response-directive.public" title="public">Section&nbsp;7.2.2.5</a> 
                   </td>
                </tr>
                <tr>
                   <td class="left">s-maxage</td>
-                  <td class="left"> <a href="#cache-response-directive.s-maxage" title="s-maxage">Section&nbsp;7.2.2.9</a> 
+                  <td class="left"><a href="#cache-response-directive.s-maxage" title="s-maxage">Section&nbsp;7.2.2.9</a> 
                   </td>
                </tr>
                <tr>
                   <td class="left">stale-if-error</td>
-                  <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> 
+                  <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> 
                   </td>
                </tr>
                <tr>
                   <td class="left">stale-while-revalidate</td>
-                  <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> 
+                  <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> 
                   </td>
                </tr>
@@ -1641 +1641 @@
                   <td class="left">110</td>
                   <td class="left">Response is Stale</td>
-                  <td class="left"> <a href="#warn.110" id="rfc.xref.warn.110.1" title="110 Response is Stale">Section&nbsp;7.5.1</a> 
+                  <td class="left"><a href="#warn.110" id="rfc.xref.warn.110.1" title="110 Response is Stale">Section&nbsp;7.5.1</a> 
                   </td>
                </tr>
@@ -1647 +1647 @@
                   <td class="left">111</td>
                   <td class="left">Revalidation Failed</td>
-                  <td class="left"> <a href="#warn.111" id="rfc.xref.warn.111.1" title="111 Revalidation Failed">Section&nbsp;7.5.2</a> 
+                  <td class="left"><a href="#warn.111" id="rfc.xref.warn.111.1" title="111 Revalidation Failed">Section&nbsp;7.5.2</a> 
                   </td>
                </tr>
@@ -1653 +1653 @@
                   <td class="left">112</td>
                   <td class="left">Disconnected Operation</td>
-                  <td class="left"> <a href="#warn.112" id="rfc.xref.warn.112.1" title="112 Disconnected Operation">Section&nbsp;7.5.3</a> 
+                  <td class="left"><a href="#warn.112" id="rfc.xref.warn.112.1" title="112 Disconnected Operation">Section&nbsp;7.5.3</a> 
                   </td>
                </tr>
@@ -1659 +1659 @@
                   <td class="left">113</td>
                   <td class="left">Heuristic Expiration</td>
-                  <td class="left"> <a href="#warn.113" id="rfc.xref.warn.113.1" title="113 Heuristic Expiration">Section&nbsp;7.5.4</a> 
+                  <td class="left"><a href="#warn.113" id="rfc.xref.warn.113.1" title="113 Heuristic Expiration">Section&nbsp;7.5.4</a> 
                   </td>
                </tr>
@@ -1665 +1665 @@
                   <td class="left">199</td>
                   <td class="left">Miscellaneous Warning</td>
-                  <td class="left"> <a href="#warn.199" id="rfc.xref.warn.199.1" title="199 Miscellaneous Warning">Section&nbsp;7.5.5</a> 
+                  <td class="left"><a href="#warn.199" id="rfc.xref.warn.199.1" title="199 Miscellaneous Warning">Section&nbsp;7.5.5</a> 
                   </td>
                </tr>
@@ -1671 +1671 @@
                   <td class="left">214</td>
                   <td class="left">Transformation Applied</td>
-                  <td class="left"> <a href="#warn.214" id="rfc.xref.warn.214.1" title="214 Transformation Applied">Section&nbsp;7.5.6</a> 
+                  <td class="left"><a href="#warn.214" id="rfc.xref.warn.214.1" title="214 Transformation Applied">Section&nbsp;7.5.6</a> 
                   </td>
                </tr>
@@ -1677 +1677 @@
                   <td class="left">299</td>
                   <td class="left">Miscellaneous Persistent Warning</td>
-                  <td class="left"> <a href="#warn.299" id="rfc.xref.warn.299.1" title="299 Miscellaneous Persistent Warning">Section&nbsp;7.5.7</a> 
+                  <td class="left"><a href="#warn.299" id="rfc.xref.warn.299.1" title="299 Miscellaneous Persistent Warning">Section&nbsp;7.5.7</a> 
                   </td>
                </tr>
@@ -1705 +1705 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <td class="left"> <a href="#header.age" id="rfc.xref.header.age.3" title="Age">Section&nbsp;7.1</a> 
+                  <td class="left"><a href="#header.age" id="rfc.xref.header.age.3" title="Age">Section&nbsp;7.1</a> 
                   </td>
                </tr>
@@ -1712 +1712 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <td class="left"> <a href="#header.cache-control" id="rfc.xref.header.cache-control.2" title="Cache-Control">Section&nbsp;7.2</a> 
+                  <td class="left"><a href="#header.cache-control" id="rfc.xref.header.cache-control.2" title="Cache-Control">Section&nbsp;7.2</a> 
                   </td>
                </tr>
@@ -1719 +1719 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <td class="left"> <a href="#header.expires" id="rfc.xref.header.expires.4" title="Expires">Section&nbsp;7.3</a> 
+                  <td class="left"><a href="#header.expires" id="rfc.xref.header.expires.4" title="Expires">Section&nbsp;7.3</a> 
                   </td>
                </tr>
@@ -1726 +1726 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <td class="left"> <a href="#header.pragma" id="rfc.xref.header.pragma.2" title="Pragma">Section&nbsp;7.4</a> 
+                  <td class="left"><a href="#header.pragma" id="rfc.xref.header.pragma.2" title="Pragma">Section&nbsp;7.4</a> 
                   </td>
                </tr>
@@ -1733 +1733 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <td class="left"> <a href="#header.warning" id="rfc.xref.header.warning.5" title="Warning">Section&nbsp;7.5</a> 
+                  <td class="left"><a href="#header.warning" id="rfc.xref.header.warning.5" title="Warning">Section&nbsp;7.5</a> 
                   </td>
                </tr>
@@ -1773 +1773 @@
          <tr>
             <td class="reference"><b id="Part1">[Part1]</b></td>
-            <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.
+            <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.
             </td>
          </tr>
          <tr>
             <td class="reference"><b id="Part2">[Part2]</b></td>
-            <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.
+            <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.
             </td>
          </tr>
          <tr>
             <td class="reference"><b id="Part4">[Part4]</b></td>
-            <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.
+            <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.
             </td>
          </tr>
          <tr>
             <td class="reference"><b id="Part5">[Part5]</b></td>
-            <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.
+            <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.
             </td>
          </tr>
          <tr>
             <td class="reference"><b id="Part7">[Part7]</b></td>
-            <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.
+            <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.
             </td>
          </tr>
@@ -1965 +1965 @@
       <p id="rfc.section.D.1.p.1">Closed issues: </p>
       <ul>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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'"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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'"
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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'"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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'"
          </li>
       </ul>
@@ -1985 +1985 @@
       <p id="rfc.section.D.2.p.1">Closed issues: </p>
       <ul>
-         <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'"
+         <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'"
          </li>
       </ul>
@@ -1997 +1997 @@
       <p id="rfc.section.D.3.p.1">Closed issues: </p>
       <ul>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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.
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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.
          </li>
       </ul>
@@ -2009 +2009 @@
       <p id="rfc.section.D.4.p.1">Closed issues: </p>
       <ul>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
          </li>
       </ul>

draft-ietf-httpbis/latest/p6-cache.xml

@@ -13 +13 @@
   <!ENTITY SHOULD-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHOULD NOT</bcp14>">
   <!ENTITY ID-VERSION "latest">
-  <!ENTITY ID-MONTH "June">
+  <!ENTITY ID-MONTH "July">
   <!ENTITY ID-YEAR "2013">
   <!ENTITY mdash "&#8212;">

draft-ietf-httpbis/latest/p7-auth.html

@@ -440 +440 @@
   }
   @top-right {
-       content: "June 2013";
+       content: "July 2013";
   }
   @top-center {
@@ -449 +449 @@
   }
   @bottom-center {
-       content: "Expires December 11, 2013";
+       content: "Expires January 2, 2014";
   }
   @bottom-right {
@@ -484 +484 @@
       <link rel="Appendix" title="D Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.D">
       <link href="p6-cache.html" rel="prev">
-      <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/">
+      <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/">
       <link rel="schema.dct" href="http://purl.org/dc/terms/">
       <meta name="dct.creator" content="Fielding, R.">
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p7-auth-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2013-06-09">
+      <meta name="dct.issued" scheme="ISO8601" content="2013-07-01">
       <meta name="dct.replaces" content="urn:ietf:rfc:2616">
       <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.">
@@ -517 +517 @@
             <tr>
                <td class="left">Intended status: Standards Track</td>
-               <td class="right">June 9, 2013</td>
+               <td class="right">July 1, 2013</td>
             </tr>
             <tr>
-               <td class="left">Expires: December 11, 2013</td>
+               <td class="left">Expires: January 2, 2014</td>
                <td class="right"></td>
             </tr>
@@ -546 +546 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on December 11, 2013.</p>
+      <p>This Internet-Draft will expire on January 2, 2014.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
@@ -659 +659 @@
       </p>
       <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> ) ]
-</pre><div class="note" id="rfc.section.2.1.p.8"> 
-         <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
+</pre><div class="note" id="rfc.section.2.1.p.8">
+         <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
             of a challenge can itself contain a comma-separated list of authentication parameters.
          </p> 
       </div>
-      <div class="note" id="rfc.section.2.1.p.9"> 
-         <p> <b>Note:</b> Many clients fail to parse challenges containing unknown schemes. A workaround for this problem is to list well-supported
+      <div class="note" id="rfc.section.2.1.p.9">
+         <p><b>Note:</b> Many clients fail to parse challenges containing unknown schemes. A workaround for this problem is to list well-supported
             schemes (such as "basic") first. 
          </p> 
@@ -779 +779 @@
          "type" and "title", and another one for the "Basic" scheme with a realm value of "simple".
       </p>
-      <div class="note" id="rfc.section.4.4.p.6"> 
-         <p> <b>Note:</b> The challenge grammar production uses the list syntax as well. Therefore, a sequence of comma, whitespace, and comma can be
+      <div class="note" id="rfc.section.4.4.p.6">
+         <p><b>Note:</b> The challenge grammar production uses the list syntax as well. Therefore, a sequence of comma, whitespace, and comma can be
             considered both as applying to the preceding challenge, or to be an empty entry in the list of challenges. In practice, this
             ambiguity does not affect the semantics of the header field value and thus is harmless.
@@ -804 +804 @@
          work:
       </p>
-      <p id="rfc.section.5.1.2.p.2"> </p>
+      <p id="rfc.section.5.1.2.p.2"></p>
       <ul>
          <li>
@@ -828 +828 @@
                can use a generic parser that applies to all authentication schemes.
             </p>
-            <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
+            <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
                repeated for new parameters.
             </p>
@@ -869 +869 @@
                   <td class="left">401</td>
                   <td class="left">Unauthorized</td>
-                  <td class="left"> <a href="#status.401" id="rfc.xref.status.401.1" title="401 Unauthorized">Section&nbsp;3.1</a> 
+                  <td class="left"><a href="#status.401" id="rfc.xref.status.401.1" title="401 Unauthorized">Section&nbsp;3.1</a> 
                   </td>
                </tr>
@@ -875 +875 @@
                   <td class="left">407</td>
                   <td class="left">Proxy Authentication Required</td>
-                  <td class="left"> <a href="#status.407" id="rfc.xref.status.407.1" title="407 Proxy Authentication Required">Section&nbsp;3.2</a> 
+                  <td class="left"><a href="#status.407" id="rfc.xref.status.407.1" title="407 Proxy Authentication Required">Section&nbsp;3.2</a> 
                   </td>
                </tr>
@@ -903 +903 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <td class="left"> <a href="#header.authorization" id="rfc.xref.header.authorization.3" title="Authorization">Section&nbsp;4.1</a> 
+                  <td class="left"><a href="#header.authorization" id="rfc.xref.header.authorization.3" title="Authorization">Section&nbsp;4.1</a> 
                   </td>
                </tr>
@@ -910 +910 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <td class="left"> <a href="#header.proxy-authenticate" id="rfc.xref.header.proxy-authenticate.2" title="Proxy-Authenticate">Section&nbsp;4.2</a> 
+                  <td class="left"><a href="#header.proxy-authenticate" id="rfc.xref.header.proxy-authenticate.2" title="Proxy-Authenticate">Section&nbsp;4.2</a> 
                   </td>
                </tr>
@@ -917 +917 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <td class="left"> <a href="#header.proxy-authorization" id="rfc.xref.header.proxy-authorization.2" title="Proxy-Authorization">Section&nbsp;4.3</a> 
+                  <td class="left"><a href="#header.proxy-authorization" id="rfc.xref.header.proxy-authorization.2" title="Proxy-Authorization">Section&nbsp;4.3</a> 
                   </td>
                </tr>
@@ -924 +924 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <td class="left"> <a href="#header.www-authenticate" id="rfc.xref.header.www-authenticate.3" title="WWW-Authenticate">Section&nbsp;4.4</a> 
+                  <td class="left"><a href="#header.www-authenticate" id="rfc.xref.header.www-authenticate.3" title="WWW-Authenticate">Section&nbsp;4.4</a> 
                   </td>
                </tr>
@@ -978 +978 @@
          <tr>
             <td class="reference"><b id="Part1">[Part1]</b></td>
-            <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.
+            <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.
             </td>
          </tr>
          <tr>
             <td class="reference"><b id="Part2">[Part2]</b></td>
-            <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.
+            <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.
             </td>
          </tr>
          <tr>
             <td class="reference"><b id="Part6">[Part6]</b></td>
-            <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.
+            <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.
             </td>
          </tr>
@@ -1102 +1102 @@
       <p id="rfc.section.D.1.p.1">Closed issues: </p>
       <ul>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
          </li>
       </ul>
@@ -1116 +1116 @@
       <p id="rfc.section.D.2.p.1">Closed issues: </p>
       <ul>
-         <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"
+         <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"
          </li>
       </ul>
@@ -1126 +1126 @@
       <p id="rfc.section.D.3.p.1">Closed issues: </p>
       <ul>
-         <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"
+         <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"
          </li>
       </ul>
@@ -1132 +1132 @@
       <p id="rfc.section.D.4.p.1">Closed issues: </p>
       <ul>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
-         </li>
-         <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"
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
+         </li>
+         <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"
          </li>
       </ul>

draft-ietf-httpbis/latest/p7-auth.xml

@@ -13 +13 @@
   <!ENTITY SHOULD-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHOULD NOT</bcp14>">
   <!ENTITY ID-VERSION "latest">
-  <!ENTITY ID-MONTH "June">
+  <!ENTITY ID-MONTH "July">
   <!ENTITY ID-YEAR "2013">
   <!ENTITY mdash "&#8212;">