RFC 3009

RFC 3009: Registration of parityfec MIME types ✨

Okay bestie, here's the vibe check first 🎀. This is RFC 3009, called "Registration of parityfec MIME types". It came out in November 2000 and was written for the Network Working Group by J. Rosenberg (dynamicsoft) and H. Schulzrinne (Columbia U.). It's a Standards Track document. The title block doesn't list any documents it obsoletes or updates, so nothing gets replaced or patched here 💅.

---

Status of This Memo

So this doc is an Internet standards track protocol for the whole Internet community, and it's literally asking for discussion and suggestions 🫶. If you want the current standardization state and status of this protocol, check the current edition of the "Internet Official Protocol Standards" (STD 1). Distribution of this memo is unlimited 🌈.

Copyright Notice

Copyright (C) The Internet Society (2000). All Rights Reserved.

Abstract

Okay so the RTP (Real-time Transport Protocol) payload format for generic forward error correction lets RTP participants boost their loss resiliency using traditional parity-based channel codes 🛡️. It needs four new MIME types: audio/parityfec, video/parityfec, text/parityfec and application/parityfec. And this document is the MIME type registration for all of those formats, so it's giving official paperwork energy 📝.

1 Introduction

The RTP payload format for generic forward error correction [1] is all about helping RTP participants improve loss resiliency with traditional parity-based channel codes 💜. It needs four new MIME types: audio/parityfec, video/parityfec, text/paritfyfec and application/parityfec. Next, RFC 2048 [2] is the one that explains how to register new MIME types inside the IETF tree 🌸. The Audio/Video Transport working group also came up with extra rules you have to follow when registering RTP payload formats [3], so this document registers those formats by following those rules ✨.

2 Registration of audio/parityfec

Here's the registration form for 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

Quick heads up: [3] says RTP payload formats without a defined rate must define a rate parameter as part of their MIME registration 📏. The generic FEC payload format [1] doesn't specify a rate parameter, but the rate for FEC data is equal to the rate of the media data it protects. Iconic, honestly 🔥.

Optional parameters: none

Typical optional parameters from [3], like the number of channels and the duration of audio per packet, don't apply to FEC data 🙈. The number of channels is basically the same as the media data it protects, and the same goes for the duration of audio per packet.

Encoding considerations: This format is only defined for transport inside 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 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 that want 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: Using this format within RTP and the Session Description Protocol (SDP) [6] is fully specified within RFC 2733 [1] 🫶.

3 Registration of video/parityfec

Next up is the form for 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

Same deal as the audio one, bestie 🧚. [3] says RTP payload formats without a defined rate must define a rate parameter as part of their MIME registration. The generic FEC payload format [1] doesn't specify a rate parameter, but the rate for FEC data is equal to the rate of the media data it protects ✨.

Optional parameters: none

Typical optional parameters from [3], like the number of channels and the duration of audio per packet, don't apply to FEC data 🌸. The number of channels is effectively the same as the media data it protects, and the same is true for the duration of video per packet.

Encoding considerations: This format is only defined for transport inside 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 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 that want 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: Using this format within RTP and the Session Description Protocol (SDP) [6] is fully specified within RFC 2733 [1] 💅.

7 Authors' Addresses ✨

the authors, the people who wrote this, and how to find them 💌

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 📚

okay the reading list, and yes every single one of these is cited, no cap 🤓

[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 🎀

the legal bit, but make it cute 💅

Copyright (C) The Internet Society (2000). All Rights Reserved.

okay so anyone can copy this document and share it, and people can even write derivative works that comment on it, explain it, or help people implement it. they can be published and distributed, in whole or in part, without restriction of any kind, as long as the copyright notice and this paragraph are included on every copy and derivative work. ✨

however, the document itself may not be modified in any way. that means you can't remove the copyright notice or the references to the Internet Society or other Internet organizations. the exceptions are when it's needed for developing Internet standards, in which case the copyright procedures defined in the Internet Standards process must be followed, or when it's translated into a language other than English. 🌸

the limited permissions above are perpetual and will not be revoked by the Internet Society or its successors or assigns. forever and ever, bestie 🫶

and this document and the information in it are 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. thank you to them for keeping the lights on ✨💜