RFC 2198: RTP Payload for Redundant Audio Data
In plain English — editorial summary, not part of the RFC
This document describes a payload format for use with the real-time transport protocol (RTP), version 2, for encoding redundant audio data. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2198
- Published
- September 1997
- Authors
- C. Perkins; I. Kouvelas; O. Hodson; V. Hardman; M. Handley; J.C. Bolot; A. Vega-Garcia; S. Fosse-Parisis
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 11
- Also known as
- —
- Updated by:
- RFC 6354
Topics
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 2190RTP Payload Format for H.263 Video StreamsCurrent
September 1997
- RFC 2250RTP Payload Format for MPEG1/MPEG2 VideoCurrent
January 1998
- RFC 2343RTP Payload Format for Bundled MPEGCurrent
May 1998
- RFC 2354Options for Repair of Streaming MediaCurrent
June 1998
- RFC 2038RTP Payload Format for MPEG1/MPEG2 VideoObsoleted
October 1996
- RFC 2035RTP Payload Format for JPEG-compressed VideoObsoleted
October 1996
- RFC 2032RTP Payload Format for H.261 Video StreamsObsoleted
October 1996
- RFC 2029RTP Payload Format of Sun's CellB Video EncodingCurrent
October 1996
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?