Changeset 1275 for draft-ietf-httpbis

Timestamp:

Apr 27, 2011, 11:24:11 PM (9 years ago)

Author:

julian.reschke@…

Message:

draft-ietf-httpstate-cookie published as RFC 6265

Location:

draft-ietf-httpbis/latest

Files:

• p1-messaging.html (modified) (11 diffs)
• p1-messaging.xml (modified) (4 diffs)

draft-ietf-httpbis/latest/p1-messaging.html

@@ -359 +359 @@
   } 
   @bottom-center {
-       content: "Expires October 20, 2011"; 
+       content: "Expires October 30, 2011"; 
   } 
   @bottom-right {
@@ -410 +410 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2011-04-18">
+      <meta name="dct.issued" scheme="ISO8601" content="2011-04-28">
       <meta name="dct.replaces" content="urn:ietf:rfc:2145">
       <meta name="dct.replaces" content="urn:ietf:rfc:2616">
@@ -442 +442 @@
             </tr>
             <tr>
-               <td class="left">Expires: October 20, 2011</td>
+               <td class="left">Expires: October 30, 2011</td>
                <td class="right">HP</td>
             </tr>
@@ -495 +495 @@
             <tr>
                <td class="left"></td>
-               <td class="right">April 18, 2011</td>
+               <td class="right">April 28, 2011</td>
             </tr>
          </tbody>
@@ -525 +525 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on October 20, 2011.</p>
+      <p>This Internet-Draft will expire on October 30, 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>
@@ -1149 +1149 @@
          indicate the same authority (the same host listening to the same TCP port). They are distinct name spaces and are considered
          to be distinct origin servers. However, an extension to HTTP that is defined to apply to entire host domains, such as the
-         Cookie protocol <a href="#draft-ietf-httpstate-cookie" id="rfc.xref.draft-ietf-httpstate-cookie.1"><cite title="HTTP State Management Mechanism">[draft-ietf-httpstate-cookie]</cite></a>, can allow information set by one service to impact communication with other services within a matching group of host domains.
+         Cookie protocol <a href="#RFC6265" id="rfc.xref.RFC6265.1"><cite title="HTTP State Management Mechanism">[RFC6265]</cite></a>, can allow information set by one service to impact communication with other services within a matching group of host domains.
       </p>
       <p id="rfc.section.2.6.2.p.6">The process for authoritative access to an "https" identified resource is defined in <a href="#RFC2818" id="rfc.xref.RFC2818.1"><cite title="HTTP Over TLS">[RFC2818]</cite></a>.
@@ -1240 +1240 @@
       <div class="note" id="rfc.section.3.2.p.7"> 
          <p> <b>Note:</b> The "Set-Cookie" header field as implemented in practice can occur multiple times, but does not use the list syntax, and thus
-            cannot be combined into a single line (<a href="#draft-ietf-httpstate-cookie" id="rfc.xref.draft-ietf-httpstate-cookie.2"><cite title="HTTP State Management Mechanism">[draft-ietf-httpstate-cookie]</cite></a>). (See Appendix A.2.3 of <a href="#Kri2001" id="rfc.xref.Kri2001.1"><cite title="HTTP Cookies: Standards, Privacy, and Politics">[Kri2001]</cite></a> for details.) Also note that the Set-Cookie2 header field specified in <a href="#RFC2965" id="rfc.xref.RFC2965.1"><cite title="HTTP State Management Mechanism">[RFC2965]</cite></a> does not share this problem.
+            cannot be combined into a single line (<a href="#RFC6265" id="rfc.xref.RFC6265.2"><cite title="HTTP State Management Mechanism">[RFC6265]</cite></a>). (See Appendix A.2.3 of <a href="#Kri2001" id="rfc.xref.Kri2001.1"><cite title="HTTP Cookies: Standards, Privacy, and Politics">[Kri2001]</cite></a> for details.) Also note that the Set-Cookie2 header field specified in <a href="#RFC2965" id="rfc.xref.RFC2965.1"><cite title="HTTP State Management Mechanism">[RFC2965]</cite></a> does not share this problem.
          </p> 
       </div>
@@ -2933 +2933 @@
          </tr>
          <tr>
+            <td class="reference"><b id="RFC6265">[RFC6265]</b></td>
+            <td class="top"><a href="mailto:abarth@eecs.berkeley.edu" title="&#xA;        University of California, Berkeley&#xA;      ">Barth, A.</a>, “<a href="http://tools.ietf.org/html/rfc6265">HTTP State Management Mechanism</a>”, RFC&nbsp;6265, April&nbsp;2011.
+            </td>
+         </tr>
+         <tr>
             <td class="reference"><b id="Spe">[Spe]</b></td>
             <td class="top">Spero, S., “<a href="http://sunsite.unc.edu/mdma-release/http-prob.html">Analysis of HTTP Performance Problems</a>”, &lt;<a href="http://sunsite.unc.edu/mdma-release/http-prob.html">http://sunsite.unc.edu/mdma-release/http-prob.html</a>&gt;.
@@ -2940 +2945 @@
             <td class="reference"><b id="Tou1998">[Tou1998]</b></td>
             <td class="top"><a href="mailto:touch@isi.edu" title="USC/Information Sciences Institute">Touch, J.</a>, <a href="mailto:johnh@isi.edu" title="USC/Information Sciences Institute">Heidemann, J.</a>, and <a href="mailto:katia@isi.edu" title="USC/Information Sciences Institute">K. Obraczka</a>, “<a href="http://www.isi.edu/touch/pubs/http-perf96/">Analysis of HTTP Performance</a>”, ISI Research Report&nbsp;ISI/RR-98-463, Aug&nbsp;1998, &lt;<a href="http://www.isi.edu/touch/pubs/http-perf96/">http://www.isi.edu/touch/pubs/http-perf96/</a>&gt;.<br>(original report dated Aug. 1996)
-            </td>
-         </tr>
-         <tr>
-            <td class="reference"><b id="draft-ietf-httpstate-cookie">[draft-ietf-httpstate-cookie]</b></td>
-            <td class="top"><a href="mailto:abarth@eecs.berkeley.edu" title="&#xA;        University of California, Berkeley&#xA;      ">Barth, A.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpstate-cookie-23">HTTP State Management Mechanism</a>”, Internet-Draft&nbsp;draft-ietf-httpstate-cookie-23 (work in progress), March&nbsp;2011.
             </td>
          </tr>
@@ -3622 +3622 @@
                   <li>deflate (Coding Format)&nbsp;&nbsp;<a href="#rfc.iref.d.2">6.2.2.2</a></li>
                   <li>downstream&nbsp;&nbsp;<a href="#rfc.iref.d.1"><b>2.3</b></a></li>
-                  <li><em>draft-ietf-httpstate-cookie</em>&nbsp;&nbsp;<a href="#rfc.xref.draft-ietf-httpstate-cookie.1">2.6.2</a>, <a href="#rfc.xref.draft-ietf-httpstate-cookie.2">3.2</a>, <a href="#draft-ietf-httpstate-cookie"><b>13.2</b></a></li>
                </ul>
             </li>
@@ -3895 +3894 @@
                      </ul>
                   </li>
+                  <li><em>RFC6265</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC6265.1">2.6.2</a>, <a href="#rfc.xref.RFC6265.2">3.2</a>, <a href="#RFC6265"><b>13.2</b></a></li>
                </ul>
             </li>

draft-ietf-httpbis/latest/p1-messaging.xml

@@ -1102 +1102 @@
    distinct origin servers.  However, an extension to HTTP that is
    defined to apply to entire host domains, such as the Cookie protocol 
-   <xref target="draft-ietf-httpstate-cookie"/>, can allow information
+   <xref target="RFC6265"/>, can allow information
    set by one service to impact communication with other services
    within a matching group of host domains.
@@ -1292 +1292 @@
    <x:h>Note:</x:h> The "Set-Cookie" header field as implemented in
    practice can occur multiple times, but does not use the list syntax, and
-   thus cannot be combined into a single line (<xref target="draft-ietf-httpstate-cookie"/>). (See Appendix A.2.3 of <xref target="Kri2001"/>
+   thus cannot be combined into a single line (<xref target="RFC6265"/>). (See Appendix A.2.3 of <xref target="Kri2001"/>
    for details.) Also note that the Set-Cookie2 header field specified in
    <xref target="RFC2965"/> does not share this problem. 
@@ -4764 +4764 @@
 </reference>
 
-<reference anchor='draft-ietf-httpstate-cookie'>
+<reference anchor="RFC6265">
   <front>
     <title>HTTP State Management Mechanism</title>
@@ -4773 +4773 @@
       <address><email>abarth@eecs.berkeley.edu</email></address>
     </author>
-    <date year='2011' month='March' />
+    <date year="2011" month="April" />
   </front>
-  <seriesInfo name="Internet-Draft" value="draft-ietf-httpstate-cookie-23"/>
+  <seriesInfo name="RFC" value="6265"/>
 </reference>