RFC 3009: Registration of parityfec MIME types
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 5109.
Current document in this lineage: RFC 5109 — RTP Payload Format for Generic Forward Error Correction
In plain English — editorial summary, not part of the RFC
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. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3009
- Published
- November 2000
- Authors
- J. Rosenberg; H. Schulzrinne
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 10
- Also known as
- —
- Obsoleted by:
- RFC 5109
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 2733 (1999)
- RFC 3009 (2000)
- RFC 5109 (2007) ✓
Read the full history of RTP Payload Format for Generic Forward Error Correction →
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3676The Text/Plain Format and DelSp ParametersCurrent
February 2004
- RFC 9996Media Types for Protocol BuffersCurrent
July 2026
- RFC 3003The audio/mpeg Media TypeCurrent
November 2000
- RFC 3016RTP Payload Format for MPEG-4 Audio/Visual StreamsObsoleted
November 2000
- RFC 3204MIME media types for ISUP and QSIG ObjectsUpdated
December 2001
- RFC 2646The Text/Plain Format ParameterObsoleted
August 1999
- RFC 3420Internet Media Type message/sipfragCurrent
November 2002
- RFC 3555MIME Type Registration of RTP Payload FormatsObsoleted
July 2003
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?