MhasIANA Registered

MIME: audio/mhas
Extensions: —
{
  "full": "audio/mhas",
  "type": "audio",
  "subtype": "mhas",
  "extensions": [],
  "iana": {
    "template_url": "https://www.iana.org/assignments/media-types/audio/mhas",
    "encoding_considerations": "Files are encoded binary MHAS audio packets in the MPEG-H Audio \n   Stream (MHAS) format as defined in ISO/IEC 23008-3.\n\n   Files shall be transmitted without CR/LF conversion, 7-bit \n   stripping, or any other modification to the binary data.\n\n   For use over the Internet, it is assumed that lower layers take \n   care of transmission errors, so audio/mhas data may include frames \n   without the optional cyclic redundancy check (CRC).\n\nSecurity considerations: MPEG-H 3D Audio is a tagged data format and \n   does not employ executable content. Some tags are available for \n   private use (e.g. the Data Stream Element). As such, arbitrary \n   material could potentially be transferred in the MPEG-H 3D Audio \n   stream, including executable content. Tagged data containing \n   executable content should never be sent and must not be executed \n   if it is received.\n\n   Note: The requirement that such content must not be executed on \n   receipt is especially important since situations exist where \n   content will be generated independently and therefore could \n   contain executable content that the sender or receiver is unaware \n   of.\n\n   It is the responsibility of the decoder/player client to respect \n   and apply appropriate file security and protection against any \n   potential malicious content.\n\n   The decoder/player needs to have access to sufficient memory for \n   storing the data obtained from decoding an MPEG-H 3D Audio stream.\n\n   audio/mhas objects are not signed or encrypted internally. \n   External security mechanisms must be employed to ensure content \n   confidentiality and integrity.\n\nInteroperability considerations: The MPEG-H 3D Audio codec technology \n   is specified in ISO/IEC 23008-3. Implementations of the MPEG-H 3D \n   Audio technology have reference software for reading and writing \n   the file format and are available for a variety of computer \n   platforms.\n\nPublished specification: ISO/IEC 23008-3\n\nApplications which use this media: MPEG-H 3D Audio is device, \n   platform, and vendor neutral and is supported by a wide range of \n   encoders and decoders/players, for example for Multimedia, HLS \n   IETF HTTP Live Streaming, and MPEG-DASH.\n\nFragment identifier considerations: N/A\n\nRestrictions on usage: N/A",
    "security_considerations": "does not employ executable content. Some tags are available for \n   private use (e.g. the Data Stream Element). As such, arbitrary \n   material could potentially be transferred in the MPEG-H 3D Audio \n   stream, including executable content. Tagged data containing \n   executable content should never be sent and must not be executed \n   if it is received.\n\n   Note: The requirement that such content must not be executed on \n   receipt is especially important since situations exist where \n   content will be generated independently and therefore could \n   contain executable content that the sender or receiver is unaware \n   of.\n\n   It is the responsibility of the decoder/player client to respect \n   and apply appropriate file security and protection against any \n   potential malicious content.\n\n   The decoder/player needs to have access to sufficient memory for \n   storing the data obtained from decoding an MPEG-H 3D Audio stream.\n\n   audio/mhas objects are not signed or encrypted internally. \n   External security mechanisms must be employed to ensure content \n   confidentiality and integrity.\n\nInteroperability considerations: The MPEG-H 3D Audio codec technology \n   is specified in ISO/IEC 23008-3. Implementations of the MPEG-H 3D \n   Audio technology have reference software for reading and writing \n   the file format and are available for a variety of computer \n   platforms.\n\nPublished specification: ISO/IEC 23008-3\n\nApplications which use this media: MPEG-H 3D Audio is device, \n   platform, and vendor neutral and is supported by a wide range of \n   encoders and decoders/players, for example for Multimedia, HLS \n   IETF HTTP Live Streaming, and MPEG-DASH.\n\nFragment identifier considerations: N/A\n\nRestrictions on usage: N/A",
    "interoperability_considerations": "is specified in ISO/IEC 23008-3. Implementations of the MPEG-H 3D \n   Audio technology have reference software for reading and writing \n   the file format and are available for a variety of computer \n   platforms.\n\nPublished specification: ISO/IEC 23008-3\n\nApplications which use this media: MPEG-H 3D Audio is device, \n   platform, and vendor neutral and is supported by a wide range of \n   encoders and decoders/players, for example for Multimedia, HLS \n   IETF HTTP Live Streaming, and MPEG-DASH.\n\nFragment identifier considerations: N/A\n\nRestrictions on usage: N/A",
    "additional_information": "1. Deprecated alias names for this type: N/A\n\n   2. Magic number(s): Receivers can search for the following \n      syncword within the binary data stream: mpeghAudioStreamPacket()\n      0xC001A5 (24bit sequence).\n\n   3. File extension(s): .mhas\n\n   4. Macintosh file type code: N/A\n\n   5. Object Identifiers: N/A\n\nGeneral Comments: N/A",
    "intended_usage": "common",
    "template_text": "[omitted]"
  }
}