draft-ietf-avt-rtp-jpeg2000-beam-00.txt   draft-ietf-avt-rtp-jpeg2000-beam-01.txt 
INTERNET-DRAFT Andrew Leung
draft-ietf-avt-rtp-jpeg2000-beam-00.txt Satoshi Futemma
Eisaburo Itakura
Sony Corporation
February 14, 2005
Expires: August 25, 2005
Enhanced Processing For Priority and Header in: Audio Video Transport A. Leung
RTP Payload Format for JPEG 2000 Video Streams Internet-Draft S. Futemma
Expires: January 19, 2006 E. Itakura
Sony
July 18, 2005
Enhanced Payload Format for Priority & Header Processing RTP Payload
Format for JPEG 2000 Video Streams BEAM extension
draft-ietf-avt-rtp-jpeg2000-beam-01
Status of this Memo Status of this Memo
By submitting this Internet-Draft, we certify that any applicable By submitting this Internet-Draft, each author represents that any
patent or other IPR claims of which I am aware have been disclosed, applicable patent or other IPR claims of which he or she is aware
and any of which we become aware will be disclosed, in accordance have been or will be disclosed, and any of which he or she becomes
with RFC 3668. aware will be disclosed, in accordance with Section 6 of BCP 79.
This document may not be modified, and derivative works of it may not
be created.
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
other groups may also distribute working documents as other groups may also distribute working documents as Internet-
Internet-Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six months
months and may be updated, replaced, or obsoleted by other and may be updated, replaced, or obsoleted by other documents at any
documents at any time. It is inappropriate to use Internet-Drafts time. It is inappropriate to use Internet-Drafts as reference
as reference materials or to cite them other than as "work in material or to cite them other than as "work in progress."
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-Drafts 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 January 19, 2006.
Copyright Notice
Copyright (C) The Internet Society (2005).
Abstract Abstract
This memo describes extended uses for payload header in RFCXXXY, An This memo describes extended uses for payload header in RFCXXXY, An
RTP Payload Format for JPEG 2000 Video, for better support of JPEG RTP Payload Format for JPEG 2000 Video, for better support of JPEG
2000 features such as scalability and includes a main header 2000 features such as scalability and includes a main header recovery
recovery method. method.
This memo MUST be accompanied with an implementation of RFCXXXY for This memo MUST be accompanied with an implementation of RFCXXXY for a
a complete implementation. RFCXXXY itself is a complete description complete implementation. RFCXXXY itself is a complete description of
of the payload header and signaling, this document only describes the payload header and signaling, this document only describes
additional processing of values for the payload header. There is additional processing for the payload header. There is an additional
also another MIME and SDP marker signaling for implementations of MIME and SDP marker signaling for implementations of this document.
this document.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1 History . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.2 Description of the Mechanisms . . . . . . . . . . . . . . 3
1.2.1 Main Header Compensation . . . . . . . . . . . . . . . 3
1.2.2 Priority Table . . . . . . . . . . . . . . . . . . . . 3
1.3 Conventions Used in This Document . . . . . . . . . . . . 4
2. Payload Format Enhanced Processing . . . . . . . . . . . . . . 5
2.1 Enhanced Processing Markers . . . . . . . . . . . . . . . 5
3. Priority Mapping Table . . . . . . . . . . . . . . . . . . . . 7
3.1 Pre-Defined Priority Mapping . . . . . . . . . . . . . . . 7
3.1.1 Packet Number Based Ordering . . . . . . . . . . . . . 7
3.1.2 Progression Based Ordering . . . . . . . . . . . . . . 7
3.1.3 Layer Based Ordering . . . . . . . . . . . . . . . . . 8
3.1.4 Resolution Based Ordering . . . . . . . . . . . . . . 9
3.1.5 Component Based Ordering . . . . . . . . . . . . . . . 9
3.2 Application Specific Priority Table . . . . . . . . . . . 9
4. JPEG 2000 Main Header Compensation Scheme . . . . . . . . . . 10
4.1 Sender Processing . . . . . . . . . . . . . . . . . . . . 10
4.2 Receiver Processing . . . . . . . . . . . . . . . . . . . 10
5. Security Consideration . . . . . . . . . . . . . . . . . . . . 12
6. IANA Consideration . . . . . . . . . . . . . . . . . . . . . . 13
6.1 MIME Registration . . . . . . . . . . . . . . . . . . . . 13
6.2 SDP Parameters . . . . . . . . . . . . . . . . . . . . . . 14
7. Usage with the SDP Offer/Answer Model . . . . . . . . . . . . 15
7.1 Examples . . . . . . . . . . . . . . . . . . . . . . . . . 15
7.1.1 Example 1 . . . . . . . . . . . . . . . . . . . . . . 15
7.1.2 Example 2 . . . . . . . . . . . . . . . . . . . . . . 16
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17
8.1 Normative References . . . . . . . . . . . . . . . . . . . 17
8.2 Informative References . . . . . . . . . . . . . . . . . . 17
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 17
A. Sample Headers in Detail . . . . . . . . . . . . . . . . . . . 19
Intellectual Property and Copyright Statements . . . . . . . . 27
1. Introduction 1. Introduction
This document is an extension of RFCXXXY, An RTP Payload Format for This document is an extension of RFCXXXY, An RTP Payload Format for
JPEG 2000 Video. There are additional mechanisms to be used with JPEG 2000 Video. There are additional mechanisms to be used with
certain parts of the header in RFCXXXY to support JPEG 2000 certain parts of the header in RFCXXXY to support JPEG 2000 features
features such as scalability and a main header recovery method. such as scalability and a main header recovery method. These
These mechanisms are described in detail in this document. mechanisms are described in detail in this document.
History 1.1 History
In the development of RFCXXXY, Sony Corporation filed a patent In the development of RFCXXXY, Sony Corporation filed a patent
application on certain mechanisms with the main header recovery, application on certain mechanisms with the main header recovery,
priority table usage, etc. As these are not "essential" to the core priority table usage, etc. in RFCXXXY. As these are not "essential"
RTP format and only describes a mechanism, it was decided that to the core RTP format of RFCXXXY and only describes a mechanism, it
splitting these mechanisms from the core RTP format (essentially was decided that splitting these mechanisms from the core RTP format
IPR free) into another document (IPR). This is the document (essentially IPR free) into another document (IPR). This is the
describing the mechanisms. document describing the IPR related mechanisms for main header
recover, priority table usage, etc.
Description of the mechanisms 1.2 Description of the Mechanisms
o Main Header Compensation 1.2.1 Main Header Compensation
JPEG 2000's scalable coding scheme allows for decompressing JPEG 2000's scalable coding scheme allows for decompressing truncated
truncated or partial data streams but only when the main header or partial data streams but only when the main header is present. If
is present. If the header is lost, the data is useless. Also, the header is lost, the data is useless. With JPEG 2000 video
with JPEG 2000 video coding, coding parameters between frames coding, coding parameters between frames will rarely change and
will rarely change and previous headers may be used in newly previous headers may be used in newly received data which the header
received data without headers. have been lost.
A recovery of the main header that has been lost is very simple A recovery of the main header that has been lost is very simple with
with this procedure. In the case of JPEG 2000 video, it is common this procedure. In the case of JPEG 2000 video, it is common that
that encode parameters will not vary greatly between each encode parameters will not vary greatly between each successive
successive frame. Even if the RTP packet including the main header frame. Even if the RTP packet including the main header of a frame
of a frame has been dropped, decoding may be performed by using the has been dropped, decoding may be performed by using the main header
main header of a previous frame. of a previous frame.
o Priority Table 1.2.2 Priority Table
JPEG 2000 codestream has rich functionality built into it so JPEG 2000 codestream has rich functionality built into it so decoders
decoders can easily handle scalable delivery or progressive can easily handle scalable delivery or progressive transmission.
transmission. Progressive transmission allows images to be Progressive transmission allows images to be reconstructed with
reconstructed with increasing pixel accuracy or spatial resolution. increasing pixel accuracy or spatial resolution. This feature allows
This feature allows the reconstruction of images with different the reconstruction of images with different resolutions and pixel
resolutions and pixel accuracy, for different target devices. A accuracy, for different target devices. A single image source can
single image source can provide a codestream that is easily provide a codestream that is easily processed for smaller image
processed for smaller image display devices. display devices.
JPEG 2000 packets contain all compressed image data from a JPEG 2000 packets contain all compressed image data from a specific:
specific: layer, component, resolution level, and/or precinct. The layer, component, resolution level, and/or precinct. The order in
order in which these JPEG 2000 packets are found in the codestream which these JPEG 2000 packets are found in the codestream is called:
is called: progression order. The ordering of the JPEG 2000 packets progression order. The ordering of the JPEG 2000 packets can
can progress along four axes: layer, component, resolution and progress along four axes: layer, component, resolution and precinct
precinct. (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.1 Conventions Used in this Document 1.3 Conventions Used in This Document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
in this document are to be interpreted as described in RFC2119 document are to be interpreted as described in RFC2119 [1].
[1].
2. Payload Format Enhanced Processing 2. Payload Format Enhanced Processing
2.1 Enhanced Processing Markers 2.1 Enhanced Processing Markers
This section of the document describes changes in the mh_id and This section of the document describes changes in the value of mh_id
priority value which differ from RFCXXXY. Implementions of this and priority value and interpretation which differ from RFCXXXY.
document should follow protocol in RFCXXXY first then add in Implementions of this document should follow protocol in RFCXXXY
additional header processing for this document. Implementations first then add in additional header processing as described in this
following this document are expected to seamlessly work with document. Implementations following this document are expected to
implementations of just RFCXXXY. seamlessly work with implementations of RFCXXXY and this document as
well.
The RTP payload header format for JPEG 2000 video stream is as The RTP payload header format for JPEG 2000 video stream is as
follows: 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Fig. 3: 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 Main header identification value. This is used for JPEG 2000 main
2000 main header recovery. header recovery.
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. described in the main header remains unchanged between frames.
The initial value of mh_id is random, and may take any value The initial value of mh_id is random, and may take any value
between 1-7, but MUST NOT be 0. between 1-7, but MUST NOT be 0.
When mh_id is 0, it has special usage for The mh_id value MUST increment by 1 every time a new main header
the receiver. This special usage is described in Section xxx of is transmitted. Once the mh_id value is greater than 7, it rolls
this document. over to 1.
The mh_id value MUST increment by 1 every time a new main When mh_id is 0, it has special usage for the receiver. This
header is transmitted. Once the mh_id value is greater than 7, special usage is described in Section 4.2 of this document.
it rolls over to 1.
Senders should follow Section 4.1 of this document for proper
mh_id usage.
priority : 8 bits priority : 8 bits
The priority field indicates the importance of the JPEG 2000 The priority field indicates the importance of the JPEG 2000
packet included in the payload. Typically, a higher priority packet included in the payload. Typically, a higher priority is
is set in the packets containing JPEG 2000 packets containing set in the packets containing JPEG 2000 packets containing the
the lower sub-bands. lower sub-bands.
This header is described in detail in documentXXX. Systems not
using the method described in documentXXX at the sender this
value SHOULD be set to 0 and receivers SHOULD ignore this
value.
Special values of priority: Special values of priority:
0 : This is reserved for payload which contain a 0: This is reserved for payload which contain a header (main or
header (main or tile part header.) This is tile part header.) This is considered the highest importance.
considered the highest importance.
1 to 255 : These values decrease in importance as the 1 to 255: These values decrease in importance as the values
values increase. (i.e. 1 is more important than increase. (i.e. 1 is more important than 2, etc.) Hence
2, etc.) Hence applying priority values should applying priority values should correlate directly to JPEG 2000
correlate directly to JPEG 2000 codestream in codestream in importance in basic usage.
importance in basic usage.
The lower the priority value is the higher the priority. The lower the priority value is the higher the priority. Simply,
Simply, the priority value 0 is the highest priority and 255 is the priority value 0 is the highest priority and 255 is the lowest
the lowest priority. We define the priority value 0 as a priority. We define the priority value 0 as a special priority
special priority value for the headers (the main header or value for the headers (the main header or tile-part header). When
tile-part header). When any headers (the main header or any headers (the main header or tile-part header) are packed into
tile-part header) are packed into the RTP packet, the sender the RTP packet, the sender MUST set the priority value to 0.
MUST set the priority value to 0.
Assignment of the values are described in Section 3 with pre-
defined table assignments in Section 3.1.
3. Priority Mapping Table 3. Priority Mapping Table
For the progression order, the priority value for each JPEG 2000 For the progression order, the priority value for each JPEG 2000
packet is given by the priority mapping table. packet is given by the priority mapping table.
3.1 Pre-Defined Priority Mapping 3.1 Pre-Defined Priority Mapping
This document specify several commonly-used several priority This document specify several commonly-used priority mapping tables,
mapping table, pre-defined priority mapping tables: packet number pre-defined priority mapping tables: packet number based (default),
based (default), progression-based, layer-based, resolution-based, progression-based, layer-based, resolution-based, component-based.
component-based.
Packet number priority mapping is REQUIRED to be supported by Packet number priority mapping is REQUIRED to be supported by clients
clients implementing this specification. Other priority mapping implementing this specification. Other priority mapping tables
tables (progression, layer, resolution, and component based) are (progression, layer, resolution, and component based) are OPTIONAL to
OPTIONAL to implementations of this specification. implementations of this specification.
Rules that all implementations of this specification MUST follow Rules that all implementations of this specification MUST follow in
in all priority modes: all priority modes:
When there is a header in the packet with a JPEG 2000 packet, o When there is a header in the packet with a JPEG 2000 packet, the
the sender MUST set the payload packet priority value to 0. sender MUST set the payload packet priority value to 0.
When there are multiple JPEG 2000 packets in the same RTP payload o When there are multiple JPEG 2000 packets in the same RTP payload
packet, the sender MUST set the payload packet priority value to packet, the sender MUST set the payload packet priority value to
the lowest priority value of the lowest JPEG 2000 packet. the lowest priority value of the lowest JPEG 2000 packet. (i.e. if
(i.e. if JPEG 2000 packets with priority: 5,6,7 are packed into a JPEG 2000 packets with priority: 5,6,7 are packed into a single
single payload, the priority value MUST be 5.) payload, the priority value MUST be 5.)
3.1.1 Packet number based Ordering 3.1.1 Packet Number Based Ordering
This is the default mode for payload packet priority value and This is the default mode for payload packet priority value and all
all implementation of this specification MUST support. implementation of this specification MUST support.
The sender will have a one-to-one association between payload The sender will have a one-to-one association between payload packet
packet priority value and the payload packet value (i.e. the priority value and the payload packet value (i.e. the JPEG 2000
JPEG 2000 codestream.) The RTP packet value is equal to the codestream.) The RTP packet value is equal to the JPEG 2000 packet
JPEG 2000 packet value. value.
If the packet value of JPEG 2000 codestream is greater than 255, If the packet value of JPEG 2000 codestream is greater than 255, the
the sender MUST set the payload priority value to 255. sender MUST set the payload priority value to 255.
3.1.2 Progression-based Ordering 3.1.2 Progression Based Ordering
The sender will assign the payload packet priority value only The sender will assign the payload packet priority value only based
based on layer, resolution, and component ordering of the on layer, resolution, and component ordering of the codestream.
codestream.
This is similar to the JPEG 2000 packet number based format but This is similar to the JPEG 2000 packet number based format but will
will not take into account the precinct number or position in the not take into account the precinct number or position in the JPEG
JPEG 2000 codestream. 2000 codestream.
For example: For example:
If the codestream is ordered in LRCP (Layer, Resolution,
Component, Position)
All the packets in layer 0 If the codestream is ordered in LRCP (Layer, Resolution, Component,
Position)
All the packets in:
layer 0
resolution 0 resolution 0
component 0 : packet priority value : 1 component 0
All the packets in layer 0 then the packet priority value : 1
All the packets in:
layer 0
resolution 0 resolution 0
component 1 : packet priority value : 2 component 1
All the packets in layer 0 then the packet priority value : 2
All the packets in:
layer 0
resolution 0 resolution 0
component 2 : packet priority value : 3 component 2
3.1.3 Layer-based Ordering then the packet priority value : 3
Layer-based priority mapping table simplifies the default mapping 3.1.3 Layer Based Ordering
to just matching JPEG 2000 packets together from the same layer.
Layer-based priority mapping table simplifies the default mapping to
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
All the packets in layer 3 : packet priority value : 4 ...
All the packets in layer n : packet priority value : n+1
3.1.4 Resolution-based Ordering 3.1.4 Resolution Based Ordering
Resolution-based priority mapping table is similar to the layer Resolution-based priority mapping table is similar to the layer based
based order but for JPEG 2000 packets of the same resolution order but for JPEG 2000 packets of the same resolution
For example: For example:
All the packets in resolution 0 : packet priority value : 1 All the packets in resolution 0 : packet priority value : 1
All the packets in resolution 1 : packet priority value : 2 All the packets in resolution 1 : packet priority value : 2
All the packets in resolution 2 : packet priority value : 3 All the packets in resolution 2 : packet priority value : 3
All the packets in resolution 3 : packet priority value : 4 ...
All the packets in resolution n : packet priority value : n+1
3.1.5 Component-based Ordering 3.1.5 Component Based Ordering
Component-based priority mapping table is mapping together Component-based priority mapping table is mapping together JPEG 2000
JPEG 2000 components of the same component components of the same component
For example: For example:
All the packets in component 0 : packet priority value : 1 All the packets in component 0 : packet priority value : 1
All the packets in component 1 : packet priority value : 2 All the packets in component 1 : packet priority value : 2
All the packets in component 2 : packet priority value : 3 All the packets in component 2 : packet priority value : 3
All the packets in component 3 : packet priority value : 4 ...
All the packets in component n : packet priority value : n+1
3.2 Application Specific Priority Table 3.2 Application Specific Priority Table
The application specific priority table specification is intended The application specific priority table specification is intended for
for experimental use as new applications and new priority mapping experimental use as new applications and new priority mapping tables
tables are developed. are developed.
A case sensitive 8 character ASCII code describing the application A case sensitive 8 character ASCII code describing the application
specific priority mapping name. The description of these specific priority mapping name. The description of these application
application specific priority tables are outside the scope of this specific priority tables are outside the scope of this document.
document.
This extension may be used when codestream is divided into many This extension may be used when the codestream is divided into many
layers and many resolutions. layers and many resolutions.
4. JPEG 2000 Main Header Compensation Scheme 4. JPEG 2000 Main Header Compensation Scheme
The mh_id field of the payload header is used to recognize whether The mh_id field of the payload header is used to recognize whether
the encoding parameters of the main header are the same as the the encoding parameters of the main header are the same as the
encoding parameters of the previous frame. The same value is set encoding parameters of the previous frame. The same value is set in
in mh_id of the RTP packet in the same frame. The mh_id and encode mh_id of the RTP packet in the same frame. The mh_id and encode
parameters are not associated with each other as 1:1 but they are parameters are not associated with each other as 1:1 but they are
used to recognize whether the encode parameters of the previous used to recognize whether the encode parameters of the previous frame
frame are the same or not in the event of lost headers. are the same or not in the event of a lost header.
The mh_id field value SHOULD be saved from previous frames to be The mh_id field value SHOULD be saved from previous frames to be used
used to recover the current frame's main header. If the mh_id of to recover the current frame's main header. If the mh_id of the
the current frame has the same value as the mh_id value of the current frame has the same value as the mh_id value of the previous
previous frame, the previous frame's main header SHOULD be used to frame, the previous frame's main header MAY be used to decode the
decode the current frame, in case of a lost header. current frame, in case of a lost header in the current frame.
The sender MUST increment mh_id when parameters in the header The sender MUST increment mh_id when parameters in the header change
change and send a new main header accordingly. and send a new main header accordingly.
The receiver MAY use the mh_id and MAY retain the header for such The receiver MAY use the mh_id and MAY retain the header for such
compensation. compensation.
4.1 Sender Processing 4.1 Sender Processing
The sender MUST transmit RTP packets with the same mh_id value The sender MUST transmit RTP packets with the same mh_id value unless
unless the encoder parameters are different from the previous the encoder parameters are different from the previous frame. The
frame. The encoding parameters are the fixed information marker encoding parameters are the fixed information marker segment (SIZ
segment (SIZ marker) and functional marker segments (COD, COC, RGN, marker) and functional marker segments (COD, COC, RGN, QCD, QCC, and
QCD, QCC, and POC) specified in JPEG 2000 Part 1 Annex A [2]. POC) specified in JPEG 2000 Part 1 Annex A [2]. An initial value of
An initial value of mh_id MUST be selected randomly between 1 and mh_id MUST be selected randomly between 1 and 7 for security reasons.
7.
If the encode parameters changes, the sender transmitting RTP If the encode parameters changes, the sender transmitting RTP packets
packets MUST increment the mh_id value by one, but when mh_id value MUST increment the mh_id value by one, but when mh_id value becomes
becomes greater than 7, a sender MUST set mh_id value to 1. greater than 7, a sender MUST set mh_id value to 1.
4.2 Receiver Processing 4.2 Receiver Processing
When the receiver receives the main header completely, the RTP When the receiver receives the main header completely, the RTP
sequence number, the mh_id and main header should be saved. Only sequence number, the mh_id and main header should be saved. Only the
the last main header that was received completely SHOULD be saved. last main header that was received completely SHOULD be saved. When
When the mh_id value is 0, the receiver SHOULD NOT save the header. the mh_id value is 0, the receiver SHOULD NOT save the header.
When the main header is not received, the receiver may compare the When the main header is not received, the receiver may compare the
current payload header's mh_id value with the saved mh_id value. current payload header's mh_id value with the previous saved mh_id
When the values are the same, decoding may be performed by using value. If the values match, decoding may be performed by using the
the saved main header. previously saved main header.
If the mh_id field is set to 0, the receiver MUST not save the If the mh_id field is set to 0, the receiver MUST not save the main
main header and MUST NOT compensate for lost headers. header and MUST NOT compensate for lost headers.
5. Security Consideration 5. Security Consideration
RTP packets using the payload format defined in this specification RTP packets using the payload format defined in this specification
are subject to the security considerations discussed in the RTP are subject to the security considerations discussed in the RTP
specifications[3] and any applicable profile. This implies that specifications[3] and any applicable profile. This implies that
confidentiality of the media streams is achieved by encryption. confidentiality of the media streams is achieved by encryption. Data
Data compression used with this payload format is applied compression used with this payload format is applied end-to-end,
end-to-end, encryption may be performed on the compressed data so encryption may be performed on the compressed data so there is no
there is no conflict between the two operations. conflict between the two operations.
A potential denial-of-service threat exists for data encodings A potential denial-of-service threat exists for data encodings using
using compression techniques that have non-uniform receiver-end compression techniques that have non-uniform receiver-end
computational load. The attacker can inject pathological computational load. The attacker can inject pathological datagrams
datagrams into the stream which are complex to decode and cause into the stream which are complex to decode and cause the receiver to
the receiver to be overloaded. The usage of authentication of at be overloaded. The usage of authentication of at least the RTP
least the RTP packet is RECOMMENDED, for example with SRTP [4]. packet is RECOMMENDED, for example with SRTP [2].
If QoS enhanced service is used, RTP receivers SHOULD monitor If QoS enhanced service is used, RTP receivers SHOULD monitor packet
packet loss to ensure that the service that was requested is loss to ensure that the service that was requested is actually being
actually being delivered. If it is not, then they SHOULD assume delivered. If it is not, then they SHOULD assume that they are
that they are receiving best-effort service and behave accordingly. receiving best-effort service and behave accordingly.
If best-effort service is being used, users of this payload format If best-effort service is being used, users of this payload format
MUST monitor packet loss to ensure that the packet loss rate is MUST monitor packet loss to ensure that the packet loss rate is
within acceptable parameters. Packet loss is considered acceptable within acceptable parameters. Packet loss is considered acceptable
if a TCP flow across the same network path, experiencing the same if a TCP flow across the same network path, experiencing the same
network conditions, would achieve an average throughput, measured network conditions, would achieve an average throughput, measured on
on a reasonable timescale, that is not less than the RTP flow is a reasonable timescale, that is not less than the RTP flow is
achieving. This condition can be satisfied by implementing achieving. This condition can be satisfied by implementing
congestion control mechanisms to adapt the transmission rate (or congestion control mechanisms to adapt the transmission rate (or the
the number of layers subscribed for a layered multicast session), number of layers subscribed for a layered multicast session), or by
or by arranging for a receiver to leave the session if the loss arranging for a receiver to leave the session if the loss rate is
rate is unacceptably high. unacceptably high.
As with any IP-based protocol, in some circumstances a receiver As with any IP-based protocol, in some circumstances a receiver may
may be overloaded simply by receiving too many packets, either be overloaded simply by receiving too many packets, either desired or
desired or undesired. Network-layer authentication may be used to undesired. Network-layer authentication may be used to discard
discard packets from undesired sources, but the processing cost of packets from undesired sources, but the processing cost of the
the authentication itself may be too high. In a multicast authentication itself may be too high. In a multicast environment,
environment, pruning of specific sources may be implemented in pruning of specific sources may be implemented in future versions of
future versions of IGMP [7] and in multicast routing protocols to IGMP [7] and in multicast routing protocols to allow a receiver to
allow a receiver to select which sources are allowed to reach it. select which sources are allowed to reach it.
6. IANA Consideration 6. IANA Consideration
6.1 MIME Registration 6.1 MIME Registration
This document defines a new RTP payload name and associated MIME This document defines a new RTP payload name and associated MIME
type, jpeg2000. type, jpeg2000.
The receiver MUST ignore any unspecified parameter. The receiver MUST ignore any unspecified parameter.
The MIME registration form for JPEG 2000 video stream is enclosed The MIME registration form for JPEG 2000 video stream is enclosed
below: below:
MIME media type name: video MIME media type name: video
MIME subtype name: jpeg2000 MIME subtype name: jpeg2000
REQUIRED parameters: BEAM REQUIRED parameters: BEAM
BEAM: Implmentations of this standard must include this option in 'BEAM': Implmentations of this standard must include this option
the parameter list when establishing a session. If this option is in the parameter list when establishing a session. If this option
supported, by the receiver/sender, both should reply with this is supported, by the receiver/sender, both should reply with this
option in the mime parameter list. If the answer omits this in option in the MIME parameter list. If the answer omits this in
the mime parameter list, the answerer does not support this the MIME parameter list, the answerer does not support this option
option
Encoding considerations: Encoding considerations:
JPEG 2000 video stream may be transmitted with RTP as specified
in this document.
Security considerations: see section 9 of RFC XXXX. JPEG 2000 video stream may be transmitted with RTP as specified in
this document.
Security considerations: see section 9 of RFC AXXX.
Interoperability considerations: Interoperability considerations:
JPEG 2000 video stream is a sequence of JPEG 2000 still
images. An implementation in compliant with [1] can decode and JPEG 2000 video stream is a sequence of JPEG 2000 still images.
attempt to display the encoded JPEG 2000 video stream. An implementation in compliant with [2] can decode and attempt to
display the encoded JPEG 2000 video stream.
Published specification: ISO/IEC 15444-1 | ITU-T Rec. T.800 Published specification: ISO/IEC 15444-1 | ITU-T Rec. T.800
Applications which use this media type: Applications which use this media type:
video streaming and communication video streaming and communication
Additional information: none Additional information: none
Magic number(s): none Magic number(s): none
File extension(s): none File extension(s): none
Macintosh File Type Code(s): none Macintosh File Type Code(s): none
Person & email address to contact for further information: Person & email address to contact for further information:
Eisaburo Itakura, Satoshi Futemma Eisaburo Itakura, Satoshi Futemma
Email: {itakura|satosi-f}@sm.sony.co.jp Email: {itakura|satosi-f}@sm.sony.co.jp
Intended usage: COMMON Intended usage: COMMON
Author/Change controller: Author/Change controller:
Eisaburo Itakura, Satoshi Futemma Eisaburo Itakura, Satoshi Futemma
Email: {itakura|satosi-f}@sm.sony.co.jp Email: {itakura|satosi-f}@sm.sony.co.jp
6.2 SDP Parameters 6.2 SDP Parameters
In addition to section 7.2 in RFCXXXY:
The MIME media type video/jpeg2000 string is mapped to fields in In addition to SDP Parameters section in RFCXXXY:
the Session Description Protocol (SDP) [5] as follows:
The MIME 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 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 MUST be 90000.
o The REQUIRED parameters "BEAM" MUST be included in the "a=fmtp" o The REQUIRED parameters "BEAM" MUST be included in the "a=fmtp"
line of SDP. line of SDP.
o The OPTIONAL parameters "priority-table-default", o The OPTIONAL parameters "priority-table-default", "priority-table-
"priority-table-definition", "priority-table-protocol", MUST be definition", "priority-table-protocol", MUST be included in the
included in the "a=fmtp" line of SDP. "a=fmtp" line of SDP.
These parameters are expressed as a MIME media type string, in the These parameters are expressed as a MIME media type string, in the
form of a semicolon separated list of parameter=value pairs. form of a semicolon separated list of parameter=value pairs.
Therefore, an example of media representation in SDP is as Therefore, an example of media representation in SDP is as follows:
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 BEAM;sampling=YCbCr-4:2:0;width=128;height=128 a=fmtp:98 BEAM;sampling=YCbCr-4:2:0;width=128;height=128
7. Usage with the SDP Offer/Answer Model 7. Usage with the SDP Offer/Answer Model
In addition to section 8 in RFCXXXY: In addition to SDP Offer/Answer section in RFCXXXY:
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.
o The parameters "BEAM" MUST appear in the offer o The parameters "BEAM" MUST appear in the offer if the parameter
If the parameter "BEAM" is not in the answer, receivers should "BEAM" is not in the answer, receivers should not process the
not process the header according to this document. Senders SHOULD header according to this document. Senders SHOULD continue to
continue to send data with payload headers according to send data with payload headers according to mechanisms outlined in
mechanisms outlined in this document. This is highly recommended this document. This is highly recommended for multicast streams
for multicast streams where not all receivers are of the same where not all receivers are of the same type.
type.
7.1 Examples 7.1 Examples
An example offer/answer exchanges are provided. Offer/Answer example exchanges are provided.
7.1.2 Example 1 7.1.1 Example 1
Alice offers BEAM functionality, YCbCr 422 color space, interlace Alice offers BEAM functionality, YCbCr 422 color space, interlace
image with 720-pixel width and 480-pixel height and several image with 720-pixel width and 480-pixel height and several priority-
priority-table options (jp2-packet, progression, layer, table options (jp2-packet, progression, layer, resolution, component)
resolution, component) as below: as below:
v=0 v=0
o=alice 2890844526 2890844526 IN IP4 host.anywhere.com o=alice 2890844526 2890844526 IN IP4 host.anywhere.com
s= s=
c=IN IP4 host.anywhere.com c=IN IP4 host.anywhere.com
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 BEAM;sampling=YCbCr-4:2:2;interlace a=fmtp:98 BEAM;sampling=YCbCr-4:2:2;interlace
a=fmtp:98 priority-table-definition=jp2-packet,progression,layer, a=fmtp:98 priority-table-definition=jp2-packet,progression,layer,
resolution,component; width=720; height=480 resolution,component; width=720; height=480
Bob accepts BEAM functionality, YCbCr-4:2:2 color space,interlace Bob accepts BEAM functionality, YCbCr-4:2:2 color space,interlace
image and jp2-packet based priority mapping (default mapping image and jp2-packet based priority mapping (default mapping table)
table) and replies: and replies:
v=0 v=0
o=bob 2890844730 2890844731 IN IP4 host.example.com o=bob 2890844730 2890844731 IN IP4 host.example.com
s= s=
c=IN IP4 host.example.com c=IN IP4 host.example.com
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 BEAM;sampling=YCbCr-4:2:2;interlace a=fmtp:98 BEAM;sampling=YCbCr-4:2:2;interlace
Note that "priority-table-definition" parameter in Bob's answer is Note that "priority-table-definition" parameter in Bob's answer is
omitted, so default priority mapping table (jp2-packet number based omitted, so default priority mapping table (jp2-packet number based
priority mapping) is used. priority mapping) is used.
7.1.2 Example 2 7.1.2 Example 2
Alice offers YCbCr 420 color space, progressive image with Alice offers YCbCr 420 color space, progressive image with 320-pixel
320-pixel width and 240-pixel height and layer priority-table width and 240-pixel height and layer priority-table options as below:
options as below:
v=0 v=0
o=alice 2890844526 2890844526 IN IP4 host.anywhere.com o=alice 2890844526 2890844526 IN IP4 host.anywhere.com
s= s=
c=IN IP4 host.anywhere.com c=IN IP4 host.anywhere.com
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 BEAM;sampling=YCbCr-4:2:0 a=fmtp:98 BEAM;sampling=YCbCr-4:2:0
a=fmtp:98 priority-table-definition=layer; width=320; height=240 a=fmtp:98 priority-table-definition=layer; width=320; height=240
Bob does not accept BEAM functionality but accepts YCbCr-4:2:0 Bob does not accept BEAM functionality but accepts YCbCr-4:2:0 color
color space,interlace image and layer based priority mapping and space,interlace image and layer based priority mapping and replies:
replies:
v=0 v=0
o=bob 2890844730 2890844731 IN IP4 host.example.com o=bob 2890844730 2890844731 IN IP4 host.example.com
s= s=
c=IN IP4 host.example.com c=IN IP4 host.example.com
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 sampling=YCbCr-4:2:2 a=fmtp:98 sampling=YCbCr-4:2:2
Note that "BEAM" parameter was not in Bob's answer so Alice must Note that "BEAM" parameter was not in Bob's answer so Alice must not
not use settings described in this document for sending or use settings described in this document for sending or receiving.
receiving.
7.2 Sample Headers in Detail 8. References
This section has various sample headers in various configurations for 8.1 Normative References
reference.
For reference, the payload header. [1] Bradner, "Key words for use in RFCs to Indicate Requirement
Levels", RFC 2119, March 1997.
[2] ISO/IEC JTC1/SC29, ISO/IEC 15444-1 | ITU-T Rec. T.800,
"Information Technology - JPEG 2000 Image Coding System - Part
1: Core Coding System", December 2000.
[3] Schulzrinne, Casner, Frederick, and Jacobson, "RTP: A Transport
Protocol for Real Time Applications", RFC 3550, STD 64,
July 2003.
[4] Baugher, McGrew, Naslund, Carrara, and Norrman, "The Secure
Real-time Transport Protocol (SRTP", RFC 3711, March 2004.
[5] Handley and Jacobson, "SDP: Session Description Protocol",
RFC 2327, April 1998.
[6] Rosenberg and Schulzrinne, "An Offer/Answer Model with Session
Description Protocol (SDP)", RFC 3264, June 2002.
8.2 Informative References
[7] Deering, "Host Extensions for IP Multicasting", RFC 1112,
August 1989.
Authors' Addresses
Andrew Leung
Sony Corporation
6-7-35 Kitashinagawa
Shinagawa-ku
Tokyo 141-0001
Japan
Phone: +81 3 5448 2125
Email: andrew.leung@jp.sony.com
URI: http://www.sony.com/
Satoshi Futemma
Sony Corporation
6-7-35 Kitashinagawa
Shinagawa-ku
Tokyo 141-0001
Japan
Phone: +81 3 5448 2125
Email: satosi-f@sm.sony.co.jp
URI: http://www.sony.com/
Eisaburo Itakura
Sony Corporation
6-7-35 Kitashinagawa
Shinagawa-ku
Tokyo 141-0001
Japan
Phone: +81 3 5448 2125
Email: itakura@sm.sony.co.jp
URI: http://www.sony.com/
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|tp |MHF|mh_id|T| priority | tile number | |tp |MHF|mh_id|T| priority | tile number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|reserved | fragment offset | |reserved | fragment offset |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
For the first packet with the main header, this is what it will Figure 2
look like.
Note, for this example MTU will be taken as: 1500bytes (Ethernet)
Sample 1: Progressive image with single tile, 3500bytes
(i.e. thumbnail)
First Packet: First Packet: This packet will have the whole main header. 210bytes
This packet will have the whole main header.
210bytes
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 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 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 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 .... | |FF4FFF51002F000 .... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Second Packet: Figure 3
This packet will have a tile header and the first tile part LLband
1500bytes Second Packet: This packet will have a tile header and the first tile
part LLband 1500bytes
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 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 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 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|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF90 000A 0000 0000 2DB3 0001 FF93 | |FF90 000A 0000 0000 2DB3 0001 FF93 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Third Packet: Figure 4
This packet will have the next part in the tile, no tile header Third Packet: This packet will have the next part in the tile, no
1500bytes tile header 1500bytes
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|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 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 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|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|E841 4526 4556 9850 C2EA .... | |E841 4526 4556 9850 C2EA .... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Fourth Packet:
Last packet for the image Figure 5
290bytes
Fourth Packet: Last packet for the image 290bytes
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|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 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 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|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|A55D 8B73 3B25 25C7 B9EB .... 2FBEB153| |A55D 8B73 3B25 25C7 B9EB .... 2FBEB153|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Smaple 2: Image with 4 tiles Figure 6
First Packet: First Packet: This packet will have the whole main header. 210bytes
This packet will have the whole main header.
210bytes
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 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 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 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 .... | |FF4FFF51002F000 .... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Second Packet: Figure 7
This packet will have a first tile part (tile 0) Second Packet: This packet will have a first tile part (tile 0)
1400bytes 1400bytes
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|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 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 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|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF90 000A 0000 0000 0578 0001 FF93 .... | |FF90 000A 0000 0000 0578 0001 FF93 .... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Third Packet:
This packet will have a second tile part (tile 1) Figure 8
Third Packet: This packet will have a second tile part (tile 1)
1423bytes 1423bytes
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|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 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 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|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF90 000A 0001 0000 058F 0001 FF93 .... | |FF90 000A 0001 0000 058F 0001 FF93 .... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 15, line 17 skipping to change at page 21, line 32
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|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 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 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|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF90 000A 0001 0000 058F 0001 FF93 .... | |FF90 000A 0001 0000 058F 0001 FF93 .... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Fourth Packet: Figure 9
This packet will have a third tile part (tile 2)
Fourth Packet: This packet will have a third tile part (tile 2)
1355bytes 1355bytes
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|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 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 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|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF90 000A 0002 0000 054B 0001 FF93 .... | |FF90 000A 0002 0000 054B 0001 FF93 .... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Fifth Packet: Figure 10
This packet will have a fourth tile part (tile 3) Fifth Packet: This packet will have a fourth tile part (tile 3)
1290bytes 1290bytes
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|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 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 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|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF90 000A 0003 0000 050A 0001 FF93 .... | |FF90 000A 0003 0000 050A 0001 FF93 .... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Sample 3: Packing multiple tiles in single payload, fragmented header Figure 11
No header compensation, progressive image
First Packet: This packet will have the first part of the main
header. 110bytes
First Packet:
This packet will have the first part of the main header.
110bytes
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 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 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 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 .... | |FF4FFF51002F000 .... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Second Packet: Figure 12
This packet has the second part of the header.
Second Packet: This packet has the second part of the header.
1400bytes 1400bytes
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 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 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 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|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF6400FF .... | |FF6400FF .... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Third Packet: Figure 13
This packet has two tiles, tile 0 and tile 1 Third Packet: This packet has two tiles, tile 0 and tile 1 1400bytes
1400bytes
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 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 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 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|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|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 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Fourth Packet:
This packet has one tile, tile 2 Figure 14
1395bytes
Fourth Packet: This packet has one tile, tile 2 1395bytes
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|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 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 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|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF90 000A 0002 0000 0573 0001 FF93 .... | |FF90 000A 0002 0000 0573 0001 FF93 .... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Sample 4: Interlace image, single tile Figure 15
First packet: First packet: This packet will have the whole main header for the odd
This packet will have the whole main header for the odd field field 210bytes
210bytes
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| |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|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|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 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 .... | |FF4FFF51002F000 .... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Second packet: Figure 16
This packet will have the first part of the odd field's tile Second packet: This packet will have the first part of the odd
1400bytes field's tile 1400bytes
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| |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|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|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 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|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF90 000A 0000 0000 0578 0001 FF93 .... | |FF90 000A 0000 0000 0578 0001 FF93 .... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Third packet:
This packet will have the second part of the odd field's tile Figure 17
1400bytes
Third packet: This packet will have the second part of the odd
field's tile 1400bytes
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| |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|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|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 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|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|7F04 E708 27D9 D11D 22CB ... | |7F04 E708 27D9 D11D 22CB ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Fourth packet: Figure 18
This packet will have the third part of the odd field's tile
1300bytes Fourth packet: This packet will have the third part of the odd
field's tile 1300bytes
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| |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|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|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 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|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|98BD EC9B 2826 DC62 D4AB ... | |98BD EC9B 2826 DC62 D4AB ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Fifth packet: Figure 19
This packet will have the whole main header for the even field Fifth packet: This packet will have the whole main header for the
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| |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|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|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 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 .... | |FF4FFF51002F000 .... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Sixth packet:
This packet will have the first part of the odd field's tile Figure 20
1400bytes
Sixth packet: This packet will have the first part of the odd field's
tile 1400bytes
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| |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|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|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 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|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF90 000A 0000 0000 0578 0001 FF93 .... | |FF90 000A 0000 0000 0578 0001 FF93 .... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Seventh packet: Figure 21
This packet will have the second part of the odd field's tile
1400bytes Seventh packet: This packet will have the second part of the odd
field's tile 1400bytes
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| |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 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 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|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|626C 42F0 166B 6BD0 F8E1 ... | |626C 42F0 166B 6BD0 F8E1 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Eighth packet: Figure 22
This packet will have the third part of the odd field's tile Eighth packet: This packet will have the third part of the odd
1300bytes field's tile 1300bytes
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| |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 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 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|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|8114 41D5 18AB 4A1B ... | |8114 41D5 18AB 4A1B ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
11. Intellectual Property Right Statement Figure 23
Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed Intellectual Property Rights or other rights that might be claimed to
to pertain to the implementation or use of the technology described pertain to the implementation or use of the technology described in
in this document or the extent to which any license under such this document or the extent to which any license under such rights
rights might or might not be available; nor does it represent that might or might not be available; nor does it represent that it has
it has made any independent effort to identify any such rights. made any independent effort to identify any such rights. Information
Information on the procedures with respect to rights in RFC on the procedures with respect to rights in RFC documents can be
documents can be found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use attempt made to obtain a general license or permission for the use of
of such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository specification can be obtained from the IETF on-line IPR repository at
at http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
12. Informative Appendix Disclaimer of Validity
12.1 Recommended Practices
Receiver Processing
In general, the receiver should scan for headers in packets
that have an MHF value > 0 to aid in main header recovery.
Receivers should be aware of both BEAM capable and incapbale
senders. If the sender is incapable of BEAM functionality,
receivers should not interpret headers as described in this
document.
13. References
Normative References
[1] S. Bradner, "Key words for use in RFCs to Indicate Requirement
Levels", BCP14, RFC2119, March 1997.
[2] ISO/IEC JTC1/SC29, ISO/IEC 15444-1 | ITU-T Rec. T.800
"Information technology - JPEG 2000 image coding system -
Part 1: Core coding system", December 2000.
[3] H. Schulzrinne, S. Casner, R. Frederick, and V. Jacobson,
"RTP: A Transport Protocol for Real Time
Applications", STD 64, RFC
3550, July 2003.
[4] M. Baugher, D. McGrew, M. Naslund, E. Carrara and K. Norrman,
"The Secure Real-time Transport Protocol (SRTP)", RFC 3711,
March 2004.
[5] M. Handley and V. Jacobson, "SDP: Session Description
Protocol", RFC 2327, April 1998.
[6] J. Rosenberg and H. Schulzrinne, "An Offer/Answer Model with
Session Description Protocol (SDP)", RFC 3264, June 2002.
Informative References
[7] Deering, S., "Host Extensions for IP Multicasting", STD 5,
RFC 1112, August 1989.
14. Authors' Addresses This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Andrew Leung/Satoshi Futemma/Eisaburo Itakura Copyright Statement
Sony Corporation
6-7-35 Kitashinagawa Shinagawa-ku
Tokyo 141-0001 JAPAN
Phone: +81 3 5448 2125
Fax: +81 3 5448 4560
Email: andrew.leung@jp.sony.com, {satosi-f|itakura}@sm.sony.co.jp
15. Full Copyright Statement Copyright (C) The Internet Society (2005). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
Copyright (C) The Internet Society (2004). This document is Acknowledgment
subject to the rights, licenses and restrictions contained in BCP
78, and except as set forth therein, the authors retain all their
rights.
This document and the information contained herein are provided on Funding for the RFC Editor function is currently provided by the
an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE Internet Society.
REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT
THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR
ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE.
 End of changes. 

This html diff was produced by rfcdiff 1.25, available from http://www.levkowetz.com/ietf/tools/rfcdiff/