idnits 2.17.1 draft-ietf-avt-rtp-jpeg2000-beam-10.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 1083. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 1094. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 1101. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 1107. 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 (Apr 24, 2008) is 5817 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' Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 9 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 26, 2008 Sony 6 Apr 24, 2008 8 Payload Format for JPEG 2000 Video: Extensions for Scalability and Main 9 Header Recovery 10 draft-ietf-avt-rtp-jpeg2000-beam-10 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 26, 2008. 37 Copyright Notice 39 Copyright (C) The IETF Trust (2008). 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 main header recovery. 47 This memo must be accompanied with a complete implementation of "RTP 48 Payload Format for JPEG 2000 Video Streams." That document is a 49 complete description of the payload header and signaling, this 50 document only describes additional processing for the payload header. 51 There is an additional media type and SDP marker signaling for 52 implementations of this document. 54 Table of Contents 56 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 57 1.1. Description of the Mechanisms . . . . . . . . . . . . . . 4 58 1.1.1. Main Header Compensation . . . . . . . . . . . . . . . 4 59 1.1.2. Priority Table . . . . . . . . . . . . . . . . . . . . 4 60 1.2. Motivations for Priority Field coding . . . . . . . . . . 5 61 1.2.1. Scenario: Just enough resolution . . . . . . . . . . . 5 62 1.2.2. Scenario: Multiple clients, single source . . . . . . 5 63 1.3. Conventions Used in This Document . . . . . . . . . . . . 5 64 2. Payload Format Enhanced Processing . . . . . . . . . . . . . . 6 65 2.1. Enhanced Processing Markers . . . . . . . . . . . . . . . 6 66 3. Priority Mapping Table . . . . . . . . . . . . . . . . . . . . 8 67 3.1. Packet Number Based Ordering . . . . . . . . . . . . . . . 8 68 3.2. Progression Based Ordering . . . . . . . . . . . . . . . . 8 69 3.3. Layer Based Ordering . . . . . . . . . . . . . . . . . . . 10 70 3.4. Resolution Based Ordering . . . . . . . . . . . . . . . . 10 71 3.5. Component Based Ordering . . . . . . . . . . . . . . . . . 10 72 4. JPEG 2000 Main Header Compensation Scheme . . . . . . . . . . 12 73 4.1. Sender Processing . . . . . . . . . . . . . . . . . . . . 12 74 4.2. Receiver Processing . . . . . . . . . . . . . . . . . . . 12 75 5. Media Type Registration . . . . . . . . . . . . . . . . . . . 14 76 6. SDP Parameters . . . . . . . . . . . . . . . . . . . . . . . . 15 77 6.1. Mapping of the optional parameters to SDP . . . . . . . . 15 78 6.2. Usage with the SDP Offer/Answer Model . . . . . . . . . . 15 79 6.2.1. Examples . . . . . . . . . . . . . . . . . . . . . . . 16 80 7. IANA Consideration . . . . . . . . . . . . . . . . . . . . . . 19 81 8. Security Consideration . . . . . . . . . . . . . . . . . . . . 20 82 9. Congestion Control . . . . . . . . . . . . . . . . . . . . . . 21 83 10. Normative References . . . . . . . . . . . . . . . . . . . . . 22 84 Appendix A. Sample Headers in Detail . . . . . . . . . . . . . . 23 85 A.1. Sample 1: Progressive image with single tile, 3500 86 bytes (i.e. thumbnail) . . . . . . . . . . . . . . . . . . 23 87 A.2. Smaple 2: Image with 4 tiles . . . . . . . . . . . . . . . 25 88 A.3. Sample 3: Packing multiple tiles in single payload, 89 fragmented header. No header compensation, progressive 90 image . . . . . . . . . . . . . . . . . . . . . . . . . . 26 91 A.4. Sample 4: Interlace image, single tile . . . . . . . . . . 28 92 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 32 93 Intellectual Property and Copyright Statements . . . . . . . . . . 33 95 1. Introduction 97 This document is an extension of: "RTP Payload Format for JPEG 2000 98 Video Streams" [1]. These are additional mechanisms which can be 99 used with certain parts of the header in [1] to support JPEG 2000 100 features such as: scalability and a main header compensation method. 101 These mechanisms are described in detail in this document. 103 These are optional extensions to RFC XXXY [1].which one may use to 104 make better use of JPEG 2000 features. These extensions are not 105 required for any implementations of RFC XXXY[1]. 107 1.1. Description of the Mechanisms 109 1.1.1. Main Header Compensation 111 JPEG 2000 has a scalable coding scheme which allows for decompressing 112 truncated or partial data streams but only when the main header is 113 present. If the header is lost, the data is useless. With JPEG 2000 114 video coding, coding parameters between frames will rarely change and 115 previous headers may be used in newly received data which the header 116 have been lost. 118 Compensation of the main header that has been lost is very simple 119 with this procedure. In the case of JPEG 2000 video, it is very 120 common that encode parameters will not vary greatly between 121 successive frames. Even if the RTP packet including the main header 122 of a frame has been dropped, decoding may be performed by using the 123 main header of a prior frame. 125 1.1.2. Priority Table 127 JPEG 2000 codestream has rich functionality built into it so decoders 128 can easily handle scalable delivery or progressive transmission. 129 Progressive transmission allows images to be reconstructed with 130 increasing pixel accuracy or spatial resolution. This feature allows 131 the reconstruction of images with different resolutions and pixel 132 accuracy, for different target devices. A single image source can 133 provide a codestream that is easily processed for smaller image 134 display devices. 136 JPEG 2000 packets contain all compressed image data from a specific: 137 layer, component, resolution level, and/or precinct. The order in 138 which these JPEG 2000 packets are found in the codestream is called: 139 the progression order. The ordering of the JPEG 2000 packets can 140 progress along four axes: layer, component, resolution and precinct 141 (or position). 143 Providing a priority field to indicate the importance of data 144 contained in a given RTP packet can aid in usage of JPEG 2000 145 progressive and scalable functions. 147 1.2. Motivations for Priority Field coding 149 JPEG 2000 coding scheme allows one to reorder the codestream in many 150 ways. Even when the coding scheme is determined and arranged by the 151 encoder, a decoder can still re-arrange the code stream on the fly to 152 suit decode parameters such as: re-arranging from resolution 153 progressive to quality progressive. 155 Using the priority field coding, the decoder gains insight into the 156 codestream without access to the full codestream and exposes features 157 of JPEG 2000 to a higher level. 159 A few of the scenarios are presented below the authors have thought 160 of to utilize this field. The priority field allows more information 161 about the image to be sent without more signaling between sender and 162 receivers to leverage JPEG 2000 capabilities. 164 1.2.1. Scenario: Just enough resolution 166 The scenario is when rapid scene access is more important than higher 167 quality. By using the priority field, the receiver can decode for 168 its own quality level. If the sender cannot determine the receiver's 169 resolution, the receiver can select which parts of the codestream to 170 decode/load by using the priority field. 172 1.2.2. Scenario: Multiple clients, single source 174 In a multicast environment, there are clients with better visual 175 capability than others (i.e. TV conference vs. Mobile). The 176 respective clients can use the priority field to determine which 177 packets are vital for their own visual presentation. The sender will 178 have to do work on the priority field to optimally serve all the 179 clients while only managing a single visual stream. 181 1.3. Conventions Used in This Document 183 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 184 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 185 document are to be interpreted as described in RFC2119. [2]. 187 RFC-Editor Note: The RFC Editor is requested to replace all 188 occurences of RFC XXXY with the RFC number 189 draft-ietf-avt-rtp-jpeg2000 receives. At that time, please remove 190 this note. 192 2. Payload Format Enhanced Processing 194 2.1. Enhanced Processing Markers 196 This section of the document describes additional usage in the values 197 of mh_id and priority fields and interpretation which differ from RFC 198 XXXY [1]. Implementions of this document should follow RFC XXXY [1] 199 first then add additional header processing as described in this 200 document. Implementations following this document are expected to 201 interoperate with implementations of [1] and this document as well. 203 The RTP payload header format for JPEG 2000 video stream is as 204 follows: 206 0 1 2 3 207 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 208 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 209 |tp |MHF|mh_id|T| priority | tile number | 210 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 211 |reserved | fragment offset | 212 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 214 Figure 1: RTP payload header format for JPEG 2000 216 mh_id (Main Header Identification) : 3 bits 218 Main header identification value. This is used for JPEG 2000 main 219 header recovery. 221 The initial value of mh_id MUST be 1 at the beginning of the 222 session. 224 The same mh_id value is used as long as the coding parameters 225 described in the main header remains unchanged between frames. 227 The mh_id value MUST be incremented by 1 every time a new main 228 header is transmitted. Once the mh_id value becomes greater than 229 7, it SHOULD roll over to 1. 231 When mh_id is 0, it has special usage for the receiver. This 232 special usage is described in Section 4.2 of this document. 234 Senders should follow Section 4.1 of this document for proper 235 mh_id assignment and usage. 237 priority : 8 bits 239 The priority field indicates the importance of the JPEG 2000 240 packet included in the payload. Typically, a higher priority is 241 set in the packets containing JPEG 2000 packets containing the 242 lower sub-bands. 244 Special values of priority: 246 0: This is reserved for payload which contain a header (main or 247 tile part header.) This is considered the most important. 249 1 to 255: These values decrease in importance as the values 250 increase. (i.e. 1 is more important than 2, etc.) Applying 251 priority values should correlate directly to JPEG 2000 252 codestream in importance. 254 The lower the priority value is the higher the importance. A 255 priority value of 0 is the highest importance and 255 is the 256 lowest importance. We define the priority value 0 as a special 257 priority value for the headers (the main header or tile-part 258 header). If any headers (the main header or tile-part header) are 259 packed into the RTP payload, the sender MUST set the priority 260 value to 0. 262 Assignment of the values are described in Section 3 264 3. Priority Mapping Table 266 For the progression order, the priority value for each JPEG 2000 267 packet is given by the priority mapping table. 269 This document specify several commonly-used priority mapping tables, 270 pre-defined priority mapping tables: packet number based (default), 271 progression-based, layer-based, resolution-based, position-based, and 272 component-based. 274 Packet number priority mapping is REQUIRED to be supported by clients 275 implementing this specification. Other priority mapping tables 276 (progression, layer, resolution, and component based) are OPTIONAL to 277 implementations of this specification. 279 Rules that all implementations of this specification MUST follow in 280 all priority modes: 282 o When there is a header in the packet with a JPEG 2000 packet, the 283 sender MUST set the payload packet priority value to 0. 285 o When there are multiple JPEG 2000 packets in the same RTP payload 286 packet, the sender MUST set the payload packet priority value to 287 the lowest JPEG 2000 packet. (i.e. if JPEG 2000 packets with 288 priority: 5,6,7 are packed into a single payload, the priority 289 value will be 5.) 291 3.1. Packet Number Based Ordering 293 Packet number based ordering assigns the payload packet priority 294 value from the "JPEG 2000 packet value". (note: JPEG 2000 codestreams 295 are stored in units of packets and each packet has a value .) This 296 method is the default method for assigning priority value. All 297 implementations of this specification MUST support this method. 299 If the JPEG 2000 codestream packet value is greater than 255, the 300 sender MUST set the payload priority value to 255. 302 3.2. Progression Based Ordering 304 The sender will assign the payload packet priority value only based 305 on layer, resolution, and component ordering of the codestream. 307 The ordering can assign the different priority values in the same 308 layer or the resolution level, which cannot do in the layer based 309 ordering or resolution based ordering. 311 The difference from the packet number based ordering is that it does 312 not assign the value in the position level, which saves the priority 313 values usage. The position based priority signaling is not so 314 important because a receiver could recognize the position by checking 315 the tile number field. Therefore, the ordering would be useful. 317 For example: 319 If the codestream is ordered in LRCP (Layer, Resolution, Component, 320 Position) with 1 layer, 2 resolutions, 3 components, and 2 positions, 321 an example would have packet numbering as so: 323 All the packets in: 325 layer.........0 326 resolution....0 327 component.....0 328 position......0 or 1 330 then the packet priority value : 1 332 All the packets in: 334 layer.........0 335 resolution....0 336 component.....1 337 position......0 or 1 339 then the packet priority value : 2 341 All the packets in: 343 layer.........0 344 resolution....0 345 component.....2 346 position......0 or 1 348 then the packet priority value : 3 350 All the packets in: 352 layer.........0 353 resolution....1 354 component.....0 355 position......0 or 1 357 then the packet priority value : 4 358 All the packets in: 360 layer.........0 361 resolution....1 362 component.....1 363 position......0 or 1 365 then the packet priority value : 5 367 3.3. Layer Based Ordering 369 Layer-based priority mapping table simplifies the default mapping to 370 just matching JPEG 2000 packets together from the same layer. 372 For example: 374 All the packets in layer 0 : packet priority value : 1 375 All the packets in layer 1 : packet priority value : 2 376 All the packets in layer 2 : packet priority value : 3 377 ... 378 All the packets in layer n : packet priority value : n+1 379 All the packets in layer 255 : packet priority value : 255 381 3.4. Resolution Based Ordering 383 Resolution-based priority mapping table is similar to the layer based 384 order but for JPEG 2000 packets of the same resolution 386 For example: 388 All the packets in resolution 0 : packet priority value : 1 389 All the packets in resolution 1 : packet priority value : 2 390 All the packets in resolution 2 : packet priority value : 3 391 ... 392 All the packets in resolution n : packet priority value : n+1 393 All the packets in resolution 255 : packet priority value : 255 395 3.5. Component Based Ordering 397 Component-based priority mapping table is mapping together JPEG 2000 398 components of the same component 400 For example: 402 All the packets in component 0 : packet priority value : 1 403 All the packets in component 1 : packet priority value : 2 404 All the packets in component 2 : packet priority value : 3 405 ... 407 All the packets in component n : packet priority value : n+1 408 All the packets in component 255 : packet priority value : 255 410 4. JPEG 2000 Main Header Compensation Scheme 412 The mh_id field of the payload header is used to indicate whether the 413 encoding parameters of the main header are the same as the encoding 414 parameters of the previous frame. The same value is set in mh_id of 415 the RTP packet in the same frame. The mh_id and encode parameters 416 are not associated with each other as 1:1 but they are used to 417 indicate whether the encode parameters of the previous frame are the 418 same or not in the event of a lost header. 420 The mh_id field value SHOULD be saved from previous frames to be used 421 to recover the current frame's main header. If the mh_id of the 422 current frame has the same value as the mh_id value of the previous 423 frame, the previous frame's main header MAY be used to decode the 424 current frame, in case of a lost header in the current frame. 426 The sender MUST increment mh_id when parameters in the header change 427 and send a new main header accordingly. 429 The receiver MAY use the mh_id and MAY retain the header for such 430 compensation. 432 4.1. Sender Processing 434 The sender MUST transmit RTP packets with the same mh_id value if the 435 encoder parameters of the current frame are the same as the previous 436 frame. The encoding parameters are the fixed information marker 437 segment (SIZ marker) and functional marker segments (COD, COC, RGN, 438 QCD, QCC, and POC) specified in JPEG 2000 Part 1 Annex A [3]. 440 An initial value of mh_id MUST be selected randomly between 1 and 7 441 for security reasons. 443 If the encode parameters changes, the sender transmitting RTP packets 444 MUST increment the mh_id value by one, but when mh_id value becomes 445 greater than 7, a sender MUST set mh_id value back to 1. 447 4.2. Receiver Processing 449 When the receiver receives the main header completely, the RTP 450 sequence number, the mh_id and main header should be saved. Only the 451 last main header that was received completely SHOULD be saved. When 452 the mh_id value is 0, the receiver SHOULD NOT save the header. 454 When the main header is not received, the receiver may compare the 455 current payload header's mh_id value with the previous saved mh_id 456 value. If the values match, decoding may be performed by using the 457 previously saved main header. 459 If the mh_id field is set to 0, the receiver MUST NOT save the main 460 header and MUST NOT compensate for lost headers. 462 If the mh_id value changes, receivers SHOULD save the current header 463 and save the new mh_id value. The old saved header should be deleted 464 from storage. 466 5. Media Type Registration 468 This document extends the associated media type from RFC XXXY[1]. 469 Here are additional optional parameters. 471 Additional optional parameters: 473 mhc : Main Header Compensation. this option is used when sender 474 and/or receiver is utilizing the Main Header compensation 475 technique as specified in this document. Acceptable values 476 when using the Main Header compensation technique is "1", 477 otherwise, it should be "0". 479 This is a list of options to be included when the sender or 480 receiver is utilizing the Priority Table option as specified in 481 this document. 483 pt : Priority Table. this option is followed by a comma-separated 484 list of predefined priority table definitions to be used by 485 sender or receiver. 487 The option appearing front most in the option line is the most 488 important and next are of decreasing importance. 490 Acceptable values: 492 progression : this table follows the progression ordering 493 of the codestream. 495 layer : this table follows the layer ordering of the 496 codestream. 498 resolution : this table follows the resolution ordering of 499 the codestream. 501 component : this table follows the component ordering of 502 the codestream. 504 default : this table follows the ordering of the 505 codestream. 507 6. SDP Parameters 509 6.1. Mapping of the optional parameters to SDP 511 The new optional parameters mhc and pt, if presented, MUST be 512 included in the "a=fmtp" line of SDP. These parameters are expressed 513 as a media type string, in the form of a semicolon separated list of 514 parameter=value pairs. 516 6.2. Usage with the SDP Offer/Answer Model 518 In addition to SDP Offer/Answer section in RFC XXXY [1]: 520 When offering JPEG 2000 over RTP using SDP in an Offer/Answer model 521 [4], the following rules and limitations apply: 523 o All parameters MUST have an acceptable value for that parameter. 525 o All parameters MUST correspond to the parameters of the payload. 527 o If the optional parameter "mhc" is used, it MUST appear in the 528 offer with value "1", and if accepted, it SHOULD appear in the 529 answer. 531 o If the optional parameter "pt" is used, it MUST appear in the 532 offer containing a complete comma-separated list indicating which 533 priority table definitions the sender supprots. If accepted, it 534 SHOULD appear in the answer containing a single priority table 535 definition selected from the offer. 537 o If the optional parameter "mhc" is used, it MUST appear in the 538 offer with value "1", and if accepted, it MUST appear in the 539 answer. If the optional parameter "pt" is used, it MUST appear in 540 the offer containing a complete comma-separated list indicating 541 which priority table definitions the sender supports. If 542 accepted, it MUST appear in the answer containing a single 543 priority table definition selected from the offer. 545 o In a multicast environment: 547 * Senders should send out one option for priority-table- 548 definition for everyone in the group. 550 * Even if a single client in the group does not support the 551 extensions outlined in this document, senders MAY use these 552 mechanisms. A receiver which doesn't support the mechanisms 553 would safely ignore the values.in mh_id and priority field. 555 6.2.1. Examples 557 Offer/Answer example exchanges are provided. 559 6.2.1.1. Example 1 561 Alice offers Main Header Compensation functionality, YCbCr 422 color 562 space, interlace image with 720-pixel width and 480-pixel height and 563 several priority-table options (default, progression, layer, 564 resolution, component) as below: 566 v=0 567 o=alice 2890844526 2890844526 IN IP4 host.example 568 s= 569 c=IN IP4 host.example 570 t=0 0 571 m=video 49170 RTP/AVP 98 572 a=rtpmap:98 jpeg2000/90000 573 a=fmtp:98 mhc=1; sampling=YCbCr-4:2:2; interlace=1; 574 pt=default,progression,layer,resolution, component; 575 width=720;height=480 577 Bob accepts Main Header Compensation functionality, YCbCr-4:2:2 color 578 space, interlace image, default mapping table and replies: 580 v=0 581 o=bob 2890844730 2890844731 IN IP4 host.example 582 s= 583 c=IN IP4 host.example 584 t=0 0 585 m=video 49920 RTP/AVP 98 586 a=rtpmap:98 jpeg2000/90000 587 a=fmtp:98 mhc=1; sampling=YCbCr-4:2:2;interlace=1; 588 pt=default;width=720;height=480 590 6.2.1.2. Example 2 592 Alice offers Main Header Compensation, YCbCr 420 color space, 593 progressive image with 320-pixel width and 240-pixel height and layer 594 priority-table options as below: 596 v=0 597 o=alice 2890844526 2890844526 IN IP4 host.example 598 s= 599 c=IN IP4 host.example 600 t=0 0 601 m=video 49170 RTP/AVP 98 602 a=rtpmap:98 jpeg2000/90000 603 a=fmtp:98 mhc=1; sampling=YCbCr-4:2:0; 604 pt=layer;width=320;height=240 606 Bob does not accept Main Header Compensation functionality but 607 accepts YCbCr-4:2:0 color space,layer based priority mapping and 608 replies: 610 v=0 611 o=bob 2890844730 2890844731 IN IP4 host.example 612 s= 613 c=IN IP4 host.example 614 t=0 0 615 m=video 49920 RTP/AVP 98 616 a=rtpmap:98 jpeg2000/90000 617 a=fmtp:98 mhc=0; sampling=YCbCr-4:2:0; 618 pt=layer;width=320;height=240 620 6.2.1.3. Example 3 622 Alice offers 27 MHz timestamp, Main Header Compensation, YCbCr 420 623 color space, progressive image with 320-pixel width and 240-pixel 624 height and layer priority-table options as below: 626 v=0 627 o=alice 2890844526 2890844526 IN IP4 host.example 628 s= 629 c=IN IP4 host.example 630 t=0 0 631 m=video 49170 RTP/AVP 98 99 632 a=rtpmap:98 jpeg2000/27000000 633 a=rtpmap:99 jpeg2000/90000 634 a=fmtp:98 mhc=1; sampling=YCbCr-4:2:0; 635 pt=layer;width=320;height=240 636 a=fmtp:99 mhc=1; sampling=YCbCr-4:2:0; 637 pt=layer;width=320;height=240 639 Bob can accept payload type with 27 MHz timestamp, and does not 640 accept Main Header Compensation functionality but accepts YCbCr-4:2:0 641 color space,layer based priority mapping and replies: 643 v=0 644 o=bob 2890844730 2890844731 IN IP4 host.example 645 s= 646 c=IN IP4 host.example 647 t=0 0 648 m=video 49920 RTP/AVP 98 649 a=rtpmap:98 jpeg2000/27000000 650 a=fmtp:98 mhc=0; sampling=YCbCr-4:2:0; 651 pt=layer;width=320;height=240 653 7. IANA Consideration 655 This document extends the associated media type from XXXY [1]. 656 Additional parameters are specified in Section 5 of this document. 658 8. Security Consideration 660 Please refer to section 6 of RFC XXXY [1] for Security Considerations 661 regarding this RTP format. The security issues regarding enhanced 662 mechanisms presented in this document are discussed in the section. 664 The mh_id field can identify a maximum of 7 different main headers. 665 If severe packet loss (either random or intentionally introduced by 666 an attacker) causes 6 successive updates to the main header to be 667 lost, the decoder will attempt decompression using an incorrect main 668 header. Care should be taken to prevent implementation bugs with 669 potential security consequences." 671 9. Congestion Control 673 Please refer to section 7 of RFC XXXY [1] for Congestion Control 674 regarding this RTP format. 676 10. Normative References 678 [1] Futemma, "RTP Payload Format for JPEG 2000 Video Streams", 679 RFC XXXY, April 2007. 681 [2] Bradner, "Key words for use in RFCs to Indicate Requirement 682 Levels", RFC 2119, March 1997. 684 [3] ISO/IEC JTC1/SC29, ISO/IEC 15444-1 | ITU-T Rec. T.800, 685 "Information Technology - JPEG 2000 Image Coding System - Part 686 1: Core Coding System", December 2000. 688 [4] Rosenberg and Schulzrinne, "An Offer/Answer Model with Session 689 Description Protocol (SDP)", RFC 3264, June 2002. 691 Appendix A. Sample Headers in Detail 693 The following figures are sample RTP headers demonstrating values 694 that should appear in the RTP header. The packet priority is Packet 695 Number Based Priority. 697 For reference, the payload header as follows 699 0 1 2 3 700 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 701 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 702 |tp |MHF|mh_id|T| priority | tile number | 703 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 704 |reserved | fragment offset | 705 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 707 Figure 2: JPEG200 payload header 709 A.1. Sample 1: Progressive image with single tile, 3500 bytes (i.e. 710 thumbnail) 712 First Packet: This packet will have the whole main header. 210 bytes 714 0 1 2 3 715 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 716 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 717 | 0 | 3 | 1 |1| 0 | 0 | 718 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 719 | 0 | 0 | 720 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 721 |FF4F FF51 002F 0000 .... | 722 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 724 Figure 3: Header Sample 1-1 (First Packet) 726 Second Packet: This packet will have a tile header and the first tile 727 part LLband 1500 bytes 729 0 1 2 3 730 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 731 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 732 | 0 | 0 | 1 |0| 1 | 0 | 733 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 734 | 0 | 210 | 735 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 736 |FF90 000A 0000 0000 2DB3 0001 FF93 .... | 737 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 739 Figure 4: Header Sample 1-2 (Second Packet) 741 Third Packet: This packet will have the next part in the tile, no 742 tile header 1500 bytes 744 0 1 2 3 745 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 746 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 747 | 0 | 0 | 1 |0| 2 | 0 | 748 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 749 | 0 | 1710 | 750 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 751 |E841 4526 4556 9850 C2EA .... | 752 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 754 Figure 5: Header Sample 1-3 (Third Packet) 756 Fourth Packet: Last packet for the image 290 bytes 758 0 1 2 3 759 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 760 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 761 | 0 | 0 | 1 |0| 3 | 0 | 762 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 763 | 0 | 3210 | 764 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 765 |A55D 8B73 3B25 25C7 B9EB .... 2FBE B153| 766 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 768 Figure 6: Header Sample 1-4 (Fourth Packet) 770 A.2. Smaple 2: Image with 4 tiles 772 First Packet: This packet will have the whole main header. 210 bytes 774 0 1 2 3 775 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 776 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 777 | 0 | 3 | 1 |1| 0 | 0 | 778 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 779 | 0 | 0 | 780 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 781 |FF4F FF51 002F 0000 .... | 782 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 784 Figure 7: Header Sample 2-1 (First Packet) 786 Second Packet: This packet will have a first tile part (tile 0) 1400 787 bytes 789 0 1 2 3 790 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 791 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 792 | 0 | 0 | 1 |0| 1 | 0 | 793 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 794 | 0 | 210 | 795 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 796 |FF90 000A 0000 0000 0578 0001 FF93 .... | 797 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 799 Figure 8: Header Sample 2-2 (Second Packet) 801 Third Packet: This packet will have a second tile part (tile 1) 1423 802 bytes 804 0 1 2 3 805 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 806 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 807 | 0 | 0 | 1 |0| 1 | 1 | 808 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 809 | 0 | 1610 | 810 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 811 |FF90 000A 0001 0000 058F 0001 FF93 .... | 812 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 814 Figure 9: Header Sample 2-3 (Third Packet) 816 Fourth Packet: This packet will have a third tile part (tile 2) 1355 817 bytes 819 0 1 2 3 820 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 821 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 822 | 0 | 0 | 1 |0| 1 | 2 | 823 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 824 | 0 | 3033 | 825 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 826 |FF90 000A 0002 0000 054B 0001 FF93 .... | 827 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 829 Figure 10: Header Sample 2-4 (4th Packet) 831 Fifth Packet: This packet will have a fourth tile part (tile 3) 1290 832 bytes 834 0 1 2 3 835 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 836 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 837 | 0 | 0 | 1 |0| 1 | 3 | 838 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 839 | 0 | 4388 | 840 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 841 |FF90 000A 0003 0000 050A 0001 FF93 .... | 842 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 844 Figure 11: Header Sample 2-5 (5th Packet) 846 A.3. Sample 3: Packing multiple tiles in single payload, fragmented 847 header. No header compensation, progressive image 849 First Packet: This packet will have the first part of the main 850 header. 110 bytes 852 0 1 2 3 853 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 854 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 855 | 0 | 1 | 0 |1| 0 | 0 | 856 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 857 | 0 | 0 | 858 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 859 |FF4F FF51 002F 0000 .... | 860 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 861 Figure 12: Header Sample 3-1 (First Packet) 863 Second Packet: This packet has the second part of the main header. 864 1400 bytes 866 0 1 2 3 867 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 868 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 869 | 0 | 2 | 0 |1| 0 | 0 | 870 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 871 | 0 | 110 | 872 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 873 |FF64 00FF .... | 874 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 876 Figure 13: Header Sample 3-2 (Second Packet) 878 Third Packet: This packet has two tiles, tile 0 and tile 1 1400 bytes 880 0 1 2 3 881 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 882 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 883 | 0 | 0 | 0 |1| 1 | 0 | 884 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 885 | 0 | 1510 | 886 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 887 |FF90 000A 0000 0000 02BC 0001 FF93 ... | 888 // . // 889 |FF90 000A 0001 0000 02BC 0001 FF93 ... | 890 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 892 Figure 14: Header Sample 3-3 (Third Packet) 894 Fourth Packet: This packet has one tile, tile 2 1395 bytes 896 0 1 2 3 897 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 898 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 899 | 0 | 0 | 0 |0| 1 | 2 | 900 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 901 | 0 | 2910 | 902 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 903 |FF90 000A 0002 0000 0573 0001 FF93 .... | 904 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 906 Figure 15: Header Sample 3-4 (4th Packet) 908 A.4. Sample 4: Interlace image, single tile 910 The codestream of each image is ordered in LRCP (Layer, Resolution, 911 Component, Position) with 1 layer, 3 resolutions, 3 components and 1 912 position. 914 First packet: This packet will have the whole main header for the odd 915 field 210 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 | 1 | 3 | 1 |1| 0 | 0 | 921 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 922 | 0 | 0 | 923 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 924 |FF4F FF51 002F 0000 .... | 925 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 927 Figure 16: Header Sample 4-1 (First Packet) 929 Second packet: This packet will have the first part of the odd 930 field's tile where three jp2-packets are included. 1400 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 | 1 | 0 | 1 |1| 1 | 0 | 936 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 937 | 0 | 210 | 938 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 939 |FF90 000A 0000 0000 0578 0001 FF93 .... | 940 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 942 Figure 17: Header Sample 4-2 (Second Packet) 944 Third packet: This packet will have the second part of the odd 945 field's tile 1400 bytes 947 0 1 2 3 948 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 949 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 950 | 1 | 0 | 1 |1| 4 | 0 | 951 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 952 | 0 | 1610 | 953 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 954 |7F04 E708 27D9 D11D 22CB ... | 955 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 957 Figure 18: Header Sample 4-3 (Third Packet) 959 Fourth packet: This packet will have the third part of the odd 960 field's tile 1300 bytes 962 0 1 2 3 963 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 964 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 965 | 1 | 0 | 1 |1| 7 | 0 | 966 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 967 | 0 | 3010 | 968 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 969 |98BD EC9B 2826 DC62 D4AB ... | 970 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 972 Figure 19: Header Sample 4 (4th Packet) 974 Fifth packet: This packet will have the whole main header for the 975 even field 977 0 1 2 3 978 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 979 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 980 | 2 | 3 | 1 |1| 0 | 0 | 981 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 982 | 0 | 0 | 983 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 984 |FF4F FF51 002F 0000 .... | 985 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 987 Figure 20: Header Sample 4 (5th Packet) 989 Sixth packet: This packet will have the first part of the odd field's 990 tile 1400 bytes 992 0 1 2 3 993 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 994 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 995 | 2 | 0 | 1 |1| 1 | 0 | 996 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 997 | 0 | 1610 | 998 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 999 |FF90 000A 0000 0000 0578 0001 FF93 .... | 1000 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1002 Figure 21: Header Sample 4 (6th Packet) 1004 Seventh packet: This packet will have the second part of the odd 1005 field's tile 1400 bytes 1007 0 1 2 3 1008 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 1009 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1010 | 2 | 0 | 1 |1| 4 | 0 | 1011 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1012 | 0 | 3010 | 1013 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1014 |626C 42F0 166B 6BD0 F8E1 ... | 1015 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1017 Figure 22: Header Sample 4 (7th Packet) 1019 Eighth packet: This packet will have the third part of the odd 1020 field's tile 1300 bytes 1022 0 1 2 3 1023 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 1024 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1025 | 2 | 0 | 1 |1| 7 | 0 | 1026 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1027 | 0 | 4410 | 1028 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1029 |8114 41D5 18AB 4A1B ... | 1030 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1032 Figure 23: Header Sample 4 (8th Packet) 1034 Authors' Addresses 1036 Andrew Leung 1037 Sony Corporation 1038 1-7-1 Konan 1039 Minato-ku 1040 Tokyo 108-0075 1041 Japan 1043 Phone: +81 3 6748-2111 1044 Email: andrew @ ualberta . net 1045 URI: http://www.sony.net/ 1047 Satoshi Futemma 1048 Sony Corporation 1049 1-7-1 Konan 1050 Minato-ku 1051 Tokyo 108-0075 1052 Japan 1054 Phone: +81 3 6748-2111 1055 Email: satosi-f @ sm . sony . co . jp 1056 URI: http://www.sony.net/ 1058 Eisaburo Itakura 1059 Sony Corporation 1060 1-7-1 Konan 1061 Minato-ku 1062 Tokyo 108-0075 1063 Japan 1065 Phone: +81 3 6748-2111 1066 Email: itakura @ sm . sony . co . jp 1067 URI: http://www.sony.net/ 1069 Full Copyright Statement 1071 Copyright (C) The IETF Trust (2008). 1073 This document is subject to the rights, licenses and restrictions 1074 contained in BCP 78, and except as set forth therein, the authors 1075 retain all their rights. 1077 This document and the information contained herein are provided on an 1078 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 1079 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 1080 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 1081 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 1082 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 1083 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1085 Intellectual Property 1087 The IETF takes no position regarding the validity or scope of any 1088 Intellectual Property Rights or other rights that might be claimed to 1089 pertain to the implementation or use of the technology described in 1090 this document or the extent to which any license under such rights 1091 might or might not be available; nor does it represent that it has 1092 made any independent effort to identify any such rights. Information 1093 on the procedures with respect to rights in RFC documents can be 1094 found in BCP 78 and BCP 79. 1096 Copies of IPR disclosures made to the IETF Secretariat and any 1097 assurances of licenses to be made available, or the result of an 1098 attempt made to obtain a general license or permission for the use of 1099 such proprietary rights by implementers or users of this 1100 specification can be obtained from the IETF on-line IPR repository at 1101 http://www.ietf.org/ipr. 1103 The IETF invites any interested party to bring to its attention any 1104 copyrights, patents or patent applications, or other proprietary 1105 rights that may cover technology that may be required to implement 1106 this standard. Please address the information to the IETF at 1107 ietf-ipr@ietf.org. 1109 Acknowledgment 1111 Funding for the RFC Editor function is provided by the IETF 1112 Administrative Support Activity (IASA).