draft-ietf-avt-rtp-jpeg2000-beam-06.txt   draft-ietf-avt-rtp-jpeg2000-beam-07.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: October 19, 2007 Sony Expires: January 21, 2008 Sony
April 17, 2007 July 20, 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-06 draft-ietf-avt-rtp-jpeg2000-beam-07
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 October 19, 2007. This Internet-Draft will expire on January 21, 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 3, line 32 skipping to change at page 3, line 32
3.4. Resolution Based Ordering . . . . . . . . . . . . . . . . 10 3.4. Resolution Based Ordering . . . . . . . . . . . . . . . . 10
3.5. Component Based Ordering . . . . . . . . . . . . . . . . . 11 3.5. Component Based Ordering . . . . . . . . . . . . . . . . . 11
4. JPEG 2000 Main Header Compensation Scheme . . . . . . . . . . 12 4. JPEG 2000 Main Header Compensation Scheme . . . . . . . . . . 12
4.1. Sender Processing . . . . . . . . . . . . . . . . . . . . 12 4.1. Sender Processing . . . . . . . . . . . . . . . . . . . . 12
4.2. Receiver Processing . . . . . . . . . . . . . . . . . . . 12 4.2. Receiver Processing . . . . . . . . . . . . . . . . . . . 12
5. Security Consideration . . . . . . . . . . . . . . . . . . . . 14 5. Security Consideration . . . . . . . . . . . . . . . . . . . . 14
6. Congestion Control . . . . . . . . . . . . . . . . . . . . . . 15 6. Congestion Control . . . . . . . . . . . . . . . . . . . . . . 15
7. IANA Consideration . . . . . . . . . . . . . . . . . . . . . . 16 7. IANA Consideration . . . . . . . . . . . . . . . . . . . . . . 16
7.1. Media Type Registration . . . . . . . . . . . . . . . . . 16 7.1. Media Type Registration . . . . . . . . . . . . . . . . . 16
7.2. SDP Parameters . . . . . . . . . . . . . . . . . . . . . . 19 7.2. SDP Parameters . . . . . . . . . . . . . . . . . . . . . . 19
8. Usage with the SDP Offer/Answer Model . . . . . . . . . . . . 20 8. Usage with the SDP Offer/Answer Model . . . . . . . . . . . . 21
8.1. Examples . . . . . . . . . . . . . . . . . . . . . . . . . 20 8.1. Examples . . . . . . . . . . . . . . . . . . . . . . . . . 21
8.1.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . 20 8.1.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . 21
8.1.2. Example 2 . . . . . . . . . . . . . . . . . . . . . . 21 8.1.2. Example 2 . . . . . . . . . . . . . . . . . . . . . . 22
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 23 8.1.3. Example 3 . . . . . . . . . . . . . . . . . . . . . . 23
9.1. Normative References . . . . . . . . . . . . . . . . . . . 23 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 24
9.2. Informative References . . . . . . . . . . . . . . . . . . 23 9.1. Normative References . . . . . . . . . . . . . . . . . . . 24
Appendix A. Sample Headers in Detail . . . . . . . . . . . . . . 24 9.2. Informative References . . . . . . . . . . . . . . . . . . 24
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 32 Appendix A. Sample Headers in Detail . . . . . . . . . . . . . . 25
Intellectual Property and Copyright Statements . . . . . . . . . . 33 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 33
Intellectual Property and Copyright Statements . . . . . . . . . . 34
1. Introduction 1. Introduction
This document is an extension of: "RTP Payload Format for JPEG 2000 This document is an extension of: "RTP Payload Format for JPEG 2000
Video Streams" [1]. These are additional mechanisms that can be used Video Streams" [1]. These are additional mechanisms that can be used
with certain parts of the header in [1] to support JPEG 2000 features with certain parts of the header in [1] to support JPEG 2000 features
such as scalability and a main header compensation method. These such as scalability and a main header compensation method. These
mechanisms are described in detail in this document. mechanisms are described in detail in this document.
1.1. History 1.1. History
skipping to change at page 19, line 28 skipping to change at page 19, line 28
In addition to SDP Parameters section in [1]: In addition to SDP Parameters section in [1]:
The media type video/jpeg2000 string is mapped to fields in the The media type video/jpeg2000 string is mapped to fields in the
Session Description Protocol (SDP) [5] as follows: Session Description Protocol (SDP) [5] as follows:
o The media name in the "m=" line of SDP MUST be video. o The media name in the "m=" line of SDP MUST be video.
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 MUST be 90000. o The clock rate in the "a=rtpmap" line SHOULD be 90000. Senders
that wish to use a non-90kHz rate SHOULD also offer the same
stream using a 90kHz timestamp rate with a different RTP payload
type allowing graceful fallback to 90kHz for compatibility.
o The OPTIONAL parameters "mhc" or "pt" MUST be included in the o The OPTIONAL parameters "mhc" or "pt" 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 mhc=1;pt=default; sampling=YCbCr-4:2:0; width=128; a=fmtp:98 mhc=1;pt=default; sampling=YCbCr-4:2:0; width=128;
height=128 height=128
An example for using non-90kHz timestamp is as follows:
m=video 49170/2 RTP/AVP 98 99
a=rtpmap:98 jpeg2000/27000000
a=rtpmap:99 jpeg2000/90000
a=fmtp:98 mhc=1;pt=default; sampling=YCbCr-4:2:0; width=128;
height=128
a=fmtp:99 mhc=1;pt=default; sampling=YCbCr-4:2:0; width=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.
o All parameters MUST correspond to the parameters of the payload. o All parameters MUST correspond to the parameters of the payload.
skipping to change at page 23, line 5 skipping to change at page 23, line 6
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 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
Alice offers 27 MHz timestamp, Main Header Compensation, YCbCr 420
color space, progressive image with 320-pixel width and 240-pixel
height and layer priority-table options as below:
v=0
o=alice 2890844526 2890844526 IN IP4 host.example
s=
c=IN IP4 host.example
t=0 0
m=video 49170 RTP/AVP 98 99
a=rtpmap:98 jpeg2000/27000000
a=rtpmap:99 jpeg2000/90000
a=fmtp:98 mhc=1; sampling=YCbCr-4:2:0;
pt=layer;width=320;height=240
a=fmtp:99 mhc=1; sampling=YCbCr-4:2:0;
pt=layer;width=320;height=240
Bob can accept payload type with 27 MHz timestamp, and does not
accept Main Header Compensation functionality but accepts YCbCr-4:2:0
color space,layer based priority mapping and replies:
v=0
o=bob 2890844730 2890844731 IN IP4 host.example
s=
c=IN IP4 host.example
t=0 0
m=video 49920 RTP/AVP 98
a=rtpmap:98 jpeg2000/27000000
a=fmtp:98 mhc=0; sampling=YCbCr-4:2:0;
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
Levels", RFC 2119, March 1997. Levels", RFC 2119, March 1997.
skipping to change at page 23, line 32 skipping to change at page 24, line 32
[5] Handley and Jacobson, "SDP: Session Description Protocol", [5] Handley and Jacobson, "SDP: Session Description Protocol",
RFC 4566, July 2006. RFC 4566, July 2006.
[6] Rosenberg and Schulzrinne, "An Offer/Answer Model with Session [6] Rosenberg and Schulzrinne, "An Offer/Answer Model with Session
Description Protocol (SDP)", RFC 3264, June 2002. Description Protocol (SDP)", RFC 3264, June 2002.
[7] Freed and Klensin, "Media Type Specifications and Registration [7] Freed and Klensin, "Media Type Specifications and Registration
Procedures", RFC 4288, December 2005. Procedures", RFC 4288, December 2005.
[8] Casner and Hoschka, "MIME Type Registration of RTP Payload [8] Casner, "Media Type Registration of RTP Payload Formats",
Formats", RFC 3555, July 2003. RFC 4855, February 2007.
9.2. Informative References 9.2. Informative References
[9] Perkins and Gharai, "RTP Payload Format for Uncompressed Video", [9] Perkins and Gharai, "RTP Payload Format for Uncompressed Video",
RFC 4175, September 2005. RFC 4175, September 2005.
Appendix A. Sample Headers in Detail Appendix A. Sample Headers in Detail
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
 End of changes. 8 change blocks. 
17 lines changed or deleted 64 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/