Changeset 122 for draft-ietf-httpbis/latest
- Timestamp:
- 31/12/07 17:30:10 (15 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p3-payload.html
r121 r122 1204 1204 <h2 id="rfc.references.1"><a href="#rfc.section.9.1" id="rfc.section.9.1">9.1</a> Normative References 1205 1205 </h2> 1206 <table summary="Normative References"> 1206 <table summary="Normative References"> 1207 1207 <tr> 1208 1208 <td class="reference"><b id="ISO-8859-1">[ISO-8859-1]</b></td> … … 1238 1238 </tr> 1239 1239 <tr> 1240 <td class="reference"><b id="RFC1950">[RFC1950]</b></td> 1241 <td class="top"><a title="Aladdin Enterprises">Deutsch, L.P.</a> and J-L. Gailly, “<a href="http://tools.ietf.org/html/rfc1950">ZLIB Compressed Data Format Specification version 3.3</a>”, RFC 1950, May 1996.<br>RFC1950 is an Informational RFC, thus it may be less stable than this specification. On the other hand, this downward reference 1242 was present since <a href="#RFC2068" id="rfc.xref.RFC2068.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a> (published in 1997), therefore it is unlikely to cause problems in practice. 1243 </td> 1244 </tr> 1245 <tr> 1246 <td class="reference"><b id="RFC1951">[RFC1951]</b></td> 1247 <td class="top"><a title="Aladdin Enterprises">Deutsch, P.</a>, “<a href="http://tools.ietf.org/html/rfc1951">DEFLATE Compressed Data Format Specification version 1.3</a>”, RFC 1951, May 1996.<br>RFC1951 is an Informational RFC, thus it may be less stable than this specification. On the other hand, this downward reference 1248 was present since <a href="#RFC2068" id="rfc.xref.RFC2068.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a> (published in 1997), therefore it is unlikely to cause problems in practice. 1249 </td> 1250 </tr> 1251 <tr> 1252 <td class="reference"><b id="RFC1952">[RFC1952]</b></td> 1253 <td class="top"><a title="Aladdin Enterprises">Deutsch, P.</a>, <a>Gailly, J-L.</a>, <a>Adler, M.</a>, <a>Deutsch, L.P.</a>, and <a>G. Randers-Pehrson</a>, “<a href="http://tools.ietf.org/html/rfc1952">GZIP file format specification version 4.3</a>”, RFC 1952, May 1996.<br>RFC1952 is an Informational RFC, thus it may be less stable than this specification. On the other hand, this downward reference 1254 was present since <a href="#RFC2068" id="rfc.xref.RFC2068.3"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a> (published in 1997), therefore it is unlikely to cause problems in practice. 1255 </td> 1256 </tr> 1257 <tr> 1240 1258 <td class="reference"><b id="RFC2119">[RFC2119]</b></td> 1241 1259 <td class="top"><a title="Harvard University">Bradner, S.</a>, “<a href="http://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>”, BCP 14, RFC 2119, March 1997. … … 1259 1277 <h2 id="rfc.references.3"><a href="#rfc.section.9.3" id="rfc.section.9.3">9.3</a> References (to be categorized) 1260 1278 </h2> 1261 <table summary="References (to be categorized)"> 1279 <table summary="References (to be categorized)"> 1262 1280 <tr> 1263 1281 <td class="reference"><b id="RFC1766">[RFC1766]</b></td> … … 1283 1301 <td class="reference"><b id="RFC1945">[RFC1945]</b></td> 1284 1302 <td class="top"><a title="MIT, Laboratory for Computer Science">Berners-Lee, T.</a>, <a title="University of California, Irvine, Department of Information and Computer Science">Fielding, R.T.</a>, and <a title="W3 Consortium, MIT Laboratory for Computer Science">H.F. Nielsen</a>, “<a href="http://tools.ietf.org/html/rfc1945">Hypertext Transfer Protocol -- HTTP/1.0</a>”, RFC 1945, May 1996. 1285 </td>1286 </tr>1287 <tr>1288 <td class="reference"><b id="RFC1950">[RFC1950]</b></td>1289 <td class="top"><a title="Aladdin Enterprises">Deutsch, L.P.</a> and J-L. Gailly, “<a href="http://tools.ietf.org/html/rfc1950">ZLIB Compressed Data Format Specification version 3.3</a>”, RFC 1950, May 1996.1290 </td>1291 </tr>1292 <tr>1293 <td class="reference"><b id="RFC1951">[RFC1951]</b></td>1294 <td class="top"><a title="Aladdin Enterprises">Deutsch, P.</a>, “<a href="http://tools.ietf.org/html/rfc1951">DEFLATE Compressed Data Format Specification version 1.3</a>”, RFC 1951, May 1996.1295 </td>1296 </tr>1297 <tr>1298 <td class="reference"><b id="RFC1952">[RFC1952]</b></td>1299 <td class="top"><a title="Aladdin Enterprises">Deutsch, P.</a>, <a>Gailly, J-L.</a>, <a>Adler, M.</a>, <a>Deutsch, L.P.</a>, and <a>G. Randers-Pehrson</a>, “<a href="http://tools.ietf.org/html/rfc1952">GZIP file format specification version 4.3</a>”, RFC 1952, May 1996.1300 1303 </td> 1301 1304 </tr> … … 1422 1425 </p> 1423 1426 <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a> <a id="additional.features" href="#additional.features">Additional Features</a></h1> 1424 <p id="rfc.section.B.p.1"> <a href="#RFC1945" id="rfc.xref.RFC1945.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.0">[RFC1945]</cite></a> and <a href="#RFC2068" id="rfc.xref.RFC2068. 1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a> document protocol elements used by some existing HTTP implementations, but not consistently and correctly across most HTTP/1.11427 <p id="rfc.section.B.p.1"> <a href="#RFC1945" id="rfc.xref.RFC1945.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.0">[RFC1945]</cite></a> and <a href="#RFC2068" id="rfc.xref.RFC2068.4"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a> document protocol elements used by some existing HTTP implementations, but not consistently and correctly across most HTTP/1.1 1425 1428 applications. Implementors are advised to be aware of these features, but cannot rely upon their presence in, or interoperability 1426 1429 with, other HTTP/1.1 applications. Some of these describe proposed experimental features, and some describe features that … … 1464 1467 <p id="rfc.section.C.1.p.4">Quality Values of zero should indicate that "I don't want something" to allow clients to refuse a representation. (<a href="#quality.values" title="Quality Values">Section 2.4</a>) 1465 1468 </p> 1466 <p id="rfc.section.C.1.p.5">The Alternates<span id="rfc.iref.a.5"></span><span id="rfc.iref.h.11"></span>, Content-Version<span id="rfc.iref.c.8"></span><span id="rfc.iref.h.12"></span>, Derived-From<span id="rfc.iref.d.2"></span><span id="rfc.iref.h.13"></span>, Link<span id="rfc.iref.l.1"></span><span id="rfc.iref.h.14"></span>, URI<span id="rfc.iref.u.1"></span><span id="rfc.iref.h.15"></span>, Public<span id="rfc.iref.p.1"></span><span id="rfc.iref.h.16"></span> and Content-Base<span id="rfc.iref.c.9"></span><span id="rfc.iref.h.17"></span> header fields were defined in previous versions of this specification, but not commonly implemented. See <a href="#RFC2068" id="rfc.xref.RFC2068. 2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>.1469 <p id="rfc.section.C.1.p.5">The Alternates<span id="rfc.iref.a.5"></span><span id="rfc.iref.h.11"></span>, Content-Version<span id="rfc.iref.c.8"></span><span id="rfc.iref.h.12"></span>, Derived-From<span id="rfc.iref.d.2"></span><span id="rfc.iref.h.13"></span>, Link<span id="rfc.iref.l.1"></span><span id="rfc.iref.h.14"></span>, URI<span id="rfc.iref.u.1"></span><span id="rfc.iref.h.15"></span>, Public<span id="rfc.iref.p.1"></span><span id="rfc.iref.h.16"></span> and Content-Base<span id="rfc.iref.c.9"></span><span id="rfc.iref.h.17"></span> header fields were defined in previous versions of this specification, but not commonly implemented. See <a href="#RFC2068" id="rfc.xref.RFC2068.5"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>. 1467 1470 </p> 1468 1471 <h2 id="rfc.section.C.2"><a href="#rfc.section.C.2">C.2</a> <a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2> … … 1488 1491 </li> 1489 1492 <li> <<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/46">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/46</a>>: "RFC1700 references" 1493 </li> 1494 <li> <<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/68">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/68</a>>: "Encoding References Normative" 1490 1495 </li> 1491 1496 </ul> … … 1666 1671 <li class="indline1"><em>RFC1867</em> <a class="iref" href="#rfc.xref.RFC1867.1">2.3.2</a>, <a class="iref" href="#RFC1867"><b>9.3</b></a></li> 1667 1672 <li class="indline1"><em>RFC1945</em> <a class="iref" href="#RFC1945"><b>9.3</b></a>, <a class="iref" href="#rfc.xref.RFC1945.1">B</a></li> 1668 <li class="indline1"><em>RFC1950</em> <a class="iref" href="#rfc.xref.RFC1950.1">2.2</a>, <a class="iref" href="#RFC1950"><b>9. 3</b></a></li>1669 <li class="indline1"><em>RFC1951</em> <a class="iref" href="#rfc.xref.RFC1951.1">2.2</a>, <a class="iref" href="#RFC1951"><b>9. 3</b></a></li>1670 <li class="indline1"><em>RFC1952</em> <a class="iref" href="#rfc.xref.RFC1952.1">2.2</a>, <a class="iref" href="#RFC1952"><b>9. 3</b></a></li>1673 <li class="indline1"><em>RFC1950</em> <a class="iref" href="#rfc.xref.RFC1950.1">2.2</a>, <a class="iref" href="#RFC1950"><b>9.1</b></a></li> 1674 <li class="indline1"><em>RFC1951</em> <a class="iref" href="#rfc.xref.RFC1951.1">2.2</a>, <a class="iref" href="#RFC1951"><b>9.1</b></a></li> 1675 <li class="indline1"><em>RFC1952</em> <a class="iref" href="#rfc.xref.RFC1952.1">2.2</a>, <a class="iref" href="#RFC1952"><b>9.1</b></a></li> 1671 1676 <li class="indline1"><em>RFC2045</em> <a class="iref" href="#RFC2045"><b>9.3</b></a>, <a class="iref" href="#rfc.xref.RFC2045.1">A</a>, <a class="iref" href="#rfc.xref.RFC2045.2">A.1</a>, <a class="iref" href="#rfc.xref.RFC2045.3">A.2</a></li> 1672 1677 <li class="indline1"><em>RFC2046</em> <a class="iref" href="#rfc.xref.RFC2046.1">2.3.2</a>, <a class="iref" href="#RFC2046"><b>9.3</b></a>, <a class="iref" href="#rfc.xref.RFC2046.2">A.2</a><ul class="ind"> … … 1678 1683 </ul> 1679 1684 </li> 1680 <li class="indline1"><em>RFC2068</em> <a class="iref" href="# RFC2068"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2068.1">B</a>, <a class="iref" href="#rfc.xref.RFC2068.2">C.1</a></li>1685 <li class="indline1"><em>RFC2068</em> <a class="iref" href="#rfc.xref.RFC2068.1">§</a>, <a class="iref" href="#rfc.xref.RFC2068.2">§</a>, <a class="iref" href="#rfc.xref.RFC2068.3">§</a>, <a class="iref" href="#RFC2068"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2068.4">B</a>, <a class="iref" href="#rfc.xref.RFC2068.5">C.1</a></li> 1681 1686 <li class="indline1"><em>RFC2076</em> <a class="iref" href="#RFC2076"><b>9.3</b></a>, <a class="iref" href="#rfc.xref.RFC2076.1">B</a></li> 1682 1687 <li class="indline1"><em>RFC2110</em> <a class="iref" href="#RFC2110"><b>9.3</b></a>, <a class="iref" href="#rfc.xref.RFC2110.1">A.6</a>, <a class="iref" href="#rfc.xref.RFC2110.2">C.1</a></li> -
draft-ietf-httpbis/latest/p3-payload.xml
r121 r122 1692 1692 </reference> 1693 1693 1694 <reference anchor="RFC1950"> 1695 <front> 1696 <title>ZLIB Compressed Data Format Specification version 3.3</title> 1697 <author initials="L.P." surname="Deutsch" fullname="L. Peter Deutsch"> 1698 <organization>Aladdin Enterprises</organization> 1699 <address><email>ghost@aladdin.com</email></address> 1700 </author> 1701 <author initials="J-L." surname="Gailly" fullname="Jean-Loup Gailly"> 1702 <organization/> 1703 </author> 1704 <date month="May" year="1996"/> 1705 </front> 1706 <seriesInfo name="RFC" value="1950"/> 1707 <annotation> 1708 RFC1950 is an Informational RFC, thus it may be less stable than 1709 this specification. On the other hand, this downward reference was 1710 present since <xref target="RFC2068"/> (published in 1997), therefore it is unlikely 1711 to cause problems in practice. 1712 </annotation> 1713 </reference> 1714 1715 <reference anchor="RFC1951"> 1716 <front> 1717 <title>DEFLATE Compressed Data Format Specification version 1.3</title> 1718 <author initials="P." surname="Deutsch" fullname="L. Peter Deutsch"> 1719 <organization>Aladdin Enterprises</organization> 1720 <address><email>ghost@aladdin.com</email></address> 1721 </author> 1722 <date month="May" year="1996"/> 1723 </front> 1724 <seriesInfo name="RFC" value="1951"/> 1725 <annotation> 1726 RFC1951 is an Informational RFC, thus it may be less stable than 1727 this specification. On the other hand, this downward reference was 1728 present since <xref target="RFC2068"/> (published in 1997), therefore it is unlikely 1729 to cause problems in practice. 1730 </annotation> 1731 </reference> 1732 1733 <reference anchor="RFC1952"> 1734 <front> 1735 <title>GZIP file format specification version 4.3</title> 1736 <author initials="P." surname="Deutsch" fullname="L. Peter Deutsch"> 1737 <organization>Aladdin Enterprises</organization> 1738 <address><email>ghost@aladdin.com</email></address> 1739 </author> 1740 <author initials="J-L." surname="Gailly" fullname="Jean-Loup Gailly"> 1741 <organization/> 1742 <address><email>gzip@prep.ai.mit.edu</email></address> 1743 </author> 1744 <author initials="M." surname="Adler" fullname="Mark Adler"> 1745 <organization/> 1746 <address><email>madler@alumni.caltech.edu</email></address> 1747 </author> 1748 <author initials="L.P." surname="Deutsch" fullname="L. Peter Deutsch"> 1749 <organization/> 1750 <address><email>ghost@aladdin.com</email></address> 1751 </author> 1752 <author initials="G." surname="Randers-Pehrson" fullname="Glenn Randers-Pehrson"> 1753 <organization/> 1754 <address><email>randeg@alumni.rpi.edu</email></address> 1755 </author> 1756 <date month="May" year="1996"/> 1757 </front> 1758 <seriesInfo name="RFC" value="1952"/> 1759 <annotation> 1760 RFC1952 is an Informational RFC, thus it may be less stable than 1761 this specification. On the other hand, this downward reference was 1762 present since <xref target="RFC2068"/> (published in 1997), therefore it is unlikely 1763 to cause problems in practice. 1764 </annotation> 1765 </reference> 1766 1694 1767 <reference anchor="RFC2119"> 1695 1768 <front> … … 1869 1942 </front> 1870 1943 <seriesInfo name="RFC" value="1864"/> 1871 </reference>1872 1873 <reference anchor="RFC1952">1874 <front>1875 <title>GZIP file format specification version 4.3</title>1876 <author initials="P." surname="Deutsch" fullname="L. Peter Deutsch">1877 <organization>Aladdin Enterprises</organization>1878 <address><email>ghost@aladdin.com</email></address>1879 </author>1880 <author initials="J-L." surname="Gailly" fullname="Jean-Loup Gailly">1881 <organization/>1882 <address><email>gzip@prep.ai.mit.edu</email></address></author>1883 <author initials="M." surname="Adler" fullname="Mark Adler">1884 <organization/>1885 <address><email>madler@alumni.caltech.edu</email></address></author>1886 <author initials="L.P." surname="Deutsch" fullname="L. Peter Deutsch">1887 <organization/>1888 <address><email>ghost@aladdin.com</email></address>1889 </author>1890 <author initials="G." surname="Randers-Pehrson" fullname="Glenn Randers-Pehrson">1891 <organization/>1892 <address><email>randeg@alumni.rpi.edu</email></address>1893 </author>1894 <date month="May" year="1996"/>1895 </front>1896 <seriesInfo name="RFC" value="1952"/>1897 </reference>1898 1899 <reference anchor="RFC1951">1900 <front>1901 <title>DEFLATE Compressed Data Format Specification version 1.3</title>1902 <author initials="P." surname="Deutsch" fullname="L. Peter Deutsch">1903 <organization>Aladdin Enterprises</organization>1904 <address><email>ghost@aladdin.com</email></address>1905 </author>1906 <date month="May" year="1996"/>1907 </front>1908 <seriesInfo name="RFC" value="1951"/>1909 </reference>1910 1911 <reference anchor="RFC1950">1912 <front>1913 <title>ZLIB Compressed Data Format Specification version 3.3</title>1914 <author initials="L.P." surname="Deutsch" fullname="L. Peter Deutsch">1915 <organization>Aladdin Enterprises</organization>1916 <address><email>ghost@aladdin.com</email></address>1917 </author>1918 <author initials="J-L." surname="Gailly" fullname="Jean-Loup Gailly">1919 <organization/>1920 </author>1921 <date month="May" year="1996"/>1922 </front>1923 <seriesInfo name="RFC" value="1950"/>1924 1944 </reference> 1925 1945 … … 2354 2374 "RFC1700 references" 2355 2375 </t> 2376 <t> 2377 <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/68"/>: 2378 "Encoding References Normative" 2379 </t> 2356 2380 </list> 2357 2381 </t>
Note: See TracChangeset
for help on using the changeset viewer.