* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Changeset 670


Ignore:
Timestamp:
2009-08-07 07:18:03 (5 years ago)
Author:
julian.reschke@gmx.de
Message:

Rephrase registration procedures for Transfer/Content? Codings in terms of RFC5226, requiring Expert Review & Specification (see #188)

Location:
draft-ietf-httpbis/latest
Files:
5 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.html

    r664 r670  
    394394      <meta name="DC.Creator" content="Reschke, J. F."> 
    395395      <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest"> 
    396       <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-08-06"> 
     396      <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-08-07"> 
    397397      <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616"> 
    398398      <meta name="DC.Description.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 1 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 1 provides an overview of HTTP and its associated terminology, defines the &#34;http&#34; and &#34;https&#34; Uniform Resource Identifier (URI) schemes, defines the generic message syntax and parsing requirements for HTTP message frames, and describes general security concerns for implementations."> 
     
    425425         </tr> 
    426426         <tr> 
    427             <td class="header left">Expires: February 7, 2010</td> 
     427            <td class="header left">Expires: February 8, 2010</td> 
    428428            <td class="header right">HP</td> 
    429429         </tr> 
     
    478478         <tr> 
    479479            <td class="header left"></td> 
    480             <td class="header right">August 6, 2009</td> 
     480            <td class="header right">August 7, 2009</td> 
    481481         </tr> 
    482482      </table> 
     
    502502      <p>The list of Internet-Draft Shadow Directories can be accessed at &lt;<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>&gt;. 
    503503      </p> 
    504       <p>This Internet-Draft will expire in February 7, 2010.</p> 
     504      <p>This Internet-Draft will expire in February 8, 2010.</p> 
    505505      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 
    506506      <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p> 
     
    575575                     <li class="tocline1">2.10.2&nbsp;&nbsp;&nbsp;<a href="#transfer.codings">Transfer Codings</a><ul class="toc"> 
    576576                           <li class="tocline1">2.10.2.1&nbsp;&nbsp;&nbsp;<a href="#chunked.transfer.encoding">Chunked Transfer Coding</a></li> 
     577                           <li class="tocline1">2.10.2.2&nbsp;&nbsp;&nbsp;<a href="#transfer.coding.registry">Transfer Coding Registry</a></li> 
    577578                        </ul> 
    578579                     </li> 
     
    14591460         of message-bodies is the difficulty in determining the exact body length (<a href="#message.length" title="Message Length">Section&nbsp;2.7.4</a>), or the desire to encrypt data over a shared transport. 
    14601461      </p> 
    1461       <p id="rfc.section.2.10.2.p.8">The Internet Assigned Numbers Authority (IANA) acts as a registry for transfer-coding value tokens. Initially, the registry 
    1462          contains the following tokens: "chunked" (<a href="#chunked.transfer.encoding" title="Chunked Transfer Coding">Section&nbsp;2.10.2.1</a>), "gzip", "compress", and "deflate" (<a href="p3-payload.html#content.codings" title="Content Codings">Section 2.2</a> of <a href="#Part3" id="rfc.xref.Part3.7"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>). 
    1463       </p> 
    1464       <p id="rfc.section.2.10.2.p.9">New transfer-coding value tokens <em class="bcp14">SHOULD</em> be registered in the same way as new content-coding value tokens (<a href="p3-payload.html#content.codings" title="Content Codings">Section 2.2</a> of <a href="#Part3" id="rfc.xref.Part3.8"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>). 
    1465       </p> 
    1466       <p id="rfc.section.2.10.2.p.10">A server which receives an entity-body with a transfer-coding it does not understand <em class="bcp14">SHOULD</em> return 501 (Not Implemented), and close the connection. A server <em class="bcp14">MUST NOT</em> send transfer-codings to an HTTP/1.0 client. 
     1462      <p id="rfc.section.2.10.2.p.8">A server which receives an entity-body with a transfer-coding it does not understand <em class="bcp14">SHOULD</em> return 501 (Not Implemented), and close the connection. A server <em class="bcp14">MUST NOT</em> send transfer-codings to an HTTP/1.0 client. 
    14671463      </p> 
    14681464      <h4 id="rfc.section.2.10.2.1"><a href="#rfc.section.2.10.2.1">2.10.2.1</a>&nbsp;<a id="chunked.transfer.encoding" href="#chunked.transfer.encoding">Chunked Transfer Coding</a></h4> 
     
    15261522</pre><p id="rfc.section.2.10.2.1.p.9">All HTTP/1.1 applications <em class="bcp14">MUST</em> be able to receive and decode the "chunked" transfer-coding, and <em class="bcp14">MUST</em> ignore chunk-ext extensions they do not understand. 
    15271523      </p> 
     1524      <h4 id="rfc.section.2.10.2.2"><a href="#rfc.section.2.10.2.2">2.10.2.2</a>&nbsp;<a id="transfer.coding.registry" href="#transfer.coding.registry">Transfer Coding Registry</a></h4> 
     1525      <p id="rfc.section.2.10.2.2.p.1">The HTTP Transfer Coding Registry defines the name space for the transfer coding names.</p> 
     1526      <p id="rfc.section.2.10.2.2.p.2">Registrations <em class="bcp14">MUST</em> include the following fields:  
     1527      </p> 
     1528      <ul> 
     1529         <li>Name</li> 
     1530         <li>Description</li> 
     1531         <li>Pointer to specification text</li> 
     1532      </ul> 
     1533      <p id="rfc.section.2.10.2.2.p.3">Values to be added to this name space require expert review and a specification (see "Expert Review" and "Specification Required" 
     1534         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. 
     1535      </p> 
     1536      <p id="rfc.section.2.10.2.2.p.4">The registry itself is maintained at &lt;<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>&gt;. 
     1537      </p> 
    15281538      <h3 id="rfc.section.2.10.3"><a href="#rfc.section.2.10.3">2.10.3</a>&nbsp;<a id="product.tokens" href="#product.tokens">Product Tokens</a></h3> 
    15291539      <p id="rfc.section.2.10.3.p.1">Product tokens are used to allow communicating applications to identify themselves by software name and version. Most fields 
     
    15391549      </p> 
    15401550      <h3 id="rfc.section.2.10.4"><a href="#rfc.section.2.10.4">2.10.4</a>&nbsp;<a id="quality.values" href="#quality.values">Quality Values</a></h3> 
    1541       <p id="rfc.section.2.10.4.p.1">Both transfer codings (TE request header, <a href="#header.te" id="rfc.xref.header.te.3" title="TE">Section&nbsp;3.5</a>) and content negotiation (<a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 4</a> of <a href="#Part3" id="rfc.xref.Part3.9"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) use short "floating point" numbers to indicate the relative importance ("weight") of various negotiable parameters. A weight 
     1551      <p id="rfc.section.2.10.4.p.1">Both transfer codings (TE request header, <a href="#header.te" id="rfc.xref.header.te.3" title="TE">Section&nbsp;3.5</a>) and content negotiation (<a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 4</a> of <a href="#Part3" id="rfc.xref.Part3.7"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) use short "floating point" numbers to indicate the relative importance ("weight") of various negotiable parameters. A weight 
    15421552         is normalized to a real number in the range 0 through 1, where 0 is the minimum and 1 the maximum value. If a parameter has 
    15431553         a quality value of 0, then content with this parameter is `not acceptable' for the client. HTTP/1.1 applications <em class="bcp14">MUST NOT</em> generate more than three digits after the decimal point. User configuration of these values <em class="bcp14">SHOULD</em> also be limited in this fashion. 
     
    22132223      </dl> 
    22142224      <h2 id="rfc.section.4.4"><a href="#rfc.section.4.4">4.4</a>&nbsp;<a id="transfer.coding.registration" href="#transfer.coding.registration">Transfer Coding Registry</a></h2> 
    2215       <p id="rfc.section.4.4.p.1">The registration procedure for HTTP Transfer Codings is now defined by <a href="#transfer.codings" title="Transfer Codings">Section&nbsp;2.10.2</a> of this document. 
     2225      <p id="rfc.section.4.4.p.1">The registration procedure for HTTP Transfer Codings is now defined by <a href="#transfer.coding.registry" title="Transfer Coding Registry">Section&nbsp;2.10.2.2</a> of this document. 
    22162226      </p> 
    22172227      <p id="rfc.section.4.4.p.2">The HTTP Transfer Codings Registry located at &lt;<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>&gt; should be updated with the registration below: 
     
    22222232            <thead> 
    22232233               <tr> 
    2224                   <th>Registry Name</th> 
     2234                  <th>Name</th> 
    22252235                  <th>Description</th> 
    22262236                  <th>Reference</th> 
     
    23842394      <h2 id="rfc.references.2"><a href="#rfc.section.7.2" id="rfc.section.7.2">7.2</a> Informative References 
    23852395      </h2> 
    2386       <table summary="Informative References">                                           
     2396      <table summary="Informative References">                                             
    23872397         <tr> 
    23882398            <td class="reference"><b id="Kri2001">[Kri2001]</b></td> 
     
    24742484            <td class="reference"><b id="RFC4395">[RFC4395]</b></td> 
    24752485            <td class="top"><a title="AT&amp;T Laboratories">Hansen, T.</a>, <a title="Qualcomm, Inc.">Hardie, T.</a>, and <a title="Adobe Systems">L. Masinter</a>, “<a href="http://tools.ietf.org/html/rfc4395">Guidelines and Registration Procedures for New URI Schemes</a>”, BCP&nbsp;115, RFC&nbsp;4395, February&nbsp;2006. 
     2486            </td> 
     2487         </tr> 
     2488         <tr> 
     2489            <td class="reference"><b id="RFC5226">[RFC5226]</b></td> 
     2490            <td class="top"><a title="IBM">Narten, T.</a> and <a title="Google">H. Alvestrand</a>, “<a href="http://tools.ietf.org/html/rfc5226">Guidelines for Writing an IANA Considerations Section in RFCs</a>”, BCP&nbsp;26, RFC&nbsp;5226, May&nbsp;2008. 
    24762491            </td> 
    24772492         </tr> 
     
    25212536      </p> 
    25222537      <p id="rfc.section.A.p.4">The character set of an entity-body <em class="bcp14">SHOULD</em> be labeled as the lowest common denominator of the character codes used within that body, with the exception that not labeling 
    2523          the entity is preferred over labeling the entity with the labels US-ASCII or ISO-8859-1. See <a href="#Part3" id="rfc.xref.Part3.10"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>. 
     2538         the entity is preferred over labeling the entity with the labels US-ASCII or ISO-8859-1. See <a href="#Part3" id="rfc.xref.Part3.8"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>. 
    25242539      </p> 
    25252540      <p id="rfc.section.A.p.5">Additional rules for requirements on parsing and encoding of dates and other potential problems with date encodings include:</p> 
     
    26132628      <p id="rfc.section.B.3.p.2">Transfer-coding and message lengths all interact in ways that required fixing exactly when chunked encoding is used (to allow 
    26142629         for transfer encoding that may not be self delimiting); it was important to straighten out exactly how message lengths are 
    2615          computed. (Sections <a href="#transfer.codings" title="Transfer Codings">2.10.2</a>, <a href="#message.length" title="Message Length">2.7.4</a>, <a href="#header.content-length" id="rfc.xref.header.content-length.3" title="Content-Length">3.2</a>, see also <a href="#Part3" id="rfc.xref.Part3.11"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="#Part5" id="rfc.xref.Part5.1"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a> and <a href="#Part6" id="rfc.xref.Part6.8"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) 
     2630         computed. (Sections <a href="#transfer.codings" title="Transfer Codings">2.10.2</a>, <a href="#message.length" title="Message Length">2.7.4</a>, <a href="#header.content-length" id="rfc.xref.header.content-length.3" title="Content-Length">3.2</a>, see also <a href="#Part3" id="rfc.xref.Part3.9"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="#Part5" id="rfc.xref.Part5.1"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a> and <a href="#Part6" id="rfc.xref.Part6.8"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) 
    26162631      </p> 
    26172632      <p id="rfc.section.B.3.p.3">The use and interpretation of HTTP version numbers has been clarified by <a href="#RFC2145" id="rfc.xref.RFC2145.3"><cite title="Use and Interpretation of HTTP Version Numbers">[RFC2145]</cite></a>. Require proxies to upgrade requests to highest protocol version they support to deal with problems discovered in HTTP/1.0 
     
    30403055         </li> 
    30413056         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/157">http://tools.ietf.org/wg/httpbis/trac/ticket/157</a>&gt;: "IP addresses in URLs" 
     3057         </li> 
     3058         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/188">http://tools.ietf.org/wg/httpbis/trac/ticket/188</a>&gt;: "pick IANA policy (RFC5226) for Transfer Coding / Content Coding" 
    30423059         </li> 
    30433060      </ul> 
     
    32573274                     </ul> 
    32583275                  </li> 
    3259                   <li class="indline1"><em>Part3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.1">1</a>, <a class="iref" href="#rfc.xref.Part3.2">1.2.2</a>, <a class="iref" href="#rfc.xref.Part3.3">1.2.3</a>, <a class="iref" href="#rfc.xref.Part3.4">1.2.3</a>, <a class="iref" href="#rfc.xref.Part3.5">2.8</a>, <a class="iref" href="#rfc.xref.Part3.6">2.9</a>, <a class="iref" href="#rfc.xref.Part3.7">2.10.2</a>, <a class="iref" href="#rfc.xref.Part3.8">2.10.2</a>, <a class="iref" href="#rfc.xref.Part3.9">2.10.4</a>, <a class="iref" href="#Part3"><b>7.1</b></a>, <a class="iref" href="#rfc.xref.Part3.10">A</a>, <a class="iref" href="#rfc.xref.Part3.11">B.3</a><ul class="ind"> 
    3260                         <li class="indline1"><em>Section 2.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.7">2.10.2</a>, <a class="iref" href="#rfc.xref.Part3.8">2.10.2</a></li> 
     3276                  <li class="indline1"><em>Part3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.1">1</a>, <a class="iref" href="#rfc.xref.Part3.2">1.2.2</a>, <a class="iref" href="#rfc.xref.Part3.3">1.2.3</a>, <a class="iref" href="#rfc.xref.Part3.4">1.2.3</a>, <a class="iref" href="#rfc.xref.Part3.5">2.8</a>, <a class="iref" href="#rfc.xref.Part3.6">2.9</a>, <a class="iref" href="#rfc.xref.Part3.7">2.10.4</a>, <a class="iref" href="#Part3"><b>7.1</b></a>, <a class="iref" href="#rfc.xref.Part3.8">A</a>, <a class="iref" href="#rfc.xref.Part3.9">B.3</a><ul class="ind"> 
    32613277                        <li class="indline1"><em>Section 2.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.2">1.2.2</a></li> 
    32623278                        <li class="indline1"><em>Section 3.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.4">1.2.3</a>, <a class="iref" href="#rfc.xref.Part3.5">2.8</a>, <a class="iref" href="#rfc.xref.Part3.6">2.9</a></li> 
    32633279                        <li class="indline1"><em>Section 3.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.3">1.2.3</a></li> 
    3264                         <li class="indline1"><em>Section 4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.9">2.10.4</a></li> 
     3280                        <li class="indline1"><em>Section 4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.7">2.10.4</a></li> 
    32653281                        <li class="indline1"><em>Appendix A</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.1">1</a></li> 
    32663282                     </ul> 
     
    33183334                  <li class="indline1"><em>RFC4288</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC4288.1">4.3</a>, <a class="iref" href="#RFC4288"><b>7.2</b></a></li> 
    33193335                  <li class="indline1"><em>RFC4395</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC4395.1">4.2</a>, <a class="iref" href="#RFC4395"><b>7.2</b></a></li> 
     3336                  <li class="indline1"><em>RFC5226</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5226.1">2.10.2.2</a>, <a class="iref" href="#RFC5226"><b>7.2</b></a><ul class="ind"> 
     3337                        <li class="indline1"><em>Section 4.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5226.1">2.10.2.2</a></li> 
     3338                     </ul> 
     3339                  </li> 
    33203340                  <li class="indline1"><em>RFC5234</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5234.1">1.2</a>, <a class="iref" href="#rfc.xref.RFC5234.2">1.2</a>, <a class="iref" href="#rfc.xref.RFC5234.3">1.2.1</a>, <a class="iref" href="#rfc.xref.RFC5234.4">6</a>, <a class="iref" href="#RFC5234"><b>7.1</b></a><ul class="ind"> 
    33213341                        <li class="indline1"><em>Appendix B.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5234.2">1.2</a></li> 
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r664 r670  
    17951795</t> 
    17961796<t> 
    1797    The Internet Assigned Numbers Authority (IANA) acts as a registry for 
    1798    transfer-coding value tokens. Initially, the registry contains the 
    1799    following tokens: "chunked" (<xref target="chunked.transfer.encoding"/>), 
    1800    "gzip", "compress", and "deflate" (&content-codings;). 
    1801 </t> 
    1802 <t> 
    1803    New transfer-coding value tokens &SHOULD; be registered in the same way 
    1804    as new content-coding value tokens (&content-codings;). 
    1805 </t> 
    1806 <t> 
    18071797   A server which receives an entity-body with a transfer-coding it does 
    18081798   not understand &SHOULD; return 501 (Not Implemented), and close the 
     
    19071897   "chunked" transfer-coding, and &MUST; ignore chunk-ext extensions 
    19081898   they do not understand. 
     1899</t> 
     1900</section> 
     1901 
     1902<section title="Transfer Coding Registry" anchor="transfer.coding.registry"> 
     1903<t> 
     1904   The HTTP Transfer Coding Registry defines the name space for the transfer 
     1905   coding names. 
     1906</t> 
     1907<t> 
     1908   Registrations &MUST; include the following fields: 
     1909   <list style="symbols"> 
     1910     <t>Name</t> 
     1911     <t>Description</t> 
     1912     <t>Pointer to specification text</t> 
     1913   </list> 
     1914</t> 
     1915<t> 
     1916   Values to be added to this name space require expert review and a specification 
     1917   (see "Expert Review" and "Specification Required" in 
     1918   <xref target="RFC5226" x:fmt="of" x:sec="4.1"/>), and &MUST; 
     1919   conform to the purpose of transfer coding defined in this section. 
     1920</t> 
     1921<t> 
     1922   The registry itself is maintained at 
     1923   <eref target="http://www.iana.org/assignments/http-parameters"/>. 
    19091924</t> 
    19101925</section> 
     
    32003215<t> 
    32013216   The registration procedure for HTTP Transfer Codings is now defined 
    3202    by <xref target="transfer.codings"/> of this document. 
     3217   by <xref target="transfer.coding.registry"/> of this document. 
    32033218</t> 
    32043219<t> 
     
    32073222</t> 
    32083223<texttable align="left" suppress-title="true" anchor="iana.transfer.coding.registration.table"> 
    3209    <ttcol>Registry Name</ttcol> 
     3224   <ttcol>Name</ttcol> 
    32103225   <ttcol>Description</ttcol> 
    32113226   <ttcol>Reference</ttcol> 
     
    40394054</reference> 
    40404055 
     4056<reference anchor='RFC5226'> 
     4057  <front> 
     4058    <title>Guidelines for Writing an IANA Considerations Section in RFCs</title> 
     4059    <author initials='T.' surname='Narten' fullname='T. Narten'> 
     4060      <organization>IBM</organization> 
     4061      <address><email>narten@us.ibm.com</email></address> 
     4062    </author> 
     4063    <author initials='H.' surname='Alvestrand' fullname='H. Alvestrand'> 
     4064      <organization>Google</organization> 
     4065      <address><email>Harald@Alvestrand.no</email></address> 
     4066    </author> 
     4067    <date year='2008' month='May' /> 
     4068  </front> 
     4069  <seriesInfo name='BCP' value='26' /> 
     4070  <seriesInfo name='RFC' value='5226' /> 
     4071</reference> 
     4072 
    40414073<reference anchor="RFC5322"> 
    40424074  <front> 
     
    49664998      "IP addresses in URLs" 
    49674999    </t> 
     5000    <t> 
     5001      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/188"/>: 
     5002      "pick IANA policy (RFC5226) for Transfer Coding / Content Coding" 
     5003    </t> 
    49685004  </list> 
    49695005</t> 
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r666 r670  
    462462</t> 
    463463<t> 
    464   The registry itself is maintained at <eref target="http://www.iana.org/assignments/http-methods"/>. 
     464  The registry itself is maintained at <eref target="http://www.iana.org/assignments/http-parameters"/>. 
    465465</t> 
    466466</section> 
  • draft-ietf-httpbis/latest/p3-payload.html

    r668 r670  
    407407      <meta name="DC.Creator" content="Reschke, J. F."> 
    408408      <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p3-payload-latest"> 
    409       <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-08-06"> 
     409      <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-08-07"> 
    410410      <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616"> 
    411411      <meta name="DC.Description.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 3 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 3 defines HTTP message content, metadata, and content negotiation."> 
     
    438438         </tr> 
    439439         <tr> 
    440             <td class="header left">Expires: February 7, 2010</td> 
     440            <td class="header left">Expires: February 8, 2010</td> 
    441441            <td class="header right">HP</td> 
    442442         </tr> 
     
    491491         <tr> 
    492492            <td class="header left"></td> 
    493             <td class="header right">August 6, 2009</td> 
     493            <td class="header right">August 7, 2009</td> 
    494494         </tr> 
    495495      </table> 
     
    515515      <p>The list of Internet-Draft Shadow Directories can be accessed at &lt;<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>&gt;. 
    516516      </p> 
    517       <p>This Internet-Draft will expire in February 7, 2010.</p> 
     517      <p>This Internet-Draft will expire in February 8, 2010.</p> 
    518518      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 
    519519      <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p> 
     
    551551                  </ul> 
    552552               </li> 
    553                <li class="tocline1">2.2&nbsp;&nbsp;&nbsp;<a href="#content.codings">Content Codings</a></li> 
     553               <li class="tocline1">2.2&nbsp;&nbsp;&nbsp;<a href="#content.codings">Content Codings</a><ul class="toc"> 
     554                     <li class="tocline1">2.2.1&nbsp;&nbsp;&nbsp;<a href="#content.coding.registry">Content Coding Registry</a></li> 
     555                  </ul> 
     556               </li> 
    554557               <li class="tocline1">2.3&nbsp;&nbsp;&nbsp;<a href="#media.types">Media Types</a><ul class="toc"> 
    555558                     <li class="tocline1">2.3.1&nbsp;&nbsp;&nbsp;<a href="#canonicalization.and.text.defaults">Canonicalization and Text Defaults</a></li> 
     
    790793         </dd> 
    791794      </dl> 
    792       <p id="rfc.section.2.2.p.9">New content-coding value tokens <em class="bcp14">SHOULD</em> be registered; to allow interoperability between clients and servers, specifications of the content coding algorithms needed 
    793          to implement a new value <em class="bcp14">SHOULD</em> be publicly available and adequate for independent implementation, and conform to the purpose of content coding defined in 
    794          this section. 
     795      <h3 id="rfc.section.2.2.1"><a href="#rfc.section.2.2.1">2.2.1</a>&nbsp;<a id="content.coding.registry" href="#content.coding.registry">Content Coding Registry</a></h3> 
     796      <p id="rfc.section.2.2.1.p.1">The HTTP Content Coding Registry defines the name space for the content coding names.</p> 
     797      <p id="rfc.section.2.2.1.p.2">Registrations <em class="bcp14">MUST</em> include the following fields:  
     798      </p> 
     799      <ul> 
     800         <li>Name</li> 
     801         <li>Description</li> 
     802         <li>Pointer to specification text</li> 
     803      </ul> 
     804      <p id="rfc.section.2.2.1.p.3">Values to be added to this name space require expert review and a specification (see "Expert Review" and "Specification Required" 
     805         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. 
     806      </p> 
     807      <p id="rfc.section.2.2.1.p.4">The registry itself is maintained at &lt;<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>&gt;. 
    795808      </p> 
    796809      <h2 id="rfc.section.2.3"><a href="#rfc.section.2.3">2.3</a>&nbsp;<a id="media.types" href="#media.types">Media Types</a></h2> 
     
    14851498      </div> 
    14861499      <h2 id="rfc.section.6.3"><a href="#rfc.section.6.3">6.3</a>&nbsp;<a id="content.coding.registration" href="#content.coding.registration">Content Coding Registry</a></h2> 
    1487       <p id="rfc.section.6.3.p.1">The registration procedure for HTTP Content Codings is now defined by <a href="#content.codings" title="Content Codings">Section&nbsp;2.2</a> of this document. 
     1500      <p id="rfc.section.6.3.p.1">The registration procedure for HTTP Content Codings is now defined by <a href="#content.coding.registry" title="Content Coding Registry">Section&nbsp;2.2.1</a> of this document. 
    14881501      </p> 
    14891502      <p id="rfc.section.6.3.p.2">The HTTP Content Codings Registry located at &lt;<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>&gt; should be updated with the registrations below: 
     
    14941507            <thead> 
    14951508               <tr> 
    1496                   <th>Registry Name</th> 
     1509                  <th>Name</th> 
    14971510                  <th>Description</th> 
    14981511                  <th>Reference</th> 
     
    16471660      <h2 id="rfc.references.2"><a href="#rfc.section.9.2" id="rfc.section.9.2">9.2</a> Informative References 
    16481661      </h2> 
    1649       <table summary="Informative References">                             
     1662      <table summary="Informative References">                               
    16501663         <tr> 
    16511664            <td class="reference"><b id="BCP97">[BCP97]</b></td> 
     
    17111724            <td class="reference"><b id="RFC4288">[RFC4288]</b></td> 
    17121725            <td class="top"><a title="Sun Microsystems">Freed, N.</a> and <a>J. Klensin</a>, “<a href="http://tools.ietf.org/html/rfc4288">Media Type Specifications and Registration Procedures</a>”, BCP&nbsp;13, RFC&nbsp;4288, December&nbsp;2005. 
     1726            </td> 
     1727         </tr> 
     1728         <tr> 
     1729            <td class="reference"><b id="RFC5226">[RFC5226]</b></td> 
     1730            <td class="top"><a title="IBM">Narten, T.</a> and <a title="Google">H. Alvestrand</a>, “<a href="http://tools.ietf.org/html/rfc5226">Guidelines for Writing an IANA Considerations Section in RFCs</a>”, BCP&nbsp;26, RFC&nbsp;5226, May&nbsp;2008. 
    17131731            </td> 
    17141732         </tr> 
     
    20552073      <p id="rfc.section.E.9.p.1">Closed issues: </p> 
    20562074      <ul> 
    2057          <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/13">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/13</a>&gt;: "Updated reference for language tags" 
     2075         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/13">http://tools.ietf.org/wg/httpbis/trac/ticket/13</a>&gt;: "Updated reference for language tags" 
    20582076         </li> 
    20592077         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/155">http://tools.ietf.org/wg/httpbis/trac/ticket/155</a>&gt;: "Content Sniffing" 
     2078         </li> 
     2079         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/188">http://tools.ietf.org/wg/httpbis/trac/ticket/188</a>&gt;: "pick IANA policy (RFC5226) for Transfer Coding / Content Coding" 
    20602080         </li> 
    20612081      </ul> 
     
    22752295                     </ul> 
    22762296                  </li> 
     2297                  <li class="indline1"><em>RFC5226</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5226.1">2.2.1</a>, <a class="iref" href="#RFC5226"><b>9.2</b></a><ul class="ind"> 
     2298                        <li class="indline1"><em>Section 4.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5226.1">2.2.1</a></li> 
     2299                     </ul> 
     2300                  </li> 
    22772301                  <li class="indline1"><em>RFC5234</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5234.1">1.3</a>, <a class="iref" href="#rfc.xref.RFC5234.2">1.3</a>, <a class="iref" href="#RFC5234"><b>9.1</b></a><ul class="ind"> 
    22782302                        <li class="indline1"><em>Appendix B.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5234.2">1.3</a></li> 
  • draft-ietf-httpbis/latest/p3-payload.xml

    r668 r670  
    526526  </t></list> 
    527527</t> 
    528 <t> 
    529    New content-coding value tokens &SHOULD; be registered; to allow 
    530    interoperability between clients and servers, specifications of the 
    531    content coding algorithms needed to implement a new value &SHOULD; be 
    532    publicly available and adequate for independent implementation, and 
     528 
     529<section title="Content Coding Registry" anchor="content.coding.registry"> 
     530<t> 
     531   The HTTP Content Coding Registry defines the name space for the content 
     532   coding names. 
     533</t> 
     534<t> 
     535   Registrations &MUST; include the following fields: 
     536   <list style="symbols"> 
     537     <t>Name</t> 
     538     <t>Description</t> 
     539     <t>Pointer to specification text</t> 
     540   </list> 
     541</t> 
     542<t> 
     543   Values to be added to this name space require expert review and a specification 
     544   (see "Expert Review" and "Specification Required" in 
     545   <xref target="RFC5226" x:fmt="of" x:sec="4.1"/>), and &MUST; 
    533546   conform to the purpose of content coding defined in this section. 
    534547</t> 
     548<t> 
     549   The registry itself is maintained at 
     550   <eref target="http://www.iana.org/assignments/http-parameters"/>. 
     551</t> 
     552</section> 
     553 
    535554</section> 
    536555 
     
    17021721<t> 
    17031722   The registration procedure for HTTP Content Codings is now defined 
    1704    by <xref target="content.codings"/> of this document. 
     1723   by <xref target="content.coding.registry"/> of this document. 
    17051724</t> 
    17061725<t> 
     
    17091728</t> 
    17101729<texttable align="left" suppress-title="true" anchor="iana.content.coding.registration.table"> 
    1711    <ttcol>Registry Name</ttcol> 
     1730   <ttcol>Name</ttcol> 
    17121731   <ttcol>Description</ttcol> 
    17131732   <ttcol>Reference</ttcol> 
     
    24892508</reference> 
    24902509 
     2510<reference anchor='RFC5226'> 
     2511  <front> 
     2512    <title>Guidelines for Writing an IANA Considerations Section in RFCs</title> 
     2513    <author initials='T.' surname='Narten' fullname='T. Narten'> 
     2514      <organization>IBM</organization> 
     2515      <address><email>narten@us.ibm.com</email></address> 
     2516    </author> 
     2517    <author initials='H.' surname='Alvestrand' fullname='H. Alvestrand'> 
     2518      <organization>Google</organization> 
     2519      <address><email>Harald@Alvestrand.no</email></address> 
     2520    </author> 
     2521    <date year='2008' month='May' /> 
     2522  </front> 
     2523  <seriesInfo name='BCP' value='26' /> 
     2524  <seriesInfo name='RFC' value='5226' /> 
     2525</reference> 
     2526 
    24912527<reference anchor="RFC5322"> 
    24922528  <front> 
     
    30883124  <list style="symbols">  
    30893125    <t> 
    3090       <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/13"/>: 
     3126      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/13"/>: 
    30913127      "Updated reference for language tags" 
    30923128    </t> 
     
    30943130      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/155"/>: 
    30953131      "Content Sniffing" 
     3132    </t> 
     3133    <t> 
     3134      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/188"/>: 
     3135      "pick IANA policy (RFC5226) for Transfer Coding / Content Coding" 
    30963136    </t> 
    30973137  </list> 
Note: See TracChangeset for help on using the changeset viewer.