Ignore:
Timestamp:
Aug 7, 2009, 7:18:03 AM (10 years ago)
Author:
julian.reschke@…
Message:

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

File:
1 edited

Legend:

Unmodified
Added
Removed
  • 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>
Note: See TracChangeset for help on using the changeset viewer.