draft-ietf-avt-rtp-jpeg2000-beam-08.txt   draft-ietf-avt-rtp-jpeg2000-beam-09.txt 
Audio Video Transport A. Leung Audio Video Transport A. Leung
Internet-Draft S. Futemma Internet-Draft S. Futemma
Intended status: Standards Track E. Itakura Intended status: Standards Track E. Itakura
Expires: March 9, 2008 Sony Expires: March 15, 2008 Sony
Sep 6, 2007 Sep 12, 2007
Payload Format for JPEG 2000 Video: Extensions for Scalability and Main Payload Format for JPEG 2000 Video: Extensions for Scalability and Main
Header Recovery Header Recovery
draft-ietf-avt-rtp-jpeg2000-beam-08 draft-ietf-avt-rtp-jpeg2000-beam-09
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 36 skipping to change at page 1, line 36
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on March 9, 2008. This Internet-Draft will expire on March 15, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
Abstract Abstract
This memo describes extended uses for payload header in RFC document: This memo describes extended uses for payload header in RFC document:
"RTP Payload Format for JPEG 2000 Video Streams." For better support "RTP Payload Format for JPEG 2000 Video Streams." For better support
of JPEG 2000 features such as scalability and includes a main header of JPEG 2000 features such as scalability and includes a main header
skipping to change at page 19, line 40 skipping to change at page 19, line 40
o The encoding name in the "a=rtpmap" line of SDP MUST be jpeg2000 o The encoding name in the "a=rtpmap" line of SDP MUST be jpeg2000
(the MIME subtype). (the MIME subtype).
o The clock rate in the "a=rtpmap" line is set according to the o The clock rate in the "a=rtpmap" line is set according to the
"rate" parameter. Senders that wish to use a non-90kHz rate "rate" parameter. Senders that wish to use a non-90kHz rate
SHOULD also offer the same stream using a 90kHz timestamp rate SHOULD also offer the same stream using a 90kHz timestamp rate
with a different RTP payload type allowing graceful fallback to with a different RTP payload type allowing graceful fallback to
90kHz for compatibility. 90kHz for compatibility.
o The OPTIONAL parameters "mhc" or "pt" MUST be included in the o The REQUIRED parameter, "sampling", MUST be included in the
"a=fmtp" line of SDP.
o The OPTIONAL parameters, if presented, MUST be included in the
"a=fmtp" line of SDP. "a=fmtp" line of SDP.
These parameters are expressed as a media type string, in the form of These parameters are expressed as a media type string, in the form of
a semicolon separated list of parameter=value pairs. a semicolon separated list of parameter=value pairs.
Therefore, an example of media representation in SDP is as follows: Therefore, an example of media representation in SDP is as follows:
m=video 49170/2 RTP/AVP 98 m=video 49170/2 RTP/AVP 98
a=rtpmap:98 jpeg2000/90000 a=rtpmap:98 jpeg2000/90000
a=fmtp:98 rate=90000;mhc=1;pt=default; sampling=YCbCr-4:2:0; a=fmtp:98 mhc=1;pt=default; sampling=YCbCr-4:2:0; width=128;
width=128; height=128 height=128
An example for using non-90kHz timestamp is as follows: An example for using non-90kHz timestamp is as follows:
m=video 49170/2 RTP/AVP 98 99 m=video 49170/2 RTP/AVP 98 99
a=rtpmap:98 jpeg2000/27000000 a=rtpmap:98 jpeg2000/27000000
a=rtpmap:99 jpeg2000/90000 a=rtpmap:99 jpeg2000/90000
a=fmtp:98 rate=27000000;mhc=1;pt=default; sampling=YCbCr-4:2:0; a=fmtp:98 mhc=1;pt=default; sampling=YCbCr-4:2:0; width=128;
width=128; height=128 height=128
a=fmtp:99 rate=90000;mhc=1;pt=default; sampling=YCbCr-4:2:0; a=fmtp:99 mhc=1;pt=default; sampling=YCbCr-4:2:0; width=128;
width=128; height=128 height=128
8. Usage with the SDP Offer/Answer Model 8. Usage with the SDP Offer/Answer Model
In addition to SDP Offer/Answer section in RFC XXXY [1]: In addition to SDP Offer/Answer section in RFC XXXY [1]:
When offering JPEG 2000 over RTP using SDP in an Offer/Answer model When offering JPEG 2000 over RTP using SDP in an Offer/Answer model
[6], the following rules and limitations apply: [6], the following rules and limitations apply:
o All parameters MUST have an acceptable value for that parameter. o All parameters MUST have an acceptable value for that parameter.
skipping to change at page 22, line 7 skipping to change at page 22, line 7
several priority-table options (default, progression, layer, several priority-table options (default, progression, layer,
resolution, component) as below: resolution, component) as below:
v=0 v=0
o=alice 2890844526 2890844526 IN IP4 host.example o=alice 2890844526 2890844526 IN IP4 host.example
s= s=
c=IN IP4 host.example c=IN IP4 host.example
t=0 0 t=0 0
m=video 49170 RTP/AVP 98 m=video 49170 RTP/AVP 98
a=rtpmap:98 jpeg2000/90000 a=rtpmap:98 jpeg2000/90000
a=fmtp:98 rate=90000;mhc=1; sampling=YCbCr-4:2:2; interlace=1; a=fmtp:98 mhc=1; sampling=YCbCr-4:2:2; interlace=1;
pt=default,progression,layer,resolution, component; pt=default,progression,layer,resolution, component;
width=720;height=480 width=720;height=480
Bob accepts Main Header Compensation functionality, YCbCr-4:2:2 color Bob accepts Main Header Compensation functionality, YCbCr-4:2:2 color
space, interlace image, default mapping table and replies: space, interlace image, default mapping table and replies:
v=0 v=0
o=bob 2890844730 2890844731 IN IP4 host.example o=bob 2890844730 2890844731 IN IP4 host.example
s= s=
c=IN IP4 host.example c=IN IP4 host.example
t=0 0 t=0 0
m=video 49920 RTP/AVP 98 m=video 49920 RTP/AVP 98
a=rtpmap:98 jpeg2000/90000 a=rtpmap:98 jpeg2000/90000
a=fmtp:98 rate=90000;mhc=1; sampling=YCbCr-4:2:2;interlace=1; a=fmtp:98 mhc=1; sampling=YCbCr-4:2:2;interlace=1;
pt=default;width=720;height=480 pt=default;width=720;height=480
8.1.2. Example 2 8.1.2. Example 2
Alice offers Main Header Compensation, YCbCr 420 color space, Alice offers Main Header Compensation, YCbCr 420 color space,
progressive image with 320-pixel width and 240-pixel height and layer progressive image with 320-pixel width and 240-pixel height and layer
priority-table options as below: priority-table options as below:
v=0 v=0
o=alice 2890844526 2890844526 IN IP4 host.example o=alice 2890844526 2890844526 IN IP4 host.example
s= s=
c=IN IP4 host.example c=IN IP4 host.example
t=0 0 t=0 0
m=video 49170 RTP/AVP 98 m=video 49170 RTP/AVP 98
a=rtpmap:98 jpeg2000/90000 a=rtpmap:98 jpeg2000/90000
a=fmtp:98 rate=90000;mhc=1; sampling=YCbCr-4:2:0; a=fmtp:98 mhc=1; sampling=YCbCr-4:2:0;
pt=layer;width=320;height=240 pt=layer;width=320;height=240
Bob does not accept Main Header Compensation functionality but Bob does not accept Main Header Compensation functionality but
accepts YCbCr-4:2:0 color space,layer based priority mapping and accepts YCbCr-4:2:0 color space,layer based priority mapping and
replies: replies:
v=0 v=0
o=bob 2890844730 2890844731 IN IP4 host.example o=bob 2890844730 2890844731 IN IP4 host.example
s= s=
c=IN IP4 host.example c=IN IP4 host.example
t=0 0 t=0 0
m=video 49920 RTP/AVP 98 m=video 49920 RTP/AVP 98
a=rtpmap:98 jpeg2000/90000 a=rtpmap:98 jpeg2000/90000
a=fmtp:98 rate=90000;mhc=0; sampling=YCbCr-4:2:0; a=fmtp:98 mhc=0; sampling=YCbCr-4:2:0;
pt=layer;width=320;height=240 pt=layer;width=320;height=240
8.1.3. Example 3 8.1.3. Example 3
Alice offers 27 MHz timestamp, Main Header Compensation, YCbCr 420 Alice offers 27 MHz timestamp, Main Header Compensation, YCbCr 420
color space, progressive image with 320-pixel width and 240-pixel color space, progressive image with 320-pixel width and 240-pixel
height and layer priority-table options as below: height and layer priority-table options as below:
v=0 v=0
o=alice 2890844526 2890844526 IN IP4 host.example o=alice 2890844526 2890844526 IN IP4 host.example
s= s=
c=IN IP4 host.example c=IN IP4 host.example
t=0 0 t=0 0
m=video 49170 RTP/AVP 98 99 m=video 49170 RTP/AVP 98 99
a=rtpmap:98 jpeg2000/27000000 a=rtpmap:98 jpeg2000/27000000
a=rtpmap:99 jpeg2000/90000 a=rtpmap:99 jpeg2000/90000
a=fmtp:98 rate=27000000;mhc=1; sampling=YCbCr-4:2:0; a=fmtp:98 mhc=1; sampling=YCbCr-4:2:0;
pt=layer;width=320;height=240 pt=layer;width=320;height=240
a=fmtp:99 rate=90000;mhc=1; sampling=YCbCr-4:2:0; a=fmtp:99 mhc=1; sampling=YCbCr-4:2:0;
pt=layer;width=320;height=240 pt=layer;width=320;height=240
Bob can accept payload type with 27 MHz timestamp, and does not Bob can accept payload type with 27 MHz timestamp, and does not
accept Main Header Compensation functionality but accepts YCbCr-4:2:0 accept Main Header Compensation functionality but accepts YCbCr-4:2:0
color space,layer based priority mapping and replies: color space,layer based priority mapping and replies:
v=0 v=0
o=bob 2890844730 2890844731 IN IP4 host.example o=bob 2890844730 2890844731 IN IP4 host.example
s= s=
c=IN IP4 host.example c=IN IP4 host.example
t=0 0 t=0 0
m=video 49920 RTP/AVP 98 m=video 49920 RTP/AVP 98
a=rtpmap:98 jpeg2000/27000000 a=rtpmap:98 jpeg2000/27000000
a=fmtp:98 rate=27000000;mhc=0; sampling=YCbCr-4:2:0; a=fmtp:98 mhc=0; sampling=YCbCr-4:2:0;
pt=layer;width=320;height=240 pt=layer;width=320;height=240
9. References 9. References
9.1. Normative References 9.1. Normative References
[1] Futemma, "RTP Payload Format for JPEG 2000 Video Streams", [1] Futemma, "RTP Payload Format for JPEG 2000 Video Streams",
RFC XXXY, April 2007. RFC XXXY, April 2007.
[2] Bradner, "Key words for use in RFCs to Indicate Requirement [2] Bradner, "Key words for use in RFCs to Indicate Requirement
 End of changes. 13 change blocks. 
18 lines changed or deleted 22 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/