Registration of parityfec MIME types
obsoleted by
- rfc-5109 — RTP Payload Format for Generic Forward Error Correction
Extracted elements (9)
Although AVT procedures mandate that RTP payload formats without a defined rate must define a rate parameter, no rate parameter is defined for parityfec because the FEC data rate is inherently equal to the rate of the media it protects, making a separate parameter redundant.
Typical optional parameters such as number of channels and duration per packet are omitted from the parityfec registrations because these values are effectively the same as those of the protected media stream, so they add no independent information.
Usage of all four parityfec MIME types within RTP and SDP is fully specified within RFC 2733; implementors must consult that document for interoperability details.
Each parityfec MIME type is only defined for transport within RTP; its use within RTP is fully specified by RFC 2733.
Registers the MIME media type application/parityfec for RTP-transported parity-based forward error correction application data. The type has no required or optional parameters; its rate equals that of the protected media.
Registers the MIME media type audio/parityfec for RTP-transported parity-based forward error correction audio data. The type has no required or optional parameters; its rate equals that of the protected media.
Registers the MIME media type text/parityfec for RTP-transported parity-based forward error correction text data. The type has no required or optional parameters; its rate equals that of the protected media.
Registers the MIME media type video/parityfec for RTP-transported parity-based forward error correction video data. The type has no required or optional parameters; its rate equals that of the protected media.
The parityfec MIME registrations introduce no additional security considerations beyond those that apply to the payloads themselves, as detailed in RFC 2733.