[rfc-dist] RFC 5371 on RTP Payload Format for JPEG 2000 Video Streams

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Tue Oct 21 09:47:03 PDT 2008

A new Request for Comments is now available in online RFC libraries.

        RFC 5371

        Title:      RTP Payload Format for JPEG 
                    2000 Video Streams 
        Author:     S. Futemma, E. Itakura, A. Leung
        Status:     Standards Track
        Date:       October 2008
        Mailbox:    satosi-f at sm.sony.co.jp, 
                    itakura at sm.sony.co.jp, 
                    andrew at ualberta.net
        Pages:      31
        Characters: 62655
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-avt-rtp-jpeg2000-20.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5371.txt

This memo describes an RTP payload format for the ISO/IEC
International Standard 15444-1 | ITU-T Rec. T.800, better known as
JPEG 2000.  JPEG 2000 features are considered in the design of this
payload format.  JPEG 2000 is a truly scalable compression technology
allowing applications to encode once and decode many different ways.
The JPEG 2000 video stream is formed by extending from a single image
to a series of JPEG 2000 images.  [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
unlimited distribution.

The RFC Editor Team
USC/Information Sciences Institute

More information about the rfc-dist mailing list