Changeset 96 for draft-ietf-httpbis/latest/p4-conditional.xml
- Timestamp:
- 22/12/07 19:14:28 (15 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p4-conditional.xml
r95 r96 220 220 without edit. 221 221 </t> 222 223 <section title="Requirements" anchor="intro.requirements"> 224 <t> 225 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 226 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 227 document are to be interpreted as described in <xref target="RFC2119"/>. 228 </t> 229 <t> 230 An implementation is not compliant if it fails to satisfy one or more 231 of the &MUST; or &REQUIRED; level requirements for the protocols it 232 implements. An implementation that satisfies all the &MUST; or &REQUIRED; 233 level and all the &SHOULD; level requirements for its protocols is said 234 to be "unconditionally compliant"; one that satisfies all the &MUST; 235 level requirements but not all the &SHOULD; level requirements for its 236 protocols is said to be "conditionally compliant." 237 </t> 238 </section> 222 239 </section> 223 240 … … 1097 1114 </front> 1098 1115 <seriesInfo name="RFC" value="2616"/> 1116 </reference> 1117 1118 <reference anchor="RFC2119"> 1119 <front> 1120 <title>Key words for use in RFCs to Indicate Requirement Levels</title> 1121 <author initials="S." surname="Bradner" fullname="Scott Bradner"> 1122 <organization>Harvard University</organization> 1123 <address><email>sob@harvard.edu</email></address> 1124 </author> 1125 <date month="March" year="1997"/> 1126 </front> 1127 <seriesInfo name="BCP" value="14"/> 1128 <seriesInfo name="RFC" value="2119"/> 1099 1129 </reference> 1100 1130
Note: See TracChangeset
for help on using the changeset viewer.