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.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.