RFC 5404: RTP Payload Format for G.719
In plain English — editorial summary, not part of the RFC
This document specifies the payload format for packetization of the G.719 full-band codec encoded audio signals into the Real-time Transport Protocol (RTP). The payload format supports transmission of multiple channels, multiple frames per payload, and interleaving. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5404
- Published
- January 2009
- Authors
- M. Westerlund; I. Johansson
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 27
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5459G.729.1 RTP Payload Format Update: Discontinuous Transmission (DTX) SupportCurrent
January 2009
- RFC 4749RTP Payload Format for the G.729.1 Audio CodecUpdated
October 2006
- RFC 4628RTP Payload Format for H.263 Moving RFC 2190 to Historic StatusCurrent
February 2007
- RFC 6185RTP Payload Format for H.264 Reduced-Complexity Decoding Operation (RCDO) VideoCurrent
May 2011
- RFC 3047RTP Payload Format for ITU-T Recommendation G.722.1Obsoleted
January 2001
- RFC 5431Diameter ITU-T Rw Policy Enforcement Interface ApplicationCurrent
March 2009
- RFC 5317Joint Working Team (JWT) Report on MPLS Architectural Considerations for a Transport ProfileCurrent
February 2009
- RFC 5654Requirements of an MPLS Transport ProfileCurrent
September 2009
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?