Changeset 2003

Timestamp:

28/11/12 07:31:16 (9 years ago)

Author:

fielding@…

Message:

properly note that we are updating RFC2817 and RFC2818; addresses #128

Location:

draft-ietf-httpbis/latest

Files:

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

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

@@ -514 +514 @@
             </tr>
             <tr>
-               <td class="left">Updates: <a href="http://tools.ietf.org/html/rfc2817">2817</a> (if approved)
+               <td class="left">Updates: <a href="http://tools.ietf.org/html/rfc2817">2817</a>, <a href="http://tools.ietf.org/html/rfc2818">2818</a> (if approved)
                </td>
                <td class="right">greenbytes</td>
@@ -723 +723 @@
          </li>
       </ul>
-      <p id="rfc.section.1.p.2">This HTTP/1.1 specification obsoletes and moves to historic status <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2616.1">RFC 2616</cite>, its predecessor <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2068.1">RFC 2068</cite>, <cite title="Use and Interpretation of HTTP Version Numbers" id="rfc.xref.RFC2145.1">RFC 2145</cite> (on HTTP versioning), and <cite title="Upgrading to TLS Within HTTP/1.1" id="rfc.xref.RFC2817.1">RFC 2817</cite> (on using CONNECT for TLS upgrades).
+      <p id="rfc.section.1.p.2">This HTTP/1.1 specification obsoletes and moves to historic status <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2616.1">RFC 2616</cite>, its predecessor <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2068.1">RFC 2068</cite>, and <cite title="Use and Interpretation of HTTP Version Numbers" id="rfc.xref.RFC2145.1">RFC 2145</cite> (on HTTP versioning). This specification also updates the use of CONNECT to establish a tunnel, previously defined in <cite title="Upgrading to TLS Within HTTP/1.1" id="rfc.xref.RFC2817.1">RFC 2817</cite>, and defines the "https" URI scheme that was described informally in <cite title="HTTP Over TLS" id="rfc.xref.RFC2818.1">RFC 2818</cite>.
       </p>
       <p id="rfc.section.1.p.3">HTTP is a generic interface protocol for information systems. It is designed to hide the details of how a service is implemented
@@ -1084 +1084 @@
          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.7.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>.
+      <p id="rfc.section.2.7.2.p.6">The process for authoritative access to an "https" identified resource is defined in <a href="#RFC2818" id="rfc.xref.RFC2818.2"><cite title="HTTP Over TLS">[RFC2818]</cite></a>.
       </p>
       <h3 id="rfc.section.2.7.3"><a href="#rfc.section.2.7.3">2.7.3</a>&nbsp;<a id="uri.comparison" href="#uri.comparison">http and https URI Normalization and Comparison</a></h3>
@@ -3283 +3283 @@
                      </ul>
                   </li>
-                  <li><em>RFC2818</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2818.1">2.7.2</a>, <a href="#RFC2818"><b>10.2</b></a></li>
+                  <li><em>RFC2818</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2818.1">1</a>, <a href="#rfc.xref.RFC2818.2">2.7.2</a>, <a href="#RFC2818"><b>10.2</b></a></li>
                   <li><em>RFC3040</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3040.1">2.3</a>, <a href="#RFC3040"><b>10.2</b></a></li>
                   <li><em>RFC3864</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3864.1">7.1</a>, <a href="#RFC3864"><b>10.2</b></a></li>

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

@@ -69 +69 @@
 <?rfc-ext allow-markup-in-artwork="yes" ?>
 <?rfc-ext include-references-in-index="yes" ?>
-<rfc obsoletes="2145,2616" updates="2817" category="std" x:maturity-level="proposed"
+<rfc obsoletes="2145,2616" updates="2817,2818" category="std" x:maturity-level="proposed"
      ipr="pre5378Trust200902" docName="draft-ietf-httpbis-p1-messaging-&ID-VERSION;"
      xmlns:x='http://purl.org/net/xml2rfc/ext'>
@@ -158 +158 @@
    This HTTP/1.1 specification obsoletes and moves to historic status
    <xref target="RFC2616" x:fmt="none">RFC 2616</xref>, its predecessor
-   <xref target="RFC2068" x:fmt="none">RFC 2068</xref>,
-   <xref target="RFC2145" x:fmt="none">RFC 2145</xref> (on HTTP versioning),
-   and <xref target="RFC2817" x:fmt="none">RFC 2817</xref> (on using CONNECT
-   for TLS upgrades).
+   <xref target="RFC2068" x:fmt="none">RFC 2068</xref>, and
+   <xref target="RFC2145" x:fmt="none">RFC 2145</xref> (on HTTP versioning).
+   This specification also updates the use of CONNECT to establish a tunnel,
+   previously defined in <xref target="RFC2817" x:fmt="none">RFC 2817</xref>,
+   and defines the "https" URI scheme that was described informally in
+   <xref target="RFC2818" x:fmt="none">RFC 2818</xref>.
 </t>
 <t>