Changeset 1275 for draft-ietf-httpbis/latest/p1-messaging.xml

Timestamp:

28/04/11 06:24:11 (11 years ago)

Author:

julian.reschke@…

Message:

draft-ietf-httpstate-cookie published as RFC 6265

File:

• draft-ietf-httpbis/latest/p1-messaging.xml (modified) (4 diffs)

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>