Changeset 1682 for draft-ietf-httpbis/latest/p7-auth.html

Timestamp:

21/06/12 09:01:49 (11 years ago)

Author:

julian.reschke@…

Message:

Clarify that in general recipients MUST be able to parse everything allowed by the ABNF (see #361)

File:

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

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

@@ -645 +645 @@
       <p id="rfc.section.1.1.p.4">This document also uses ABNF to define valid protocol elements (<a href="#notation" title="Syntax Notation">Section&nbsp;1.2</a>). In addition to the prose requirements placed upon them, Senders <em class="bcp14">MUST NOT</em> generate protocol elements that are invalid.
       </p>
-      <p id="rfc.section.1.1.p.5">Unless noted otherwise, Recipients <em class="bcp14">MAY</em> take steps to recover a usable protocol element from an invalid construct. However, HTTP does not define specific error handling
+      <p id="rfc.section.1.1.p.5">Unless noted otherwise, Recipients <em class="bcp14">MUST</em> be able to parse all protocol elements matching the ABNF rules defined for them and <em class="bcp14">MAY</em> take steps to recover a usable protocol element from an invalid construct. However, HTTP does not define specific error handling
          mechanisms, except in cases where it has direct impact on security. This is because different uses of the protocol require
          different error handling strategies; for example, a Web browser may wish to transparently recover from a response where the
@@ -1150 +1150 @@
          </li>
          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/357">http://tools.ietf.org/wg/httpbis/trac/ticket/357</a>&gt;: "Authentication exchanges"
+         </li>
+         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/361">http://tools.ietf.org/wg/httpbis/trac/ticket/361</a>&gt;: "ABNF requirements for recipients"
          </li>
       </ul>