RFC 3009 PROPOSED STANDARD RTP · MIME · ERROR CORRECTION
Registration of parityfec MIME types
Names for forward error correction streams in RTP
RFC EDITOR
Rosenberg, J. and H. Schulzrinne, "Registration of parityfec MIME types", RFC 3009, DOI 10.17487/RFC3009, November 2000, <https://www.rfc-editor.org/info/rfc3009>.
BIBTEX
@misc{rfc3009,
series = {Request for Comments},
number = 3009,
howpublished = {RFC 3009},
publisher = {RFC Editor},
doi = {10.17487/RFC3009},
url = {https://www.rfc-editor.org/info/rfc3009},
author = {J. Rosenberg and H. Schulzrinne},
title = {{Registration of parityfec MIME types}},
pagetotal = 10,
year = 2000,
month = nov,
} LINEAGE · FROM THE RFC INDEXOpen full graph →
RFC text
Contents
Network Working Group J. Rosenberg
Request for Comments: 3009 dynamicsoft
Category: Standards Track H. Schulzrinne
Columbia U.
November 2000
Registration of parityfec MIME types
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.
Copyright Notice
Copyright (C) The Internet Society (2000). All Rights Reserved.
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.
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
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: the same security considerations
apply to these mime registrations as to the payloads for
for them, as detailed in RFC 2733.
Interoperability considerations: none
Published specification: This MIME type 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
72 Eagle Rock Avenue
First Floor
East Hanover, NJ 07936
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
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: the same security considerations
apply to these MIME registrations as to the payloads for
for them, as detailed in RFC 2733.
Interoperability considerations: none
Published specification: This MIME type 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
72 Eagle Rock Avenue
First Floor
East Hanover, NJ 07936
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
transport within the Real Time Transport protocol (RTP)
[4,5]. Its transport within RTP is fully specified with 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.
Interoperability considerations: none
Published specification: This MIME type 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
72 Eagle Rock Avenue
First Floor
East Hanover, NJ 07936
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].
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: the same security considerations
apply to these MIME registrations as to the payloads for
for them, as detailed in RFC 2733.
Interoperability considerations: none
Published specification: This MIME type 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
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
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 additional security
considerations.
7 Authors' Addresses
Jonathan Rosenberg
dynamicsoft
72 Eagle Rock Avenue
First Floor
East Hanover, NJ 07936
EMail: jdrosen@dynamicsoft.com
Henning Schulzrinne
Columbia University
M/S 0401
1214 Amsterdam Ave.
New York, NY 10027-7003
EMail: schulzrinne@cs.columbia.edu
8 Bibliography
[1] Rosenberg, J. and H. Schulzrinne, "An RTP Payload Format for
Generic Forward Error Correction", RFC 2733, December 1999.
[2] Freed, N., Klensin, J. and J. Postel, "Multipurpose Internet Mail
Extensions (MIME) Part Four: Registration Procedures", RFC 2048,
November 1996.
[3] Casner, S. and P. Hoschka, "MIME type registration of RTP payload
formats", Work in Progress.
[4] Schulzrinne, H., Casner, S., Frederick, R. and V. Jacobson,
"RTP: a transport protocol for real-time applications", RFC 1889,
January 1996.
[5] Schulzrinne, H., Casner, S., Frederick, R. and V. Jacobson, "RTP:
a transport protocol for real-time applications", Work in
Progress.
[6] Handley, M. and V. Jacobson, "SDP: Session Description Protocol",
RFC 2327, April 1998.
9 Full Copyright Statement
Copyright (C) The Internet Society (2000). All Rights Reserved.
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.
AI ELI5
On this page
PROBLEMRTP streams that carry parity-based forward error correction data need standardized MIME type labels so applications can recognize and handle them correctly.
MECHANISMRFC 3009 registers four MIME types (audio/parityfec, video/parityfec, text/parityfec, application/parityfec) that identify FEC streams for different media types when carried in RTP.
WHY IT MATTERSApplications can now use these MIME labels to signal and negotiate FEC streams in RTP sessions, improving error resilience. RFC 5109 later superseded it with an improved format.
§1Introduction
RFC 2733 defines a generic RTP payload format for forward error correction (FEC) that uses traditional parity-based channel codes. This technique allows RTP participants to improve loss resiliency by computing and sending additional repair data alongside the original media. To support this, four new MIME types are needed to identify FEC streams: audio/parityfec, video/parityfec, text/parityfec, and application/parityfec. This RFC registers those types following IETF procedures.
Some RTP messages include extra repair data to help rebuild lost pieces. These registrations give those streams official names.
§2MIME Type Registrations
The RFC registers four MIME types, one for each media class. Each registration follows the same pattern and references RFC 2733 for the actual format specification.
Key points across all registrations: the FEC data has no required parameters, as the FEC frame rate matches the original media's rate. The encoding is only defined for RTP transport. Security considerations reference RFC 2733. All four types are intended for common use in streaming applications that need loss recovery.
Four official names are registered, one each for audio, video, text, and application repair data streams. They all follow the same rules.
§3Security Considerations
This MIME registration itself does not introduce additional security considerations beyond those in RFC 2733, which defines the actual FEC payload format. Security properties of FEC streams depend on the underlying media protection and the RTP security mechanisms in use.
The registration doesn't add any new security problems. Any security issues would come from the original protection method used by the repair data.
§5References
[1]RFC 2733Rosenberg, J. and H. Schulzrinne, "An RTP Payload Format for Generic Forward Error Correction", RFC 2733, December 1999.December 1999[2]RFC 2048Freed, N., Klensin, J. and J. Postel, "Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures", RFC 2048, November 1996.November 1996
[3]Casner, S. and P. Hoschka, "MIME type registration of RTP payload formats", Work in Progress.
[4]RFC 1889Schulzrinne, H., Casner, S., Frederick, R. and V. Jacobson, "RTP: a transport protocol for real-time applications", RFC 1889, January 1996.January 1996[6]RFC 2327Handley, M. and V. Jacobson, "SDP: Session Description Protocol", RFC 2327, April 1998.April 1998