[Docs] [txt|pdf] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits]

Versions: (draft-edwards-avt-rtp-jpeg2000) 00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 RFC 5371

Satoshi
INTERNET-DRAFT                                          Satoshi Futemma
draft-ietf-avt-rtp-jpeg2000-07.txt                         Andrew Leung
                                                       Eisaburo Itakura
                                                       Sony Corporation
                                                      December 30, 2004
                                                 Expires: June 30, 2005


              RTP Payload Format for JPEG 2000 Video Streams

Status of this Memo

    By submitting this Internet-Draft, we certify that any applicable
    patent or other IPR claims of which I am aware have been disclosed,
    and any of which we become aware will be disclosed, in accordance
    with RFC 3668.

    Internet-Drafts are working documents of the Internet Engineering
    Task Force (IETF), its areas, and its working groups. Note that
    other groups may also distribute working documents as
    Internet-Drafts.

    Internet-Drafts are draft documents valid for a maximum of six
    months and may be updated, replaced, or obsoleted by other
    documents at any time. It is inappropriate to use Internet-Drafts
    as reference materials or to cite them other than as "work in
    progress."

    The list of current Internet-Drafts can be accessed at
    http://www.ietf.org/ietf/1id-abstracts.txt

    The list of Internet-Drafts Shadow Directories can be accessed at
    http://www.ietf.org/shadow.html.

Abstract

    This memo describes an RTP payload format for the ISO/IEC
    International Standard 15444-1 | ITU-T Rec. T.800, otherwise better
    known as: JPEG 2000.
    JPEG 2000 features are considered and there are provisions in the
    design of this payload format for scalability. JPEG 2000 is a truly
    scalable compression technology allowing applications to encode one
    way and decode many different ways. Extending from a single image
    to a series of JPEG 2000 images, one has a JPEG 2000 video stream.





















Futemma, et al.                                                [Page 1]

INTERNET-DRAFT    draft-ietf-avt-rtp-jpeg2000-07.txt  December 30, 2004


Table of Contents

    1.  Introduction ..............................................  3
      1.1   Conventions Used in this Document .....................  5
    2.  JPEG 2000 Video Features ..................................  6
    3.  Payload Design ............................................  6
    4.  Payload Format ............................................  6
      4.1   RTP fixed header usage ................................  6
      4.2   RTP Payload Header Format .............................  7
    5.  RTP Packetization .........................................  9
    6.  Security Consideration .................................... 10
    7.  IANA Consideration ........................................ 11
      7.1   MIME Registration ..................................... 11
      7.2   SDP Parameters ........................................ 13
    8.  Usage with the SDP Offer/Answer Model ..................... 13
      8.1   Examples  ............................................. 13
    9.  Intellectual Property Right Statement ..................... 14
    10.  Informative Appendix  .................................... 14
      10.1   Recommended Practices ................................ 14
      10.2   Sample Headers in Detail ............................. 15
    11.  References  .............................................. 21
    12.  Authors' Addresses ....................................... 22
    13.  Full Copyright Statement ................................. 22































Futemma, et al.                                                [Page 2]

INTERNET-DRAFT    draft-ietf-avt-rtp-jpeg2000-07.txt  December 30, 2004

