source: draft-ietf-httpbis/orig/rfc2817.html @ 1050

Last change on this file since 1050 was 978, checked in by julian.reschke@…, 13 years ago

regen HTML using latest version of xslt

  • Property svn:eol-style set to native
  • Property svn:mime-type set to text/html
File size: 49.6 KB
1<!DOCTYPE html
2  PUBLIC "-//W3C//DTD HTML 4.01//EN">
3<html lang="en">
4   <head profile="">
5      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
6      <title>Upgrading to TLS Within HTTP/1.1</title><style type="text/css" title="Xml2Rfc (sans serif)">
7a {
8  text-decoration: none;
10a.smpl {
11  color: black;
13a:hover {
14  text-decoration: underline;
16a:active {
17  text-decoration: underline;
19address {
20  margin-top: 1em;
21  margin-left: 2em;
22  font-style: normal;
24body {
25  color: black;
26  font-family: verdana, helvetica, arial, sans-serif;
27  font-size: 10pt;
29cite {
30  font-style: normal;
32dd {
33  margin-right: 2em;
35dl {
36  margin-left: 2em;
39ul.empty {
40  list-style-type: none;
42ul.empty li {
43  margin-top: .5em;
45dl p {
46  margin-left: 0em;
48dt {
49  margin-top: .5em;
51h1 {
52  font-size: 14pt;
53  line-height: 21pt;
54  page-break-after: avoid;
55} {
57  page-break-before: always;
59h1 a {
60  color: #333333;
62h2 {
63  font-size: 12pt;
64  line-height: 15pt;
65  page-break-after: avoid;
67h3, h4, h5, h6 {
68  font-size: 10pt;
69  page-break-after: avoid;
71h2 a, h3 a, h4 a, h5 a, h6 a {
72  color: black;
74img {
75  margin-left: 3em;
77li {
78  margin-left: 2em;
79  margin-right: 2em;
81ol {
82  margin-left: 2em;
83  margin-right: 2em;
85ol p {
86  margin-left: 0em;
88p {
89  margin-left: 2em;
90  margin-right: 2em;
92pre {
93  margin-left: 3em;
94  background-color: lightyellow;
95  padding: .25em;
97pre.text2 {
98  border-style: dotted;
99  border-width: 1px;
100  background-color: #f0f0f0;
101  width: 69em;
103pre.inline {
104  background-color: white;
105  padding: 0em;
107pre.text {
108  border-style: dotted;
109  border-width: 1px;
110  background-color: #f8f8f8;
111  width: 69em;
113pre.drawing {
114  border-style: solid;
115  border-width: 1px;
116  background-color: #f8f8f8;
117  padding: 2em;
119table {
120  margin-left: 2em;
122table.header {
123  border-spacing: 1px;
124  width: 95%;
125  font-size: 10pt;
126  color: white;
127} {
129  vertical-align: top;
131td.topnowrap {
132  vertical-align: top;
133  white-space: nowrap;
135table.header td {
136  background-color: gray;
137  width: 50%;
139table.header a {
140  color: white;
142td.reference {
143  vertical-align: top;
144  white-space: nowrap;
145  padding-right: 1em;
147thead {
148  display:table-header-group;
150ul.toc {
151  list-style: none;
152  margin-left: 1.5em;
153  margin-right: 0em;
154  padding-left: 0em;
156li.tocline0 {
157  line-height: 150%;
158  font-weight: bold;
159  font-size: 10pt;
160  margin-left: 0em;
161  margin-right: 0em;
163li.tocline1 {
164  line-height: normal;
165  font-weight: normal;
166  font-size: 9pt;
167  margin-left: 0em;
168  margin-right: 0em;
170li.tocline2 {
171  font-size: 0pt;
173ul p {
174  margin-left: 0em;
176.bcp14 {
177  font-style: normal;
178  text-transform: lowercase;
179  font-variant: small-caps;
181.comment {
182  background-color: yellow;
183} {
185  text-align: center;
187.error {
188  color: red;
189  font-style: italic;
190  font-weight: bold;
192.figure {
193  font-weight: bold;
194  text-align: center;
195  font-size: 9pt;
197.filename {
198  color: #333333;
199  font-weight: bold;
200  font-size: 12pt;
201  line-height: 21pt;
202  text-align: center;
204.fn {
205  font-weight: bold;
207.hidden {
208  display: none;
210.left {
211  text-align: left;
213.right {
214  text-align: right;
216.title {
217  color: #990000;
218  font-size: 18pt;
219  line-height: 18pt;
220  font-weight: bold;
221  text-align: center;
222  margin-top: 36pt;
224.vcardline {
225  display: block;
227.warning {
228  font-size: 14pt;
229  background-color: yellow;
233@media print {
234  .noprint {
235    display: none;
236  }
238  a {
239    color: black;
240    text-decoration: none;
241  }
243  table.header {
244    width: 90%;
245  }
247  td.header {
248    width: 50%;
249    color: black;
250    background-color: white;
251    vertical-align: top;
252    font-size: 12pt;
253  }
255  ul.toc a::after {
256    content: leader('.') target-counter(attr(href), page);
257  }
259  a.iref {
260    content: target-counter(attr(href), page);
261  }
263  .print2col {
264    column-count: 2;
265    -moz-column-count: 2;
266    column-fill: auto;
267  }
270@page {
271  @top-left {
272       content: "RFC 2817";
273  }
274  @top-right {
275       content: "May 2000";
276  }
277  @top-center {
278       content: "Upgrading to TLS Within HTTP/1.1";
279  }
280  @bottom-left {
281       content: "Khare & Lawrence";
282  }
283  @bottom-center {
284       content: "Standards Track";
285  }
286  @bottom-right {
287       content: "[Page " counter(page) "]";
288  }
291@page:first {
292    @top-left {
293      content: normal;
294    }
295    @top-right {
296      content: normal;
297    }
298    @top-center {
299      content: normal;
300    }
302</style><link rel="Contents" href="#rfc.toc">
303      <link rel="Author" href="#rfc.authors">
304      <link rel="Copyright" href="#rfc.copyright">
305      <link rel="Chapter" title="1 Motivation" href="#rfc.section.1">
306      <link rel="Chapter" title="2 Introduction" href="#rfc.section.2">
307      <link rel="Chapter" title="3 Client Requested Upgrade to HTTP over TLS" href="#rfc.section.3">
308      <link rel="Chapter" title="4 Server Requested Upgrade to HTTP over TLS" href="#rfc.section.4">
309      <link rel="Chapter" title="5 Upgrade across Proxies" href="#rfc.section.5">
310      <link rel="Chapter" title="6 Rationale for the use of a 4xx (client error) Status Code" href="#rfc.section.6">
311      <link rel="Chapter" title="7 IANA Considerations" href="#rfc.section.7">
312      <link rel="Chapter" title="8 Security Considerations" href="#rfc.section.8">
313      <link rel="Chapter" href="#rfc.section.9" title="9 References">
314      <link rel="Appendix" title="A Acknowledgments" href="#rfc.section.A">
315      <link rel="Alternate" title="Authorative ASCII Version" href="">
316      <link rel="Help" title="Additional Information on" href="">
317      <meta name="generator" content=", Revision 1.520, 2010-07-14 12:36:35, XSLT vendor: SAXON 8.9 from Saxonica">
318      <link rel="schema.dct" href="">
319      <meta name="dct.creator" content="Khare, R.">
320      <meta name="dct.creator" content="Lawrence, S.">
321      <meta name="dct.identifier" content="urn:ietf:rfc:2817">
322      <meta name="dct.issued" scheme="ISO8601" content="2000-05">
323      <meta name="dct.abstract" content="This memo explains how to use the Upgrade mechanism in HTTP/1.1 to initiate Transport Layer Security (TLS) over an existing TCP connection. This allows unsecured and secured HTTP traffic to share the same well known port (in this case, http: at 80 rather than https: at 443). It also enables &#34;virtual hosting&#34;, so a single HTTP + TLS server can disambiguate traffic intended for several hostnames at a single IP address. Since HTTP/1.1 defines Upgrade as a hop-by-hop mechanism, this memo also documents the HTTP CONNECT method for establishing end-to-end tunnels across HTTP proxies. Finally, this memo establishes new IANA registries for public HTTP status codes, as well as public or private Upgrade product tokens. This memo does NOT affect the current definition of the 'https' URI scheme, which already defines a separate namespace ( and are not equivalent).">
324      <meta name="dct.isPartOf" content="urn:issn:2070-1721">
325      <meta name="description" content="This memo explains how to use the Upgrade mechanism in HTTP/1.1 to initiate Transport Layer Security (TLS) over an existing TCP connection. This allows unsecured and secured HTTP traffic to share the same well known port (in this case, http: at 80 rather than https: at 443). It also enables &#34;virtual hosting&#34;, so a single HTTP + TLS server can disambiguate traffic intended for several hostnames at a single IP address. Since HTTP/1.1 defines Upgrade as a hop-by-hop mechanism, this memo also documents the HTTP CONNECT method for establishing end-to-end tunnels across HTTP proxies. Finally, this memo establishes new IANA registries for public HTTP status codes, as well as public or private Upgrade product tokens. This memo does NOT affect the current definition of the 'https' URI scheme, which already defines a separate namespace ( and are not equivalent).">
326   </head>
327   <body>
328      <table class="header">
329         <tbody>
330            <tr>
331               <td class="left">Network Working Group</td>
332               <td class="right">R. Khare</td>
333            </tr>
334            <tr>
335               <td class="left">Request for Comments: 2817</td>
336               <td class="right">4K Associates / UC Irvine</td>
337            </tr>
338            <tr>
339               <td class="left">Updates: <a href="">2616</a></td>
340               <td class="right">S. Lawrence</td>
341            </tr>
342            <tr>
343               <td class="left">Category: Standards Track</td>
344               <td class="right">Agranat Systems, Inc.</td>
345            </tr>
346            <tr>
347               <td class="left"></td>
348               <td class="right">May 2000</td>
349            </tr>
350         </tbody>
351      </table>
352      <p class="title">Upgrading to TLS Within HTTP/1.1</p>
353      <h1><a id="rfc.status" href="#rfc.status">Status of this Memo</a></h1>
354      <p>This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions
355         for improvements. Please refer to the current edition of the “Internet Official Protocol Standards” (STD 1) for the standardization
356         state and status of this protocol. Distribution of this memo is unlimited.
357      </p>
358      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
359      <p>Copyright © The Internet Society (2000). All Rights Reserved.</p>
360      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
361      <p>This memo explains how to use the Upgrade mechanism in HTTP/1.1 to initiate Transport Layer Security (TLS) over an existing
362         TCP connection. This allows unsecured and secured HTTP traffic to share the same well known port (in this case, http: at 80
363         rather than https: at 443). It also enables "virtual hosting", so a single HTTP + TLS server can disambiguate traffic intended
364         for several hostnames at a single IP address.
365      </p> 
366      <p>Since HTTP/1.1 <a href="#RFC2616"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[1]</cite></a> defines Upgrade as a hop-by-hop mechanism, this memo also documents the HTTP CONNECT method for establishing end-to-end tunnels
367         across HTTP proxies. Finally, this memo establishes new IANA registries for public HTTP status codes, as well as public or
368         private Upgrade product tokens.
369      </p> 
370      <p>This memo does NOT affect the current definition of the 'https' URI scheme, which already defines a separate namespace (
371         and are not equivalent).
372      </p>
373      <hr class="noprint">
374      <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
375      <ul class="toc">
376         <li class="tocline0">1.&nbsp;&nbsp;&nbsp;<a href="#rfc.section.1">Motivation</a></li>
377         <li class="tocline0">2.&nbsp;&nbsp;&nbsp;<a href="#rfc.section.2">Introduction</a><ul class="toc">
378               <li class="tocline1">2.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.2.1">Requirements Terminology</a></li>
379            </ul>
380         </li>
381         <li class="tocline0">3.&nbsp;&nbsp;&nbsp;<a href="">Client Requested Upgrade to HTTP over TLS</a><ul class="toc">
382               <li class="tocline1">3.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.3.1">Optional Upgrade</a></li>
383               <li class="tocline1">3.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.3.2">Mandatory Upgrade</a></li>
384               <li class="tocline1">3.3&nbsp;&nbsp;&nbsp;<a href="#rfc.section.3.3">Server Acceptance of Upgrade Request</a></li>
385            </ul>
386         </li>
387         <li class="tocline0">4.&nbsp;&nbsp;&nbsp;<a href="">Server Requested Upgrade to HTTP over TLS</a><ul class="toc">
388               <li class="tocline1">4.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.4.1">Optional Advertisement</a></li>
389               <li class="tocline1">4.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.4.2">Mandatory Advertisement</a></li>
390            </ul>
391         </li>
392         <li class="tocline0">5.&nbsp;&nbsp;&nbsp;<a href="#upgrade.across.proxies">Upgrade across Proxies</a><ul class="toc">
393               <li class="tocline1">5.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.5.1">Implications of Hop By Hop Upgrade</a></li>
394               <li class="tocline1">5.2&nbsp;&nbsp;&nbsp;<a href="#requesting.a.tunnel.with.connect">Requesting a Tunnel with CONNECT</a></li>
395               <li class="tocline1">5.3&nbsp;&nbsp;&nbsp;<a href="#rfc.section.5.3">Establishing a Tunnel with CONNECT</a></li>
396            </ul>
397         </li>
398         <li class="tocline0">6.&nbsp;&nbsp;&nbsp;<a href="#rationale.for.the.use.of.a.4xx.status.code">Rationale for the use of a 4xx (client error) Status Code</a></li>
399         <li class="tocline0">7.&nbsp;&nbsp;&nbsp;<a href="#rfc.section.7">IANA Considerations</a><ul class="toc">
400               <li class="tocline1">7.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.7.1">HTTP Status Code Registry</a></li>
401               <li class="tocline1">7.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.7.2">HTTP Upgrade Token Registry</a></li>
402            </ul>
403         </li>
404         <li class="tocline0">8.&nbsp;&nbsp;&nbsp;<a href="#rfc.section.8">Security Considerations</a><ul class="toc">
405               <li class="tocline1">8.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.8.1">Implications for the https: URI Scheme</a></li>
406               <li class="tocline1">8.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.8.2">Security Considerations for CONNECT</a></li>
407            </ul>
408         </li>
409         <li class="tocline0">9.&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a></li>
410         <li class="tocline0"><a href="#rfc.authors">Authors' Addresses</a></li>
411         <li class="tocline0">A.&nbsp;&nbsp;&nbsp;<a href="#rfc.section.A">Acknowledgments</a></li>
412         <li class="tocline0"><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li>
413      </ul>
414      <hr class="noprint">
415      <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;Motivation
416      </h1>
417      <p id="rfc.section.1.p.1">The historical practice of deploying HTTP over SSL3 <a href="#RFC2818"><cite title="HTTP Over TLS">[3]</cite></a> has distinguished the combination from HTTP alone by a unique URI scheme and the TCP port number. The scheme 'http' meant
418         the HTTP protocol alone on port 80, while 'https' meant the HTTP protocol over SSL on port 443. Parallel well-known port numbers
419         have similarly been requested -- and in some cases, granted -- to distinguish between secured and unsecured use of other application
420         protocols (e.g. snews, ftps). This approach effectively halves the number of available well known ports.
421      </p>
422      <p id="rfc.section.1.p.2">At the Washington DC IETF meeting in December 1997, the Applications Area Directors and the IESG reaffirmed that the practice
423         of issuing parallel "secure" port numbers should be deprecated. The HTTP/1.1 Upgrade mechanism can apply Transport Layer Security <a href="#RFC2246"><cite title="The TLS Protocol Version 1.0">[6]</cite></a> to an open HTTP connection.
424      </p>
425      <p id="rfc.section.1.p.3">In the nearly two years since, there has been broad acceptance of the concept behind this proposal, but little interest in
426         implementing alternatives to port 443 for generic Web browsing. In fact, nothing in this memo affects the current interpretation
427         of https: URIs. However, new application protocols built atop HTTP, such as the Internet Printing Protocol <a href="#RFC2565"><cite title="Internet Printing Protocol/1.0: Encoding and Transport">[7]</cite></a>, call for just such a mechanism in order to move ahead in the IETF standards process.
428      </p>
429      <p id="rfc.section.1.p.4">The Upgrade mechanism also solves the "virtual hosting" problem. Rather than allocating multiple IP addresses to a single
430         host, an HTTP/1.1 server will use the Host: header to disambiguate the intended web service. As HTTP/1.1 usage has grown more
431         prevalent, more ISPs are offering name-based virtual hosting, thus delaying IP address space exhaustion.
432      </p>
433      <p id="rfc.section.1.p.5">TLS (and SSL) have been hobbled by the same limitation as earlier versions of HTTP: the initial handshake does not specify
434         the intended hostname, relying exclusively on the IP address. Using a cleartext HTTP/1.1 Upgrade: preamble to the TLS handshake
435         -- choosing the certificates based on the initial Host: header -- will allow ISPs to provide secure name-based virtual hosting
436         as well.
437      </p>
438      <hr class="noprint">
439      <h1 id="rfc.section.2" class="np"><a href="#rfc.section.2">2.</a>&nbsp;Introduction
440      </h1>
441      <p id="rfc.section.2.p.1">TLS, a.k.a., SSL (Secure Sockets Layer), establishes a private end-to-end connection, optionally including strong mutual authentication,
442         using a variety of cryptosystems. Initially, a handshake phase uses three subprotocols to set up a record layer, authenticate
443         endpoints, set parameters, as well as report errors. Then, there is an ongoing layered record protocol that handles encryption,
444         compression, and reassembly for the remainder of the connection. The latter is intended to be completely transparent. For
445         example, there is no dependency between TLS's record markers and or certificates and HTTP/1.1's chunked encoding or authentication.
446      </p>
447      <p id="rfc.section.2.p.2">Either the client or server can use the HTTP/1.1 <a href="#RFC2616"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[1]</cite></a> Upgrade mechanism (<a href="">Section 14.42</a>) to indicate that a TLS-secured connection is desired or necessary. This memo defines the "TLS/1.0" Upgrade token, and a
448         new HTTP Status Code, "426 Upgrade Required".
449      </p>
450      <p id="rfc.section.2.p.3"> <a href="" title="Client Requested Upgrade to HTTP over TLS">Section&nbsp;3</a> and <a href="" title="Server Requested Upgrade to HTTP over TLS">Section&nbsp;4</a> describe the operation of a directly connected client and server. Intermediate proxies must establish an end-to-end tunnel
451         before applying those operations, as explained in <a href="#upgrade.across.proxies" title="Upgrade across Proxies">Section&nbsp;5</a>.
452      </p>
453      <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;Requirements Terminology
454      </h2>
455      <p id="rfc.section.2.1.p.1">Keywords "MUST", "MUST NOT", "REQUIRED", "SHOULD", "SHOULD NOT" and "MAY" that appear in this document are to be interpreted
456         as described in RFC 2119 <a href="#RFC2119"><cite title="Key words for use in RFCs to Indicate Requirement Levels">[11]</cite></a>.
457      </p>
458      <hr class="noprint">
459      <h1 id="rfc.section.3" class="np"><a href="#rfc.section.3">3.</a>&nbsp;<a id="" href="">Client Requested Upgrade to HTTP over TLS</a></h1>
460      <p id="rfc.section.3.p.1">When the client sends an HTTP/1.1 request with an Upgrade header field containing the token "TLS/1.0", it is requesting the
461         server to complete the current HTTP/1.1 request after switching to TLS/1.0.
462      </p>
463      <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;Optional Upgrade
464      </h2>
465      <p id="rfc.section.3.1.p.1">A client <em class="bcp14">MAY</em> offer to switch to secured operation during any clear HTTP request when an unsecured response would be acceptable:
466      </p>
467      <div id="rfc.figure.u.1"></div><pre class="text2">
468    GET HTTP/1.1
469    Host:
470    Upgrade: TLS/1.0
471    Connection: Upgrade
472</pre><p id="rfc.section.3.1.p.3">In this case, the server <em class="bcp14">MAY</em> respond to the clear HTTP operation normally, OR switch to secured operation (as detailed in the next section).
473      </p>
474      <p id="rfc.section.3.1.p.4">Note that HTTP/1.1 <a href="#RFC2616"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[1]</cite></a> specifies "the upgrade keyword <em class="bcp14">MUST</em> be supplied within a Connection header field (section 14.10) whenever Upgrade is present in an HTTP/1.1 message".
475      </p>
476      <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;Mandatory Upgrade
477      </h2>
478      <p id="rfc.section.3.2.p.1">If an unsecured response would be unacceptable, a client <em class="bcp14">MUST</em> send an OPTIONS request first to complete the switch to TLS/1.0 (if possible).
479      </p>
480      <div id="rfc.figure.u.2"></div><pre class="text2">
481    OPTIONS * HTTP/1.1
482    Host:
483    Upgrade: TLS/1.0
484    Connection: Upgrade
485</pre><h2 id="rfc.section.3.3"><a href="#rfc.section.3.3">3.3</a>&nbsp;Server Acceptance of Upgrade Request
486      </h2>
487      <p id="rfc.section.3.3.p.1">As specified in HTTP/1.1 <a href="#RFC2616"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[1]</cite></a>, if the server is prepared to initiate the TLS handshake, it <em class="bcp14">MUST</em> send the intermediate "101 Switching Protocol" and <em class="bcp14">MUST</em> include an Upgrade response header specifying the tokens of the protocol stack it is switching to:
488      </p>
489      <div id="rfc.figure.u.3"></div><pre class="text">
490    HTTP/1.1 101 Switching Protocols
491    Upgrade: TLS/1.0, HTTP/1.1
492    Connection: Upgrade
493</pre><p id="rfc.section.3.3.p.3">Note that the protocol tokens listed in the Upgrade header of a 101 Switching Protocols response specify an ordered 'bottom-up'
494         stack.
495      </p>
496      <p id="rfc.section.3.3.p.4">As specified in HTTP/1.1 <a href="#RFC2616"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[1]</cite></a>, <a href="">Section 10.1.2</a>: "The server will switch protocols to those defined by the response's Upgrade header field immediately after the empty line
497         which terminates the 101 response".
498      </p>
499      <p id="rfc.section.3.3.p.5">Once the TLS handshake completes successfully, the server <em class="bcp14">MUST</em> continue with the response to the original request. Any TLS handshake failure <em class="bcp14">MUST</em> lead to disconnection, per the TLS error alert specification.
500      </p>
501      <hr class="noprint">
502      <h1 id="rfc.section.4" class="np"><a href="#rfc.section.4">4.</a>&nbsp;<a id="" href="">Server Requested Upgrade to HTTP over TLS</a></h1>
503      <p id="rfc.section.4.p.1">The Upgrade response header field advertises possible protocol upgrades a server <em class="bcp14">MAY</em> accept. In conjunction with the "426 Upgrade Required" status code, a server can advertise the exact protocol upgrade(s) that
504         a client <em class="bcp14">MUST</em> accept to complete the request.
505      </p>
506      <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a>&nbsp;Optional Advertisement
507      </h2>
508      <p id="rfc.section.4.1.p.1">As specified in HTTP/1.1 <a href="#RFC2616"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[1]</cite></a>, the server <em class="bcp14">MAY</em> include an Upgrade header in any response other than 101 or 426 to indicate a willingness to switch to any (combination) of
509         the protocols listed.
510      </p>
511      <h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a>&nbsp;Mandatory Advertisement
512      </h2>
513      <p id="rfc.section.4.2.p.1">A server <em class="bcp14">MAY</em> indicate that a client request can not be completed without TLS using the "426 Upgrade Required" status code, which <em class="bcp14">MUST</em> include an an Upgrade header field specifying the token of the required TLS version.
514      </p>
515      <div id="rfc.figure.u.4"></div><pre class="text2">
516    HTTP/1.1 426 Upgrade Required
517    Upgrade: TLS/1.0, HTTP/1.1
518    Connection: Upgrade
519</pre><p id="rfc.section.4.2.p.3">The server <em class="bcp14">SHOULD</em> include a message body in the 426 response which indicates in human readable form the reason for the error and describes any
520         alternative courses which may be available to the user.
521      </p>
522      <p id="rfc.section.4.2.p.4">Note that even if a client is willing to use TLS, it must use the operations in <a href="" title="Client Requested Upgrade to HTTP over TLS">Section&nbsp;3</a> to proceed; the TLS handshake cannot begin immediately after the 426 response.
523      </p>
524      <hr class="noprint">
525      <h1 id="rfc.section.5" class="np"><a href="#rfc.section.5">5.</a>&nbsp;<a id="upgrade.across.proxies" href="#upgrade.across.proxies">Upgrade across Proxies</a></h1>
526      <p id="rfc.section.5.p.1">As a hop-by-hop header, Upgrade is negotiated between each pair of HTTP counterparties. If a User Agent sends a request with
527         an Upgrade header to a proxy, it is requesting a change to the protocol between itself and the proxy, not an end-to-end change.
528      </p>
529      <p id="rfc.section.5.p.2">Since TLS, in particular, requires end-to-end connectivity to provide authentication and prevent man-in-the-middle attacks,
530         this memo specifies the CONNECT method to establish a tunnel across proxies.
531      </p>
532      <p id="rfc.section.5.p.3">Once a tunnel is established, any of the operations in <a href="" title="Client Requested Upgrade to HTTP over TLS">Section&nbsp;3</a> can be used to establish a TLS connection.
533      </p>
534      <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;Implications of Hop By Hop Upgrade
535      </h2>
536      <p id="rfc.section.5.1.p.1">If an origin server receives an Upgrade header from a proxy and responds with a 101 Switching Protocols response, it is changing
537         the protocol only on the connection between the proxy and itself. Similarly, a proxy might return a 101 response to its client
538         to change the protocol on that connection independently of the protocols it is using to communicate toward the origin server.
539      </p>
540      <p id="rfc.section.5.1.p.2">These scenarios also complicate diagnosis of a 426 response. Since Upgrade is a hop-by-hop header, a proxy that does not recognize
541         426 might remove the accompanying Upgrade header and prevent the client from determining the required protocol switch. If
542         a client receives a 426 status without an accompanying Upgrade header, it will need to request an end to end tunnel connection
543         as described in <a href="#requesting.a.tunnel.with.connect" title="Requesting a Tunnel with CONNECT">Section&nbsp;5.2</a> and repeat the request in order to obtain the required upgrade information.
544      </p>
545      <p id="rfc.section.5.1.p.3">This hop-by-hop definition of Upgrade was a deliberate choice. It allows for incremental deployment on either side of proxies,
546         and for optimized protocols between cascaded proxies without the knowledge of the parties that are not a part of the change.
547      </p>
548      <h2 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a>&nbsp;<a id="requesting.a.tunnel.with.connect" href="#requesting.a.tunnel.with.connect">Requesting a Tunnel with CONNECT</a></h2>
549      <p id="rfc.section.5.2.p.1">A CONNECT method requests that a proxy establish a tunnel connection on its behalf. The Request-URI portion of the Request-Line
550         is always an 'authority' as defined by URI Generic Syntax <a href="#RFC2396"><cite title="Uniform Resource Identifiers (URI): Generic Syntax">[2]</cite></a>, which is to say the host name and port number destination of the requested connection separated by a colon:
551      </p>
552      <div id="rfc.figure.u.5"></div><pre class="text2">
553   CONNECT HTTP/1.1
554   Host:
555</pre><p id="rfc.section.5.2.p.3">Other HTTP mechanisms can be used normally with the CONNECT method -- except end-to-end protocol Upgrade requests, of course,
556         since the tunnel must be established first.
557      </p>
558      <p id="rfc.section.5.2.p.4">For example, proxy authentication might be used to establish the authority to create a tunnel:</p>
559      <div id="rfc.figure.u.6"></div><pre class="text2">
560   CONNECT HTTP/1.1
561   Host:
562   Proxy-Authorization: basic aGVsbG86d29ybGQ=
563</pre><p id="rfc.section.5.2.p.6">Like any other pipelined HTTP/1.1 request, data to be tunneled may be sent immediately after the blank line. The usual caveats
564         also apply: data may be discarded if the eventual response is negative, and the connection may be reset with no response if
565         more than one TCP segment is outstanding.
566      </p>
567      <h2 id="rfc.section.5.3"><a href="#rfc.section.5.3">5.3</a>&nbsp;Establishing a Tunnel with CONNECT
568      </h2>
569      <p id="rfc.section.5.3.p.1">Any successful (2xx) response to a CONNECT request indicates that the proxy has established a connection to the requested
570         host and port, and has switched to tunneling the current connection to that server connection.
571      </p>
572      <p id="rfc.section.5.3.p.2">It may be the case that the proxy itself can only reach the requested origin server through another proxy. In this case, the
573         first proxy <em class="bcp14">SHOULD</em> make a CONNECT request of that next proxy, requesting a tunnel to the authority. A proxy <em class="bcp14">MUST NOT</em> respond with any 2xx status code unless it has either a direct or tunnel connection established to the authority.
574      </p>
575      <p id="rfc.section.5.3.p.3">An origin server which receives a CONNECT request for itself <em class="bcp14">MAY</em> respond with a 2xx status code to indicate that a connection is established.
576      </p>
577      <p id="rfc.section.5.3.p.4">If at any point either one of the peers gets disconnected, any outstanding data that came from that peer will be passed to
578         the other one, and after that also the other connection will be terminated by the proxy. If there is outstanding data to that
579         peer undelivered, that data will be discarded.
580      </p>
581      <hr class="noprint">
582      <h1 id="rfc.section.6" class="np"><a href="#rfc.section.6">6.</a>&nbsp;<a id="rationale.for.the.use.of.a.4xx.status.code" href="#rationale.for.the.use.of.a.4xx.status.code">Rationale for the use of a 4xx (client error) Status Code</a></h1>
583      <p id="rfc.section.6.p.1">Reliable, interoperable negotiation of Upgrade features requires an unambiguous failure signal. The 426 Upgrade Required status
584         code allows a server to definitively state the precise protocol extensions a given resource must be served with.
585      </p>
586      <p id="rfc.section.6.p.2">It might at first appear that the response should have been some form of redirection (a 3xx code), by analogy to an old-style
587         redirection to an https: URI. User agents that do not understand Upgrade: preclude this.
588      </p>
589      <p id="rfc.section.6.p.3">Suppose that a 3xx code had been assigned for "Upgrade Required"; a user agent that did not recognize it would treat it as
590         300. It would then properly look for a "Location" header in the response and attempt to repeat the request at the URL in that
591         header field. Since it did not know to Upgrade to incorporate the TLS layer, it would at best fail again at the new URL.
592      </p>
593      <hr class="noprint">
594      <h1 id="rfc.section.7" class="np"><a href="#rfc.section.7">7.</a>&nbsp;IANA Considerations
595      </h1>
596      <p id="rfc.section.7.p.1">IANA shall create registries for two name spaces, as described in BCP 26 <a href="#RFC2434"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[10]</cite></a>:
597      </p>
598      <ul>
599         <li>HTTP Status Codes</li>
600         <li>HTTP Upgrade Tokens</li>
601      </ul>
602      <h2 id="rfc.section.7.1"><a href="#rfc.section.7.1">7.1</a>&nbsp;HTTP Status Code Registry
603      </h2>
604      <p id="rfc.section.7.1.p.1">The HTTP Status Code Registry defines the name space for the Status-Code token in the Status line of an HTTP response. The
605         initial values for this name space are those specified by:
606      </p>
607      <ol>
608         <li>Draft Standard for HTTP/1.1 <a href="#RFC2616"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[1]</cite></a></li>
609         <li>Web Distributed Authoring and Versioning <a href="#RFC2518"><cite title="HTTP Extensions for Distributed Authoring -- WEBDAV">[4]</cite></a> [defines 420-424]
610         </li>
611         <li>WebDAV Advanced Collections <a href="#ADVCOL"><cite title="WebDAV Advanced Collection Protocol">[5]</cite></a> (Work in Progress) [defines 425]
612         </li>
613         <li><a href="#rationale.for.the.use.of.a.4xx.status.code" title="Rationale for the use of a 4xx (client error) Status Code">Section&nbsp;6</a> [defines 426]
614         </li>
615      </ol>
616      <p id="rfc.section.7.1.p.2">Values to be added to this name space <em class="bcp14">SHOULD</em> be subject to review in the form of a standards track document within the IETF Applications Area. Any such document <em class="bcp14">SHOULD</em> be traceable through statuses of either 'Obsoletes' or 'Updates' to the Draft Standard for HTTP/1.1 <a href="#RFC2616"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[1]</cite></a>.
617      </p>
618      <h2 id="rfc.section.7.2"><a href="#rfc.section.7.2">7.2</a>&nbsp;HTTP Upgrade Token Registry
619      </h2>
620      <p id="rfc.section.7.2.p.1">The HTTP Upgrade Token Registry defines the name space for product tokens used to identify protocols in the Upgrade HTTP header
621         field. Each registered token should be associated with one or a set of specifications, and with contact information.
622      </p>
623      <p id="rfc.section.7.2.p.2">The Draft Standard for HTTP/1.1 <a href="#RFC2616"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[1]</cite></a> specifies that these tokens obey the production for 'product':
624      </p>
625      <div id="rfc.figure.u.7"></div><pre class="inline">
626   product         = token ["/" product-version]
627   product-version = token
628</pre><p id="rfc.section.7.2.p.4">Registrations should be allowed on a First Come First Served basis as described in BCP 26 <a href="#RFC2434"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[10]</cite></a>. These specifications need not be IETF documents or be subject to IESG review, but should obey the following rules:
629      </p>
630      <ol>
631         <li>A token, once registered, stays registered forever.</li>
632         <li>The registration <em class="bcp14">MUST</em> name a responsible party for the registration.
633         </li>
634         <li>The registration <em class="bcp14">MUST</em> name a point of contact.
635         </li>
636         <li>The registration <em class="bcp14">MAY</em> name the documentation required for the token.
637         </li>
638         <li>The responsible party <em class="bcp14">MAY</em> change the registration at any time. The IANA will keep a record of all such changes, and make them available upon request.
639         </li>
640         <li>The responsible party for the first registration of a "product" token <em class="bcp14">MUST</em> approve later registrations of a "version" token together with that "product" token before they can be registered.
641         </li>
642         <li>If absolutely required, the IESG <em class="bcp14">MAY</em> reassign the responsibility for a token. This will normally only be used in the case when a responsible party cannot be contacted.
643         </li>
644      </ol>
645      <p id="rfc.section.7.2.p.5">This specification defines the protocol token "TLS/1.0" as the identifier for the protocol specified by The TLS Protocol <a href="#RFC2246"><cite title="The TLS Protocol Version 1.0">[6]</cite></a>.
646      </p>
647      <p id="rfc.section.7.2.p.6">It is NOT required that specifications for upgrade tokens be made publicly available, but the contact information for the
648         registration <em class="bcp14">SHOULD</em> be.
649      </p>
650      <hr class="noprint">
651      <h1 id="rfc.section.8" class="np"><a href="#rfc.section.8">8.</a>&nbsp;Security Considerations
652      </h1>
653      <p id="rfc.section.8.p.1">The potential for a man-in-the-middle attack (deleting the Upgrade header) remains the same as current, mixed http/https practice: </p>
654      <ul>
655         <li>Removing the Upgrade header is similar to rewriting web pages to change https:// links to http:// links.</li>
656         <li>The risk is only present if the server is willing to vend such information over both a secure and an insecure channel in the
657            first place.
658         </li>
659         <li>If the client knows for a fact that a server is TLS-compliant, it can insist on it by only sending an Upgrade request with
660            a no-op method like OPTIONS.
661         </li>
662         <li>Finally, as the https: specification warns, "users should carefully examine the certificate presented by the server to determine
663            if it meets their expectations".
664         </li>
665      </ul>
666      <p id="rfc.section.8.p.2">Furthermore, for clients that do not explicitly try to invoke TLS, servers can use the Upgrade header in any response other
667         than 101 or 426 to advertise TLS compliance. Since TLS compliance should be considered a feature of the server and not the
668         resource at hand, it should be sufficient to send it once, and let clients cache that fact.
669      </p>
670      <h2 id="rfc.section.8.1"><a href="#rfc.section.8.1">8.1</a>&nbsp;Implications for the https: URI Scheme
671      </h2>
672      <p id="rfc.section.8.1.p.1">While nothing in this memo affects the definition of the 'https' URI scheme, widespread adoption of this mechanism for HyperText
673         content could use 'http' to identify both secure and non-secure resources.
674      </p>
675      <p id="rfc.section.8.1.p.2">The choice of what security characteristics are required on the connection is left to the client and server. This allows either
676         party to use any information available in making this determination. For example, user agents may rely on user preference
677         settings or information about the security of the network such as 'TLS required on all POST operations not on my local net',
678         or servers may apply resource access rules such as 'the FORM on this page must be served and submitted using TLS'.
679      </p>
680      <h2 id="rfc.section.8.2"><a href="#rfc.section.8.2">8.2</a>&nbsp;Security Considerations for CONNECT
681      </h2>
682      <p id="rfc.section.8.2.p.1">A generic TCP tunnel is fraught with security risks. First, such authorization should be limited to a small number of known
683         ports. The Upgrade: mechanism defined here only requires onward tunneling at port 80. Second, since tunneled data is opaque
684         to the proxy, there are additional risks to tunneling to other well-known or reserved ports. A putative HTTP client CONNECTing
685         to port 25 could relay spam via SMTP, for example.
686      </p>
687      <h1 class="np" id="rfc.references"><a href="#rfc.section.9" id="rfc.section.9">9.</a> References
688      </h1>
689      <table>
690         <tr>
691            <td class="reference"><b id="RFC2616">[1]</b></td>
692            <td class="top"><a href="" title="University of California, Irvine">Fielding, R.</a>, <a href="" title="W3C">Gettys, J.</a>, <a href="" title="Compaq Computer Corporation">Mogul, J.</a>, <a href="" title="MIT Laboratory for Computer Science">Frystyk, H.</a>, <a href="" title="Xerox Corporation">Masinter, L.</a>, <a href="" title="Microsoft Corporation">Leach, P.</a>, and <a href="" title="W3C">T. Berners-Lee</a>, “<a href="">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2616, June&nbsp;1999.
693            </td>
694         </tr> 
695         <tr>
696            <td class="reference"><b id="RFC2396">[2]</b></td>
697            <td class="top"><a href="" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="" title="University of California, Irvine">Fielding, R.</a>, and <a href="" title="Xerox PARC">L. Masinter</a>, “<a href="">Uniform Resource Identifiers (URI): Generic Syntax</a>”, RFC&nbsp;2396, August&nbsp;1998.
698            </td>
699         </tr> 
700         <tr>
701            <td class="reference"><b id="RFC2818">[3]</b></td>
702            <td class="top"><a href="" title="RTFM, Inc.">Rescorla, E.</a>, “<a href="">HTTP Over TLS</a>”, RFC&nbsp;2818, May&nbsp;2000.
703            </td>
704         </tr> 
705         <tr>
706            <td class="reference"><b id="RFC2518">[4]</b></td>
707            <td class="top"><a href="" title="Microsoft Corporation">Goland, Y.</a>, <a href="" title="Dept. Of Information and Computer Science, University of California, Irvine">Whitehead, E.</a>, <a href="" title="Netscape">Faizi, A.</a>, <a href="" title="Novell">Carter, S.</a>, and <a href="" title="Novell">D. Jensen</a>, “<a href="">HTTP Extensions for Distributed Authoring -- WEBDAV</a>”, RFC&nbsp;2518, February&nbsp;1999.
708            </td>
709         </tr> 
710         <tr>
711            <td class="reference"><b id="ADVCOL">[5]</b></td>
712            <td class="top">Slein, J. and E. Whitehead, “WebDAV Advanced Collection Protocol”.<br>Work In Progress.
713            </td>
714         </tr> 
715         <tr>
716            <td class="reference"><b id="RFC2246">[6]</b></td>
717            <td class="top"><a href="" title="Certicom">Dierks, T.</a> and <a href="" title="Certicom">C. Allen</a>, “<a href="">The TLS Protocol Version 1.0</a>”, RFC&nbsp;2246, January&nbsp;1999.
718            </td>
719         </tr> 
720         <tr>
721            <td class="reference"><b id="RFC2565">[7]</b></td>
722            <td class="top"><a href="" title="Xerox Corporation">Herriot, R.</a>, <a href="" title="Hewlett-Packard">Butler, S.</a>, <a href="" title="Microsoft">Moore, P.</a>, and <a href="" title="Sharp Laboratories">R. Turner</a>, “<a href="">Internet Printing Protocol/1.0: Encoding and Transport</a>”, RFC&nbsp;2565, April&nbsp;1999.
723            </td>
724         </tr> 
725         <tr>
726            <td class="reference"><b id="Luo97">[8]</b></td>
727            <td class="top">Luotonen, A., “Tunneling TCP based protocols through Web proxy servers”.<br>Work In Progress. (Also available in: Luotonen, Ari. Web Proxy Servers, Prentice-Hall, 1997 ISBN:0136806120.)
728            </td>
729         </tr> 
730         <tr>
731            <td class="reference"><b id="RFC2629">[9]</b></td>
732            <td class="top"><a href="" title="Invisible Worlds, Inc.">Rose, M.</a>, “<a href="">Writing I-Ds and RFCs using XML</a>”, RFC&nbsp;2629, June&nbsp;1999.
733            </td>
734         </tr> 
735         <tr>
736            <td class="reference"><b id="RFC2434">[10]</b></td>
737            <td class="top"><a href="" title="IBM Corporation">Narten, T.</a> and <a href="" title="Maxware">H. Alvestrand</a>, “<a href="">Guidelines for Writing an IANA Considerations Section in RFCs</a>”, BCP&nbsp;26, RFC&nbsp;2434, October&nbsp;1998.
738            </td>
739         </tr> 
740         <tr>
741            <td class="reference"><b id="RFC2119">[11]</b></td>
742            <td class="top"><a href="" title="Harvard University">Bradner, S.</a>, “<a href="">Key words for use in RFCs to Indicate Requirement Levels</a>”, BCP&nbsp;14, RFC&nbsp;2119, March&nbsp;1997.
743            </td>
744         </tr>
745      </table>
746      <hr class="noprint">
747      <div class="avoidbreak">
748         <h1 id="rfc.authors" class="np"><a href="#rfc.authors">Authors' Addresses</a></h1>
749         <address class="vcard"><span class="vcardline"><span class="fn">Rohit Khare</span><span class="n hidden"><span class="family-name">Khare</span><span class="given-name">Rohit</span></span></span><span class="org vcardline">4K Associates / UC Irvine</span><span class="vcardline">EMail: <a href=""><span class="email"></span></a></span></address>
750         <address class="vcard"><span class="vcardline"><span class="fn">Scott Lawrence</span><span class="n hidden"><span class="family-name">Lawrence</span><span class="given-name">Scott</span></span></span><span class="org vcardline">Agranat Systems, Inc.</span><span class="vcardline">EMail: <a href=""><span class="email"></span></a></span></address>
751      </div>
752      <hr class="noprint">
753      <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;Acknowledgments
754      </h1>
755      <p id="rfc.section.A.p.1">The CONNECT method was originally described in a Work in Progress titled, "Tunneling TCP based protocols through Web proxy
756         servers", <a href="#Luo97"><cite title="Tunneling TCP based protocols through Web proxy servers">[8]</cite></a> by Ari Luotonen of Netscape Communications Corporation. It was widely implemented by HTTP proxies, but was never made a part
757         of any IETF Standards Track document. The method name CONNECT was reserved, but not defined in <a href="#RFC2616"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[1]</cite></a>.
758      </p>
759      <p id="rfc.section.A.p.2">The definition provided here is derived directly from that earlier memo, with some editorial changes and conformance to the
760         stylistic conventions since established in other HTTP specifications.
761      </p>
762      <p id="rfc.section.A.p.3">Additional Thanks to: </p>
763      <ul>
764         <li>Paul Hoffman for his work on the STARTTLS command extension for ESMTP.</li>
765         <li>Roy Fielding for assistance with the rationale behind Upgrade: and its interaction with OPTIONS.</li>
766         <li>Eric Rescorla for his work on standardizing the existing https: practice to compare with.</li>
767         <li>Marshall Rose, for the xml2rfc document type description and tools <a href="#RFC2629"><cite title="Writing I-Ds and RFCs using XML">[9]</cite></a>.
768         </li>
769         <li>Jim Whitehead, for sorting out the current range of available HTTP status codes.</li>
770         <li>Henrik Frystyk Nielsen, whose work on the Mandatory extension mechanism pointed out a hop-by-hop Upgrade still requires tunneling.</li>
771         <li>Harald Alvestrand for improvements to the token registration rules.</li>
772      </ul>
773      <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
774      <p>Copyright © The Internet Society (2000). All Rights Reserved.</p>
775      <p>This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise
776         explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without
777         restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative
778         works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references
779         to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards
780         in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to
781         translate it into languages other than English.
782      </p>
783      <p>The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.</p>
784      <p>This document and the information contained herein is provided on an “AS IS” basis and THE INTERNET SOCIETY AND THE INTERNET
787         PURPOSE.
788      </p>
789      <hr class="noprint">
790      <h1 class="np"><a id="rfc.ipr" href="#rfc.ipr">Intellectual Property</a></h1>
791      <p>The IETF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed
792         to pertain to the implementation or use of the technology described in this document or the extent to which any license under
793         such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights.
794         Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be
795         found in BCP-11. Copies of claims of rights made available for publication and any assurances of licenses to be made available,
796         or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementors
797         or users of this specification can be obtained from the IETF Secretariat.
798      </p>
799      <p>The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary
800         rights which may cover technology that may be required to practice this standard. Please address the information to the IETF
801         Executive Director.
802      </p>
803      <h1>Acknowledgment</h1>
804      <p>Funding for the RFC Editor function is currently provided by the Internet Society.</p>
805   </body>
Note: See TracBrowser for help on using the repository browser.