idnits 2.17.1 draft-ietf-avt-rtp-jpeg2000-beam-01.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.2b on line 19. -- Found old boilerplate from RFC 3978, Section 5.5 on line 1051. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 1028. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 1035. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 1041. ** The document has an RFC 3978 Section 5.2(b) Derivative Works Limitation clause. ** 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 : ---------------------------------------------------------------------------- == There are 4 instances of lines with non-RFC2606-compliant FQDNs in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: If the mh_id field is set to 0, the receiver MUST not save the main header and MUST NOT compensate for lost headers. -- 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 (July 18, 2005) is 6858 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: '4' is defined on line 648, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. '2' ** Obsolete normative reference: RFC 2327 (ref. '5') (Obsoleted by RFC 4566) Summary: 5 errors (**), 0 flaws (~~), 5 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: January 19, 2006 E. Itakura 5 Sony 6 July 18, 2005 8 Enhanced Payload Format for Priority & Header Processing RTP Payload 9 Format for JPEG 2000 Video Streams BEAM extension 10 draft-ietf-avt-rtp-jpeg2000-beam-01 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. 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 January 19, 2006. 39 Copyright Notice 41 Copyright (C) The Internet Society (2005). 43 Abstract 45 This memo describes extended uses for payload header in RFCXXXY, An 46 RTP Payload Format for JPEG 2000 Video, for better support of JPEG 47 2000 features such as scalability and includes a main header recovery 48 method. 50 This memo MUST be accompanied with an implementation of RFCXXXY for a 51 complete implementation. RFCXXXY itself is a complete description of 52 the payload header and signaling, this document only describes 53 additional processing for the payload header. There is an additional 54 MIME and SDP marker signaling for implementations of this document. 56 Table of Contents 58 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 59 1.1 History . . . . . . . . . . . . . . . . . . . . . . . . . 3 60 1.2 Description of the Mechanisms . . . . . . . . . . . . . . 3 61 1.2.1 Main Header Compensation . . . . . . . . . . . . . . . 3 62 1.2.2 Priority Table . . . . . . . . . . . . . . . . . . . . 3 63 1.3 Conventions Used in This Document . . . . . . . . . . . . 4 64 2. Payload Format Enhanced Processing . . . . . . . . . . . . . . 5 65 2.1 Enhanced Processing Markers . . . . . . . . . . . . . . . 5 66 3. Priority Mapping Table . . . . . . . . . . . . . . . . . . . . 7 67 3.1 Pre-Defined Priority Mapping . . . . . . . . . . . . . . . 7 68 3.1.1 Packet Number Based Ordering . . . . . . . . . . . . . 7 69 3.1.2 Progression Based Ordering . . . . . . . . . . . . . . 7 70 3.1.3 Layer Based Ordering . . . . . . . . . . . . . . . . . 8 71 3.1.4 Resolution Based Ordering . . . . . . . . . . . . . . 9 72 3.1.5 Component Based Ordering . . . . . . . . . . . . . . . 9 73 3.2 Application Specific Priority Table . . . . . . . . . . . 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. IANA Consideration . . . . . . . . . . . . . . . . . . . . . . 13 79 6.1 MIME Registration . . . . . . . . . . . . . . . . . . . . 13 80 6.2 SDP Parameters . . . . . . . . . . . . . . . . . . . . . . 14 81 7. Usage with the SDP Offer/Answer Model . . . . . . . . . . . . 15 82 7.1 Examples . . . . . . . . . . . . . . . . . . . . . . . . . 15 83 7.1.1 Example 1 . . . . . . . . . . . . . . . . . . . . . . 15 84 7.1.2 Example 2 . . . . . . . . . . . . . . . . . . . . . . 16 85 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17 86 8.1 Normative References . . . . . . . . . . . . . . . . . . . 17 87 8.2 Informative References . . . . . . . . . . . . . . . . . . 17 88 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 17 89 A. Sample Headers in Detail . . . . . . . . . . . . . . . . . . . 19 90 Intellectual Property and Copyright Statements . . . . . . . . 27 92 1. Introduction 94 This document is an extension of RFCXXXY, An RTP Payload Format for 95 JPEG 2000 Video. There are additional mechanisms to be used with 96 certain parts of the header in RFCXXXY to support JPEG 2000 features 97 such as scalability and a main header recovery method. These 98 mechanisms are described in detail in this document. 100 1.1 History 102 In the development of RFCXXXY, Sony Corporation filed a patent 103 application on certain mechanisms with the main header recovery, 104 priority table usage, etc. in RFCXXXY. As these are not "essential" 105 to the core RTP format of RFCXXXY and only describes a mechanism, it 106 was decided that splitting these mechanisms from the core RTP format 107 (essentially IPR free) into another document (IPR). This is the 108 document describing the IPR related mechanisms for main header 109 recover, priority table usage, etc. 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 A recovery of the main header that has been lost is very simple with 123 this procedure. In the case of JPEG 2000 video, it is common that 124 encode parameters will not vary greatly between each successive 125 frame. Even if the RTP packet including the main header of a frame 126 has been dropped, decoding may be performed by using the main header 127 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: 141 layer, component, resolution level, and/or precinct. The order in 142 which these JPEG 2000 packets are found in the codestream is called: 143 progression order. The ordering of the JPEG 2000 packets can 144 progress along four axes: layer, component, resolution and precinct 145 (or position). 147 Providing a priority field to indicate the importance of data 148 contained in a given RTP packet can aid in usage of JPEG 2000 149 progressive and scalable functions. 151 1.3 Conventions Used in This Document 153 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 154 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 155 document are to be interpreted as described in RFC2119 [1]. 157 2. Payload Format Enhanced Processing 159 2.1 Enhanced Processing Markers 161 This section of the document describes changes in the value of mh_id 162 and priority value and interpretation which differ from RFCXXXY. 163 Implementions of this document should follow protocol in RFCXXXY 164 first then add in additional header processing as described in this 165 document. Implementations following this document are expected to 166 seamlessly work with implementations of RFCXXXY and this document as 167 well. 169 The RTP payload header format for JPEG 2000 video stream is as 170 follows: 172 0 1 2 3 173 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 174 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 175 |tp |MHF|mh_id|T| priority | tile number | 176 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 177 |reserved | fragment offset | 178 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 180 Figure 1: RTP payload header format for JPEG 2000 182 mh_id (Main Header Identification) : 3 bits 184 Main header identification value. This is used for JPEG 2000 main 185 header recovery. 187 The same mh_id value is used as long as the coding parameters 188 described in the main header remains unchanged between frames. 190 The initial value of mh_id is random, and may take any value 191 between 1-7, but MUST NOT be 0. 193 The mh_id value MUST increment by 1 every time a new main header 194 is transmitted. Once the mh_id value is greater than 7, it rolls 195 over to 1. 197 When mh_id is 0, it has special usage for the receiver. This 198 special usage is described in Section 4.2 of this document. 200 Senders should follow Section 4.1 of this document for proper 201 mh_id usage. 203 priority : 8 bits 205 The priority field indicates the importance of the JPEG 2000 206 packet included in the payload. Typically, a higher priority is 207 set in the packets containing JPEG 2000 packets containing the 208 lower sub-bands. 210 Special values of priority: 212 0: This is reserved for payload which contain a header (main or 213 tile part header.) This is considered the highest importance. 215 1 to 255: These values decrease in importance as the values 216 increase. (i.e. 1 is more important than 2, etc.) Hence 217 applying priority values should correlate directly to JPEG 2000 218 codestream in importance in basic usage. 220 The lower the priority value is the higher the priority. Simply, 221 the priority value 0 is the highest priority and 255 is the lowest 222 priority. We define the priority value 0 as a special priority 223 value for the headers (the main header or tile-part header). When 224 any headers (the main header or tile-part header) are packed into 225 the RTP packet, the sender MUST set the priority value to 0. 227 Assignment of the values are described in Section 3 with pre- 228 defined table assignments in Section 3.1. 230 3. Priority Mapping Table 232 For the progression order, the priority value for each JPEG 2000 233 packet is given by the priority mapping table. 235 3.1 Pre-Defined Priority Mapping 237 This document specify several commonly-used priority mapping tables, 238 pre-defined priority mapping tables: packet number based (default), 239 progression-based, layer-based, resolution-based, component-based. 241 Packet number priority mapping is REQUIRED to be supported by clients 242 implementing this specification. Other priority mapping tables 243 (progression, layer, resolution, and component based) are OPTIONAL to 244 implementations of this specification. 246 Rules that all implementations of this specification MUST follow in 247 all priority modes: 249 o When there is a header in the packet with a JPEG 2000 packet, the 250 sender MUST set the payload packet priority value to 0. 252 o When there are multiple JPEG 2000 packets in the same RTP payload 253 packet, the sender MUST set the payload packet priority value to 254 the lowest priority value of the lowest JPEG 2000 packet. (i.e. if 255 JPEG 2000 packets with priority: 5,6,7 are packed into a single 256 payload, the priority value MUST be 5.) 258 3.1.1 Packet Number Based Ordering 260 This is the default mode for payload packet priority value and all 261 implementation of this specification MUST support. 263 The sender will have a one-to-one association between payload packet 264 priority value and the payload packet value (i.e. the JPEG 2000 265 codestream.) The RTP packet value is equal to the JPEG 2000 packet 266 value. 268 If the packet value of JPEG 2000 codestream is greater than 255, the 269 sender MUST set the payload priority value to 255. 271 3.1.2 Progression Based Ordering 273 The sender will assign the payload packet priority value only based 274 on layer, resolution, and component ordering of the codestream. 276 This is similar to the JPEG 2000 packet number based format but will 277 not take into account the precinct number or position in the JPEG 278 2000 codestream. 280 For example: 282 If the codestream is ordered in LRCP (Layer, Resolution, Component, 283 Position) 285 All the packets in: 287 layer 0 288 resolution 0 289 component 0 291 then the packet priority value : 1 293 All the packets in: 295 layer 0 296 resolution 0 297 component 1 299 then the packet priority value : 2 301 All the packets in: 303 layer 0 304 resolution 0 305 component 2 307 then the packet priority value : 3 309 3.1.3 Layer Based Ordering 311 Layer-based priority mapping table simplifies the default mapping to 312 just matching JPEG 2000 packets together from the same layer. 314 For example: 316 All the packets in layer 0 : packet priority value : 1 317 All the packets in layer 1 : packet priority value : 2 318 All the packets in layer 2 : packet priority value : 3 319 ... 320 All the packets in layer n : packet priority value : n+1 322 3.1.4 Resolution Based Ordering 324 Resolution-based priority mapping table is similar to the layer based 325 order but for JPEG 2000 packets of the same resolution 327 For example: 329 All the packets in resolution 0 : packet priority value : 1 330 All the packets in resolution 1 : packet priority value : 2 331 All the packets in resolution 2 : packet priority value : 3 332 ... 333 All the packets in resolution n : packet priority value : n+1 335 3.1.5 Component Based Ordering 337 Component-based priority mapping table is mapping together JPEG 2000 338 components of the same component 340 For example: 342 All the packets in component 0 : packet priority value : 1 343 All the packets in component 1 : packet priority value : 2 344 All the packets in component 2 : packet priority value : 3 345 ... 346 All the packets in component n : packet priority value : n+1 348 3.2 Application Specific Priority Table 350 The application specific priority table specification is intended for 351 experimental use as new applications and new priority mapping tables 352 are developed. 354 A case sensitive 8 character ASCII code describing the application 355 specific priority mapping name. The description of these application 356 specific priority tables are outside the scope of this document. 358 This extension may be used when the codestream is divided into many 359 layers and many resolutions. 361 4. JPEG 2000 Main Header Compensation Scheme 363 The mh_id field of the payload header is used to recognize whether 364 the encoding parameters of the main header are the same as the 365 encoding parameters of the previous frame. The same value is set in 366 mh_id of the RTP packet in the same frame. The mh_id and encode 367 parameters are not associated with each other as 1:1 but they are 368 used to recognize whether the encode parameters of the previous frame 369 are the same or not in the event of a lost header. 371 The mh_id field value SHOULD be saved from previous frames to be used 372 to recover the current frame's main header. If the mh_id of the 373 current frame has the same value as the mh_id value of the previous 374 frame, the previous frame's main header MAY be used to decode the 375 current frame, in case of a lost header in the current frame. 377 The sender MUST increment mh_id when parameters in the header change 378 and send a new main header accordingly. 380 The receiver MAY use the mh_id and MAY retain the header for such 381 compensation. 383 4.1 Sender Processing 385 The sender MUST transmit RTP packets with the same mh_id value unless 386 the encoder parameters are different from the previous frame. The 387 encoding parameters are the fixed information marker segment (SIZ 388 marker) and functional marker segments (COD, COC, RGN, QCD, QCC, and 389 POC) specified in JPEG 2000 Part 1 Annex A [2]. An initial value of 390 mh_id MUST be selected randomly between 1 and 7 for security reasons. 392 If the encode parameters changes, the sender transmitting RTP packets 393 MUST increment the mh_id value by one, but when mh_id value becomes 394 greater than 7, a sender MUST set mh_id value to 1. 396 4.2 Receiver Processing 398 When the receiver receives the main header completely, the RTP 399 sequence number, the mh_id and main header should be saved. Only the 400 last main header that was received completely SHOULD be saved. When 401 the mh_id value is 0, the receiver SHOULD NOT save the header. 403 When the main header is not received, the receiver may compare the 404 current payload header's mh_id value with the previous saved mh_id 405 value. If the values match, decoding may be performed by using the 406 previously saved main header. 408 If the mh_id field is set to 0, the receiver MUST not save the main 409 header and MUST NOT compensate for lost headers. 411 5. Security Consideration 413 RTP packets using the payload format defined in this specification 414 are subject to the security considerations discussed in the RTP 415 specifications[3] and any applicable profile. This implies that 416 confidentiality of the media streams is achieved by encryption. Data 417 compression used with this payload format is applied end-to-end, 418 encryption may be performed on the compressed data so there is no 419 conflict between the two operations. 421 A potential denial-of-service threat exists for data encodings using 422 compression techniques that have non-uniform receiver-end 423 computational load. The attacker can inject pathological datagrams 424 into the stream which are complex to decode and cause the receiver to 425 be overloaded. The usage of authentication of at least the RTP 426 packet is RECOMMENDED, for example with SRTP [2]. 428 If QoS enhanced service is used, RTP receivers SHOULD monitor packet 429 loss to ensure that the service that was requested is actually being 430 delivered. If it is not, then they SHOULD assume that they are 431 receiving best-effort service and behave accordingly. 433 If best-effort service is being used, users of this payload format 434 MUST monitor packet loss to ensure that the packet loss rate is 435 within acceptable parameters. Packet loss is considered acceptable 436 if a TCP flow across the same network path, experiencing the same 437 network conditions, would achieve an average throughput, measured on 438 a reasonable timescale, that is not less than the RTP flow is 439 achieving. This condition can be satisfied by implementing 440 congestion control mechanisms to adapt the transmission rate (or the 441 number of layers subscribed for a layered multicast session), or by 442 arranging for a receiver to leave the session if the loss rate is 443 unacceptably high. 445 As with any IP-based protocol, in some circumstances a receiver may 446 be overloaded simply by receiving too many packets, either desired or 447 undesired. Network-layer authentication may be used to discard 448 packets from undesired sources, but the processing cost of the 449 authentication itself may be too high. In a multicast environment, 450 pruning of specific sources may be implemented in future versions of 451 IGMP [7] and in multicast routing protocols to allow a receiver to 452 select which sources are allowed to reach it. 454 6. IANA Consideration 456 6.1 MIME Registration 458 This document defines a new RTP payload name and associated MIME 459 type, jpeg2000. 461 The receiver MUST ignore any unspecified parameter. 463 The MIME registration form for JPEG 2000 video stream is enclosed 464 below: 466 MIME media type name: video 468 MIME subtype name: jpeg2000 470 REQUIRED parameters: BEAM 472 'BEAM': Implmentations of this standard must include this option 473 in the parameter list when establishing a session. If this option 474 is supported, by the receiver/sender, both should reply with this 475 option in the MIME parameter list. If the answer omits this in 476 the MIME parameter list, the answerer does not support this option 478 Encoding considerations: 480 JPEG 2000 video stream may be transmitted with RTP as specified in 481 this document. 483 Security considerations: see section 9 of RFC AXXX. 485 Interoperability considerations: 487 JPEG 2000 video stream is a sequence of JPEG 2000 still images. 488 An implementation in compliant with [2] can decode and attempt to 489 display the encoded JPEG 2000 video stream. 491 Published specification: ISO/IEC 15444-1 | ITU-T Rec. T.800 493 Applications which use this media type: 495 video streaming and communication 497 Additional information: none 499 Magic number(s): none 501 File extension(s): none 502 Macintosh File Type Code(s): none 504 Person & email address to contact for further information: 506 Eisaburo Itakura, Satoshi Futemma 507 Email: {itakura|satosi-f}@sm.sony.co.jp 509 Intended usage: COMMON 511 Author/Change controller: 513 Eisaburo Itakura, Satoshi Futemma 514 Email: {itakura|satosi-f}@sm.sony.co.jp 516 6.2 SDP Parameters 518 In addition to SDP Parameters section in RFCXXXY: 520 The MIME media type video/jpeg2000 string is mapped to fields in the 521 Session Description Protocol (SDP) [5] as follows: 523 o The media name in the "m=" line of SDP MUST be video. 525 o The encoding name in the "a=rtpmap" line of SDP MUST be jpeg2000 526 (the MIME subtype). 528 o The clock rate in the "a=rtpmap" line MUST be 90000. 530 o The REQUIRED parameters "BEAM" MUST be included in the "a=fmtp" 531 line of SDP. 533 o The OPTIONAL parameters "priority-table-default", "priority-table- 534 definition", "priority-table-protocol", MUST be included in the 535 "a=fmtp" line of SDP. 537 These parameters are expressed as a MIME media type string, in the 538 form of a semicolon separated list of parameter=value pairs. 540 Therefore, an example of media representation in SDP is as follows: 542 m=video 49170/2 RTP/AVP 98 543 a=rtpmap:98 jpeg2000/90000 544 a=fmtp:98 BEAM;sampling=YCbCr-4:2:0;width=128;height=128 546 7. Usage with the SDP Offer/Answer Model 548 In addition to SDP Offer/Answer section in RFCXXXY: 550 When offering JPEG 2000 over RTP using SDP in an Offer/Answer model 551 [6], the following rules and limitations apply: 553 o All parameters MUST have an acceptable value for that parameter. 555 o All parameters MUST correspond to the parameters of the payload. 557 o The parameters "BEAM" MUST appear in the offer if the parameter 558 "BEAM" is not in the answer, receivers should not process the 559 header according to this document. Senders SHOULD continue to 560 send data with payload headers according to mechanisms outlined in 561 this document. This is highly recommended for multicast streams 562 where not all receivers are of the same type. 564 7.1 Examples 566 Offer/Answer example exchanges are provided. 568 7.1.1 Example 1 570 Alice offers BEAM functionality, YCbCr 422 color space, interlace 571 image with 720-pixel width and 480-pixel height and several priority- 572 table options (jp2-packet, progression, layer, resolution, component) 573 as below: 575 v=0 576 o=alice 2890844526 2890844526 IN IP4 host.anywhere.com 577 s= 578 c=IN IP4 host.anywhere.com 579 t=0 0 580 m=video 49170 RTP/AVP 98 581 a=rtpmap:98 jpeg2000/90000 582 a=fmtp:98 BEAM;sampling=YCbCr-4:2:2;interlace 583 a=fmtp:98 priority-table-definition=jp2-packet,progression,layer, 584 resolution,component; width=720; height=480 586 Bob accepts BEAM functionality, YCbCr-4:2:2 color space,interlace 587 image and jp2-packet based priority mapping (default mapping table) 588 and replies: 590 v=0 591 o=bob 2890844730 2890844731 IN IP4 host.example.com 592 s= 593 c=IN IP4 host.example.com 594 t=0 0 595 m=video 49920 RTP/AVP 98 596 a=rtpmap:98 jpeg2000/90000 597 a=fmtp:98 BEAM;sampling=YCbCr-4:2:2;interlace 599 Note that "priority-table-definition" parameter in Bob's answer is 600 omitted, so default priority mapping table (jp2-packet number based 601 priority mapping) is used. 603 7.1.2 Example 2 605 Alice offers YCbCr 420 color space, progressive image with 320-pixel 606 width and 240-pixel height and layer priority-table options as below: 608 v=0 609 o=alice 2890844526 2890844526 IN IP4 host.anywhere.com 610 s= 611 c=IN IP4 host.anywhere.com 612 t=0 0 613 m=video 49170 RTP/AVP 98 614 a=rtpmap:98 jpeg2000/90000 615 a=fmtp:98 BEAM;sampling=YCbCr-4:2:0 616 a=fmtp:98 priority-table-definition=layer; width=320; height=240 618 Bob does not accept BEAM functionality but accepts YCbCr-4:2:0 color 619 space,interlace image and layer based priority mapping and replies: 621 v=0 622 o=bob 2890844730 2890844731 IN IP4 host.example.com 623 s= 624 c=IN IP4 host.example.com 625 t=0 0 626 m=video 49920 RTP/AVP 98 627 a=rtpmap:98 jpeg2000/90000 628 a=fmtp:98 sampling=YCbCr-4:2:2 630 Note that "BEAM" parameter was not in Bob's answer so Alice must not 631 use settings described in this document for sending or receiving. 633 8. References 635 8.1 Normative References 637 [1] Bradner, "Key words for use in RFCs to Indicate Requirement 638 Levels", RFC 2119, March 1997. 640 [2] ISO/IEC JTC1/SC29, ISO/IEC 15444-1 | ITU-T Rec. T.800, 641 "Information Technology - JPEG 2000 Image Coding System - Part 642 1: Core Coding System", December 2000. 644 [3] Schulzrinne, Casner, Frederick, and Jacobson, "RTP: A Transport 645 Protocol for Real Time Applications", RFC 3550, STD 64, 646 July 2003. 648 [4] Baugher, McGrew, Naslund, Carrara, and Norrman, "The Secure 649 Real-time Transport Protocol (SRTP", RFC 3711, March 2004. 651 [5] Handley and Jacobson, "SDP: Session Description Protocol", 652 RFC 2327, April 1998. 654 [6] Rosenberg and Schulzrinne, "An Offer/Answer Model with Session 655 Description Protocol (SDP)", RFC 3264, June 2002. 657 8.2 Informative References 659 [7] Deering, "Host Extensions for IP Multicasting", RFC 1112, 660 August 1989. 662 Authors' Addresses 664 Andrew Leung 665 Sony Corporation 666 6-7-35 Kitashinagawa 667 Shinagawa-ku 668 Tokyo 141-0001 669 Japan 671 Phone: +81 3 5448 2125 672 Email: andrew.leung@jp.sony.com 673 URI: http://www.sony.com/ 674 Satoshi Futemma 675 Sony Corporation 676 6-7-35 Kitashinagawa 677 Shinagawa-ku 678 Tokyo 141-0001 679 Japan 681 Phone: +81 3 5448 2125 682 Email: satosi-f@sm.sony.co.jp 683 URI: http://www.sony.com/ 685 Eisaburo Itakura 686 Sony Corporation 687 6-7-35 Kitashinagawa 688 Shinagawa-ku 689 Tokyo 141-0001 690 Japan 692 Phone: +81 3 5448 2125 693 Email: itakura@sm.sony.co.jp 694 URI: http://www.sony.com/ 696 Appendix A. Sample Headers in Detail 698 0 1 2 3 699 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 700 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 701 |tp |MHF|mh_id|T| priority | tile number | 702 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 703 |reserved | fragment offset | 704 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 706 Figure 2 708 First Packet: This packet will have the whole main header. 210bytes 710 0 1 2 3 711 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 712 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 713 |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| 714 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 715 |0 0 0 0 0 0 0 0|0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0| 716 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 717 |FF4FFF51002F000 .... | 718 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 720 Figure 3 722 Second Packet: This packet will have a tile header and the first tile 723 part LLband 1500bytes 725 0 1 2 3 726 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 727 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 728 |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| 729 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 730 |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| 731 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 732 |FF90 000A 0000 0000 2DB3 0001 FF93 | 733 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 735 Figure 4 737 Third Packet: This packet will have the next part in the tile, no 738 tile header 1500bytes 740 0 1 2 3 741 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 742 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 743 |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| 744 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 745 |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| 746 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 747 |E841 4526 4556 9850 C2EA .... | 748 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 750 Figure 5 752 Fourth Packet: Last packet for the image 290bytes 754 0 1 2 3 755 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 756 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 757 |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| 758 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 759 |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| 760 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 761 |A55D 8B73 3B25 25C7 B9EB .... 2FBEB153| 762 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 764 Figure 6 766 First Packet: This packet will have the whole main header. 210bytes 768 0 1 2 3 769 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 770 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 771 |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| 772 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 773 |0 0 0 0 0 0 0 0|0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0| 774 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 775 |FF4FFF51002F000 .... | 776 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 778 Figure 7 780 Second Packet: This packet will have a first tile part (tile 0) 781 1400bytes 783 0 1 2 3 784 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 785 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 786 |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| 787 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 788 |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| 789 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 790 |FF90 000A 0000 0000 0578 0001 FF93 .... | 791 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 793 Figure 8 795 Third Packet: This packet will have a second tile part (tile 1) 796 1423bytes 798 0 1 2 3 799 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 800 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 801 |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| 802 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 803 |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| 804 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 805 |FF90 000A 0001 0000 058F 0001 FF93 .... | 806 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 808 Figure 9 810 Fourth Packet: This packet will have a third tile part (tile 2) 811 1355bytes 813 0 1 2 3 814 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 815 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 816 |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| 817 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 818 |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| 819 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 820 |FF90 000A 0002 0000 054B 0001 FF93 .... | 821 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 823 Figure 10 825 Fifth Packet: This packet will have a fourth tile part (tile 3) 826 1290bytes 828 0 1 2 3 829 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 830 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 831 |0 0|0 0|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| 832 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 833 |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| 834 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 835 |FF90 000A 0003 0000 050A 0001 FF93 .... | 836 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 838 Figure 11 840 First Packet: This packet will have the first part of the main 841 header. 110bytes 843 0 1 2 3 844 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 845 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 846 |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| 847 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 848 |0 0 0 0 0 0 0 0|0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0| 849 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 850 |FF4FFF51002F000 .... | 851 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 853 Figure 12 855 Second Packet: This packet has the second part of the header. 856 1400bytes 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|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| 862 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 863 |0 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| 864 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 865 |FF6400FF .... | 866 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 868 Figure 13 870 Third Packet: This packet has two tiles, tile 0 and tile 1 1400bytes 872 0 1 2 3 873 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 874 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 875 |0 0|0 0|0 0 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| 876 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 877 |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| 878 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 879 |FF90 000A 0000 0000 02BC 0001 FF93 ... | 880 |FF90 000A 0001 0000 02BC 0001 FF93 ... | 881 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 883 Figure 14 885 Fourth Packet: This packet has one tile, tile 2 1395bytes 887 0 1 2 3 888 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 889 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 890 |0 0|0 0|0 0 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| 891 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 892 |0 0 0 0 0 0 0 0|0 0 0 0 0 0 0 0 0 0 0 0 1 0 1 1 0 1 0 1 1 1 1 0| 893 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 894 |FF90 000A 0002 0000 0573 0001 FF93 .... | 895 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 897 Figure 15 899 First packet: This packet will have the whole main header for the odd 900 field 210bytes 902 0 1 2 3 903 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 904 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 905 |0 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| 906 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 907 |0 0 0 0 0 0 0 0|0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0| 908 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 909 |FF4FFF51002F000 .... | 910 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 912 Figure 16 914 Second packet: This packet will have the first part of the odd 915 field's tile 1400bytes 917 0 1 2 3 918 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 919 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 920 |0 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| 921 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 922 |0 0 0 0 0 0 0 0|0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 1 0 0 1 0| 923 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 924 |FF90 000A 0000 0000 0578 0001 FF93 .... | 925 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 927 Figure 17 929 Third packet: This packet will have the second part of the odd 930 field's tile 1400bytes 932 0 1 2 3 933 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 934 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 935 |0 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| 936 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 937 |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| 938 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 939 |7F04 E708 27D9 D11D 22CB ... | 940 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 942 Figure 18 944 Fourth packet: This packet will have the third part of the odd 945 field's tile 1300bytes 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 |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| 951 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 952 |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| 953 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 954 |98BD EC9B 2826 DC62 D4AB ... | 955 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 957 Figure 19 959 Fifth packet: This packet will have the whole main header for the 960 even field 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|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| 966 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 967 |0 0 0 0 0 0 0 0|0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0| 968 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 969 |FF4FFF51002F000 .... | 970 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 972 Figure 20 974 Sixth packet: This packet will have the first part of the odd field's 975 tile 1400bytes 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 |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| 981 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 982 |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| 983 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 984 |FF90 000A 0000 0000 0578 0001 FF93 .... | 985 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 987 Figure 21 989 Seventh packet: This packet will have the second part of the odd 990 field's tile 1400bytes 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 |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| 996 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 997 |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| 998 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 999 |626C 42F0 166B 6BD0 F8E1 ... | 1000 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1002 Figure 22 1004 Eighth packet: This packet will have the third part of the odd 1005 field's tile 1300bytes 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 |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| 1011 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1012 |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| 1013 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1014 |8114 41D5 18AB 4A1B ... | 1015 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1017 Figure 23 1019 Intellectual Property Statement 1021 The IETF takes no position regarding the validity or scope of any 1022 Intellectual Property Rights or other rights that might be claimed to 1023 pertain to the implementation or use of the technology described in 1024 this document or the extent to which any license under such rights 1025 might or might not be available; nor does it represent that it has 1026 made any independent effort to identify any such rights. Information 1027 on the procedures with respect to rights in RFC documents can be 1028 found in BCP 78 and BCP 79. 1030 Copies of IPR disclosures made to the IETF Secretariat and any 1031 assurances of licenses to be made available, or the result of an 1032 attempt made to obtain a general license or permission for the use of 1033 such proprietary rights by implementers or users of this 1034 specification can be obtained from the IETF on-line IPR repository at 1035 http://www.ietf.org/ipr. 1037 The IETF invites any interested party to bring to its attention any 1038 copyrights, patents or patent applications, or other proprietary 1039 rights that may cover technology that may be required to implement 1040 this standard. Please address the information to the IETF at 1041 ietf-ipr@ietf.org. 1043 Disclaimer of Validity 1045 This document and the information contained herein are provided on an 1046 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 1047 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 1048 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 1049 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 1050 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 1051 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1053 Copyright Statement 1055 Copyright (C) The Internet Society (2005). This document is subject 1056 to the rights, licenses and restrictions contained in BCP 78, and 1057 except as set forth therein, the authors retain all their rights. 1059 Acknowledgment 1061 Funding for the RFC Editor function is currently provided by the 1062 Internet Society.