1. Introduction

    This document specifies a payload formats for JPEG 2000 video
    streams over the Real-time Transport Protocol (RTP). JPEG 2000 is
    an ISO/IEC International Standard and ITU-T Recommendation (ISO/IEC
    International Standard 15444-1 | ITU-T Rec. T.800) developed for
    next generation still image compression. JPEG is and stands for
    the: Joint Photograhers Experts Group developing the standard. Its
    basic compression technology is described in detail in [1] & [7].

    Part 3 of the JPEG 2000 standard defines Motion JPEG 2000 [7].
    However, Motion JPEG 2000 focuses on the file format and it does
    not specify the transmission format for the network.

    JPEG 2000 supports many powerful features that are not supported
    in the current JPEG standard [1] & [7]:

      o Higher compression efficiency than JPEG with less visual loss
      or distortion especially at extreme compression ratios.

      o A single codestream that offers both lossy and superior
      lossless compression.

      o Better error resiliency than JPEG.

      o Progressive transmission by pixel accuracy (SNR scalability)
      and resolution (resolution scalability.)

      o Random codestream access and processing.

    The JPEG 2000 algorithm is briefly explained. Figure 1 shows a
    block diagram of the JPEG 2000 encoding method.

                                                     +-----+
                                                     | ROI |
                                                     +-----+
                                                        |
                                                        V
                   +----------+   +----------+   +------------+
                   |DC, comp. |   | Wavelet  |   |            |
    raw image  ==> |transform-|==>|transform-|==>|Quantization|==+
                   |  ation   |   |  ation   |   |            |  |
                   +----------+   +----------+   +------------+  |
                                                                 |
                  +-----------+   +----------+   +------------+  |
                  |           |   |          |   |            |  |
     JPEG 2000 <==| Data      |<==| Rate     |<==| EBCOT      |<=+
     codestream   | Ordering  |   | Control  |   |            |
                  +-----------+   +----------+   +------------+

           Figure 1: Block diagram of the JPEG 2000 encoder

    The image is transformed into wavelet coefficients. The image is
    sampled into various levels usually vertically and horizontally

Futemma, et al.                                                [Page 3]

INTERNET-DRAFT    draft-ietf-avt-rtp-jpeg2000-07.txt  December 30, 2004

    from high frequencies (which contains all the sharp details) to the
    low frequencies (which contains all the flat areas.)  Quantization
    is performed on the coefficients within each sub-band.

    After quantization, code blocks are formed from within the
    precincts within the tiles. Precincts are a finer separation than
    tiles and code blocks are the smallest separation of the image
    data. EBCOT coding (Embedded Block Coding Optimized for Truncation)
    is performed within each code block and arithmetically encoded by
    bit plane. Rate control is performed to achieve the highest quality
    image for the specified rate.

    As a result, for a given tile, data units called JPEG 2000 packets
    are generated, which contain data from a specific layer, a specific
    component, a specific resolution, and a specific precinct.

    Finally, the JPEG 2000 packets are interleaved according to the
    progression along four axes: layer, resolution, component and
    precinct, and add a JPEG 2000 header to become a fully compliant
    JPEG 2000 codestream.

    To decompress a JPEG 2000 codestream, one would follow the reverse
    order of the encoding order, minus the quantization, rate control,
    and data ordering step.

    It is outside the scope of this document to describe in detail
    this procedure. Please refer to various JPEG 2000 texts for
    further details [1].

    Figure 2 shows a JPEG 2000 codestream in detail. A JPEG 2000
    codestream is structured from the main header beginning with the
    SOC (Start Of Codestream) marker, one or more tiles, and the EOC
    (End Of Codestream) marker to indicate the end of the codestream.
    Each tile consists of a tile-part header that starts with the SOT
    (Start of Tile) marker and ends with a SOD (Start of Data) marker,
    and bitstream (a series of JPEG 2000 packet.)

           +--  +------------+
     Main  |    |    SOC     |  Required as the first marker.
     header|    +------------+
           |    |    main    |  Main header marker segments
           +--  +------------+
           |    |    SOT     |  Required at the beginning of each
     Tile- |    +------------+    tile-part header.
     part  |    |   T0,TP0   |  Tile 0, tile-part 0 header marker
     header|    +------------+    segments
           |    |    SOD     |  Required at the end of each tile-part
           +--  +------------+    header
                | bitstream  |  Tile-part bitstream
           +--  +------------+
           |    |    SOT     |
     Tile- |    +------------+
     part  |    |   T1,TP0   |
     header|    +------------+

Futemma, et al.                                                [Page 4]

INTERNET-DRAFT    draft-ietf-avt-rtp-jpeg2000-07.txt  December 30, 2004

           |    |    SOD     |
           +--  +------------+
                | bit stream |
                +------------+
                      .
                      .
                      .
                +------------+
                |    EOC     |  Required as the last marker in the code
                +------------+  stream

          Figure 2: Basic construction of the JPEG 2000 codestream

