Changeset 96 for draft-ietf-httpbis/latest/p4-conditional.html
- Timestamp:
- 22/12/07 19:14:28 (14 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p4-conditional.html
r95 r96 483 483 <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1> 484 484 <ul class="toc"> 485 <li class="tocline0">1. <a href="#introduction">Introduction</a></li> 485 <li class="tocline0">1. <a href="#introduction">Introduction</a><ul class="toc"> 486 <li class="tocline1">1.1 <a href="#intro.requirements">Requirements</a></li> 487 </ul> 488 </li> 486 489 <li class="tocline0">2. <a href="#entity.tags">Entity Tags</a></li> 487 490 <li class="tocline0">3. <a href="#rfc.section.3">Status Code Definitions</a><ul class="toc"> … … 512 515 <p id="rfc.section.1.p.1">This document will define aspects of HTTP related to conditional request messages based on time stamps and entity-tags. Right 513 516 now it only includes the extracted relevant sections of <a href="#RFC2616">RFC 2616</a> <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2616.2">[RFC2616]</cite> without edit. 517 </p> 518 <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a> <a id="intro.requirements" href="#intro.requirements">Requirements</a></h2> 519 <p id="rfc.section.1.1.p.1">The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" 520 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>. 521 </p> 522 <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." 514 523 </p> 515 524 <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a> <a id="entity.tags" href="#entity.tags">Entity Tags</a></h1> … … 879 888 <h1 id="rfc.references"><a href="#rfc.section.10" id="rfc.section.10">10.</a> References 880 889 </h1> 881 <table summary="References"> 890 <table summary="References"> 882 891 <tr> 883 892 <td class="reference"><b id="Part1">[Part1]</b></td> … … 898 907 <td class="reference"><b id="RFC2068">[RFC2068]</b></td> 899 908 <td class="top"><a title="University of California, Irvine, Department of Information and Computer Science">Fielding, R.</a>, <a title="MIT Laboratory for Computer Science">Gettys, J.</a>, <a title="Digital Equipment Corporation, Western Research Laboratory">Mogul, J.</a>, <a title="MIT Laboratory for Computer Science">Nielsen, H.</a>, and <a title="MIT Laboratory for Computer Science">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/rfc2068">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC 2068, January 1997. 909 </td> 910 </tr> 911 <tr> 912 <td class="reference"><b id="RFC2119">[RFC2119]</b></td> 913 <td class="top"><a title="Harvard University">Bradner, S.</a>, “<a href="http://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>”, BCP 14, RFC 2119, March 1997. 900 914 </td> 901 915 </tr> … … 1027 1041 </ul> 1028 1042 </li> 1043 <li class="indline1"><em>RFC2119</em> <a class="iref" href="#rfc.xref.RFC2119.1">1.1</a>, <a class="iref" href="#RFC2119"><b>10</b></a></li> 1029 1044 <li class="indline1"><em>RFC2616</em> <a class="iref" href="#rfc.xref.RFC2616.1">§</a>, <a class="iref" href="#rfc.xref.RFC2616.2">1</a>, <a class="iref" href="#RFC2616"><b>10</b></a></li> 1030 1045 </ul>
Note: See TracChangeset
for help on using the changeset viewer.