Ignore:
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:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r2046 r2047  
    11931193</t>
    11941194<t>
    1195    New HTTP header fields &SHOULD; be registered with IANA in the
     1195   New HTTP header fields ought to be be registered with IANA in the
    11961196   Message Header Field Registry, as described in &iana-header-registry;.
    1197    Unrecognized header fields &MUST; be forwarded by a proxy unless the
     1197   A proxy &MUST; forward unrecognized header fields unless the
    11981198   field-name is listed in the <x:ref>Connection</x:ref> header field
    11991199   (<xref target="header.connection"/>) or the proxy is specifically
    1200    configured to block or otherwise transform such fields.
    1201    Unrecognized header fields &SHOULD; be ignored by other recipients.
     1200   configured to block, or otherwise transform, such fields.
     1201   Other recipients &SHOULD; ignore unrecognized header fields.
    12021202</t>
    12031203</section>
     
    12161216</t>
    12171217<t>
    1218    Multiple header fields with the same field name &MUST-NOT; be
    1219    sent in a message unless the entire field value for that
    1220    header field is defined as a comma-separated list [i.e., #(values)].
     1218   A sender &MUST-NOT; generate multiple header fields with the same field
     1219   name in a message unless either the entire field value for that
     1220   header field is defined as a comma-separated list [i.e., #(values)]
     1221   or the header field is a well-known exception (as noted below).
    12211222</t>
    12221223<t>
     
    18731874</artwork></figure>
    18741875<t>
    1875    All transfer-coding names are case-insensitive and &SHOULD; be registered
     1876   All transfer-coding names are case-insensitive and ought to be registered
    18761877   within the HTTP Transfer Coding registry, as defined in
    18771878   <xref target="transfer.coding.registry"/>.
     
    30863087   the family of Hypertext Transfer Protocols, as defined by the HTTP
    30873088   version rules of <xref target="http.version"/> and future updates to this
    3088    specification. Additional tokens can be registered with IANA using the
     3089   specification. Additional tokens ought to be registered with IANA using the
    30893090   registration procedure defined in <xref target="upgrade.token.registry"/>.
    30903091</t>
Note: See TracChangeset for help on using the changeset viewer.