Changeset 2488


Ignore:
Timestamp:
11/11/13 21:03:06 (7 years ago)
Author:
fielding@…
Message:

Fix the maximum value for delta-seconds for senders to be 2147483647 instead of 2147483648, since the goal was to prevent 32bit INT_MAX overflow on recipients; reduce other implementation requirements to an ought and to what is necessary to preserve the intended value; see #512

Location:
draft-ietf-httpbis/latest
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p6-cache.html

    r2485 r2488  
    723723               <p id="rfc.section.1.2.1.p.1">The delta-seconds rule specifies a non-negative integer, representing time in seconds.</p>
    724724               <div id="rfc.figure.u.1"></div><pre class="inline"><span id="rfc.iref.g.1"></span>  <a href="#delta-seconds" class="smpl">delta-seconds</a>  = 1*<a href="#imported.abnf" class="smpl">DIGIT</a>
    725 </pre><p id="rfc.section.1.2.1.p.3">If a cache receives a delta-seconds value larger than the largest positive integer it can represent, or if any of its subsequent
    726                   calculations overflows, the cache <em class="bcp14">MUST</em> consider the value to be 2147483648 (2<sup>31</sup>). A recipient parsing a delta-seconds value <em class="bcp14">MUST</em> use an arithmetic type of at least 31 bits of range, and a sender <em class="bcp14">MUST NOT</em> generate delta-seconds with a value greater than 2147483648.
    727                </p>
    728                <p id="rfc.section.1.2.1.p.4">Note that this value (2147483648) might cause implementation issues on some platforms (in particular, those that represent
    729                   MAX_INT as 2<sup>31</sup>-1), and therefore ought to be handled carefullly.
     725</pre><p id="rfc.section.1.2.1.p.3">A recipient parsing a delta-seconds value ought to use an arithmetic type of at least 32 bits of signed integer range. A sender <em class="bcp14">MUST NOT</em> generate a delta-seconds value greater than 2147483647 (32bit INT_MAX, or 2<sup>31</sup> - 1).
     726               </p>
     727               <p id="rfc.section.1.2.1.p.4">If a cache receives a delta-seconds value larger than the largest positive integer it can represent, or if any of its subsequent
     728                  calculations overflows, the cache <em class="bcp14">MUST</em> consider the value to be the largest positive integer it can represent.
    730729               </p>
    731730            </div>
  • draft-ietf-httpbis/latest/p6-cache.xml

    r2485 r2488  
    213213</artwork></figure>
    214214<t>
     215   A recipient parsing a delta-seconds value ought to use an arithmetic type
     216   of at least 32 bits of signed integer range. A sender &MUST-NOT; generate a
     217   delta-seconds value greater than 2147483647 (32bit INT_MAX, or
     218   2<x:sup>31</x:sup> - 1).
     219</t>
     220<t>
    215221   If a cache receives a delta-seconds value larger than the largest
    216222   positive integer it can represent, or if any of its subsequent calculations
    217    overflows, the cache &MUST; consider the value to be 2147483648
    218    (2<x:sup>31</x:sup>). A recipient parsing a delta-seconds value &MUST; use
    219    an arithmetic type of at least 31 bits of range, and a sender &MUST-NOT;
    220    generate delta-seconds with a value greater than 2147483648.
    221 </t>
    222 <t>
    223    Note that this value (2147483648) might cause implementation issues on some
    224    platforms (in particular, those that represent MAX_INT as
    225    2<x:sup>31</x:sup>-1), and therefore ought to be handled carefullly.
     223   overflows, the cache &MUST; consider the value to be the largest positive
     224   integer it can represent.
    226225</t>
    227226</section>
Note: See TracChangeset for help on using the changeset viewer.