RFC 3839
MIME Type Registrations for 3rd Generation Partnership Project (3GPP) Multimedia files
RFC 3839: MIME Type Registrations for 3rd Generation Partnership Project (3GPP) Multimedia files ✨
okay bestie, the title block is giving important standards energy 🎀. This one is from the Network Working Group, written by R. Castagno (Nokia Mobile Phones) and D. Singer (Apple Computer, Inc.) in July 2004. It's on the Standards Track 🦋. The header doesn't list any RFCs it obsoletes or updates, so there's nothing to chase there 💅.
Status of This Memo
okay so this section says the doc is an Internet standards track protocol for the Internet community, and it's basically asking everyone to talk about it and send ideas for making it better 💖. If you want to know where this protocol stands in the standardization process, check the current edition of the "Internet Official Protocol Standards" (STD 1) 📚. Distribution of this memo is unlimited 🌈.
Copyright Notice
Copyright (C) The Internet Society (2004). 🔥
Abstract
so the whole point of this doc is to register and document the standard MIME types for the 3GPP multimedia file format, which belongs to the family based on the ISO Media File Format 🎬✨.
1. Introduction
okay real talk, this section is where the key words live 👑. Here's the list, exactly as written: "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL". In this document they're meant to be read as described in BCP 14, RFC 2119 [RFC2119] 🫶.
so the third-generation partnership project (3GPP) made a standard file format for third-generation cellular telephony, and it holds audio/visual sequences that can be downloaded to phones [3GPP] 📱🌸. At the time of writing, a 3GPP file (3GP) can hold H.263 or MPEG-4 video, AMR Narrow-band speech, AMR wide-band speech, or AAC audio, plus 3GPP timed text 🎀.
inside the file, like every file in the 'ISO' family, there's an intrinsic file-type box 📦. It says which specifications the file complies with, and which players are allowed by the content author to play it. A player might only be compliant with one specification, and that's still fine 🧚. The identification happens through four-letter 'brands' 🔤.
the big rule: 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 in this doc are needed so these files get identified correctly when they're served over HTTP, included in multi-part documents, or used anywhere else MIME types show up 💖.
2. Security Considerations
ngl, this section is the serious one, so pay attention 😭🚨.
the 3GPP file format can hold audio, video, and displayable text data 🎶. There's currently no provision for 'active' elements (such as scripts) of any kind 🙅♀️.
it's totally possible for someone to author malicious files that try to demand an excessively large picture size, a high sampling-rate audio, and so on. The good news is that 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 🧩. Theoretically, metadata fields or media formats could be defined in the future that induce particular actions on the part of the recipient, which would bring additional security risks. However, this type of capability is currently not supported in the referenced specification 🙈.
there's no current provision in the standards for encryption, signing, or authentication of these file formats 💀.
3. MIME Types
this registration covers 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
okay so the type audio/3gpp may be used for files that contain audio but no visual presentation (no video and no timed text, for example) 🎧✨.
Here's the registration template, verbatim:
To: ietf-types@iana.org
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 a
parameter that would allow for
codecs in use within the MIME type
to be asserted and determined
without examination of the file.
Those with interests in the area
should monitor registrations for
updates.
Encoding considerations: files are binary and should be
transmitted in a suitable encoding
without CR/LF conversion, 7-bit
stripping etc.; base64 is a suitable
encoding. Note that this MIME type
is used only for files; separate
types are used for real-time
transfer, such as for the RTP
payload format for AMR audio
[RFC3267].
Security considerations: see the security considerations
section in RFC 3839
Interoperability considerations: The 3GPP organization has defined the
specification, interoperability, and
conformance, and conducts regular
interoperability testing.
Published specification: 3GPP 26.234, Release 5; 3GPP 26.244,
Release 6 or later. 3GPP
specifications are publicly
accessible at the 3GPP web site,
www.3gpp.org.
Applications which use this media type: Multi-media
Additional information: The type "audio/3gpp" MAY be used for
files containing audio but no visual
presentation. Files served under
this type MUST NOT contain any
visual material. (Note that 3GPP
timed text is visually presented
and is considered to be visual
material).
Magic number(s): None. However, the file-type box
must occur first in the file, and
MUST contain a 3GPP brand in its
compatible brands list.
File extension(s): 3gp and 3gpp are both declared at
http://www.nist.gov/nics/; 3gp is
preferred
Macintosh File Type Code(s): '3gpp'
Person & email address to contact for further information:
Nokia MIME manager, mime@nokia.com
Intended usage: COMMON
Change controller: 3GPP3.2. Any files
so the type video/3gpp is valid for all files 🎥💜. It's also valid to serve an audio-only file as video/3gpp 🦋.
Here's the second template, verbatim:
To: ietf-types@iana.org
Subject: Registration of Standard MIME media type video/3gpp
MIME media type name: video
MIME subtype name: 3gpp
Required parameters: none
Optional parameters: none
Encoding considerations: files are binary and should be
transmitted in a suitable encoding
without CR/LF conversion, 7-bit
stripping etc.; base64 is a suitable
encoding. Note that this MIME type
is used only for files; separate
types are used for real-time
transfer, such as for the RTP
payload formats for H.263
[RFC2429] and AMR audio
[RFC3267].
Security considerations: see the security considerations
section in RFC 3839
Interoperability considerations: The 3GPP organization has defined the
specification, interoperability, and
conformance, and conducts regular
interoperability testing.
Published specification: 3GPP 26.234, Release 5; 3GPP 26.244,
Release 6 or later. 3GPP
specifications are publicly
accessible at the 3GPP web site,
www.3gpp.org.
Applications which use this media type: Multi-media
Additional information:
Magic number(s): None. However, the file-type box
must occur first in the file, and
MUST contain a 3GPP brand in its
compatible brands list.
File extension(s): 3gp and 3gpp are both declared at
http://www.nist.gov/nics/; 3gp is
preferred
Macintosh File Type Code(s): '3gpp'
Person & email address to contact for further information:
Nokia MIME manager, mime@nokia.com
Intended usage: COMMON
Change controller: 3GPP4. IANA Considerations
this doc registers the MIME types audio/3gpp and video/3gpp, which were defined above 📝🌷.
5. Acknowledgments
big thank yous 🫶💖. The review by the 3GPP SA4 committee is gratefully acknowledged, especially Per Frojdh 🙌. The chairs of the AVT working group, especially Colin Perkins, gave excellent guidance and feedback, and the authors are super grateful 🥹✨.
6. References
6.1. Normative References
here are the normative references, copied exactly 📚:
[3GPP] Published specifications in releases 5 and 6: Release 5:
3GPP TS 26.234: Transparent end-to-end packet switched
streaming service (PSS); Protocols and codecs. Release 6:
3GPP TS 26.244: Transparent end-to-end packet switched
streaming service (PSS); 3GPP file format (3GP)
[MIME1] Freed, N. and N. Borenstein, "Multipurpose Internet Mail
Extensions (MIME) Part One: Format of Internet Message
Bodies", RFC 2045, November 1996.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.6.2. Informative References ✨
Okay so these are the "good to know" references, bestie. You don't need them to implement anything, but they're where the backstory lives 📚
- [RFC2429] Bormann, C., Cline, L., Deisher, G., Gardos, T., Maciocco, C., Newell, D., Ott, J., Sullivan, G., Wenger, S. and C. Zhu, "RTP Payload Format for the 1998 Version of ITU-T Rec. H.263 Video (H.263+)", RFC 2429, October 1998. 🎥
- [RFC3267] Sjoberg, J., Westerlund, M., Lakaniemi, A. and Q. Xie, "Real-Time Transport Protocol (RTP) Payload Format and File Storage Format for the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate WideBand (AMR-WB) Audio Codecs", RFC 3267, June 2002. 🎙️
7. Authors' Contact Information 🎀
Meet the two people who wrote this thing. Roberto from Nokia and David from Apple, iconic duo 🫶
Roberto Castagno
Nokia Mobile Phones
PO Box 88, FIN-33721 Tampere
(Tieteenkatu 1, FIN-33720 Tampere)
Finland
Phone: +358 7180 35796
EMail: roberto.castagno@nokia.com
David Singer
Apple Computer, Inc.
One Infinite Loop, MS:302-3MT
Cupertino CA 95014
USA
Phone: +1 408 974 3162
EMail: singer@apple.com8. Full Copyright Statement 💅
Okay, the legal bit, but make it cute. The Internet Society owns the copyright (2004 vibes 🌸). This document is subject to the rights, licenses and restrictions in BCP 78, and the authors keep all their rights, except as set out there.
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property 🔥
Here's the deal with patents and other IP drama. The IETF doesn't take a side on whether any IP rights covering this technology are valid or how wide they are, and it doesn't say whether licences are available. It also hasn't checked for any rights on its own. If you want the details on IP rights for RFC documents, check out BCP 78 and BCP 79 🧐
Copies of IPR disclosures sent to the IETF Secretariat, plus any licence assurances, or the results of an attempt to get a general licence or permission to use those proprietary rights for implementers or users of this spec, can be found in the IETF online IPR repository at http://www.ietf.org/ipr.
The IETF also invites anyone to flag any copyrights, patents, patent applications or other proprietary rights that might cover technology needed to implement this standard. Send that info to the IETF at ietf-ipr@ietf.org 📬
Acknowledgement 🌈
The RFC Editor function is funded by the Internet Society right now. Thank you, ISOC 🙏✨
📦 where this page comes from
- ietf: rfc3839 2004-07
- 💖 girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms