Network Working Group J. Rosenberg
Request for Comments: 3009 dynamicsoft
Category: Standards Track H. Schulzrinne
Columbia U.
November 2000
Network Working Group J. Rosenberg
Request for Comments: 3009 dynamicsoft
Category: Standards Track H. Schulzrinne
Columbia U.
November 2000
Registration of parityfec MIME types
parityfec 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 (2000). All Rights Reserved.
版权所有（C）互联网协会（2000年）。版权所有。
Abstract
摘要
The RTP (Real-time Transport Protocol) payload format for generic forward error correction allows RTP participants to improve loss resiliency through the use of traditional parity-based channel codes. This payload format requires four new MIME types, audio/parityfec, video/parityfec, text/parityfec and application/parityfec. This document serves as the MIME type registration for those formats.
用于通用前向纠错的RTP（实时传输协议）有效负载格式允许RTP参与者通过使用传统的基于奇偶校验的信道码来提高丢失恢复能力。此有效负载格式需要四种新的MIME类型：音频/parityfec、视频/parityfec、文本/parityfec和应用程序/parityfec。此文档用作这些格式的MIME类型注册。
1 Introduction
1导言
The RTP payload format for generic forward error correction [1] allows RTP participants to improve loss resiliency through the use of traditional parity-based channel codes. This payload format requires four new MIME types, audio/parityfec, video/parityfec, text/paritfyfec and application/parityfec. RFC 2048 [2] defines procedures for registration of new MIME types within the IETF tree. Furthermore, the Audio/Video Transport working group has defined additional procedures that must be followed when registering RTP payload formats [3]. This document serves as the MIME type registration for those formats based on those procedures.
通用前向纠错的RTP有效负载格式[1]允许RTP参与者通过使用传统的基于奇偶校验的信道码来提高丢失恢复能力。此有效负载格式需要四种新的MIME类型：音频/parityfec、视频/parityfec、文本/parityfec和应用程序/parityfec。RFC 2048[2]定义了在IETF树中注册新MIME类型的过程。此外，音频/视频传输工作组定义了注册RTP有效负载格式时必须遵循的附加程序[3]。本文档作为基于这些过程的这些格式的MIME类型注册。
2 Registration of audio/parityfec
2音频/parityfec的注册
To: ietf-types@iana.org
致：ietf-types@iana.org
Subject: Registration of MIME media type audio/parityfec
主题：注册MIME媒体类型音频/parityfec
MIME media type name: audio
MIME媒体类型名称：音频
MIME subtype name: parityfec
MIME子类型名称：parityfec
Required parameters: none
所需参数：无
Note that [3] mandates that RTP payload formats without a defined rate must define a rate parameter as part of their MIME registration. The payload format for generic forward error correction [1] does not specify a rate parameter. However, the rate for FEC data is equal to the rate of the media data it protects.
注意，[3]要求没有定义速率的RTP有效负载格式必须定义速率参数作为MIME注册的一部分。通用前向纠错[1]的有效负载格式未指定速率参数。但是，FEC数据的速率等于其保护的媒体数据的速率。
Optional parameters: none
可选参数：无
Typical optional parameters [3], such as the number of channels, and the duration of audio per packet, do not apply to FEC data. The number of channels is effectively the same as the media data it protects; the same is true for the duration of audio per packet.
典型的可选参数[3]，如通道数和每个数据包的音频持续时间，不适用于FEC数据。通道的数量实际上与其保护的媒体数据相同；每个数据包的音频持续时间也是如此。
Encoding considerations: This format is only defined for transport within the Real Time Transport protocol (RTP) [4,5]. Its transport within RTP is fully specified with RFC 2733 [1].
编码注意事项：此格式仅定义用于实时传输协议（RTP）[4,5]中的传输。其在RTP内的传输完全由RFC 2733[1]规定。
Security considerations: the same security considerations apply to these mime registrations as to the payloads for for them, as detailed in RFC 2733.
安全注意事项：这些mime注册的安全注意事项与有效负载的安全注意事项相同，详见RFC 2733。
Interoperability considerations: none
互操作性注意事项：无
Published specification: This MIME type is described fully within RFC 2733 [1].
已发布的规范：RFC2733[1]中对该MIME类型进行了完整的描述。
Applications which use this media type: Audio and video streaming tools which seek to improve resiliency to loss by sending additional data with the media stream.
使用此媒体类型的应用程序：音频和视频流工具，通过使用媒体流发送附加数据来提高丢失恢复能力。
Additional information: none
其他信息：无
Person & email address to contact for further information:
联系人和电子邮件地址，以获取更多信息：
Jonathan Rosenberg dynamicsoft 72 Eagle Rock Avenue First Floor East Hanover, NJ 07936 email: jdrosen@dynamicsoft.com jdrosen@alum.mit.edu
Jonathan Rosenberg dynamicsoft 72 Eagle Rock Avenue一楼东汉诺威，NJ 07936电子邮件：jdrosen@dynamicsoft.com jdrosen@alum.mit.edu
Intended usage: COMMON
预期用途：普通
Author/Change controller: This registration is part of the IETF registration tree.
作者/变更控制者：此注册是IETF注册树的一部分。
RTP and SDP Issues: Usage of this format within RTP and the Session Description Protocol (SDP) [6] are fully specified within RFC 2733 [1].
RTP和SDP问题：RTP和会话描述协议（SDP）[6]中此格式的使用在RFC 2733[1]中有详细说明。
3 Registration of video/parityfec
3视频/parityfec的注册
To: ietf-types@iana.org
致：ietf-types@iana.org
Subject: Registration of MIME media type video/parityfec
主题：注册MIME媒体类型视频/parityfec
MIME media type name: video
MIME媒体类型名称：视频
MIME subtype name: parityfec
MIME子类型名称：parityfec
Required parameters: none
所需参数：无
Note that [3] mandates that RTP payload formats without a defined rate must define a rate parameter as part of their MIME registration. The payload format for generic forward error correction [1] does not specify a rate parameter. However, the rate for FEC data is equal to the rate of the media data it protects.
注意，[3]要求没有定义速率的RTP有效负载格式必须定义速率参数作为MIME注册的一部分。通用前向纠错[1]的有效负载格式未指定速率参数。但是，FEC数据的速率等于其保护的媒体数据的速率。
Optional parameters: none
可选参数：无
Typical optional parameters [3], such as the number of channels, and the duration of audio per packet, do not apply to FEC data. The number of channels is effectively the same as the media data it protects; the same is true for the duration of video per packet.
典型的可选参数[3]，如通道数和每个数据包的音频持续时间，不适用于FEC数据。通道的数量实际上与其保护的媒体数据相同；每个数据包的视频持续时间也是如此。
Encoding considerations: This format is only defined for transport within the Real Time Transport protocol (RTP) [4,5]. Its transport within RTP is fully specified with RFC 2733 [1].
编码注意事项：此格式仅定义用于实时传输协议（RTP）[4,5]中的传输。其在RTP内的传输完全由RFC 2733[1]规定。
Security considerations: the same security considerations apply to these MIME registrations as to the payloads for for them, as detailed in RFC 2733.
安全注意事项：这些MIME注册的安全注意事项与有效负载的安全注意事项相同，详见RFC 2733。
Interoperability considerations: none
互操作性注意事项：无
Published specification: This MIME type is described fully within RFC 2733 [1].
已发布的规范：RFC2733[1]中对该MIME类型进行了完整的描述。
Applications which use this media type: Audio and video streaming tools which seek to improve resiliency to loss by sending additional data with the media stream.
使用此媒体类型的应用程序：音频和视频流工具，通过使用媒体流发送附加数据来提高丢失恢复能力。
Additional information: none
其他信息：无
Person & email address to contact for further information:
联系人和电子邮件地址，以获取更多信息：
Jonathan Rosenberg dynamicsoft 72 Eagle Rock Avenue First Floor East Hanover, NJ 07936 email: jdrosen@dynamicsoft.com jdrosen@alum.mit.edu
Jonathan Rosenberg dynamicsoft 72 Eagle Rock Avenue一楼东汉诺威，NJ 07936电子邮件：jdrosen@dynamicsoft.com jdrosen@alum.mit.edu
Intended usage: COMMON
预期用途：普通
Author/Change controller: This registration is part of the IETF registration tree.
作者/变更控制者：此注册是IETF注册树的一部分。
RTP and SDP Issues: Usage of this format within RTP and the Session Description Protocol (SDP) [6] are fully specified within RFC 2733 [1].
RTP和SDP问题：RTP和会话描述协议（SDP）[6]中此格式的使用在RFC 2733[1]中有详细说明。
4 Registration of text/parityfec
4文本/对等项的注册
To: ietf-types@iana.org
致：ietf-types@iana.org
Subject: Registration of MIME media type text/parityfec
主题：注册MIME媒体类型text/parityfec
MIME media type name: text
MIME媒体类型名称：text
MIME subtype name: parityfec
MIME子类型名称：parityfec
Required parameters: none
所需参数：无
Note that [3] mandates that RTP payload formats without a defined rate must define a rate parameter as part of their MIME registration. The payload format for generic forward error correction [1] does not specify a rate parameter. However, the rate for FEC data is equal to the rate of the media data it protects.
注意，[3]要求没有定义速率的RTP有效负载格式必须定义速率参数作为MIME注册的一部分。通用前向纠错[1]的有效负载格式未指定速率参数。但是，FEC数据的速率等于其保护的媒体数据的速率。
Optional parameters: none
可选参数：无
Typical optional parameters [3], such as the number of channels, and the duration of audio per packet, do not apply to FEC data. The number of channels is effectively the same as the media data it protects; the same is true for the duration of text per packet.
典型的可选参数[3]，如通道数和每个数据包的音频持续时间，不适用于FEC数据。通道的数量实际上与其保护的媒体数据相同；对于每个数据包的文本持续时间也是如此。
Encoding considerations: This format is only defined for transport within the Real Time Transport protocol (RTP) [4,5]. Its transport within RTP is fully specified with RFC 2733 [1].
编码注意事项：此格式仅定义用于实时传输协议（RTP）[4,5]中的传输。其在RTP内的传输完全由RFC 2733[1]规定。
Security considerations: the same security considerations apply to these MIME registrations as to the payloads for for them, as detailed in RFC 2733.
安全注意事项：这些MIME注册的安全注意事项与有效负载的安全注意事项相同，详见RFC 2733。
Interoperability considerations: none
互操作性注意事项：无
Published specification: This MIME type is described fully within RFC 2733 [1].
已发布的规范：RFC2733[1]中对该MIME类型进行了完整的描述。
Applications which use this media type: Audio, video and text streaming tools which seek to improve resiliency to loss by sending additional data with the media stream.
使用此媒体类型的应用程序：音频、视频和文本流媒体工具，通过使用媒体流发送附加数据来提高丢失恢复能力。
Additional information: none
其他信息：无
Person & email address to contact for further information:
联系人和电子邮件地址，以获取更多信息：
Jonathan Rosenberg dynamicsoft 72 Eagle Rock Avenue First Floor East Hanover, NJ 07936 email: jdrosen@dynamicsoft.com jdrosen@alum.mit.edu
Jonathan Rosenberg dynamicsoft 72 Eagle Rock Avenue一楼东汉诺威，NJ 07936电子邮件：jdrosen@dynamicsoft.com jdrosen@alum.mit.edu
Intended usage: COMMON
预期用途：普通
Author/Change controller: This registration is part of the IETF registration tree.
作者/变更控制者：此注册是IETF注册树的一部分。
RTP and SDP Issues: Usage of this format within RTP and the Session Description Protocol (SDP) [6] are fully specified within RFC 2733 [1].
RTP和SDP问题：RTP和会话描述协议（SDP）[6]中此格式的使用在RFC 2733[1]中有详细说明。
5 Registration of application/parityfec
5申请登记/parityfec
To: ietf-types@iana.org
致：ietf-types@iana.org
Subject: Registration of MIME media type application/parityfec
主题：注册MIME媒体类型应用程序/parityfec
MIME media type name: application
MIME媒体类型名称：应用程序
MIME subtype name: parityfec
MIME子类型名称：parityfec
Required parameters: none
所需参数：无
Note that [3] mandates that RTP payload formats without a defined rate must define a rate parameter as part of their MIME registration. The payload format for generic forward error correction [1] does not specify a rate parameter. However, the rate for FEC data is equal to the rate of the media data it protects.
注意，[3]要求没有定义速率的RTP有效负载格式必须定义速率参数作为MIME注册的一部分。通用前向纠错[1]的有效负载格式未指定速率参数。但是，FEC数据的速率等于其保护的媒体数据的速率。
Optional parameters: none
可选参数：无
Typical optional parameters [3], such as the number of channels, and the duration of audio per packet, do not apply to FEC data. The number of channels is effectively the same as the media data it protects; the same is true for the duration of application data per packet.
典型的可选参数[3]，如通道数和每个数据包的音频持续时间，不适用于FEC数据。通道的数量实际上与其保护的媒体数据相同；对于每个数据包的应用程序数据持续时间也是如此。
Encoding considerations: This format is only defined for transport within the Real Time Transport protocol (RTP) [4,5]. Its transport within RTP is fully specified with RFC 2733 [1].
编码注意事项：此格式仅定义用于实时传输协议（RTP）[4,5]中的传输。其在RTP内的传输完全由RFC 2733[1]规定。
Security considerations: the same security considerations apply to these MIME registrations as to the payloads for for them, as detailed in RFC 2733.
安全注意事项：这些MIME注册的安全注意事项与有效负载的安全注意事项相同，详见RFC 2733。
Interoperability considerations: none
互操作性注意事项：无
Published specification: This MIME type is described fully within RFC 2733 [1].
已发布的规范：RFC2733[1]中对该MIME类型进行了完整的描述。
Applications which use this media type: Audio, video and application streaming tools which seek to improve resiliency to loss by sending additional data with the media stream.
使用此媒体类型的应用程序：音频、视频和应用程序流媒体工具，通过使用媒体流发送附加数据来提高丢失恢复能力。
Additional information: none
其他信息：无
Person & email address to contact for further information:
联系人和电子邮件地址，以获取更多信息：
Jonathan Rosenberg dynamicsoft 72 Eagle Rock Avenue First Floor East Hanover, NJ 07936 email: jdrosen@dynamicsoft.com jdrosen@alum.mit.edu
Jonathan Rosenberg dynamicsoft 72 Eagle Rock Avenue一楼东汉诺威，NJ 07936电子邮件：jdrosen@dynamicsoft.com jdrosen@alum.mit.edu
Intended usage: COMMON
预期用途：普通
Author/Change controller: This registration is part of the IETF registration tree.
作者/变更控制者：此注册是IETF注册树的一部分。
RTP and SDP Issues: Usage of this format within RTP and the Session Description Protocol (SDP) [6] are fully specified within RFC 2733 [1].
RTP和SDP问题：RTP和会话描述协议（SDP）[6]中此格式的使用在RFC 2733[1]中有详细说明。
6 Security Considerations
6安全考虑
This MIME registration does not introduce any additional security considerations.
此MIME注册不会引入任何其他安全注意事项。
7 Authors' Addresses
7作者地址
Jonathan Rosenberg dynamicsoft 72 Eagle Rock Avenue First Floor East Hanover, NJ 07936
Jonathan Rosenberg dynamicsoft 72 Eagle Rock大道一楼东汉诺威，NJ 07936
EMail: jdrosen@dynamicsoft.com
EMail: jdrosen@dynamicsoft.com
Henning Schulzrinne Columbia University M/S 0401 1214 Amsterdam Ave. New York, NY 10027-7003
亨宁·舒尔兹林内哥伦比亚大学M/S 0401 1214纽约州纽约市阿姆斯特丹大道10027-7003
EMail: schulzrinne@cs.columbia.edu
EMail: schulzrinne@cs.columbia.edu
8 Bibliography
8参考书目
[1] Rosenberg, J. and H. Schulzrinne, "An RTP Payload Format for Generic Forward Error Correction", RFC 2733, December 1999.
[1] Rosenberg，J.和H.Schulzrinne，“通用前向纠错的RTP有效载荷格式”，RFC 2733，1999年12月。
[2] Freed, N., Klensin, J. and J. Postel, "Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures", RFC 2048, November 1996.
[2] Freed，N.，Klensin，J.和J.Postel，“多用途互联网邮件扩展（MIME）第四部分：注册程序”，RFC 20481996年11月。
[3] Casner, S. and P. Hoschka, "MIME type registration of RTP payload formats", Work in Progress.
[3] Casner，S.和P.Hoschka，“RTP有效载荷格式的MIME类型注册”，正在进行中。
[4] Schulzrinne, H., Casner, S., Frederick, R. and V. Jacobson, "RTP: a transport protocol for real-time applications", RFC 1889, January 1996.
[4] Schulzrinne，H.，Casner，S.，Frederick，R.和V.Jacobson，“RTP：实时应用的传输协议”，RFC 1889，1996年1月。
[5] Schulzrinne, H., Casner, S., Frederick, R. and V. Jacobson, "RTP: a transport protocol for real-time applications", Work in Progress.
[5] Schulzrinne，H.，Casner，S.，Frederick，R.和V.Jacobson，“RTP：实时应用的传输协议”，正在进行中。
[6] Handley, M. and V. Jacobson, "SDP: Session Description Protocol", RFC 2327, April 1998.
[6] Handley，M.和V.Jacobson，“SDP：会话描述协议”，RFC 2327，1998年4月。
9 Full Copyright Statement
9完整版权声明
Copyright (C) The Internet Society (2000). All Rights Reserved.
版权所有（C）互联网协会（2000年）。版权所有。
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.
本文件及其译本可复制并提供给他人，对其进行评论或解释或协助其实施的衍生作品可全部或部分编制、复制、出版和分发，不受任何限制，前提是上述版权声明和本段包含在所有此类副本和衍生作品中。但是，不得以任何方式修改本文件本身，例如删除版权通知或对互联网协会或其他互联网组织的引用，除非出于制定互联网标准的需要，在这种情况下，必须遵循互联网标准过程中定义的版权程序，或根据需要将其翻译成英语以外的其他语言。
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.
上述授予的有限许可是永久性的，互联网协会或其继承人或受让人不会撤销。
This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS 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.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。