Changeset 1084 for draft-ietf-httpbis-content-disp/latest/draft-ietf-httpbis-content-disp.html

Timestamp:

12/11/10 12:54:50 (10 years ago)

Author:

julian.reschke@…

Message:

fix a date

File:

• draft-ietf-httpbis-content-disp/latest/draft-ietf-httpbis-content-disp.html (modified) (5 diffs)

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

@@ -404 +404 @@
       <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-11-07">
+      <meta name="dct.issued" scheme="ISO8601" content="2010-11-12">
       <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.">
@@ -422 +422 @@
                <td class="left">Updates: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved)
                </td>
-               <td class="right">November 7, 2010</td>
+               <td class="right">November 12, 2010</td>
             </tr>
             <tr>
@@ -429 +429 @@
             </tr>
             <tr>
-               <td class="left">Expires: May 11, 2011</td>
+               <td class="left">Expires: May 16, 2011</td>
                <td class="right"></td>
             </tr>
@@ -458 +458 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on May 11, 2011.</p>
+      <p>This Internet-Draft will expire on May 16, 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>
@@ -822 +822 @@
       <p id="rfc.section.C.3.p.2">As with the approaches above, this is not interoperable and furthermore risks misinterpreting the actual value.</p>
       <h2 id="rfc.section.C.4"><a href="#rfc.section.C.4">C.4</a>&nbsp;<a id="alternatives.implementations" href="#alternatives.implementations">Implementations (to be removed by RFC Editor before publication)</a></h2>
-      <p id="rfc.section.C.4.p.1">Unfortunately, as of October 2010, neither the encoding defined in RFCs 2231 and 5987, nor any of the alternate approaches
+      <p id="rfc.section.C.4.p.1">Unfortunately, as of November 2010, neither the encoding defined in RFCs 2231 and 5987, nor any of the alternate approaches
          discussed above was implemented interoperably. Thus, this specification recommends the approach defined in RFC 5987, which
          at least has the advantage of actually being specified properly.