Changeset 576 for draft-ietf-httpbis/latest/p5-range.html

Timestamp:

06/05/09 07:11:26 (13 years ago)

Author:

julian.reschke@…

Message:

Make spec consistent in not stating "decimal" when it's already clear from the ABNF (related to #161)

File:

• draft-ietf-httpbis/latest/p5-range.html (modified) (5 diffs)

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

@@ -467 +467 @@
          <tr>
             <td class="header left"></td>
-            <td class="header right">May 1, 2009</td>
+            <td class="header right">May 6, 2009</td>
          </tr>
       </table>
@@ -724 +724 @@
       </p>
       <p id="rfc.section.5.2.p.6">In the case of a byte range request: A server sending a response with status code 416 (Requested range not satisfiable) <em class="bcp14">SHOULD</em> include a Content-Range field with a byte-range-resp-spec of "*". The instance-length specifies the current length of the
-         selected resource as a decimal number. A response with status code 206 (Partial Content) <em class="bcp14">MUST NOT</em> include a Content-Range field with a byte-range-resp-spec of "*".
+         selected resource. A response with status code 206 (Partial Content) <em class="bcp14">MUST NOT</em> include a Content-Range field with a byte-range-resp-spec of "*".
       </p>
       <p id="rfc.section.5.2.p.7">Examples of byte-content-range-spec values, assuming that the entity contains a total of 1234 bytes: </p>
@@ -808 +808 @@
   <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a>   = 1*<a href="#notation" class="smpl">DIGIT</a>
 </pre><p id="rfc.section.5.4.1.p.5">The first-byte-pos value in a byte-range-spec gives the byte-offset of the first byte in a range. The last-byte-pos value
-         gives the byte-offset of the last byte in the range; that is, the byte positions specified are inclusive. Byte offsets are
-         decimal and start at zero.
+         gives the byte-offset of the last byte in the range; that is, the byte positions specified are inclusive. Byte offsets start
+         at zero.
       </p>
       <p id="rfc.section.5.4.1.p.6">If the last-byte-pos value is present, it <em class="bcp14">MUST</em> be greater than or equal to the first-byte-pos in that byte-range-spec, or the byte-range-spec is syntactically invalid. The
@@ -820 +820 @@
       <div id="rfc.figure.u.16"></div><pre class="inline"><span id="rfc.iref.g.21"></span><span id="rfc.iref.g.22"></span>  <a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a> = "-" <a href="#rule.ranges-specifier" class="smpl">suffix-length</a>
   <a href="#rule.ranges-specifier" class="smpl">suffix-length</a> = 1*<a href="#notation" class="smpl">DIGIT</a>
-</pre><p id="rfc.section.5.4.1.p.10">A suffix-byte-range-spec is used to specify the suffix of the entity-body, of a length given by the decimal suffix-length
-         value. (That is, this form specifies the last N bytes of an entity-body.) If the entity is shorter than the specified suffix-length,
-         the entire entity-body is used.
+</pre><p id="rfc.section.5.4.1.p.10">A suffix-byte-range-spec is used to specify the suffix of the entity-body, of a length given by the suffix-length value. (That
+         is, this form specifies the last N bytes of an entity-body.) If the entity is shorter than the specified suffix-length, the
+         entire entity-body is used.
       </p>
       <p id="rfc.section.5.4.1.p.11">If a syntactically valid byte-range-set includes at least one byte-range-spec whose first-byte-pos is less than the current
@@ -1227 +1227 @@
       </ul>
       <h2 id="rfc.section.D.8"><a href="#rfc.section.D.8">D.8</a>&nbsp;<a id="changes.since.06" href="#changes.since.06">Since draft-ietf-httpbis-p5-range-06</a></h2>
+      <p id="rfc.section.D.8.p.1">Closed issues: </p>
+      <ul>
+         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/161">http://tools.ietf.org/wg/httpbis/trac/ticket/161</a>&gt;: "base for numeric protocol elements"
+         </li>
+      </ul>
       <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
       <p class="noprint"><a href="#rfc.index.2">2</a> <a href="#rfc.index.4">4</a> <a href="#rfc.index.A">A</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a>