Network Working Group R. Castagno
Request for Comments: 3839 Nokia Mobile Phones
Category: Standards Track D. Singer
Apple Computer, Inc.
July 2004
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
第三代合作伙伴计划（3GPP）多媒体文件的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 (2004).
版权所有（C）互联网协会（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.
本文档用于注册和记录与3GPP多媒体文件格式相关的标准MIME类型，3GPP多媒体文件格式是基于ISO媒体文件格式的系列的一部分。
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].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照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.
第三代蜂窝电话的第三代合作伙伴计划（3GPP）定义了一种标准文件格式，其中包含可下载到蜂窝电话的音频/视频序列[3GPP]。在撰写本文时，3GPP文件格式（3GP）可以包含H.263或MPEG-4视频、AMR窄带语音、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'.
与“ISO”系列中的所有文件一样，在文件中有一个内部文件类型框，用于标识文件符合的规范，以及内容作者允许哪些播放器（可能仅符合一个规范）播放文件。此标识通过四个字母“品牌”进行标识。
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.
此处定义的MIME[MIME1]类型标识的文件必须包含3GPP发布的标准中定义的品牌，该标准可应用于3GPP文件的兼容品牌列表中。
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.
当这些文件通过HTTP提供、包含在多部分文档中或在使用MIME类型的其他地方使用时，需要这里定义的MIME类型来正确识别这些文件。
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.
3GPP文件格式可以包含音频、视频和可显示的文本数据。目前没有任何类型的“活动”元素（如脚本）的规定。
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.
应注意，选定的元数据字段可能包含部分用于保护媒体免受未经授权使用或分发的信息。在这种情况下，意图是根据基于世界知识产权组织（WIPO）条约的国家协定，更改或删除该领域的数据将被视为犯罪。
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.
3GPP文件具有可扩展的结构，因此理论上可以在将来定义元数据字段或媒体格式，这些元数据字段或媒体格式可用于诱导接收方的特定操作，从而带来额外的安全风险。但是，参考规范中目前不支持这种类型的功能。
There is no current provision in the standards for encryption, signing, or authentication of these file formats.
标准中没有关于这些文件格式的加密、签名或身份验证的现行规定。
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".
此注册适用于所有定义为使用“3GP”文件格式并在3GPP规范中以合适品牌标识的文件。所有这些文件通常的文件后缀是“.3gp”。
The type "audio/3gpp" may be used for files containing audio but no visual presentation (neither video nor timed text, for example).
类型“audio/3gpp”可用于包含音频但没有视频呈现（例如，既不是视频也不是定时文本）的文件。
To: ietf-types@iana.org
Subject: Registration of Standard MIME media type audio/3gpp
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).
MIME媒体类型名称：音频MIME子类型名称：3gpp必需参数：无可选参数：与此注册相关的任何正在进行的工作都可能引入新的可选参数。一个示例领域的工作可能引入一个参数，该参数允许断言和确定MIME类型中使用的编解码器，而无需检查文件。那些对该地区感兴趣的人应该监控注册的更新情况。编码注意事项：文件为二进制文件，应以适当的编码传输，无需CR/LF转换、7位剥离等。；base64是一种合适的编码。请注意，此MIME类型仅用于文件；单独的类型用于实时传输，例如用于AMR音频的RTP有效负载格式[RFC3267]。安全注意事项：请参阅RFC 3839互操作性注意事项：3GPP组织已定义了规范、互操作性和一致性，并定期进行互操作性测试。发布的规范：3GPP 26.234，第5版；3GPP 26.244，第6版或更高版本。3GPP规范可在3GPP网站www.3GPP.org上公开访问。使用此媒体类型的应用程序：多媒体附加信息：“音频/3gpp”类型可用于包含音频但不包含视频演示的文件。在此类型下提供的文件不得包含任何可视材料。（请注意，3GPP定时文本以可视方式呈现，并被视为可视材料）。
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: 3GPP
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: 3GPP
The type "video/3gpp" is valid for all files. It is valid to serve an audio-only file as "video/3gpp".
类型“video/3gpp”对所有文件都有效。仅音频文件作为“视频/3gpp”提供是有效的。
To: ietf-types@iana.org
Subject: Registration of Standard MIME media type video/3gpp
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
MIME媒体类型名称：视频MIME子类型名称：3gpp所需参数：无可选参数：无编码注意事项：文件为二进制文件，应以合适的编码传输，无需CR/LF转换、7位剥离等。；base64是一种合适的编码。请注意，此MIME类型仅用于文件；单独的类型用于实时传输，例如用于H.263[RFC2429]和AMR音频[RFC3267]的RTP有效负载格式。安全注意事项：请参阅RFC 3839互操作性注意事项：3GPP组织已定义了规范、互操作性和一致性，并定期进行互操作性测试。发布的规范：3GPP 26.234，第5版；3GPP 26.244，第6版或更高版本。3GPP规范可在3GPP网站www.3GPP.org上公开访问。使用此媒体类型的应用程序：多媒体
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: 3GPP
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: 3GPP
This document registers the MIME types audio/3gpp and video/3gpp, defined above.
本文档注册了上文定义的MIME类型audio/3gpp和video/3gpp。
The review of the 3GPP SA4 committee is gratefully acknowledged, in particular Per Frojdh. The chairs of the AVT working group, in particular Colin Perkins, have provided both excellent guidance and feedback, for which the authors are grateful.
感谢3GPP SA4委员会的审查，特别是Per Frojdh。AVT工作组主席，特别是Colin Perkins，提供了出色的指导和反馈，作者对此表示感谢。
[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)
[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.
[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月。
[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.
[RFC3267]Sjoberg，J.，Westerlund，M.，Lakaniemi，A.和Q.Xie，“自适应多速率（AMR）和自适应多速率宽带（AMR-WB）音频编解码器的实时传输协议（RTP）有效载荷格式和文件存储格式”，RFC 3267，2002年6月。
Roberto Castagno Nokia Mobile Phones PO Box 88, FIN-33721 Tampere (Tieteenkatu 1, FIN-33720 Tampere) Finland
Roberto Castagno诺基亚手机邮政信箱88号，FIN-33721坦佩雷（Tieteenkatu 1号，FIN-33720坦佩雷）芬兰
Phone: +358 7180 35796
EMail: roberto.castagno@nokia.com
Phone: +358 7180 35796
EMail: roberto.castagno@nokia.com
David Singer Apple Computer, Inc. One Infinite Loop, MS:302-3MT Cupertino CA 95014 USA
David Singer苹果电脑有限公司One Infinite Loop，MS:302-3MT Cupertino CA 95014美国
Phone: +1 408 974 3162
EMail: singer@apple.com
Phone: +1 408 974 3162
EMail: singer@apple.com
Copyright (C) The Internet Society (2004). 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.
版权所有（C）互联网协会（2004年）。本文件受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 currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。