Changeset 670 for draft-ietf-httpbis/latest/p1-messaging.xml
- Timestamp:
- 07/08/09 14:18:03 (13 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.xml
r664 r670 1795 1795 </t> 1796 1796 <t> 1797 The Internet Assigned Numbers Authority (IANA) acts as a registry for1798 transfer-coding value tokens. Initially, the registry contains the1799 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 way1804 as new content-coding value tokens (&content-codings;).1805 </t>1806 <t>1807 1797 A server which receives an entity-body with a transfer-coding it does 1808 1798 not understand &SHOULD; return 501 (Not Implemented), and close the … … 1907 1897 "chunked" transfer-coding, and &MUST; ignore chunk-ext extensions 1908 1898 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"/>. 1909 1924 </t> 1910 1925 </section> … … 3200 3215 <t> 3201 3216 The registration procedure for HTTP Transfer Codings is now defined 3202 by <xref target="transfer.coding s"/> of this document.3217 by <xref target="transfer.coding.registry"/> of this document. 3203 3218 </t> 3204 3219 <t> … … 3207 3222 </t> 3208 3223 <texttable align="left" suppress-title="true" anchor="iana.transfer.coding.registration.table"> 3209 <ttcol> RegistryName</ttcol>3224 <ttcol>Name</ttcol> 3210 3225 <ttcol>Description</ttcol> 3211 3226 <ttcol>Reference</ttcol> … … 4039 4054 </reference> 4040 4055 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 4041 4073 <reference anchor="RFC5322"> 4042 4074 <front> … … 4966 4998 "IP addresses in URLs" 4967 4999 </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> 4968 5004 </list> 4969 5005 </t>
Note: See TracChangeset
for help on using the changeset viewer.