Ignore:
Timestamp:
Dec 22, 2007, 11:14:28 AM (12 years ago)
Author:
julian.reschke@…
Message:

Add "Requirements" subsection everywhere (including reference to RFC2119), add missing bcp14 markup.

File:
1 edited

Legend:

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

    r95 r96  
    267267   between HTTP and MIME is described in &diff2045entity;.
    268268</t>
     269
     270<section title="Requirements" anchor="intro.requirements">
     271<t>
     272   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
     273   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
     274   document are to be interpreted as described in <xref target="RFC2119"/>.
     275</t>
     276<t>
     277   An implementation is not compliant if it fails to satisfy one or more
     278   of the &MUST; or &REQUIRED; level requirements for the protocols it
     279   implements. An implementation that satisfies all the &MUST; or &REQUIRED;
     280   level and all the &SHOULD; level requirements for its protocols is said
     281   to be "unconditionally compliant"; one that satisfies all the &MUST;
     282   level requirements but not all the &SHOULD; level requirements for its
     283   protocols is said to be "conditionally compliant."
     284</t>
     285</section>
    269286</section>
    270287
     
    11371154   If the 301 status code is received in response to a request method
    11381155   that is known to be "safe", as defined in <xref target="safe.methods"/>,
    1139    then the request MAY be automatically redirected by the user agent without
     1156   then the request &MAY; be automatically redirected by the user agent without
    11401157   confirmation.  Otherwise, the user agent &MUST-NOT; automatically redirect the
    11411158   request unless it can be confirmed by the user, since this might
     
    11681185   If the 302 status code is received in response to a request method
    11691186   that is known to be "safe", as defined in <xref target="safe.methods"/>,
    1170    then the request MAY be automatically redirected by the user agent without
     1187   then the request &MAY; be automatically redirected by the user agent without
    11711188   confirmation.  Otherwise, the user agent &MUST-NOT; automatically redirect the
    11721189   request unless it can be confirmed by the user, since this might
     
    12661283   If the 307 status code is received in response to a request method
    12671284   that is known to be "safe", as defined in <xref target="safe.methods"/>,
    1268    then the request MAY be automatically redirected by the user agent without
     1285   then the request &MAY; be automatically redirected by the user agent without
    12691286   confirmation.  Otherwise, the user agent &MUST-NOT; automatically redirect the
    12701287   request unless it can be confirmed by the user, since this might
     
    24802497</reference>
    24812498
     2499<reference anchor="RFC2119">
     2500  <front>
     2501    <title>Key words for use in RFCs to Indicate Requirement Levels</title>
     2502    <author initials="S." surname="Bradner" fullname="Scott Bradner">
     2503      <organization>Harvard University</organization>
     2504      <address><email>sob@harvard.edu</email></address>
     2505    </author>
     2506    <date month="March" year="1997"/>
     2507  </front>
     2508  <seriesInfo name="BCP" value="14"/>
     2509  <seriesInfo name="RFC" value="2119"/>
     2510</reference>
     2511
    24822512<reference anchor="Luo1998">
    24832513<front>
Note: See TracChangeset for help on using the changeset viewer.