Ignore:
Timestamp:
Aug 7, 2009, 7:18:03 AM (11 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/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>
Note: See TracChangeset for help on using the changeset viewer.