1.1 Conventions Used in this Document

    The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
    NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
    in this document are to be interpreted as described in RFC2119
    [2].

2. JPEG 2000 Video Features

    JPEG 2000 video streams are formed as a continuous series of JPEG
    2000 still images. Previously described features of JPEG 2000 may
    be used effectively in streaming applications. A JPEG 2000 video
    stream has the following qualities:

    o At low bit rates, the SNR is improved dramatically over JPEG and
      Motion JPEG.

    o This is a full intra frame format - each frame is independently
      compressed - and therefore has a low encoding and decoding delay.

    o JPEG 2000 has flexible and accurate rate control.

      This is suitable for traffic control and congestion control
      during network transmission.

    o JPEG 2000 can provide its own codestream error resilience markers
      to aid in codestream recovery outside of this specification.

3. Payload Design

    To provide a payload format that maximizes JPEG 2000 features, the
    following are taken into consideration:

    o Provisions for packet loss

      On the Internet, 5% packet loss is common and this percentage may
      vary, upto 20% or more. To split JPEG 2000 video streams into RTP
      packets, efficient packetization of the code stream is required
      to minimize problems in decoding due to missing packets. If the
      main header is lost in transmission, the image cannot be decoded.


Futemma, et al.                                                [Page 5]

INTERNET-DRAFT    draft-ietf-avt-rtp-jpeg2000-07.txt  December 30, 2004


4. Payload Format

4.1 RTP fixed header usage

    For each RTP packet, the RTP fixed header is followed by the JPEG
    2000 RTP payload header (this specification), which is followed by
    the payload, a piece of a JPEG 2000 codestream.

    The RTP header fields that have a meaning specific to a JPEG 2000
    video stream are described as follows:

    Marker bit (M): The marker bit of the RTP fixed header MUST be set
      to 1 on the last RTP packet of a video frame, otherwise, it
      MUST be 0. When transmission is performed by multiple RTP
      sessions, this bit is 1 in the last packet of the frame in each
      session.

    Payload type (PT): The payload type is dynamically assigned by
      means outside the scope of this document. A payload type in the
      dynamic range shall be chosen by means of an out of band
      signaling protocol (e.g., RTSP, SIP, etc.)

    Timestamp: The RTP timestamp are in units of 90 kHz. The same
      timestamp value MUST appear in each RTP packet carrying a
      fragment of a given frame. When a JPEG 2000 image is in interlace
      format, the odd field and the corresponding even field MUST have
      the same timestamp. The initial value of the timestamp is to be
      random to counter known plaintext attacks on encryption.

4.2 RTP Payload Header Format

    The RTP payload header format for JPEG 2000 video stream is as
    follows:

     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
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |tp |MHF|mh_id|T|     priority  |           tile number         |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |reserved       |             fragment offset                   |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

    Figure 3:  RTP payload header format for JPEG 2000

    tp (type) : 2 bits

        This field indicates how a JPEG 2000 image is scanned (meaning
        - progressive or interlace).

        0: If the payload is progressively scanned.

        1: An image is the odd field of an interlaced video signal.
        The height specified in the JPEG 2000 main header is half

Futemma, et al.                                                [Page 6]

INTERNET-DRAFT    draft-ietf-avt-rtp-jpeg2000-07.txt  December 30, 2004

        of the height of the entire displayed image. In a receiver, an
        odd field should be de-interlaced with the even field following
        it so that lines from each image are displayed alternately.

        2: An image is the even field of an interlaced video signal.

        3: An image is a single field from an interlaced video
        signal, intended to be displayed full frame as if it were
        received as both the odd & even field of the frame. On a
        computer monitor, each line in the image should be
        displayed twice, doubling the height of the image.

    MHF (Main Header Flag) : 2 bits

        MHF indicates whether a main header or piece of a main header
        is in the RTP packet.

        If there is no header, MHF has a value of 0.
        If there is just a part of a fragmented header, MHF has a value
        of 1.
        If there is the last part of a fragmented header, MHF has value
        of 2.
        If the whole header in the packet, MHF has a value of 3.

        +----+-------------------------------------------------------+
        |MHF | Description                                           |
        +----+-------------------------------------------------------+
        | 0  | no main header in the payload                         |
        | 1  | piece of fragmented header                            |
        | 2  | last part of a fragmented header                      |
        | 3  | a whole main header                                   |
        +----+-------------------------------------------------------+
        Table 1: MHF usage values

    mh_id (Main Header Identification) : 3 bits

        Main header identification value. This is used for JPEG
        2000 main header recovery.

        For implementations following this specification, the sender
        SHOULD set this value to 0 and the receiver SHOULD ignore this
        field on processing.

        Usage of this header is described in further 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.

    T (Tile field invalidation flag) : 1 bit

        T bit indicates whether the tile number field is valid or
        invalid. A sender MUST set the T bit to 1 when the tile number
        field is invalid and 0 when valid.


