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.html

    r1684 r1685  
    547547      </p>
    548548      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1>
    549       <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org), which is archived
     549      <p>Discussion of this draft ought to take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org), which is archived
    550550         at &lt;<a href="http://lists.w3.org/Archives/Public/ietf-http-wg/">http://lists.w3.org/Archives/Public/ietf-http-wg/</a>&gt;.
    551551      </p> 
     
    931931      <h3 id="rfc.section.2.2.1"><a href="#rfc.section.2.2.1">2.2.1</a>&nbsp;<a id="considerations.for.new.methods" href="#considerations.for.new.methods">Considerations for New Methods</a></h3>
    932932      <p id="rfc.section.2.2.1.p.1">When it is necessary to express new semantics for a HTTP request that aren't specific to a single application or media type,
    933          and currently defined methods are inadequate, it may be appropriate to register a new method.
     933         and currently defined methods are inadequate, it might be appropriate to register a new method.
    934934      </p>
    935935      <p id="rfc.section.2.2.1.p.2">HTTP methods are generic; that is, they are potentially applicable to any resource, not just one particular media type, "type"
     
    11561156         if the eventual response is negative, and the connection may be reset with no response if more than one TCP segment is outstanding.
    11571157      </p>
    1158       <p id="rfc.section.2.3.8.p.10">It may be the case that the proxy itself can only reach the requested origin server through another proxy. In this case, the
    1159          first proxy <em class="bcp14">SHOULD</em> make a CONNECT request of that next proxy, requesting a tunnel to the authority. A proxy <em class="bcp14">MUST NOT</em> respond with any 2xx status code unless it has either a direct or tunnel connection established to the authority.
     1158      <p id="rfc.section.2.3.8.p.10">It might be the case that the proxy itself can only reach the requested origin server through another proxy. In this case,
     1159         the first proxy <em class="bcp14">SHOULD</em> make a CONNECT request of that next proxy, requesting a tunnel to the authority. A proxy <em class="bcp14">MUST NOT</em> respond with any 2xx status code unless it has either a direct or tunnel connection established to the authority.
    11601160      </p>
    11611161      <p id="rfc.section.2.3.8.p.11">If at any point either one of the peers gets disconnected, any outstanding data that came from that peer will be passed to
     
    20342034<span id="s426body">This service requires use of the HTTP/3.0 protocol.
    20352035</span></pre><p id="rfc.section.4.6.15.p.3">The server <em class="bcp14">SHOULD</em> include a message body in the 426 response which indicates in human readable form the reason for the error and describes any
    2036          alternative courses which may be available to the user.
     2036         alternative courses which might be available to the user.
    20372037      </p>
    20382038      <h2 id="rfc.section.4.7"><a href="#rfc.section.4.7">4.7</a>&nbsp;<a id="status.5xx" href="#status.5xx">Server Error 5xx</a></h2>
     
    36233623         no better mechanism.
    36243624      </p>
    3625       <p id="rfc.section.11.1.p.8">Furthermore, the User-Agent header field may contain enough entropy to be used, possibly in conjunction with other material,
     3625      <p id="rfc.section.11.1.p.8">Furthermore, the User-Agent header field might contain enough entropy to be used, possibly in conjunction with other material,
    36263626         to uniquely identify the user.
    36273627      </p>
     
    45584558      <p id="rfc.section.E.26.p.1">Closed issues: </p>
    45594559      <ul>
    4560          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/43">http://tools.ietf.org/wg/httpbis/trac/ticket/43</a>&gt;: "Fragment combination / precedence during redirects" (added warning about having a fragid on the redirect may cause inconvenience
     4560         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/43">http://tools.ietf.org/wg/httpbis/trac/ticket/43</a>&gt;: "Fragment combination / precedence during redirects" (added warning about having a fragid on the redirect might cause inconvenience
    45614561            in some cases)
    45624562         </li>
Note: See TracChangeset for help on using the changeset viewer.