Jun 21, 2012, 2:01:49 AM (7 years ago)

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

1 edited


  • draft-ietf-httpbis/latest/p5-range.html

    r1667 r1682  
    449449  }
    450450  @bottom-center {
    451        content: "Expires December 3, 2012";
     451       content: "Expires December 23, 2012";
    452452  }
    453453  @bottom-right {
    492492      <meta name="dct.creator" content="Reschke, J. F.">
    493493      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest">
    494       <meta name="dct.issued" scheme="ISO8601" content="2012-06-01">
     494      <meta name="dct.issued" scheme="ISO8601" content="2012-06-21">
    495495      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    496496      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 5 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 5 defines range requests and the rules for constructing and combining responses to those requests.">
    518518            </tr>
    519519            <tr>
    520                <td class="left">Expires: December 3, 2012</td>
     520               <td class="left">Expires: December 23, 2012</td>
    521521               <td class="right">J. Reschke, Editor</td>
    522522            </tr>
    527527            <tr>
    528528               <td class="left"></td>
    529                <td class="right">June 1, 2012</td>
     529               <td class="right">June 21, 2012</td>
    530530            </tr>
    531531         </tbody>
    555555         in progress”.
    556556      </p>
    557       <p>This Internet-Draft will expire on December 3, 2012.</p>
     557      <p>This Internet-Draft will expire on December 23, 2012.</p>
    558558      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    559559      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    680680      <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.
    681681      </p>
    682       <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
     682      <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
    683683         mechanisms, except in cases where it has direct impact on security. This is because different uses of the protocol require
    684684         different error handling strategies; for example, a Web browser may wish to transparently recover from a response where the
    14931493      <ul>
    14941494         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/358">http://tools.ietf.org/wg/httpbis/trac/ticket/358</a>&gt;: "ABNF list expansion code problem"
     1495         </li>
     1496         <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"
    14951497         </li>
    14961498      </ul>
Note: See TracChangeset for help on using the changeset viewer.