MIME Type Registrations for 3rd Generation Partnership Project (3GPP) Multimedia files
RFC - Proposed Standard
(July 2004; No errata)
Updated by RFC 6381
Was draft-singer-avt-3gpp-mime (individual in tsv area)
|Formats||plain text pdf htmlized bibtex|
|Document shepherd||No shepherd assigned|
|This information refers to IESG processing after the RFC was initially published:|
|IESG||IESG state||RFC 3839 (Proposed Standard)|
|Responsible AD||Alexey Melnikov|
Magnus Westerlund has agreed to serve as the document shepherd.
Note that this document is obsoleted by 3GPP TS 26.244 V8.1.0.
|Send notices email@example.com, firstname.lastname@example.org|
Network Working Group R. Castagno Request for Comments: 3839 Nokia Mobile Phones Category: Standards Track D. Singer Apple Computer, Inc. July 2004 MIME Type Registrations for 3rd Generation Partnership Project (3GPP) Multimedia files Status of this Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (2004). Abstract 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. 1. Introduction The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14, RFC 2119 [RFC2119]. The third-generation partnership project (3GPP) for third-generation cellular telephony has defined a standard file format to contain audio/visual sequences which may be downloaded to cellular phones [3GPP]. At the time of writing, the 3GPP file format (3GP) can contain H.263 or MPEG-4 video, and AMR Narrow-band speech, AMR wide- band speech, or AAC audio, and 3GPP timed text. Within the file, as with all files in the 'ISO' family, there is an intrinsic file-type box, which identifies those specifications to which the file complies, and which players (possibly compliant with only one specification) are permitted by the content author to play the file. This identification is through four-letter 'brands'. Castagno & Singer Standards Track [Page 1] RFC 3839 MIME Type Registrations for 3GPP July 2004 Files identified by the MIME [MIME1] type defined here MUST contain a brand defined in a standard issued by 3GPP that can apply to 3GPP files, in their compatible brands list. The MIME types defined here are needed to correctly identify such files when they are served over HTTP, included in multi-part documents, or used in other places where MIME types are used. 2. Security Considerations The 3GPP file format may contain audio, video, and displayable text data. There is currently no provision for 'active' elements (such as scripts) of any kind. Clearly it is possible to author malicious files which attempt to call for an excessively large picture size, high sampling-rate audio etc. However, clients can and usually do protect themselves against this kind of attack. It should be noted that selected metadata fields may encompass information partly intended to protect the media against unauthorized use or distribution. In this case, the intention is that alteration or removal of the data in the field would be treated as an offense under national agreements based on World Intellectual Property Organization (WIPO) treaties. 3GPP files have an extensible structure, so that it is theoretically possible that metadata fields or media formats could be defined in the future which could be used to induce particular actions on the part of the recipient, thus presenting additional security risks. However, this type of capability is currently not supported in the referenced specification. There is no current provision in the standards for encryption, signing, or authentication of these file formats. 3. MIME Types This registration applies to all files defined as using the '3GP' file format and identified with a suitable brand in a 3GPP specification. The usual file suffix for all these files is ".3gp". 3.1. Files with audio but no video The type "audio/3gpp" may be used for files containing audio but no visual presentation (neither video nor timed text, for example). Castagno & Singer Standards Track [Page 2] RFC 3839 MIME Type Registrations for 3GPP July 2004 To: email@example.com Subject: Registration of Standard MIME media type audio/3gpp MIME media type name: audio MIME subtype name: 3gpp Required parameters: none Optional parameters: none Ongoing work related to this registration may introduce new optional parameters. One example area of effort may introduce aShow full document text