Changeset 96 for draft-ietf-httpbis/latest/p6-cache.xml
- Timestamp:
- 22/12/07 19:14:28 (13 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p6-cache.xml
r95 r96 227 227 </t> 228 228 229 <section title="Requirements" anchor="intro.requirements"> 230 <t> 231 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 232 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 233 document are to be interpreted as described in <xref target="RFC2119"/>. 234 </t> 235 <t> 236 An implementation is not compliant if it fails to satisfy one or more 237 of the &MUST; or &REQUIRED; level requirements for the protocols it 238 implements. An implementation that satisfies all the &MUST; or &REQUIRED; 239 level and all the &SHOULD; level requirements for its protocols is said 240 to be "unconditionally compliant"; one that satisfies all the &MUST; 241 level requirements but not all the &SHOULD; level requirements for its 242 protocols is said to be "conditionally compliant." 243 </t> 244 </section> 245 229 246 <section title="Terminology" anchor="intro.terminology"> 230 247 <t> … … 2711 2728 </reference> 2712 2729 2730 <reference anchor="RFC2119"> 2731 <front> 2732 <title>Key words for use in RFCs to Indicate Requirement Levels</title> 2733 <author initials="S." surname="Bradner" fullname="Scott Bradner"> 2734 <organization>Harvard University</organization> 2735 <address><email>sob@harvard.edu</email></address> 2736 </author> 2737 <date month="March" year="1997"/> 2738 </front> 2739 <seriesInfo name="BCP" value="14"/> 2740 <seriesInfo name="RFC" value="2119"/> 2741 </reference> 2742 2713 2743 <reference anchor="RFC2616"> 2714 2744 <front>
Note: See TracChangeset
for help on using the changeset viewer.