📡 ToastRFC
HomeRFC 9112

§12 IANA Considerations RFC 9112

Tap any MUST / SHOULD / MAY for what it means. Chips link cited RFCs and glossary terms.

§12 IANA Considerations

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

§12.1 Field Name Registration

IANA has added the following field names to the "Hypertext Transfer Protocol (HTTP) Field Name Registry" at , as described in HTTP.

Field Name  |  Status  |  Section  |  Comments
Close  |  permanent  |  9.6  |  (reserved)
MIME-Version  |  permanent  |  B.1  |  
Transfer-Encoding  |  permanent  |  6.1  |  

§12.2 Media Type Registration

IANA has updated the "Media Types" registry at with the registration information in Sections 10.1 and 10.2 for the media types "message/http" and "application/http", respectively.

§12.3 Transfer Coding Registration

IANA has updated the "HTTP Transfer Coding Registry" at with the registration procedure of Section 7.3 and the content coding names summarized in the table below.

Name  |  Description  |  Section
chunked  |  Transfer in a series of chunks  |  7.1
compress  |  UNIX "compress" data format Welch  |  7.2
deflate  |  "deflate" compressed data (RFC1951) inside the "zlib" data format (RFC1950)  |  7.2
gzip  |  GZIP file format RFC1952  |  7.2
trailers  |  (reserved)  |  12.3
x-compress  |  Deprecated (alias for compress)  |  7.2
x-gzip  |  Deprecated (alias for gzip)  |  7.2
cites RFC 1950cites RFC 1951cites RFC 1952

Note: the coding name "trailers" is reserved because its use would conflict with the keyword "trailers" in the TE header field (HTTP).

§12.4 ALPN Protocol ID Registration

IANA has updated the "TLS Application-Layer Protocol Negotiation (ALPN) Protocol IDs" registry at with the registration below:

Protocol  |  Identification Sequence  |  Reference
HTTP/1.1  |  0x68 0x74 0x74 0x70 0x2f 0x31 0x2e 0x31 ("http/1.1")  |  RFC 9112