Changeset 277
- Timestamp:
- 12/07/08 10:20:09 (14 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p3-payload.html
r272 r277 474 474 <tr> 475 475 <td class="header left"></td> 476 <td class="header right">July 6, 2008</td>476 <td class="header right">July 12, 2008</td> 477 477 </tr> 478 478 </table> … … 1403 1403 <tr> 1404 1404 <td class="reference"><b id="RFC1950">[RFC1950]</b></td> 1405 <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>RFC 1950 is an Informational RFC, thus it may be less stable than this specification. On the other hand, this downward reference1406 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.1405 <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>RFC 1950 is an Informational RFC, thus it may be less stable than this specification. On the other hand, this downward reference 1406 was present since the publication of RFC 2068 in 1997 (<a href="#RFC2068" id="rfc.xref.RFC2068.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>), therefore it is unlikely to cause problems in practice. See also <a href="#BCP97" id="rfc.xref.BCP97.1"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>. 1407 1407 </td> 1408 1408 </tr> 1409 1409 <tr> 1410 1410 <td class="reference"><b id="RFC1951">[RFC1951]</b></td> 1411 <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>RFC 1951 is an Informational RFC, thus it may be less stable than this specification. On the other hand, this downward reference1412 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.1411 <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>RFC 1951 is an Informational RFC, thus it may be less stable than this specification. On the other hand, this downward reference 1412 was present since the publication of RFC 2068 in 1997 (<a href="#RFC2068" id="rfc.xref.RFC2068.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>), therefore it is unlikely to cause problems in practice. See also <a href="#BCP97" id="rfc.xref.BCP97.2"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>. 1413 1413 </td> 1414 1414 </tr> 1415 1415 <tr> 1416 1416 <td class="reference"><b id="RFC1952">[RFC1952]</b></td> 1417 <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>RFC 1952 is an Informational RFC, thus it may be less stable than this specification. On the other hand, this downward reference1418 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.1417 <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>RFC 1952 is an Informational RFC, thus it may be less stable than this specification. On the other hand, this downward reference 1418 was present since the publication of RFC 2068 in 1997 (<a href="#RFC2068" id="rfc.xref.RFC2068.3"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>), therefore it is unlikely to cause problems in practice. See also <a href="#BCP97" id="rfc.xref.BCP97.3"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>. 1419 1419 </td> 1420 1420 </tr> … … 1437 1437 <h2 id="rfc.references.2"><a href="#rfc.section.10.2" id="rfc.section.10.2">10.2</a> Informative References 1438 1438 </h2> 1439 <table summary="Informative References"> 1439 <table summary="Informative References"> 1440 <tr> 1441 <td class="reference"><b id="BCP97">[BCP97]</b></td> 1442 <td class="top"><a>Klensin, J.</a> and <a title="MIT">S. Hartman</a>, “<a href="http://tools.ietf.org/html/rfc4897">Handling Normative References to Standards-Track Documents</a>”, BCP 97, RFC 4897, June 2007. 1443 </td> 1444 </tr> 1440 1445 <tr> 1441 1446 <td class="reference"><b id="RFC1945">[RFC1945]</b></td> … … 1685 1690 <p id="rfc.section.D.5.p.1">Closed issues: </p> 1686 1691 <ul> 1687 <li> <<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/121">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/121</a>>: "RFC 1806 has been replaced by RFC2183" 1692 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/121">http://tools.ietf.org/wg/httpbis/trac/ticket/121</a>>: "RFC 1806 has been replaced by RFC2183" 1693 </li> 1694 </ul> 1695 <p id="rfc.section.D.5.p.2">Other changes: </p> 1696 <ul> 1697 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/68">http://tools.ietf.org/wg/httpbis/trac/ticket/68</a>>: "Encoding References Normative" -- rephrase the annotation and reference <a href="#BCP97" id="rfc.xref.BCP97.4"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>. 1688 1698 </li> 1689 1699 </ul> … … 1713 1723 </p> 1714 1724 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> 1715 <p class="noprint"><a href="#rfc.index.A">A</a> <a href="#rfc.index. C">C</a> <a href="#rfc.index.D">D</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.L">L</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.U">U</a>1725 <p class="noprint"><a href="#rfc.index.A">A</a> <a href="#rfc.index.B">B</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.D">D</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.L">L</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.U">U</a> 1716 1726 </p> 1717 1727 <div class="print2col"> … … 1723 1733 <li class="indline1">Accept-Language header <a class="iref" href="#rfc.xref.header.accept-language.1">5.1</a>, <a class="iref" href="#rfc.iref.a.4"><b>6.4</b></a>, <a class="iref" href="#rfc.xref.header.accept-language.2">7.1</a></li> 1724 1734 <li class="indline1">Alternates header <a class="iref" href="#rfc.iref.a.5"><b>C.1</b></a></li> 1735 </ul> 1736 </li> 1737 <li class="indline0"><a id="rfc.index.B" href="#rfc.index.B"><b>B</b></a><ul class="ind"> 1738 <li class="indline1"><em>BCP97</em> <a class="iref" href="#rfc.xref.BCP97.1">§</a>, <a class="iref" href="#rfc.xref.BCP97.2">§</a>, <a class="iref" href="#rfc.xref.BCP97.3">§</a>, <a class="iref" href="#BCP97"><b>10.2</b></a>, <a class="iref" href="#rfc.xref.BCP97.4">D.5</a></li> 1725 1739 </ul> 1726 1740 </li> -
draft-ietf-httpbis/latest/p3-payload.xml
r271 r277 1922 1922 <seriesInfo name="RFC" value="1950"/> 1923 1923 <annotation> 1924 RFC 1950 is an Informational RFC, thus it may be less stable than1924 RFC 1950 is an Informational RFC, thus it may be less stable than 1925 1925 this specification. On the other hand, this downward reference was 1926 present since <xref target="RFC2068"/> (published in 1997), therefore it is unlikely 1927 to cause problems in practice. 1926 present since the publication of RFC 2068 in 1997 (<xref target="RFC2068"/>), 1927 therefore it is unlikely to cause problems in practice. See also 1928 <xref target="BCP97"/>. 1928 1929 </annotation> 1929 1930 </reference> … … 1940 1941 <seriesInfo name="RFC" value="1951"/> 1941 1942 <annotation> 1942 RFC 1951 is an Informational RFC, thus it may be less stable than1943 RFC 1951 is an Informational RFC, thus it may be less stable than 1943 1944 this specification. On the other hand, this downward reference was 1944 present since <xref target="RFC2068"/> (published in 1997), therefore it is unlikely 1945 to cause problems in practice. 1945 present since the publication of RFC 2068 in 1997 (<xref target="RFC2068"/>), 1946 therefore it is unlikely to cause problems in practice. See also 1947 <xref target="BCP97"/>. 1946 1948 </annotation> 1947 1949 </reference> … … 1974 1976 <seriesInfo name="RFC" value="1952"/> 1975 1977 <annotation> 1976 RFC 1952 is an Informational RFC, thus it may be less stable than1978 RFC 1952 is an Informational RFC, thus it may be less stable than 1977 1979 this specification. On the other hand, this downward reference was 1978 present since <xref target="RFC2068"/> (published in 1997), therefore it is unlikely 1979 to cause problems in practice. 1980 present since the publication of RFC 2068 in 1997 (<xref target="RFC2068"/>), 1981 therefore it is unlikely to cause problems in practice. See also 1982 <xref target="BCP97"/>. 1980 1983 </annotation> 1981 1984 </reference> … … 2276 2279 <seriesInfo name="RFC" value="4288"/> 2277 2280 </reference> 2281 2282 <reference anchor='BCP97'> 2283 <front> 2284 <title>Handling Normative References to Standards-Track Documents</title> 2285 <author initials='J.' surname='Klensin' fullname='J. Klensin'> 2286 <organization /> 2287 <address> 2288 <email>klensin+ietf@jck.com</email> 2289 </address> 2290 </author> 2291 <author initials='S.' surname='Hartman' fullname='S. Hartman'> 2292 <organization>MIT</organization> 2293 <address> 2294 <email>hartmans-ietf@mit.edu</email> 2295 </address> 2296 </author> 2297 <date year='2007' month='June' /> 2298 </front> 2299 <seriesInfo name='BCP' value='97' /> 2300 <seriesInfo name='RFC' value='4897' /> 2301 </reference> 2302 2278 2303 2279 2304 </references> … … 2625 2650 <list style="symbols"> 2626 2651 <t> 2627 <eref target="http:// www3.tools.ietf.org/wg/httpbis/trac/ticket/121"/>:2652 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/121"/>: 2628 2653 "RFC 1806 has been replaced by RFC2183" 2629 2654 </t> 2630 2655 </list> 2631 2656 </t> 2657 <t> 2658 Other changes: 2659 <list style="symbols"> 2660 <t> 2661 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/68"/>: 2662 "Encoding References Normative" -- rephrase the annotation and reference 2663 <xref target="BCP97"/>. 2664 </t> 2665 </list> 2666 </t> 2632 2667 </section> 2633 2668
Note: See TracChangeset
for help on using the changeset viewer.