Changeset 1567
- Timestamp:
- Mar 8, 2012, 2:01:34 AM (8 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 12 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r1566 r1567 460 460 } 461 461 @bottom-center { 462 content: "Expires September 8, 2012";462 content: "Expires September 9, 2012"; 463 463 } 464 464 @bottom-right { … … 510 510 <meta name="dct.creator" content="Reschke, J. F."> 511 511 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest"> 512 <meta name="dct.issued" scheme="ISO8601" content="2012-03-0 7">512 <meta name="dct.issued" scheme="ISO8601" content="2012-03-08"> 513 513 <meta name="dct.replaces" content="urn:ietf:rfc:2145"> 514 514 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> … … 542 542 </tr> 543 543 <tr> 544 <td class="left">Expires: September 8, 2012</td>544 <td class="left">Expires: September 9, 2012</td> 545 545 <td class="right">HP</td> 546 546 </tr> … … 595 595 <tr> 596 596 <td class="left"></td> 597 <td class="right">March 7, 2012</td>597 <td class="right">March 8, 2012</td> 598 598 </tr> 599 599 </tbody> … … 628 628 in progress”. 629 629 </p> 630 <p>This Internet-Draft will expire on September 8, 2012.</p>630 <p>This Internet-Draft will expire on September 9, 2012.</p> 631 631 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 632 632 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 801 801 </li> 802 802 <li>A.2 <a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li> 803 <li>A.3 <a href="#changes.from.rfc.2817">Changes from RFC 2817</a></li> 803 804 </ul> 804 805 </li> … … 1880 1881 <p id="rfc.section.5.3.p.3">Names of transfer codings <em class="bcp14">MUST NOT</em> overlap with names of content codings (<a href="p3-payload.html#content.codings" title="Content Codings">Section 2.2</a> of <a href="#Part3" id="rfc.xref.Part3.3"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>), unless the encoding transformation is identical (as it is the case for the compression codings defined in <a href="#compression.codings" title="Compression Codings">Section 5.2</a>). 1881 1882 </p> 1882 <p id="rfc.section.5.3.p.4">Values to be added to this name space require a specification (see "Specification Required" in<a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a> of <a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>), and <em class="bcp14">MUST</em> conform to the purpose of transfer coding defined in this section.1883 <p id="rfc.section.5.3.p.4">Values to be added to this name space require IETF Review (see <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a> of <a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>), and <em class="bcp14">MUST</em> conform to the purpose of transfer coding defined in this section. 1883 1884 </p> 1884 1885 <p id="rfc.section.5.3.p.5">The registry itself is maintained at <<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>>. … … 2365 2366 details how the connection will be processed after it has been upgraded. 2366 2367 </p> 2367 <p id="rfc.section.8.3.1.p.2">Registrations are allowed on a First Come First Served basis as described in <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a> of <a href="#RFC5226" id="rfc.xref.RFC5226.2"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>. The specifications need not be IETF documents or be subject to IESG review. Registrationsare subject to the following rules:2368 <p id="rfc.section.8.3.1.p.2">Registrations require IETF Review (see <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a> of <a href="#RFC5226" id="rfc.xref.RFC5226.2"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>) and are subject to the following rules: 2368 2369 </p> 2369 2370 <ol> … … 3091 3092 disallowed line folding in chunk extensions, and deprecate their use. (<a href="#chunked.encoding" title="Chunked Transfer Coding">Section 5.1</a>) 3092 3093 </p> 3093 <p id="rfc.section.A.2.p.10">Remove hard limit of two connections per server. Remove requirement to retry a sequence of requests as long it was idempotent. 3094 <p id="rfc.section.A.2.p.10">Registration of Transfer Codings now requires IETF Review (<a href="#transfer.coding.registry" title="Transfer Coding Registry">Section 5.3</a>) 3095 </p> 3096 <p id="rfc.section.A.2.p.11">Remove hard limit of two connections per server. Remove requirement to retry a sequence of requests as long it was idempotent. 3094 3097 Remove requirements about when servers are allowed to close connections prematurely. (<a href="#persistent.practical" title="Practical Considerations">Section 6.1.4</a>) 3095 3098 </p> 3096 <p id="rfc.section.A.2.p.11">Remove requirement to retry requests under certain cirumstances when the server prematurely closes the connection. (<a href="#message.transmission.requirements" title="Message Transmission Requirements">Section 6.2</a>) 3097 </p> 3098 <p id="rfc.section.A.2.p.12">Change ABNF productions for header fields to only define the field value. (<a href="#header.field.definitions" title="Header Field Definitions">Section 8</a>) 3099 </p> 3100 <p id="rfc.section.A.2.p.13">Clarify exactly when close connection options must be sent. (<a href="#header.connection" id="rfc.xref.header.connection.12" title="Connection">Section 8.1</a>) 3101 </p> 3102 <p id="rfc.section.A.2.p.14">Define the semantics of the "Upgrade" header field in responses other than 101 (this was incorporated from <a href="#RFC2817" id="rfc.xref.RFC2817.3"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>). (<a href="#header.upgrade" id="rfc.xref.header.upgrade.3" title="Upgrade">Section 8.3</a>) 3099 <p id="rfc.section.A.2.p.12">Remove requirement to retry requests under certain cirumstances when the server prematurely closes the connection. (<a href="#message.transmission.requirements" title="Message Transmission Requirements">Section 6.2</a>) 3100 </p> 3101 <p id="rfc.section.A.2.p.13">Change ABNF productions for header fields to only define the field value. (<a href="#header.field.definitions" title="Header Field Definitions">Section 8</a>) 3102 </p> 3103 <p id="rfc.section.A.2.p.14">Clarify exactly when close connection options must be sent. (<a href="#header.connection" id="rfc.xref.header.connection.12" title="Connection">Section 8.1</a>) 3104 </p> 3105 <p id="rfc.section.A.2.p.15">Define the semantics of the "Upgrade" header field in responses other than 101 (this was incorporated from <a href="#RFC2817" id="rfc.xref.RFC2817.3"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>). (<a href="#header.upgrade" id="rfc.xref.header.upgrade.3" title="Upgrade">Section 8.3</a>) 3106 </p> 3107 <h2 id="rfc.section.A.3"><a href="#rfc.section.A.3">A.3</a> <a id="changes.from.rfc.2817" href="#changes.from.rfc.2817">Changes from RFC 2817</a></h2> 3108 <p id="rfc.section.A.3.p.1">Registration of Upgrade tokens now requires IETF Review (<a href="#upgrade.token.registry" title="Upgrade Token Registry">Section 8.3.1</a>) 3103 3109 </p> 3104 3110 <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a> <a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1> … … 3614 3620 </li> 3615 3621 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/343">http://tools.ietf.org/wg/httpbis/trac/ticket/343</a>>: "chunk-extensions" 3622 </li> 3623 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/346">http://tools.ietf.org/wg/httpbis/trac/ticket/346</a>>: "make IANA policy definitions consistent" 3616 3624 </li> 3617 3625 </ul> -
draft-ietf-httpbis/latest/p1-messaging.xml
r1566 r1567 2392 2392 </t> 2393 2393 <t> 2394 Values to be added to this name space require a specification2395 (see "Specification Required" in<xref target="RFC5226" x:fmt="of" x:sec="4.1"/>), and &MUST;2394 Values to be added to this name space require IETF Review (see 2395 <xref target="RFC5226" x:fmt="of" x:sec="4.1"/>), and &MUST; 2396 2396 conform to the purpose of transfer coding defined in this section. 2397 2397 </t> … … 3322 3322 </t> 3323 3323 <t> 3324 Registrations are allowed on a First Come First Served basis as 3325 described in <xref target="RFC5226" x:sec="4.1" x:fmt="of"/>. The 3326 specifications need not be IETF documents or be subject to IESG review. 3327 Registrations are subject to the following rules: 3324 Registrations require IETF Review (see 3325 <xref target="RFC5226" x:sec="4.1" x:fmt="of"/>) and are subject to the 3326 following rules: 3328 3327 <list style="numbers"> 3329 3328 <t>A protocol-name token, once registered, stays registered forever.</t> … … 5007 5006 </t> 5008 5007 <t> 5008 Registration of Transfer Codings now requires IETF Review 5009 (<xref target="transfer.coding.registry"/>) 5010 </t> 5011 <t> 5009 5012 Remove hard limit of two connections per server. 5010 5013 Remove requirement to retry a sequence of requests as long it was idempotent. … … 5030 5033 101 (this was incorporated from <xref target="RFC2817"/>). 5031 5034 (<xref target="header.upgrade"/>) 5035 </t> 5036 </section> 5037 5038 <section title="Changes from RFC 2817" anchor="changes.from.rfc.2817"> 5039 <t> 5040 Registration of Upgrade tokens now requires IETF Review 5041 (<xref target="upgrade.token.registry"/>) 5032 5042 </t> 5033 5043 </section> … … 5937 5947 "chunk-extensions" 5938 5948 </t> 5949 <t> 5950 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/346"/>: 5951 "make IANA policy definitions consistent" 5952 </t> 5939 5953 </list> 5940 5954 </t> -
draft-ietf-httpbis/latest/p2-semantics.html
r1561 r1567 460 460 } 461 461 @bottom-center { 462 content: "Expires September 5, 2012";462 content: "Expires September 9, 2012"; 463 463 } 464 464 @bottom-right { … … 513 513 <meta name="dct.creator" content="Reschke, J. F."> 514 514 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 515 <meta name="dct.issued" scheme="ISO8601" content="2012-03-0 4">515 <meta name="dct.issued" scheme="ISO8601" content="2012-03-08"> 516 516 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 517 517 <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."> … … 544 544 </tr> 545 545 <tr> 546 <td class="left">Expires: September 5, 2012</td>546 <td class="left">Expires: September 9, 2012</td> 547 547 <td class="right">HP</td> 548 548 </tr> … … 597 597 <tr> 598 598 <td class="left"></td> 599 <td class="right">March 4, 2012</td>599 <td class="right">March 8, 2012</td> 600 600 </tr> 601 601 </tbody> … … 627 627 in progress”. 628 628 </p> 629 <p>This Internet-Draft will expire on September 5, 2012.</p>629 <p>This Internet-Draft will expire on September 9, 2012.</p> 630 630 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 631 631 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 935 935 <li>Pointer to specification text</li> 936 936 </ul> 937 <p id="rfc.section.2.2.p.3">Values to be added to this name space are subject to IETF review (<a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>).937 <p id="rfc.section.2.2.p.3">Values to be added to this name space require IETF Review (see <a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>). 938 938 </p> 939 939 <p id="rfc.section.2.2.p.4">The registry itself is maintained at <<a href="http://www.iana.org/assignments/http-methods">http://www.iana.org/assignments/http-methods</a>>. … … 1412 1412 <h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a> <a id="status.code.registry" href="#status.code.registry">Status Code Registry</a></h2> 1413 1413 <p id="rfc.section.4.2.p.1">The HTTP Status Code Registry defines the name space for the status-code token in the status-line of an HTTP response.</p> 1414 <p id="rfc.section.4.2.p.2">Values to be added to this name space are subject to IETF review (<a href="#RFC5226" id="rfc.xref.RFC5226.2"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>).1414 <p id="rfc.section.4.2.p.2">Values to be added to this name space require IETF Review (see <a href="#RFC5226" id="rfc.xref.RFC5226.2"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>). 1415 1415 </p> 1416 1416 <p id="rfc.section.4.2.p.3">The registry itself is maintained at <<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>>. -
draft-ietf-httpbis/latest/p2-semantics.xml
r1561 r1567 461 461 </t> 462 462 <t> 463 Values to be added to this name space are subject to IETF review464 ( <xref target="RFC5226" x:fmt="," x:sec="4.1"/>).463 Values to be added to this name space require IETF Review 464 (see <xref target="RFC5226" x:fmt="," x:sec="4.1"/>). 465 465 </t> 466 466 <t> … … 756 756 </t> 757 757 <t> 758 Values to be added to this name space are subject to IETF review759 ( <xref target="RFC5226" x:fmt="," x:sec="4.1"/>).758 Values to be added to this name space require IETF Review 759 (see <xref target="RFC5226" x:fmt="," x:sec="4.1"/>). 760 760 </t> 761 761 <t> -
draft-ietf-httpbis/latest/p3-payload.html
r1566 r1567 460 460 } 461 461 @bottom-center { 462 content: "Expires September 8, 2012";462 content: "Expires September 9, 2012"; 463 463 } 464 464 @bottom-right { … … 511 511 <meta name="dct.creator" content="Reschke, J. F."> 512 512 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p3-payload-latest"> 513 <meta name="dct.issued" scheme="ISO8601" content="2012-03-0 7">513 <meta name="dct.issued" scheme="ISO8601" content="2012-03-08"> 514 514 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 515 515 <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."> … … 537 537 </tr> 538 538 <tr> 539 <td class="left">Expires: September 8, 2012</td>539 <td class="left">Expires: September 9, 2012</td> 540 540 <td class="right">J. Mogul</td> 541 541 </tr> … … 594 594 <tr> 595 595 <td class="left"></td> 596 <td class="right">March 7, 2012</td>596 <td class="right">March 8, 2012</td> 597 597 </tr> 598 598 </tbody> … … 622 622 in progress”. 623 623 </p> 624 <p>This Internet-Draft will expire on September 8, 2012.</p>624 <p>This Internet-Draft will expire on September 9, 2012.</p> 625 625 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 626 626 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 857 857 <p id="rfc.section.2.2.1.p.3">Names of content codings <em class="bcp14">MUST NOT</em> overlap with names of transfer codings (<a href="p1-messaging.html#transfer.codings" title="Transfer Codings">Section 5</a> of <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>), unless the encoding transformation is identical (as is the case for the compression codings defined in <a href="p1-messaging.html#compression.codings" title="Compression Codings">Section 5.2</a> of <a href="#Part1" id="rfc.xref.Part1.14"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). 858 858 </p> 859 <p id="rfc.section.2.2.1.p.4">Values to be added to this name space require a specification (see "Specification Required" in<a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a> of <a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>), and <em class="bcp14">MUST</em> conform to the purpose of content coding defined in this section.859 <p id="rfc.section.2.2.1.p.4">Values to be added to this name space require IETF Review (see <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a> of <a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>), and <em class="bcp14">MUST</em> conform to the purpose of content coding defined in this section. 860 860 </p> 861 861 <p id="rfc.section.2.2.1.p.5">The registry itself is maintained at <<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>>. … … 1847 1847 <p id="rfc.section.C.p.1">Clarify contexts that charset is used in. (<a href="#character.sets" title="Character Encodings (charset)">Section 2.1</a>) 1848 1848 </p> 1849 <p id="rfc.section.C.p.2">Remove the default character encoding for text media types; the default now is whatever the media type definition says. (<a href="#canonicalization.and.text.defaults" title="Canonicalization and Text Defaults">Section 2.3.1</a>) 1850 </p> 1851 <p id="rfc.section.C.p.3">Change ABNF productions for header fields to only define the field value. (<a href="#header.field.definitions" title="Header Field Definitions">Section 6</a>) 1852 </p> 1853 <p id="rfc.section.C.p.4">Remove definition of Content-MD5 header field because it was inconsistently implemented with respect to partial responses, 1849 <p id="rfc.section.C.p.2">Registration of Content Codings now requires IETF Review (<a href="#content.coding.registry" title="Content Coding Registry">Section 2.2.1</a>) 1850 </p> 1851 <p id="rfc.section.C.p.3">Remove the default character encoding for text media types; the default now is whatever the media type definition says. (<a href="#canonicalization.and.text.defaults" title="Canonicalization and Text Defaults">Section 2.3.1</a>) 1852 </p> 1853 <p id="rfc.section.C.p.4">Change ABNF productions for header fields to only define the field value. (<a href="#header.field.definitions" title="Header Field Definitions">Section 6</a>) 1854 </p> 1855 <p id="rfc.section.C.p.5">Remove definition of Content-MD5 header field because it was inconsistently implemented with respect to partial responses, 1854 1856 and also because of known deficiencies in the hash algorithm itself (see <a href="#RFC6151" id="rfc.xref.RFC6151.1"><cite title="Updated Security Considerations for the MD5 Message-Digest and the HMAC-MD5 Algorithms">[RFC6151]</cite></a> for details). (<a href="#header.field.definitions" title="Header Field Definitions">Section 6</a>) 1855 1857 </p> 1856 <p id="rfc.section.C.p. 5">Remove ISO-8859-1 special-casing in Accept-Charset. (<a href="#header.accept-charset" id="rfc.xref.header.accept-charset.3" title="Accept-Charset">Section 6.2</a>)1857 </p> 1858 <p id="rfc.section.C.p. 6">Remove base URI setting semantics for Content-Location due to poor implementation support, which was caused by too many broken1858 <p id="rfc.section.C.p.6">Remove ISO-8859-1 special-casing in Accept-Charset. (<a href="#header.accept-charset" id="rfc.xref.header.accept-charset.3" title="Accept-Charset">Section 6.2</a>) 1859 </p> 1860 <p id="rfc.section.C.p.7">Remove base URI setting semantics for Content-Location due to poor implementation support, which was caused by too many broken 1859 1861 servers emitting bogus Content-Location header fields, and also the potentially undesirable effect of potentially breaking 1860 1862 relative links in content-negotiated resources. (<a href="#header.content-location" id="rfc.xref.header.content-location.3" title="Content-Location">Section 6.7</a>) 1861 1863 </p> 1862 <p id="rfc.section.C.p. 7">Remove reference to non-existant identity transfer-coding value tokens. (<a href="#no.content-transfer-encoding" id="rfc.xref.no.content-transfer-encoding.1" title="No Content-Transfer-Encoding">Appendix A.5</a>)1863 </p> 1864 <p id="rfc.section.C.p. 8">Remove discussion of Content-Disposition header field, it is now defined by <a href="#RFC6266" id="rfc.xref.RFC6266.2"><cite title="Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)">[RFC6266]</cite></a>. (<a href="#additional.features" title="Additional Features">Appendix B</a>)1864 <p id="rfc.section.C.p.8">Remove reference to non-existant identity transfer-coding value tokens. (<a href="#no.content-transfer-encoding" id="rfc.xref.no.content-transfer-encoding.1" title="No Content-Transfer-Encoding">Appendix A.5</a>) 1865 </p> 1866 <p id="rfc.section.C.p.9">Remove discussion of Content-Disposition header field, it is now defined by <a href="#RFC6266" id="rfc.xref.RFC6266.2"><cite title="Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)">[RFC6266]</cite></a>. (<a href="#additional.features" title="Additional Features">Appendix B</a>) 1865 1867 </p> 1866 1868 <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a> <a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1> … … 2153 2155 </ul> 2154 2156 <h2 id="rfc.section.E.20"><a href="#rfc.section.E.20">E.20</a> <a id="changes.since.18" href="#changes.since.18">Since draft-ietf-httpbis-p3-payload-18</a></h2> 2155 <p id="rfc.section.E.20.p.1">None yet.</p> 2157 <p id="rfc.section.E.20.p.1">Closed issues: </p> 2158 <ul> 2159 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/346">http://tools.ietf.org/wg/httpbis/trac/ticket/346</a>>: "make IANA policy definitions consistent" 2160 </li> 2161 </ul> 2156 2162 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> 2157 2163 <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> -
draft-ietf-httpbis/latest/p3-payload.xml
r1566 r1567 462 462 </t> 463 463 <t> 464 Values to be added to this name space require a specification 465 (see "Specification Required" in 466 <xref target="RFC5226" x:fmt="of" x:sec="4.1"/>), and &MUST; 464 Values to be added to this name space require IETF Review 465 (see <xref target="RFC5226" x:fmt="of" x:sec="4.1"/>), and &MUST; 467 466 conform to the purpose of content coding defined in this section. 468 467 </t> … … 2526 2525 </t> 2527 2526 <t> 2527 Registration of Content Codings now requires IETF Review 2528 (<xref target="content.coding.registry"/>) 2529 </t> 2530 <t> 2528 2531 Remove the default character encoding for text media types; the default 2529 2532 now is whatever the media type definition says. … … 3082 3085 <section title="Since draft-ietf-httpbis-p3-payload-18" anchor="changes.since.18"> 3083 3086 <t> 3084 None yet. 3087 Closed issues: 3088 <list style="symbols"> 3089 <t> 3090 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/346"/>: 3091 "make IANA policy definitions consistent" 3092 </t> 3093 </list> 3085 3094 </t> 3086 3095 </section> -
draft-ietf-httpbis/latest/p5-range.html
r1566 r1567 460 460 } 461 461 @bottom-center { 462 content: "Expires September 8, 2012";462 content: "Expires September 9, 2012"; 463 463 } 464 464 @bottom-right { … … 509 509 <meta name="dct.creator" content="Reschke, J. F."> 510 510 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest"> 511 <meta name="dct.issued" scheme="ISO8601" content="2012-03-0 7">511 <meta name="dct.issued" scheme="ISO8601" content="2012-03-08"> 512 512 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 513 513 <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."> … … 535 535 </tr> 536 536 <tr> 537 <td class="left">Expires: September 8, 2012</td>537 <td class="left">Expires: September 9, 2012</td> 538 538 <td class="right">J. Mogul</td> 539 539 </tr> … … 592 592 <tr> 593 593 <td class="left"></td> 594 <td class="right">March 7, 2012</td>594 <td class="right">March 8, 2012</td> 595 595 </tr> 596 596 </tbody> … … 620 620 in progress”. 621 621 </p> 622 <p>This Internet-Draft will expire on September 8, 2012.</p>622 <p>This Internet-Draft will expire on September 9, 2012.</p> 623 623 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 624 624 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 789 789 <li>Pointer to specification text</li> 790 790 </ul> 791 <p id="rfc.section.2.1.p.3">Values to be added to this name space are subject to IETF review (<a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>).791 <p id="rfc.section.2.1.p.3">Values to be added to this name space require IETF Review (see <a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>). 792 792 </p> 793 793 <p id="rfc.section.2.1.p.4">The registry itself is maintained at <<a href="http://www.iana.org/assignments/http-range-specifiers">http://www.iana.org/assignments/http-range-specifiers</a>>. -
draft-ietf-httpbis/latest/p5-range.xml
r1566 r1567 386 386 </t> 387 387 <t> 388 Values to be added to this name space are subject to IETF review389 ( <xref target="RFC5226" x:fmt="," x:sec="4.1"/>).388 Values to be added to this name space require IETF Review 389 (see <xref target="RFC5226" x:fmt="," x:sec="4.1"/>). 390 390 </t> 391 391 <t> -
draft-ietf-httpbis/latest/p6-cache.html
r1564 r1567 463 463 } 464 464 @bottom-center { 465 content: "Expires September 7, 2012";465 content: "Expires September 9, 2012"; 466 466 } 467 467 @bottom-right { … … 511 511 <meta name="dct.creator" content="Reschke, J. F."> 512 512 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest"> 513 <meta name="dct.issued" scheme="ISO8601" content="2012-03-0 6">513 <meta name="dct.issued" scheme="ISO8601" content="2012-03-08"> 514 514 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 515 515 <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."> … … 537 537 </tr> 538 538 <tr> 539 <td class="left">Expires: September 7, 2012</td>539 <td class="left">Expires: September 9, 2012</td> 540 540 <td class="right">J. Mogul</td> 541 541 </tr> … … 602 602 <tr> 603 603 <td class="left"></td> 604 <td class="right">March 6, 2012</td>604 <td class="right">March 8, 2012</td> 605 605 </tr> 606 606 </tbody> … … 632 632 in progress”. 633 633 </p> 634 <p>This Internet-Draft will expire on September 7, 2012.</p>634 <p>This Internet-Draft will expire on September 9, 2012.</p> 635 635 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 636 636 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1510 1510 <li>Pointer to specification text</li> 1511 1511 </ul> 1512 <p id="rfc.section.3.2.3.p.9">Values to be added to this name space are subject to IETF review (<a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>).1512 <p id="rfc.section.3.2.3.p.9">Values to be added to this name space require IETF Review (see <a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>). 1513 1513 </p> 1514 1514 <p id="rfc.section.3.2.3.p.10">The registry itself is maintained at <<a href="http://www.iana.org/assignments/http-cache-directives">http://www.iana.org/assignments/http-cache-directives</a>>. … … 1696 1696 <li>Pointer to specification text</li> 1697 1697 </ul> 1698 <p id="rfc.section.3.6.8.p.3">Values to be added to this name space are subject to IETF review (<a href="#RFC5226" id="rfc.xref.RFC5226.2"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>).1698 <p id="rfc.section.3.6.8.p.3">Values to be added to this name space require IETF Review (see <a href="#RFC5226" id="rfc.xref.RFC5226.2"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>). 1699 1699 </p> 1700 1700 <p id="rfc.section.3.6.8.p.4">The registry itself is maintained at <<a href="http://www.iana.org/assignments/http-warn-codes">http://www.iana.org/assignments/http-warn-codes</a>>. -
draft-ietf-httpbis/latest/p6-cache.xml
r1564 r1567 1639 1639 </t> 1640 1640 <t> 1641 Values to be added to this name space are subject to IETF review (<xref1641 Values to be added to this name space require IETF Review (see <xref 1642 1642 target="RFC5226" x:fmt="," x:sec="4.1"/>). 1643 1643 </t> … … 1983 1983 </t> 1984 1984 <t> 1985 Values to be added to this name space are subject to IETF review (<xref1985 Values to be added to this name space require IETF Review (see <xref 1986 1986 target="RFC5226" x:fmt="," x:sec="4.1"/>). 1987 1987 </t> -
draft-ietf-httpbis/latest/p7-auth.html
r1562 r1567 460 460 } 461 461 @bottom-center { 462 content: "Expires September 5, 2012";462 content: "Expires September 9, 2012"; 463 463 } 464 464 @bottom-right { … … 506 506 <meta name="dct.creator" content="Reschke, J. F."> 507 507 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p7-auth-latest"> 508 <meta name="dct.issued" scheme="ISO8601" content="2012-03-0 4">508 <meta name="dct.issued" scheme="ISO8601" content="2012-03-08"> 509 509 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 510 510 <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."> … … 537 537 </tr> 538 538 <tr> 539 <td class="left">Expires: September 5, 2012</td>539 <td class="left">Expires: September 9, 2012</td> 540 540 <td class="right">HP</td> 541 541 </tr> … … 590 590 <tr> 591 591 <td class="left"></td> 592 <td class="right">March 4, 2012</td>592 <td class="right">March 8, 2012</td> 593 593 </tr> 594 594 </tbody> … … 618 618 in progress”. 619 619 </p> 620 <p>This Internet-Draft will expire on September 5, 2012.</p>620 <p>This Internet-Draft will expire on September 9, 2012.</p> 621 621 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 622 622 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 830 830 <li>Notes (optional)</li> 831 831 </ul> 832 <p id="rfc.section.2.3.p.3">Values to be added to this name space are subject to IETF review (<a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>).832 <p id="rfc.section.2.3.p.3">Values to be added to this name space require IETF Review (see <a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>). 833 833 </p> 834 834 <p id="rfc.section.2.3.p.4">The registry itself is maintained at <<a href="http://www.iana.org/assignments/http-authschemes">http://www.iana.org/assignments/http-authschemes</a>>. -
draft-ietf-httpbis/latest/p7-auth.xml
r1562 r1567 477 477 </t> 478 478 <t> 479 Values to be added to this name space are subject to IETF review480 ( <xref target="RFC5226" x:fmt="," x:sec="4.1"/>).479 Values to be added to this name space require IETF Review 480 (see <xref target="RFC5226" x:fmt="," x:sec="4.1"/>). 481 481 </t> 482 482 <t>
Note: See TracChangeset
for help on using the changeset viewer.