Ignore:
Timestamp:
Jul 30, 2010, 6:06:01 PM (9 years ago)
Author:
fielding@…
Message:

Replace lowercase should with less normative words, where possible.

File:
1 edited

Legend:

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

    r968 r969  
    263263   of received communication, and the expected behavior of recipients.
    264264   If the communication is considered in isolation, then successful
    265    actions should be reflected in corresponding changes to the
     265   actions ought to be reflected in corresponding changes to the
    266266   observable interface provided by servers. However, since multiple
    267267   clients might act in parallel and perhaps at cross-purposes, we
     
    11071107   empty line received where a Request-Line is expected. In other words, if
    11081108   the server is reading the protocol stream at the beginning of a
    1109    message and receives a CRLF first, it should ignore the CRLF.
     1109   message and receives a CRLF first, it &SHOULD; ignore the CRLF.
    11101110</t>
    11111111<t>
     
    13331333     Such a message might indicate an attempt to perform request or response
    13341334     smuggling (bypass of security-related checks on message routing or content)
    1335      and thus should be handled as an error.  The provided Content-Length &MUST;
     1335     and thus ought to be handled as an error.  The provided Content-Length &MUST;
    13361336     be removed, prior to forwarding the message downstream, or replaced with
    13371337     the real message-body length after the transfer-coding is decoded.
     
    16031603    meaning of the request when the origin server is improperly using
    16041604    a non-reserved URI character for a reserved purpose.  Implementors
    1605     should be aware that some pre-HTTP/1.1 proxies have been known to
     1605    need to be aware that some pre-HTTP/1.1 proxies have been known to
    16061606    rewrite the request-target.
    16071607  </t>
     
    33113311   The HTTP Upgrade Token Registry defines the name space for product
    33123312   tokens used to identify protocols in the Upgrade header field.
    3313    Each registered token should be associated with one or a set of
    3314    specifications, and with contact information.
    3315 </t>
    3316 <t>
    3317    Registrations should be allowed on a First Come First Served basis as
    3318    described in <xref target="RFC5226" x:sec="4.1" x:fmt="of"/>. These
    3319    specifications need not be IETF documents or be subject to IESG review, but
    3320    should obey the following rules:
     3313   Each registered token is associated with contact information and
     3314   an optional set of specifications that details how the connection
     3315   will be processed after it has been upgraded.
     3316</t>
     3317<t>
     3318   Registrations are allowed on a First Come First Served basis as
     3319   described in <xref target="RFC5226" x:sec="4.1" x:fmt="of"/>. The
     3320   specifications need not be IETF documents or be subject to IESG review.
     3321   Registrations are subject to the following rules:
    33213322  <list style="numbers">
    33223323    <t>A token, once registered, stays registered forever.</t>
     
    33243325       registration.</t>
    33253326    <t>The registration &MUST; name a point of contact.</t>
    3326     <t>The registration &MAY; name the documentation required for the
    3327        token.</t>
     3327    <t>The registration &MAY; name a set of specifications associated with that
     3328       token. Such specifications need not be publicly available.</t>
    33283329    <t>The responsible party &MAY; change the registration at any time.
    33293330       The IANA will keep a record of all such changes, and make them
     
    33373338  </list>
    33383339</t>
    3339 <t>
    3340    It is not required that specifications for upgrade tokens be made
    3341    publicly available, but the contact information for the registration
    3342    should be.
    3343 </t>
    33443340</section>
    33453341
     
    34533449<section title="Header Field Registration" anchor="header.field.registration">
    34543450<t>
    3455    The Message Header Field Registry located at <eref target="http://www.iana.org/assignments/message-headers/message-header-index.html"/> should be updated
     3451   The Message Header Field Registry located at <eref target="http://www.iana.org/assignments/message-headers/message-header-index.html"/> shall be updated
    34563452   with the permanent registrations below (see <xref target="RFC3864"/>):
    34573453</t>
     
    35303526   The entries for the "http" and "https" URI Schemes in the registry located at
    35313527   <eref target="http://www.iana.org/assignments/uri-schemes.html"/>
    3532    should be updated to point to Sections <xref target="http.uri" format="counter"/>
     3528   shall be updated to point to Sections <xref target="http.uri" format="counter"/>
    35333529   and <xref target="https.uri" format="counter"/> of this document
    35343530   (see <xref target="RFC4395"/>).
     
    36933689<t>
    36943690   The HTTP Transfer Codings Registry located at <eref target="http://www.iana.org/assignments/http-parameters"/>
    3695    should be updated with the registrations below:
     3691   shall be updated with the registrations below:
    36963692</t>
    36973693<texttable align="left" suppress-title="true" anchor="iana.transfer.coding.registration.table">
     
    37323728<t>
    37333729   The HTTP Status Code Registry located at <eref target="http://www.iana.org/assignments/http-upgrade-tokens/"/>
    3734    should be updated with the registration below:
     3730   shall be updated with the registration below:
    37353731</t>
    37363732<texttable align="left" suppress-title="true">
     
    38603856</t>
    38613857<t>
    3862    Proxy operators should protect the systems on which proxies run as
     3858   Proxy operators need to protect the systems on which proxies run as
    38633859   they would protect any system that contains or transports sensitive
    38643860   information. In particular, log information gathered at proxies often
    38653861   contains highly sensitive personal information, and/or information
    3866    about organizations. Log information should be carefully guarded, and
    3867    appropriate guidelines for use should be developed and followed.
     3862   about organizations. Log information needs to be carefully guarded, and
     3863   appropriate guidelines for use need to be developed and followed.
    38683864   (<xref target="abuse.of.server.log.information"/>).
    38693865</t>
    38703866<t>
    3871    Proxy implementors should consider the privacy and security
     3867   Proxy implementors need to consider the privacy and security
    38723868   implications of their design and coding decisions, and of the
    38733869   configuration options they provide to proxy operators (especially the
Note: See TracChangeset for help on using the changeset viewer.