Changeset 2480

Timestamp:

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

Author:

julian.reschke@…

Message:

clarify integer parsing requirement (see #507)

Location:

draft-ietf-httpbis/latest

Files:

• p1-messaging.html (modified) (6 diffs)
• p1-messaging.xml (modified) (2 diffs)
• p5-range.html (modified) (7 diffs)
• p5-range.xml (modified) (2 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"

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

@@ -1711 +1711 @@
    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 &SHOULD; anticipate potentially large decimal numerals and
+   recipient &MUST; anticipate potentially large decimal numerals and
    prevent parsing errors due to integer conversion overflows
    (<xref target="attack.protocol.element.size.overflows"/>).
@@ -5414 +5414 @@
     </t>
     <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/507"/>:
+      "integer value parsing"
+    </t>
+    <t>
       <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/517"/>:
       "move IANA registrations to correct draft"

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

@@ -445 +445 @@
   }
   @bottom-center {
-       content: "Expires May 9, 2014";
+       content: "Expires May 11, 2014";
   }
   @bottom-right {
@@ -488 +488 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-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:2616">
       <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines range requests and the rules for constructing and combining responses to those requests.">
@@ -514 +514 @@
             </tr>
             <tr>
-               <td class="left">Expires: May 9, 2014</td>
+               <td class="left">Expires: May 11, 2014</td>
                <td class="right">J. Reschke, Editor</td>
             </tr>
@@ -523 +523 @@
             <tr>
                <td class="left"></td>
-               <td class="right">November 5, 2013</td>
+               <td class="right">November 7, 2013</td>
             </tr>
          </tbody>
@@ -549 +549 @@
             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">
@@ -718 +718 @@
             <p id="rfc.section.2.1.p.13">If a valid <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a> includes at least one <a href="#rule.ranges-specifier" class="smpl">byte-range-spec</a> with a <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> that is less than the current length of the representation, or at least one <a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a> with a non-zero <a href="#rule.ranges-specifier" class="smpl">suffix-length</a>, then the <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a> is satisfiable. Otherwise, the <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a> is unsatisfiable.
             </p>
-            <p id="rfc.section.2.1.p.14">In the byte range syntax, <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a>, <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a>, and <a href="#rule.ranges-specifier" class="smpl">suffix-length</a> are expressed as decimal number of octets. Since there is no predefined limit to the length of a payload, recipients ought
-               to anticipate potentially large decimal numerals and prevent parsing errors due to integer conversion overflows.
+            <p id="rfc.section.2.1.p.14">In the byte range syntax, <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a>, <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a>, and <a href="#rule.ranges-specifier" class="smpl">suffix-length</a> are expressed as decimal number of octets. Since there is no predefined limit to the length of a payload, recipients <em class="bcp14">MUST</em> anticipate potentially large decimal numerals and prevent parsing errors due to integer conversion overflows.
             </p>
          </div>
@@ -1380 +1379 @@
             <ul>
                <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/506">http://tools.ietf.org/wg/httpbis/trac/ticket/506</a>&gt;: "APPSDIR review of draft-ietf-httpbis-p5-range-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/508">http://tools.ietf.org/wg/httpbis/trac/ticket/508</a>&gt;: "broken sentence in description of 206"

draft-ietf-httpbis/latest/p5-range.xml

@@ -314 +314 @@
    <x:ref>last-byte-pos</x:ref>, and <x:ref>suffix-length</x:ref> are
    expressed as decimal number of octets. Since there is no predefined limit
-   to the length of a payload, recipients ought to anticipate potentially
+   to the length of a payload, recipients &MUST; anticipate potentially
    large decimal numerals and prevent parsing errors due to integer conversion
    overflows.
@@ -1514 +1514 @@
     </t>
     <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/507"/>:
+      "integer value parsing"
+    </t>
+    <t>
       <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/508"/>:
       "broken sentence in description of 206"