draft-ietf-avt-rtp-jpeg2000-beam-09.txt   draft-ietf-avt-rtp-jpeg2000-beam-10.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 15, 2008 Sony Expires: October 26, 2008 Sony
Sep 12, 2007 Apr 24, 2008
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-09 draft-ietf-avt-rtp-jpeg2000-beam-10
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 15, 2008. This Internet-Draft will expire on October 26, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2008).
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 main header recovery.
recovery method.
This memo must be accompanied with a complete implementation of "RTP This memo must be accompanied with a complete implementation of "RTP
Payload Format for JPEG 2000 Video Streams." That document is a Payload Format for JPEG 2000 Video Streams." That document is a
complete description of the payload header and signaling, this complete description of the payload header and signaling, this
document only describes additional processing for the payload header. document only describes additional processing for the payload header.
There is an additional media type and SDP marker signaling for There is an additional media type and SDP marker signaling for
implementations of this document. implementations of this document.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1. History . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.1. Description of the Mechanisms . . . . . . . . . . . . . . 4
1.2. Description of the Mechanisms . . . . . . . . . . . . . . 4 1.1.1. Main Header Compensation . . . . . . . . . . . . . . . 4
1.2.1. Main Header Compensation . . . . . . . . . . . . . . . 4 1.1.2. Priority Table . . . . . . . . . . . . . . . . . . . . 4
1.2.2. Priority Table . . . . . . . . . . . . . . . . . . . . 4 1.2. Motivations for Priority Field coding . . . . . . . . . . 5
1.3. Motivations for Priority Field coding . . . . . . . . . . 5 1.2.1. Scenario: Just enough resolution . . . . . . . . . . . 5
1.3.1. Scenario: Just enough resolution . . . . . . . . . . . 5 1.2.2. Scenario: Multiple clients, single source . . . . . . 5
1.3.2. Scenario: Multiple clients, single source . . . . . . 5 1.3. Conventions Used in This Document . . . . . . . . . . . . 5
1.4. Conventions Used in This Document . . . . . . . . . . . . 6 2. Payload Format Enhanced Processing . . . . . . . . . . . . . . 6
2. Payload Format Enhanced Processing . . . . . . . . . . . . . . 7 2.1. Enhanced Processing Markers . . . . . . . . . . . . . . . 6
2.1. Enhanced Processing Markers . . . . . . . . . . . . . . . 7 3. Priority Mapping Table . . . . . . . . . . . . . . . . . . . . 8
3. Priority Mapping Table . . . . . . . . . . . . . . . . . . . . 9 3.1. Packet Number Based Ordering . . . . . . . . . . . . . . . 8
3.1. Packet Number Based Ordering . . . . . . . . . . . . . . . 9 3.2. Progression Based Ordering . . . . . . . . . . . . . . . . 8
3.2. Progression Based Ordering . . . . . . . . . . . . . . . . 9
3.3. Layer Based Ordering . . . . . . . . . . . . . . . . . . . 10 3.3. Layer Based Ordering . . . . . . . . . . . . . . . . . . . 10
3.4. Resolution Based Ordering . . . . . . . . . . . . . . . . 10 3.4. Resolution Based Ordering . . . . . . . . . . . . . . . . 10
3.5. Component Based Ordering . . . . . . . . . . . . . . . . . 11 3.5. Component Based Ordering . . . . . . . . . . . . . . . . . 10
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. Media Type Registration . . . . . . . . . . . . . . . . . . . 14
6. Congestion Control . . . . . . . . . . . . . . . . . . . . . . 15 6. SDP Parameters . . . . . . . . . . . . . . . . . . . . . . . . 15
7. IANA Consideration . . . . . . . . . . . . . . . . . . . . . . 16 6.1. Mapping of the optional parameters to SDP . . . . . . . . 15
7.1. Media Type Registration . . . . . . . . . . . . . . . . . 16 6.2. Usage with the SDP Offer/Answer Model . . . . . . . . . . 15
7.2. SDP Parameters . . . . . . . . . . . . . . . . . . . . . . 19 6.2.1. Examples . . . . . . . . . . . . . . . . . . . . . . . 16
8. Usage with the SDP Offer/Answer Model . . . . . . . . . . . . 21 7. IANA Consideration . . . . . . . . . . . . . . . . . . . . . . 19
8.1. Examples . . . . . . . . . . . . . . . . . . . . . . . . . 21 8. Security Consideration . . . . . . . . . . . . . . . . . . . . 20
8.1.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . 21 9. Congestion Control . . . . . . . . . . . . . . . . . . . . . . 21
8.1.2. Example 2 . . . . . . . . . . . . . . . . . . . . . . 22 10. Normative References . . . . . . . . . . . . . . . . . . . . . 22
8.1.3. Example 3 . . . . . . . . . . . . . . . . . . . . . . 23 Appendix A. Sample Headers in Detail . . . . . . . . . . . . . . 23
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 24 A.1. Sample 1: Progressive image with single tile, 3500
9.1. Normative References . . . . . . . . . . . . . . . . . . . 24 bytes (i.e. thumbnail) . . . . . . . . . . . . . . . . . . 23
9.2. Informative References . . . . . . . . . . . . . . . . . . 24 A.2. Smaple 2: Image with 4 tiles . . . . . . . . . . . . . . . 25
Appendix A. Sample Headers in Detail . . . . . . . . . . . . . . 25 A.3. Sample 3: Packing multiple tiles in single payload,
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 33 fragmented header. No header compensation, progressive
Intellectual Property and Copyright Statements . . . . . . . . . . 34 image . . . . . . . . . . . . . . . . . . . . . . . . . . 26
A.4. Sample 4: Interlace image, single tile . . . . . . . . . . 28
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 32
Intellectual Property and Copyright Statements . . . . . . . . . . 33
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 which can be
with certain parts of the header in [1] to support JPEG 2000 features used with certain parts of the header in [1] to support JPEG 2000
such as scalability and a main header compensation method. These features such as: scalability and a main header compensation method.
mechanisms are described in detail in this document. These mechanisms are described in detail in this document.
1.1. History
In the development of RFC XXXY [1], there was an issue of IPR claims These are optional extensions to RFC XXXY [1].which one may use to
on certain mechanisms with main header compensation, priority table make better use of JPEG 2000 features. These extensions are not
usage, etc. in RFC XXXY [1]. As these are not "essential" to the required for any implementations of RFC XXXY[1].
core RTP format of RFC XXXY [1] and only describes a mechanism, it
was decided that splitting these mechanisms from the core JPEG 2000
RTP format in to a separate document. This is the document
describing the IPR related mechanisms for main header recover and
priority table usage.
1.2. Description of the Mechanisms 1.1. Description of the Mechanisms
1.2.1. Main Header Compensation 1.1.1. Main Header Compensation
JPEG 2000's scalable coding scheme allows for decompressing truncated JPEG 2000 has a scalable coding scheme which allows for decompressing
or partial data streams but only when the main header is present. If truncated or partial data streams but only when the main header is
the header is lost, the data is useless. With JPEG 2000 video present. If the header is lost, the data is useless. With JPEG 2000
coding, coding parameters between frames will rarely change and video coding, coding parameters between frames will rarely change and
previous headers may be used in newly received data which the header previous headers may be used in newly received data which the header
have been lost. have been lost.
Compensation of the main header that has been lost is very simple Compensation of the main header that has been lost is very simple
with this procedure. In the case of JPEG 2000 video, it is very with this procedure. In the case of JPEG 2000 video, it is very
common that encode parameters will not vary greatly between common that encode parameters will not vary greatly between
successive frames. Even if the RTP packet including the main header successive frames. Even if the RTP packet including the main header
of a frame has been dropped, decoding may be performed by using the of a frame has been dropped, decoding may be performed by using the
main header of a prior frame. main header of a prior frame.
1.2.2. Priority Table 1.1.2. Priority Table
JPEG 2000 codestream has rich functionality built into it so decoders JPEG 2000 codestream has rich functionality built into it so decoders
can easily handle scalable delivery or progressive transmission. can easily handle scalable delivery or progressive transmission.
Progressive transmission allows images to be reconstructed with Progressive transmission allows images to be reconstructed with
increasing pixel accuracy or spatial resolution. This feature allows increasing pixel accuracy or spatial resolution. This feature allows
the reconstruction of images with different resolutions and pixel the reconstruction of images with different resolutions and pixel
accuracy, for different target devices. A single image source can accuracy, for different target devices. A single image source can
provide a codestream that is easily processed for smaller image provide a codestream that is easily processed for smaller image
display devices. display devices.
JPEG 2000 packets contain all compressed image data from a specific: JPEG 2000 packets contain all compressed image data from a specific:
layer, component, resolution level, and/or precinct. The order in layer, component, resolution level, and/or precinct. The order in
which these JPEG 2000 packets are found in the codestream is called: which these JPEG 2000 packets are found in the codestream is called:
progression order. The ordering of the JPEG 2000 packets can the progression order. The ordering of the JPEG 2000 packets can
progress along four axes: layer, component, resolution and precinct progress along four axes: layer, component, resolution and precinct
(or position). (or position).
Providing a priority field to indicate the importance of data Providing a priority field to indicate the importance of data
contained in a given RTP packet can aid in usage of JPEG 2000 contained in a given RTP packet can aid in usage of JPEG 2000
progressive and scalable functions. progressive and scalable functions.
1.3. Motivations for Priority Field coding 1.2. Motivations for Priority Field coding
JPEG 2000 coding scheme allows one to reorder the codestream in many JPEG 2000 coding scheme allows one to reorder the codestream in many
ways. Even when the coding scheme is determined and arranged by the ways. Even when the coding scheme is determined and arranged by the
encoder, a decoder can still re-arrange the code stream on the fly to encoder, a decoder can still re-arrange the code stream on the fly to
suit decode parameters such as: re-arranging from resolution suit decode parameters such as: re-arranging from resolution
progressive to quality progressive. progressive to quality progressive.
Using the priority field coding, the decoder gains insight into the Using the priority field coding, the decoder gains insight into the
codestream without access to the full codestream and exposes features codestream without access to the full codestream and exposes features
of JPEG 2000 to a higher level. of JPEG 2000 to a higher level.
A few of the scenarios are presented below the authors have thought A few of the scenarios are presented below the authors have thought
of to utilize this field. The priority field allows more information of to utilize this field. The priority field allows more information
about the image to be sent without more signaling between sender and about the image to be sent without more signaling between sender and
receivers to leverage JPEG 2000 capabilities. receivers to leverage JPEG 2000 capabilities.
1.3.1. Scenario: Just enough resolution 1.2.1. Scenario: Just enough resolution
The scenario is when rapid scene access is more important than higher The scenario is when rapid scene access is more important than higher
quality. By using the priority field, the receiver can decode for quality. By using the priority field, the receiver can decode for
its own quality level. If the sender cannot determine the receiver's its own quality level. If the sender cannot determine the receiver's
resolution, the receiver can select which parts of the codestream to resolution, the receiver can select which parts of the codestream to
decode/load by using the priority field. decode/load by using the priority field.
1.3.2. Scenario: Multiple clients, single source 1.2.2. Scenario: Multiple clients, single source
In a multicast environment, there are clients with better visual In a multicast environment, there are clients with better visual
capability than others (i.e. TV conference vs. Mobile). The capability than others (i.e. TV conference vs. Mobile). The
respective clients can use the priority field to determine which respective clients can use the priority field to determine which
packets are vital for their own visual presentation. The sender will packets are vital for their own visual presentation. The sender will
have to do work on the priority field to optimally serve all the have to do work on the priority field to optimally serve all the
clients while only managing a single visual stream. clients while only managing a single visual stream.
1.4. Conventions Used in This Document 1.3. Conventions Used in This Document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC2119. [2]. document are to be interpreted as described in RFC2119. [2].
RFC-Editor Note: The RFC Editor is requested to replace all RFC-Editor Note: The RFC Editor is requested to replace all
occurences of RFC XXXY with the RFC number occurences of RFC XXXY with the RFC number
draft-ietf-avt-rtp-jpeg2000 receives. At that time, please remove draft-ietf-avt-rtp-jpeg2000 receives. At that time, please remove
this note. this note.
skipping to change at page 7, line 34 skipping to change at page 6, line 34
|reserved | fragment offset | |reserved | fragment offset |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: RTP payload header format for JPEG 2000 Figure 1: RTP payload header format for JPEG 2000
mh_id (Main Header Identification) : 3 bits mh_id (Main Header Identification) : 3 bits
Main header identification value. This is used for JPEG 2000 main Main header identification value. This is used for JPEG 2000 main
header recovery. header recovery.
The initial value of mh_id is random, and may take any value The initial value of mh_id MUST be 1 at the beginning of the
between 1-7, but MUST NOT be 0. session.
The same mh_id value is used as long as the coding parameters The same mh_id value is used as long as the coding parameters
described in the main header remains unchanged between frames. described in the main header remains unchanged between frames.
The mh_id value MUST be incremented by 1 every time a new main The mh_id value MUST be incremented by 1 every time a new main
header is transmitted. Once the mh_id value becomes greater than header is transmitted. Once the mh_id value becomes greater than
7, it SHOULD roll over to 1. 7, it SHOULD roll over to 1.
When mh_id is 0, it has special usage for the receiver. This When mh_id is 0, it has special usage for the receiver. This
special usage is described in Section 4.2 of this document. special usage is described in Section 4.2 of this document.
skipping to change at page 9, line 48 skipping to change at page 8, line 48
implementations of this specification MUST support this method. implementations of this specification MUST support this method.
If the JPEG 2000 codestream packet value is greater than 255, the If the JPEG 2000 codestream packet value is greater than 255, the
sender MUST set the payload priority value to 255. sender MUST set the payload priority value to 255.
3.2. Progression Based Ordering 3.2. Progression Based Ordering
The sender will assign the payload packet priority value only based The sender will assign the payload packet priority value only based
on layer, resolution, and component ordering of the codestream. on layer, resolution, and component ordering of the codestream.
This is similar to the packet number based assignment but will not The ordering can assign the different priority values in the same
take into account the precinct number or position in the JPEG 2000 layer or the resolution level, which cannot do in the layer based
codestream. ordering or resolution based ordering.
The difference from the packet number based ordering is that it does
not assign the value in the position level, which saves the priority
values usage. The position based priority signaling is not so
important because a receiver could recognize the position by checking
the tile number field. Therefore, the ordering would be useful.
For example: For example:
If the codestream is ordered in LRCP (Layer, Resolution, Component, If the codestream is ordered in LRCP (Layer, Resolution, Component,
Position) Position) with 1 layer, 2 resolutions, 3 components, and 2 positions,
an example would have packet numbering as so:
All the packets in: All the packets in:
layer.........0 layer.........0
resolution....0 resolution....0
component.....0 component.....0
position......0 or 1
then the packet priority value : 1 then the packet priority value : 1
All the packets in: All the packets in:
layer.........0 layer.........0
resolution....0 resolution....0
component.....1 component.....1
position......0 or 1
then the packet priority value : 2 then the packet priority value : 2
All the packets in: All the packets in:
layer.........0 layer.........0
resolution....0 resolution....0
component.....2 component.....2
position......0 or 1
then the packet priority value : 3 then the packet priority value : 3
All the packets in:
layer.........0
resolution....1
component.....0
position......0 or 1
then the packet priority value : 4
All the packets in:
layer.........0
resolution....1
component.....1
position......0 or 1
then the packet priority value : 5
3.3. Layer Based Ordering 3.3. Layer Based Ordering
Layer-based priority mapping table simplifies the default mapping to Layer-based priority mapping table simplifies the default mapping to
just matching JPEG 2000 packets together from the same layer. just matching JPEG 2000 packets together from the same layer.
For example: For example:
All the packets in layer 0 : packet priority value : 1 All the packets in layer 0 : packet priority value : 1
All the packets in layer 1 : packet priority value : 2 All the packets in layer 1 : packet priority value : 2
All the packets in layer 2 : packet priority value : 3 All the packets in layer 2 : packet priority value : 3
skipping to change at page 14, line 5 skipping to change at page 14, line 5
value. If the values match, decoding may be performed by using the value. If the values match, decoding may be performed by using the
previously saved main header. previously saved main header.
If the mh_id field is set to 0, the receiver MUST NOT save the main If the mh_id field is set to 0, the receiver MUST NOT save the main
header and MUST NOT compensate for lost headers. header and MUST NOT compensate for lost headers.
If the mh_id value changes, receivers SHOULD save the current header If the mh_id value changes, receivers SHOULD save the current header
and save the new mh_id value. The old saved header should be deleted and save the new mh_id value. The old saved header should be deleted
from storage. from storage.
5. Security Consideration 5. Media Type Registration
Please refer to section 6 of RFC XXXY [1] for Security Considerations
regarding this RTP format.
6. Congestion Control
Please refer to section 7 of RFC XXXY [1] for Congestion Control
regarding this RTP format.
7. IANA Consideration
7.1. Media Type Registration
This document extends the associated media type from RFC XXXY[1]:
Here is the complete original for reference.
This registration uses the template defined in [7] and follows [8].
Type name: video
Subtype name: jpeg2000
Required parameters:
rate: The RTP timestamp clock rate. The default rate is 90000,
but other rates MAY be specified. Rates below 1000 Hz SHOULD
NOT be used.
sampling: A list of values specifying the color space of the
payload data.
Acceptable values:
RGB: standard Red, Green, Blue color space.
BGR: standard Blue, Green, Red color space.
RGBA: standard Red, Green, Blue, Alpha color space.
BGRA: standard Blue, Green, Red, Alpha color space.
YCbCr-4:4:4: standard YCbCr color space, no subsampling.
YCbCr-4:2:2: standard YCbCr color space, Cb and Cr are
subsampled horizontally by 1/2.
YCbCr-4:2:0: standard YCbCr color space, Cb and Cr are
subsampled horizontally and vertically by 1/2.
YCbCr-4:1:1: standard YCbCr color space, Cb and Cr are
subsampled vertically by 1/4
GRAYSCALE: basically a single component image of just
multilevels of grey.
EXTENSION VALUE: Additional color samplings can be
registered with and current listing of registered color
samplings at: Color Sampling Registration Authority.
Please refer to RTP Format for Uncompressed Video. [9]
Optional parameters:
interlace: interlace scanning. If payload is in interlace
format, the acceptable value is "1", otherwise, the value
should be "0". Each complete image forms vertically half the
display. tp value MUST properly specify the field the image
represents odd(tp=1), or even(tp=2). If this option is not
present, the payload MUST be in progressive format and tp MUST
be set to 0.
width: A parameter describing the maximum width of the video
stream. This parameter MUST appear when height is present.
Acceptable values: - an integer value between 0 -
4,294,967,295.
height: A parameter describing the maximum height of the video
stream. This parameter MUST appear when width is present.
Acceptable values: - an integer value between 0 -
4,294,967,295.
The receiver MUST ignore any unspecified parameters outside of this This document extends the associated media type from RFC XXXY[1].
list and in [1] . Here are additional optional parameters.
Additional parameters for this extension: Additional optional parameters:
mhc : Main Header Compensation. this option is used when sender mhc : Main Header Compensation. this option is used when sender
and/or receiver is utilizing the Main Header compensation and/or receiver is utilizing the Main Header compensation
technique as specified in this document. Acceptable values technique as specified in this document. Acceptable values
when using the Main Header compensation technique is "1", when using the Main Header compensation technique is "1",
otherwise, it should be "0". otherwise, it should be "0".
This is a list of options to be included when the sender or This is a list of options to be included when the sender or
receiver is utilizing the Priority Table(s) as specified in receiver is utilizing the Priority Table option as specified in
this document. this document.
pt : Priority Table. this option is followed by a comma-separated pt : Priority Table. this option is followed by a comma-separated
list of predefined priority table definitions to be used by list of predefined priority table definitions to be used by
sender or receiver. sender or receiver.
The option appearing front most in the option line is the most The option appearing front most in the option line is the most
important and next ones are of decreasing importance. important and next are of decreasing importance.
Acceptable values: Acceptable values:
progression : this table follows the progression ordering progression : this table follows the progression ordering
of the codestream. of the codestream.
layer : this table follows the layer ordering of the layer : this table follows the layer ordering of the
codestream. codestream.
resolution : this table follows the resolution ordering of resolution : this table follows the resolution ordering of
the codestream. the codestream.
component : this table follows the component ordering of component : this table follows the component ordering of
the codestream. the codestream.
default : this table follows the ordering of the default : this table follows the ordering of the
codestream. codestream.
Encoding considerations: 6. SDP Parameters
This media type is framed and binary, see Section 4.8 in [7]
Security considerations:
see security considerations section Section 5 of this document.
Interoperability considerations:
JPEG 2000 video stream is a sequence of JPEG 2000 still images.
An implementation in compliant with [3] can decode and attempt to
display the encoded JPEG 2000 video stream.
Published specification: ISO/IEC 15444-1 | ITU-T Rec. T.800
Applications which use this media type:
video streaming and communication
Person and email address to contact for further information:
Eisaburo Itakura, Satoshi Futemma, Andrew Leung
Email: {itakura|satosi-f} @ sm . sony . co . jp, andrew @ ualberta
. net
Intended usage: Restriction
Restrictions on Usage:
This media type depends on RTP framing, and hence is only
defined for the transfer via RTP [4]. Transport within other
framing protocols is not defined at the time.
Author/Change Controller:
Author:
Eisaburo Itakura, Satoshi Futemma, Andrew Leung
Email: {itakura|satosi-f} @ sm . sony . co . jp, andrew @
ualberta . net
Change controller:
IETF Audio/Video Transport Working Group delegated from the
IESG
7.2. SDP Parameters
In addition to SDP Parameters section in [1]:
The media type video/jpeg2000 string is mapped to fields in the
Session Description Protocol (SDP) [5] as follows:
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
(the MIME subtype).
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
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 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.
These parameters are expressed as a media type string, in the form of
a semicolon separated list of parameter=value pairs.
Therefore, an example of media representation in SDP is as follows:
m=video 49170/2 RTP/AVP 98
a=rtpmap:98 jpeg2000/90000
a=fmtp:98 mhc=1;pt=default; sampling=YCbCr-4:2:0; width=128;
height=128
An example for using non-90kHz timestamp is as follows: 6.1. Mapping of the optional parameters to SDP
m=video 49170/2 RTP/AVP 98 99 The new optional parameters mhc and pt, if presented, MUST be
a=rtpmap:98 jpeg2000/27000000 included in the "a=fmtp" line of SDP. These parameters are expressed
a=rtpmap:99 jpeg2000/90000 as a media type string, in the form of a semicolon separated list of
a=fmtp:98 mhc=1;pt=default; sampling=YCbCr-4:2:0; width=128; parameter=value pairs.
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 6.2. 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: [4], 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.
o The parameters "mhc" or "pt" MUST appear in the offer and answer. o If the optional parameter "mhc" is used, it MUST appear in the
If the parameter "mhc" or "pt" is not in the answer, senders offer with value "1", and if accepted, it SHOULD appear in the
should not process the header according to this document. answer.
o For the "pt" option: o If the optional parameter "pt" is used, it MUST appear in the
offer containing a complete comma-separated list indicating which
priority table definitions the sender supprots. If accepted, it
SHOULD appear in the answer containing a single priority table
definition selected from the offer.
* Senders should send a complete list indicating which option are o If the optional parameter "mhc" is used, it MUST appear in the
available to the receiver. The receiver should answer with offer with value "1", and if accepted, it MUST appear in the
their preference from the offer list. answer. If the optional parameter "pt" is used, it MUST appear in
the offer containing a complete comma-separated list indicating
which priority table definitions the sender supports. If
accepted, it MUST appear in the answer containing a single
priority table definition selected from the offer.
o In a multicast environment: o In a multicast environment:
* Senders should send out one option for priority-table- * Senders should send out one option for priority-table-
definition for everyone in the group. definition for everyone in the group.
* If a single client in the group do not support the extensions * Even if a single client in the group does not support the
outlined in this document, senders SHOULD NOT use additional extensions outlined in this document, senders MAY use these
techniques outlined in this document. mechanisms. A receiver which doesn't support the mechanisms
would safely ignore the values.in mh_id and priority field.
This is highly recommended for multicast streams where not all
receivers are of the same type.
8.1. Examples 6.2.1. Examples
Offer/Answer example exchanges are provided. Offer/Answer example exchanges are provided.
8.1.1. Example 1 6.2.1.1. Example 1
Alice offers Main Header Compensation functionality, YCbCr 422 color Alice offers Main Header Compensation functionality, YCbCr 422 color
space, interlace image with 720-pixel width and 480-pixel height and space, interlace image with 720-pixel width and 480-pixel height and
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
skipping to change at page 22, line 24 skipping to change at page 16, line 40
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=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 6.2.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
skipping to change at page 23, line 6 skipping to change at page 17, line 21
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 6.2.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
skipping to change at page 24, line 5 skipping to change at page 19, line 5
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 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 7. IANA Consideration
9.1. Normative References This document extends the associated media type from XXXY [1].
Additional parameters are specified in Section 5 of this document.
8. Security Consideration
Please refer to section 6 of RFC XXXY [1] for Security Considerations
regarding this RTP format. The security issues regarding enhanced
mechanisms presented in this document are discussed in the section.
The mh_id field can identify a maximum of 7 different main headers.
If severe packet loss (either random or intentionally introduced by
an attacker) causes 6 successive updates to the main header to be
lost, the decoder will attempt decompression using an incorrect main
header. Care should be taken to prevent implementation bugs with
potential security consequences."
9. Congestion Control
Please refer to section 7 of RFC XXXY [1] for Congestion Control
regarding this RTP format.
10. 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.
[3] ISO/IEC JTC1/SC29, ISO/IEC 15444-1 | ITU-T Rec. T.800, [3] ISO/IEC JTC1/SC29, ISO/IEC 15444-1 | ITU-T Rec. T.800,
"Information Technology - JPEG 2000 Image Coding System - Part "Information Technology - JPEG 2000 Image Coding System - Part
1: Core Coding System", December 2000. 1: Core Coding System", December 2000.
[4] Schulzrinne, Casner, Frederick, and Jacobson, "RTP: A Transport [4] Rosenberg and Schulzrinne, "An Offer/Answer Model with Session
Protocol for Real Time Applications", RFC 3550, STD 64,
July 2003.
[5] Handley and Jacobson, "SDP: Session Description Protocol",
RFC 4566, July 2006.
[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 Appendix A. Sample Headers in Detail
Procedures", RFC 4288, December 2005.
[8] Casner, "Media Type Registration of RTP Payload Formats",
RFC 4855, February 2007.
9.2. Informative References
[9] Perkins and Gharai, "RTP Payload Format for Uncompressed Video", The following figures are sample RTP headers demonstrating values
RFC 4175, September 2005. that should appear in the RTP header. The packet priority is Packet
Number Based Priority.
Appendix A. Sample Headers in Detail For reference, the payload header as follows
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|tp |MHF|mh_id|T| priority | tile number | |tp |MHF|mh_id|T| priority | tile number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|reserved | fragment offset | |reserved | fragment offset |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2 Figure 2: JPEG200 payload header
A.1. Sample 1: Progressive image with single tile, 3500 bytes (i.e.
thumbnail)
First Packet: This packet will have the whole main header. 210 bytes First Packet: This packet will have the whole main header. 210 bytes
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0|1 1|1 0 1|1|0 0 0 0 0 0 0 0|0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0| | 0 | 3 | 1 |1| 0 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 0 0 0 0 0|0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0| | 0 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF4FFF51002F000 .... | |FF4F FF51 002F 0000 .... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 3 Figure 3: Header Sample 1-1 (First Packet)
Second Packet: This packet will have a tile header and the first tile Second Packet: This packet will have a tile header and the first tile
part LLband 1500 bytes part LLband 1500 bytes
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0|1 1|1 0 1|0|0 0 0 0 0 0 0 1|0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0| | 0 | 0 | 1 |0| 1 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 0 0 0 0 0|0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 1 0 0 1 0| | 0 | 210 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF90 000A 0000 0000 2DB3 0001 FF93 | |FF90 000A 0000 0000 2DB3 0001 FF93 .... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 4 Figure 4: Header Sample 1-2 (Second Packet)
Third Packet: This packet will have the next part in the tile, no Third Packet: This packet will have the next part in the tile, no
tile header 1500 bytes tile header 1500 bytes
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0|0 0|1 0 1|0|0 0 0 0 0 0 1 0|0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0| | 0 | 0 | 1 |0| 2 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 0 0 0 0 0|0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 1 0 1 0 1 1 1 0| | 0 | 1710 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|E841 4526 4556 9850 C2EA .... | |E841 4526 4556 9850 C2EA .... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 5 Figure 5: Header Sample 1-3 (Third Packet)
Fourth Packet: Last packet for the image 290 bytes Fourth Packet: Last packet for the image 290 bytes
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0|0 0|1 0 1|0|0 0 0 0 0 0 1 1|0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0| | 0 | 0 | 1 |0| 3 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 0 0 0 0 0|0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 0 1 0 0 0 1 0 1 0| | 0 | 3210 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|A55D 8B73 3B25 25C7 B9EB .... 2FBEB153| |A55D 8B73 3B25 25C7 B9EB .... 2FBEB153|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 6 Figure 6: Header Sample 1-4 (Fourth Packet)
A.2. Smaple 2: Image with 4 tiles
First Packet: This packet will have the whole main header. 210 bytes First Packet: This packet will have the whole main header. 210 bytes
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0|1 1|0 0 1|1|0 0 0 0 0 0 0 0|0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0| | 0 | 3 | 1 |1| 0 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 0 0 0 0 0|0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0| | 0 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF4FFF51002F000 .... | |FF4F FF51 002F 0000 .... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 7 Figure 7: Header Sample 2-1 (First Packet)
Second Packet: This packet will have a first tile part (tile 0) 1400 Second Packet: This packet will have a first tile part (tile 0) 1400
bytes bytes
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0|0 0|0 0 1|0|0 0 0 0 0 0 0 1|0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0| | 0 | 0 | 1 |0| 1 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 0 0 0 0 0|0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 1 0 0 1 0| | 0 | 210 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF90 000A 0000 0000 0578 0001 FF93 .... | |FF90 000A 0000 0000 0578 0001 FF93 .... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 8 Figure 8: Header Sample 2-2 (Second Packet)
Third Packet: This packet will have a second tile part (tile 1) 1423 Third Packet: This packet will have a second tile part (tile 1) 1423
bytes bytes
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0|0 0|0 0 1|0|0 0 0 0 0 0 0 1|0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1| | 0 | 0 | 1 |0| 1 | 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 0 0 0 0 0|0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 0 1 0 0 1 0 1 0| | 0 | 1610 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF90 000A 0001 0000 058F 0001 FF93 .... | |FF90 000A 0001 0000 058F 0001 FF93 .... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 9 Figure 9: Header Sample 2-3 (Third Packet)
Fourth Packet: This packet will have a third tile part (tile 2) 1355 Fourth Packet: This packet will have a third tile part (tile 2) 1355
bytes bytes
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0|0 0|0 0 1|0|0 0 0 0 0 0 0 1|0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0| | 0 | 0 | 1 |0| 1 | 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 0 0 0 0 0|0 0 0 0 0 0 0 0 0 0 0 0 1 0 1 1 1 1 0 1 1 0 0 1| | 0 | 3033 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF90 000A 0002 0000 054B 0001 FF93 .... | |FF90 000A 0002 0000 054B 0001 FF93 .... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 10 Figure 10: Header Sample 2-4 (4th Packet)
Fifth Packet: This packet will have a fourth tile part (tile 3) 1290 Fifth Packet: This packet will have a fourth tile part (tile 3) 1290
bytes bytes
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0|0 0|0 0 1|0|0 0 0 0 0 0 0 1|0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1| | 0 | 0 | 1 |0| 1 | 3 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 0 0 0 0 0|0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 1 0 0 1 0 0 1 0 0| | 0 | 4388 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF90 000A 0003 0000 050A 0001 FF93 .... | |FF90 000A 0003 0000 050A 0001 FF93 .... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 11 Figure 11: Header Sample 2-5 (5th Packet)
A.3. Sample 3: Packing multiple tiles in single payload, fragmented
header. No header compensation, progressive image
First Packet: This packet will have the first part of the main First Packet: This packet will have the first part of the main
header. 110 bytes header. 110 bytes
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0|0 1|0 0 0|1|0 0 0 0 0 0 0 0|0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0| | 0 | 1 | 0 |1| 0 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 0 0 0 0 0|0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0| | 0 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF4FFF51002F000 .... | |FF4F FF51 002F 0000 .... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 12: Header Sample 3-1 (First Packet)
Figure 12 Second Packet: This packet has the second part of the main header.
1400 bytes
Second Packet: This packet has the second part of the header. 1400
bytes
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0|1 0|0 0 0|1|0 0 0 0 0 0 0 0|0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0| | 0 | 2 | 0 |1| 0 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 0 0 0 0 0|0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 1 1 1 0| | 0 | 110 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF6400FF .... | |FF6400FF .... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 13 Figure 13: Header Sample 3-2 (Second Packet)
Third Packet: This packet has two tiles, tile 0 and tile 1 1400 bytes Third Packet: This packet has two tiles, tile 0 and tile 1 1400 bytes
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0|0 0|0 0 0|1|0 0 0 0 0 0 0 1|0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0| | 0 | 0 | 0 |1| 1 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 0 0 0 0 0|0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 1 1 1 1 0 0 1 1 0| | 0 | 1510 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF90 000A 0000 0000 02BC 0001 FF93 ... | |FF90 000A 0000 0000 02BC 0001 FF93 ... |
// . //
|FF90 000A 0001 0000 02BC 0001 FF93 ... | |FF90 000A 0001 0000 02BC 0001 FF93 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 14 Figure 14: Header Sample 3-3 (Third Packet)
Fourth Packet: This packet has one tile, tile 2 1395 bytes Fourth Packet: This packet has one tile, tile 2 1395 bytes
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0|0 0|0 0 0|0|0 0 0 0 0 0 0 1|0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0| | 0 | 0 | 0 |0| 1 | 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 0 0 0 0 0|0 0 0 0 0 0 0 0 0 0 0 0 1 0 1 1 0 1 0 1 1 1 1 0| | 0 | 2910 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF90 000A 0002 0000 0573 0001 FF93 .... | |FF90 000A 0002 0000 0573 0001 FF93 .... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 15 Figure 15: Header Sample 3-4 (4th Packet)
A.4. Sample 4: Interlace image, single tile
The codestream of each image is ordered in LRCP (Layer, Resolution,
Component, Position) with 1 layer, 3 resolutions, 3 components and 1
position.
First packet: This packet will have the whole main header for the odd First packet: This packet will have the whole main header for the odd
field 210 bytes field 210 bytes
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 1|1 1|0 1 0|1|0 0 0 0 0 0 0 0|0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0| | 1 | 3 | 1 |1| 0 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 0 0 0 0 0|0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0| | 0 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF4FFF51002F000 .... | |FF4F FF51 002F 0000 .... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 16 Figure 16: Header Sample 4-1 (First Packet)
Second packet: This packet will have the first part of the odd Second packet: This packet will have the first part of the odd
field's tile 1400 bytes field's tile where three jp2-packets are included. 1400 bytes
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 1|0 0|0 1 0|1|0 0 0 0 0 0 0 0|0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0| | 1 | 0 | 1 |1| 1 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 0 0 0 0 0|0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 1 0 0 1 0| | 0 | 210 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF90 000A 0000 0000 0578 0001 FF93 .... | |FF90 000A 0000 0000 0578 0001 FF93 .... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 17 Figure 17: Header Sample 4-2 (Second Packet)
Third packet: This packet will have the second part of the odd Third packet: This packet will have the second part of the odd
field's tile 1400 bytes field's tile 1400 bytes
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 1|0 0|0 1 0|1|0 0 0 0 0 0 0 1|0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0| | 1 | 0 | 1 |1| 4 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 0 0 0 0 0|0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 0 1 0 0 1 0 1 0| | 0 | 1610 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|7F04 E708 27D9 D11D 22CB ... | |7F04 E708 27D9 D11D 22CB ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 18 Figure 18: Header Sample 4-3 (Third Packet)
Fourth packet: This packet will have the third part of the odd Fourth packet: This packet will have the third part of the odd
field's tile 1300 bytes field's tile 1300 bytes
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 1|0 0|0 1 0|1|0 0 0 0 0 0 0 1|0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0| | 1 | 0 | 1 |1| 7 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 0 0 0 0 0|0 0 0 0 0 0 0 0 0 0 0 0 1 0 1 1 1 1 0 0 0 0 1 0| | 0 | 3010 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|98BD EC9B 2826 DC62 D4AB ... | |98BD EC9B 2826 DC62 D4AB ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 19 Figure 19: Header Sample 4 (4th Packet)
Fifth packet: This packet will have the whole main header for the Fifth packet: This packet will have the whole main header for the
even field even field
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|1 0|1 1|0 1 1|1|0 0 0 0 0 0 0 0|0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0| | 2 | 3 | 1 |1| 0 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 0 0 0 0 0|0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0| | 0 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF4FFF51002F000 .... | |FF4F FF51 002F 0000 .... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 20 Figure 20: Header Sample 4 (5th Packet)
Sixth packet: This packet will have the first part of the odd field's Sixth packet: This packet will have the first part of the odd field's
tile 1400 bytes tile 1400 bytes
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|1 0|0 0|0 1 0|1|0 0 0 0 0 0 0 0|0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0| | 2 | 0 | 1 |1| 1 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 0 0 0 0 0|0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 1 0 0 1 0| | 0 | 1610 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF90 000A 0000 0000 0578 0001 FF93 .... | |FF90 000A 0000 0000 0578 0001 FF93 .... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 21 Figure 21: Header Sample 4 (6th Packet)
Seventh packet: This packet will have the second part of the odd Seventh packet: This packet will have the second part of the odd
field's tile 1400 bytes field's tile 1400 bytes
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|1 0|0 0|0 1 0|1|0 0 0 0 0 0 0 1|0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0| | 2 | 0 | 1 |1| 4 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 0 0 0 0 0|0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 0 1 0 0 1 0 1 0| | 0 | 3010 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|626C 42F0 166B 6BD0 F8E1 ... | |626C 42F0 166B 6BD0 F8E1 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 22 Figure 22: Header Sample 4 (7th Packet)
Eighth packet: This packet will have the third part of the odd Eighth packet: This packet will have the third part of the odd
field's tile 1300 bytes field's tile 1300 bytes
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|1 0|0 0|0 1 0|1|0 0 0 0 0 0 0 1|0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0| | 2 | 0 | 1 |1| 7 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 0 0 0 0 0|0 0 0 0 0 0 0 0 0 0 0 0 1 0 1 1 1 1 0 0 0 0 1 0| | 0 | 4410 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|8114 41D5 18AB 4A1B ... | |8114 41D5 18AB 4A1B ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 23 Figure 23: Header Sample 4 (8th Packet)
Authors' Addresses Authors' Addresses
Andrew Leung Andrew Leung
Sony Corporation Sony Corporation
1-7-1 Konan 1-7-1 Konan
Minato-ku Minato-ku
Tokyo 108-0075 Tokyo 108-0075
Japan Japan
skipping to change at page 34, line 7 skipping to change at page 33, line 7
Minato-ku Minato-ku
Tokyo 108-0075 Tokyo 108-0075
Japan Japan
Phone: +81 3 6748-2111 Phone: +81 3 6748-2111
Email: itakura @ sm . sony . co . jp Email: itakura @ sm . sony . co . jp
URI: http://www.sony.net/ URI: http://www.sony.net/
Full Copyright Statement Full Copyright Statement
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
 End of changes. 124 change blocks. 
359 lines changed or deleted 249 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/