idnits 2.17.1 draft-ietf-avt-rtp-jpeg2000-beam-05.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 17. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 1142. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 1153. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 1160. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 1166. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (April 03, 2007) is 6232 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Possible downref: Non-RFC (?) normative reference: ref. '1' -- Possible downref: Non-RFC (?) normative reference: ref. '3' ** Obsolete normative reference: RFC 2327 (ref. '5') (Obsoleted by RFC 4566) ** Obsolete normative reference: RFC 4288 (ref. '7') (Obsoleted by RFC 6838) ** Obsolete normative reference: RFC 3555 (ref. '8') (Obsoleted by RFC 4855, RFC 4856) -- Obsolete informational reference (is this intentional?): RFC 2246 (ref. '9') (Obsoleted by RFC 4346) Summary: 4 errors (**), 0 flaws (~~), 1 warning (==), 10 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Audio Video Transport A. Leung 3 Internet-Draft S. Futemma 4 Intended status: Standards Track E. Itakura 5 Expires: October 5, 2007 Sony 6 April 03, 2007 8 Payload Format for JPEG 2000 Video: Extensions for Scalability and Main 9 Header Recovery 10 draft-ietf-avt-rtp-jpeg2000-beam-05 12 Status of this Memo 14 By submitting this Internet-Draft, each author represents that any 15 applicable patent or other IPR claims of which he or she is aware 16 have been or will be disclosed, and any of which he or she becomes 17 aware will be disclosed, in accordance with Section 6 of BCP 79. 19 Internet-Drafts are working documents of the Internet Engineering 20 Task Force (IETF), its areas, and its working groups. Note that 21 other groups may also distribute working documents as Internet- 22 Drafts. 24 Internet-Drafts are draft documents valid for a maximum of six months 25 and may be updated, replaced, or obsoleted by other documents at any 26 time. It is inappropriate to use Internet-Drafts as reference 27 material or to cite them other than as "work in progress." 29 The list of current Internet-Drafts can be accessed at 30 http://www.ietf.org/ietf/1id-abstracts.txt. 32 The list of Internet-Draft Shadow Directories can be accessed at 33 http://www.ietf.org/shadow.html. 35 This Internet-Draft will expire on October 5, 2007. 37 Copyright Notice 39 Copyright (C) The IETF Trust (2007). 41 Abstract 43 This memo describes extended uses for payload header in RFC document: 44 "RTP Payload Format for JPEG 2000 Video Streams." For better support 45 of JPEG 2000 features such as scalability and includes a main header 46 recovery method. 48 This memo MUST be accompanied with a complete implementation of "RTP 49 Payload Format for JPEG 2000 Video Streams." That document is a 50 complete description of the payload header and signaling, this 51 document only describes additional processing for the payload header. 52 There is an additional media type and SDP marker signaling for 53 implementations of this document. 55 Table of Contents 57 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 58 1.1. History . . . . . . . . . . . . . . . . . . . . . . . . . 4 59 1.2. Description of the Mechanisms . . . . . . . . . . . . . . 4 60 1.2.1. Main Header Compensation . . . . . . . . . . . . . . . 4 61 1.2.2. Priority Table . . . . . . . . . . . . . . . . . . . . 4 62 1.3. Motivations for Priority Field coding . . . . . . . . . . 5 63 1.3.1. Scenario: Just enough resolution . . . . . . . . . . . 5 64 1.3.2. Scenario: Multiple clients, single source . . . . . . 5 65 1.4. Conventions Used in This Document . . . . . . . . . . . . 6 66 2. Payload Format Enhanced Processing . . . . . . . . . . . . . . 7 67 2.1. Enhanced Processing Markers . . . . . . . . . . . . . . . 7 68 3. Priority Mapping Table . . . . . . . . . . . . . . . . . . . . 9 69 3.1. Pre-Defined Priority Mapping . . . . . . . . . . . . . . . 9 70 3.1.1. Packet Number Based Ordering . . . . . . . . . . . . . 9 71 3.1.2. Progression Based Ordering . . . . . . . . . . . . . . 9 72 3.1.3. Layer Based Ordering . . . . . . . . . . . . . . . . . 10 73 3.1.4. Resolution Based Ordering . . . . . . . . . . . . . . 10 74 3.1.5. Component Based Ordering . . . . . . . . . . . . . . . 11 75 4. JPEG 2000 Main Header Compensation Scheme . . . . . . . . . . 12 76 4.1. Sender Processing . . . . . . . . . . . . . . . . . . . . 12 77 4.2. Receiver Processing . . . . . . . . . . . . . . . . . . . 12 78 5. Security Consideration . . . . . . . . . . . . . . . . . . . . 14 79 6. Congestion Control . . . . . . . . . . . . . . . . . . . . . . 15 80 7. IANA Consideration . . . . . . . . . . . . . . . . . . . . . . 16 81 7.1. Media Type Registration . . . . . . . . . . . . . . . . . 16 82 7.2. SDP Parameters . . . . . . . . . . . . . . . . . . . . . . 19 83 8. Usage with the SDP Offer/Answer Model . . . . . . . . . . . . 20 84 8.1. Examples . . . . . . . . . . . . . . . . . . . . . . . . . 20 85 8.1.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . 20 86 8.1.2. Example 2 . . . . . . . . . . . . . . . . . . . . . . 21 87 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 23 88 9.1. Normative References . . . . . . . . . . . . . . . . . . . 23 89 9.2. Informative References . . . . . . . . . . . . . . . . . . 23 90 Appendix A. Sample Headers in Detail . . . . . . . . . . . . . . 24 91 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 32 92 Intellectual Property and Copyright Statements . . . . . . . . . . 33 94 1. Introduction 96 This document is an extension of: "RTP Payload Format for JPEG 2000 97 Video Streams"[1]. These are additional mechanisms that can be used 98 with certain parts of the header in [1] to support JPEG 2000 features 99 such as scalability and a main header compensation method. These 100 mechanisms are described in detail in this document. 102 1.1. History 104 In the development of RFC XXXY [1], there was an issue of IPR claims 105 on certain mechanisms with main header compensation, priority table 106 usage, etc. in RFC XXXY [1]. As these are not "essential" to the 107 core RTP format of RFC XXXY [1] and only describes a mechanism, it 108 was decided that splitting these mechanisms from the core JPEG 2000 109 RTP format in to a separate document. This is the document 110 describing the IPR related mechanisms for main header recover and 111 priority table usage. 113 1.2. Description of the Mechanisms 115 1.2.1. Main Header Compensation 117 JPEG 2000's scalable coding scheme allows for decompressing truncated 118 or partial data streams but only when the main header is present. If 119 the header is lost, the data is useless. With JPEG 2000 video 120 coding, coding parameters between frames will rarely change and 121 previous headers may be used in newly received data which the header 122 have been lost. 124 Compensation of the main header that has been lost is very simple 125 with this procedure. In the case of JPEG 2000 video, it is very 126 common that encode parameters will not vary greatly between 127 successive frames. Even if the RTP packet including the main header 128 of a frame has been dropped, decoding may be performed by using the 129 main header of a prior frame. 131 1.2.2. Priority Table 133 JPEG 2000 codestream has rich functionality built into it so decoders 134 can easily handle scalable delivery or progressive transmission. 135 Progressive transmission allows images to be reconstructed with 136 increasing pixel accuracy or spatial resolution. This feature allows 137 the reconstruction of images with different resolutions and pixel 138 accuracy, for different target devices. A single image source can 139 provide a codestream that is easily processed for smaller image 140 display devices. 142 JPEG 2000 packets contain all compressed image data from a specific: 143 layer, component, resolution level, and/or precinct. The order in 144 which these JPEG 2000 packets are found in the codestream is called: 145 progression order. The ordering of the JPEG 2000 packets can 146 progress along four axes: layer, component, resolution and precinct 147 (or position). 149 Providing a priority field to indicate the importance of data 150 contained in a given RTP packet can aid in usage of JPEG 2000 151 progressive and scalable functions. 153 1.3. Motivations for Priority Field coding 155 JPEG 2000 coding scheme allows one to reorder the codestream in many 156 ways. Even when the coding scheme is determined and arranged by the 157 encoder, a decoder can still re-arrange the code stream on the fly to 158 suit decode parameters such as: re-arranging from resolution 159 progressive to quality progressive. 161 Using the priority field coding, the decoder gains insight into the 162 codestream without access to the full codestream and exposes features 163 of JPEG 2000 to a higher level. 165 A few of the scenarios are presented below the authors have thought 166 of to utilize this field. The priority field allows more information 167 about the image to be sent without more signaling between sender and 168 receivers to leverage JPEG 2000 capabilities. 170 1.3.1. Scenario: Just enough resolution 172 The scenario is when rapid scene access is more important than higher 173 quality. By using the priority field, the receiver can decode for 174 its own quality level. If the sender cannot determine the receiver's 175 resolution, the receiver can select which parts of the codestream to 176 decode/load by using the priority field. 178 1.3.2. Scenario: Multiple clients, single source 180 In a multicast environment, there are clients with better visual 181 capability than others (i.e. TV conference vs. Mobile). The 182 respective clients can use the priority field to determine which 183 packets are vital for their own visual presentation. The sender will 184 have to do work on the priority field to optimally serve all the 185 clients while only managing a single visual stream. 187 1.4. Conventions Used in This Document 189 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 190 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 191 document are to be interpreted as described in RFC2119. [2]. 193 RFC-Editor Note: The RFC Editor is requested to replace all 194 occurences of RFC XXXY with the RFC number 195 draft-ietf-avt-rtp-jpeg2000 receives. At that time, please remove 196 this note. 198 2. Payload Format Enhanced Processing 200 2.1. Enhanced Processing Markers 202 This section of the document describes additional usage in the values 203 of mh_id and priority fields and interpretation which differ from RFC 204 XXXY [1]. Implementions of this document should follow RFC XXXY [1] 205 first then add additional header processing as described in this 206 document. Implementations following this document are expected to 207 interoperate with implementations of [1] and this document as well. 209 The RTP payload header format for JPEG 2000 video stream is as 210 follows: 212 0 1 2 3 213 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 214 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 215 |tp |MHF|mh_id|T| priority | tile number | 216 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 217 |reserved | fragment offset | 218 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 220 Figure 1: RTP payload header format for JPEG 2000 222 mh_id (Main Header Identification) : 3 bits 224 Main header identification value. This is used for JPEG 2000 main 225 header recovery. 227 The initial value of mh_id is random, and may take any value 228 between 1-7, but MUST NOT be 0. 230 The same mh_id value is used as long as the coding parameters 231 described in the main header remains unchanged between frames. 233 The mh_id value MUST be incremented by 1 every time a new main 234 header is transmitted. Once the mh_id value becomes greater than 235 7, it SHOULD roll over to 1. 237 When mh_id is 0, it has special usage for the receiver. This 238 special usage is described in Section 4.2 of this document. 240 Senders should follow Section 4.1 of this document for proper 241 mh_id assignment and usage. 243 priority : 8 bits 245 The priority field indicates the importance of the JPEG 2000 246 packet included in the payload. Typically, a higher priority is 247 set in the packets containing JPEG 2000 packets containing the 248 lower sub-bands. 250 Special values of priority: 252 0: This is reserved for payload which contain a header (main or 253 tile part header.) This is considered the most important. 255 1 to 255: These values decrease in importance as the values 256 increase. (i.e. 1 is more important than 2, etc.) Applying 257 priority values should correlate directly to JPEG 2000 258 codestream in importance. 260 The lower the priority value is the higher the importance. A 261 priority value of 0 is the highest importance and 255 is the 262 lowest importance. We define the priority value 0 as a special 263 priority value for the headers (the main header or tile-part 264 header). If any headers (the main header or tile-part header) are 265 packed into the RTP payload, the sender MUST set the priority 266 value to 0. 268 Assignment of the values are described in Section 3 with pre- 269 defined table assignments in Section 3.1. 271 3. Priority Mapping Table 273 For the progression order, the priority value for each JPEG 2000 274 packet is given by the priority mapping table. 276 3.1. Pre-Defined Priority Mapping 278 This document specify several commonly-used priority mapping tables, 279 pre-defined priority mapping tables: packet number based (default), 280 progression-based, layer-based, resolution-based, position-based, and 281 component-based. 283 Packet number priority mapping is REQUIRED to be supported by clients 284 implementing this specification. Other priority mapping tables 285 (progression, layer, resolution, and component based) are OPTIONAL to 286 implementations of this specification. 288 Rules that all implementations of this specification MUST follow in 289 all priority modes: 291 o When there is a header in the packet with a JPEG 2000 packet, the 292 sender MUST set the payload packet priority value to 0. 294 o When there are multiple JPEG 2000 packets in the same RTP payload 295 packet, the sender MUST set the payload packet priority value to 296 the lowest JPEG 2000 packet. (i.e. if JPEG 2000 packets with 297 priority: 5,6,7 are packed into a single payload, the priority 298 value will be 5.) 300 3.1.1. Packet Number Based Ordering 302 Packet number based ordering assigns the payload packet priority 303 value from the "JPEG 2000 packet value". (note: JPEG 2000 codestreams 304 are stored in units of packets and each packet has a value .) This 305 method is the default method for assigning priority value. All 306 implementations of this specification MUST support this method. 308 If the JPEG 2000 codestream packet value is greater than 255, the 309 sender MUST set the payload priority value to 255. 311 3.1.2. Progression Based Ordering 313 The sender will assign the payload packet priority value only based 314 on layer, resolution, and component ordering of the codestream. 316 This is similar to the packet number based assignment but will not 317 take into account the precinct number or position in the JPEG 2000 318 codestream. 320 For example: 322 If the codestream is ordered in LRCP (Layer, Resolution, Component, 323 Position) 325 All the packets in: 327 layer.........0 328 resolution....0 329 component.....0 331 then the packet priority value : 1 333 All the packets in: 335 layer.........0 336 resolution....0 337 component.....1 339 then the packet priority value : 2 341 All the packets in: 343 layer.........0 344 resolution....0 345 component.....2 347 then the packet priority value : 3 349 3.1.3. Layer Based Ordering 351 Layer-based priority mapping table simplifies the default mapping to 352 just matching JPEG 2000 packets together from the same layer. 354 For example: 356 All the packets in layer 0 : packet priority value : 1 357 All the packets in layer 1 : packet priority value : 2 358 All the packets in layer 2 : packet priority value : 3 359 ... 360 All the packets in layer n : packet priority value : n+1 361 All the packets in layer 255 : packet priority value : 255 363 3.1.4. Resolution Based Ordering 365 Resolution-based priority mapping table is similar to the layer based 366 order but for JPEG 2000 packets of the same resolution 367 For example: 369 All the packets in resolution 0 : packet priority value : 1 370 All the packets in resolution 1 : packet priority value : 2 371 All the packets in resolution 2 : packet priority value : 3 372 ... 373 All the packets in resolution n : packet priority value : n+1 374 All the packets in resolution 255 : packet priority value : 255 376 3.1.5. Component Based Ordering 378 Component-based priority mapping table is mapping together JPEG 2000 379 components of the same component 381 For example: 383 All the packets in component 0 : packet priority value : 1 384 All the packets in component 1 : packet priority value : 2 385 All the packets in component 2 : packet priority value : 3 386 ... 387 All the packets in component n : packet priority value : n+1 388 All the packets in component 255 : packet priority value : 255 390 4. JPEG 2000 Main Header Compensation Scheme 392 The mh_id field of the payload header is used to indicate whether the 393 encoding parameters of the main header are the same as the encoding 394 parameters of the previous frame. The same value is set in mh_id of 395 the RTP packet in the same frame. The mh_id and encode parameters 396 are not associated with each other as 1:1 but they are used to 397 indicate whether the encode parameters of the previous frame are the 398 same or not in the event of a lost header. 400 The mh_id field value SHOULD be saved from previous frames to be used 401 to recover the current frame's main header. If the mh_id of the 402 current frame has the same value as the mh_id value of the previous 403 frame, the previous frame's main header MAY be used to decode the 404 current frame, in case of a lost header in the current frame. 406 The sender MUST increment mh_id when parameters in the header change 407 and send a new main header accordingly. 409 The receiver MAY use the mh_id and MAY retain the header for such 410 compensation. 412 4.1. Sender Processing 414 The sender MUST transmit RTP packets with the same mh_id value if the 415 encoder parameters of the current frame are the same as the previous 416 frame. The encoding parameters are the fixed information marker 417 segment (SIZ marker) and functional marker segments (COD, COC, RGN, 418 QCD, QCC, and POC) specified in JPEG 2000 Part 1 Annex A [3]. 420 An initial value of mh_id MUST be selected randomly between 1 and 7 421 for security reasons. 423 If the encode parameters changes, the sender transmitting RTP packets 424 MUST increment the mh_id value by one, but when mh_id value becomes 425 greater than 7, a sender MUST set mh_id value back to 1. 427 4.2. Receiver Processing 429 When the receiver receives the main header completely, the RTP 430 sequence number, the mh_id and main header should be saved. Only the 431 last main header that was received completely SHOULD be saved. When 432 the mh_id value is 0, the receiver SHOULD NOT save the header. 434 When the main header is not received, the receiver may compare the 435 current payload header's mh_id value with the previous saved mh_id 436 value. If the values match, decoding may be performed by using the 437 previously saved main header. 439 If the mh_id field is set to 0, the receiver MUST NOT save the main 440 header and MUST NOT compensate for lost headers. 442 If the mh_id value changes, receivers SHOULD save the current header 443 and save the new mh_id value. The old saved header should be deleted 444 from storage. 446 5. Security Consideration 448 Please refer to section 6 of RFC XXXY [1] for Security Considerations 449 regarding this RTP format. 451 6. Congestion Control 453 Please refer to section 7 of RFC XXXY [1] for Congestion Control 454 regarding this RTP format. 456 7. IANA Consideration 458 7.1. Media Type Registration 460 This document extends the associated media type from RFC XXXY[1]: 461 Here is the complete original for reference. 463 This registration uses the template defined in [7] and follows [8]. 465 Type name: video 467 Subtype name: jpeg2000 469 Required parameters: 471 sampling: A list of values specifying the color space of the 472 payload data. 474 Acceptable values: 476 RGB: standard Red, Green, Blue color space. 478 BGR: standard Blue, Green, Red color space. 480 RGBA: standard Red, Green, Blue, Alpha color space. 482 BGRA: standard Blue, Green, Red, Alpha color space. 484 YCbCr-4:4:4: standard YCbCr color space, no subsampling. 486 YCbCr-4:2:2: standard YCbCr color space, Cb and Cr are 487 subsampled horizontally by 1/2. 489 YCbCr-4:2:0: standard YCbCr color space, Cb and Cr are 490 subsampled horizontally and vertically by 1/2. 492 YCbCr-4:1:1: standard YCbCr color space, Cb and Cr are 493 subsampled vertically by 1/4 495 GRAYSCALE: basically a single component image of just 496 multilevels of grey. 498 EXTENSION VALUE: Additional color samplings can be registered 499 with and current listing of registered color samplings at: 500 Color Sampling Registration Authority. Please refer to RTP 501 Format for Uncompressed Video. [9] 503 Optional parameters: 505 interlace: interlace scanning. If payload is in interlace 506 format, the acceptable value is "1", otherwise, the value 507 should be "0". Each complete image forms vertically half the 508 display. tp value MUST properly specify the field the image 509 represents odd(tp=1), or even(tp=2). If this option is not 510 present, the payload MUST be in progressive format and tp MUST 511 be set to 0. 513 width: A parameter describing the maximum width of the video 514 stream. This parameter MUST appear when height is present. 515 Acceptable values: - an integer value between 0 - 516 4,294,967,295. 518 height: A parameter describing the maximum height of the video 519 stream. This parameter MUST appear when width is present. 520 Acceptable values: - an integer value between 0 - 521 4,294,967,295. 523 The receiver MUST ignore any unspecified parameters outside of this 524 list and in [1] . 526 Additional parameters for this extension: 528 mhc : Main Header Compensation. this option is used when sender 529 and/or receiver is utilizing the Main Header compensation 530 technique as specified in this document. Acceptable values 531 when using the Main Header compensation technique is "1", 532 otherwise, it should be "0". 534 This is a list of options to be included when the sender or 535 receiver is utilizing the Priority Table(s) as specified in 536 this document. 538 pt : Priority Table. this option is followed by a comma-separated 539 list of predefined priority table definitions to be used by 540 sender or receiver. 542 The option appearing front most in the option line is the most 543 important and next ones are of decreasing importance. 545 Acceptable values: 547 progression : this table follows the progression ordering 548 of the codestream. 550 layer : this table follows the layer ordering of the 551 codestream. 553 resolution : this table follows the resolution ordering of 554 the codestream. 556 component : this table follows the component ordering of 557 the codestream. 559 default : this table follows the ordering of the 560 codestream. 562 Encoding considerations: 564 This media type is framed and binary, see Section 4.8 in [7] 566 Security considerations: 568 see security considerations section Section 5 of this document. 570 Interoperability considerations: 572 JPEG 2000 video stream is a sequence of JPEG 2000 still images. 573 An implementation in compliant with [3] can decode and attempt to 574 display the encoded JPEG 2000 video stream. 576 Published specification: ISO/IEC 15444-1 | ITU-T Rec. T.800 578 Applications which use this media type: 580 video streaming and communication 582 Person and email address to contact for further information: 584 Eisaburo Itakura, Satoshi Futemma, Andrew Leung 585 Email: {itakura|satosi-f} @ sm . sony . co . jp, andrew @ ualberta 586 . net 588 Intended usage: Restriction 590 Restrictions on Usage: 592 This media type depends on RTP framing, and hence is only 593 defined for the transfer via RTP [4]. Transport within other 594 framing protocols is not defined at the time. 596 Author/Change Controller: 598 Author: 600 Eisaburo Itakura, Satoshi Futemma, Andrew Leung 601 Email: {itakura|satosi-f} @ sm . sony . co . jp, andrew @ 602 ualberta . net 604 Change controller: 606 IETF Audio/Video Transport Working Group delegated from the 607 IESG 609 7.2. SDP Parameters 611 In addition to SDP Parameters section in [1]: 613 The media type video/jpeg2000 string is mapped to fields in the 614 Session Description Protocol (SDP) [5] as follows: 616 o The media name in the "m=" line of SDP MUST be video. 618 o The encoding name in the "a=rtpmap" line of SDP MUST be jpeg2000 619 (the MIME subtype). 621 o The clock rate in the "a=rtpmap" line MUST be 90000. 623 o The OPTIONAL parameters "mhc" or "pt" MUST be included in the 624 "a=fmtp" line of SDP. 626 These parameters are expressed as a media type string, in the form of 627 a semicolon separated list of parameter=value pairs. 629 Therefore, an example of media representation in SDP is as follows: 631 m=video 49170/2 RTP/AVP 98 632 a=rtpmap:98 jpeg2000/90000 633 a=fmtp:98 mhc; pt=default; sampling=YCbCr- 634 4:2:0;width=128;height=128 636 8. Usage with the SDP Offer/Answer Model 638 In addition to SDP Offer/Answer section in RFC XXXY [1]: 640 When offering JPEG 2000 over RTP using SDP in an Offer/Answer model 641 [6], the following rules and limitations apply: 643 o All parameters MUST have an acceptable value for that parameter. 645 o All parameters MUST correspond to the parameters of the payload. 647 o The parameters "mhc" or "pt" MUST appear in the offer and answer. 648 If the parameter "mhc" or "pt" is not in the answer, senders 649 should not process the header according to this document. 651 o For the "pt" option: 653 * Senders should send a complete list indicating which option are 654 available to the receiver. The receiver should answer with 655 their preference from the offer list. 657 o In a multicast environment: 659 * Senders should send out one option for priority-table- 660 definition for everyone in the group. 662 * If a single client in the group do not support the extensions 663 outlined in this document, senders SHOULD NOT use additional 664 techniques outlined in this document. 666 This is highly recommended for multicast streams where not all 667 receivers are of the same type. 669 8.1. Examples 671 Offer/Answer example exchanges are provided. 673 8.1.1. Example 1 675 Alice offers Main Header Compensation functionality, YCbCr 422 color 676 space, interlace image with 720-pixel width and 480-pixel height and 677 several priority-table options (default, progression, layer, 678 resolution, component) as below: 680 v=0 681 o=alice 2890844526 2890844526 IN IP4 host.exampl 682 s= 683 c=IN IP4 host.exampl 684 t=0 0 685 m=video 49170 RTP/AVP 98 686 a=rtpmap:98 jpeg2000/90000 687 a=fmtp:98 mhc=1;sampling= YCbCr-4:2:2;interlace=1 688 a=fmtp:98 pt=default, progression,layer, resolution, component; 689 width=720; height=480 691 Bob accepts Main Header Compensation functionality, YCbCr-4:2:2 color 692 space, interlace image, default mapping table and replies: 694 v=0 695 o=bob 2890844730 2890844731 IN IP4 host.example 696 s= 697 c=IN IP4 host.example 698 t=0 0 699 m=video 49920 RTP/AVP 98 700 a=rtpmap:98 jpeg2000/90000 701 a=fmtp:98 mhc=1;sampling= YCbCr-4:2:2;interlace=1 702 a=fmtp:98 mhc=1; pt=default; width=720;height=480 704 8.1.2. Example 2 706 Alice offers Main Header Compensation, YCbCr 420 color space, 707 progressive image with 320-pixel width and 240-pixel height and layer 708 priority-table options as below: 710 v=0 711 o=alice 2890844526 2890844526 IN IP4 host.example 712 s= 713 c=IN IP4 host.example 714 t=0 0 715 m=video 49170 RTP/AVP 98 716 a=rtpmap:98 jpeg2000/90000 717 a=fmtp:98 mhc=1;sampling= YCbCr-4:2:0 718 a=fmtp:98 pt=layer; width=320; height=240 720 Bob does not accept Main Header Compensation functionality but 721 accepts YCbCr-4:2:0 color space,layer based priority mapping and 722 replies: 724 v=0 725 o=bob 2890844730 2890844731 IN IP4 host.example 726 s= 727 c=IN IP4 host.example 728 t=0 0 729 m=video 49920 RTP/AVP 98 730 a=rtpmap:98 jpeg2000/90000 731 a=fmtp:98 mhc=1;sampling= YCbCr-4:2:0 732 a=fmtp:98 mhc=0; 733 a=fmtp:98 pt=layer; width=320; height=240 735 9. References 737 9.1. Normative References 739 [1] Futemma, "RTP Payload Format for JPEG 2000 Video Streams", 740 RFC XXXY, April 2007. 742 [2] Bradner, "Key words for use in RFCs to Indicate Requirement 743 Levels", RFC 2119, March 1997. 745 [3] ISO/IEC JTC1/SC29, ISO/IEC 15444-1 | ITU-T Rec. T.800, 746 "Information Technology - JPEG 2000 Image Coding System - Part 747 1: Core Coding System", December 2000. 749 [4] Schulzrinne, Casner, Frederick, and Jacobson, "RTP: A Transport 750 Protocol for Real Time Applications", RFC 3550, STD 64, 751 July 2003. 753 [5] Handley and Jacobson, "SDP: Session Description Protocol", 754 RFC 2327, April 1998. 756 [6] Rosenberg and Schulzrinne, "An Offer/Answer Model with Session 757 Description Protocol (SDP)", RFC 3264, June 2002. 759 [7] Freed and Klensin, "Media Type Specifications and Registration 760 Procedures", RFC 4288, December 2005. 762 [8] Casner and Hoschka, "MIME Type Registration of RTP Payload 763 Formats", RFC 3555, July 2003. 765 9.2. Informative References 767 [9] Perkins and Gharai, "RTP Payload Format for Uncompressed Video", 768 RFC 2246, September 2005. 770 Appendix A. Sample Headers in Detail 772 0 1 2 3 773 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 774 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 775 |tp |MHF|mh_id|T| priority | tile number | 776 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 777 |reserved | fragment offset | 778 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 780 Figure 2 782 First Packet: This packet will have the whole main header. 210 bytes 784 0 1 2 3 785 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 786 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 787 |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| 788 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 789 |0 0 0 0 0 0 0 0|0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0| 790 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 791 |FF4FFF51002F000 .... | 792 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 794 Figure 3 796 Second Packet: This packet will have a tile header and the first tile 797 part LLband 1500 bytes 799 0 1 2 3 800 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 801 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 802 |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| 803 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 804 |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| 805 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 806 |FF90 000A 0000 0000 2DB3 0001 FF93 | 807 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 809 Figure 4 811 Third Packet: This packet will have the next part in the tile, no 812 tile header 1500 bytes 814 0 1 2 3 815 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 816 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 817 |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| 818 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 819 |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| 820 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 821 |E841 4526 4556 9850 C2EA .... | 822 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 824 Figure 5 826 Fourth Packet: Last packet for the image 290 bytes 828 0 1 2 3 829 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 830 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 831 |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| 832 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 833 |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| 834 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 835 |A55D 8B73 3B25 25C7 B9EB .... 2FBEB153| 836 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 838 Figure 6 840 First Packet: This packet will have the whole main header. 210 bytes 842 0 1 2 3 843 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 844 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 845 |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| 846 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 847 |0 0 0 0 0 0 0 0|0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0| 848 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 849 |FF4FFF51002F000 .... | 850 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 852 Figure 7 854 Second Packet: This packet will have a first tile part (tile 0) 1400 855 bytes 857 0 1 2 3 858 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 859 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 860 |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| 861 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 862 |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| 863 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 864 |FF90 000A 0000 0000 0578 0001 FF93 .... | 865 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 867 Figure 8 869 Third Packet: This packet will have a second tile part (tile 1) 1423 870 bytes 872 0 1 2 3 873 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 874 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 875 |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| 876 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 877 |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| 878 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 879 |FF90 000A 0001 0000 058F 0001 FF93 .... | 880 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 882 Figure 9 884 Fourth Packet: This packet will have a third tile part (tile 2) 1355 885 bytes 887 0 1 2 3 888 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 889 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 890 |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| 891 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 892 |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| 893 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 894 |FF90 000A 0002 0000 054B 0001 FF93 .... | 895 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 897 Figure 10 899 Fifth Packet: This packet will have a fourth tile part (tile 3) 1290 900 bytes 902 0 1 2 3 903 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 904 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 905 |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| 906 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 907 |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| 908 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 909 |FF90 000A 0003 0000 050A 0001 FF93 .... | 910 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 912 Figure 11 914 First Packet: This packet will have the first part of the main 915 header. 110 bytes 917 0 1 2 3 918 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 919 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 920 |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| 921 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 922 |0 0 0 0 0 0 0 0|0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0| 923 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 924 |FF4FFF51002F000 .... | 925 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 927 Figure 12 929 Second Packet: This packet has the second part of the header. 1400 930 bytes 932 0 1 2 3 933 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 934 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 935 |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| 936 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 937 |0 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| 938 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 939 |FF6400FF .... | 940 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 942 Figure 13 944 Third Packet: This packet has two tiles, tile 0 and tile 1 1400 bytes 946 0 1 2 3 947 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 948 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 949 |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| 950 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 951 |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| 952 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 953 |FF90 000A 0000 0000 02BC 0001 FF93 ... | 954 |FF90 000A 0001 0000 02BC 0001 FF93 ... | 955 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 957 Figure 14 959 Fourth Packet: This packet has one tile, tile 2 1395 bytes 961 0 1 2 3 962 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 963 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 964 |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| 965 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 966 |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| 967 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 968 |FF90 000A 0002 0000 0573 0001 FF93 .... | 969 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 971 Figure 15 973 First packet: This packet will have the whole main header for the odd 974 field 210 bytes 976 0 1 2 3 977 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 978 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 979 |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| 980 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 981 |0 0 0 0 0 0 0 0|0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0| 982 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 983 |FF4FFF51002F000 .... | 984 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 986 Figure 16 988 Second packet: This packet will have the first part of the odd 989 field's tile 1400 bytes 991 0 1 2 3 992 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 993 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 994 |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| 995 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 996 |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| 997 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 998 |FF90 000A 0000 0000 0578 0001 FF93 .... | 999 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1001 Figure 17 1003 Third packet: This packet will have the second part of the odd 1004 field's tile 1400 bytes 1006 0 1 2 3 1007 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 1008 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1009 |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| 1010 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1011 |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| 1012 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1013 |7F04 E708 27D9 D11D 22CB ... | 1014 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1016 Figure 18 1018 Fourth packet: This packet will have the third part of the odd 1019 field's tile 1300 bytes 1021 0 1 2 3 1022 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 1023 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1024 |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| 1025 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1026 |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| 1027 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1028 |98BD EC9B 2826 DC62 D4AB ... | 1029 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1031 Figure 19 1033 Fifth packet: This packet will have the whole main header for the 1034 even field 1036 0 1 2 3 1037 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 1038 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1039 |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| 1040 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1041 |0 0 0 0 0 0 0 0|0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0| 1042 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1043 |FF4FFF51002F000 .... | 1044 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1046 Figure 20 1048 Sixth packet: This packet will have the first part of the odd field's 1049 tile 1400 bytes 1051 0 1 2 3 1052 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 1053 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1054 |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| 1055 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1056 |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| 1057 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1058 |FF90 000A 0000 0000 0578 0001 FF93 .... | 1059 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1061 Figure 21 1063 Seventh packet: This packet will have the second part of the odd 1064 field's tile 1400 bytes 1066 0 1 2 3 1067 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 1068 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1069 |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| 1070 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1071 |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| 1072 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1073 |626C 42F0 166B 6BD0 F8E1 ... | 1074 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1076 Figure 22 1078 Eighth packet: This packet will have the third part of the odd 1079 field's tile 1300 bytes 1081 0 1 2 3 1082 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 1083 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1084 |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| 1085 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1086 |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| 1087 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1088 |8114 41D5 18AB 4A1B ... | 1089 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1091 Figure 23 1093 Authors' Addresses 1095 Andrew Leung 1096 Sony Corporation 1097 1-7-1 Konan 1098 Minato-ku 1099 Tokyo 108-0075 1100 Japan 1102 Phone: +81 3 6748-2111 1103 Email: andrew @ ualberta . net 1104 URI: http://www.sony.net/ 1106 Satoshi Futemma 1107 Sony Corporation 1108 1-7-1 Konan 1109 Minato-ku 1110 Tokyo 108-0075 1111 Japan 1113 Phone: +81 3 6748-2111 1114 Email: satosi-f @ sm . sony . co . jp 1115 URI: http://www.sony.net/ 1117 Eisaburo Itakura 1118 Sony Corporation 1119 1-7-1 Konan 1120 Minato-ku 1121 Tokyo 108-0075 1122 Japan 1124 Phone: +81 3 6748-2111 1125 Email: itakura @ sm . sony . co . jp 1126 URI: http://www.sony.net/ 1128 Full Copyright Statement 1130 Copyright (C) The IETF Trust (2007). 1132 This document is subject to the rights, licenses and restrictions 1133 contained in BCP 78, and except as set forth therein, the authors 1134 retain all their rights. 1136 This document and the information contained herein are provided on an 1137 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 1138 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 1139 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 1140 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 1141 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 1142 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1144 Intellectual Property 1146 The IETF takes no position regarding the validity or scope of any 1147 Intellectual Property Rights or other rights that might be claimed to 1148 pertain to the implementation or use of the technology described in 1149 this document or the extent to which any license under such rights 1150 might or might not be available; nor does it represent that it has 1151 made any independent effort to identify any such rights. Information 1152 on the procedures with respect to rights in RFC documents can be 1153 found in BCP 78 and BCP 79. 1155 Copies of IPR disclosures made to the IETF Secretariat and any 1156 assurances of licenses to be made available, or the result of an 1157 attempt made to obtain a general license or permission for the use of 1158 such proprietary rights by implementers or users of this 1159 specification can be obtained from the IETF on-line IPR repository at 1160 http://www.ietf.org/ipr. 1162 The IETF invites any interested party to bring to its attention any 1163 copyrights, patents or patent applications, or other proprietary 1164 rights that may cover technology that may be required to implement 1165 this standard. Please address the information to the IETF at 1166 ietf-ipr@ietf.org. 1168 Acknowledgment 1170 Funding for the RFC Editor function is provided by the IETF 1171 Administrative Support Activity (IASA).