RFC 4628: RTP Payload Format for H.263 Moving RFC 2190 to Historic Status
In plain English — editorial summary, not part of the RFC
The first RFC that describes RTP payload format for ITU Telecommunication Standardization Sector (ITU-T) recommendation H.263 is RFC 2190. This specification discusses why to move RFC 2190 to historic status. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4628
- Published
- February 2007
- Authors
- R. Even
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rai
- Pages
- 5
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4749RTP Payload Format for the G.729.1 Audio CodecUpdated
October 2006
- RFC 5391RTP Payload Format for ITU-T Recommendation G.711.1Current
November 2008
- RFC 5459G.729.1 RTP Payload Format Update: Discontinuous Transmission (DTX) SupportCurrent
January 2009
- RFC 3047RTP Payload Format for ITU-T Recommendation G.722.1Obsoleted
January 2001
- RFC 4629RTP Payload Format for ITU-T Rec. H.263 VideoCurrent
January 2007
- RFC 4587RTP Payload Format for H.261 Video StreamsCurrent
August 2006
- RFC 4352RTP Payload Format for the Extended Adaptive Multi-Rate Wideband (AMR-WB+) Audio CodecCurrent
January 2006
- RFC 4175RTP Payload Format for Uncompressed VideoUpdated
September 2005
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?