Futemma, et al.                                                [Page 7]

INTERNET-DRAFT    draft-ietf-avt-rtp-jpeg2000-07.txt  December 30, 2004

        There are two cases where the tile number field is invalid.

        (1) When an RTP packet holds only the main header.
        A sender cannot set any number in the tile number field as no
        JPEG 2000 tile-part bitstream is included in the RTP packet.

        (2) Multiple tile-parts are packed together in one payload.
        If there are multiple tiles packed into one payload, there is
        no meaning to assign a number to the tile number field.

    priority : 8 bits

        The priority field indicates the importance of the JPEG 2000
        packet included in the payload. Typically, a higher priority
        is set in the packets containing JPEG 2000 packets containing
        the lower sub-bands.

        For implementations following this specification, the sender
        SHOULD set this value to 255 and the receiver SHOULD ignore
        this field on processing.

        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.

    tile number : 16 bits

        This field shows the tile number that a payload belongs to
        only when the T bit is 0. If T bit is set to 1, the receiver
        MUST ignore this field.

    R (Reserved) : 8 bits

        This bit is reserved for future use. This MUST be set to 0 by
        the sender. Receivers MUST ignore this field.

    fragment offset : 24 bits

        This value MUST be set to the byte offset of the current
        payload in relation to the very beginning of each JPEG 2000
        codestream (JPEG 2000 frame).

        Byte offsets are calculated from the start of each JPEG 2000
        codestream upto the current position where the current
        payload would fit into the complete JPEG 2000 image codestream.

        To perform scalable video delivery by using multiple RTP
        sessions, the offset value from the first byte of the same
        frame is set for fragment offset. It is possible, to deliver
        layered video using multiple RTP sessions, the fragment
        offset may not start from 0 in some RTP sessions even if the
        packet is the first one received.


Futemma, et al.                                                [Page 8]

INTERNET-DRAFT    draft-ietf-avt-rtp-jpeg2000-07.txt  December 30, 2004

5. RTP Packetization

    The sender must packetize the JPEG 2000 appropriately according to
    initial MIME parameters and/or details from SDP offer/answer
    parameters.

    A "packetization unit" is defined as either a JPEG 2000 main
    header, a tile-part header, or a JPEG 2000 packet.

    First, a sender divides the JPEG 2000 codestream into
    packetization units by parsing the codestream or by getting
    information from the encoder, and packs the packetization units
    into RTP packets. A sender can put an arbitrary number of
    packetization units into an RTP packet, but it  MUST preserve the
    codestream order. An example of this kind of RTP packet format is
    below:

    +------+-------+---------------+---------------+
    |RTP   |payload| packetization | packetization |
    |header|header | unit          | unit          |
    +------+-------+---------------+---------------+

    Figure 4: An Example of RTP packet format with multiple
              packetization units

    If a packetization unit with headers (IP header, RTP header and
    payload header) is larger than the MTU size, it MAY be fragmented.
    To pack a fragmented packetization unit, the fragmented unit MUST
    NOT be packed with the succeeding packetization unit within the
    same RTP packet. An example of this kind of RTP packet format is
    below:

    +------+-------+-------------------------------------------------+
    |RTP   |payload| packetization unit fragment                     |
    |header|header |                                                 |
    +------+-------+-------------------------------------------------+
    +------+-------+-------------------------------------------------+
    |RTP   |payload| packetization unit fragment                     |
    |header|header |                                                 |
    +------+-------+-------------------------------------------------+
                     .
                     .
                     .
    +------+-------+--------------------------------------------+
    |RTP   |payload| end of packetization unit fragment         |
    |header|header |                                            |
    +------+-------+--------------------------------------------+

    Figure 5: An Example of RTP packet format with a fragmented
              packetization unit


