RFC 4425: RTP Payload Format for Video Codec 1 (VC-1)
In plain English — editorial summary, not part of the RFC
This memo specifies an RTP payload format for encapsulating Video Codec 1 (VC-1) compressed bit streams, as defined by the Society of Motion Picture and Television Engineers (SMPTE) standard, SMPTE 421M. SMPTE is the main standardizing body in the motion imaging industry, and the SMPTE 421M standard defines a compressed video bit stream format and decoding process for television. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4425
- Published
- February 2006
- Authors
- A. Klemets
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 36
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4424Real-Time Transport Protocol (RTP) Payload Format for the Variable-Rate Multimode Wideband (VMR-WB) Extension Audio CodecCurrent
February 2006
- RFC 4421RTP Payload Format for Uncompressed Video: Additional Colour Sampling ModesCurrent
February 2006
- RFC 4415IANA Registration for Enumservice VoiceUpdated
February 2006
- RFC 4414An ENUM Registry Type for the Internet Registry Information Service (IRIS)Current
February 2006
- RFC 4412Communications Resource Priority for the Session Initiation Protocol (SIP)Updated
February 2006
- RFC 4411Extending the Session Initiation Protocol (SIP) Reason Header for Preemption EventsCurrent
February 2006
- RFC 4453Requirements for Consent-Based Communications in the Session Initiation Protocol (SIP)Current
April 2006
- RFC 4396RTP Payload Format for 3rd Generation Partnership Project (3GPP) Timed TextCurrent
February 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?