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

Timestamp:

19/05/13 08:09:53 (9 years ago)

Author:

fielding@…

Message:

(editorial) properly target the whitespace requirements to sender or recipient; move the requirement on parsing whitespace sequences to the field parsing section

File:

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

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

@@ -1256 +1256 @@
 <t anchor="rule.OWS">
    The OWS rule is used where zero or more linear whitespace octets might
-   appear. OWS &SHOULD; either not be generated or be generated as a single
-   SP. Multiple OWS octets that occur within field-content &SHOULD; either
-   be replaced with a single SP or transformed to all SP octets (each
-   octet other than SP replaced with SP) before interpreting the field value
-   or forwarding the message downstream.
+   appear. For protocol elements where optional whitespace is preferred to
+   improve readability, a sender &SHOULD; generate the optional whitespace
+   as a single SP; otherwise, a sender &SHOULD-NOT; generate optional
+   whitespace except as needed to white-out invalid or unwanted protocol
+   elements during in-place message filtering.
 </t>
 <t anchor="rule.RWS">
-   RWS is used when at least one linear whitespace octet is required to
-   separate field tokens. RWS &SHOULD; be generated as a single SP.
-   Multiple RWS octets that occur within field-content &SHOULD; either
-   be replaced with a single SP or transformed to all SP octets before
-   interpreting the field value or forwarding the message downstream.
+   The RWS rule is used when at least one linear whitespace octet is required
+   to separate field tokens. A sender &SHOULD; generate RWS as a single SP.
 </t>
 <t anchor="rule.BWS">
-   BWS is used where the grammar allows optional whitespace, for historical
-   reasons, but it &MUST-NOT; be generated in messages; recipients &MUST;
-   accept such bad optional whitespace and remove it before interpreting the
-   field value.
+   The BWS rule is used where the grammar allows optional whitespace only for
+   historical reasons. A sender &MUST-NOT; generate BWS in messages.
+   A recipient &MUST; parse for such bad whitespace and remove it before
+   interpreting the protocol element.
 </t>
 <t anchor="rule.whitespace">
@@ -1306 +1303 @@
    field value or after the last non-whitespace octet of the field value
    is ignored and &SHOULD; be removed before further processing (as this does
-   not change the meaning of the header field). 
+   not change the meaning of the header field).
+</t>
+<t>
+   A recipient of field-content containing multiple sequential octets of
+   optional (OWS) or required (RWS) whitespace &SHOULD; either replace the
+   sequence with a single SP or transform any non-SP octets in the sequence to
+   SP octets before interpreting the field value or forwarding the message
+   downstream.
 </t>
 <t>