6. Security Consideration


Futemma, et al.                                                [Page 9]

INTERNET-DRAFT    draft-ietf-avt-rtp-jpeg2000-07.txt  December 30, 2004

    RTP packets using the payload format defined in this specification
    are subject to the security considerations discussed in the RTP
    specifications[3] and any applicable profile. This implies that
    confidentiality of the media streams is achieved by encryption.
    Data compression used with this payload format is applied
    end-to-end, encryption may be performed on the compressed data so
    there is no conflict between the two operations.

    A potential denial-of-service threat exists for data encodings
    using compression techniques that have non-uniform receiver-end
    computational load.  The attacker can inject pathological
    datagrams into the stream which are complex to decode and cause
    the receiver to be overloaded. The usage of authentication of at
    least the RTP packet is RECOMMENDED, for example with SRTP [4].

    If QoS enhanced service is used, RTP receivers SHOULD monitor
    packet loss to ensure that the service that was requested is
    actually being delivered. If it is not, then they SHOULD assume
    that they are receiving best-effort service and behave accordingly.

    If best-effort service is being used, users of this payload format
    MUST monitor packet loss to ensure that the packet loss rate is
    within acceptable parameters. Packet loss is considered acceptable
    if a TCP flow across the same network path, experiencing the same
    network conditions, would achieve an average throughput, measured
    on a reasonable timescale, that is not less than the RTP flow is
    achieving. This condition can be satisfied by implementing
    congestion control mechanisms to adapt the transmission rate (or
    the number of layers subscribed for a layered multicast session),
    or by arranging for a receiver to leave the session if the loss
    rate is unacceptably high.

    As with any IP-based protocol, in some circumstances a receiver
    may be overloaded simply by receiving too many packets, either
    desired or undesired. Network-layer authentication may be used to
    discard packets from undesired sources, but the processing cost of
    the authentication itself may be too high. In a multicast
    environment, pruning of specific sources may be implemented in
    future versions of IGMP [8] and in multicast routing protocols to
    allow a receiver to select which sources are allowed to reach it.

7. IANA Consideration

7.1 MIME Registration

    This document defines a new RTP payload name and associated MIME
    type, jpeg2000.

    The receiver MUST ignore any unspecified parameter.

    The MIME registration form for JPEG 2000 video stream is enclosed
    below:

    MIME media type name:    video

Futemma, et al.                                               [Page 10]

INTERNET-DRAFT    draft-ietf-avt-rtp-jpeg2000-07.txt  December 30, 2004


    MIME subtype name:       jpeg2000

    REQUIRED parameters:     sampling

      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, U & V are
                            subsampled horizontally by 1/2
        - "YCbCr-4:2:0"   - standard YCbCr color space, U & V are
                            subsampled horizontally and vertically by
                            1/2
        - "YCbCr-4:1:1"   - standard YCbCr color space, U & V are
                            subsampled vertically by 1/4
        - "GRAYSCALE"     - basically a single component image of just
                            multilevels of grey.

    OPTIONAL parameters:
      interlace: interlace scanning. If this options is present, it
        means the payload is in interlace format. Each complete image
        forms vertically half the display. tp value MUST properly
        specify the field the image represents odd(tp=1), even(tp=2),
        or frame(tp=3). If this option is not present, the payload is
        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.

    Encoding considerations:
        JPEG 2000 video stream may be transmitted with RTP as specified
        in this document.

    Security considerations: see section 9 of RFC XXXX.

    Interoperability considerations:
        JPEG 2000 video stream is a sequence of JPEG 2000 still
        images. An implementation in compliant with [1] can decode and
        attempt to display the encoded JPEG 2000 video stream.


