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

Timestamp:

Dec 30, 2007, 6:56:05 AM (12 years ago)

Author:

julian.reschke@…

Message:

Add templates for Changes sections throughout, remove intro specific to draft -00, enhance a few more inter-document references, cleanup some leftovers of the symref switchover.

File:

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

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

@@ -343 +343 @@
       <link rel="Appendix" title="A Internet Media Type multipart/byteranges" href="#rfc.section.A">
       <link rel="Appendix" title="B Compatibility with Previous Versions" href="#rfc.section.B">
+      <link rel="Appendix" title="C Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.C">
       <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.353, 2007/12/11 23:20:44, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
       <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/">
@@ -471 +472 @@
       </p> 
       <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1> 
-      <p>This version of the HTTP specification contains only minimal editorial changes from <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a> (abstract, introductory paragraph, and authors' addresses). All other changes are due to partitioning the original into seven
-         mostly independent parts. The intent is for readers of future drafts to able to use draft 00 as the basis for comparison when
-         the WG makes later changes to the specification text. This draft will shortly be followed by draft 01 (containing the first
-         round of changes that have already been agreed to on the mailing list). There is no point in reviewing this draft other than
-         to verify that the partitioning has been done correctly. Roy T. Fielding, Yves Lafon, and Julian Reschke will be the editors
-         after draft 00 is submitted.
-      </p>  
       <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org). The current issues
          list is at &lt;<a href="http://www.tools.ietf.org/wg/httpbis/trac/report/11">http://www.tools.ietf.org/wg/httpbis/trac/report/11</a>&gt; and related documents (including fancy diffs) can be found at &lt;<a href="http://www.tools.ietf.org/wg/httpbis/">http://www.tools.ietf.org/wg/httpbis/</a>&gt;.
@@ -517 +511 @@
             </ul>
          </li>
+         <li class="tocline0">C.&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc">
+               <li class="tocline1">C.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.1">Since RFC2616</a></li>
+               <li class="tocline1">C.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.2">Since draft-ietf-httpbis-p5-range-00</a></li>
+            </ul>
+         </li>
          <li class="tocline0"><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li>
          <li class="tocline0"><a href="#rfc.index">Index</a></li>
@@ -522 +521 @@
       <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a id="introduction" href="#introduction">Introduction</a></h1>
       <p id="rfc.section.1.p.1">This document will define aspects of HTTP related to range requests, partial responses, and the multipart/byteranges media
-         type. Right now it only includes the extracted relevant sections of <a href="#RFC2616">RFC 2616</a> <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2616.2">[RFC2616]</cite> without edit.
+         type. Right now it only includes the extracted relevant sections of <a href="#RFC2616">RFC 2616</a> <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2616.1">[RFC2616]</cite> without edit.
       </p>
       <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a id="intro.requirements" href="#intro.requirements">Requirements</a></h2>
@@ -889 +888 @@
       <p id="rfc.section.B.2.p.1">Clarify that it is not ok to use a weak cache validator in a 206 response. (<a href="#status.206" id="rfc.xref.status.206.1" title="206 Partial Content">Section&nbsp;3.1</a>)
       </p>
+      <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;Change Log (to be removed by RFC Editor before publication)
+      </h1>
+      <h2 id="rfc.section.C.1"><a href="#rfc.section.C.1">C.1</a>&nbsp;Since RFC2616
+      </h2>
+      <p id="rfc.section.C.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
+      </p>
+      <h2 id="rfc.section.C.2"><a href="#rfc.section.C.2">C.2</a>&nbsp;Since draft-ietf-httpbis-p5-range-00
+      </h2>
+      <p id="rfc.section.C.2.p.1">TBD.</p>
       <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
       <p>Copyright © The IETF Trust (2007).</p>
@@ -1002 +1010 @@
                   <li class="indline1"><em>RFC2046</em>&nbsp;&nbsp;<a class="iref" href="#RFC2046"><b>9</b></a>, <a class="iref" href="#rfc.xref.RFC2046.1">A</a></li>
                   <li class="indline1"><em>RFC2119</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2119.1">1.1</a>, <a class="iref" href="#RFC2119"><b>9</b></a></li>
-                  <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2616.1">§</a>, <a class="iref" href="#rfc.xref.RFC2616.2">1</a>, <a class="iref" href="#RFC2616"><b>9</b></a></li>
+                  <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2616.1">1</a>, <a class="iref" href="#RFC2616"><b>9</b></a>, <a class="iref" href="#rfc.xref.RFC2616.2">C.1</a></li>
                </ul>
             </li>