Skip to main content

5. IANA Considerations

5.1 Range Unit Registry​

The "HTTP Range Unit Registry" defines the namespace for the range unit names and refers to their corresponding specifications. The registry has been created and is now maintained at http://www.iana.org/assignments/http-parameters/.

5.1.1 Procedure​

Registration of an HTTP Range Unit MUST include the following fields:

  • Name
  • Description
  • Pointer to specification text

Values to be added to this namespace require IETF Review (see [RFC5226], Section 4.1).

5.1.2 Registrations​

The initial range unit registry contains the registrations below:

Range Unit NameDescriptionReference
bytesa range of octetsSection 2.1
nonereserved as keyword, indicating no ranges are supportedSection 2.3

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

5.2 Status Code Registration​

The "Hypertext Transfer Protocol (HTTP) Status Code Registry" located at http://www.iana.org/assignments/http-status-codes has been updated to include the registrations below:

ValueDescriptionReference
206Partial ContentSection 4.1
416Range Not SatisfiableSection 4.4

5.3 Header Field Registration​

HTTP header fields are registered within the "Message Headers" registry maintained at http://www.iana.org/assignments/message-headers/.

This document defines the following HTTP header fields, so their associated registry entries have been updated according to the permanent registrations below (see [BCP90]):

Header Field NameProtocolStatusReference
Accept-RangeshttpstandardSection 2.3
Content-RangehttpstandardSection 4.2
If-RangehttpstandardSection 3.2
RangehttpstandardSection 3.1

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

5.4 Internet Media Type Registration​

IANA maintains the registry of Internet media types [BCP13] at http://www.iana.org/assignments/media-types/.

This document serves as the specification for the Internet media type "multipart/byteranges". The following has been registered with IANA.

5.4.1 Internet Media Type multipart/byteranges​

  • Type name: multipart
  • Subtype name: byteranges
  • Required parameters: boundary
  • Optional parameters: N/A
  • Encoding considerations: only "7bit", "8bit", or "binary" are permitted
  • Security considerations: see Section 6
  • Interoperability considerations: N/A
  • Published specification: This specification (see Appendix A).
  • Applications that use this media type: HTTP components supporting multiple ranges in a single request.
  • Fragment identifier considerations: N/A
  • Additional information:
    • Deprecated alias names for this type: N/A
    • Magic number(s): N/A
    • File extension(s): N/A
    • Macintosh file type code(s): N/A
  • Person and email address to contact for further information: See Authors' Addresses section.
  • Intended usage: COMMON
  • Restrictions on usage: N/A
  • Author: See Authors' Addresses section.
  • Change controller: IESG