Internet Engineering Task Force AVT WG Internet Draft J.Rosenberg,H.Schulzrinne draft-ietf-avt-fecmime-01.txt dynamicsoft,Columbia U. March 10, 2000 Expires: September, 2000 Registration of parityfec MIME types STATUS OF THIS MEMO This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet- Drafts as reference material or to cite them other than as work in progress. The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. Abstract The RTP 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. 1 Introduction 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 J.Rosenberg,H.Schulzrinne [Page 1]
Internet Draft FEC MIME March 10, 2000 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. 2 Registration of audio/parityfec To: ietf-types@iana.org Subject: Registration of MIME media type audio/parityfec MIME media type name: audio MIME subtype name: 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. 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. 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]. Security considerations: none Interoperability considerations: none Published specification: This MIME typed is described fully J.Rosenberg,H.Schulzrinne [Page 2]
Internet Draft FEC MIME March 10, 2000 within RFC 2733 [1]. 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 200 Executive Drive Suite 120 West Orange, NJ 07046 email: jdrosen@dynamicsoft.com jdrosen@alum.mit.edu Intended usage: COMMON Author/Change controller: This registration is part of the IETF registration tree. RTP and SDP Issues: Usage of this format within RTP and the Session Description Protocol (SDP) [6] are fully specified within RFC 2733 [1]. 3 Registration of video/parityfec To: ietf-types@iana.org Subject: Registration of MIME media type video/parityfec MIME media type name: video MIME subtype name: parityfec Required parameters: none J.Rosenberg,H.Schulzrinne [Page 3]
Internet Draft FEC MIME March 10, 2000 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. 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. 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]. Security considerations: none Interoperability considerations: none Published specification: This MIME typed is described fully within RFC 2733 [1]. 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 200 Executive Drive Suite 120 J.Rosenberg,H.Schulzrinne [Page 4]
Internet Draft FEC MIME March 10, 2000 West Orange, NJ 07046 email: jdrosen@dynamicsoft.com jdrosen@alum.mit.edu Intended usage: COMMON Author/Change controller: This registration is part of the IETF registration tree. RTP and SDP Issues: Usage of this format within RTP and the Session Description Protocol (SDP) [6] are fully specified within RFC 2733 [1]. 4 Registration of text/parityfec To: ietf-types@iana.org Subject: Registration of MIME media type text/parityfec MIME media type name: text MIME subtype name: 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. 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. Encoding considerations: This format is only defined for J.Rosenberg,H.Schulzrinne [Page 5]
Internet Draft FEC MIME March 10, 2000 transport within the Real Time Transport protocol (RTP) [4,5]. Its transport within RTP is fully specified with RFC 2733 [1]. Security considerations: none Interoperability considerations: none Published specification: This MIME typed is described fully within RFC 2733 [1]. 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 200 Executive Drive Suite 120 West Orange, NJ 07046 email: jdrosen@dynamicsoft.com jdrosen@alum.mit.edu Intended usage: COMMON Author/Change controller: This registration is part of the IETF registration tree. RTP and SDP Issues: Usage of this format within RTP and the Session Description Protocol (SDP) [6] are fully specified within RFC 2733 [1]. J.Rosenberg,H.Schulzrinne [Page 6]
Internet Draft FEC MIME March 10, 2000 5 Registration of application/parityfec To: ietf-types@iana.org Subject: Registration of MIME media type application/parityfec MIME media type name: application MIME subtype name: 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. 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. 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]. Security considerations: none Interoperability considerations: none Published specification: This MIME typed is described fully within RFC 2733 [1]. 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 J.Rosenberg,H.Schulzrinne [Page 7]
Internet Draft FEC MIME March 10, 2000 media stream. Additional information: none Person & email address to contact for further information: Jonathan Rosenberg dynamicsoft 200 Executive Drive Suite 120 West Orange, NJ 07046 email: jdrosen@dynamicsoft.com jdrosen@alum.mit.edu Intended usage: COMMON Author/Change controller: This registration is part of the IETF registration tree. RTP and SDP Issues: Usage of this format within RTP and the Session Description Protocol (SDP) [6] are fully specified within RFC 2733 [1]. 6 Security Considerations This MIME registration does not introduce any addititional security considerations. 7 Author's Addresses Jonathan Rosenberg dynamicsoft 200 Executive Drive Suite 120 West Orange, NJ 07052 email: jdrosen@dynamicsoft.com Henning Schulzrinne J.Rosenberg,H.Schulzrinne [Page 8]
Internet Draft FEC MIME March 10, 2000 Columbia University M/S 0401 1214 Amsterdam Ave. New York, NY 10027-7003 email: schulzrinne@cs.columbia.edu 8 Bibliography [1] J. Rosenberg and H. Schulzrinne, "An RTP payload format for generic forward error correction," Request for Comments (Proposed Standard) 2733, Internet Engineering Task Force, Dec. 1999. [2] N. Freed, J. Klensin, and J. Postel, "Multipurpose internet mail extensions (MIME) part four: Registration procedures," Request for Comments (Best Current Practice) 2048, Internet Engineering Task Force, Nov. 1996. [3] S. Casner and P. Hoschka, "MIME type registration of RTP payload formats," Internet Draft, Internet Engineering Task Force, July 1999. Work in progress. [4] H. Schulzrinne, S. Casner, R. Frederick, and V. Jacobson, "RTP: a transport protocol for real-time applications," Request for Comments (Proposed Standard) 1889, Internet Engineering Task Force, Jan. 1996. [5] H. Schulzrinne, S. Casner, R. Frederick, and V. Jacobson, "RTP: a transport protocol for real-time applications," Internet Draft, Internet Engineering Task Force, July 1999. Work in progress. [6] M. Handley and V. Jacobson, "SDP: session description protocol," Request for Comments (Proposed Standard) 2327, Internet Engineering Task Force, Apr. 1998. J.Rosenberg,H.Schulzrinne [Page 9]
