Changeset 1796 for draft-ietf-httpbis/latest/p4-conditional.xml

Timestamp:

Jul 15, 2012, 10:38:18 PM (8 years ago)

Author:

julian.reschke@…

Message:

Undo the part of [1783] that removed/moved the conformance/syntax sections.

File:

• draft-ietf-httpbis/latest/p4-conditional.xml (modified) (2 diffs)

draft-ietf-httpbis/latest/p4-conditional.xml

@@ -171 +171 @@
    for the selected representation.
 </t>
+
+<section title="Conformance and Error Handling" anchor="intro.conformance.and.error.handling">
+<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>
+   This specification targets conformance criteria according to the role of
+   a participant in HTTP communication.  Hence, HTTP requirements are placed
+   on senders, recipients, clients, servers, user agents, intermediaries,
+   origin servers, proxies, gateways, or caches, depending on what behavior
+   is being constrained by the requirement. See &architecture; for definitions
+   of these terms.
+</t>
+<t>
+   The verb "generate" is used instead of "send" where a requirement
+   differentiates between creating a protocol element and merely forwarding a
+   received element downstream.
+</t>
+<t>
+   An implementation is considered conformant if it complies with all of the
+   requirements associated with the roles it partakes in HTTP. Note that
+   SHOULD-level requirements are relevant here, unless one of the documented
+   exceptions is applicable.
+</t>
+<t>
+   This document also uses ABNF to define valid protocol elements
+   (<xref target="notation"/>).
+   In addition to the prose requirements placed upon them, senders &MUST-NOT;
+   generate protocol elements that do not match the grammar defined by the
+   ABNF rules for those protocol elements that are applicable to the sender's
+   role. If a received protocol element is processed, the recipient &MUST; be
+   able to parse any value that would match the ABNF rules for that protocol
+   element, excluding only those rules not applicable to the recipient's role.
+</t>
+<t>
+   Unless noted otherwise, a recipient &MAY; attempt to recover a usable
+   protocol element from an invalid construct.  HTTP does not define
+   specific error handling mechanisms except when they have a direct impact
+   on security, since different applications of the protocol require
+   different error handling strategies.  For example, a Web browser might
+   wish to transparently recover from a response where the
+   <x:ref>Location</x:ref> header field doesn't parse according to the ABNF,
+   whereas a systems control client might consider any form of error recovery
+   to be dangerous.
+</t>
+</section>
+
+<section title="Syntax Notation" anchor="notation">
+  <x:anchor-alias value="ALPHA"/>
+  <x:anchor-alias value="CR"/>
+  <x:anchor-alias value="DIGIT"/>
+  <x:anchor-alias value="DQUOTE"/>
+  <x:anchor-alias value="LF"/>
+  <x:anchor-alias value="OCTET"/>
+  <x:anchor-alias value="VCHAR"/>
+  <x:anchor-alias value="core.rules"/>
+  <x:anchor-alias value="obs-text"/>
+  <x:anchor-alias value="OWS"/>
+  <x:anchor-alias value="HTTP-date"/>
+<t>
+   This specification uses the Augmented Backus-Naur Form (ABNF) notation
+   of <xref target="RFC5234"/> with the list rule extension defined in
+   &notation;.  <xref target="collected.abnf"/> shows the collected ABNF
+   with the list rule expanded.
+</t>
+<t>
+  The following core rules are included by
+  reference, as defined in <xref target="RFC5234" x:fmt="," x:sec="B.1"/>:
+  ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls),
+  DIGIT (decimal 0-9), DQUOTE (double quote),
+  HEXDIG (hexadecimal 0-9/A-F/a-f), LF (line feed),
+  OCTET (any 8-bit sequence of data), SP (space), and
+  VCHAR (any visible US-ASCII character).
+</t>
+<t>
+  The ABNF rules below are defined in <xref target="Part1"/> and
+  <xref target="Part2"/>:
+</t>
+<figure><artwork type="abnf2616">
+  <x:ref>OWS</x:ref>           = &lt;OWS, defined in &whitespace;&gt;
+  <x:ref>obs-text</x:ref>      = &lt;obs-text, defined in &field-components;&gt;
+  <x:ref>HTTP-date</x:ref>     = &lt;HTTP-date, defined in &http-date;&gt;
+</artwork></figure>
+</section>
 </section>
 
@@ -1002 +1088 @@
 </t>
 </section>
-</section>
-
-<section title="ABNF Rules Defined Elsewhere" anchor="abnf.dependencies">
-  <x:anchor-alias value="ALPHA"/>
-  <x:anchor-alias value="CR"/>
-  <x:anchor-alias value="DIGIT"/>
-  <x:anchor-alias value="DQUOTE"/>
-  <x:anchor-alias value="LF"/>
-  <x:anchor-alias value="OCTET"/>
-  <x:anchor-alias value="VCHAR"/>
-  <x:anchor-alias value="core.rules"/>
-  <x:anchor-alias value="obs-text"/>
-  <x:anchor-alias value="OWS"/>
-  <x:anchor-alias value="HTTP-date"/>
-<t>
-   This specification uses the Augmented Backus-Naur Form (ABNF) notation
-   of <xref target="RFC5234"/> with the list rule extension defined in
-   &notation;.  <xref target="collected.abnf"/> shows the collected ABNF
-   with the list rule expanded.
-</t>
-<t>
-  The following core rules are included by
-  reference, as defined in <xref target="RFC5234" x:fmt="," x:sec="B.1"/>:
-  ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls),
-  DIGIT (decimal 0-9), DQUOTE (double quote),
-  HEXDIG (hexadecimal 0-9/A-F/a-f), LF (line feed),
-  OCTET (any 8-bit sequence of data), SP (space), and
-  VCHAR (any visible US-ASCII character).
-</t>
-<t>
-  The ABNF rules below are defined in <xref target="Part1"/> and
-  <xref target="Part2"/>:
-</t>
-<figure><artwork type="abnf2616">
-  <x:ref>OWS</x:ref>           = &lt;OWS, defined in &whitespace;&gt;
-  <x:ref>obs-text</x:ref>      = &lt;obs-text, defined in &field-components;&gt;
-  <x:ref>HTTP-date</x:ref>     = &lt;HTTP-date, defined in &http-date;&gt;
-</artwork></figure>
-<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>
 </section>