RFC 5372: Payload Format for JPEG 2000 Video: Extensions for Scalability and Main Header Recovery
In plain English — editorial summary, not part of the RFC
This memo describes extended uses for the payload header in "RTP Payload Format for JPEG 2000 Video Streams" as specified in RFC 5371, for better support of JPEG 2000 features such as scalability and main header recovery. This memo must be accompanied with a complete implementation of "RTP Payload Format for JPEG 2000 Video Streams". That document is a complete description of the payload header and signaling, this document only describes additional processing for the payload header. There is an additional media type and Session Description Protocol (SDP) marker signaling for implementations of this document. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5372
- Published
- October 2008
- Authors
- A. Leung; S. Futemma; E. Itakura
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 26
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5371RTP Payload Format for JPEG 2000 Video StreamsCurrent
October 2008
- RFC 5391RTP Payload Format for ITU-T Recommendation G.711.1Current
November 2008
- RFC 5285A General Mechanism for RTP Header ExtensionsObsoleted
July 2008
- RFC 5459G.729.1 RTP Payload Format Update: Discontinuous Transmission (DTX) SupportCurrent
January 2009
- RFC 5584RTP Payload Format for the Adaptive TRansform Acoustic Coding (ATRAC) FamilyCurrent
July 2009
- RFC 5117RTP TopologiesObsoleted
January 2008
- RFC 5760RTP Control Protocol (RTCP) Extensions for Single-Source Multicast Sessions with Unicast FeedbackUpdated
February 2010
- RFC 5968Guidelines for Extending the RTP Control Protocol (RTCP)Current
September 2010
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?