Futemma, et al.                                               [Page 11]

INTERNET-DRAFT    draft-ietf-avt-rtp-jpeg2000-07.txt  December 30, 2004

    Published specification: ISO/IEC 15444-1 | ITU-T Rec. T.800

    Applications which use this media type:
        video streaming and communication

    Additional information: none

    Magic number(s): none

    File extension(s): none

    Macintosh File Type Code(s): none

    Person & email address to contact for further information:
        Eisaburo Itakura, Satoshi Futemma
        Email: {itakura|satosi-f}@sm.sony.co.jp

    Intended usage: COMMON

    Author/Change controller:
        Eisaburo Itakura, Satoshi Futemma
        Email: {itakura|satosi-f}@sm.sony.co.jp

7.2 SDP Parameters

    The MIME media type video/jpeg2000 string is mapped to fields in
    the Session Description Protocol (SDP) [4] 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 MUST be 90000.

    o The REQUIRED parameters "sampling", MUST be included in the
      "a=fmtp" line of SDP.

    o The OPTIONAL parameters "width", and "height", when present,
      MUST be included in the "a=fmtp" line of SDP.

    These parameters are expressed as a MIME 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 sampling=YCbCr-4:2:0;width=128;height=128

8. Usage with the SDP Offer/Answer Model

    When offering JPEG 2000 over RTP using SDP in an Offer/Answer model

Futemma, et al.                                               [Page 12]

INTERNET-DRAFT    draft-ietf-avt-rtp-jpeg2000-07.txt  December 30, 2004

    [5], the following rules and limitations apply:

    o All parameters MUST have an acceptable value for that parameter.

    o All parameters MUST correspond to the parameters of the payload.

    o The parameters "sampling" MUST appear in the offer and the answer

    o For optional parameters "width" and "height" the following
      applies:

       -if "width" appears in the offer or answer, "height" MUST be
        present.
       -if "height" appears in the offer or answer, "width" MUST be
        present.

8.1 Examples

    An example offer/answer exchanges are provided.

    Alice offers YCbCr 422 color space, interlace image with 720-pixel
    width and 480-pixel height as below:

    v=0
    o=alice 2890844526 2890844526 IN IP4 host.anywhere.com
    s=
    c=IN IP4 host.anywhere.com
    t=0 0
    m=video 49170 RTP/AVP 98
    a=rtpmap:98 jpeg2000/90000
    a=fmtp:98 sampling=YCbCr-4:2:2;interlace
    a=fmtp:98 width=720; height=480

    Bob accepts YCbCr-4:2:2 color space, interlace image and replies:

    v=0
    o=bob 2890844730 2890844731 IN IP4 host.example.com
    s=
    c=IN IP4 host.example.com
    t=0 0
    m=video 49920 RTP/AVP 98
    a=rtpmap:98 jpeg2000/90000
    a=fmtp:98 sampling=YCbCr-4:2:2;interlace


9. Intellectual Property Right Statement

    The IETF takes no position regarding the validity or scope of any
    Intellectual Property Rights or other rights that might be claimed
    to pertain to the implementation or use of the technology described
    in this document or the extent to which any license under such
    rights might or might not be available; nor does it represent that
    it has made any independent effort to identify any such rights.
    Information on the procedures with respect to rights in RFC

Futemma, et al.                                               [Page 13]

INTERNET-DRAFT    draft-ietf-avt-rtp-jpeg2000-07.txt  December 30, 2004

    documents can be found in BCP 78 and BCP 79.

    Copies of IPR disclosures made to the IETF Secretariat and any
    assurances of licenses to be made available, or the result of an
    attempt made to obtain a general license or permission for the use
    of such proprietary rights by implementers or users of this
    specification can be obtained from the IETF on-line IPR repository
    at http://www.ietf.org/ipr.

    The IETF invites any interested party to bring to its attention any
    copyrights, patents or patent applications, or other proprietary
    rights that may cover technology that may be required to implement
    this standard.  Please address the information to the IETF at
    ietf-ipr@ietf.org.

