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

Timestamp:

13/11/08 19:41:14 (12 years ago)

Author:

julian.reschke@…

Message:

Explain rationale for OWS/BWS/RWS, do not use LWS production anymore (related to #36)

File:

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

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

@@ -488 +488 @@
 <t>
    Historically, HTTP/1.1 header field values allow linear white space folding across 
-   multiple lines. However, this specification deprecates its use; senders MUST NOT 
+   multiple lines. However, this specification deprecates its use; senders &MUST-NOT; 
    produce messages that include LWS folding (i.e., use the obs-fold rule), except
-   within the message/http media type <xref target="internet.media.type.message.http"/>. 
-   Receivers SHOULD still parse folded linear white space.
-</t>
-<t>
-    This specification uses three rules to denote the use of linear white space;
-    BWS ("Bad" White Space), OWS (Optional White Space), and RWS (Required White Space).
-</t>
-<t>
-        "Bad" white space is allowed by the BNF, but senders SHOULD NOT produce it in messages.
-        Receivers MUST accept it in incoming messages.
-</t>
-
+   within the message/http media type (<xref target="internet.media.type.message.http"/>). 
+   Receivers &SHOULD; still parse folded linear white space.
+</t>
+<t>
+   This specification uses three rules to denote the use of linear white space;
+   BWS ("Bad" White Space), OWS (Optional White Space), and RWS (Required White Space).
+</t>
+<t>
+   "Bad" white space is allowed by the BNF, but senders &SHOULD-NOT; produce it in messages.
+   Receivers &MUST; accept it in incoming messages.
+</t>
+<t>
+   Required white space is used when at least one linear white space character
+   is required to separate field tokens. In all such cases, a single SP character
+   &SHOULD; be used.
+</t>
 <t anchor="rule.whitespace">
   <x:anchor-alias value="BWS"/>
@@ -507 +511 @@
   <x:anchor-alias value="RWS"/>
   <x:anchor-alias value="obs-fold"/>
-  
 </t>
 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="OWS"/><iref primary="true" item="Grammar" subitem="RWS"/><iref primary="true" item="Grammar" subitem="BWS"/>
@@ -517 +520 @@
                  ; "bad" white space
   <x:ref>obs-fold</x:ref>       = <x:ref>CRLF</x:ref>
-                 ; <cref>to be explained: do not produce</cref>
 </artwork></figure>
 <t anchor="rule.TEXT">
@@ -528 +530 @@
 </t>
 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="TEXT"/>
-  <x:ref>TEXT</x:ref>           = %x20-7E / %x80-FF / <x:ref>LWS</x:ref>
-                 ; any <x:ref>OCTET</x:ref> except <x:ref>CTL</x:ref>s, but including <x:ref>LWS</x:ref>
+  <x:ref>TEXT</x:ref>           = %x20-7E / %x80-FF / <x:ref>OWS</x:ref>
+                 ; any <x:ref>OCTET</x:ref> except <x:ref>CTL</x:ref>s, but including <x:ref>OWS</x:ref>
 </artwork></figure>
 <t>
@@ -1196 +1198 @@
   <x:ref>message-header</x:ref> = <x:ref>field-name</x:ref> ":" [ <x:ref>field-value</x:ref> ]
   <x:ref>field-name</x:ref>     = <x:ref>token</x:ref>
-  <x:ref>field-value</x:ref>    = *( <x:ref>field-content</x:ref> / <x:ref>LWS</x:ref> )
+  <x:ref>field-value</x:ref>    = *( <x:ref>field-content</x:ref> / <x:ref>OWS</x:ref> )
   <x:ref>field-content</x:ref>  = &lt;field content&gt;
                    ; the <x:ref>OCTET</x:ref>s making up the field-value