ObsoletedPROPOSED STANDARDIETF stream

RFC 2733: An RTP Payload Format for Generic Forward Error Correction

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

This document specifies a payload format for generic forward error correction of media encapsulated in RTP. [STANDARDS-TRACK]

Document record

Document ID
RFC2733
Published
December 1999
Authors
J. Rosenberg; H. Schulzrinne
Status
PROPOSED STANDARD
Stream
IETF
Area
rai
Pages
26
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.

  1. RFC 2733 (1999)
  2. RFC 3009 (2000)
  3. 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.

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?

canonical URL: /rfc/2733-an-rtp-payload-format-for-generic-forward-error-correction