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

Timestamp:

09/12/12 16:54:07 (8 years ago)

Author:

fielding@…

Message:

Clean up pseudo normative text regarding use of registered values; partly addresses #419

File:

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

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

@@ -1193 +1193 @@
 </t>
 <t>
-   New HTTP header fields &SHOULD; be registered with IANA in the
+   New HTTP header fields ought to be be registered with IANA in the
    Message Header Field Registry, as described in &iana-header-registry;.
-   Unrecognized header fields &MUST; be forwarded by a proxy unless the
+   A proxy &MUST; forward unrecognized header fields unless the
    field-name is listed in the <x:ref>Connection</x:ref> header field
    (<xref target="header.connection"/>) or the proxy is specifically
-   configured to block or otherwise transform such fields.
-   Unrecognized header fields &SHOULD; be ignored by other recipients.
+   configured to block, or otherwise transform, such fields.
+   Other recipients &SHOULD; ignore unrecognized header fields.
 </t>
 </section>
@@ -1216 +1216 @@
 </t>
 <t>
-   Multiple header fields with the same field name &MUST-NOT; be
-   sent in a message unless the entire field value for that
-   header field is defined as a comma-separated list [i.e., #(values)].
+   A sender &MUST-NOT; generate multiple header fields with the same field
+   name in a message unless either the entire field value for that
+   header field is defined as a comma-separated list [i.e., #(values)]
+   or the header field is a well-known exception (as noted below).
 </t>
 <t>
@@ -1873 +1874 @@
 </artwork></figure>
 <t>
-   All transfer-coding names are case-insensitive and &SHOULD; be registered
+   All transfer-coding names are case-insensitive and ought to be registered
    within the HTTP Transfer Coding registry, as defined in
    <xref target="transfer.coding.registry"/>.
@@ -3086 +3087 @@
    the family of Hypertext Transfer Protocols, as defined by the HTTP
    version rules of <xref target="http.version"/> and future updates to this
-   specification. Additional tokens can be registered with IANA using the
+   specification. Additional tokens ought to be registered with IANA using the
    registration procedure defined in <xref target="upgrade.token.registry"/>.
 </t>