(registered 2021-04-28) Media type name: application Media subtype name: 3gppHal+json Required parameters: N/A Optional parameters: N/A Encoding considerations: binary As indicated in https://tools.ietf.org/html/draft-kelly-json-hal-08, a HAL Document uses the format described in [RFC4627] and has the media type "application/hal+json". The binary content-transfer-encoding must be used. Security considerations: See IETF RFC 8259, section 12. This media type does not allow for executable content. Interoperability considerations: See IETF RFC 8259 Published specification: 3GPP TS 3GPP TS 29.501 "5G System; Principles and Guidelines for Services Definition; Stage 3", version 15.8.0, available via https://www.3gpp.org/ftp/Specs/archive/29_series/29.501/29501-f80.zip. Applications which use this media: This media type is intended as to be used as HTTP body by 3GPP applications supporting the 3GPP hypermedia format as defined in the referenced specifications. Fragment identifier considerations: N/A Restrictions on usage: N/A Additional information: 1. Deprecated alias names for this type: N/A 2. Magic number(s): N/A 3. File extension(s): N/A 4. Macintosh file type code: N/A 5. Object Identifiers: N/A General Comments: This media type registration in the standards tree is registered by 3GPP, a recognized standards-related organization. It is used over internal 3GPP interfaces and on interfaces to external organizations. The basic 3GPP hypermedia format is derived from the Hypertext Application Language (HAL). The HAL media type is a popular format for representing API responses. HAL has been initially specified in an expired internet draft available at "https://tools.ietf.org/html/draft-kelly-json-hal-08". Person to contact for further information: 1. Name: Ulrich Wiehe 2. Email: Ulrich.wiehe&nokia.com Intended usage: Common Commonly used over interfaces supporting 3GPP-based authentication. Author/Change controller: 3GPP Ulrich Wiehe Ulrich.wiehe&nokia.com