Changeset 1477
- Timestamp:
- 14/11/11 10:27:42 (11 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 14 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r1476 r1477 359 359 } 360 360 @bottom-center { 361 content: "Expires May 1 4, 2012";361 content: "Expires May 17, 2012"; 362 362 } 363 363 @bottom-right { … … 409 409 <meta name="dct.creator" content="Reschke, J. F."> 410 410 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest"> 411 <meta name="dct.issued" scheme="ISO8601" content="2011-11-1 1">411 <meta name="dct.issued" scheme="ISO8601" content="2011-11-14"> 412 412 <meta name="dct.replaces" content="urn:ietf:rfc:2145"> 413 413 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> … … 441 441 </tr> 442 442 <tr> 443 <td class="left">Expires: May 1 4, 2012</td>443 <td class="left">Expires: May 17, 2012</td> 444 444 <td class="right">HP</td> 445 445 </tr> … … 494 494 <tr> 495 495 <td class="left"></td> 496 <td class="right">November 1 1, 2011</td>496 <td class="right">November 14, 2011</td> 497 497 </tr> 498 498 </tbody> … … 527 527 in progress”. 528 528 </p> 529 <p>This Internet-Draft will expire on May 1 4, 2012.</p>529 <p>This Internet-Draft will expire on May 17, 2012.</p> 530 530 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 531 531 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 2711 2711 <tr> 2712 2712 <td class="reference"><b id="RFC1950">[RFC1950]</b></td> 2713 <td class="top"><a href="mailto:ghost@aladdin.com" title="Aladdin Enterprises">Deutsch, L.</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 might be less stable than this specification. On the other hand, this downward reference 2714 was present since the publication of <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2068.5">RFC 2068</cite> in 1997, 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>. 2713 <td class="top"><a href="mailto:ghost@aladdin.com" title="Aladdin Enterprises">Deutsch, L.</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. 2715 2714 </td> 2716 2715 </tr> 2717 2716 <tr> 2718 2717 <td class="reference"><b id="RFC1951">[RFC1951]</b></td> 2719 <td class="top"><a href="mailto:ghost@aladdin.com" 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 might be less stable than this specification. On the other hand, this downward reference 2720 was present since the publication of <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2068.6">RFC 2068</cite> in 1997, 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>. 2718 <td class="top"><a href="mailto:ghost@aladdin.com" 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. 2721 2719 </td> 2722 2720 </tr> 2723 2721 <tr> 2724 2722 <td class="reference"><b id="RFC1952">[RFC1952]</b></td> 2725 <td class="top"><a href="mailto:ghost@aladdin.com" title="Aladdin Enterprises">Deutsch, P.</a>, <a href="mailto:gzip@prep.ai.mit.edu">Gailly, J-L.</a>, <a href="mailto:madler@alumni.caltech.edu">Adler, M.</a>, <a href="mailto:ghost@aladdin.com">Deutsch, L.</a>, and <a href="mailto:randeg@alumni.rpi.edu">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 might be less stable than this specification. On the other hand, this downward reference 2726 was present since the publication of <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2068.7">RFC 2068</cite> in 1997, 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>. 2723 <td class="top"><a href="mailto:ghost@aladdin.com" title="Aladdin Enterprises">Deutsch, P.</a>, <a href="mailto:gzip@prep.ai.mit.edu">Gailly, J-L.</a>, <a href="mailto:madler@alumni.caltech.edu">Adler, M.</a>, <a href="mailto:ghost@aladdin.com">Deutsch, L.</a>, and <a href="mailto:randeg@alumni.rpi.edu">G. Randers-Pehrson</a>, “<a href="http://tools.ietf.org/html/rfc1952">GZIP file format specification version 4.3</a>”, RFC 1952, May 1996. 2727 2724 </td> 2728 2725 </tr> … … 2750 2747 </h2> 2751 2748 <table> 2752 <tr>2753 <td class="reference"><b id="BCP97">[BCP97]</b></td>2754 <td class="top"><a href="mailto:klensin+ietf@jck.com">Klensin, J.</a> and <a href="mailto:hartmans-ietf@mit.edu" 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.2755 </td>2756 </tr>2757 2749 <tr> 2758 2750 <td class="reference"><b id="Kri2001">[Kri2001]</b></td> … … 2932 2924 <p id="rfc.section.A.1.2.p.1">For most implementations of HTTP/1.0, each connection is established by the client prior to the request and closed by the 2933 2925 server after sending the response. However, some implementations implement the Keep-Alive version of persistent connections 2934 described in <a href="http://tools.ietf.org/html/rfc2068#section-19.7.1">Section 19.7.1</a> of <a href="#RFC2068" id="rfc.xref.RFC2068. 8"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>.2926 described in <a href="http://tools.ietf.org/html/rfc2068#section-19.7.1">Section 19.7.1</a> of <a href="#RFC2068" id="rfc.xref.RFC2068.5"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>. 2935 2927 </p> 2936 2928 <p id="rfc.section.A.1.2.p.2">Some clients and servers might wish to be compatible with some previous implementations of persistent connections in HTTP/1.0 … … 3481 3473 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/300">http://tools.ietf.org/wg/httpbis/trac/ticket/300</a>>: "Define non-final responses" 3482 3474 </li> 3475 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/323">http://tools.ietf.org/wg/httpbis/trac/ticket/323</a>>: "intended maturity level vs normative references" 3476 </li> 3483 3477 </ul> 3484 3478 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> … … 3496 3490 </li> 3497 3491 <li><a id="rfc.index.B" href="#rfc.index.B"><b>B</b></a><ul> 3498 <li><em>BCP97</em> <a href="#rfc.xref.BCP97.1">12.1</a>, <a href="#rfc.xref.BCP97.2">12.1</a>, <a href="#rfc.xref.BCP97.3">12.1</a>, <a href="#BCP97"><b>12.2</b></a></li>3499 3492 <li>browser <a href="#rfc.iref.b.1"><b>2.1</b></a></li> 3500 3493 </ul> … … 3730 3723 </li> 3731 3724 <li><em>RFC2047</em> <a href="#rfc.xref.RFC2047.1">3.2.1</a>, <a href="#RFC2047"><b>12.2</b></a></li> 3732 <li><em>RFC2068</em> <a href="#rfc.xref.RFC2068.1">§</a>, <a href="#rfc.xref.RFC2068.2">2.6</a>, <a href="#rfc.xref.RFC2068.3">6.1.3</a>, <a href="#rfc.xref.RFC2068.4">6.2.3</a>, <a href="# rfc.xref.RFC2068.5">12.1</a>, <a href="#rfc.xref.RFC2068.6">12.1</a>, <a href="#rfc.xref.RFC2068.7">12.1</a>, <a href="#RFC2068"><b>12.2</b></a>, <a href="#rfc.xref.RFC2068.8">A.1.2</a><ul>3733 <li><em>Section 19.7.1</em> <a href="#rfc.xref.RFC2068.3">6.1.3</a>, <a href="#rfc.xref.RFC2068. 8">A.1.2</a></li>3725 <li><em>RFC2068</em> <a href="#rfc.xref.RFC2068.1">§</a>, <a href="#rfc.xref.RFC2068.2">2.6</a>, <a href="#rfc.xref.RFC2068.3">6.1.3</a>, <a href="#rfc.xref.RFC2068.4">6.2.3</a>, <a href="#RFC2068"><b>12.2</b></a>, <a href="#rfc.xref.RFC2068.5">A.1.2</a><ul> 3726 <li><em>Section 19.7.1</em> <a href="#rfc.xref.RFC2068.3">6.1.3</a>, <a href="#rfc.xref.RFC2068.5">A.1.2</a></li> 3734 3727 </ul> 3735 3728 </li> -
draft-ietf-httpbis/latest/p1-messaging.xml
r1476 r1477 55 55 <?rfc-ext allow-markup-in-artwork="yes" ?> 56 56 <?rfc-ext include-references-in-index="yes" ?> 57 <rfc obsoletes="2145,2616" updates="2817" category="std" x:maturity-level=" draft"57 <rfc obsoletes="2145,2616" updates="2817" category="std" x:maturity-level="proposed" 58 58 ipr="pre5378Trust200902" docName="draft-ietf-httpbis-p1-messaging-&ID-VERSION;" 59 59 xmlns:x='http://purl.org/net/xml2rfc/ext'> … … 4325 4325 </front> 4326 4326 <seriesInfo name="RFC" value="1950"/> 4327 < annotation>4327 <!--<annotation> 4328 4328 RFC 1950 is an Informational RFC, thus it might be less stable than 4329 4329 this specification. On the other hand, this downward reference was … … 4331 4331 therefore it is unlikely to cause problems in practice. See also 4332 4332 <xref target="BCP97"/>. 4333 </annotation> 4333 </annotation>--> 4334 4334 </reference> 4335 4335 … … 4344 4344 </front> 4345 4345 <seriesInfo name="RFC" value="1951"/> 4346 < annotation>4346 <!--<annotation> 4347 4347 RFC 1951 is an Informational RFC, thus it might be less stable than 4348 4348 this specification. On the other hand, this downward reference was … … 4350 4350 therefore it is unlikely to cause problems in practice. See also 4351 4351 <xref target="BCP97"/>. 4352 </annotation> 4352 </annotation>--> 4353 4353 </reference> 4354 4354 … … 4375 4375 </front> 4376 4376 <seriesInfo name="RFC" value="1952"/> 4377 < annotation>4377 <!--<annotation> 4378 4378 RFC 1952 is an Informational RFC, thus it might be less stable than 4379 4379 this specification. On the other hand, this downward reference was … … 4381 4381 therefore it is unlikely to cause problems in practice. See also 4382 4382 <xref target="BCP97"/>. 4383 </annotation> 4383 </annotation>--> 4384 4384 </reference> 4385 4385 … … 4753 4753 </reference> 4754 4754 4755 < reference anchor='BCP97'>4755 <!--<reference anchor='BCP97'> 4756 4756 <front> 4757 4757 <title>Handling Normative References to Standards-Track Documents</title> … … 4771 4771 <seriesInfo name='BCP' value='97' /> 4772 4772 <seriesInfo name='RFC' value='4897' /> 4773 </reference> 4773 </reference>--> 4774 4774 4775 4775 <reference anchor="Kri2001" target="http://arxiv.org/abs/cs.SE/0105018"> … … 5868 5868 "Define non-final responses" 5869 5869 </t> 5870 <t> 5871 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/323"/>: 5872 "intended maturity level vs normative references" 5873 </t> 5870 5874 </list> 5871 5875 </t> -
draft-ietf-httpbis/latest/p2-semantics.html
r1475 r1477 359 359 } 360 360 @bottom-center { 361 content: "Expires May 1 4, 2012";361 content: "Expires May 17, 2012"; 362 362 } 363 363 @bottom-right { … … 411 411 <meta name="dct.creator" content="Reschke, J. F."> 412 412 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 413 <meta name="dct.issued" scheme="ISO8601" content="2011-11-1 1">413 <meta name="dct.issued" scheme="ISO8601" content="2011-11-14"> 414 414 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 415 415 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 2 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request header fields, response status codes, and response header fields."> … … 442 442 </tr> 443 443 <tr> 444 <td class="left">Expires: May 1 4, 2012</td>444 <td class="left">Expires: May 17, 2012</td> 445 445 <td class="right">HP</td> 446 446 </tr> … … 495 495 <tr> 496 496 <td class="left"></td> 497 <td class="right">November 1 1, 2011</td>497 <td class="right">November 14, 2011</td> 498 498 </tr> 499 499 </tbody> … … 525 525 in progress”. 526 526 </p> 527 <p>This Internet-Draft will expire on May 1 4, 2012.</p>527 <p>This Internet-Draft will expire on May 17, 2012.</p> 528 528 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 529 529 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> -
draft-ietf-httpbis/latest/p2-semantics.xml
r1475 r1477 100 100 <?rfc-ext allow-markup-in-artwork="yes" ?> 101 101 <?rfc-ext include-references-in-index="yes" ?> 102 <rfc obsoletes="2616" updates="2817" category="std" x:maturity-level=" draft"102 <rfc obsoletes="2616" updates="2817" category="std" x:maturity-level="proposed" 103 103 ipr="pre5378Trust200902" docName="draft-ietf-httpbis-p2-semantics-&ID-VERSION;" 104 104 xmlns:x='http://purl.org/net/xml2rfc/ext' -
draft-ietf-httpbis/latest/p3-payload.html
r1472 r1477 359 359 } 360 360 @bottom-center { 361 content: "Expires May 8, 2012";361 content: "Expires May 17, 2012"; 362 362 } 363 363 @bottom-right { … … 410 410 <meta name="dct.creator" content="Reschke, J. F."> 411 411 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p3-payload-latest"> 412 <meta name="dct.issued" scheme="ISO8601" content="2011-11- 05">412 <meta name="dct.issued" scheme="ISO8601" content="2011-11-14"> 413 413 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 414 414 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 3 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 3 defines HTTP message content, metadata, and content negotiation."> … … 436 436 </tr> 437 437 <tr> 438 <td class="left">Expires: May 8, 2012</td>438 <td class="left">Expires: May 17, 2012</td> 439 439 <td class="right">J. Mogul</td> 440 440 </tr> … … 493 493 <tr> 494 494 <td class="left"></td> 495 <td class="right">November 5, 2011</td>495 <td class="right">November 14, 2011</td> 496 496 </tr> 497 497 </tbody> … … 521 521 in progress”. 522 522 </p> 523 <p>This Internet-Draft will expire on May 8, 2012.</p>523 <p>This Internet-Draft will expire on May 17, 2012.</p> 524 524 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 525 525 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1528 1528 <tr> 1529 1529 <td class="reference"><b id="RFC1950">[RFC1950]</b></td> 1530 <td class="top"><a href="mailto:ghost@aladdin.com" title="Aladdin Enterprises">Deutsch, L.</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 might be less stable than this specification. On the other hand, this downward reference 1531 was present since the publication of <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2068.1">RFC 2068</cite> in 1997, 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>. 1530 <td class="top"><a href="mailto:ghost@aladdin.com" title="Aladdin Enterprises">Deutsch, L.</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. 1532 1531 </td> 1533 1532 </tr> 1534 1533 <tr> 1535 1534 <td class="reference"><b id="RFC1951">[RFC1951]</b></td> 1536 <td class="top"><a href="mailto:ghost@aladdin.com" 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 might be less stable than this specification. On the other hand, this downward reference 1537 was present since the publication of <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2068.2">RFC 2068</cite> in 1997, 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>. 1535 <td class="top"><a href="mailto:ghost@aladdin.com" 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. 1538 1536 </td> 1539 1537 </tr> 1540 1538 <tr> 1541 1539 <td class="reference"><b id="RFC1952">[RFC1952]</b></td> 1542 <td class="top"><a href="mailto:ghost@aladdin.com" title="Aladdin Enterprises">Deutsch, P.</a>, <a href="mailto:gzip@prep.ai.mit.edu">Gailly, J-L.</a>, <a href="mailto:madler@alumni.caltech.edu">Adler, M.</a>, <a href="mailto:ghost@aladdin.com">Deutsch, L.</a>, and <a href="mailto:randeg@alumni.rpi.edu">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 might be less stable than this specification. On the other hand, this downward reference 1543 was present since the publication of <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2068.3">RFC 2068</cite> in 1997, 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>. 1540 <td class="top"><a href="mailto:ghost@aladdin.com" title="Aladdin Enterprises">Deutsch, P.</a>, <a href="mailto:gzip@prep.ai.mit.edu">Gailly, J-L.</a>, <a href="mailto:madler@alumni.caltech.edu">Adler, M.</a>, <a href="mailto:ghost@aladdin.com">Deutsch, L.</a>, and <a href="mailto:randeg@alumni.rpi.edu">G. Randers-Pehrson</a>, “<a href="http://tools.ietf.org/html/rfc1952">GZIP file format specification version 4.3</a>”, RFC 1952, May 1996. 1544 1541 </td> 1545 1542 </tr> … … 1578 1575 </h2> 1579 1576 <table> 1580 <tr>1581 <td class="reference"><b id="BCP97">[BCP97]</b></td>1582 <td class="top"><a href="mailto:klensin+ietf@jck.com">Klensin, J.</a> and <a href="mailto:hartmans-ietf@mit.edu" 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.1583 </td>1584 </tr>1585 1577 <tr> 1586 1578 <td class="reference"><b id="RFC1945">[RFC1945]</b></td> … … 1740 1732 </p> 1741 1733 <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a> <a id="additional.features" href="#additional.features">Additional Features</a></h1> 1742 <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.11734 <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.1 1743 1735 applications. Implementors are advised to be aware of these features, but cannot rely upon their presence in, or interoperability 1744 1736 with, other HTTP/1.1 applications. Some of these describe proposed experimental features, and some describe features that … … 1895 1887 <p id="rfc.section.E.5.p.2">Other changes: </p> 1896 1888 <ul> 1897 <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>.1889 <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 BCP97. 1898 1890 </li> 1899 1891 </ul> … … 2050 2042 </ul> 2051 2043 <h2 id="rfc.section.E.19"><a href="#rfc.section.E.19">E.19</a> <a id="changes.since.17" href="#changes.since.17">Since draft-ietf-httpbis-p3-payload-17</a></h2> 2052 <p id="rfc.section.E.19.p.1">No changes yet.</p> 2044 <p id="rfc.section.E.19.p.1">Closed issues: </p> 2045 <ul> 2046 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/323">http://tools.ietf.org/wg/httpbis/trac/ticket/323</a>>: "intended maturity level vs normative references" 2047 </li> 2048 </ul> 2053 2049 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> 2054 <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.M">M</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a>2050 <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.M">M</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> 2055 2051 </p> 2056 2052 <div class="print2col"> … … 2061 2057 <li>Accept-Encoding header field <a href="#rfc.xref.header.accept-encoding.1">2.2</a>, <a href="#rfc.xref.header.accept-encoding.2">5.1</a>, <a href="#rfc.iref.a.3"><b>6.3</b></a>, <a href="#rfc.xref.header.accept-encoding.3">7.1</a>, <a href="#rfc.xref.header.accept-encoding.4">7.2</a></li> 2062 2058 <li>Accept-Language header field <a href="#rfc.xref.header.accept-language.1">5.1</a>, <a href="#rfc.iref.a.4"><b>6.4</b></a>, <a href="#rfc.xref.header.accept-language.2">7.1</a></li> 2063 </ul>2064 </li>2065 <li><a id="rfc.index.B" href="#rfc.index.B"><b>B</b></a><ul>2066 <li><em>BCP97</em> <a href="#rfc.xref.BCP97.1">10.1</a>, <a href="#rfc.xref.BCP97.2">10.1</a>, <a href="#rfc.xref.BCP97.3">10.1</a>, <a href="#BCP97"><b>10.2</b></a>, <a href="#rfc.xref.BCP97.4">E.5</a></li>2067 2059 </ul> 2068 2060 </li> … … 2195 2187 </ul> 2196 2188 </li> 2197 <li><em>RFC2068</em> <a href="# rfc.xref.RFC2068.1">10.1</a>, <a href="#rfc.xref.RFC2068.2">10.1</a>, <a href="#rfc.xref.RFC2068.3">10.1</a>, <a href="#RFC2068"><b>10.2</b></a>, <a href="#rfc.xref.RFC2068.4">B</a></li>2189 <li><em>RFC2068</em> <a href="#RFC2068"><b>10.2</b></a>, <a href="#rfc.xref.RFC2068.1">B</a></li> 2198 2190 <li><em>RFC2076</em> <a href="#RFC2076"><b>10.2</b></a>, <a href="#rfc.xref.RFC2076.1">B</a></li> 2199 2191 <li><em>RFC2119</em> <a href="#rfc.xref.RFC2119.1">1.2</a>, <a href="#RFC2119"><b>10.1</b></a></li> -
draft-ietf-httpbis/latest/p3-payload.xml
r1472 r1477 55 55 <?rfc-ext allow-markup-in-artwork="yes" ?> 56 56 <?rfc-ext include-references-in-index="yes" ?> 57 <rfc obsoletes="2616" category="std" x:maturity-level=" draft"57 <rfc obsoletes="2616" category="std" x:maturity-level="proposed" 58 58 ipr="pre5378Trust200902" docName="draft-ietf-httpbis-p3-payload-&ID-VERSION;" 59 59 xmlns:x='http://purl.org/net/xml2rfc/ext'> … … 1887 1887 </front> 1888 1888 <seriesInfo name="RFC" value="1950"/> 1889 < annotation>1889 <!--<annotation> 1890 1890 RFC 1950 is an Informational RFC, thus it might be less stable than 1891 1891 this specification. On the other hand, this downward reference was … … 1893 1893 therefore it is unlikely to cause problems in practice. See also 1894 1894 <xref target="BCP97"/>. 1895 </annotation> 1895 </annotation>--> 1896 1896 </reference> 1897 1897 … … 1906 1906 </front> 1907 1907 <seriesInfo name="RFC" value="1951"/> 1908 < annotation>1908 <!--<annotation> 1909 1909 RFC 1951 is an Informational RFC, thus it might be less stable than 1910 1910 this specification. On the other hand, this downward reference was … … 1912 1912 therefore it is unlikely to cause problems in practice. See also 1913 1913 <xref target="BCP97"/>. 1914 </annotation> 1914 </annotation>--> 1915 1915 </reference> 1916 1916 … … 1937 1937 </front> 1938 1938 <seriesInfo name="RFC" value="1952"/> 1939 < annotation>1939 <!--<annotation> 1940 1940 RFC 1952 is an Informational RFC, thus it might be less stable than 1941 1941 this specification. On the other hand, this downward reference was … … 1943 1943 therefore it is unlikely to cause problems in practice. See also 1944 1944 <xref target="BCP97"/>. 1945 </annotation> 1945 </annotation>--> 1946 1946 </reference> 1947 1947 … … 2322 2322 </reference> 2323 2323 2324 < reference anchor='BCP97'>2324 <!--<reference anchor='BCP97'> 2325 2325 <front> 2326 2326 <title>Handling Normative References to Standards-Track Documents</title> … … 2340 2340 <seriesInfo name='BCP' value='97' /> 2341 2341 <seriesInfo name='RFC' value='4897' /> 2342 </reference> 2342 </reference>--> 2343 2343 2344 2344 <reference anchor="RFC6266"> … … 2756 2756 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/68"/>: 2757 2757 "Encoding References Normative" — rephrase the annotation and reference 2758 <xref target="BCP97"/>.2758 BCP97. 2759 2759 </t> 2760 2760 </list> … … 3067 3067 <section title="Since draft-ietf-httpbis-p3-payload-17" anchor="changes.since.17"> 3068 3068 <t> 3069 No changes yet. 3069 Closed issues: 3070 <list style="symbols"> 3071 <t> 3072 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/323"/>: 3073 "intended maturity level vs normative references" 3074 </t> 3075 </list> 3070 3076 </t> 3071 3077 </section> -
draft-ietf-httpbis/latest/p4-conditional.html
r1472 r1477 359 359 } 360 360 @bottom-center { 361 content: "Expires May 8, 2012";361 content: "Expires May 17, 2012"; 362 362 } 363 363 @bottom-right { … … 406 406 <meta name="dct.creator" content="Reschke, J. F."> 407 407 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p4-conditional-latest"> 408 <meta name="dct.issued" scheme="ISO8601" content="2011-11- 05">408 <meta name="dct.issued" scheme="ISO8601" content="2011-11-14"> 409 409 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 410 410 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 4 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 4 defines request header fields for indicating conditional requests and the rules for constructing responses to those requests."> … … 432 432 </tr> 433 433 <tr> 434 <td class="left">Expires: May 8, 2012</td>434 <td class="left">Expires: May 17, 2012</td> 435 435 <td class="right">J. Mogul</td> 436 436 </tr> … … 489 489 <tr> 490 490 <td class="left"></td> 491 <td class="right">November 5, 2011</td>491 <td class="right">November 14, 2011</td> 492 492 </tr> 493 493 </tbody> … … 519 519 in progress”. 520 520 </p> 521 <p>This Internet-Draft will expire on May 8, 2012.</p>521 <p>This Internet-Draft will expire on May 17, 2012.</p> 522 522 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 523 523 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> -
draft-ietf-httpbis/latest/p4-conditional.xml
r1472 r1477 44 44 <?rfc-ext allow-markup-in-artwork="yes" ?> 45 45 <?rfc-ext include-references-in-index="yes" ?> 46 <rfc obsoletes="2616" category="std" x:maturity-level=" draft"46 <rfc obsoletes="2616" category="std" x:maturity-level="proposed" 47 47 ipr="pre5378Trust200902" docName="draft-ietf-httpbis-p4-conditional-&ID-VERSION;" 48 48 xmlns:x='http://purl.org/net/xml2rfc/ext'> -
draft-ietf-httpbis/latest/p5-range.html
r1472 r1477 359 359 } 360 360 @bottom-center { 361 content: "Expires May 8, 2012";361 content: "Expires May 17, 2012"; 362 362 } 363 363 @bottom-right { … … 408 408 <meta name="dct.creator" content="Reschke, J. F."> 409 409 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest"> 410 <meta name="dct.issued" scheme="ISO8601" content="2011-11- 05">410 <meta name="dct.issued" scheme="ISO8601" content="2011-11-14"> 411 411 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 412 412 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 5 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 5 defines range-specific requests and the rules for constructing and combining responses to those requests."> … … 434 434 </tr> 435 435 <tr> 436 <td class="left">Expires: May 8, 2012</td>436 <td class="left">Expires: May 17, 2012</td> 437 437 <td class="right">J. Mogul</td> 438 438 </tr> … … 491 491 <tr> 492 492 <td class="left"></td> 493 <td class="right">November 5, 2011</td>493 <td class="right">November 14, 2011</td> 494 494 </tr> 495 495 </tbody> … … 519 519 in progress”. 520 520 </p> 521 <p>This Internet-Draft will expire on May 8, 2012.</p>521 <p>This Internet-Draft will expire on May 17, 2012.</p> 522 522 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 523 523 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> -
draft-ietf-httpbis/latest/p5-range.xml
r1472 r1477 39 39 <?rfc-ext allow-markup-in-artwork="yes" ?> 40 40 <?rfc-ext include-references-in-index="yes" ?> 41 <rfc obsoletes="2616" category="std" x:maturity-level="draft" 42 ipr="pre5378Trust200902" docName="draft-ietf-httpbis-p5-range-&ID-VERSION;" xmlns:x='http://purl.org/net/xml2rfc/ext'> 41 <rfc obsoletes="2616" category="std" x:maturity-level="proposed" 42 ipr="pre5378Trust200902" docName="draft-ietf-httpbis-p5-range-&ID-VERSION;" 43 xmlns:x='http://purl.org/net/xml2rfc/ext'> 43 44 <x:link rel="prev" basename="p4-conditional"/> 44 45 <x:link rel="next" basename="p6-cache"/> -
draft-ietf-httpbis/latest/p6-cache.html
r1472 r1477 362 362 } 363 363 @bottom-center { 364 content: "Expires May 8, 2012";364 content: "Expires May 17, 2012"; 365 365 } 366 366 @bottom-right { … … 410 410 <meta name="dct.creator" content="Reschke, J. F."> 411 411 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest"> 412 <meta name="dct.issued" scheme="ISO8601" content="2011-11- 05">412 <meta name="dct.issued" scheme="ISO8601" content="2011-11-14"> 413 413 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 414 414 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 6 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 6 defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages."> … … 436 436 </tr> 437 437 <tr> 438 <td class="left">Expires: May 8, 2012</td>438 <td class="left">Expires: May 17, 2012</td> 439 439 <td class="right">J. Mogul</td> 440 440 </tr> … … 501 501 <tr> 502 502 <td class="left"></td> 503 <td class="right">November 5, 2011</td>503 <td class="right">November 14, 2011</td> 504 504 </tr> 505 505 </tbody> … … 531 531 in progress”. 532 532 </p> 533 <p>This Internet-Draft will expire on May 8, 2012.</p>533 <p>This Internet-Draft will expire on May 17, 2012.</p> 534 534 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 535 535 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> -
draft-ietf-httpbis/latest/p6-cache.xml
r1472 r1477 54 54 <?rfc-ext include-references-in-index="yes" ?> 55 55 <rfc category="std" docName="draft-ietf-httpbis-p6-cache-&ID-VERSION;" ipr="pre5378Trust200902" 56 obsoletes="2616" x:maturity-level=" draft" xmlns:x="http://purl.org/net/xml2rfc/ext">56 obsoletes="2616" x:maturity-level="proposed" xmlns:x="http://purl.org/net/xml2rfc/ext"> 57 57 <x:link rel="prev" basename="p5-range"/> 58 58 <x:link rel="next" basename="p7-auth"/> -
draft-ietf-httpbis/latest/p7-auth.html
r1473 r1477 359 359 } 360 360 @bottom-center { 361 content: "Expires May 1 3, 2012";361 content: "Expires May 17, 2012"; 362 362 } 363 363 @bottom-right { … … 405 405 <meta name="dct.creator" content="Reschke, J. F."> 406 406 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p7-auth-latest"> 407 <meta name="dct.issued" scheme="ISO8601" content="2011-11-1 0">407 <meta name="dct.issued" scheme="ISO8601" content="2011-11-14"> 408 408 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 409 409 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 7 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 7 defines the HTTP Authentication framework."> … … 436 436 </tr> 437 437 <tr> 438 <td class="left">Expires: May 1 3, 2012</td>438 <td class="left">Expires: May 17, 2012</td> 439 439 <td class="right">HP</td> 440 440 </tr> … … 489 489 <tr> 490 490 <td class="left"></td> 491 <td class="right">November 1 0, 2011</td>491 <td class="right">November 14, 2011</td> 492 492 </tr> 493 493 </tbody> … … 517 517 in progress”. 518 518 </p> 519 <p>This Internet-Draft will expire on May 1 3, 2012.</p>519 <p>This Internet-Draft will expire on May 17, 2012.</p> 520 520 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 521 521 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> -
draft-ietf-httpbis/latest/p7-auth.xml
r1473 r1477 39 39 <?rfc-ext allow-markup-in-artwork="yes" ?> 40 40 <?rfc-ext include-references-in-index="yes" ?> 41 <rfc obsoletes="2616" updates="2617" category="std" x:maturity-level=" draft"41 <rfc obsoletes="2616" updates="2617" category="std" x:maturity-level="proposed" 42 42 ipr="pre5378Trust200902" docName="draft-ietf-httpbis-p7-auth-&ID-VERSION;" 43 43 xmlns:x='http://purl.org/net/xml2rfc/ext'>
Note: See TracChangeset
for help on using the changeset viewer.