10. Informative Appendix

10.1 Recommended Practices

    As the JPEG 2000 coding standard is highly flexible, many
    different but compliant data streams can be produced and still be
    labeled as a JPEG 2000 data stream.

    The following is a set of recommendations set forth from our
    experience in developing JPEG 2000 and this payload
    specification. Implementations of this standard must handle all
    possibilities mentioned in this specification. The following is a
    listing of items an implementation could optimize.

    Error Resilience Markers

        The use of error resilience markers in the JPEG 2000 data
        stream is highly recommended in all situations. Error
        recovery with these markers is helpful to the decoder and save
        external resources. Markers such as: RESET, RESTART, and
        ERTERM.

    YCbCr Color space

        The YCbCr color space provides the greatest amount of
        compression in color with respect to the human visual
        system. When used with JPEG 2000, the usage of this color
        space can provide excellent visual results at extreme bit
        rates.

    Progression Ordering

        JPEG 2000 offers many different ways to order the final code
        stream to optimize the transfer with the presentation. The
        most useful ordering in our usage cases have been for layer
        progression and resolution progression ordering.

    Tiling and Packets


Futemma, et al.                                               [Page 14]

INTERNET-DRAFT    draft-ietf-avt-rtp-jpeg2000-07.txt  December 30, 2004

        JPEG 2000 packets are formed regardless of the encoding
        method. The encoder has little control over the size of these
        JPEG 2000 packets as they maybe large or small.

        Tiling splits the image up into smaller areas and each are
        encoded separately. With tiles, the JPEG 2000 packet sizes
        are also reduced. When using tiling, almost all JPEG 2000
        packet sizes are an acceptable size (i.e. smaller than the MTU
        size of most networks.)

    Sender Processing

        There are no limitations as to how the sender should pack the
        payload. In general, the sender should pack headers separately
        from the rest of the codestream to make header recovery simple.
        Payloads should generally begin with an SOP marker and end with
        EPH marker for easier decoder processing.

10.2 Sample Headers in Detail

  This section has various sample headers in various configurations for
  reference.

    For reference, the payload header.

     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
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |tp |MHF|mh_id|T|     priority  |           tile number         |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |reserved       |             fragment offset                   |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

    For the first packet with the main header, this is what it will
    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:
    This packet will have the whole main header.
    210bytes

     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 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|
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |FF4FFF51002F000 ....                                           |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Futemma, et al.                                               [Page 15]

INTERNET-DRAFT    draft-ietf-avt-rtp-jpeg2000-07.txt  December 30, 2004


    Second Packet:
    This packet will have a tile header and the first tile part LLband
    1500bytes

     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 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|
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |FF90 000A 0000 0000 2DB3  0001 FF93                            |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

    Third Packet:
    This packet will have the next part in the tile, no tile header
    1500bytes

     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 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|
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |E841 4526 4556 9850 C2EA  ....                                 |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

    Fourth Packet:
    Last packet for the image
    290bytes

     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 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|
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |A55D 8B73 3B25 25C7 B9EB        ....                   2FBEB153|
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

  Smaple 2: Image with 4 tiles

    First Packet:
    This packet will have the whole main header.
    210bytes

     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 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|
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Futemma, et al.                                               [Page 16]

INTERNET-DRAFT    draft-ietf-avt-rtp-jpeg2000-07.txt  December 30, 2004

    |0 0 0 0 0 0 0 0|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 ....                                           |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

    Second Packet:
    This packet will have a first tile part (tile 0)
    1400bytes

     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 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|
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |FF90 000A 0000 0000 0578  0001 FF93  ....                      |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

    Third Packet:
    This packet will have a second tile part (tile 1)
    1423bytes

     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 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|
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |FF90 000A 0001 0000 058F 0001 FF93    ....                     |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

    Fourth Packet:
    This packet will have a third tile part (tile 2)
    1355bytes

     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 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|
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |FF90 000A 0002 0000 054B 0001 FF93    ....                     |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

    Fifth Packet:
    This packet will have a fourth tile part (tile 3)
    1290bytes

     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
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Futemma, et al.                                               [Page 17]

