Changeset 1971 for draft-ietf-httpbis/latest/p1-messaging.html

Timestamp:

03/11/12 14:38:39 (9 years ago)

Author:

julian.reschke@…

Message:

note removal of multipart/byteranges special case as change from RFC 2616

File:

• draft-ietf-httpbis/latest/p1-messaging.html (modified) (1 diff)

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

@@ -2839 +2839 @@
       <p id="rfc.section.A.2.p.6">Remove reference to non-existent identity transfer-coding value tokens. (Sections <a href="#message.body" title="Message Body">3.3</a> and <a href="#transfer.codings" title="Transfer Codings">4</a>)
       </p>
-      <p id="rfc.section.A.2.p.7">Clarification that the chunk length does not include the count of the octets in the chunk header and trailer. Furthermore
+      <p id="rfc.section.A.2.p.7">Remove special-case for "multipart/byteranges" in message body length detection. (<a href="#message.body.length" title="Message Body Length">Section&nbsp;3.3.3</a>)
+      </p>
+      <p id="rfc.section.A.2.p.8">Clarification that the chunk length does not include the count of the octets in the chunk header and trailer. Furthermore
          disallowed line folding in chunk extensions, and deprecate their use. (<a href="#chunked.encoding" title="Chunked Transfer Coding">Section&nbsp;4.1</a>)
       </p>
-      <p id="rfc.section.A.2.p.8">Update use of abs_path production from RFC 1808 to the path-absolute + query components of RFC 3986. State that the asterisk
+      <p id="rfc.section.A.2.p.9">Update use of abs_path production from RFC 1808 to the path-absolute + query components of RFC 3986. State that the asterisk
          form is allowed for the OPTIONS request method only. (<a href="#request-target" title="Request Target">Section&nbsp;5.3</a>)
       </p>
-      <p id="rfc.section.A.2.p.9">Clarify exactly when "close" connection options have to be sent; drop notion of header fields being "hop-by-hop" without being
+      <p id="rfc.section.A.2.p.10">Clarify exactly when "close" connection options have to be sent; drop notion of header fields being "hop-by-hop" without being
          listed in the Connection header field. (<a href="#header.connection" id="rfc.xref.header.connection.10" title="Connection">Section&nbsp;6.1</a>)
       </p>
-      <p id="rfc.section.A.2.p.10">Remove hard limit of two connections per server. Remove requirement to retry a sequence of requests as long it was idempotent.
+      <p id="rfc.section.A.2.p.11">Remove hard limit of two connections per server. Remove requirement to retry a sequence of requests as long it was idempotent.
          Remove requirements about when servers are allowed to close connections prematurely. (<a href="#persistent.connections" title="Persistent Connections">Section&nbsp;6.2</a>)
       </p>
-      <p id="rfc.section.A.2.p.11">Remove requirement to retry requests under certain circumstances when the server prematurely closes the connection. (<a href="#persistent.reuse" title="Reuse">Section&nbsp;6.2.2</a>)
-      </p>
-      <p id="rfc.section.A.2.p.12">Define the semantics of the <a href="#header.upgrade" class="smpl">Upgrade</a> header field in responses other than 101 (this was incorporated from <a href="#RFC2817" id="rfc.xref.RFC2817.3"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>). (<a href="#header.upgrade" id="rfc.xref.header.upgrade.3" title="Upgrade">Section&nbsp;6.3</a>)
-      </p>
-      <p id="rfc.section.A.2.p.13">Registration of Transfer Codings now requires IETF Review (<a href="#transfer.coding.registry" title="Transfer Coding Registry">Section&nbsp;7.4</a>)
-      </p>
-      <p id="rfc.section.A.2.p.14">Take over the Upgrade Token Registry, previously defined in <a href="http://tools.ietf.org/html/rfc2817#section-7.2">Section 7.2</a> of <a href="#RFC2817" id="rfc.xref.RFC2817.4"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>. (<a href="#upgrade.token.registry" title="Upgrade Token Registry">Section&nbsp;7.6</a>)
-      </p>
-      <p id="rfc.section.A.2.p.15">Empty list elements in list productions have been deprecated. (<a href="#abnf.extension" title="ABNF list extension: #rule">Appendix&nbsp;B</a>)
+      <p id="rfc.section.A.2.p.12">Remove requirement to retry requests under certain circumstances when the server prematurely closes the connection. (<a href="#persistent.reuse" title="Reuse">Section&nbsp;6.2.2</a>)
+      </p>
+      <p id="rfc.section.A.2.p.13">Define the semantics of the <a href="#header.upgrade" class="smpl">Upgrade</a> header field in responses other than 101 (this was incorporated from <a href="#RFC2817" id="rfc.xref.RFC2817.3"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>). (<a href="#header.upgrade" id="rfc.xref.header.upgrade.3" title="Upgrade">Section&nbsp;6.3</a>)
+      </p>
+      <p id="rfc.section.A.2.p.14">Registration of Transfer Codings now requires IETF Review (<a href="#transfer.coding.registry" title="Transfer Coding Registry">Section&nbsp;7.4</a>)
+      </p>
+      <p id="rfc.section.A.2.p.15">Take over the Upgrade Token Registry, previously defined in <a href="http://tools.ietf.org/html/rfc2817#section-7.2">Section 7.2</a> of <a href="#RFC2817" id="rfc.xref.RFC2817.4"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>. (<a href="#upgrade.token.registry" title="Upgrade Token Registry">Section&nbsp;7.6</a>)
+      </p>
+      <p id="rfc.section.A.2.p.16">Empty list elements in list productions have been deprecated. (<a href="#abnf.extension" title="ABNF list extension: #rule">Appendix&nbsp;B</a>)
       </p>
       <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="abnf.extension" href="#abnf.extension">ABNF list extension: #rule</a></h1>