source: draft-ietf-httpbis/orig/rfc2145.html @ 311

Last change on this file since 311 was 311, checked in by julian.reschke@…, 11 years ago

Update orig RFCs, also add 2145 and 5234

  • Property svn:eol-style set to native
File size: 28.7 KB
2<!DOCTYPE html
3  PUBLIC "-//W3C//DTD HTML 4.01//EN">
4<html lang="en"><head profile="">
5      <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
6   <title>Use and Interpretation of HTTP Version Numbers</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;
24blockquote {
25  border-style: solid;
26  border-color: gray;
27  border-width: 0 0 0 .25em;
28  font-style: italic;
29  padding-left: 0.5em;
31body {
32  color: black;
33  font-family: verdana, helvetica, arial, sans-serif;
34  font-size: 10pt;
36cite {
37  font-style: normal;
39div.note {
40  margin-left: 2em;
42dd {
43  margin-right: 2em;
45dl {
46  margin-left: 2em;
49dl.empty dd {
50  margin-top: .5em;
52dl p {
53  margin-left: 0em;
55dt {
56  margin-top: .5em;
58h1 {
59  font-size: 14pt;
60  line-height: 21pt;
61  page-break-after: avoid;
62} {
64  page-break-before: always;
66h1 a {
67  color: #333333;
69h2 {
70  font-size: 12pt;
71  line-height: 15pt;
72  page-break-after: avoid;
74h2 a {
75  color: black;
77h3 {
78  font-size: 10pt;
79  page-break-after: avoid;
81h3 a {
82  color: black;
84h4 {
85  font-size: 10pt;
86  page-break-after: avoid;
88h4 a {
89  color: black;
91h5 {
92  font-size: 10pt;
93  page-break-after: avoid;
95h5 a {
96  color: black;
98img {
99  margin-left: 3em;
101li {
102  margin-left: 2em;
103  margin-right: 2em;
105ol {
106  margin-left: 2em;
107  margin-right: 2em;
109ol p {
110  margin-left: 0em;
112p {
113  margin-left: 2em;
114  margin-right: 2em;
116pre {
117  margin-left: 3em;
118  background-color: lightyellow;
119  padding: .25em;
121pre.text2 {
122  border-style: dotted;
123  border-width: 1px;
124  background-color: #f0f0f0;
125  width: 69em;
127pre.inline {
128  background-color: white;
129  padding: 0em;
131pre.text {
132  border-style: dotted;
133  border-width: 1px;
134  background-color: #f8f8f8;
135  width: 69em;
137pre.drawing {
138  border-style: solid;
139  border-width: 1px;
140  background-color: #f8f8f8;
141  padding: 2em;
143table {
144  margin-left: 2em;
146table.header {
147  width: 95%;
148  font-size: 10pt;
149  color: white;
150} {
152  vertical-align: top;
154td.topnowrap {
155  vertical-align: top;
156  white-space: nowrap; 
158td.header {
159  background-color: gray;
160  width: 50%;
162td.reference {
163  vertical-align: top;
164  white-space: nowrap;
165  padding-right: 1em;
167thead {
168  display:table-header-group;
170ul.toc {
171  list-style: none;
172  margin-left: 1.5em;
173  margin-right: 0em;
174  padding-left: 0em;
176li.tocline0 {
177  line-height: 150%;
178  font-weight: bold;
179  font-size: 10pt;
180  margin-left: 0em;
181  margin-right: 0em;
183li.tocline1 {
184  line-height: normal;
185  font-weight: normal;
186  font-size: 9pt;
187  margin-left: 0em;
188  margin-right: 0em;
190li.tocline2 {
191  font-size: 0pt;
193ul p {
194  margin-left: 0em;
196ul.ind {
197  list-style: none;
198  margin-left: 1.5em;
199  margin-right: 0em;
200  padding-left: 0em;
202li.indline0 {
203  font-weight: bold;
204  line-height: 200%;
205  margin-left: 0em;
206  margin-right: 0em;
208li.indline1 {
209  font-weight: normal;
210  line-height: 150%;
211  margin-left: 0em;
212  margin-right: 0em;
214.bcp14 {
215  font-style: normal;
216  text-transform: lowercase;
217  font-variant: small-caps;
219blockquote > * .bcp14 {
220  font-style: italic;
222.comment {
223  background-color: yellow;
224} {
226  text-align: center;
228.error {
229  color: red;
230  font-style: italic;
231  font-weight: bold;
233.figure {
234  font-weight: bold;
235  text-align: center;
236  font-size: 9pt;
238.filename {
239  color: #333333;
240  font-weight: bold;
241  font-size: 12pt;
242  line-height: 21pt;
243  text-align: center;
245.fn {
246  font-weight: bold;
248.hidden {
249  display: none;
251.left {
252  text-align: left;
254.right {
255  text-align: right;
257.title {
258  color: #990000;
259  font-size: 18pt;
260  line-height: 18pt;
261  font-weight: bold;
262  text-align: center;
263  margin-top: 36pt;
265.vcardline {
266  display: block;
268.warning {
269  font-size: 14pt;
270  background-color: yellow;
274@media print {
275  .noprint {
276    display: none;
277  }
279  a {
280    color: black;
281    text-decoration: none;
282  }
284  table.header {
285    width: 90%;
286  }
288  td.header {
289    width: 50%;
290    color: black;
291    background-color: white;
292    vertical-align: top;
293    font-size: 12pt;
294  }
296  ul.toc a::after {
297    content: leader('.') target-counter(attr(href), page);
298  }
300  a.iref {
301    content: target-counter(attr(href), page);
302  }
304  .print2col {
305    column-count: 2;
306    -moz-column-count: 2;
307    column-fill: auto;
308  }
311@page {
312  @top-left {
313       content: "RFC 2145"; 
314  } 
315  @top-right {
316       content: "May 1997"; 
317  } 
318  @top-center {
319       content: "HTTP Version Numbers"; 
320  } 
321  @bottom-left {
322       content: "Mogul, et al."; 
323  } 
324  @bottom-center {
325       content: "Informational"; 
326  } 
327  @bottom-right {
328       content: "[Page " counter(page) "]"; 
329  } 
332@page:first { 
333    @top-left {
334      content: normal;
335    }
336    @top-right {
337      content: normal;
338    }
339    @top-center {
340      content: normal;
341    }
343</style><link rel="Contents" href="#rfc.toc"><link rel="Author" href="#rfc.authors"><link rel="Copyright" href="#rfc.copyright"><link rel="Chapter" title="1 Introduction" href="#rfc.section.1"><link rel="Chapter" title="2 HTTP version numbers" href="#rfc.section.2"><link rel="Chapter" title="3 Security Considerations" href="#rfc.section.3"><link rel="Chapter" href="#rfc.section.4" title="4 References"><link rel="Alternate" title="Authorative ASCII version" href=""><meta name="generator" content=", Revision 1.389, 2008-08-20 14:21:35, XSLT vendor: SAXON 6.5.5 from Michael Kay"><meta name="keywords" content="HTTP, hypertext transfer protocol"><link rel="schema.DC" href=""><meta name="DC.Creator" content="Mogul, J. C."><meta name="DC.Creator" content="Fielding, R. T."><meta name="DC.Creator" content="Gettys, J."><meta name="DC.Creator" content="Frystyk, H."><meta name="DC.Identifier" content="urn:ietf:rfc:2145"><meta name="DC.Date.Issued" scheme="ISO8601" content="1997-05"><meta name="DC.Description.Abstract" content="HTTP request and response messages include an HTTP protocol version number. Some confusion exists concerning the proper use and interpretation of HTTP version numbers, and concerning interoperability of HTTP implementations of different protocol versions. This document is an attempt to clarify the situation. It is not a modification of the intended meaning of the existing HTTP/1.0 and HTTP/1.1 documents, but it does describe the intention of the authors of those documents, and can be considered definitive when there is any ambiguity in those documents concerning HTTP version numbers, for all versions of HTTP."></head><body><table summary="header information" class="header" border="0" cellpadding="1" cellspacing="1"><tr><td class="header left">Network Working Group</td><td class="header right">J. C. Mogul</td></tr><tr><td class="header left">Request for Comments: 2145</td><td class="header right">DEC</td></tr><tr><td class="header left">Category: Informational</td><td class="header right">R. T. Fielding</td></tr><tr><td class="header left"></td><td class="header right">UC Irvine</td></tr><tr><td class="header left"></td><td class="header right">J. Gettys</td></tr><tr><td class="header left"></td><td class="header right">DEC</td></tr><tr><td class="header left"></td><td class="header right">H. Frystyk</td></tr><tr><td class="header left"></td><td class="header right">MIT/LCS</td></tr><tr><td class="header left"></td><td class="header right">May 1997</td></tr></table><p class="title">Use and Interpretation of HTTP Version Numbers</p><h1><a id="rfc.status" href="#rfc.status">Status of this Memo</a></h1><p>This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.</p><h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1><p>Copyright &copy; The Internet Society (1997). All Rights Reserved.</p><h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> <p>HTTP request and response messages include an HTTP protocol version number. Some confusion exists concerning the proper use and interpretation of HTTP version numbers, and concerning interoperability of HTTP implementations of different protocol versions. This document is an attempt to clarify the situation. It is not a modification of the intended meaning of the existing HTTP/1.0 and HTTP/1.1 documents, but it does describe the intention of the authors of those documents, and can be considered definitive when there is any ambiguity in those documents concerning HTTP version numbers, for all versions of HTTP.</p> <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note</a></h1> <p>Distribution of this document is unlimited. Please send comments to the HTTP working group at &lt;;. Discussions of the working group are archived at &lt;URL:;. General discussions about HTTP and the applications which use HTTP should take place on the &lt;; mailing list.</p> <hr class="noprint"><h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1><ul class="toc"><li class="tocline0">1.&nbsp;&nbsp;&nbsp;<a href="#rfc.section.1">Introduction</a><ul class="toc"><li class="tocline1">1.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.1.1">Robustness Principle</a></li></ul></li><li class="tocline0">2.&nbsp;&nbsp;&nbsp;<a href="#rfc.section.2">HTTP version numbers</a><ul class="toc"><li class="tocline1">2.1&nbsp;&nbsp;&nbsp;<a href="#proxy.behavior">Proxy behavior</a></li><li class="tocline1">2.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.2.2">Compatibility between minor versions of the same major version</a></li><li class="tocline1">2.3&nbsp;&nbsp;&nbsp;<a href="#rfc.section.2.3">Which version number to send in a message</a></li></ul></li><li class="tocline0">3.&nbsp;&nbsp;&nbsp;<a href="#rfc.section.3">Security Considerations</a></li><li class="tocline0">4.&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a></li><li class="tocline0">5.&nbsp;&nbsp;&nbsp;<a href="#rfc.authors">Authors' Addresses</a></li><li class="tocline0"><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li></ul><hr class="noprint"><h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;Introduction</h1><p id="rfc.section.1.p.1">HTTP request and response messages include an HTTP protocol version number. According to section <a href="">3.1</a> of the HTTP/1.1 specification <a href="#RFC2068"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[2]</cite></a>,</p><blockquote id="rfc.section.1.p.2" cite=""> <p>HTTP uses a "&lt;major&gt;.&lt;minor&gt;" numbering scheme to indicate versions of the protocol. The protocol versioning policy is intended to allow the sender to indicate the format of a message and its capacity for understanding further HTTP communication, rather than the features obtained via that communication. No change is made to the version number for the addition of message components which do not affect communication behavior or which only add to extensible field values. The &lt;minor&gt; number is incremented when the changes made to the protocol add features which do not change the general message parsing algorithm, but which may add to the message semantics and imply additional capabilities of the sender. The &lt;major&gt; number is incremented when the format of a message within the protocol is changed.</p> </blockquote><p id="rfc.section.1.p.3">The same language appears in the description of HTTP/1.0 <a href="#RFC1945"><cite title="Hypertext Transfer Protocol -- HTTP/1.0">[1]</cite></a>.</p><p id="rfc.section.1.p.4">Many readers of these documents have expressed some confusion about the intended meaning of this policy. Also, some people who wrote HTTP implementations before RFC1945 <a href="#RFC1945"><cite title="Hypertext Transfer Protocol -- HTTP/1.0">[1]</cite></a> was issued were not aware of the intentions behind the introduction of version numbers in HTTP/1.0. This has led to debate and inconsistency regarding the use and interpretation of HTTP version numbers, and has led to interoperability problems in certain cases.</p><p id="rfc.section.1.p.5">This document is an attempt to clarify the situation. It is not a modification of the intended meaning of the existing HTTP/1.0 and HTTP/1.1 documents, but it does describe the intention of the authors of those documents. In any case where either of those two documents is ambiguous regarding the use and interpretation of HTTP version numbers, this document should be considered the definitive as to the intentions of the designers of HTTP.</p><p id="rfc.section.1.p.6">The specification described in this document is not part of the specification of any individual version of HTTP, such as HTTP/1.0 or HTTP/1.1. Rather, this document describes the use of HTTP version numbers in any version of HTTP (except for HTTP/0.9, which did not include version numbers).</p><p id="rfc.section.1.p.7">No vendor or other provider of an HTTP implementation should claim any compliance with any IETF HTTP specification unless the implementation conditionally complies with the rules in this document.</p><h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;Robustness Principle</h2><p id="rfc.section.1.1.p.1">RFC791 <a href="#RFC0791"><cite title="Internet Protocol">[4]</cite></a> defines the "robustness principle" in section <a href="">3.2</a>:</p><blockquote id="rfc.section.1.1.p.2" cite=""> <p>an implementation must be conservative in its sending behavior, and liberal in its receiving behavior.</p> </blockquote><p id="rfc.section.1.1.p.3">This principle applies to HTTP, as well. It is the fundamental basis for interpreting any part of the HTTP specification that might still be ambiguous. In particular, implementations of HTTP <em class="bcp14">SHOULD NOT</em> reject messages or generate errors unnecessarily.</p><hr class="noprint"><h1 id="rfc.section.2" class="np"><a href="#rfc.section.2">2.</a>&nbsp;HTTP version numbers</h1><p id="rfc.section.2.p.1">We start by restating the language quoted above from section <a href="">3.1</a> of the HTTP/1.1 specification <a href="#RFC2068"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[2]</cite></a>: </p><dl class="empty"><dd>It is, and has always been, the explicit intent of the HTTP specification that the interpretation of an HTTP message header does not change between minor versions of the same major version.</dd><dd>It is, and has always been, the explicit intent of the HTTP specification that an implementation receiving a message header that it does not understand <em class="bcp14">MUST</em> ignore that header. (The word "ignore" has a special meaning for proxies; see section <a href="#proxy.behavior" title="Proxy behavior">2.1</a> below.)</dd></dl><p id="rfc.section.2.p.2">To make this as clear as possible: The major version sent in a message <em class="bcp14">MAY</em> indicate the interpretation of other header fields. The minor version sent in a message <em class="bcp14">MUST NOT</em> indicate the interpretation of other header fields. This reflects the principle that the minor version labels the capability of the sender, not the interpretation of the message.</p><div class="note"> <p>Note: In a future version of HTTP, we may introduce a mechanism that explicitly requires a receiving implementation to reject a message if it does not understand certain headers. For example, this might be implemented by means of a header that lists a set of other message headers that must be understood by the recipient. Any implementation claiming at least conditional compliance with this future version of HTTP would have to implement this mechanism. However, no implementation claiming compliance with a lower HTTP version (in particular, HTTP/1.1) will have to implement this mechanism.</p>  <p>This future change may be required to support the Protocol Extension Protocol (PEP) <a href="#Kha"><cite title="HTTP/1.2 Extension Protocol (PEP)">[3]</cite></a>.</p> </div><p id="rfc.section.2.p.4">One consequence of these rules is that an HTTP/1.1 message sent to an HTTP/1.0 recipient (or a recipient whose version is unknown) <em class="bcp14">MUST</em> be constructed so that it remains a valid HTTP/1.0 message when all headers not defined in the HTTP/1.0 specification <a href="#RFC1945"><cite title="Hypertext Transfer Protocol -- HTTP/1.0">[1]</cite></a> are removed.</p><h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<a id="proxy.behavior" href="#proxy.behavior">Proxy behavior</a></h2><p id="rfc.section.2.1.p.1">A proxy <em class="bcp14">MUST</em> forward an unknown header, unless it is protected by a Connection header. A proxy implementing an HTTP version &gt;= 1.1 <em class="bcp14">MUST NOT</em> forward unknown headers that are protected by a Connection header, as described in section <a href="">14.10</a> of the HTTP/1.1 specification <a href="#RFC2068"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[2]</cite></a>.</p><p id="rfc.section.2.1.p.2">We remind the reader that that HTTP version numbers are hop-by-hop components of HTTP messages, and are not end-to-end. That is, an HTTP proxy never "forwards" an HTTP version number in either a request or response.</p><h2 id="rfc.section.2.2"><a href="#rfc.section.2.2">2.2</a>&nbsp;Compatibility between minor versions of the same major version</h2><p id="rfc.section.2.2.p.1">An implementation of HTTP/x.b sending a message to a recipient whose version is known to be HTTP/x.a, a &lt; b, <em class="bcp14">MAY</em> send a header that is not defined in the specification for HTTP/x.a. For example, an HTTP/1.1 server may send a "Cache-control" header to an HTTP/1.0 client; this may be useful if the immediate recipient is an HTTP/1.0 proxy, but the ultimate recipient is an HTTP/1.1 client.</p><p id="rfc.section.2.2.p.2">An implementation of HTTP/x.b sending a message to a recipient whose version is known to be HTTP/x.a, a &lt; b, <em class="bcp14">MUST NOT</em> depend on the recipient understanding a header not defined in the specification for HTTP/x.a. For example, HTTP/1.0 clients cannot be expected to understand chunked encodings, and so an HTTP/1.1 server must never send "Transfer-Encoding: chunked" in response to an HTTP/1.0 request.</p><h2 id="rfc.section.2.3"><a href="#rfc.section.2.3">2.3</a>&nbsp;Which version number to send in a message</h2><p id="rfc.section.2.3.p.1">The most strenuous debate over the use of HTTP version numbers has centered on the problem of implementations that do not follow the robustness principle, and which fail to produce useful results when they receive a message with an HTTP minor version higher than the minor version they implement. We consider these implementations buggy, but we recognize that the robustness principle also implies that message senders should make concessions to buggy implementations when this is truly necessary for interoperation.</p><p id="rfc.section.2.3.p.2">An HTTP client <em class="bcp14">SHOULD</em> send a request version equal to the highest version for which the client is at least conditionally compliant, and whose major version is no higher than the highest version supported by the server, if this is known. An HTTP client <em class="bcp14">MUST NOT</em> send a version for which it is not at least conditionally compliant.</p><p id="rfc.section.2.3.p.3">An HTTP client <em class="bcp14">MAY</em> send a lower request version, if it is known that the server incorrectly implements the HTTP specification, but only after the client has determined that the server is actually buggy.</p><p id="rfc.section.2.3.p.4">An HTTP server <em class="bcp14">SHOULD</em> send a response version equal to the highest version for which the server is at least conditionally compliant, and whose major version is less than or equal to the one received in the request. An HTTP server <em class="bcp14">MUST NOT</em> send a version for which it is not at least conditionally compliant. A server <em class="bcp14">MAY</em> send a 505 (HTTP Version Not Supported) response if cannot send a response using the major version used in the client's request.</p><p id="rfc.section.2.3.p.5">An HTTP server <em class="bcp14">MAY</em> send a lower response version, if it is known or suspected that the client incorrectly implements the HTTP specification, but this should not be the default, and this <em class="bcp14">SHOULD</em> NOT be done if the request version is HTTP/1.1 or greater.</p><hr class="noprint"><h1 id="rfc.section.3" class="np"><a href="#rfc.section.3">3.</a>&nbsp;Security Considerations</h1><p id="rfc.section.3.p.1">None, except to the extent that security mechanisms introduced in one version of HTTP might depend on the proper interpretation of HTTP version numbers in older implementations.</p><h1 class="np" id="rfc.references"><a href="#rfc.section.4" id="rfc.section.4">4.</a> References</h1><table summary="References"> <tr><td class="reference"><b id="RFC1945">[1]</b></td><td class="top"><a href="" title="MIT, Laboratory for Computer Science">Berners-Lee, T.</a>, <a href="" title="University of California, Irvine, Department of Information and Computer Science">Fielding, R.T.</a>, and <a href="" title="W3 Consortium, MIT Laboratory for Computer Science">H.F. Nielsen</a>, &#8220;<a href="">Hypertext Transfer Protocol -- HTTP/1.0</a>&#8221;, RFC&nbsp;1945, May&nbsp;1996.</td></tr>  <tr><td class="reference"><b id="RFC2068">[2]</b></td><td class="top"><a href="" title="University of California, Irvine, Department of Information and Computer Science">Fielding, R.</a>, <a href="" title="MIT Laboratory for Computer Science">Gettys, J.</a>, <a href="" title="Digital Equipment Corporation, Western Research Laboratory">Mogul, J.</a>, <a href="" title="MIT Laboratory for Computer Science">Nielsen, H.</a>, and <a href="" title="MIT Laboratory for Computer Science">T. Berners-Lee</a>, &#8220;<a href="">Hypertext Transfer Protocol -- HTTP/1.1</a>&#8221;, RFC&nbsp;2068, January&nbsp;1997.</td></tr>  <tr><td class="reference"><b id="Kha">[3]</b></td><td class="top">Khare, R., &#8220;HTTP/1.2 Extension Protocol (PEP)&#8221;.<br>HTTP Working Group, Work in Progress.</td></tr>  <tr><td class="reference"><b id="RFC0791">[4]</b></td><td class="top">Postel, J., &#8220;<a href="">Internet Protocol</a>&#8221;, RFC&nbsp;791, September&nbsp;1981.</td></tr> </table><hr class="noprint"><h1 id="rfc.authors" class="np"><a href="#rfc.section.5" id="rfc.section.5">5.</a> <a href="#rfc.authors">Authors' Addresses</a></h1><address class="vcard"><span class="vcardline"><span class="fn">Jeffrey C. Mogul</span><span class="n hidden"><span class="family-name">Mogul</span><span class="given-name">Jeffrey C.</span></span></span><span class="org vcardline">Western Research Laboratory</span><span class="adr"><span class="street-address vcardline">Digital Equipment Corporation</span><span class="street-address vcardline">250 University Avenue</span><span class="vcardline"><span class="locality">Palo Alto</span>, <span class="region">California</span>&nbsp;<span class="postal-code">94305</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a href=""><span class="email"></span></a></span></address><address class="vcard"><span class="vcardline"><span class="fn">Roy T. Fielding</span><span class="n hidden"><span class="family-name">Fielding</span><span class="given-name">Roy T.</span></span></span><span class="org vcardline">Department of Information and Computer Science</span><span class="adr"><span class="street-address vcardline">University of California</span><span class="vcardline"><span class="locality">Irvine</span>, <span class="region">CA</span>&nbsp;<span class="postal-code">92717-3425</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+1(714)824-4056"><span class="value">+1 (714) 824-4056</span></a></span><span class="vcardline">EMail: <a href=""><span class="email"></span></a></span></address><address class="vcard"><span class="vcardline"><span class="fn">Jim Gettys</span><span class="n hidden"><span class="family-name">Gettys</span><span class="given-name">Jim</span></span></span><span class="org vcardline">MIT Laboratory for Computer Science</span><span class="adr"><span class="street-address vcardline">545 Technology Square</span><span class="vcardline"><span class="locality">Cambridge</span>, <span class="region">MA</span>&nbsp;<span class="postal-code">02139</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+1(617)2588682"><span class="value">+1 (617) 258 8682</span></a></span><span class="vcardline">EMail: <a href=""><span class="email"></span></a></span></address><address class="vcard"><span class="vcardline"><span class="fn">Henrik Frystyk Nielsen</span><span class="n hidden"><span class="family-name">Frystyk</span></span></span><span class="org vcardline">W3 Consortium</span><span class="adr"><span class="street-address vcardline">MIT Laboratory for Computer Science</span><span class="street-address vcardline">545 Technology Square</span><span class="vcardline"><span class="locality">Cambridge</span>, <span class="region">MA</span>&nbsp;<span class="postal-code">02139</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+1(617)2588682"><span class="value">+1 (617) 258 8682</span></a></span><span class="vcardline">EMail: <a href=""><span class="email"></span></a></span></address><h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1><p>Copyright &copy; The Internet Society (1997). All Rights Reserved.</p><p>This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.</p><p>The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assignees.</p><p>This document and the information contained herein is provided on an &#8220;AS IS&#8221; basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.</p><hr class="noprint"><h1 class="np"><a id="rfc.ipr" href="#rfc.ipr">Intellectual Property</a></h1><p>The IETF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be found in BCP-11. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementors or users of this specification can be obtained from the IETF Secretariat.</p><p>The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director.</p></body></html>
Note: See TracBrowser for help on using the repository browser.