Ignore:
Timestamp:
Jun 22, 2012, 12:32:37 AM (7 years ago)
Author:
julian.reschke@…
Message:

avoid the use of "may"/"should" when it could be confused with MAY/SHOULD

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r1684 r1685  
    202202<note title="Editorial Note (To be removed by RFC Editor)">
    203203  <t>
    204     Discussion of this draft should take place on the HTTPBIS working group
     204    Discussion of this draft ought to take place on the HTTPBIS working group
    205205    mailing list (ietf-http-wg@w3.org), which is archived at
    206206    <eref target="http://lists.w3.org/Archives/Public/ietf-http-wg/"/>.
     
    469469   When it is necessary to express new semantics for a HTTP request that
    470470   aren't specific to a single application or media type, and currently defined
    471    methods are inadequate, it may be appropriate to register a new method.
     471   methods are inadequate, it might be appropriate to register a new method.
    472472</t>
    473473<t>
     
    937937</t>
    938938<t>
    939    It may be the case that the proxy itself can only reach the requested
     939   It might be the case that the proxy itself can only reach the requested
    940940   origin server through another proxy.  In this case, the first proxy
    941941   &SHOULD; make a CONNECT request of that next proxy, requesting a tunnel
     
    20032003   The server &SHOULD; include a message body in the 426 response which
    20042004   indicates in human readable form the reason for the error and describes any
    2005    alternative courses which may be available to the user.
     2005   alternative courses which might be available to the user.
    20062006</t>
    20072007</section>
     
    44134413</t>
    44144414<t>
    4415    Furthermore, the User-Agent header field may contain enough entropy to be
     4415   Furthermore, the User-Agent header field might contain enough entropy to be
    44164416   used, possibly in conjunction with other material, to uniquely identify the
    44174417   user.
     
    64236423      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/43"/>:
    64246424      "Fragment combination / precedence during redirects" (added warning
    6425       about having a fragid on the redirect may cause inconvenience in
     6425      about having a fragid on the redirect might cause inconvenience in
    64266426      some cases)
    64276427    </t>
Note: See TracChangeset for help on using the changeset viewer.