Changeset 1307

Timestamp:

Jun 10, 2011, 12:24:02 AM (9 years ago)

Author:

julian.reschke@…

Message:

draft-ietf-httpbis-content-disp -> RFC6266 (see #123)

Location:

draft-ietf-httpbis/latest

Files:

• p3-payload.html (modified) (10 diffs)
• p3-payload.xml (modified) (4 diffs)

draft-ietf-httpbis/latest/p3-payload.html

@@ -359 +359 @@
   } 
   @bottom-center {
-       content: "Expires December 3, 2011"; 
+       content: "Expires December 12, 2011"; 
   } 
   @bottom-right {
@@ -408 +408 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p3-payload-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2011-06-01">
+      <meta name="dct.issued" scheme="ISO8601" content="2011-06-10">
       <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, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 3 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 3 defines HTTP message content, metadata, and content negotiation.">
@@ -434 +434 @@
             </tr>
             <tr>
-               <td class="left">Expires: December 3, 2011</td>
+               <td class="left">Expires: December 12, 2011</td>
                <td class="right">J. Mogul</td>
             </tr>
@@ -491 +491 @@
             <tr>
                <td class="left"></td>
-               <td class="right">June 1, 2011</td>
+               <td class="right">June 10, 2011</td>
             </tr>
          </tbody>
@@ -519 +519 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on December 3, 2011.</p>
+      <p>This Internet-Draft will expire on December 12, 2011.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
@@ -1639 +1639 @@
          </tr>
          <tr>
-            <td class="reference"><b id="draft-ietf-httpbis-content-disp">[draft-ietf-httpbis-content-disp]</b></td>
-            <td class="top"><a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">Reschke, J.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-content-disp-09">Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-content-disp-09 (work in progress), March&nbsp;2011.
+            <td class="reference"><b id="RFC6266">[RFC6266]</b></td>
+            <td class="top"><a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">Reschke, J.</a>, “<a href="http://tools.ietf.org/html/rfc6266">Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)</a>”, RFC&nbsp;6266, June&nbsp;2011.
             </td>
          </tr>
@@ -1725 +1725 @@
          experimental deployment found lacking that are now addressed in the base HTTP/1.1 specification.
       </p>
-      <p id="rfc.section.B.p.2">A number of other header fields, such as Content-Disposition and Title, from SMTP and MIME are also often implemented (see <a href="#draft-ietf-httpbis-content-disp" id="rfc.xref.draft-ietf-httpbis-content-disp.1"><cite title="Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)">[draft-ietf-httpbis-content-disp]</cite></a> and <a href="#RFC2076" id="rfc.xref.RFC2076.1"><cite title="Common Internet Message Headers">[RFC2076]</cite></a>).
+      <p id="rfc.section.B.p.2">A number of other header fields, such as Content-Disposition and Title, from SMTP and MIME are also often implemented (see <a href="#RFC6266" id="rfc.xref.RFC6266.1"><cite title="Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)">[RFC6266]</cite></a> and <a href="#RFC2076" id="rfc.xref.RFC2076.1"><cite title="Common Internet Message Headers">[RFC2076]</cite></a>).
       </p>
       <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h1>
@@ -1743 +1743 @@
          relative links in content-negotiated resources. (<a href="#header.content-location" id="rfc.xref.header.content-location.3" title="Content-Location">Section&nbsp;6.7</a>)
       </p>
-      <p id="rfc.section.C.p.7">Remove discussion of Content-Disposition header field, it is now defined by <a href="#draft-ietf-httpbis-content-disp" id="rfc.xref.draft-ietf-httpbis-content-disp.2"><cite title="Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)">[draft-ietf-httpbis-content-disp]</cite></a>. (<a href="#additional.features" title="Additional Features">Appendix&nbsp;B</a>)
+      <p id="rfc.section.C.p.7">Remove discussion of Content-Disposition header field, it is now defined by <a href="#RFC6266" id="rfc.xref.RFC6266.2"><cite title="Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)">[RFC6266]</cite></a>. (<a href="#additional.features" title="Additional Features">Appendix&nbsp;B</a>)
       </p>
       <p id="rfc.section.C.p.8">Remove reference to non-existant identity transfer-coding value tokens. (<a href="#no.content-transfer-encoding" title="No Content-Transfer-Encoding">Appendix&nbsp;A.5</a>)
@@ -2052 +2052 @@
             <li><a id="rfc.index.D" href="#rfc.index.D"><b>D</b></a><ul>
                   <li>deflate (Coding Format)&nbsp;&nbsp;<a href="#rfc.iref.d.1">2.2</a></li>
-                  <li><em>draft-ietf-httpbis-content-disp</em>&nbsp;&nbsp;<a href="#draft-ietf-httpbis-content-disp"><b>10.2</b></a>, <a href="#rfc.xref.draft-ietf-httpbis-content-disp.1">B</a>, <a href="#rfc.xref.draft-ietf-httpbis-content-disp.2">C</a></li>
                </ul>
             </li>
@@ -2202 +2201 @@
                   </li>
                   <li><em>RFC6151</em>&nbsp;&nbsp;<a href="#RFC6151"><b>10.2</b></a>, <a href="#rfc.xref.RFC6151.1">C</a></li>
+                  <li><em>RFC6266</em>&nbsp;&nbsp;<a href="#RFC6266"><b>10.2</b></a>, <a href="#rfc.xref.RFC6266.1">B</a>, <a href="#rfc.xref.RFC6266.2">C</a></li>
                </ul>
             </li>

draft-ietf-httpbis/latest/p3-payload.xml

@@ -2310 +2310 @@
 </reference>
 
-<reference anchor="draft-ietf-httpbis-content-disp">
+<reference anchor="RFC6266">
         <front>
     <title abbrev="Content-Disposition in HTTP">Use of the Content-Disposition Header Field
@@ -2320 +2320 @@
       </address>
     </author>
-    <date month="March" year="2011" day="28"/>
+    <date month="June" year="2011"/>
   </front>
-  <seriesInfo name='Internet-Draft' value='draft-ietf-httpbis-content-disp-09' />
+  <seriesInfo name='RFC' value='6266' />
 </reference>
 
@@ -2480 +2480 @@
 <t>
    A number of other header fields, such as Content-Disposition and Title,
-   from SMTP and MIME are also often implemented (see <xref target="draft-ietf-httpbis-content-disp"/>
-         and <xref target="RFC2076"/>).
+   from SMTP and MIME are also often implemented (see <xref target="RFC6266"/>
+   and <xref target="RFC2076"/>).
 </t>
 </section>
@@ -2518 +2518 @@
 <t>
         Remove discussion of Content-Disposition header field, it is now defined
-        by <xref target="draft-ietf-httpbis-content-disp"/>.
+        by <xref target="RFC6266"/>.
   (<xref target="additional.features"/>)
 </t>