Changeset 2480 for draft-ietf-httpbis/latest/p1-messaging.html

Timestamp:

07/11/13 15:28:22 (7 years ago)

Author:

julian.reschke@…

Message:

clarify integer parsing requirement (see #507)

File:

• draft-ietf-httpbis/latest/p1-messaging.html (modified) (6 diffs)

draft-ietf-httpbis/latest/p1-messaging.html

@@ -445 +445 @@
   }
   @bottom-center {
-       content: "Expires May 9, 2014";
+       content: "Expires May 11, 2014";
   }
   @bottom-right {
@@ -487 +487 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2013-11-05">
+      <meta name="dct.issued" scheme="ISO8601" content="2013-11-07">
       <meta name="dct.replaces" content="urn:ietf:rfc:2145">
       <meta name="dct.replaces" content="urn:ietf:rfc:2616">
@@ -516 +516 @@
             <tr>
                <td class="left">Intended status: Standards Track</td>
-               <td class="right">November 5, 2013</td>
+               <td class="right">November 7, 2013</td>
             </tr>
             <tr>
-               <td class="left">Expires: May 9, 2014</td>
+               <td class="left">Expires: May 11, 2014</td>
                <td class="right"></td>
             </tr>
@@ -548 +548 @@
             in progress”.
          </p>
-         <p>This Internet-Draft will expire on May 9, 2014.</p>
+         <p>This Internet-Draft will expire on May 11, 2014.</p>
       </div>
       <div id="rfc.copyrightnotice">
@@ -1514 +1514 @@
                </p>
                <p id="rfc.section.3.3.2.p.11">Any Content-Length field value greater than or equal to zero is valid. Since there is no predefined limit to the length of
-                  a payload, a recipient <em class="bcp14">SHOULD</em> anticipate potentially large decimal numerals and prevent parsing errors due to integer conversion overflows (<a href="#attack.protocol.element.size.overflows" title="Buffer Overflows">Section&nbsp;9.3</a>).
+                  a payload, a recipient <em class="bcp14">MUST</em> anticipate potentially large decimal numerals and prevent parsing errors due to integer conversion overflows (<a href="#attack.protocol.element.size.overflows" title="Buffer Overflows">Section&nbsp;9.3</a>).
                </p>
                <p id="rfc.section.3.3.2.p.12">If a message is received that has multiple Content-Length header fields with field-values consisting of the same decimal value,
@@ -3427 +3427 @@
             <ul>
                <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/502">http://tools.ietf.org/wg/httpbis/trac/ticket/502</a>&gt;: "APPSDIR review of draft-ietf-httpbis-p1-messaging-24"
+               </li>
+               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/507">http://tools.ietf.org/wg/httpbis/trac/ticket/507</a>&gt;: "integer value parsing"
                </li>
                <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/517">http://tools.ietf.org/wg/httpbis/trac/ticket/517</a>&gt;: "move IANA registrations to correct draft"