Changeset 1891 for draft-ietf-httpbis/latest/p1-messaging.xml

Timestamp:

13/09/12 11:44:49 (10 years ago)

Author:

julian.reschke@…

Message:

Cleanup "Changes from RFC 2616" sections.

File:

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

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

@@ -4758 +4758 @@
 </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.
-  (<xref target="request-target"/>)
-</t>
-<t>
   Require that invalid whitespace around field-names be rejected.
+  Change ABNF productions for header fields to only define the field value.
   (<xref target="header.fields"/>)
 </t>
@@ -4781 +4776 @@
 </t>
 <t>
-  Empty list elements in list productions have been deprecated.
-  (<xref target="abnf.extension"/>)
-</t>
-<t>
-  Require recipients to handle bogus <x:ref>Content-Length</x:ref> header
+  Require recipients to handle bogus "<x:ref>Content-Length</x:ref>" header
   fields as errors.
   (<xref target="message.body"/>)
@@ -4801 +4792 @@
 </t>
 <t>
-  Registration of Transfer Codings now requires IETF Review
-  (<xref target="transfer.coding.registry"/>)
+  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.
+  (<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.
+  (<xref target="header.connection"/>)
 </t>
 <t>
@@ -4817 +4816 @@
 </t>
 <t>
-  Change ABNF productions for header fields to only define the field value.
-</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.
-  (<xref target="header.connection"/>)
-</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"/>).
@@ -4831 +4821 @@
 </t>
 <t>
+  Registration of Transfer Codings now requires IETF Review
+  (<xref target="transfer.coding.registry"/>)
+</t>
+<t>
   Take over the Upgrade Token Registry, previously defined in
   <xref target="RFC2817" x:fmt="of" x:sec="7.2"/>.
   (<xref target="upgrade.token.registry"/>)
+</t>
+<t>
+  Empty list elements in list productions have been deprecated.
+  (<xref target="abnf.extension"/>)
 </t>
 </section>