Network Working Group H. Garudadri
Request for Comments: 4393 QUALCOMM
Category: Standards Track March 2006
Network Working Group H. Garudadri
Request for Comments: 4393 QUALCOMM
Category: Standards Track March 2006
MIME Type Registrations for 3GPP2 Multimedia Files
3GPP2多媒体文件的MIME类型注册
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.
本文件规定了互联网社区的互联网标准跟踪协议，并要求进行讨论和提出改进建议。有关本协议的标准化状态和状态，请参考当前版本的“互联网官方协议标准”（STD 1）。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2006).
版权所有（C）互联网协会（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.
本文档用于注册和记录与3GPP2多媒体文件格式相关的标准MIME类型，3GPP2多媒体文件格式是基于ISO媒体文件格式的系列的一部分。
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 ....................................................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
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.
第三代蜂窝电话的第三代合作伙伴项目2（3GPP2）定义了一种标准文件格式，以包含可下载到蜂窝电话的音频/视频序列[3GPP2]。在写入时，3GPP2文件格式（3G2）可以包含H.263、H.264或MPEG-4视频；和13K声码器、EVRC或AMR窄带语音或AAC音频；和3GPP定时文本。
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.
与“ISO”系列中的所有文件一样，在文件中有一个内部文件类型框，用于标识文件符合的规范，以及内容作者允许哪些播放器（可能仅符合一个规范）播放文件。此标识通过四个字母“品牌”进行标识。由本文档中定义的MIME[MIME1]类型标识的文件必须在其兼容品牌列表中包含在可应用于3GPP2文件的标准（由3GPP2发布）中定义的品牌。
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.
当这些文件通过HTTP提供服务、包含在多部分文档中或在使用MIME类型的其他地方使用时，需要使用本文档中定义的MIME类型来正确识别这些文件。
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].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119[RFC2119]中的说明进行解释。
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.
3GPP2文件格式可以包含音频、视频和可显示文本数据。目前没有任何类型的“活动”元素（如脚本）的规定。
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.
应注意，选定的元数据字段可能包含部分用于保护媒体免受未经授权使用或分发的信息。在这种情况下，意图是根据基于国家协议的世界知识产权组织（WIPO）条约，更改或删除该领域的数据将被视为犯罪。
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.
3GPP2文件具有可扩展的结构，因此理论上可能在将来定义元数据字段或媒体格式，这些元数据字段或媒体格式可用于诱导接收方的特定操作，从而带来额外的安全风险；但参考规范中目前不支持这种类型的功能。
Encryption, signing, or authentication of these file formats can be done using any media-independent transformations of the file or media data.
这些文件格式的加密、签名或身份验证可以使用文件或媒体数据的任何与媒体无关的转换来完成。
This registration applies to all files defined as using the '3G2' file format and identified with a suitable brand in a 3GPP2 specification. The usual file suffix for all these files is ".3g2".
此注册适用于定义为使用“3G2”文件格式并在3GPP2规范中以合适品牌标识的所有文件。所有这些文件通常的文件后缀是“.3g2”。
The type "audio/3gpp2" may be used for files containing audio but no visual presentation (neither video nor timed text, for example).
类型“audio/3gpp2”可用于包含音频但不包含视频呈现的文件（例如，既不是视频也不是定时文本）。
To: ietf-types@iana.org
Subject: Registration of Standard MIME media type audio/3gpp2
To: ietf-types@iana.org
Subject: Registration of Standard MIME media type audio/3gpp2
MIME media type name: audio MIME subtype name: 3gpp2 Required parameters: None. Optional parameters: Codecs. See [Bucket]. If the audio/3gpp2 body part contains another container format, the Codecs parameter MUST list all codecs indicated by all formats, including any contained formats. Optional parameter values: [3gpp2] Encoding considerations: This data is 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 13K vocoder speech [RFC2658]. Security considerations: See the security considerations section in RFC 4393 (this document). Interoperability considerations: The 3GPP2 organization has defined the specification of the media format [3gpp2]. Interoperability and conformance testing is done in cooperation with other bodies, including the Open Mobile Alliance (OMA) <http://www.openmobilealliance.org> and the International Multimedia Telecommunications Consortium (IMTC) <http://www.imtc.org/>.
MIME媒体类型名称：音频MIME子类型名称：3gpp2所需参数：无。可选参数：编解码器。见[桶]。如果音频/3gpp2主体部分包含另一种容器格式，Codecs参数必须列出所有格式指示的所有编解码器，包括任何包含的格式。可选参数值：[3gpp2]编码注意事项：此数据为二进制数据，应以适当的编码方式传输，无需CR/LF转换、7位剥离等。；base64是一种合适的编码。请注意，此MIME类型仅用于文件；单独的类型用于实时传输，例如用于13K声码器语音[RFC2658]的RTP有效负载格式。安全注意事项：请参阅RFC 4393（本文档）中的安全注意事项部分。互操作性注意事项：3GPP2组织已经定义了媒体格式[3GPP2]的规范。互操作性和一致性测试是与其他机构合作完成的，包括开放移动联盟（OMA）<http://www.openmobilealliance.org>以及国际多媒体电讯联盟(IMTC)<http://www.imtc.org/>.
Published specification:
3GPP2 C.S0045, 3GPP2 C.S0050 [3gpp2]
3GPP2 specifications are publicly accessible at the 3GPP2 web
site, <http://www.3gpp2.org>.
Applications that use this media type:
Multi-media
Additional information:
The type "audio/3gpp2" 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 visual material).
Magic number(s):
None. However, the file-type box must occur first in the file,
and MUST contain a 3GPP2 brand in its compatible brands list.
File extension(s):
3g2 and 3gpp2 are both declared at <http://www.nist.gov/nics/>;
3g2 is preferred.
Macintosh file type code(s):
'3gp2'
Person & email address to contact for further information:
H. Garudadri, hgarudadri@qualcomm.com
Intended usage:
COMMON
Change controller:
3GPP2
Published specification:
3GPP2 C.S0045, 3GPP2 C.S0050 [3gpp2]
3GPP2 specifications are publicly accessible at the 3GPP2 web
site, <http://www.3gpp2.org>.
Applications that use this media type:
Multi-media
Additional information:
The type "audio/3gpp2" 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 visual material).
Magic number(s):
None. However, the file-type box must occur first in the file,
and MUST contain a 3GPP2 brand in its compatible brands list.
File extension(s):
3g2 and 3gpp2 are both declared at <http://www.nist.gov/nics/>;
3g2 is preferred.
Macintosh file type code(s):
'3gp2'
Person & email address to contact for further information:
H. Garudadri, hgarudadri@qualcomm.com
Intended usage:
COMMON
Change controller:
3GPP2
The type "video/3gpp2" is valid for all files. It is valid to serve an audio-only file as "video/3gpp2".
类型“video/3gpp2”对所有文件都有效。仅音频文件作为“视频/3gpp2”提供是有效的。
To: ietf-types@iana.org
Subject: Registration of Standard MIME media type video/3gpp2
To: ietf-types@iana.org
Subject: Registration of Standard MIME media type video/3gpp2
MIME media type name: video MIME subtype name: 3gpp2 Required parameters: None Optional parameters: Codecs. See [Bucket]. If the video/3gpp2 body part contains another container format, the Codecs parameter MUST list all codecs indicated by all formats, including any contained formats. Optional parameter values: [3gpp2]
MIME媒体类型名称：视频MIME子类型名称：3gpp2必需参数：无可选参数：编解码器。见[桶]。如果视频/3gpp2主体部分包含另一种容器格式，Codecs参数必须列出所有格式指示的所有编解码器，包括任何包含的格式。可选参数值：[3gpp2]
Encoding considerations: This data is 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 13K vocoder speech [RFC2658]. Security considerations: See the security considerations section in RFC 4393 (this document). Interoperability considerations: The 3GPP2 organization has defined the specification of the media format [3gpp2]. Interoperability and conformance testing is done in cooperation with other bodies, including the Open Mobile Alliance (OMA) <http://www.openmobilealliance.org> and the International Multimedia Telecommunications Consortium (IMTC) <http://www.imtc.org/>. Published specification: 3GPP2 C.S0045, 3GPP2 C.S0050 [3gpp2]
编码注意事项：该数据为二进制数据，应以适当的编码方式传输，无需CR/LF转换、7位剥离等。；base64是一种合适的编码。请注意，此MIME类型仅用于文件；单独的类型用于实时传输，例如用于H.263[RFC2429]和13K声码器语音[RFC2658]的RTP有效负载格式。安全注意事项：请参阅RFC 4393（本文档）中的安全注意事项部分。互操作性注意事项：3GPP2组织已经定义了媒体格式[3GPP2]的规范。互操作性和一致性测试是与其他机构合作完成的，包括开放移动联盟（OMA）<http://www.openmobilealliance.org>以及国际多媒体电讯联盟(IMTC)<http://www.imtc.org/>. 发布规范：3GPP2 C.S0045、3GPP2 C.S0050[3GPP2]
3GPP2 specifications are publicly accessible at the 3GPP2 web
site, <http://www.3gpp2.org>.
Applications that 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 3GPP2 brand in its compatible brands list.
File extension(s):
3g2 and 3gpp2 are both declared at <http://www.nist.gov/nics/>;
3g2 is preferred.
Macintosh file type code(s):
'3gp2'
Person & email address to contact for further information:
H.Garudadri, hgarudadri@qualcomm.com
Intended usage:
COMMON
Change controller:
3GPP2
3GPP2 specifications are publicly accessible at the 3GPP2 web
site, <http://www.3gpp2.org>.
Applications that 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 3GPP2 brand in its compatible brands list.
File extension(s):
3g2 and 3gpp2 are both declared at <http://www.nist.gov/nics/>;
3g2 is preferred.
Macintosh file type code(s):
'3gp2'
Person & email address to contact for further information:
H.Garudadri, hgarudadri@qualcomm.com
Intended usage:
COMMON
Change controller:
3GPP2
This document registers the MIME media types audio/3gpp2 and video/3gpp2, defined above.
本文档注册了上文定义的MIME媒体类型audio/3gpp2和video/3gpp2。
This document used RFC 3839 as a template. The authors of RFC 3839, R. Castagno, and D. Singer, are gratefully acknowledged.
本文件使用RFC 3839作为模板。感谢RFC3839的作者R.卡斯塔尼奥和D.辛格。
[3gpp2] Published specifications: C.S0050: 3GPP2 File Formats for Multimedia Services. C.S0045: Multimedia Messaging Service (MMS) Media Format and Codecs for cdma2000 Spread Spectrum Systems.
[3gpp2]发布的规范：C.S0050:3gpp2多媒体服务文件格式。C.S0045：cdma2000扩频系统的彩信服务（MMS）媒体格式和编解码器。
[Bucket] Gellens, R., Singer, D., and P. Frojdh, "The Codecs Parameter for "Bucket" Media Types", RFC 4281, November 2005.
[Bucket]Gellens，R.，Singer，D.，和P.Frojdh，“Bucket”媒体类型的编解码器参数”，RFC 42812005年11月。
[MIME1] Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies", RFC 2045, November 1996.
[MIME1]Freed，N.和N.Borenstein，“多用途Internet邮件扩展（MIME）第一部分：Internet邮件正文格式”，RFC 20451996年11月。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[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.
[RFC2429]Bormann，C.，Cline，L.，Deisher，G.，Gardos，T.，Maciocco，C.，Newell，D.，Ott，J.，Sullivan，G.，Wenger，S.，和C.Zhu，“1998版ITU-T Rec.H.263视频（H.263+）的RTP有效载荷格式”，RFC 24291998年10月。
[RFC2658] McKay, K., "RTP Payload Format for PureVoice(tm) Audio", RFC 2658, August 1999.
[RFC2658]McKay，K.，“PureVoice（tm）音频的RTP有效载荷格式”，RFC2658，1999年8月。
Author's Address
作者地址
Harinath Garudadri Qualcomm Inc 5775 Morehouse Dr. San Diego, CA 92121
Harinath Garudadri高通公司5775加利福尼亚州圣地亚哥Morehouse Dr.92121
Phone: +1 858 651 6383
EMail: hgarudadri@qualcomm.com
Phone: +1 858 651 6383
EMail: hgarudadri@qualcomm.com
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (2006).
版权所有（C）互联网协会（2006年）。
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
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
知识产权
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息，请参见BCP 78和BCP 79。
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.
Acknowledgement
确认
Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA).
RFC编辑器功能的资金由IETF行政支持活动（IASA）提供。