Changeset 96 for draft-ietf-httpbis/latest/p7-auth.xml

Timestamp:

22/12/07 19:14:28 (14 years ago)

Author:

julian.reschke@…

Message:

Add "Requirements" subsection everywhere (including reference to RFC2119), add missing bcp14 markup.

File:

• draft-ietf-httpbis/latest/p7-auth.xml (modified) (2 diffs)

draft-ietf-httpbis/latest/p7-auth.xml

@@ -222 +222 @@
    from that specification.
 </t>
+
+<section title="Requirements" anchor="intro.requirements">
+<t>
+   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
+   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
+   document are to be interpreted as described in <xref target="RFC2119"/>.
+</t>
+<t>
+   An implementation is not compliant if it fails to satisfy one or more
+   of the &MUST; or &REQUIRED; level requirements for the protocols it
+   implements. An implementation that satisfies all the &MUST; or &REQUIRED;
+   level and all the &SHOULD; level requirements for its protocols is said
+   to be "unconditionally compliant"; one that satisfies all the &MUST;
+   level requirements but not all the &SHOULD; level requirements for its
+   protocols is said to be "conditionally compliant."
+</t>
+</section>
 </section>
 
@@ -487 +504 @@
 </reference>
 
+<reference anchor="RFC2119">
+  <front>
+    <title>Key words for use in RFCs to Indicate Requirement Levels</title>
+    <author initials="S." surname="Bradner" fullname="Scott Bradner">
+      <organization>Harvard University</organization>
+      <address><email>sob@harvard.edu</email></address>
+    </author>
+    <date month="March" year="1997"/>
+  </front>
+  <seriesInfo name="BCP" value="14"/>
+  <seriesInfo name="RFC" value="2119"/>
+</reference>
+
 <reference anchor="RFC2616">
    <front>