idnits 2.17.1 draft-ietf-avt-rtp-jpeg2000-beam-04.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 19. -- Found old boilerplate from RFC 3978, Section 5.5 on line 1112. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 1089. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 1096. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 1102. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 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 (May 16, 2006) is 6549 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) == Unused Reference: '5' is defined on line 709, but no explicit reference was found in the text == Unused Reference: '10' is defined on line 726, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. '1' -- Possible downref: Non-RFC (?) normative reference: ref. '3' ** Obsolete normative reference: RFC 2327 (ref. '6') (Obsoleted by RFC 4566) ** Obsolete normative reference: RFC 4288 (ref. '8') (Obsoleted by RFC 6838) ** Obsolete normative reference: RFC 3555 (ref. '9') (Obsoleted by RFC 4855, RFC 4856) Summary: 6 errors (**), 0 flaws (~~), 4 warnings (==), 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 Expires: November 17, 2006 E. Itakura 5 Sony 6 May 16, 2006 8 Payload Format for JPEG 2000 Video: Extensions for Scalability and Main 9 Header Recovery 10 draft-ietf-avt-rtp-jpeg2000-beam-04 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. 18 This document may not be modified, and derivative works of it may not 19 be created, other than to extract Section 1.2 as-is for separate use. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF), its areas, and its working groups. Note that 23 other groups may also distribute working documents as Internet- 24 Drafts. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 The list of current Internet-Drafts can be accessed at 32 http://www.ietf.org/ietf/1id-abstracts.txt. 34 The list of Internet-Draft Shadow Directories can be accessed at 35 http://www.ietf.org/shadow.html. 37 This Internet-Draft will expire on November 17, 2006. 39 Copyright Notice 41 Copyright (C) The Internet Society (2006). 43 Abstract 45 This memo describes extended uses for payload header in RFC document: 46 "RTP Payload Format for JPEG 2000 Video Streams." For better support 47 of JPEG 2000 features such as scalability and includes a main header 48 recovery method. 50 This memo MUST be accompanied with a complete implementation of "RTP 51 Payload Format for JPEG 2000 Video Streams." That document is a 52 complete description of the payload header and signaling, this 53 document only describes additional processing for the payload header. 54 There is an additional media type and SDP marker signaling for 55 implementations of this document. 57 Table of Contents 59 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 60 1.1. History . . . . . . . . . . . . . . . . . . . . . . . . . 3 61 1.2. Description of the Mechanisms . . . . . . . . . . . . . . 3 62 1.2.1. Main Header Compensation . . . . . . . . . . . . . . . 3 63 1.2.2. Priority Table . . . . . . . . . . . . . . . . . . . . 3 64 1.3. Conventions Used in This Document . . . . . . . . . . . . 4 65 2. Payload Format Enhanced Processing . . . . . . . . . . . . . . 5 66 2.1. Enhanced Processing Markers . . . . . . . . . . . . . . . 5 67 3. Priority Mapping Table . . . . . . . . . . . . . . . . . . . . 7 68 3.1. Pre-Defined Priority Mapping . . . . . . . . . . . . . . . 7 69 3.1.1. Packet Number Based Ordering . . . . . . . . . . . . . 7 70 3.1.2. Progression Based Ordering . . . . . . . . . . . . . . 7 71 3.1.3. Layer Based Ordering . . . . . . . . . . . . . . . . . 8 72 3.1.4. Resolution Based Ordering . . . . . . . . . . . . . . 8 73 3.1.5. Component Based Ordering . . . . . . . . . . . . . . . 9 74 4. JPEG 2000 Main Header Compensation Scheme . . . . . . . . . . 10 75 4.1. Sender Processing . . . . . . . . . . . . . . . . . . . . 10 76 4.2. Receiver Processing . . . . . . . . . . . . . . . . . . . 10 77 5. Security Consideration . . . . . . . . . . . . . . . . . . . . 12 78 6. Congestion Control . . . . . . . . . . . . . . . . . . . . . . 13 79 7. IANA Consideration . . . . . . . . . . . . . . . . . . . . . . 14 80 7.1. Media Type Registration . . . . . . . . . . . . . . . . . 14 81 7.2. SDP Parameters . . . . . . . . . . . . . . . . . . . . . . 17 82 8. Usage with the SDP Offer/Answer Model . . . . . . . . . . . . 18 83 8.1. Examples . . . . . . . . . . . . . . . . . . . . . . . . . 18 84 8.1.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . 18 85 8.1.2. Example 2 . . . . . . . . . . . . . . . . . . . . . . 19 86 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20 87 9.1. Normative References . . . . . . . . . . . . . . . . . . . 20 88 9.2. Informative References . . . . . . . . . . . . . . . . . . 20 89 Appendix A. Sample Headers in Detail . . . . . . . . . . . . . . 21 90 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 29 91 Intellectual Property and Copyright Statements . . . . . . . . . . 30 93 1. Introduction 95 This document is an extension of: "RTP Payload Format for JPEG 2000 96 Video Streams" [1]. There are additional mechanisms that can be used 97 with certain parts of the header in [1] to support JPEG 2000 features 98 such as scalability and a main header compensation method. These 99 mechanisms are described in detail in this document. 101 1.1. History 103 In the development of RFC XXXY [1], there was an issue of IPR claims 104 on certain mechanisms with main header compensation, priority table 105 usage, etc. in RFC XXXY [1]. As these are not "essential" to the 106 core RTP format of RFC XXXY [1] and only describes a mechanism, it 107 was decided that splitting these mechanisms from the core RTP format 108 in to a separate document. This is the document describing the IPR 109 related mechanisms for main header recover and priority table usage. 111 1.2. Description of the Mechanisms 113 1.2.1. Main Header Compensation 115 JPEG 2000's scalable coding scheme allows for decompressing truncated 116 or partial data streams but only when the main header is present. If 117 the header is lost, the data is useless. With JPEG 2000 video 118 coding, coding parameters between frames will rarely change and 119 previous headers may be used in newly received data which the header 120 have been lost. 122 Compensation of the main header that has been lost is very simple 123 with this procedure. In the case of JPEG 2000 video, it is very 124 common that encode parameters will not vary greatly between 125 successive frames. Even if the RTP packet including the main header 126 of a frame has been dropped, decoding may be performed by using the 127 main header of a previous frame. 129 1.2.2. Priority Table 131 JPEG 2000 codestream has rich functionality built into it so decoders 132 can easily handle scalable delivery or progressive transmission. 133 Progressive transmission allows images to be reconstructed with 134 increasing pixel accuracy or spatial resolution. This feature allows 135 the reconstruction of images with different resolutions and pixel 136 accuracy, for different target devices. A single image source can 137 provide a codestream that is easily processed for smaller image 138 display devices. 140 JPEG 2000 packets contain all compressed image data from a specific: 142 layer, component, resolution level, and/or precinct. The order in 143 which these JPEG 2000 packets are found in the codestream is called: 144 progression order. The ordering of the JPEG 2000 packets can 145 progress along four axes: layer, component, resolution and precinct 146 (or position). 148 Providing a priority field to indicate the importance of data 149 contained in a given RTP packet can aid in usage of JPEG 2000 150 progressive and scalable functions. 152 1.3. Conventions Used in This Document 154 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 155 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 156 document are to be interpreted as described in RFC2119. [2]. 158 RFC-Editor Note: The RFC Editor is requested to replace all 159 occurences of RFC XXXY with the RFC number 160 draft-ietf-avt-rtp-jpeg2000 receives. At that time, please remove 161 this note. 163 2. Payload Format Enhanced Processing 165 2.1. Enhanced Processing Markers 167 This section of the document describes additional usage in the values 168 of mh_id and priority fields and interpretation which differ from RFC 169 XXXY [1]. Implementions of this document should follow RFC XXXY [1] 170 first then add additional header processing as described in this 171 document. Implementations following this document are expected to 172 interoperate with implementations of [1] and this document as well. 174 The RTP payload header format for JPEG 2000 video stream is as 175 follows: 177 0 1 2 3 178 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 179 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 180 |tp |MHF|mh_id|T| priority | tile number | 181 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 182 |reserved | fragment offset | 183 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 185 Figure 1: RTP payload header format for JPEG 2000 187 mh_id (Main Header Identification) : 3 bits 189 Main header identification value. This is used for JPEG 2000 main 190 header recovery. 192 The initial value of mh_id is random, and may take any value 193 between 1-7, but MUST NOT be 0. 195 The same mh_id value is used as long as the coding parameters 196 described in the main header remains unchanged between frames. 198 The mh_id value MUST be incremented by 1 every time a new main 199 header is transmitted. Once the mh_id value is greater than 7, it 200 rolls over to 1. 202 When mh_id is 0, it has special usage for the receiver. This 203 special usage is described in Section 4.2 of this document. 205 Senders should follow Section 4.1 of this document for proper 206 mh_id assignment and usage. 208 priority : 8 bits 210 The priority field indicates the importance of the JPEG 2000 211 packet included in the payload. Typically, a higher priority is 212 set in the packets containing JPEG 2000 packets containing the 213 lower sub-bands. 215 Special values of priority: 217 0: This is reserved for payload which contain a header (main or 218 tile part header.) This is considered the most important. 220 1 to 255: These values decrease in importance as the values 221 increase. (i.e. 1 is more important than 2, etc.) Hence 222 applying priority values should correlate directly to JPEG 2000 223 codestream in importance. 225 The lower the priority value is the higher the importance. 226 Simply, the priority value 0 is the highest importance and 255 is 227 the lowest importance. We define the priority value 0 as a 228 special priority value for the headers (the main header or tile- 229 part header). When any headers (the main header or tile-part 230 header) are packed into the RTP payload, the sender MUST set the 231 priority value to 0. 233 Assignment of the values are described in Section 3 with pre- 234 defined table assignments in Section 3.1. 236 3. Priority Mapping Table 238 For the progression order, the priority value for each JPEG 2000 239 packet is given by the priority mapping table. 241 3.1. Pre-Defined Priority Mapping 243 This document specify several commonly-used priority mapping tables, 244 pre-defined priority mapping tables: packet number based (default), 245 progression-based, layer-based, resolution-based, position-based, and 246 component-based. 248 Packet number priority mapping is REQUIRED to be supported by clients 249 implementing this specification. Other priority mapping tables 250 (progression, layer, resolution, and component based) are OPTIONAL to 251 implementations of this specification. 253 Rules that all implementations of this specification MUST follow in 254 all priority modes: 256 o When there is a header in the packet with a JPEG 2000 packet, the 257 sender MUST set the payload packet priority value to 0. 259 o When there are multiple JPEG 2000 packets in the same RTP payload 260 packet, the sender MUST set the payload packet priority value to 261 the lowest JPEG 2000 packet. (i.e. if JPEG 2000 packets with 262 priority: 5,6,7 are packed into a single payload, the priority 263 value will be 5.) 265 3.1.1. Packet Number Based Ordering 267 Packet number based ordering assigns the payload packet priority 268 value from the "JPEG 2000 packet value". (note: JPEG 2000 codestreams 269 are stored in units of packets and each packet has a value .) This 270 method is the default method for assigning priority value. All 271 implementations of this specification MUST support this method. 273 If the JPEG 2000 codestream packet value is greater than 255, the 274 sender MUST set the payload priority value to 255. 276 3.1.2. Progression Based Ordering 278 The sender will assign the payload packet priority value only based 279 on layer, resolution, and component ordering of the codestream. 281 This is similar to the packet number based assignment but will not 282 take into account the precinct number or position in the JPEG 2000 283 codestream. 285 For example: 287 If the codestream is ordered in LRCP (Layer, Resolution, Component, 288 Position) 290 All the packets in: 292 layer.........0 293 resolution....0 294 component.....0 296 then the packet priority value : 1 298 All the packets in: 300 layer.........0 301 resolution....0 302 component.....1 304 then the packet priority value : 2 306 All the packets in: 308 layer.........0 309 resolution....0 310 component.....2 312 then the packet priority value : 3 314 3.1.3. Layer Based Ordering 316 Layer-based priority mapping table simplifies the default mapping to 317 just matching JPEG 2000 packets together from the same layer. 319 For example: 321 All the packets in layer 0 : packet priority value : 1 322 All the packets in layer 1 : packet priority value : 2 323 All the packets in layer 2 : packet priority value : 3 324 ... 325 All the packets in layer n : packet priority value : n+1 327 3.1.4. Resolution Based Ordering 329 Resolution-based priority mapping table is similar to the layer based 330 order but for JPEG 2000 packets of the same resolution 332 For example: 334 All the packets in resolution 0 : packet priority value : 1 335 All the packets in resolution 1 : packet priority value : 2 336 All the packets in resolution 2 : packet priority value : 3 337 ... 338 All the packets in resolution n : packet priority value : n+1 340 3.1.5. Component Based Ordering 342 Component-based priority mapping table is mapping together JPEG 2000 343 components of the same component 345 For example: 347 All the packets in component 0 : packet priority value : 1 348 All the packets in component 1 : packet priority value : 2 349 All the packets in component 2 : packet priority value : 3 350 ... 351 All the packets in component n : packet priority value : n+1 353 4. JPEG 2000 Main Header Compensation Scheme 355 The mh_id field of the payload header is used to indicate whether the 356 encoding parameters of the main header are the same as the encoding 357 parameters of the previous frame. The same value is set in mh_id of 358 the RTP packet in the same frame. The mh_id and encode parameters 359 are not associated with each other as 1:1 but they are used to 360 indicate whether the encode parameters of the previous frame are the 361 same or not in the event of a lost header. 363 The mh_id field value SHOULD be saved from previous frames to be used 364 to recover the current frame's main header. If the mh_id of the 365 current frame has the same value as the mh_id value of the previous 366 frame, the previous frame's main header MAY be used to decode the 367 current frame, in case of a lost header in the current frame. 369 The sender MUST increment mh_id when parameters in the header change 370 and send a new main header accordingly. 372 The receiver MAY use the mh_id and MAY retain the header for such 373 compensation. 375 4.1. Sender Processing 377 The sender MUST transmit RTP packets with the same mh_id value if the 378 encoder parameters of the current frame are the same as the previous 379 frame. The encoding parameters are the fixed information marker 380 segment (SIZ marker) and functional marker segments (COD, COC, RGN, 381 QCD, QCC, and POC) specified in JPEG 2000 Part 1 Annex A [3]. 383 An initial value of mh_id MUST be selected randomly between 1 and 7 384 for security reasons. 386 If the encode parameters changes, the sender transmitting RTP packets 387 MUST increment the mh_id value by one, but when mh_id value becomes 388 greater than 7, a sender MUST set mh_id value to 1. 390 4.2. Receiver Processing 392 When the receiver receives the main header completely, the RTP 393 sequence number, the mh_id and main header should be saved. Only the 394 last main header that was received completely SHOULD be saved. When 395 the mh_id value is 0, the receiver SHOULD NOT save the header. 397 When the main header is not received, the receiver may compare the 398 current payload header's mh_id value with the previous saved mh_id 399 value. If the values match, decoding may be performed by using the 400 previously saved main header. 402 If the mh_id field is set to 0, the receiver MUST NOT save the main 403 header and MUST NOT compensate for lost headers. 405 If the mh_id value changes, receivers SHOULD save the current header 406 and save the new mh_id value. The old saved header should be deleted 407 from storage. 409 5. Security Consideration 411 Please refer to section 6 of RFC XXXY [1] for Security Considerations 412 regarding this RTP format. 414 6. Congestion Control 416 Please refer to section 7 of RFC XXXY [1] for Congestion Control 417 regarding this RTP format. 419 7. IANA Consideration 421 7.1. Media Type Registration 423 This document extends the associated media type from RFC XXXY[1]: 424 Here is the complete original for reference. 426 This registration uses the template defined in [8] and follows [9]. 428 Type name: video 430 Subtype name: jpeg2000 432 Required parameters: 434 sampling: A list of values specifying the color space of the 435 payload data. 437 Acceptable values: 439 RGB: standard Red, Green, Blue color space. 441 BGR: standard Blue, Green, Red color space. 443 RGBA: standard Red, Green, Blue, Alpha color space. 445 BGRA: standard Blue, Green, Red, Alpha color space. 447 YCbCr-4:4:4: standard YCbCr color space, no subsampling. 449 YCbCr-4:2:2: standard YCbCr color space, Cb and Cr are 450 subsampled horizontally by 1/2. 452 YCbCr-4:2:0: standard YCbCr color space, Cb and Cr are 453 subsampled horizontally and vertically by 1/2. 455 YCbCr-4:1:1: standard YCbCr color space, Cb and Cr are 456 subsampled vertically by 1/4 458 GRAYSCALE: basically a single component image of just 459 multilevels of grey. 461 EXTENSION VALUE: Additional color samplings can be registered 462 with and current listing of registered color samplings at: 463 Color Sampling Registration Authority. 465 Optional parameters: 467 interlace: interlace scanning. If payload is in interlace format, 468 the acceptable value is "1", otherwise, the value should be 469 "0". Each complete image forms vertically half the display. tp 470 value MUST properly specify the field the image represents 471 odd(tp=1), or even(tp=2). If this option is not present, the 472 payload MUST be in progressive format and tp MUST be set to 0. 474 width: A parameter describing the maximum width of the video 475 stream. This parameter MUST appear when height is present. 476 Acceptable values: - an integer value between 0 - 477 4,294,967,295. 479 height: A parameter describing the maximum height of the video 480 stream. This parameter MUST appear when width is present. 481 Acceptable values: - an integer value between 0 - 482 4,294,967,295. 484 The receiver MUST ignore any unspecified parameters outside of this 485 list and in [1] . 487 Additional parameters for this extension: 489 mhc : Main Header Compensation. this option is used when sender 490 and/or receiver is utilizing the Main Header compensation 491 technique as specified in this document. Acceptable values 492 when using the Main Header compensation technique is "1", 493 otherwise, it should be "0". 495 This is a list of options to be included when the sender or 496 receiver is utilizing the Priority Table(s) as specified in 497 this document. 499 pt : Priority Table. this option is followed by a comma-separated 500 list of predefined priority table definitions to be used by 501 sender or receiver. 503 The option appearing front most in the option line is the most 504 important and next ones are of decreasing importance. 506 Acceptable values: 508 progression : this table follows the progression ordering of 509 the codestream. 511 layer : this table follows the layer ordering of the 512 codestream. 514 resolution : this table follows the resolution ordering of 515 the codestream. 517 component : this table follows the component ordering of the 518 codestream. 520 default : this table follows the ordering of the codestream. 522 Encoding considerations: 524 This media type is framed and binary, see Section 4.8 in [8] 526 Security considerations: 528 see security considerations section Section 5 of this document. 530 Interoperability considerations: 532 JPEG 2000 video stream is a sequence of JPEG 2000 still images. 533 An implementation in compliant with [3] can decode and attempt to 534 display the encoded JPEG 2000 video stream. 536 Published specification: ISO/IEC 15444-1 | ITU-T Rec. T.800 538 Applications which use this media type: 540 video streaming and communication 542 Person and email address to contact for further information: 544 Eisaburo Itakura, Satoshi Futemma, Andrew Leung 545 Email: {itakura|satosi-f}@sm.sony.co.jp, andrew@ualberta.net 547 Intended usage: Restriction 549 Restrictions on Usage: 551 This media type depends on RTP framing, and hence is only 552 defined for the transfer via RTP [4]. Transport within other 553 framing protocols is not defined at the time. 555 Author/Change Controller: 557 Author: 559 Eisaburo Itakura, Satoshi Futemma, Andrew Leung 560 Email: {itakura|satosi-f}@sm.sony.co.jp, andrew@ualberta.net 562 Change controller: 564 IETF Audio/Video Transport Working Group delegated from the 565 IESG 567 7.2. SDP Parameters 569 In addition to SDP Parameters section in [1]: 571 The media type video/jpeg2000 string is mapped to fields in the 572 Session Description Protocol (SDP) [6] as follows: 574 o The media name in the "m=" line of SDP MUST be video. 576 o The encoding name in the "a=rtpmap" line of SDP MUST be jpeg2000 577 (the MIME subtype). 579 o The clock rate in the "a=rtpmap" line MUST be 90000. 581 o The OPTIONAL parameters "mhc" or "pt" MUST be included in the 582 "a=fmtp" line of SDP. 584 These parameters are expressed as a media type string, in the form of 585 a semicolon separated list of parameter=value pairs. 587 Therefore, an example of media representation in SDP is as follows: 589 m=video 49170/2 RTP/AVP 98 590 a=rtpmap:98 jpeg2000/90000 591 a=fmtp:98 mhc; pt=default; sampling=YCbCr- 592 4:2:0;width=128;height=128 594 8. Usage with the SDP Offer/Answer Model 596 In addition to SDP Offer/Answer section in RFC XXXY [1]: 598 When offering JPEG 2000 over RTP using SDP in an Offer/Answer model 599 [7], the following rules and limitations apply: 601 o All parameters MUST have an acceptable value for that parameter. 603 o All parameters MUST correspond to the parameters of the payload. 605 o The parameters "mhc" or "pt" MUST appear in the offer and answer. 606 If the parameter "mhc" or "pt" is not in the answer, senders 607 should not process the header according to this document. 609 o For the "pt" option: 611 * Senders should send a complete list indicating which option are 612 available to the receiver. The receiver should answer with 613 their preference from the offer list. 615 o In a multicast environment: 617 * Senders should send out one option for priority-table- 618 definition for everyone in the group. 620 * If a single client in the group do not support the extensions 621 outlined in this document, senders SHOULD NOT use additional 622 techniques outlined in this document. 624 This is highly recommended for multicast streams where not all 625 receivers are of the same type. 627 8.1. Examples 629 Offer/Answer example exchanges are provided. 631 8.1.1. Example 1 633 Alice offers Main Header Compensation functionality, YCbCr 422 color 634 space, interlace image with 720-pixel width and 480-pixel height and 635 several priority-table options (default, progression, layer, 636 resolution, component) as below: 638 v=0 639 o=alice 2890844526 2890844526 IN IP4 host.example.com 640 s= 641 c=IN IP4 host.example.com 642 t=0 0 643 m=video 49170 RTP/AVP 98 644 a=rtpmap:98 jpeg2000/90000 645 a=fmtp:98 mhc=1;sampling= YCbCr-4:2:2;interlace=1 646 a=fmtp:98 pt=default, progression,layer, resolution, component; 647 width=720; height=480 649 Bob accepts Main Header Compensation functionality, YCbCr-4:2:2 color 650 space, interlace image, default mapping table and replies: 652 v=0 653 o=bob 2890844730 2890844731 IN IP4 host.example.com 654 s= 655 c=IN IP4 host.example.com 656 t=0 0 657 m=video 49920 RTP/AVP 98 658 a=rtpmap:98 jpeg2000/90000 659 a=fmtp:98 mhc=1; pt=default; width=720;height=480 661 8.1.2. Example 2 663 Alice offers Main Header Compensation, YCbCr 420 color space, 664 progressive image with 320-pixel width and 240-pixel height and layer 665 priority-table options as below: 667 v=0 668 o=alice 2890844526 2890844526 IN IP4 host.example.com 669 s= 670 c=IN IP4 host.example.com 671 t=0 0 672 m=video 49170 RTP/AVP 98 673 a=rtpmap:98 jpeg2000/90000 674 a=fmtp:98 mhc=1;sampling= YCbCr-4:2:0 675 a=fmtp:98 pt=layer; width=320; height=240 677 Bob does not accept Main Header Compensation functionality but 678 accepts YCbCr-4:2:0 color space,layer based priority mapping and 679 replies: 681 v=0 682 o=bob 2890844730 2890844731 IN IP4 host.example.com 683 s= 684 c=IN IP4 host.example.com 685 t=0 0 686 m=video 49920 RTP/AVP 98 687 a=rtpmap:98 jpeg2000/90000 688 a=fmtp:98 mhc=0; 689 a=fmtp:98 pt=layer; width=320; height=240 691 9. References 693 9.1. Normative References 695 [1] Futemma, "RTP Payload Format for JPEG 2000 Video Streams", 696 RFC XXXY, March 2006. 698 [2] Bradner, "Key words for use in RFCs to Indicate Requirement 699 Levels", RFC 2119, March 1997. 701 [3] ISO/IEC JTC1/SC29, ISO/IEC 15444-1 | ITU-T Rec. T.800, 702 "Information Technology - JPEG 2000 Image Coding System - Part 703 1: Core Coding System", December 2000. 705 [4] Schulzrinne, Casner, Frederick, and Jacobson, "RTP: A Transport 706 Protocol for Real Time Applications", RFC 3550, STD 64, 707 July 2003. 709 [5] Baugher, McGrew, Naslund, Carrara, and Norrman, "The Secure 710 Real-time Transport Protocol (SRTP", RFC 3711, March 2004. 712 [6] Handley and Jacobson, "SDP: Session Description Protocol", 713 RFC 2327, April 1998. 715 [7] Rosenberg and Schulzrinne, "An Offer/Answer Model with Session 716 Description Protocol (SDP)", RFC 3264, June 2002. 718 [8] Freed and Klensin, "Media Type Specifications and Registration 719 Procedures", RFC 4288, December 2005. 721 [9] Casner and Hoschka, "MIME Type Registration of RTP Payload 722 Formats", RFC 3555, July 2003. 724 9.2. Informative References 726 [10] Deering, "Host Extensions for IP Multicasting", RFC 1112, 727 August 1989. 729 Appendix A. Sample Headers in Detail 731 0 1 2 3 732 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 733 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 734 |tp |MHF|mh_id|T| priority | tile number | 735 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 736 |reserved | fragment offset | 737 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 739 Figure 2 741 First Packet: This packet will have the whole main header. 210 bytes 743 0 1 2 3 744 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 745 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 746 |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| 747 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 748 |0 0 0 0 0 0 0 0|0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0| 749 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 750 |FF4FFF51002F000 .... | 751 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 753 Figure 3 755 Second Packet: This packet will have a tile header and the first tile 756 part LLband 1500 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 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| 762 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 763 |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| 764 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 765 |FF90 000A 0000 0000 2DB3 0001 FF93 | 766 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 768 Figure 4 769 Third Packet: This packet will have the next part in the tile, no 770 tile header 1500 bytes 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 |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| 776 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 777 |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| 778 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 779 |E841 4526 4556 9850 C2EA .... | 780 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 782 Figure 5 784 Fourth Packet: Last packet for the image 290 bytes 786 0 1 2 3 787 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 788 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 789 |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| 790 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 791 |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| 792 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 793 |A55D 8B73 3B25 25C7 B9EB .... 2FBEB153| 794 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 796 Figure 6 798 First Packet: This packet will have the whole main header. 210 bytes 800 0 1 2 3 801 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 802 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 803 |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| 804 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 805 |0 0 0 0 0 0 0 0|0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0| 806 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 807 |FF4FFF51002F000 .... | 808 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 810 Figure 7 811 Second Packet: This packet will have a first tile part (tile 0) 1400 812 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|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| 818 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 819 |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| 820 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 821 |FF90 000A 0000 0000 0578 0001 FF93 .... | 822 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 824 Figure 8 826 Third Packet: This packet will have a second tile part (tile 1) 1423 827 bytes 829 0 1 2 3 830 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 831 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 832 |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| 833 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 834 |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| 835 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 836 |FF90 000A 0001 0000 058F 0001 FF93 .... | 837 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 839 Figure 9 841 Fourth Packet: This packet will have a third tile part (tile 2) 1355 842 bytes 844 0 1 2 3 845 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 846 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 847 |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| 848 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 849 |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| 850 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 851 |FF90 000A 0002 0000 054B 0001 FF93 .... | 852 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 854 Figure 10 855 Fifth Packet: This packet will have a fourth tile part (tile 3) 1290 856 bytes 858 0 1 2 3 859 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 860 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 861 |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| 862 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 863 |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| 864 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 865 |FF90 000A 0003 0000 050A 0001 FF93 .... | 866 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 868 Figure 11 870 First Packet: This packet will have the first part of the main 871 header. 110 bytes 873 0 1 2 3 874 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 875 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 876 |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| 877 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 878 |0 0 0 0 0 0 0 0|0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0| 879 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 880 |FF4FFF51002F000 .... | 881 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 883 Figure 12 885 Second Packet: This packet has the second part of the header. 1400 886 bytes 888 0 1 2 3 889 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 890 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 891 |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| 892 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 893 |0 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| 894 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 895 |FF6400FF .... | 896 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 898 Figure 13 899 Third Packet: This packet has two tiles, tile 0 and tile 1 1400 bytes 901 0 1 2 3 902 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 903 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 904 |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| 905 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 906 |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| 907 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 908 |FF90 000A 0000 0000 02BC 0001 FF93 ... | 909 |FF90 000A 0001 0000 02BC 0001 FF93 ... | 910 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 912 Figure 14 914 Fourth Packet: This packet has one tile, tile 2 1395 bytes 916 0 1 2 3 917 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 918 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 919 |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| 920 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 921 |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| 922 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 923 |FF90 000A 0002 0000 0573 0001 FF93 .... | 924 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 926 Figure 15 928 First packet: This packet will have the whole main header for the odd 929 field 210 bytes 931 0 1 2 3 932 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 933 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 934 |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| 935 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 936 |0 0 0 0 0 0 0 0|0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0| 937 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 938 |FF4FFF51002F000 .... | 939 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 941 Figure 16 942 Second packet: This packet will have the first part of the odd 943 field's tile 1400 bytes 945 0 1 2 3 946 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 947 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 948 |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| 949 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 950 |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| 951 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 952 |FF90 000A 0000 0000 0578 0001 FF93 .... | 953 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 955 Figure 17 957 Third packet: This packet will have the second part of the odd 958 field's tile 1400 bytes 960 0 1 2 3 961 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 962 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 963 |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| 964 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 965 |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| 966 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 967 |7F04 E708 27D9 D11D 22CB ... | 968 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 970 Figure 18 972 Fourth packet: This packet will have the third part of the odd 973 field's tile 1300 bytes 975 0 1 2 3 976 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 977 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 978 |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| 979 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 980 |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| 981 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 982 |98BD EC9B 2826 DC62 D4AB ... | 983 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 985 Figure 19 986 Fifth packet: This packet will have the whole main header for the 987 even field 989 0 1 2 3 990 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 991 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 992 |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| 993 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 994 |0 0 0 0 0 0 0 0|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 |FF4FFF51002F000 .... | 997 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 999 Figure 20 1001 Sixth packet: This packet will have the first part of the odd field's 1002 tile 1400 bytes 1004 0 1 2 3 1005 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 1006 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1007 |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| 1008 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1009 |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| 1010 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1011 |FF90 000A 0000 0000 0578 0001 FF93 .... | 1012 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1014 Figure 21 1016 Seventh packet: This packet will have the second part of the odd 1017 field's tile 1400 bytes 1019 0 1 2 3 1020 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 1021 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1022 |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| 1023 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1024 |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| 1025 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1026 |626C 42F0 166B 6BD0 F8E1 ... | 1027 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1029 Figure 22 1030 Eighth packet: This packet will have the third part of the odd 1031 field's tile 1300 bytes 1033 0 1 2 3 1034 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 1035 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1036 |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| 1037 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1038 |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| 1039 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1040 |8114 41D5 18AB 4A1B ... | 1041 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1043 Figure 23 1045 Authors' Addresses 1047 Andrew Leung 1048 Sony Corporation 1049 6-7-35 Kitashinagawa 1050 Shinagawa-ku 1051 Tokyo 141-0001 1052 Japan 1054 Phone: +81 3 5448 2125 1055 Email: andrew@ualberta.net 1056 URI: http://www.sony.com/ 1058 Satoshi Futemma 1059 Sony Corporation 1060 6-7-35 Kitashinagawa 1061 Shinagawa-ku 1062 Tokyo 141-0001 1063 Japan 1065 Phone: +81 3 5448 2125 1066 Email: satosi-f@sm.sony.co.jp 1067 URI: http://www.sony.com/ 1069 Eisaburo Itakura 1070 Sony Corporation 1071 6-7-35 Kitashinagawa 1072 Shinagawa-ku 1073 Tokyo 141-0001 1074 Japan 1076 Phone: +81 3 5448 2125 1077 Email: itakura@sm.sony.co.jp 1078 URI: http://www.sony.com/ 1080 Intellectual Property Statement 1082 The IETF takes no position regarding the validity or scope of any 1083 Intellectual Property Rights or other rights that might be claimed to 1084 pertain to the implementation or use of the technology described in 1085 this document or the extent to which any license under such rights 1086 might or might not be available; nor does it represent that it has 1087 made any independent effort to identify any such rights. Information 1088 on the procedures with respect to rights in RFC documents can be 1089 found in BCP 78 and BCP 79. 1091 Copies of IPR disclosures made to the IETF Secretariat and any 1092 assurances of licenses to be made available, or the result of an 1093 attempt made to obtain a general license or permission for the use of 1094 such proprietary rights by implementers or users of this 1095 specification can be obtained from the IETF on-line IPR repository at 1096 http://www.ietf.org/ipr. 1098 The IETF invites any interested party to bring to its attention any 1099 copyrights, patents or patent applications, or other proprietary 1100 rights that may cover technology that may be required to implement 1101 this standard. Please address the information to the IETF at 1102 ietf-ipr@ietf.org. 1104 Disclaimer of Validity 1106 This document and the information contained herein are provided on an 1107 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 1108 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 1109 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 1110 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 1111 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 1112 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1114 Copyright Statement 1116 Copyright (C) The Internet Society (2006). This document is subject 1117 to the rights, licenses and restrictions contained in BCP 78, and 1118 except as set forth therein, the authors retain all their rights. 1120 Acknowledgment 1122 Funding for the RFC Editor function is currently provided by the 1123 Internet Society.