[rfc-dist] RFC 5372 on Payload Format for JPEG 2000 Video: Extensions for Scalability and Main Header Recovery
rfc-editor at rfc-editor.org
Tue Oct 21 09:47:26 PDT 2008
A new Request for Comments is now available in online RFC libraries.
Title: Payload Format for JPEG 2000
Video: Extensions for Scalability and Main
Author: A. Leung, S. Futemma, E. Itakura
Status: Standards Track
Date: October 2008
Mailbox: andrew at ualberta.net,
satosi-f at sm.sony.co.jp,
itakura at sm.sony.co.jp
I-D Tag: draft-ietf-avt-rtp-jpeg2000-beam-11.txt
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
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]
This document is a product of the Audio/Video Transport Working Group of the IETF.
This is now a Proposed Standard Protocol.
STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements. Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol. Distribution of this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
The RFC Editor Team
USC/Information Sciences Institute
More information about the rfc-dist