Changeset 847 for draft-ietf-httpbis/10


Ignore:
Timestamp:
Jul 12, 2010, 4:11:48 AM (9 years ago)
Author:
julian.reschke@…
Message:

Make requirements sections consistent again.

Location:
draft-ietf-httpbis/10
Files:
14 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/10/p1-messaging.html

    r845 r847  
    741741         protocols it implements. An implementation that satisfies all the "MUST" or "REQUIRED" level and all the "SHOULD" level requirements
    742742         for its protocols is said to be "unconditionally compliant"; one that satisfies all the "MUST" level requirements but not
    743          all the "SHOULD" level requirements for its protocols is said to be "conditionally compliant."
     743         all the "SHOULD" level requirements for its protocols is said to be "conditionally compliant".
    744744      </p>
    745745      <div id="rfc.iref.g.1"></div>
  • draft-ietf-httpbis/10/p1-messaging.xml

    r845 r847  
    297297   to be "unconditionally compliant"; one that satisfies all the "MUST"
    298298   level requirements but not all the "SHOULD" level requirements for its
    299    protocols is said to be "conditionally compliant."
     299   protocols is said to be "conditionally compliant".
    300300</t>
    301301</section>
  • draft-ietf-httpbis/10/p2-semantics.html

    r845 r847  
    699699         in this document are to be interpreted as described in <a href="#RFC2119" id="rfc.xref.RFC2119.1"><cite title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</cite></a>.
    700700      </p>
    701       <p id="rfc.section.1.1.p.2">An implementation is not compliant if it fails to satisfy one or more of the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level requirements for the protocols it implements. An implementation that satisfies all the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level and all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "unconditionally compliant"; one that satisfies all the <em class="bcp14">MUST</em> level requirements but not all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "conditionally compliant."
     701      <p id="rfc.section.1.1.p.2">An implementation is not compliant if it fails to satisfy one or more of the "MUST" or "REQUIRED" level requirements for the
     702         protocols it implements. An implementation that satisfies all the "MUST" or "REQUIRED" level and all the "SHOULD" level requirements
     703         for its protocols is said to be "unconditionally compliant"; one that satisfies all the "MUST" level requirements but not
     704         all the "SHOULD" level requirements for its protocols is said to be "conditionally compliant".
    702705      </p>
    703706      <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a id="notation" href="#notation">Syntax Notation</a></h2>
  • draft-ietf-httpbis/10/p2-semantics.xml

    r845 r847  
    293293<t>
    294294   An implementation is not compliant if it fails to satisfy one or more
    295    of the &MUST; or &REQUIRED; level requirements for the protocols it
    296    implements. An implementation that satisfies all the &MUST; or &REQUIRED;
    297    level and all the &SHOULD; level requirements for its protocols is said
    298    to be "unconditionally compliant"; one that satisfies all the &MUST;
    299    level requirements but not all the &SHOULD; level requirements for its
    300    protocols is said to be "conditionally compliant."
     295   of the "MUST" or "REQUIRED" level requirements for the protocols it
     296   implements. An implementation that satisfies all the "MUST" or "REQUIRED"
     297   level and all the "SHOULD" level requirements for its protocols is said
     298   to be "unconditionally compliant"; one that satisfies all the "MUST"
     299   level requirements but not all the "SHOULD" level requirements for its
     300   protocols is said to be "conditionally compliant".
    301301</t>
    302302</section>
  • draft-ietf-httpbis/10/p3-payload.html

    r845 r847  
    679679         in this document are to be interpreted as described in <a href="#RFC2119" id="rfc.xref.RFC2119.1"><cite title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</cite></a>.
    680680      </p>
    681       <p id="rfc.section.1.2.p.2">An implementation is not compliant if it fails to satisfy one or more of the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level requirements for the protocols it implements. An implementation that satisfies all the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level and all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "unconditionally compliant"; one that satisfies all the <em class="bcp14">MUST</em> level requirements but not all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "conditionally compliant."
     681      <p id="rfc.section.1.2.p.2">An implementation is not compliant if it fails to satisfy one or more of the "MUST" or "REQUIRED" level requirements for the
     682         protocols it implements. An implementation that satisfies all the "MUST" or "REQUIRED" level and all the "SHOULD" level requirements
     683         for its protocols is said to be "unconditionally compliant"; one that satisfies all the "MUST" level requirements but not
     684         all the "SHOULD" level requirements for its protocols is said to be "conditionally compliant".
    682685      </p>
    683686      <h2 id="rfc.section.1.3"><a href="#rfc.section.1.3">1.3</a>&nbsp;<a id="notation" href="#notation">Syntax Notation</a></h2>
  • draft-ietf-httpbis/10/p3-payload.xml

    r845 r847  
    306306<t>
    307307   An implementation is not compliant if it fails to satisfy one or more
    308    of the &MUST; or &REQUIRED; level requirements for the protocols it
    309    implements. An implementation that satisfies all the &MUST; or &REQUIRED;
    310    level and all the &SHOULD; level requirements for its protocols is said
    311    to be "unconditionally compliant"; one that satisfies all the &MUST;
    312    level requirements but not all the &SHOULD; level requirements for its
    313    protocols is said to be "conditionally compliant."
     308   of the "MUST" or "REQUIRED" level requirements for the protocols it
     309   implements. An implementation that satisfies all the "MUST" or "REQUIRED"
     310   level and all the "SHOULD" level requirements for its protocols is said
     311   to be "unconditionally compliant"; one that satisfies all the "MUST"
     312   level requirements but not all the "SHOULD" level requirements for its
     313   protocols is said to be "conditionally compliant".
    314314</t>
    315315</section>
  • draft-ietf-httpbis/10/p4-conditional.html

    r845 r847  
    608608         in this document are to be interpreted as described in <a href="#RFC2119" id="rfc.xref.RFC2119.1"><cite title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</cite></a>.
    609609      </p>
    610       <p id="rfc.section.1.1.p.2">An implementation is not compliant if it fails to satisfy one or more of the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level requirements for the protocols it implements. An implementation that satisfies all the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level and all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "unconditionally compliant"; one that satisfies all the <em class="bcp14">MUST</em> level requirements but not all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "conditionally compliant."
     610      <p id="rfc.section.1.1.p.2">An implementation is not compliant if it fails to satisfy one or more of the "MUST" or "REQUIRED" level requirements for the
     611         protocols it implements. An implementation that satisfies all the "MUST" or "REQUIRED" level and all the "SHOULD" level requirements
     612         for its protocols is said to be "unconditionally compliant"; one that satisfies all the "MUST" level requirements but not
     613         all the "SHOULD" level requirements for its protocols is said to be "conditionally compliant".
    611614      </p>
    612615      <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a id="notation" href="#notation">Syntax Notation</a></h2>
  • draft-ietf-httpbis/10/p4-conditional.xml

    r845 r847  
    247247<t>
    248248   An implementation is not compliant if it fails to satisfy one or more
    249    of the &MUST; or &REQUIRED; level requirements for the protocols it
    250    implements. An implementation that satisfies all the &MUST; or &REQUIRED;
    251    level and all the &SHOULD; level requirements for its protocols is said
    252    to be "unconditionally compliant"; one that satisfies all the &MUST;
    253    level requirements but not all the &SHOULD; level requirements for its
    254    protocols is said to be "conditionally compliant."
     249   of the "MUST" or "REQUIRED" level requirements for the protocols it
     250   implements. An implementation that satisfies all the "MUST" or "REQUIRED"
     251   level and all the "SHOULD" level requirements for its protocols is said
     252   to be "unconditionally compliant"; one that satisfies all the "MUST"
     253   level requirements but not all the "SHOULD" level requirements for its
     254   protocols is said to be "conditionally compliant".
    255255</t>
    256256</section>
  • draft-ietf-httpbis/10/p5-range.html

    r845 r847  
    609609         in this document are to be interpreted as described in <a href="#RFC2119" id="rfc.xref.RFC2119.1"><cite title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</cite></a>.
    610610      </p>
    611       <p id="rfc.section.1.1.p.2">An implementation is not compliant if it fails to satisfy one or more of the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level requirements for the protocols it implements. An implementation that satisfies all the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level and all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "unconditionally compliant"; one that satisfies all the <em class="bcp14">MUST</em> level requirements but not all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "conditionally compliant."
     611      <p id="rfc.section.1.1.p.2">An implementation is not compliant if it fails to satisfy one or more of the "MUST" or "REQUIRED" level requirements for the
     612         protocols it implements. An implementation that satisfies all the "MUST" or "REQUIRED" level and all the "SHOULD" level requirements
     613         for its protocols is said to be "unconditionally compliant"; one that satisfies all the "MUST" level requirements but not
     614         all the "SHOULD" level requirements for its protocols is said to be "conditionally compliant".
    612615      </p>
    613616      <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a id="notation" href="#notation">Syntax Notation</a></h2>
  • draft-ietf-httpbis/10/p5-range.xml

    r845 r847  
    243243<t>
    244244   An implementation is not compliant if it fails to satisfy one or more
    245    of the &MUST; or &REQUIRED; level requirements for the protocols it
    246    implements. An implementation that satisfies all the &MUST; or &REQUIRED;
    247    level and all the &SHOULD; level requirements for its protocols is said
    248    to be "unconditionally compliant"; one that satisfies all the &MUST;
    249    level requirements but not all the &SHOULD; level requirements for its
    250    protocols is said to be "conditionally compliant."
     245   of the "MUST" or "REQUIRED" level requirements for the protocols it
     246   implements. An implementation that satisfies all the "MUST" or "REQUIRED"
     247   level and all the "SHOULD" level requirements for its protocols is said
     248   to be "unconditionally compliant"; one that satisfies all the "MUST"
     249   level requirements but not all the "SHOULD" level requirements for its
     250   protocols is said to be "conditionally compliant".
    251251</t>
    252252</section>
  • draft-ietf-httpbis/10/p6-cache.html

    r845 r847  
    694694         in this document are to be interpreted as described in <a href="#RFC2119" id="rfc.xref.RFC2119.1"><cite title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</cite></a>.
    695695      </p>
    696       <p id="rfc.section.1.3.p.2">An implementation is not compliant if it fails to satisfy one or more of the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level requirements for the protocols it implements. An implementation that satisfies all the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level and all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "unconditionally compliant"; one that satisfies all the <em class="bcp14">MUST</em> level requirements but not all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "conditionally compliant."
     696      <p id="rfc.section.1.3.p.2">An implementation is not compliant if it fails to satisfy one or more of the "MUST" or "REQUIRED" level requirements for the
     697         protocols it implements. An implementation that satisfies all the "MUST" or "REQUIRED" level and all the "SHOULD" level requirements
     698         for its protocols is said to be "unconditionally compliant"; one that satisfies all the "MUST" level requirements but not
     699         all the "SHOULD" level requirements for its protocols is said to be "conditionally compliant".
    697700      </p>
    698701      <h2 id="rfc.section.1.4"><a href="#rfc.section.1.4">1.4</a>&nbsp;<a id="notation" href="#notation">Syntax Notation</a></h2>
  • draft-ietf-httpbis/10/p6-cache.xml

    r845 r847  
    340340<section anchor="intro.requirements" title="Requirements">
    341341<t>
    342   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD
    343   NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as
    344   described in <xref target="RFC2119" />.
    345 </t>
    346 <t>
    347   An implementation is not compliant if it fails to satisfy one or more of the &MUST;
    348   or &REQUIRED; level requirements for the protocols it implements. An implementation
    349   that satisfies all the &MUST; or &REQUIRED; level and all the &SHOULD; level
    350   requirements for its protocols is said to be "unconditionally compliant"; one that
    351   satisfies all the &MUST; level requirements but not all the &SHOULD; level
    352   requirements for its protocols is said to be "conditionally compliant."
     342   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
     343   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
     344   document are to be interpreted as described in <xref target="RFC2119"/>.
     345</t>
     346<t>
     347   An implementation is not compliant if it fails to satisfy one or more
     348   of the "MUST" or "REQUIRED" level requirements for the protocols it
     349   implements. An implementation that satisfies all the "MUST" or "REQUIRED"
     350   level and all the "SHOULD" level requirements for its protocols is said
     351   to be "unconditionally compliant"; one that satisfies all the "MUST"
     352   level requirements but not all the "SHOULD" level requirements for its
     353   protocols is said to be "conditionally compliant".
    353354</t>
    354355</section>
  • draft-ietf-httpbis/10/p7-auth.html

    r845 r847  
    593593         in this document are to be interpreted as described in <a href="#RFC2119" id="rfc.xref.RFC2119.1"><cite title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</cite></a>.
    594594      </p>
    595       <p id="rfc.section.1.1.p.2">An implementation is not compliant if it fails to satisfy one or more of the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level requirements for the protocols it implements. An implementation that satisfies all the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level and all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "unconditionally compliant"; one that satisfies all the <em class="bcp14">MUST</em> level requirements but not all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "conditionally compliant."
     595      <p id="rfc.section.1.1.p.2">An implementation is not compliant if it fails to satisfy one or more of the "MUST" or "REQUIRED" level requirements for the
     596         protocols it implements. An implementation that satisfies all the "MUST" or "REQUIRED" level and all the "SHOULD" level requirements
     597         for its protocols is said to be "unconditionally compliant"; one that satisfies all the "MUST" level requirements but not
     598         all the "SHOULD" level requirements for its protocols is said to be "conditionally compliant".
    596599      </p>
    597600      <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a id="notation" href="#notation">Syntax Notation</a></h2>
  • draft-ietf-httpbis/10/p7-auth.xml

    r845 r847  
    234234<t>
    235235   An implementation is not compliant if it fails to satisfy one or more
    236    of the &MUST; or &REQUIRED; level requirements for the protocols it
    237    implements. An implementation that satisfies all the &MUST; or &REQUIRED;
    238    level and all the &SHOULD; level requirements for its protocols is said
    239    to be "unconditionally compliant"; one that satisfies all the &MUST;
    240    level requirements but not all the &SHOULD; level requirements for its
    241    protocols is said to be "conditionally compliant."
     236   of the "MUST" or "REQUIRED" level requirements for the protocols it
     237   implements. An implementation that satisfies all the "MUST" or "REQUIRED"
     238   level and all the "SHOULD" level requirements for its protocols is said
     239   to be "unconditionally compliant"; one that satisfies all the "MUST"
     240   level requirements but not all the "SHOULD" level requirements for its
     241   protocols is said to be "conditionally compliant".
    242242</t>
    243243</section>
Note: See TracChangeset for help on using the changeset viewer.