Changeset 2012 for draft-ietf-httpbis

Timestamp:

29/11/12 00:26:24 (10 years ago)

Author:

mnot@…

Message:

Rewrite changes from 2616

File:

• draft-ietf-httpbis/latest/p1-messaging.xml (modified) (3 diffs)

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

@@ -4719 +4719 @@
 <section title="Changes from RFC 2616" anchor="changes.from.rfc.2616">
 <t>
-  Clarify that the string "HTTP" in the HTTP-version ABNF production is case
-  sensitive. Restrict the version numbers to be single digits due to the fact
-  that implementations are known to handle multi-digit version numbers
-  incorrectly.
+  The HTTP-version ABNF production has been clarified to be case-sensitive.
+  Additionally, version numbers has been restricted to single digits, due
+  to the fact that implementations are known to handle multi-digit version
+  numbers incorrectly.
   (<xref target="http.version"/>)
 </t>
 <t>
-  Take over the definition of "HTTPS" URI scheme, previously defined in
-  <xref target="RFC2818" x:fmt="of" x:sec="2.4"/>.
+  The "HTTPS" URI scheme is now defined by this specification; previously,
+  it was done in  <xref target="RFC2818" x:fmt="of" x:sec="2.4"/>.
   (<xref target="https.uri"/>)
 </t>
 <t>
-  Require that invalid whitespace around field-names be rejected.
-  Change ABNF productions for header fields to only define the field value.
+  Invalid whitespace around field-names is now required to be rejected, 
+  because accepting it represents a security vulnerability.
+  (<xref target="header.fields"/>)
+</t>
+<t>
+  The ABNF productions defining header fields now only list the field value.
   (<xref target="header.fields"/>)
 </t>
@@ -4742 +4746 @@
 </t>
 <t>  
-  The NUL octet is no longer allowed in comment and quoted-string
-  text. The quoted-pair rule no longer allows escaping control characters other than HTAB.
-  Non-ASCII content in header fields and reason phrase has been obsoleted and
-  made opaque (the TEXT rule was removed).
+  The NUL octet is no longer allowed in comment and quoted-string text.
   (<xref target="field.components"/>)
-</t>
-<t>
-  Require recipients to handle bogus "<x:ref>Content-Length</x:ref>" header
-  fields as errors.
+</t>  
+<t>
+  The quoted-pair rule no longer allows escaping control characters other than
+  HTAB.
+  (<xref target="field.components"/>)
+</t>
+<t>
+  Non-ASCII content in header fields and the reason phrase has been obsoleted
+  and made opaque (the TEXT rule was removed). 
+  (<xref target="field.components"/>)
+</t>
+<t>
+  Bogus "<x:ref>Content-Length</x:ref>" header fields are now required to be
+  handled as errors by recipients.
   (<xref target="header.content-length"/>)
 </t>
 <t>
-  Remove reference to non-existent identity transfer-coding value tokens.
+  The "identity" transfer-coding value token has been removed.
   (Sections <xref format="counter" target="message.body"/> and
   <xref format="counter" target="transfer.codings"/>)
 </t>
 <t>
-  Remove special-case for "multipart/byteranges" in message body length
-  detection; add CONNECT as special case.
+  "multipart/byteranges" is no longer a way of determining message body length
+  detection.
   (<xref target="message.body.length"/>)
 </t>
 <t>
-  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.
+  CONNECT is a new, special case in determining message body length.
+  (<xref target="message.body.length"/>)
+</t>
+<t>
+  Chunk length does not include the count of the octets in the
+  chunk header and trailer.
   (<xref target="chunked.encoding"/>)
 </t>
 <t>
-  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.
+  Use of chunk extensions is deprecated, and line folding in them is 
+  disallowed.
+  (<xref target="chunked.encoding"/>)
+</t>
+<t>
+  The path-absolute + query components of RFC3986 have been used to define the
+  request-target, instead of abs_path from RFC 1808.
   (<xref target="request-target"/>)
 </t>
 <t>
-  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.
+  The asterisk form of the request-target is only allowed in the OPTIONS
+  method.
+  (<xref target="request-target"/>)
+</t>
+<t>
+  Exactly when "close" connection options have to be sent has been clarified.
   (<xref target="header.connection"/>)
 </t>
-<t>
-  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.
+<t>  
+  "hop-by-hop" header fields are required to appear in the Connection header
+  field; just because they're defined as hop-by-hop in this specification
+  doesn't exempt them.
+  (<xref target="header.connection"/>)
+</t>
+<t>
+  The limit of two connections per server has been removed.
   (<xref target="persistent.connections"/>)
 </t>
 <t>
-  Remove requirement to retry requests under certain circumstances when the
-  server prematurely closes the connection.
+  An idempotent sequence of requests is no longer required to be retried.
+  (<xref target="persistent.connections"/>)
+</t>
+<t>
+  The requirement to retry requests under certain circumstances when the
+  server prematurely closes the connection has been removed.
   (<xref target="persistent.reuse"/>)
 </t>
 <t>
-  Define the semantics of the <x:ref>Upgrade</x:ref> header field in responses
-  other than 101 (this was incorporated from <xref target="RFC2817"/>).
+  Some extraneous requirements about when servers are allowed to close
+  connections prematurely have been removed.
+  (<xref target="persistent.connections"/>)
+</t>
+<t>
+  The semantics of the <x:ref>Upgrade</x:ref> header field is now defined in
+  responses other than 101 (this was incorporated from <xref
+  target="RFC2817"/>).
   (<xref target="header.upgrade"/>)
 </t>
@@ -4803 +4837 @@
 </t>
 <t>
-  Take over the Upgrade Token Registry, previously defined in
-  <xref target="RFC2817" x:fmt="of" x:sec="7.2"/>.
+  This specification now defines the Upgrade Token Registry, previously
+  defined in <xref target="RFC2817" x:fmt="of" x:sec="7.2"/>.
   (<xref target="upgrade.token.registry"/>)
 </t>