18. IANA Considerations

The change controller for the following registrations is: "IETF ([email protected]) - Internet Engineering Task Force".

18.1. URI Scheme Registration

IANA has updated the "Uniform Resource Identifier (URI) Schemes" registry [BCP35] at \https://www.iana.org/assignments/uri-schemes/\`` with the permanent schemes listed in Table 2 in Section 4.2.

18.2. Method Registration

IANA has updated the "Hypertext Transfer Protocol (HTTP) Method Registry" at \https://www.iana.org/assignments/http-methods\`` with the registration procedure of Section 16.1.1 and the method names summarized in the table below.

Method	Safe	Idempotent	Section
CONNECT	no	no	9.3.6
DELETE	no	yes	9.3.5
GET	yes	yes	9.3.1
HEAD	yes	yes	9.3.2
OPTIONS	yes	yes	9.3.7
POST	no	no	9.3.3
PUT	no	yes	9.3.4
TRACE	yes	yes	9.3.8
*	no	no	18.2

The method name "" is reserved because using "" as a method name would conflict with its usage as a wildcard in some fields (e.g., "Access-Control-Request-Method").

18.3. Status Code Registration

IANA has updated the "Hypertext Transfer Protocol (HTTP) Status Code Registry" at \https://www.iana.org/assignments/http-status-codes\`` with the registration procedure of Section 16.2.1 and the status code values summarized in the table below.

Value	Description	Section
100	Continue	15.2.1
101	Switching Protocols	15.2.2
200	OK	15.3.1
201	Created	15.3.2
202	Accepted	15.3.3
203	Non-Authoritative Information	15.3.4
204	No Content	15.3.5
205	Reset Content	15.3.6
206	Partial Content	15.3.7
300	Multiple Choices	15.4.1
301	Moved Permanently	15.4.2
302	Found	15.4.3
303	See Other	15.4.4
304	Not Modified	15.4.5
305	Use Proxy	15.4.6
306	(Unused)	15.4.7
307	Temporary Redirect	15.4.8
308	Permanent Redirect	15.4.9
400	Bad Request	15.5.1
401	Unauthorized	15.5.2
402	Payment Required	15.5.3
403	Forbidden	15.5.4
404	Not Found	15.5.5
405	Method Not Allowed	15.5.6
406	Not Acceptable	15.5.7
407	Proxy Authentication Required	15.5.8
408	Request Timeout	15.5.9
409	Conflict	15.5.10
410	Gone	15.5.11
411	Length Required	15.5.12
412	Precondition Failed	15.5.13
413	Content Too Large	15.5.14
414	URI Too Long	15.5.15
415	Unsupported Media Type	15.5.16
416	Range Not Satisfiable	15.5.17
417	Expectation Failed	15.5.18
418	(Unused)	15.5.19
421	Misdirected Request	15.5.20
422	Unprocessable Content	15.5.21
426	Upgrade Required	15.5.22
500	Internal Server Error	15.6.1
501	Not Implemented	15.6.2
502	Bad Gateway	15.6.3
503	Service Unavailable	15.6.4
504	Gateway Timeout	15.6.5
505	HTTP Version Not Supported	15.6.6

18.4. Field Name Registration

This specification updates the HTTP-related aspects of the existing registration procedures for message header fields defined in [RFC3864]. It replaces the old procedure in relation to HTTP by defining a new registration procedure and moving HTTP field definitions to a separate registry.

IANA has created a new registry as outlined in Section 16.3.1, titled "Hypertext Transfer Protocol (HTTP) Field Name Registry".

IANA has moved all entries with the protocol 'http' from the "Permanent Message Header Field Names" and "Provisional Message Header Field Names" registries (see \https://www.iana.org/assignments/message-headers/\``) to this registry.

Major field names include: Accept, Accept-Charset, Accept-Encoding, Accept-Language, Accept-Ranges, Allow, Authentication-Info, Authorization, Connection, Content-Encoding, Content-Language, Content-Length, Content-Location, Content-Range, Content-Type, Date, ETag, Expect, From, Host, If-Match, If-Modified-Since, If-None-Match, If-Range, If-Unmodified-Since, Last-Modified, Location, Max-Forwards, Proxy-Authenticate, Proxy-Authentication-Info, Proxy-Authorization, Range, Referer, Retry-After, Server, TE, Trailer, Upgrade, User-Agent, Vary, Via, WWW-Authenticate, and others.

The field name "*" is reserved because using that name as an HTTP header field might conflict with its special semantics in the Vary header field (Section 12.5.5).

18.5. Authentication Scheme Registration

IANA has updated the "Hypertext Transfer Protocol (HTTP) Authentication Scheme Registry" at \https://www.iana.org/assignments/http-authschemes\`` with the registration procedure of Section 16.4.1 and the authentication schemes described in Section 11.

18.6. Content Coding Registration

IANA has updated the "HTTP Content Coding Registry" at \https://www.iana.org/assignments/http-parameters/\`` with the registration procedure of Section 16.6.1 and the content coding names described in Section 8.4.1.

Major content codings include:

• compress
• deflate
• gzip
• x-compress
• x-gzip

18.7. Range Unit Registration

IANA has updated the "HTTP Range Unit Registry" at \https://www.iana.org/assignments/http-parameters/\`` with the registration procedure of Section 16.5.1.

Registered range units:

• bytes (see Section 14.1.2)
• none (reserved in Section 14.3)

18.8. Media Type Registration

IANA has updated the "Media Types" registry at \https://www.iana.org/assignments/media-types\`` with the registration information for the media type multipart/byteranges defined in Section 14.6.

18.9. Port Registration

IANA has updated the "Service Name and Transport Protocol Port Number Registry" at \https://www.iana.org/assignments/service-names-port-numbers/\`` with the port number registrations described in Section 4.2.

Registered ports:

• HTTP: Port 80/tcp
• HTTPS: Port 443/tcp

18.10. Upgrade Token Registration

IANA has updated the "Hypertext Transfer Protocol (HTTP) Upgrade Token Registry" at \https://www.iana.org/assignments/http-upgrade-tokens\`` with the registration procedure of Section 16.7 and the upgrade token "HTTP" described in Section 7.8.