INTERNET-DRAFT    draft-ietf-avt-rtp-jpeg2000-07.txt  December 30, 2004

    |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|
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |FF90 000A 0003 0000 050A 0001 FF93    ....                     |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+


  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 header.
    110bytes

     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 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|
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |FF4FFF51002F000 ....                                           |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

    Second Packet:
    This packet has the second part of the header.
    1400bytes

     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 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|
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |FF6400FF ....                                                  |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

    Third Packet:
    This packet has two tiles, tile 0 and tile 1
    1400bytes

     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 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|
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |FF90 000A 0000 0000 02BC 0001 FF93  ...                        |
    |FF90 000A 0001 0000 02BC 0001 FF93 ...                         |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+


Futemma, et al.                                               [Page 18]

INTERNET-DRAFT    draft-ietf-avt-rtp-jpeg2000-07.txt  December 30, 2004

    Fourth Packet:
    This packet has one tile, tile 2
    1395bytes

     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 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|
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |FF90 000A 0002 0000 0573 0001 FF93    ....                     |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

  Sample 4: Interlace image, single tile

    First packet:
    This packet will have the whole main header for the odd field
    210bytes

     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|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|
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |FF4FFF51002F000 ....                                           |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

    Second packet:
    This packet will have the first part of the odd field's tile
    1400bytes

     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|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|
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |FF90 000A 0000 0000 0578  0001 FF93  ....                      |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

    Third packet:
    This packet will have the second part of the odd field's tile
    1400bytes

     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|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|

Futemma, et al.                                               [Page 19]

INTERNET-DRAFT    draft-ietf-avt-rtp-jpeg2000-07.txt  December 30, 2004

    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |7F04 E708 27D9 D11D 22CB ...                                   |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

    Fourth packet:
    This packet will have the third part of the odd field's tile
    1300bytes

     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|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|
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |98BD EC9B 2826 DC62 D4AB ...                                   |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

    Fifth packet:
    This packet will have the whole main header for the even field

     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
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |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|
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |FF4FFF51002F000 ....                                           |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

    Sixth packet:
    This packet will have the first part of the odd field's tile
    1400bytes

     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
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |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|
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |FF90 000A 0000 0000 0578  0001 FF93  ....                      |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

    Seventh packet:
    This packet will have the second part of the odd field's tile
    1400bytes

     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
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |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|
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Futemma, et al.                                               [Page 20]

INTERNET-DRAFT    draft-ietf-avt-rtp-jpeg2000-07.txt  December 30, 2004

    |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 ...                                   |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

    Eighth packet:
    This packet will have the third part of the odd field's tile
    1300bytes

     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
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |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|
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |8114 41D5 18AB 4A1B ...                                        |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

11. References

Normative References

    [1] 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.

    [2] S. Bradner, "Key words for use in RFCs to Indicate Requirement
        Levels", BCP14, RFC2119, March 1997.

    [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] ISO/IEC JTC1/SC29, ISO/IEC 15444-3 "Information technology -
        JPEG 2000 image coding system - Part 3: Motion JPEG 2000",
        July 2002.

    [8] Deering, S., "Host Extensions for IP Multicasting", STD 5,
        RFC 1112, August 1989.


Futemma, et al.                                               [Page 21]

INTERNET-DRAFT    draft-ietf-avt-rtp-jpeg2000-07.txt  December 30, 2004

12. Authors' Addresses

    Satoshi Futemma/Eisaburo Itakura/Andrew Leung
    Sony Corporation
    6-7-35 Kitashinagawa Shinagawa-ku
    Tokyo 141-0001 JAPAN
    Phone: +81 3 5448 2125
    Fax:   +81 3 5448 4560
    Email: {satosi-f|itakura}@sm.sony.co.jp, andrew.leung@jp.sony.com

13. Full Copyright Statement

    Copyright (C) The Internet Society (2004).  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.

    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.































Futemma, et al.                                               [Page 22]


Html markup produced by rfcmarkup 1.107, available from http://tools.ietf.org/tools/rfcmarkup/