As per Relevance of the word registration, we have this rfc below:
Network Working Group J.
Request for Comments: 3009
Category: Standards Track H.
Columbia U
November 2000
Registration of parityfec MIME
Status of this
This document specifies an Internet standards track protocol for
Internet community, and requests discussion and suggestions
improvements. Please refer to the current edition of the "
Official Protocol Standards" (STD 1) for the standardization
and status of this protocol. Distribution of this memo is unlimited
Copyright
Copyright (C) The Internet Society (2000). All Rights Reserved
The RTP (Real-time Transport Protocol) payload format for
forward error correction allows RTP participants to improve
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.
document serves as the MIME type registration for those formats
1
The RTP payload format for generic forward error correction [1]
allows RTP participants to improve loss resiliency through the use
traditional parity-based channel codes. This payload format
four new MIME types, audio/parityfec, video/parityfec
text/paritfyfec and application/parityfec. RFC 2048 [2]
procedures for registration of new MIME types within the IETF tree
Furthermore, the Audio/Video Transport working group has
additional procedures that must be followed when registering
payload formats [3]. This document serves as the MIME
registration for those formats based on those procedures
Rosenberg & Schulzrinne Standards Track [Page 1]
RFC 3009 FEC MIME November 2000
2 Registration of audio/
To: ietf-types@iana.
Subject: Registration of MIME media type audio/
MIME media type name:
MIME subtype name:
Required parameters:
Note that [3] mandates that RTP payload formats without
defined rate must define a rate parameter as part of
MIME registration. The payload format for generic
error correction [1] does not specify a rate parameter
However, the rate for FEC data is equal to the rate of
media data it protects
Optional parameters:
Typical optional parameters [3], such as the number
channels, and the duration of audio per packet, do
apply to FEC data. The number of channels is
the same as the media data it protects; the same is
for the duration of audio per packet
Encoding considerations: This format is only defined
transport within the Real Time Transport protocol (RTP
[4,5]. Its transport within RTP is fully specified with
2733 [1].
Security considerations: the same security
apply to these mime registrations as to the payloads
for them, as detailed in RFC 2733.
Interoperability considerations:
Published specification: This MIME type is described
within RFC 2733 [1].
Applications which use this media type: Audio and
streaming tools which seek to improve resiliency to loss
sending additional data with the media stream
Additional information:
Rosenberg & Schulzrinne Standards Track [Page 2]
RFC 3009 FEC MIME November 2000
Person & email address to contact for further information
Jonathan
72 Eagle Rock
First
East Hanover, NJ 07936
email: jdrosen@dynamicsoft.
jdrosen@alum.mit.
Intended usage:
Author/Change controller: This registration is part of the
registration tree
RTP and SDP Issues: Usage of this format within RTP and
Session Description Protocol (SDP) [6] are fully
within RFC 2733 [1].
3 Registration of video/
To: ietf-types@iana.
Subject: Registration of MIME media type video/
MIME media type name:
MIME subtype name:
Required parameters:
Note that [3] mandates that RTP payload formats without
defined rate must define a rate parameter as part of
MIME registration. The payload format for generic
error correction [1] does not specify a rate parameter
However, the rate for FEC data is equal to the rate of
media data it protects
Optional parameters:
Typical optional parameters [3], such as the number
channels, and the duration of audio per packet, do
apply to FEC data. The number of channels is
the same as the media data it protects; the same is
for the duration of video per packet
Rosenberg & Schulzrinne Standards Track [Page 3]
RFC 3009 FEC MIME November 2000
Encoding considerations: This format is only defined
transport within the Real Time Transport protocol (RTP
[4,5]. Its transport within RTP is fully specified with
2733 [1].
Security considerations: the same security
apply to these MIME registrations as to the payloads
for them, as detailed in RFC 2733.
Interoperability considerations:
Published specification: This MIME type is described
within RFC 2733 [1].
Applications which use this media type: Audio and
streaming tools which seek to improve resiliency to loss
sending additional data with the media stream
Additional information:
Person & email address to contact for further information
Jonathan
72 Eagle Rock
First
East Hanover, NJ 07936
email: jdrosen@dynamicsoft.
jdrosen@alum.mit.
Intended usage:
Author/Change controller: This registration is part of the
registration tree
RTP and SDP Issues: Usage of this format within RTP and
Session Description Protocol (SDP) [6] are fully
within RFC 2733 [1].
4 Registration of text/
To: ietf-types@iana.
Subject: Registration of MIME media type text/
MIME media type name:
MIME subtype name:
Rosenberg & Schulzrinne Standards Track [Page 4]
RFC 3009 FEC MIME November 2000
Required parameters:
Note that [3] mandates that RTP payload formats without
defined rate must define a rate parameter as part of
MIME registration. The payload format for generic
error correction [1] does not specify a rate parameter
However, the rate for FEC data is equal to the rate of
media data it protects
Optional parameters:
Typical optional parameters [3], such as the number
channels, and the duration of audio per packet, do
apply to FEC data. The number of channels is
the same as the media data it protects; the same is
for the duration of text per packet
Encoding considerations: This format is only defined
transport within the Real Time Transport protocol (RTP
[4,5]. Its transport within RTP is fully specified with
2733 [1].
Security considerations: the same security
apply to these MIME registrations as to the payloads
for them, as detailed in RFC 2733.
Interoperability considerations:
Published specification: This MIME type is described
within RFC 2733 [1].
Applications which use this media type: Audio, video and
streaming tools which seek to improve resiliency to loss
sending additional data with the media stream
Additional information:
Person & email address to contact for further information
Jonathan
72 Eagle Rock
First
East Hanover, NJ 07936
email: jdrosen@dynamicsoft.
jdrosen@alum.mit.
Intended usage:
Rosenberg & Schulzrinne Standards Track [Page 5]
RFC 3009 FEC MIME November 2000
Author/Change controller: This registration is part of the
registration tree
RTP and SDP Issues: Usage of this format within RTP and
Session Description Protocol (SDP) [6] are fully
within RFC 2733 [1].
5 Registration of application/
To: ietf-types@iana.
Subject: Registration of MIME media type application/
MIME media type name:
MIME subtype name:
Required parameters:
Note that [3] mandates that RTP payload formats without
defined rate must define a rate parameter as part of
MIME registration. The payload format for generic
error correction [1] does not specify a rate parameter
However, the rate for FEC data is equal to the rate of
media data it protects
Optional parameters:
Typical optional parameters [3], such as the number
channels, and the duration of audio per packet, do
apply to FEC data. The number of channels is
the same as the media data it protects; the same is
for the duration of application data per packet
Encoding considerations: This format is only defined
transport within the Real Time Transport protocol (RTP
[4,5]. Its transport within RTP is fully specified with
2733 [1].
Security considerations: the same security
apply to these MIME registrations as to the payloads
for them, as detailed in RFC 2733.
Interoperability considerations:
Published specification: This MIME type is described
within RFC 2733 [1].
Rosenberg & Schulzrinne Standards Track [Page 6]
RFC 3009 FEC MIME November 2000
Applications which use this media type: Audio, video
application streaming tools which seek to
resiliency to loss by sending additional data with
media stream
Additional information:
Person & email address to contact for further information
Jonathan
72 Eagle Rock
First
East Hanover, NJ 07936
email: jdrosen@dynamicsoft.
jdrosen@alum.mit.
Intended usage:
Author/Change controller: This registration is part of the
registration tree
RTP and SDP Issues: Usage of this format within RTP and
Session Description Protocol (SDP) [6] are fully
within RFC 2733 [1].
6 Security
This MIME registration does not introduce any additional
considerations
Rosenberg & Schulzrinne Standards Track [Page 7]
RFC 3009 FEC MIME November 2000
7 Authors'
Jonathan
72 Eagle Rock
First
East Hanover, NJ 07936
EMail: jdrosen@dynamicsoft.
Henning
Columbia
M/S 0401
1214 Amsterdam Ave
New York, NY 10027-7003
EMail: schulzrinne@cs.columbia.
Rosenberg & Schulzrinne Standards Track [Page 8]
RFC 3009 FEC MIME November 2000
8
[1] Rosenberg, J. and H. Schulzrinne, "An RTP Payload Format
Generic Forward Error Correction", RFC 2733, December 1999.
[2] Freed, N., Klensin, J. and J. Postel, "Multipurpose Internet
Extensions (MIME) Part Four: Registration Procedures", RFC 2048,
November 1996.
[3] Casner, S. and P. Hoschka, "MIME type registration of RTP
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
Progress
[6] Handley, M. and V. Jacobson, "SDP: Session Description Protocol",
RFC 2327, April 1998.
Rosenberg & Schulzrinne Standards Track [Page 9]
RFC 3009 FEC MIME November 2000
9 Full Copyright
Copyright (C) The Internet Society (2000). All Rights Reserved
This document and translations of it may be copied and furnished
others, and derivative works that comment on or otherwise explain
or assist in its implementation may be prepared, copied,
and distributed, in whole or in part, without restriction of
kind, provided that the above copyright notice and this paragraph
included on all such copies and derivative works. However,
document itself may not be modified in any way, such as by
the copyright notice or references to the Internet Society or
Internet organizations, except as needed for the purpose
developing Internet standards in which case the procedures
copyrights defined in the Internet Standards process must
followed, or as required to translate it into languages other
English
The limited permissions granted above are perpetual and will not
revoked by the Internet Society or its successors or assigns
This document and the information contained herein is provided on
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Funding for the RFC Editor function is currently provided by
Internet Society
Rosenberg & Schulzrinne Standards Track [Page 10]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
