rfc-3839

MIME Type Registrations for 3rd Generation Partnership Project (3GPP) Multimedia files

R. Castagno, D. Singer
date2004-07 streamIETF wgnon working group statusPROPOSED STANDARD pages7 canonicalhttps://www.rfc-editor.org/rfc/rfc3839 doi10.17487/RFC3839
This document serves to register and document the standard MIME types associated with the 3GPP multimedia file format, which is part of the family based on the ISO Media File Format. [STANDARDS-TRACK]

updated by

Extracted elements (14)

design-rationale §1

Separate MIME types are registered for audio-only (audio/3gpp) versus any content (video/3gpp) to allow correct content negotiation and identification when files are served over HTTP or included in multi-part documents, without requiring examination of file contents.

interoperability-note §3.2

It is valid to serve an audio-only 3GPP file as video/3gpp; the video/3gpp type is valid for all 3GPP files regardless of content type.

interoperability-note §3.1

The audio/3gpp and video/3gpp MIME types are used only for files; separate MIME types and RTP payload formats are used for real-time transfer (e.g., RFC 2429 for H.263 video, RFC 3267 for AMR audio).

rtp, realtime

normative-requirement §1 MUST

Files identified by the MIME types defined in this document MUST contain a brand defined in a standard issued by 3GPP that can apply to 3GPP files, in their compatible brands list.

normative-requirement §3.1 MUST NOT

Files served under the audio/3gpp type MUST NOT contain any visual material, including 3GPP timed text which is considered visual material.

normative-requirement §3.1 MUST

The file-type box MUST occur first in the file, and MUST contain a 3GPP brand in its compatible brands list. This applies to both audio/3gpp and video/3gpp files.

normative-requirement §3.1 MAY

The type audio/3gpp MAY be used for files containing audio but no visual presentation. Serving audio-only files as video/3gpp is also valid.

protocol-element §3.1

3GPP files must be transmitted in a binary-safe encoding without CR/LF conversion or 7-bit stripping; base64 is specified as a suitable encoding for MIME transport.

protocol-element §1

The 3GP file format is based on the ISO Media File Format and contains an intrinsic file-type box that identifies specifications the file complies with via four-letter 'brands'. At the time of writing, supported codecs include H.263 or MPEG-4 video, AMR Narrow-band, AMR Wide-band speech, AAC audio, and 3GPP timed text.

registry §3.1

Registers the MIME type audio/3gpp for 3GPP multimedia files containing audio but no visual presentation. The preferred file extension is .3gp and the Macintosh file type code is '3gpp'.

registry

registry §3.2

Registers the MIME type video/3gpp for all 3GPP multimedia files, including audio-only files. The preferred file extension is .3gp and the Macintosh file type code is '3gpp'.

registry

security-consideration §2

3GPP files have an extensible structure, so future metadata fields or media formats could theoretically be defined to induce actions on recipients, presenting additional security risks not present in the current specification. There is no current provision for encryption, signing, or authentication.

security, crypto

security-consideration §2

Selected metadata fields may contain DRM or rights management information; alteration or removal of such data could constitute an offense under national agreements based on WIPO treaties.

security

security-consideration §2

The 3GPP file format currently has no provision for active elements such as scripts, limiting the attack surface, though malicious files could request excessively large picture sizes or high sampling-rate audio.

security