Changeset 2003


Ignore:
Timestamp:
Nov 27, 2012, 11:31:16 PM (7 years ago)
Author:
fielding@…
Message:

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

Location:
draft-ietf-httpbis/latest
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.html

    r2001 r2003  
    514514            </tr>
    515515            <tr>
    516                <td class="left">Updates: <a href="http://tools.ietf.org/html/rfc2817">2817</a> (if approved)
     516               <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)
    517517               </td>
    518518               <td class="right">greenbytes</td>
     
    723723         </li>
    724724      </ul>
    725       <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).
     725      <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>.
    726726      </p>
    727727      <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
     
    10841084         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.
    10851085      </p>
    1086       <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>.
     1086      <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>.
    10871087      </p>
    10881088      <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>
     
    32833283                     </ul>
    32843284                  </li>
    3285                   <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>
     3285                  <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>
    32863286                  <li><em>RFC3040</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3040.1">2.3</a>, <a href="#RFC3040"><b>10.2</b></a></li>
    32873287                  <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

    r1997 r2003  
    6969<?rfc-ext allow-markup-in-artwork="yes" ?>
    7070<?rfc-ext include-references-in-index="yes" ?>
    71 <rfc obsoletes="2145,2616" updates="2817" category="std" x:maturity-level="proposed"
     71<rfc obsoletes="2145,2616" updates="2817,2818" category="std" x:maturity-level="proposed"
    7272     ipr="pre5378Trust200902" docName="draft-ietf-httpbis-p1-messaging-&ID-VERSION;"
    7373     xmlns:x='http://purl.org/net/xml2rfc/ext'>
     
    158158   This HTTP/1.1 specification obsoletes and moves to historic status
    159159   <xref target="RFC2616" x:fmt="none">RFC 2616</xref>, its predecessor
    160    <xref target="RFC2068" x:fmt="none">RFC 2068</xref>,
    161    <xref target="RFC2145" x:fmt="none">RFC 2145</xref> (on HTTP versioning),
    162    and <xref target="RFC2817" x:fmt="none">RFC 2817</xref> (on using CONNECT
    163    for TLS upgrades).
     160   <xref target="RFC2068" x:fmt="none">RFC 2068</xref>, and
     161   <xref target="RFC2145" x:fmt="none">RFC 2145</xref> (on HTTP versioning).
     162   This specification also updates the use of CONNECT to establish a tunnel,
     163   previously defined in <xref target="RFC2817" x:fmt="none">RFC 2817</xref>,
     164   and defines the "https" URI scheme that was described informally in
     165   <xref target="RFC2818" x:fmt="none">RFC 2818</xref>.
    164166</t>
    165167<t>
Note: See TracChangeset for help on using the changeset viewer.