Changeset 1259

Timestamp:

Apr 4, 2011, 10:08:48 AM (9 years ago)

Author:

julian.reschke@…

Message:

Reference C-D spec in Changes from 2616 (see #123)

Location:

draft-ietf-httpbis/latest

Files:

• p3-payload.html (modified) (5 diffs)
• p3-payload.xml (modified) (3 diffs)

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

@@ -1605 +1605 @@
       <h2 id="rfc.references.2"><a href="#rfc.section.10.2" id="rfc.section.10.2">10.2</a> Informative References
       </h2>
-      <table>                              
+      <table>                                
          <tr>
             <td class="reference"><b id="BCP97">[BCP97]</b></td>
@@ -1679 +1679 @@
             <td class="reference"><b id="RFC5322">[RFC5322]</b></td>
             <td class="top">Resnick, P., “<a href="http://tools.ietf.org/html/rfc5322">Internet Message Format</a>”, RFC&nbsp;5322, October&nbsp;2008.
+            </td>
+         </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>
          </tr>
@@ -1763 +1768 @@
          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="#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="#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>
       <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>
@@ -1778 +1783 @@
          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.6">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>)
+      <p id="rfc.section.C.p.6">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>
+      <p id="rfc.section.C.p.7">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>)
       </p>
       <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
@@ -2084 +2091 @@
             <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>

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

@@ -2392 +2392 @@
 </reference>
 
+<reference anchor="draft-ietf-httpbis-content-disp">
+        <front>
+    <title abbrev="Content-Disposition in HTTP">Use of the Content-Disposition Header Field
+    in the Hypertext Transfer Protocol (HTTP)</title>
+    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke">
+      <organization abbrev="greenbytes">greenbytes GmbH</organization>
+      <address>
+        <email>julian.reschke@greenbytes.de</email>     
+      </address>
+    </author>
+    <date month="March" year="2011" day="28"/>
+  </front>
+  <seriesInfo name='Internet-Draft' value='draft-ietf-httpbis-content-disp-09' />
+</reference>
 
 </references>
@@ -2548 +2562 @@
 <t>
    A number of other header fields, such as Content-Disposition and Title,
-   from SMTP and MIME are also often implemented (see <xref target="RFC2076"/>).
+   from SMTP and MIME are also often implemented (see <xref target="draft-ietf-httpbis-content-disp"/>
+         and <xref target="RFC2076"/>).
 </t>
 </section>
@@ -2576 +2591 @@
   of potentially breaking relative links in content-negotiated resources.
   (<xref target="header.content-location"/>)
+</t>
+<t>
+        Remove discussion of Content-Disposition header field, it is now defined
+        by <xref target="draft-ietf-httpbis-content-disp"/>.
+  (<xref target="additional.features"/>)
 </t>
 <t>