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

File:
1 edited

Legend:

Unmodified
Added
Removed
  • 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.