RFC 4175: RTP Payload Format for Uncompressed Video
In plain English — editorial summary, not part of the RFC
This memo specifies a packetization scheme for encapsulating uncompressed video into a payload format for the Real-time Transport Protocol, RTP. It supports a range of standard- and high-definition video formats, including common television formats such as ITU BT.601, and standards from the Society of Motion Picture and Television Engineers (SMPTE), such as SMPTE 274M and SMPTE 296M. The format is designed to be applicable and extensible to new video formats as they are developed. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4175
- Published
- September 2005
- Authors
- L. Gharai; C. Perkins
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 18
- Also known as
- —
- Updated by:
- RFC 4421
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 3497RTP Payload Format for Society of Motion Picture and Television Engineers (SMPTE) 292M VideoCurrent
March 2003
- RFC 4170Tunneling Multiplexed Compressed RTP (TCRTP)Current
November 2005
- RFC 4184RTP Payload Format for AC-3 AudioCurrent
October 2005
- RFC 4102Registration of the text/red MIME Sub-TypeUpdated
June 2005
- RFC 4060RTP Payload Formats for European Telecommunications Standards Institute (ETSI) European Standard ES 202 050, ES 202 211, and ES 202 212 Distributed Speech Recognition EncodingCurrent
May 2005
- RFC 4352RTP Payload Format for the Extended Adaptive Multi-Rate Wideband (AMR-WB+) Audio CodecCurrent
January 2006
- RFC 3952Real-time Transport Protocol (RTP) Payload Format for internet Low Bit Rate Codec (iLBC) SpeechCurrent
December 2004
- RFC 4573MIME Type Registration for RTP Payload Format for H.224Current
July 2006
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?