Ignore:
Timestamp:
Dec 22, 2007, 11:14:28 AM (12 years ago)
Author:
julian.reschke@…
Message:

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

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p7-auth.xml

    r95 r96  
    222222   from that specification.
    223223</t>
     224
     225<section title="Requirements" anchor="intro.requirements">
     226<t>
     227   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
     228   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
     229   document are to be interpreted as described in <xref target="RFC2119"/>.
     230</t>
     231<t>
     232   An implementation is not compliant if it fails to satisfy one or more
     233   of the &MUST; or &REQUIRED; level requirements for the protocols it
     234   implements. An implementation that satisfies all the &MUST; or &REQUIRED;
     235   level and all the &SHOULD; level requirements for its protocols is said
     236   to be "unconditionally compliant"; one that satisfies all the &MUST;
     237   level requirements but not all the &SHOULD; level requirements for its
     238   protocols is said to be "conditionally compliant."
     239</t>
     240</section>
    224241</section>
    225242
     
    487504</reference>
    488505
     506<reference anchor="RFC2119">
     507  <front>
     508    <title>Key words for use in RFCs to Indicate Requirement Levels</title>
     509    <author initials="S." surname="Bradner" fullname="Scott Bradner">
     510      <organization>Harvard University</organization>
     511      <address><email>sob@harvard.edu</email></address>
     512    </author>
     513    <date month="March" year="1997"/>
     514  </front>
     515  <seriesInfo name="BCP" value="14"/>
     516  <seriesInfo name="RFC" value="2119"/>
     517</reference>
     518
    489519<reference anchor="RFC2616">
    490520   <front>
Note: See TracChangeset for help on using the changeset viewer.