MIME Type Registrations for 3GPP2 Multimedia Files
RFC 4393

Document Type RFC - Proposed Standard (March 2006; No errata)
Updated by RFC 6381
Was draft-garudadri-avt-3gpp2-mime (individual in tsv area)
Last updated 2013-03-02
Stream IETF
Formats plain text pdf html
Stream WG state (None)
Consensus Unknown
Document shepherd No shepherd assigned
IESG IESG state RFC 4393 (Proposed Standard)
Telechat date
Responsible AD Allison Mankin
Send notices to hardie@qualcomm.com, hgarudad@qualcomm.com, rg+ietf@qualcomm.com, keith.miller@nokia.com
Network Working Group                                       H. Garudadri
Request for Comments: 4393                                      QUALCOMM
Category: Standards Track                                     March 2006

           MIME Type Registrations for 3GPP2 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 (2006).

Abstract

   This document serves to register and document the standard MIME types
   associated with the 3GPP2 multimedia file format, which is part of
   the family based on the ISO Media File Format.

Table of Contents

   1. Introduction ....................................................1
      1.1. Conventions Used in This Document ..........................2
   2. Security Considerations .........................................2
   3. MIME Types ......................................................3
      3.1. Files with Audio but No Video ..............................3
      3.2. Any Files ..................................................4
   4. IANA Considerations .............................................5
   5. Acknowledgements ................................................6
   6. References ......................................................6
      6.1. Normative References .......................................6
      6.2. Informative References .....................................6

1.  Introduction

   The third-generation partnership project 2 (3GPP2) for 3rd generation
   cellular telephony has defined a standard file format to contain
   audio/visual sequences that may be downloaded to cellular phones
   [3gpp2].  At the time of writing, the 3GPP2 file format (3G2) can
   contain H.263, H.264, or MPEG-4 video; and 13K Vocoder, EVRC or AMR
   Narrow-band speech, or AAC audio; and 3GPP timed text.

Garudadri                   Standards Track                     [Page 1]
RFC 4393             3GPP2 Multimedia Registrations           March 2006

   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'.
   Files identified by the MIME [MIME1] type defined in this document
   MUST contain, in their compatible brands list, a brand defined in a
   standard (issued by 3GPP2) that can apply to 3GPP2 files.

   The MIME types defined in this document are needed correctly to
   identify such files when they are served over HTTP, included in
   multi-part documents, or used in other places where MIME types are
   used.

1.1.  Conventions Used in This Document

   In this document, the key words "MUST", "MUST NOT", "REQUIRED",
   "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY",
   and "OPTIONAL" are to be interpreted as described in RFC 2119
   [RFC2119].

2.  Security Considerations

   The 3GPP2 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 that 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 agreement-based World Intellectual Property
   Organization (WIPO) treaties.

   3GPP2 files have an extensible structure, so it is theoretically
   possible that metadata fields or media formats could be defined in
   the future that could be used to induce particular actions on the
   part of the recipient, thus presenting additional security risks; but
   this type of capability is currently not supported in the referenced
   specification.

Garudadri                   Standards Track                     [Page 2]
RFC 4393             3GPP2 Multimedia Registrations           March 2006
Show full document text