Changeset 1017 for draft-ietf-httpbis-content-disp/02

Timestamp:

22/09/10 07:42:35 (10 years ago)

Author:

julian.reschke@…

Message:

prepare publication of draft-ietf-httpbis-content-disp-02

Location:

draft-ietf-httpbis-content-disp/02

Files:

• . (copied) (copied from draft-ietf-httpbis-content-disp/latest)
• draft-ietf-httpbis-content-disp-02.txt (added)
• draft-ietf-httpbis-content-disp-02.xml (added)
• draft-ietf-httpbis-content-disp.html (modified) (4 diffs)
• draft-ietf-httpbis-content-disp.xml (modified) (2 diffs)

draft-ietf-httpbis-content-disp/02/draft-ietf-httpbis-content-disp.html

@@ -400 +400 @@
       <link rel="schema.dct" href="http://purl.org/dc/terms/">
       <meta name="dct.creator" content="Reschke, J. F.">
-      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-content-disp-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2010-09-21">
+      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-content-disp-02">
+      <meta name="dct.issued" scheme="ISO8601" content="2010-09-22">
       <meta name="dct.abstract" content="HTTP/1.1 defines the Content-Disposition response header field, but points out that it is not part of the HTTP/1.1 Standard. This specification takes over the definition and registration of Content-Disposition, as used in HTTP, and clarifies internationalization aspects.">
       <meta name="description" content="HTTP/1.1 defines the Content-Disposition response header field, but points out that it is not part of the HTTP/1.1 Standard. This specification takes over the definition and registration of Content-Disposition, as used in HTTP, and clarifies internationalization aspects.">
@@ -419 +419 @@
                <td class="left">Updates: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved)
                </td>
-               <td class="right">September 21, 2010</td>
+               <td class="right">September 22, 2010</td>
             </tr>
             <tr>
@@ -426 +426 @@
             </tr>
             <tr>
-               <td class="left">Expires: March 25, 2011</td>
+               <td class="left">Expires: March 26, 2011</td>
                <td class="right"></td>
             </tr>
          </tbody>
       </table>
-      <p class="title">Use of the Content-Disposition&nbsp;Header&nbsp;Field in the Hypertext&nbsp;Transfer&nbsp;Protocol&nbsp;(HTTP)<br><span class="filename">draft-ietf-httpbis-content-disp-latest</span></p>
+      <p class="title">Use of the Content-Disposition&nbsp;Header&nbsp;Field in the Hypertext&nbsp;Transfer&nbsp;Protocol&nbsp;(HTTP)<br><span class="filename">draft-ietf-httpbis-content-disp-02</span></p>
       <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> 
       <p>HTTP/1.1 defines the Content-Disposition response header field, but points out that it is not part of the HTTP/1.1 Standard.
@@ -455 +455 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on March 25, 2011.</p>
+      <p>This Internet-Draft will expire on March 26, 2011.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>

draft-ietf-httpbis-content-disp/02/draft-ietf-httpbis-content-disp.xml

@@ -25 +25 @@
 ]>
 
-<rfc xmlns:x="http://purl.org/net/xml2rfc/ext" xmlns:ed="http://greenbytes.de/2002/rfcedit" ipr="trust200902" docName="draft-ietf-httpbis-content-disp-latest" category="std" x:maturity-level="proposed" xml:lang="en" updates="2616">
+<rfc xmlns:x="http://purl.org/net/xml2rfc/ext" xmlns:ed="http://greenbytes.de/2002/rfcedit" ipr="trust200902" docName="draft-ietf-httpbis-content-disp-02" category="std" x:maturity-level="proposed" xml:lang="en" updates="2616">
         <front>
   <title abbrev="Content-Disposition in HTTP">Use of the Content-Disposition&#160;Header&#160;Field
@@ -42 +42 @@
   </author>
 
-  <date month="September" year="2010"/>
+  <date month="September" year="2010" day="22"/>
   <workgroup>HTTPbis Working Group</workgroup>