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/latest
Files:
14 edited

Legend:

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

    r844 r847  
    404404      <meta name="dct.creator" content="Reschke, J. F.">
    405405      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest">
    406       <meta name="dct.issued" scheme="ISO8601" content="2010-07-09">
     406      <meta name="dct.issued" scheme="ISO8601" content="2010-07-12">
    407407      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    408408      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 1 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 1 provides an overview of HTTP and its associated terminology, defines the &#34;http&#34; and &#34;https&#34; Uniform Resource Identifier (URI) schemes, defines the generic message syntax and parsing requirements for HTTP message frames, and describes general security concerns for implementations.">
     
    435435            </tr>
    436436            <tr>
    437                <td class="left">Expires: January 10, 2011</td>
     437               <td class="left">Expires: January 13, 2011</td>
    438438               <td class="right">HP</td>
    439439            </tr>
     
    488488            <tr>
    489489               <td class="left"></td>
    490                <td class="right">July 9, 2010</td>
     490               <td class="right">July 12, 2010</td>
    491491            </tr>
    492492         </tbody>
     
    516516         in progress”.
    517517      </p>
    518       <p>This Internet-Draft will expire in January 10, 2011.</p>
     518      <p>This Internet-Draft will expire in January 13, 2011.</p>
    519519      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    520520      <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    742742         protocols it implements. An implementation that satisfies all the "MUST" or "REQUIRED" level and all the "SHOULD" level requirements
    743743         for its protocols is said to be "unconditionally compliant"; one that satisfies all the "MUST" level requirements but not
    744          all the "SHOULD" level requirements for its protocols is said to be "conditionally compliant."
     744         all the "SHOULD" level requirements for its protocols is said to be "conditionally compliant".
    745745      </p>
    746746      <div id="rfc.iref.g.1"></div>
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r844 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/latest/p2-semantics.html

    r844 r847  
    403403      <meta name="dct.creator" content="Reschke, J. F.">
    404404      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
    405       <meta name="dct.issued" scheme="ISO8601" content="2010-07-09">
     405      <meta name="dct.issued" scheme="ISO8601" content="2010-07-12">
    406406      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    407407      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 2 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request-header fields, response status codes, and response-header fields.">
     
    434434            </tr>
    435435            <tr>
    436                <td class="left">Expires: January 10, 2011</td>
     436               <td class="left">Expires: January 13, 2011</td>
    437437               <td class="right">HP</td>
    438438            </tr>
     
    487487            <tr>
    488488               <td class="left"></td>
    489                <td class="right">July 9, 2010</td>
     489               <td class="right">July 12, 2010</td>
    490490            </tr>
    491491         </tbody>
     
    514514         in progress”.
    515515      </p>
    516       <p>This Internet-Draft will expire in January 10, 2011.</p>
     516      <p>This Internet-Draft will expire in January 13, 2011.</p>
    517517      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    518518      <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    700700         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>.
    701701      </p>
    702       <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."
     702      <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
     703         protocols it implements. An implementation that satisfies all the "MUST" or "REQUIRED" level and all the "SHOULD" level requirements
     704         for its protocols is said to be "unconditionally compliant"; one that satisfies all the "MUST" level requirements but not
     705         all the "SHOULD" level requirements for its protocols is said to be "conditionally compliant".
    703706      </p>
    704707      <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/latest/p2-semantics.xml

    r844 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/latest/p3-payload.html

    r844 r847  
    401401      <meta name="dct.creator" content="Reschke, J. F.">
    402402      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p3-payload-latest">
    403       <meta name="dct.issued" scheme="ISO8601" content="2010-07-09">
     403      <meta name="dct.issued" scheme="ISO8601" content="2010-07-12">
    404404      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    405405      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 3 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 3 defines HTTP message content, metadata, and content negotiation.">
     
    427427            </tr>
    428428            <tr>
    429                <td class="left">Expires: January 10, 2011</td>
     429               <td class="left">Expires: January 13, 2011</td>
    430430               <td class="right">J. Mogul</td>
    431431            </tr>
     
    484484            <tr>
    485485               <td class="left"></td>
    486                <td class="right">July 9, 2010</td>
     486               <td class="right">July 12, 2010</td>
    487487            </tr>
    488488         </tbody>
     
    510510         in progress”.
    511511      </p>
    512       <p>This Internet-Draft will expire in January 10, 2011.</p>
     512      <p>This Internet-Draft will expire in January 13, 2011.</p>
    513513      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    514514      <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    680680         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>.
    681681      </p>
    682       <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."
     682      <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
     683         protocols it implements. An implementation that satisfies all the "MUST" or "REQUIRED" level and all the "SHOULD" level requirements
     684         for its protocols is said to be "unconditionally compliant"; one that satisfies all the "MUST" level requirements but not
     685         all the "SHOULD" level requirements for its protocols is said to be "conditionally compliant".
    683686      </p>
    684687      <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/latest/p3-payload.xml

    r844 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/latest/p4-conditional.html

    r844 r847  
    400400      <meta name="dct.creator" content="Reschke, J. F.">
    401401      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p4-conditional-latest">
    402       <meta name="dct.issued" scheme="ISO8601" content="2010-07-09">
     402      <meta name="dct.issued" scheme="ISO8601" content="2010-07-12">
    403403      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    404404      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 4 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 4 defines request header fields for indicating conditional requests and the rules for constructing responses to those requests.">
     
    426426            </tr>
    427427            <tr>
    428                <td class="left">Expires: January 10, 2011</td>
     428               <td class="left">Expires: January 13, 2011</td>
    429429               <td class="right">J. Mogul</td>
    430430            </tr>
     
    483483            <tr>
    484484               <td class="left"></td>
    485                <td class="right">July 9, 2010</td>
     485               <td class="right">July 12, 2010</td>
    486486            </tr>
    487487         </tbody>
     
    509509         in progress”.
    510510      </p>
    511       <p>This Internet-Draft will expire in January 10, 2011.</p>
     511      <p>This Internet-Draft will expire in January 13, 2011.</p>
    512512      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    513513      <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    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/latest/p4-conditional.xml

    r844 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/latest/p5-range.html

    r844 r847  
    400400      <meta name="dct.creator" content="Reschke, J. F.">
    401401      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest">
    402       <meta name="dct.issued" scheme="ISO8601" content="2010-07-09">
     402      <meta name="dct.issued" scheme="ISO8601" content="2010-07-12">
    403403      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    404404      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 5 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 5 defines range-specific requests and the rules for constructing and combining responses to those requests.">
     
    426426            </tr>
    427427            <tr>
    428                <td class="left">Expires: January 10, 2011</td>
     428               <td class="left">Expires: January 13, 2011</td>
    429429               <td class="right">J. Mogul</td>
    430430            </tr>
     
    483483            <tr>
    484484               <td class="left"></td>
    485                <td class="right">July 9, 2010</td>
     485               <td class="right">July 12, 2010</td>
    486486            </tr>
    487487         </tbody>
     
    509509         in progress”.
    510510      </p>
    511       <p>This Internet-Draft will expire in January 10, 2011.</p>
     511      <p>This Internet-Draft will expire in January 13, 2011.</p>
    512512      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    513513      <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    610610         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>.
    611611      </p>
    612       <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."
     612      <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
     613         protocols it implements. An implementation that satisfies all the "MUST" or "REQUIRED" level and all the "SHOULD" level requirements
     614         for its protocols is said to be "unconditionally compliant"; one that satisfies all the "MUST" level requirements but not
     615         all the "SHOULD" level requirements for its protocols is said to be "conditionally compliant".
    613616      </p>
    614617      <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/latest/p5-range.xml

    r844 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/latest/p6-cache.html

    r844 r847  
    402402      <meta name="dct.creator" content="Reschke, J. F.">
    403403      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest">
    404       <meta name="dct.issued" scheme="ISO8601" content="2010-07-09">
     404      <meta name="dct.issued" scheme="ISO8601" content="2010-07-12">
    405405      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    406406      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. This document is Part 6 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 6 defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages.">
     
    428428            </tr>
    429429            <tr>
    430                <td class="left">Expires: January 10, 2011</td>
     430               <td class="left">Expires: January 13, 2011</td>
    431431               <td class="right">J. Mogul</td>
    432432            </tr>
     
    489489            <tr>
    490490               <td class="left"></td>
    491                <td class="right">July 9, 2010</td>
     491               <td class="right">July 12, 2010</td>
    492492            </tr>
    493493         </tbody>
     
    515515         in progress”.
    516516      </p>
    517       <p>This Internet-Draft will expire in January 10, 2011.</p>
     517      <p>This Internet-Draft will expire in January 13, 2011.</p>
    518518      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    519519      <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    695695         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>.
    696696      </p>
    697       <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."
     697      <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
     698         protocols it implements. An implementation that satisfies all the "MUST" or "REQUIRED" level and all the "SHOULD" level requirements
     699         for its protocols is said to be "unconditionally compliant"; one that satisfies all the "MUST" level requirements but not
     700         all the "SHOULD" level requirements for its protocols is said to be "conditionally compliant".
    698701      </p>
    699702      <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/latest/p6-cache.xml

    r844 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/latest/p7-auth.html

    r844 r847  
    394394      <meta name="dct.creator" content="Reschke, J. F.">
    395395      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p7-auth-latest">
    396       <meta name="dct.issued" scheme="ISO8601" content="2010-07-09">
     396      <meta name="dct.issued" scheme="ISO8601" content="2010-07-12">
    397397      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    398398      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 7 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 7 defines HTTP Authentication.">
     
    425425            </tr>
    426426            <tr>
    427                <td class="left">Expires: January 10, 2011</td>
     427               <td class="left">Expires: January 13, 2011</td>
    428428               <td class="right">HP</td>
    429429            </tr>
     
    478478            <tr>
    479479               <td class="left"></td>
    480                <td class="right">July 9, 2010</td>
     480               <td class="right">July 12, 2010</td>
    481481            </tr>
    482482         </tbody>
     
    504504         in progress”.
    505505      </p>
    506       <p>This Internet-Draft will expire in January 10, 2011.</p>
     506      <p>This Internet-Draft will expire in January 13, 2011.</p>
    507507      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    508508      <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    594594         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>.
    595595      </p>
    596       <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."
     596      <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
     597         protocols it implements. An implementation that satisfies all the "MUST" or "REQUIRED" level and all the "SHOULD" level requirements
     598         for its protocols is said to be "unconditionally compliant"; one that satisfies all the "MUST" level requirements but not
     599         all the "SHOULD" level requirements for its protocols is said to be "conditionally compliant".
    597600      </p>
    598601      <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/latest/p7-auth.xml

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