Network Working Group S. Futemma
Request for Comments: 5371 E. Itakura
Category: Standards Track A. Leung
Sony
October 2008
Network Working Group S. Futemma
Request for Comments: 5371 E. Itakura
Category: Standards Track A. Leung
Sony
October 2008
RTP Payload Format for JPEG 2000 Video Streams
JPEG 2000视频流的RTP有效负载格式
Status of This Memo
关于下段备忘
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
本文件规定了互联网社区的互联网标准跟踪协议，并要求进行讨论和提出改进建议。有关本协议的标准化状态和状态，请参考当前版本的“互联网官方协议标准”（STD 1）。本备忘录的分发不受限制。
Abstract
摘要
This memo describes an RTP payload format for the ISO/IEC International Standard 15444-1 | ITU-T Rec. T.800, better known as JPEG 2000. JPEG 2000 features are considered in the design of this payload format. JPEG 2000 is a truly scalable compression technology allowing applications to encode once and decode many different ways. The JPEG 2000 video stream is formed by extending from a single image to a series of JPEG 2000 images.
本备忘录描述了ISO/IEC国际标准15444-1 | ITU-T Rec.T.800（也称为JPEG 2000）的RTP有效载荷格式。在设计这种有效载荷格式时考虑了JPEG 2000特性。JPEG 2000是一种真正可伸缩的压缩技术，允许应用程序以一次编码和多种不同方式解码。JPEG 2000视频流通过从单个图像扩展到一系列JPEG 2000图像而形成。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Conventions Used in This Document . . . . . . . . . . . . 6
2. JPEG 2000 Video Features . . . . . . . . . . . . . . . . . . . 6
3. Payload Design . . . . . . . . . . . . . . . . . . . . . . . . 6
4. Payload Format . . . . . . . . . . . . . . . . . . . . . . . . 7
4.1. RTP Fixed Header Usage . . . . . . . . . . . . . . . . . . 7
4.2. RTP Payload Header Format . . . . . . . . . . . . . . . . 8
5. RTP Packetization . . . . . . . . . . . . . . . . . . . . . . 10
6. Media Type Registration . . . . . . . . . . . . . . . . . . . 11
7. SDP Parameters . . . . . . . . . . . . . . . . . . . . . . . . 14
7.1. SDP Mapping . . . . . . . . . . . . . . . . . . . . . . . 14
7.2. Usage with the SDP Offer/Answer Model . . . . . . . . . . 15
7.2.1. Examples . . . . . . . . . . . . . . . . . . . . . . . 16
7.2.2. Examples: Non-90kHz Timestamp . . . . . . . . . . . . 16
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17
9. Security Considerations . . . . . . . . . . . . . . . . . . . 17
10. Congestion Control . . . . . . . . . . . . . . . . . . . . . . 18
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19
11.1. Normative References . . . . . . . . . . . . . . . . . . . 19
11.2. Informative References . . . . . . . . . . . . . . . . . . 19
Appendix A. Informative Appendix . . . . . . . . . . . . . . . . 21
A.1. Recommended Practices . . . . . . . . . . . . . . . . . . 21
A.2. Sample Headers in Detail . . . . . . . . . . . . . . . . . 22
A.2.1. Sample 1: Progressive Image with Single Tile, 3500
Bytes (i.e., thumbnail) . . . . . . . . . . . . . . . 22
A.2.2. Sample 2: Image with 4 Tiles . . . . . . . . . . . . . 24
A.2.3. Sample 3: Packing Multiple Tiles in Single
Payload, Fragmented Header . . . . . . . . . . . . . . 25
A.2.4. Sample 4: Interlace Image, Single Tile . . . . . . . . 27
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Conventions Used in This Document . . . . . . . . . . . . 6
2. JPEG 2000 Video Features . . . . . . . . . . . . . . . . . . . 6
3. Payload Design . . . . . . . . . . . . . . . . . . . . . . . . 6
4. Payload Format . . . . . . . . . . . . . . . . . . . . . . . . 7
4.1. RTP Fixed Header Usage . . . . . . . . . . . . . . . . . . 7
4.2. RTP Payload Header Format . . . . . . . . . . . . . . . . 8
5. RTP Packetization . . . . . . . . . . . . . . . . . . . . . . 10
6. Media Type Registration . . . . . . . . . . . . . . . . . . . 11
7. SDP Parameters . . . . . . . . . . . . . . . . . . . . . . . . 14
7.1. SDP Mapping . . . . . . . . . . . . . . . . . . . . . . . 14
7.2. Usage with the SDP Offer/Answer Model . . . . . . . . . . 15
7.2.1. Examples . . . . . . . . . . . . . . . . . . . . . . . 16
7.2.2. Examples: Non-90kHz Timestamp . . . . . . . . . . . . 16
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17
9. Security Considerations . . . . . . . . . . . . . . . . . . . 17
10. Congestion Control . . . . . . . . . . . . . . . . . . . . . . 18
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19
11.1. Normative References . . . . . . . . . . . . . . . . . . . 19
11.2. Informative References . . . . . . . . . . . . . . . . . . 19
Appendix A. Informative Appendix . . . . . . . . . . . . . . . . 21
A.1. Recommended Practices . . . . . . . . . . . . . . . . . . 21
A.2. Sample Headers in Detail . . . . . . . . . . . . . . . . . 22
A.2.1. Sample 1: Progressive Image with Single Tile, 3500
Bytes (i.e., thumbnail) . . . . . . . . . . . . . . . 22
A.2.2. Sample 2: Image with 4 Tiles . . . . . . . . . . . . . 24
A.2.3. Sample 3: Packing Multiple Tiles in Single
Payload, Fragmented Header . . . . . . . . . . . . . . 25
A.2.4. Sample 4: Interlace Image, Single Tile . . . . . . . . 27
This document specifies a payload format for JPEG 2000 video streams over the Real-time Transport Protocol (RTP). JPEG 2000 is an ISO/IEC International Standard and ITU-T Recommendation (ISO/IEC International Standard 15444-1 | ITU-T Rec. T.800) developed for next-generation, still-image compression. JPEG stands for the Joint Photographers Experts Group, an international group made of academia and industry to develop image compression standards. JPEG 2000 basic compression technology is defined in detail in ISO JPEG 2000 Part 1: Core Coding System [JPEG2000Pt_1], with motion defined in ISO JPEG 2000 Part 3: Motion JPEG 2000 [JPEG2000Pt_3].
本文档通过实时传输协议（RTP）为JPEG 2000视频流指定有效负载格式。JPEG 2000是为下一代静止图像压缩而开发的ISO/IEC国际标准和ITU-T建议（ISO/IEC国际标准15444-1 | ITU-T Rec.T.800）。JPEG代表联合摄影师专家组，这是一个由学术界和工业界组成的国际组织，旨在制定图像压缩标准。JPEG 2000基本压缩技术在ISO JPEG 2000第1部分：核心编码系统[JPEG2000Pt_1]中有详细定义，运动在ISO JPEG 2000第3部分：运动JPEG 2000[JPEG2000Pt_3]中有定义。
Part 3 of the JPEG 2000 standard defines Motion JPEG 2000 [JPEG2000Pt_3]. However, Motion JPEG 2000 defines a file format, not a transmission format for the network. This document specifies a transmission format for the network for a series of JPEG 2000 images.
JPEG 2000标准的第3部分定义了运动JPEG 2000[JPEG2000Pt_3]。但是，Motion JPEG 2000定义的是文件格式，而不是网络传输格式。本文档指定了一系列JPEG 2000图像的网络传输格式。
JPEG 2000 supports many powerful features [JPEG2000Pt_1] [JPEG2000Pt_3] that are not supported in the current JPEG standard, such as:
JPEG 2000支持许多当前JPEG标准不支持的强大功能[JPEG2000Pt_1][JPEG2000Pt_3]，例如：
o Higher compression efficiency than JPEG with less visual distortion especially at extreme compression ratios.
o 与JPEG相比，压缩效率更高，视觉失真更小，尤其是在极端压缩比下。
o A single codestream that offers both lossy and lossless compression.
o 提供有损和无损压缩的单个码流。
o Better error resiliency than JPEG.
o 比JPEG具有更好的错误恢复能力。
o Progressive transmission by pixel accuracy (Signal-to-Noise Ratio (SNR) scalability) and resolution (resolution scalability).
o 通过像素精度（信噪比（SNR）可伸缩性）和分辨率（分辨率可伸缩性）渐进传输。
o Random codestream access and processing.
o 随机码流访问和处理。
The JPEG 2000 algorithm is briefly explained. Figure 1 shows a block diagram of the JPEG 2000 encoding method.
简要说明了JPEG2000算法。图1显示了JPEG2000编码方法的框图。
+-----+
| ROI |
+-----+
|
V
+----------+ +----------+ +------------+
|DC, comp. | | Wavelet | | |
Raw Image ==> |transform-|==>|transform-|==>|Quantization|==+
| ation | | ation | | | |
+----------+ +----------+ +------------+ |
|
+-----------+ +----------+ +------------+ |
| | | | | | |
JPEG 2000 <==| Data |<==| Rate |<==| EBCOT |<=+
codestream | Ordering | | Control | | |
+-----------+ +----------+ +------------+
+-----+
| ROI |
+-----+
|
V
+----------+ +----------+ +------------+
|DC, comp. | | Wavelet | | |
Raw Image ==> |transform-|==>|transform-|==>|Quantization|==+
| ation | | ation | | | |
+----------+ +----------+ +------------+ |
|
+-----------+ +----------+ +------------+ |
| | | | | | |
JPEG 2000 <==| Data |<==| Rate |<==| EBCOT |<=+
codestream | Ordering | | Control | | |
+-----------+ +----------+ +------------+
Figure 1: Block diagram of the JPEG 2000 encoder
图1:JPEG 2000编码器的框图
The image is first transformed into wavelet coefficients. The image is sampled into various levels, vertically and horizontally, from high frequencies (which contain sharp details) to low frequencies (which contain smooth areas). Quantization is performed on the coefficients within each sub-band.
首先将图像变换为小波系数。从高频（包含锐利细节）到低频（包含平滑区域），图像被垂直和水平采样到不同的级别。对每个子带内的系数执行量化。
After quantization, code blocks are formed from within the precincts within the tiles. (Precincts are a finer separation than tiles, and code blocks are the smallest separation of the image data.) EBCOT coding (Embedded Block Coding Optimized for Truncation) is performed within each code block and arithmetically encoded by bit plane. Rate control is performed to achieve the highest quality image for a specified rate.
量化后，代码块从瓷砖内的区域内形成。（选区是比分片更精细的分离，代码块是图像数据的最小分离。）EBCOT编码（针对截断优化的嵌入式块编码）在每个代码块内执行，并通过位平面进行算术编码。速率控制用于以指定速率获得最高质量的图像。
As a result, for a given tile, data units called JPEG 2000 packets are generated, which contain data from a specific layer, specific component, specific resolution, or specific precinct, depending on the data ordering.
因此，对于给定的磁贴，生成称为JPEG 2000数据包的数据单元，这些数据单元包含来自特定层、特定组件、特定分辨率或特定区域的数据，具体取决于数据顺序。
Finally, the JPEG 2000 packets are interleaved according to the progression along four axes: layer, resolution, component, and precinct. A JPEG 2000 header is added to become a fully compliant JPEG 2000 codestream.
最后，JPEG2000数据包根据沿四个轴（层、分辨率、分量和区域）的进程进行交织。添加JPEG 2000头以成为完全兼容的JPEG 2000码流。
To decompress a JPEG 2000 codestream, one would follow the reverse order of the encoding order, without the rate control.
要解压缩JPEG2000码流，将按照编码顺序的相反顺序进行，而不进行速率控制。
It is outside the scope of this document to further describe in detail this procedure. Please refer to various JPEG 2000 related texts for further details [JPEG2000Pt_1].
进一步详细描述本程序超出了本文件的范围。有关更多详细信息，请参阅各种JPEG 2000相关文本[JPEG2000Pt_1]。
Figure 2 shows a JPEG 2000 codestream in detail. A JPEG 2000 codestream is structured from the main header, beginning with the SOC (Start Of Codestream) marker, one or more tiles, and the EOC (End Of Codestream) marker to indicate the end of the codestream. Each tile consists of a tile-part header that starts with the SOT (Start of Tile) marker and ends with a SOD (Start of Data) marker, and bitstream (a series of JPEG 2000 packets).
图2详细显示了JPEG2000码流。JPEG 2000码流从主头部开始，以SOC（码流开始）标记、一个或多个分片和EOC（码流结束）标记表示码流结束。每个磁贴由一个磁贴部分标头组成，该标头以SOT（磁贴开始）标记开始，以SOD（数据开始）标记结束，并包含位流（一系列JPEG 2000数据包）。
+-- +------------+
Main | | SOC | Required as the first marker
header| +------------+
| | main | Main header marker segments
+-- +------------+
| | SOT | Required at the beginning of each
Tile- | +------------+ tile-part header
part | | T0,TP0 | Tile 0, tile-part 0 header marker
header| +------------+ segments
| | SOD | Required at the end of each tile-part
+-- +------------+ header
| bitstream | Tile-part bitstream
+-- +------------+
| | SOT |
Tile- | +------------+
part | | T1,TP0 |
header| +------------+
| | SOD |
+-- +------------+
| bit stream |
+------------+
.
.
.
+------------+
| EOC | Required as the last marker in the
+------------+ codestream
+-- +------------+
Main | | SOC | Required as the first marker
header| +------------+
| | main | Main header marker segments
+-- +------------+
| | SOT | Required at the beginning of each
Tile- | +------------+ tile-part header
part | | T0,TP0 | Tile 0, tile-part 0 header marker
header| +------------+ segments
| | SOD | Required at the end of each tile-part
+-- +------------+ header
| bitstream | Tile-part bitstream
+-- +------------+
| | SOT |
Tile- | +------------+
part | | T1,TP0 |
header| +------------+
| | SOD |
+-- +------------+
| bit stream |
+------------+
.
.
.
+------------+
| EOC | Required as the last marker in the
+------------+ codestream
Figure 2: Basic construction of the JPEG 2000 codestream
图2:JPEG2000码流的基本结构
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119[RFC2119]中所述进行解释。
JPEG 2000 video streams are formed as a continuous series of JPEG 2000 still images. Previously described features of JPEG 2000 may be used effectively in streaming applications for a JPEG 2000 video. A JPEG 2000 video stream has the following qualities:
JPEG 2000视频流形成为一系列连续的JPEG 2000静止图像。先前描述的JPEG 2000的特征可以有效地用于JPEG 2000视频的流应用中。JPEG 2000视频流具有以下质量：
o At low bit rates, the SNR is improved dramatically over JPEG and Motion JPEG.
o 在低比特率下，与JPEG和运动JPEG相比，信噪比显著提高。
o This is a full intra-frame format -- each frame is independently compressed -- and therefore has a low encoding and decoding delay.
o 这是一种完整的帧内格式——每个帧都是独立压缩的——因此具有较低的编码和解码延迟。
o JPEG 2000 has flexible and accurate rate control.
o JPEG 2000具有灵活准确的速率控制。
o This is suitable for traffic control and congestion control during network transmission.
o 这适用于网络传输期间的流量控制和拥塞控制。
o JPEG 2000 can provide its own codestream error resilience markers to aid in codestream recovery outside of this specification.
o JPEG 2000可以提供自己的码流错误恢复标记，以帮助在此规范之外的码流恢复。
To design a payload format that maximizes JPEG 2000 features, the following are taken into consideration:
要设计最大化JPEG 2000功能的有效载荷格式，应考虑以下因素：
o Provisions for packet loss:
o 丢包准备金：
On the Internet, 5% packet loss is common and this percentage may vary up to 20% or more. To split JPEG 2000 video streams into RTP packets, efficient packetization of the codestream is required to minimize problems in decoding due to missing packets. If the main header is lost, the image cannot be decoded.
在互联网上，5%的数据包丢失是很常见的，这个百分比可能会变化到20%或更多。为了将JPEG2000视频流分割成RTP数据包，需要对码流进行有效的打包，以尽量减少由于丢失数据包而导致的解码问题。如果主标题丢失，图像将无法解码。
o JPEG 2000 Scalability
o JPEG 2000可扩展性
JPEG 2000 has powerful scalability features and markers in the payload header to indicate the specific meaning of the payload, such as:
JPEG 2000在有效载荷标题中具有强大的可扩展性功能和标记，以指示有效载荷的特定含义，例如：
* Special markers for the headers, fragments of headers, etc.
* 标题、标题片段等的特殊标记。
* Tile numbering for association of packets.
* 数据包关联的磁贴编号。
* Since this is primarily for video applications, special markers are used to indicate format (i.e., interlace odd/even fields).
* 由于这主要用于视频应用，因此使用特殊标记来指示格式（即，交错奇偶场）。
* Priority importance of the packet using methods described in RFC 5372 [RFC5372].
* 使用RFC 5372[RFC5372]中所述方法的数据包的优先级重要性。
* Main header recovery using methods described in RFC 5372 [RFC5372].
* 使用RFC 5372[RFC5372]中描述的方法恢复主标头。
Additional usage of the payload header is described in RFC 5372 [RFC5372].
RFC 5372[RFC5372]中描述了有效负载标头的其他用途。
For each RTP packet, the RTP fixed header is followed by the JPEG 2000 RTP payload header, which is followed by the payload, a piece of a JPEG 2000 codestream, which is usually a JPEG 2000 packet.
对于每个RTP数据包，RTP固定报头之后是JPEG 2000 RTP有效载荷报头，该报头之后是有效载荷，即JPEG 2000码流的一段，通常是JPEG 2000数据包。
The RTP header fields that have a meaning specific to a JPEG 2000 video stream are described as follows:
具有特定于JPEG 2000视频流的含义的RTP报头字段描述如下：
Marker bit (M): The marker bit of the RTP fixed header MUST be set to 1 for the last RTP packet of a video frame; otherwise, it MUST be 0. When transmission is performed by multiple RTP sessions, this bit is 1 in the last packet of the frame in each session.
标记位（M）：对于视频帧的最后一个RTP数据包，RTP固定报头的标记位必须设置为1；否则，它必须为0。当由多个RTP会话执行传输时，该位在每个会话中帧的最后一个数据包中为1。
Payload type (PT): The payload type is dynamically assigned by means outside the scope of this document. A payload type in the dynamic range shall be chosen by means of an out-of-band signaling protocol (i.e., Real Time Streaming Protocol (RTSP), SIP, etc.).
有效负载类型（PT）：有效负载类型通过本文档范围之外的方式动态分配。应通过带外信令协议（即实时流协议（RTSP）、SIP等）选择动态范围内的有效负载类型。
Timestamp: Timestamp indicates the presentation time of the frame contained in the RTP packet. The same timestamp value MUST appear in each RTP packet carrying a fragment of a given frame. When a JPEG 2000 image is in interlace format, the odd field and the corresponding even field MUST have the same timestamp value. Following the RTP specification [RFC3550], the initial value of the timestamp should be randomly chosen.
Timestamp：Timestamp表示RTP数据包中包含的帧的显示时间。携带给定帧片段的每个RTP数据包中必须出现相同的时间戳值。当JPEG 2000图像为隔行扫描格式时，奇数字段和相应的偶数字段必须具有相同的时间戳值。按照RTP规范[RFC3550]，应随机选择时间戳的初始值。
As for the clock rate, senders and receivers MUST support the 90kHz RTP timestamp rate, and MAY support other rates. RTP timestamp rates below 1000 Hz SHOULD NOT be used because they will result in insufficient resolution for RTP Control Protocol (RTCP) measurements based on the RTP timestamp, such as the interarrival
至于时钟速率，发送方和接收方必须支持90kHz RTP时间戳速率，并且可以支持其他速率。不应使用低于1000 Hz的RTP时间戳速率，因为它们将导致基于RTP时间戳的RTP控制协议（RTCP）测量的分辨率不足，例如到达间隔
jitter. The clock rate MUST be negotiated at the start of the session. When using the Session Description Protocol (SDP), it MUST be expressed using the "rtpmap" attributes. If a non-90kHz clock rate is to be used, it is RECOMMENDED to present not only a preferable clock rate but also 90kHz clock rate with a different RTP payload type.
抖动。必须在会话开始时协商时钟速率。使用会话描述协议（SDP）时，必须使用“rtpmap”属性表示。如果要使用非90kHz的时钟频率，建议不仅提供优选的时钟频率，还提供具有不同RTP有效负载类型的90kHz时钟频率。
The RTP payload header format for JPEG 2000 video stream is as follows:
JPEG 2000视频流的RTP有效负载头格式如下：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|tp |MHF|mh_id|T| priority | tile number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|reserved | fragment offset |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|tp |MHF|mh_id|T| priority | tile number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|reserved | fragment offset |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 3: RTP payload header format for JPEG 2000
图3:JPEG 2000的RTP有效载荷头格式
tp (type): 2 bits
tp（类型）：2位
This field indicates how a JPEG 2000 image is scanned (progressive or interlace).
此字段指示如何扫描JPEG 2000图像（逐行扫描或隔行扫描）。
0: The payload is progressively scanned.
0：逐步扫描有效负载。
1: The payload is part of an odd field of an interlaced video frame. The height specified in the JPEG 2000 main header is half of the height of the entire displayed image. In a receiver, an odd field should be de-interlaced with the even field following it so that lines from each image are displayed alternately.
1：有效载荷是隔行扫描视频帧的奇数场的一部分。JPEG 2000主标题中指定的高度是整个显示图像高度的一半。在接收器中，奇数场应与其后的偶数场去隔行，以便交替显示来自每个图像的行。
2: The payload is part of an even field of an interlaced video signal.
2：有效载荷是隔行扫描视频信号的偶数场的一部分。
MHF (Main Header Flag): 2 bits
MHF（主标题标志）：2位
MHF indicates whether a main header or packet of a main header is in the RTP packet.
MHF指示主报头或主报头的数据包是否在RTP数据包中。
If there is no header, MHF has a value of 0. If there is just a part of a fragmented header, MHF has a value of 1. If there is the last part of a fragmented header, MHF has value of 2. If the whole header is in the packet, MHF has a value of 3.
如果没有标头，MHF的值为0。如果一个片段头只有一部分，那么MHF的值为1。如果存在分段标头的最后一部分，则MHF的值为2。如果整个报头在数据包中，MHF的值为3。
+-----------+----------------------------------+
| MHF Value | Description |
+-----------+----------------------------------+
| 0 | no main header in the payload |
| 1 | piece of fragmented header |
| 2 | last part of a fragmented header |
| 3 | a whole main header |
+-----------+----------------------------------+
+-----------+----------------------------------+
| MHF Value | Description |
+-----------+----------------------------------+
| 0 | no main header in the payload |
| 1 | piece of fragmented header |
| 2 | last part of a fragmented header |
| 3 | a whole main header |
+-----------+----------------------------------+
Table 1: MHF Usage Values
表1：MHF使用值
mh_id (Main Header Identification): 3 bits
mh_id（主标头标识）：3位
Main header identification value. This is used for JPEG 2000 main header recovery.
主标题标识值。这用于JPEG 2000主标题恢复。
For implementations following only this specification, the sender SHOULD set this value to 0 and the receiver SHOULD ignore this field on processing.
对于仅遵循此规范的实现，发送方应将此值设置为0，接收方应在处理时忽略此字段。
T (Tile field invalidation flag): 1 bit
T（平铺字段无效标志）：1位
The T bit indicates whether the tile number field is valid or invalid. A sender MUST set the T bit to 1 when invalid and 0 when valid.
T位指示平铺编号字段是否有效。发送方必须在无效时将T位设置为1，在有效时将T位设置为0。
There are two cases where the tile number field is invalid:
有两种情况下磁贴编号字段无效：
* When an RTP packet holds only the main header. A sender cannot set any number in the tile number field, as no JPEG 2000 tile-part bitstream is included in the RTP packet.
* 当RTP数据包仅包含主报头时。发送方不能在tile number字段中设置任何数字，因为RTP数据包中不包括JPEG 2000 tile部分比特流。
* Multiple tile-parts are packed together in a single payload. If there are multiple tiles packed into a single payload, there is no meaning to assign a number to the tile number field.
* 多个瓷砖部件打包在一个有效负载中。如果有多个磁贴打包到单个有效负载中，则没有意义为磁贴编号字段分配编号。
priority: 8 bits
优先级：8位
The priority field indicates the importance of the JPEG 2000 packet included in the payload. Typically, a higher priority value is set in the packets containing JPEG 2000 packets that contain the lower sub-bands.
优先级字段指示有效载荷中包括的JPEG 2000分组的重要性。通常，在包含较低子带的JPEG 2000包的包中设置较高的优先级值。
For implementations following only this specification, the sender SHOULD set this value to 255 and the receiver SHOULD ignore this field on processing.
对于仅遵循此规范的实现，发送方应将此值设置为255，接收方应在处理时忽略此字段。
tile number: 16 bits
磁贴编号：16位
This field shows the tile number of the payload. This field is only valid when the T bit is 0. If the T bit is set to 1, the receiver MUST ignore this field.
此字段显示有效负载的磁贴编号。此字段仅在T位为0时有效。如果T位设置为1，接收器必须忽略此字段。
R (Reserved): 8 bits
R（保留）：8位
This bit is reserved for future use. Senders MUST set this to 0. Receivers MUST ignore this field.
此位保留供将来使用。发件人必须将此设置为0。接收者必须忽略此字段。
fragment offset: 24 bits
片段偏移量：24位
This value MUST be set to the byte offset of the current payload in relation to the very beginning of each JPEG 2000 codestream (JPEG 2000 frame).
该值必须设置为当前有效负载相对于每个JPEG 2000码流（JPEG 2000帧）最开始的字节偏移量。
Byte offsets are calculated from the start of each JPEG 2000 codestream up to the current position where the current payload would fit into the complete JPEG 2000 codestream.
字节偏移量是从每个JPEG 2000码流的开始计算到当前有效负载适合完整JPEG 2000码流的当前位置。
To perform scalable video delivery by using multiple RTP sessions, the offset value from the first byte of the same frame is set for fragment offset. It is then possible to deliver layered video using multiple RTP sessions; the fragment offset might not start from 0 in some RTP sessions even if the packet is the first one received in the RTP session.
要通过使用多个RTP会话执行可伸缩视频交付，将同一帧的第一个字节的偏移值设置为片段偏移。然后可以使用多个RTP会话交付分层视频；在某些RTP会话中，即使数据包是RTP会话中接收到的第一个数据包，片段偏移量也可能不会从0开始。
The sender must packetize the JPEG 2000 appropriately according to initial media type parameters and/or details from SDP offer/answer parameters.
发送方必须根据初始媒体类型参数和/或SDP提供/应答参数的详细信息对JPEG 2000进行适当打包。
A "packetization unit" is defined as either a JPEG 2000 main header, a tile-part header, or a JPEG 2000 packet.
“分组单元”被定义为JPEG 2000主报头、平铺部分报头或JPEG 2000分组。
First, a sender divides the JPEG 2000 codestream into packetization units by parsing the codestream or by getting information from the encoder, and packs the packetization units into RTP packets. A sender can put an arbitrary number of packetization units into an RTP packet, but it MUST preserve the codestream order. An example of this kind of RTP packet format is shown in Figure 4:
首先，发送方通过解析码流或从编码器获取信息将JPEG 2000码流划分为分组单元，并将分组单元打包为RTP分组。发送方可以将任意数量的打包单元放入RTP数据包中，但它必须保持码流顺序。这种RTP数据包格式的示例如图4所示：
+------+-------+---------------+---------------+
|RTP |payload| packetization | packetization |
|header|header | unit | unit |
+------+-------+---------------+---------------+
+------+-------+---------------+---------------+
|RTP |payload| packetization | packetization |
|header|header | unit | unit |
+------+-------+---------------+---------------+
Figure 4: An example with multiple packetization units
图4：具有多个打包单元的示例
If a packetization unit with headers (IP header, RTP header, and payload header) is larger than the MTU size, it MAY be fragmented. To pack a fragmented packetization unit, the fragmented unit MUST NOT be packed with the succeeding packetization unit within the same RTP packet. An example of this kind of RTP packet format is shown in Figure 5:
如果带有报头（IP报头、RTP报头和有效负载报头）的打包单元大于MTU大小，则它可能被分段。要打包碎片化单元，碎片化单元不得与同一RTP数据包内的后续打包单元打包。这种RTP数据包格式的示例如图5所示：
+------+-------+-------------------------------------------------+
|RTP |payload| packetization unit fragment |
|header|header | |
+------+-------+-------------------------------------------------+
+------+-------+-------------------------------------------------+
|RTP |payload| packetization unit fragment |
|header|header | |
+------+-------+-------------------------------------------------+
.
.
.
+------+-------+------------------------------------+
|RTP |payload| end of packetization unit fragment |
|header|header | |
+------+-------+------------------------------------+
+------+-------+-------------------------------------------------+
|RTP |payload| packetization unit fragment |
|header|header | |
+------+-------+-------------------------------------------------+
+------+-------+-------------------------------------------------+
|RTP |payload| packetization unit fragment |
|header|header | |
+------+-------+-------------------------------------------------+
.
.
.
+------+-------+------------------------------------+
|RTP |payload| end of packetization unit fragment |
|header|header | |
+------+-------+------------------------------------+
Figure 5: An example with a fragmented packetization unit
图5：一个碎片化打包单元的示例
This registration uses the template defined in [RFC4288] and follows [RFC4855].
此注册使用[RFC4288]中定义的模板，并遵循[RFC4855]。
Type name: video
类型名称：视频
Subtype name: jpeg2000
子类型名称：jpeg2000
Required parameters:
所需参数：
rate: The RTP timestamp clock rate. The default rate is 90000, but other rates MAY be specified. Rates below 1000 Hz SHOULD NOT be used.
速率：RTP时间戳时钟速率。默认费率为90000，但可以指定其他费率。不应使用低于1000 Hz的频率。
sampling: A list of values specifying the color space of the payload data.
采样：指定有效负载数据颜色空间的值列表。
Acceptable values:
可接受值：
RGB: standard Red, Green, Blue color space.
RGB：标准红、绿、蓝颜色空间。
BGR: standard Blue, Green, Red color space.
BGR：标准蓝、绿、红颜色空间。
RGBA: standard Red, Green, Blue, Alpha color space.
RGBA：标准红、绿、蓝、阿尔法颜色空间。
BGRA: standard Blue, Green, Red, Alpha color space.
BGRA：标准蓝、绿、红、阿尔法色空间。
YCbCr-4:4:4: standard YCbCr color space; no subsampling.
YCbCr-4:4:4：标准YCbCr颜色空间；没有二次抽样。
YCbCr-4:2:2: standard YCbCr color space; Cb and Cr are subsampled horizontally by 1/2.
YCbCr-4:2:2：标准YCbCr颜色空间；Cb和Cr水平二分之一取样。
YCbCr-4:2:0: standard YCbCr color space; Cb and Cr are subsampled horizontally and vertically by 1/2.
YCbCr-4:2:0：标准YCbCr颜色空间；Cb和Cr水平和垂直二分之一取样。
YCbCr-4:1:1: standard YCbCr color space; Cb and Cr are subsampled vertically by 1/4.
YCbCr-4:1:1：标准YCbCr颜色空间；Cb和Cr垂直二次取样1/4。
GRAYSCALE: basically, a single component image of just multilevels of grey.
灰度：基本上，一个单一组成部分的图像只是多层次的灰色。
EXTENSION VALUE: Additional color samplings can be registered with the current listing of registered color samplings at: Color Sampling Registration Authority. Please refer to RTP Format for Uncompressed Video [RFC4175].
扩展值：其他颜色采样可以在：颜色采样注册机构的当前已注册颜色采样列表中注册。请参考未压缩视频的RTP格式[RFC4175]。
Optional parameters:
可选参数：
interlace: Interlace scanning. If the payload is in interlace
format, the acceptable value is "1"; otherwise, the value
should be "0". Each complete image forms, vertically, half the
display. The tp value MUST properly specify the field the
image represents: odd(tp=1) or even(tp=2). If this option is
interlace: Interlace scanning. If the payload is in interlace
format, the acceptable value is "1"; otherwise, the value
should be "0". Each complete image forms, vertically, half the
display. The tp value MUST properly specify the field the
image represents: odd(tp=1) or even(tp=2). If this option is
not present, the payload MUST be in progressive format and the tp MUST be set to 0.
如果不存在，则有效负载必须为渐进格式，并且tp必须设置为0。
width: A parameter describing the maximum width of the video stream. This parameter MUST appear when height is present. Acceptable values: -- an integer value between 0 -- 4,294,967,295.
宽度：描述视频流最大宽度的参数。当存在高度时，此参数必须出现。可接受值：--介于0--4294967295之间的整数值。
height: A parameter describing the maximum height of the video stream. This parameter MUST appear when width is present. Acceptable values: -- an integer value between 0 -- 4,294,967,295.
高度：描述视频流最大高度的参数。当存在宽度时，此参数必须出现。可接受值：--介于0--4294967295之间的整数值。
The receiver MUST ignore any unspecified parameters.
接收器必须忽略任何未指定的参数。
Encoding considerations:
编码注意事项：
This media type is framed and binary, see Section 4.8 of [RFC4288].
该媒体类型为框架式和二进制，见[RFC4288]第4.8节。
Security considerations: See Section 9 of this document.
安全注意事项：见本文件第9节。
Interoperability considerations:
互操作性注意事项：
The JPEG 2000 video stream is a sequence of JPEG 2000 still images. An implementation compliant with [JPEG2000Pt_1] can decode and attempt to display the encoded JPEG 2000 video stream.
JPEG 2000视频流是JPEG 2000静止图像序列。符合[JPEG2000Pt_1]的实现可以解码并尝试显示编码的JPEG2000视频流。
Published specification: ISO/IEC 15444-1 | ITU-T Rec. T.800
出版规范：ISO/IEC 15444-1 | ITU-T Rec.T.800
Applications that use this media type:
使用此媒体类型的应用程序：
video streaming and communication
视频流和通信
Person and email address to contact for further information:
联系人和电子邮件地址，以获取更多信息：
Eisaburo Itakura, Satoshi Futemma, Andrew Leung Email: itakura@sm.sony.co.jp, satosi-f@sm.sony.co.jp, andrew@ualberta.net
Itakura Eisaburo、Satoshi Futemma、Andrew Leung电子邮件：itakura@sm.sony.co.jp，satosi-f@sm.sony.co.jp, andrew@ualberta.net
Intended usage: COMMON
预期用途：普通
Restrictions on Usage:
使用限制：
This media type depends on RTP framing, and hence is only defined for the transfer via RTP [RFC3550]. Transport within other framing protocols is not defined at the time.
此媒体类型取决于RTP帧，因此仅为通过RTP传输定义[RFC3550]。当时未定义其他帧协议内的传输。
Author/Change Controller:
作者/变更控制员：
Author:
作者：
Eisaburo Itakura, Satoshi Futemma, Andrew Leung Email: itakura@sm.sony.co.jp, satosi-f@sm.sony.co.jp, andrew@ualberta.net
Itakura Eisaburo、Satoshi Futemma、Andrew Leung电子邮件：itakura@sm.sony.co.jp，satosi-f@sm.sony.co.jp, andrew@ualberta.net
Change controller:
更改控制器：
IETF Audio/Video Transport Working Group delegated from the IESG.
IESG授权的IETF音频/视频传输工作组。
The media type video/jpeg2000 string is mapped to fields in the Session Description Protocol (SDP) [RFC4566] as follows:
媒体类型视频/jpeg2000字符串映射到会话描述协议（SDP）[RFC4566]中的字段，如下所示：
o The media name in the "m=" line of SDP MUST be video.
o SDP的“m=”行中的媒体名称必须是视频。
o The encoding name in the "a=rtpmap" line of SDP MUST be jpeg2000 (the subtype).
o SDP的“a=rtpmap”行中的编码名称必须是jpeg2000（子类型）。
o The clock rate in the "a=rtpmap" line is set according to the "rate" parameter. Senders that wish to use a non-90kHz rate SHOULD also offer the same stream using a 90kHz timestamp rate with a different RTP payload type, allowing graceful fallback to 90kHz for compatibility.
o “a=rtpmap”行中的时钟速率根据“速率”参数设置。希望使用非90kHz速率的发送方还应使用不同RTP有效负载类型的90kHz时间戳速率提供相同的流，从而允许优雅地回退到90kHz以实现兼容性。
o The REQUIRED parameter, "sampling", MUST be included in the "a=fmtp" line of SDP.
o 所需参数“采样”必须包含在SDP的“a=fmtp”行中。
o The OPTIONAL parameters, if presented, MUST be included in the "a=fmtp" line of SDP.
o 可选参数（如有）必须包含在SDP的“a=fmtp”行中。
These parameters are expressed as a media type string, in the form of a semicolon separated list of parameter=value pairs.
这些参数表示为媒体类型字符串，以分号分隔的参数=值对列表的形式。
Therefore, an example of media representation in SDP using typical parameters is as follows:
因此，使用典型参数的SDP中的媒体表示示例如下：
m=video 49170/2 RTP/AVP 98
a=rtpmap:98 jpeg2000/90000
a=fmtp:98 sampling=YCbCr-4:2:0;width=128;height=128
m=video 49170/2 RTP/AVP 98
a=rtpmap:98 jpeg2000/90000
a=fmtp:98 sampling=YCbCr-4:2:0;width=128;height=128
An example for using non-90kHz timestamp is as follows:
使用非90kHz时间戳的示例如下：
m=video 49170/2 RTP/AVP 98 99
a=rtpmap:98 jpeg2000/27000000
a=rtpmap:99 jpeg2000/90000
a=fmtp:98 sampling=YCbCr-4:2:0;width=128;height=128
a=fmtp:99 sampling=YCbCr-4:2:0;width=128;height=128
m=video 49170/2 RTP/AVP 98 99
a=rtpmap:98 jpeg2000/27000000
a=rtpmap:99 jpeg2000/90000
a=fmtp:98 sampling=YCbCr-4:2:0;width=128;height=128
a=fmtp:99 sampling=YCbCr-4:2:0;width=128;height=128
When offering JPEG 2000 over RTP using SDP in an Offer/Answer model [RFC3264], the following rules and limitations apply:
在提供/应答模型[RFC3264]中使用SDP通过RTP提供JPEG 2000时，适用以下规则和限制：
o All parameters MUST have an acceptable value for the parameter.
o 所有参数必须具有可接受的参数值。
o All parameters MUST correspond to the parameters of the payload.
o 所有参数必须与有效载荷的参数相对应。
o The parameter "sampling" with an acceptable answer MUST appear in the offer and in the answer if accepted by the receiver. The receiver SHOULD do its best to handle the received codestream in the color space offered. If the receiver cannot handle the offered color space for whatever reason, it should reply with its preferred color space in the answer and gracefully end the session. Senders do not need to conform to the color space in the answer, but they should take note that the session ended due to color sampling issues.
o 带有可接受答案的参数“采样”必须出现在报价中，如果接收方接受，则必须出现在答案中。接收器应尽最大努力在提供的颜色空间中处理接收到的码流。如果接收者出于任何原因无法处理提供的颜色空间，则应在回答中使用其首选颜色空间进行回复，并优雅地结束会话。发件人不需要符合答案中的颜色空间，但他们应该注意，会话因颜色采样问题而结束。
o For optional parameter "interlace", if this option is used, it MUST appear in the offer and, if accepted, it SHOULD appear in the answer. Receivers should do their best to handle interlace or progressive codestreams but, if for some reason, receivers cannot accommodate, receivers should reply with preferred settings in the answer, then gracefully end the session. Senders do not need to adjust settings upon this answer, but they should take note that the session ended due to interlace or progressive issues.
o 对于可选参数“interlace”，如果使用此选项，则必须出现在报价中，如果接受，则应出现在答案中。接收机应尽最大努力处理交错或渐进式码流，但如果出于某种原因，接收机无法适应，则接收机应在应答中使用首选设置进行应答，然后优雅地结束会话。发件人无需根据此回答调整设置，但应注意，会话因交错或渐进问题而结束。
o For optional parameters "width" and "height", the following applies:
o 对于可选参数“宽度”和“高度”，以下内容适用：
* if "width" appears in the offer or answer, "height" MUST be present.
* 如果报价或答复中出现“宽度”，则必须显示“高度”。
* if "height" appears in the offer or answer, "width" MUST be present.
* 如果报价或答复中出现“高度”，则必须显示“宽度”。
o Width and height should appear in the offer as the maximum dimensions the sender can offer. In the answer, it SHOULD represent the maximum the receiver can accommodate. If there is a
o 宽度和高度应显示在报价中，作为发件人可以提供的最大尺寸。在回答中，它应该表示接收器可以容纳的最大值。如果有
difference between the offer and answer, the sender should re-offer a new width and height and appropriately scale down the codestream for the receiver.
在提供和回答之间的差异，发送方应该重新提供一个新的宽度和高度，并适当地缩小接收方的码流。
o In a multicast environment, [RFC1112] receivers should do their best to conform to parameters in the offer from the sender. Senders should use recommended settings in multicast environments and take note of answers. For width and height, the sender should accommodate to the lowest values it receives from all answers.
o 在多播环境中，[RFC1112]接收方应尽最大努力符合发送方提供的参数。发件人应在多播环境中使用建议的设置，并记下答案。对于宽度和高度，发送者应适应从所有答案中获得的最低值。
o Any unknown options in the offer should be ignored and deleted from the answer.
o 报价中的任何未知选项都应忽略并从答案中删除。
Example offer/answer exchanges are provided.
提供了报价/应答交换示例。
Alice offers YCbCr 4:2:2 color space, interlace image with 720-pixel width and 480-pixel height as below:
Alice提供YCbCr 4:2:2颜色空间、720像素宽和480像素高的隔行扫描图像，如下所示：
v=0
o=alice 2890844526 2890844526 IN IP4 host.example
s=
c=IN IP4 host.example
t=0 0
m=video 49170 RTP/AVP 98
a=rtpmap:98 jpeg2000/90000
a=fmtp:98 sampling=YCbCr-4:2:2; interlace=1; width=720;height=480
v=0
o=alice 2890844526 2890844526 IN IP4 host.example
s=
c=IN IP4 host.example
t=0 0
m=video 49170 RTP/AVP 98
a=rtpmap:98 jpeg2000/90000
a=fmtp:98 sampling=YCbCr-4:2:2; interlace=1; width=720;height=480
Bob accepts YCbCr-4:2:2 color space, interlace image and replies:
Bob接受YCbCr-4:2:2颜色空间、隔行扫描图像并回复：
v=0
o=bob 2890844730 2890844731 IN IP4 host.example
s=
c=IN IP4 host.example
t=0 0
m=video 49920 RTP/AVP 98
a=rtpmap:98 jpeg2000/90000
a=fmtp:98 sampling=YCbCr-4:2:2; interlace=1; width=720;height=480
v=0
o=bob 2890844730 2890844731 IN IP4 host.example
s=
c=IN IP4 host.example
t=0 0
m=video 49920 RTP/AVP 98
a=rtpmap:98 jpeg2000/90000
a=fmtp:98 sampling=YCbCr-4:2:2; interlace=1; width=720;height=480
Example offer/answer exchanges, where an offerer wishes to use non-90kHz timestamp, are provided.
提供了报价人希望使用非90kHz时间戳的报价/应答交换示例。
Alice offers an RTP payload type with 27MHz clock rate as well as with 90kHz clock rate, and each payload type includes: YCbCr 4:2:2 color space, interlace image, 720-pixel width and 480-pixel height.
Alice提供了一种RTP有效负载类型，具有27MHz时钟频率和90kHz时钟频率，每种有效负载类型包括：YCbCr 4:2:2颜色空间、隔行扫描图像、720像素宽度和480像素高度。
She puts 27MHz clock rate attributes prior to 90kHz because she wants to use 27 MHz rather than 90kHz.
她将27MHz时钟频率属性置于90kHz之前，因为她希望使用27MHz而不是90kHz。
v=0
o=alice 2890844526 2890844526 IN IP4 host.example
s=
c=IN IP4 host.example
t=0 0
m=video 49170 RTP/AVP 98 99
a=rtpmap:98 jpeg2000/27000000
a=rtpmap:99 jpeg2000/90000
a=fmtp:98 sampling=YCbCr-4:2:2; interlace=1; width=720;height=480
a=fmtp:99 sampling=YCbCr-4:2:2; interlace=1; width=720;height=480
v=0
o=alice 2890844526 2890844526 IN IP4 host.example
s=
c=IN IP4 host.example
t=0 0
m=video 49170 RTP/AVP 98 99
a=rtpmap:98 jpeg2000/27000000
a=rtpmap:99 jpeg2000/90000
a=fmtp:98 sampling=YCbCr-4:2:2; interlace=1; width=720;height=480
a=fmtp:99 sampling=YCbCr-4:2:2; interlace=1; width=720;height=480
If Bob can accept 27MHz clock rate, he replies as below:
如果Bob可以接受27MHz的时钟频率，他回答如下：
v=0
o=bob 2890844730 2890844731 IN IP4 host.example
s=
c=IN IP4 host.example
t=0 0
m=video 49920 RTP/AVP 98
a=rtpmap:98 jpeg2000/27000000
a=fmtp:98 sampling=YCbCr-4:2:2; interlace=1; width=720;height=480
v=0
o=bob 2890844730 2890844731 IN IP4 host.example
s=
c=IN IP4 host.example
t=0 0
m=video 49920 RTP/AVP 98
a=rtpmap:98 jpeg2000/27000000
a=fmtp:98 sampling=YCbCr-4:2:2; interlace=1; width=720;height=480
If Bob doesn't accept 27MHz clock rate, he replies as below:
如果Bob不接受27MHz时钟频率，他回答如下：
v=0
o=bob 2890844730 2890844731 IN IP4 host.example
s=
c=IN IP4 host.example
t=0 0
m=video 49920 RTP/AVP 99
a=rtpmap:99 jpeg2000/90000
a=fmtp:99 sampling=YCbCr-4:2:2; interlace=1; width=720;height=480
v=0
o=bob 2890844730 2890844731 IN IP4 host.example
s=
c=IN IP4 host.example
t=0 0
m=video 49920 RTP/AVP 99
a=rtpmap:99 jpeg2000/90000
a=fmtp:99 sampling=YCbCr-4:2:2; interlace=1; width=720;height=480
A new media subtype (video/jpeg2000) has been registered by IANA. For details, see Section 6 of this document.
IANA已经注册了一个新的媒体子类型（视频/jpeg2000）。有关详细信息，请参阅本文件第6节。
RTP packets using the payload format defined in this specification are subject to the security considerations discussed in the RTP specification [RFC3550], and in any applicable RTP profile. The main security considerations for the RTP packet carrying the RTP payload format defined within this memo are confidentiality, integrity, and
使用本规范中定义的有效负载格式的RTP数据包应遵守RTP规范[RFC3550]和任何适用RTP配置文件中讨论的安全注意事项。携带本备忘录中定义的RTP有效载荷格式的RTP数据包的主要安全注意事项是机密性、完整性和安全性
source authenticity. Confidentiality is achieved by encryption of the RTP payload. Integrity of the RTP packets is through the use of suitable cryptographic integrity protection mechanism. A cryptographic system may also allow the authentication of the source of the payload. A suitable security mechanism for this RTP payload format should provide confidentiality, integrity protection, and at least a source authentication method capable of determining whether or not an RTP packet is from a member of the RTP session.
来源真实性。保密性是通过对RTP有效负载进行加密来实现的。RTP数据包的完整性是通过使用合适的密码完整性保护机制实现的。密码系统还可允许对有效载荷的源进行认证。该RTP有效载荷格式的合适安全机制应提供机密性、完整性保护，以及至少能够确定RTP分组是否来自RTP会话的成员的源认证方法。
Note that the appropriate mechanism to provide security to RTP and payloads following this memo may vary. It is dependent on the application, the transport, and the signaling protocol employed. Therefore, a single mechanism is not sufficient, although if suitable, the usage of SRTP [RFC3711] is recommended. Other mechanism that may be used are IPsec [RFC4301] and Transport Layer Security (TLS) [RFC5246] (RTP over TCP), but other alternatives may also exist.
请注意，根据本备忘录为RTP和有效负载提供安全性的适当机制可能会有所不同。它取决于应用程序、传输和所采用的信令协议。因此，单一机制是不够的，尽管如果合适，建议使用SRTP[RFC3711]。可以使用的其他机制是IPsec[RFC4301]和传输层安全（TLS）[RFC5246]（TCP上的RTP），但也可能存在其他替代方案。
If Quality of Service (QoS) enhanced service is used, RTP receivers SHOULD monitor packet loss to ensure that the service that was requested is actually being delivered. If it is not, then they SHOULD assume that they are receiving best-effort service and behave accordingly.
如果使用服务质量（QoS）增强服务，RTP接收器应监控数据包丢失，以确保请求的服务实际正在交付。如果不是，那么他们应该假设他们正在接受尽力而为的服务，并相应地采取行动。
If best-effort service is being used, users of this payload format MUST monitor packet loss to ensure that the packet loss rate is within acceptable parameters. Packet loss is considered acceptable if a TCP flow across the same network path, experiencing the same network conditions, would achieve an average throughput, measured on a reasonable timescale, that is not less than the RTP flow is achieving. This condition can be satisfied by implementing congestion control mechanisms to adapt the transmission rate (or the number of layers subscribed for a layered multicast session), or by arranging for a receiver to leave the session if the loss rate is unacceptably high.
如果正在使用尽力而为服务，则此有效负载格式的用户必须监控数据包丢失，以确保数据包丢失率在可接受的参数范围内。如果在相同的网络路径上，经历相同的网络条件的TCP流将达到在合理的时间尺度上测量的平均吞吐量，即不小于RTP流所达到的平均吞吐量，则认为丢包是可接受的。可以通过实现拥塞控制机制来适应传输速率（或分层多播会话订阅的层数），或者如果丢失率高得令人无法接受，则通过安排接收机离开会话来满足该条件。
[JPEG2000Pt_1] ISO/IEC JTC1/SC29, ISO/IEC 15444-1 | ITU-T Rec. T.800, "Information Technology - JPEG 2000 Image Coding System - Part 1: Core Coding System", December 2000.
[JPEG2000Pt_1]ISO/IEC JTC1/SC29，ISO/IEC 15444-1 | ITU-T Rec.T.800，“信息技术-JPEG 2000图像编码系统-第1部分：核心编码系统”，2000年12月。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V. Jacobson, "RTP: A Transport Protocol for Real-Time Applications", STD 64, RFC 3550, July 2003.
[RFC3550]Schulzrinne，H.，Casner，S.，Frederick，R.，和V.Jacobson，“RTP：实时应用的传输协议”，STD 64，RFC 35502003年7月。
[RFC3711] Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K. Norrman, "The Secure Real-time Transport Protocol (SRTP)", RFC 3711, March 2004.
[RFC3711]Baugher，M.，McGrew，D.，Naslund，M.，Carrara，E.，和K.Norrman，“安全实时传输协议（SRTP）”，RFC 37112004年3月。
[RFC4288] Freed, N. and J. Klensin, "Media Type Specifications and Registration Procedures", BCP 13, RFC 4288, December 2005.
[RFC4288]Freed，N.和J.Klensin，“介质类型规范和注册程序”，BCP 13，RFC 4288，2005年12月。
[RFC4855] Casner, S., "Media Type Registration of RTP Payload Formats", RFC 4855, February 2007.
[RFC4855]Casner，S.，“RTP有效负载格式的媒体类型注册”，RFC 48552007年2月。
[RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session Description Protocol", RFC 4566, July 2006.
[RFC4566]Handley，M.，Jacobson，V.，和C.Perkins，“SDP：会话描述协议”，RFC4566，2006年7月。
[RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model with Session Description Protocol (SDP)", RFC 3264, June 2002.
[RFC3264]Rosenberg，J.和H.Schulzrinne，“具有会话描述协议（SDP）的提供/应答模型”，RFC 3264，2002年6月。
[JPEG2000Pt_3] ISO/IEC JTC1/SC29, ISO/IEC 15444-1 | ITU-T Rec. T.800, "Information Technology - JPEG 2000 Image Coding System - Part 3: Motion JPEG 2000", July 2002.
[JPEG2000Pt_3]ISO/IEC JTC1/SC29，ISO/IEC 15444-1 | ITU-T Rec.T.800，“信息技术-JPEG 2000图像编码系统-第3部分：运动JPEG 2000”，2002年7月。
[RFC5372] Leung, A., Futemma, S., and E. Itakura, "Payload Format for JPEG 2000 Video: Extensions for Scalability and Main Header Recovery", RFC 5372, October 2008.
[RFC5372]Leung，A.，Futemma，S.，和E.Itakura，“JPEG 2000视频的有效载荷格式：可扩展性和主头恢复扩展”，RFC 5372，2008年10月。
[RFC4301] Kent, S. and K. Seo, "Security Architecture for the Internet Protocol", RFC 4301, December 2005.
[RFC4301]Kent，S.和K.Seo，“互联网协议的安全架构”，RFC 43012005年12月。
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security (TLS) Protocol Version 1.2", RFC 5246, August 2008.
[RFC5246]Dierks，T.和E.Rescorla，“传输层安全（TLS）协议版本1.2”，RFC 5246，2008年8月。
[RFC4175] Gharai, L. and C. Perkins, "RTP Payload Format for Uncompressed Video", RFC 4175, September 2005.
[RFC4175]Gharai，L.和C.Perkins，“未压缩视频的RTP有效载荷格式”，RFC 41752005年9月。
[RFC1112] Deering, S., "Host extensions for IP multicasting", STD 5, RFC 1112, August 1989.
[RFC1112]Deering，S.，“IP多播的主机扩展”，STD 5，RFC11121989年8月。
As the JPEG 2000 coding standard is highly flexible, many different but compliant data streams may be produced and still be compliant JPEG 2000 codestreams.
由于JPEG 2000编码标准是高度灵活的，因此可以产生许多不同但兼容的数据流，并且仍然是兼容的JPEG 2000码流。
The following is a set of recommendations set forth from our experience in developing JPEG 2000 and this payload specification. Implementations of this standard must handle all possibilities mentioned in this specification. The following is a listing of items an implementation may optimize.
以下是根据我们开发JPEG 2000和本有效载荷规范的经验提出的一组建议。本标准的实施必须处理本规范中提到的所有可能性。以下是实施可能优化的项目列表。
Error Resilience Markers: The use of error resilience markers in the JPEG 2000 data stream is highly recommended in all situations. Error recovery with these markers is helpful to the decoder and saves external resources (e.g., markers such as RESET, RESTART, and ERTERM).
错误恢复标记：强烈建议在所有情况下在JPEG 2000数据流中使用错误恢复标记。使用这些标记进行错误恢复有助于解码器并节省外部资源（例如，重置、重新启动和ERTERM等标记）。
YCbCr Color Space: The YCbCr color space provides the greatest amount of compression in color with respect to the human visual system. When used with JPEG 2000, this color space can provide excellent visual results at low bit rates.
YCbCr颜色空间：相对于人类视觉系统，YCbCr颜色空间提供了最大数量的颜色压缩。当与JPEG 2000一起使用时，此颜色空间可以在低比特率下提供出色的视觉效果。
Progression Ordering: JPEG 2000 offers many different ways to order the final code stream to optimize the transfer with the presentation. We have found that the most useful codestream ordering is layer progression and resolution progression ordering.
渐进排序：JPEG 2000提供了许多不同的方法来排序最终的代码流，以优化演示文稿的传输。我们发现最有用的码流排序是层级数和分辨率级数排序。
Tiling and Packets: JPEG 2000 packets are formed regardless of the encoding method. The encoder has little control over the size of these JPEG 2000 packets as they may be large or small. Tiling splits the image into smaller areas and each is encoded separately. With tiles, the JPEG 2000 packet sizes are also reduced. When using tiling, almost all JPEG 2000 packet sizes are an acceptable size for transmission (i.e., smaller than the MTU size of most networks).
平铺和数据包：JPEG 2000数据包的形成与编码方法无关。编码器几乎无法控制这些JPEG 2000数据包的大小，因为它们可能大或小。平铺将图像分割为更小的区域，每个区域分别编码。使用tiles时，JPEG 2000数据包的大小也会减小。使用平铺时，几乎所有JPEG 2000数据包大小都是可接受的传输大小（即，小于大多数网络的MTU大小）。
Sender Processing: There are no limitations as to how the sender should pack the payload. In general, the sender should pack headers separately from the rest of the codestream to make header recovery simple. Payloads should generally begin with a Start of Packet (SOP) marker and end with an End of Packet Header (EPH) marker for easier decoder processing.
发送方处理：对于发送方应该如何打包有效负载没有限制。通常，发送方应该将头与代码流的其余部分分开打包，以简化头恢复。为便于解码器处理，有效负载通常应以数据包开始（SOP）标记开始，以数据包结束报头（EPH）标记结束。
This section has various sample headers in various configurations for reference.
本节提供了各种配置中的各种示例标题，以供参考。
For reference, the payload header is as follows:
作为参考，有效载荷标题如下所示：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|tp |MHF|mh_id|T| priority | tile number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|reserved | fragment offset |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|tp |MHF|mh_id|T| priority | tile number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|reserved | fragment offset |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 6: JPEG 2000 Payload Header
图6:JPEG2000有效载荷标题
A.2.1. Sample 1: Progressive Image with Single Tile, 3500 Bytes (i.e., thumbnail)
A.2.1. 示例1：单块渐进图像，3500字节（即缩略图）
First Packet: This packet will have the whole main header 210 bytes
第一个数据包：这个数据包将有整个主报头210字节
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 3 | 0 |1| 255 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF4F FF51 002F 000 .... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 3 | 0 |1| 255 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF4F FF51 002F 000 .... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 7: Header Sample 1-1 (First Packet)
图7：报头示例1-1（第一个数据包）
Second Packet: This packet will have a tile header and the first tile part LLband 1500 bytes
第二个数据包：这个数据包将有一个tile头和第一个tile部分LLband 1500字节
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 3 | 0 |0| 255 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 210 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF90 000A 0000 0000 2DB3 0001 FF93 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 3 | 0 |0| 255 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 210 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF90 000A 0000 0000 2DB3 0001 FF93 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 8: Header Sample 1-2 (Second Packet)
图8：报头示例1-2（第二个数据包）
Third Packet: This packet will have the next part in the tile, no tile header 1500 bytes
第三个数据包：这个数据包将在磁贴中有下一部分，没有磁贴头1500字节
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 0 | 0 |0| 255 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 1710 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|E841 4526 4556 9850 C2EA ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 0 | 0 |0| 255 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 1710 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|E841 4526 4556 9850 C2EA ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 9: Header Sample 1-3 (Third Packet)
图9：报头示例1-3（第三个数据包）
Fourth Packet: Last packet for the image 290 bytes
第四个数据包：图像290字节的最后一个数据包
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 0 | 0 |0| 255 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 3210 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|A55D 8B73 3B25 25C7 B9EB ... 2FBE B153|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 0 | 0 |0| 255 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 3210 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|A55D 8B73 3B25 25C7 B9EB ... 2FBE B153|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 10: Header Sample 1-4 (4th Packet)
图10：标题示例1-4（第4个数据包）
First Packet: This packet will have the whole main header. 210 bytes
第一个数据包：这个数据包将有整个主报头。210字节
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 3 | 0 |1| 255 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF4F FF51 002F 000 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 3 | 0 |1| 255 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF4F FF51 002F 000 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 11: Header Sample 2-1 (First Packet)
图11：报头示例2-1（第一个数据包）
Second Packet: This packet will have a first tile part (tile 0) 1400 bytes
第二个数据包：此数据包将具有第一个磁贴部分（磁贴0）1400字节
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 0 | 0 |0| 255 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 210 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF90 000A 0000 0000 0578 0001 FF93 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 0 | 0 |0| 255 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 210 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF90 000A 0000 0000 0578 0001 FF93 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 12: Header Sample 2-2 (Second Packet)
图12：报头示例2-2（第二个数据包）
Third Packet: This packet will have a second tile part (tile 1) 1423 bytes
第三个数据包：该数据包将有第二个磁贴部分（磁贴1）1423字节
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 0 | 0 |0| 255 | 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 1610 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF90 000A 0001 0000 058F 0001 FF93 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 0 | 0 |0| 255 | 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 1610 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF90 000A 0001 0000 058F 0001 FF93 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 13: Header Sample 2-3 (Third Packet)
图13：报头示例2-3（第三个数据包）
Fourth Packet: This packet will have a third tile part (tile 2) 1355 bytes
第四个数据包：该数据包将有第三个磁贴部分（磁贴2）1355字节
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 0 | 0 |0| 255 | 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 3033 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF90 000A 0002 0000 054B 0001 FF93 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 0 | 0 |0| 255 | 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 3033 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF90 000A 0002 0000 054B 0001 FF93 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 14: Header Sample 2-4 (4th Packet)
图14：标题示例2-4（第4个数据包）
Fifth Packet: This packet will have a fourth tile part (tile 3) 1290 bytes
第五个数据包：这个数据包将有第四个tile部分（tile 3）1290字节
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 0 | 0 |0| 255 | 3 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 4388 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF90 000A 0003 0000 050A 0001 FF93 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 0 | 0 |0| 255 | 3 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 4388 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF90 000A 0003 0000 050A 0001 FF93 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 15: Header Sample 2-5 (5th Packet)
图15：标题示例2-5（第5包）
A.2.3. Sample 3: Packing Multiple Tiles in Single Payload, Fragmented Header
A.2.3. 示例3：在单个有效负载、碎片标题中打包多个磁贴
First Packet: This packet will have the first part of the main header 110 bytes
第一个数据包：该数据包将具有主报头的第一部分110字节
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 1 | 0 |1| 255 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF4F FF51 002F 000 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 1 | 0 |1| 255 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF4F FF51 002F 000 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 16: Header Sample 3-1 (First Packet)
图16：报头示例3-1（第一个数据包）
Second Packet: This packet has the second part of the header 1400 bytes
第二个数据包：这个数据包的头的第二部分是1400字节
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 2 | 0 |1| 255 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 110 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF64 00FF ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 2 | 0 |1| 255 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 110 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF64 00FF ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 17: Header Sample 3-2 (Second Packet)
图17：报头示例3-2（第二个数据包）
Third Packet: This packet has two tiles, tile 0 and tile 1 1400 bytes
第三个数据包：这个数据包有两个分片，分片0和分片1 1400字节
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 0 | 0 |1| 255 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 1510 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF90 000A 0000 0000 02BC 0001 FF93 ... |
// //
|FF90 000A 0001 0000 02BC 0001 FF93 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 0 | 0 |1| 255 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 1510 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF90 000A 0000 0000 02BC 0001 FF93 ... |
// //
|FF90 000A 0001 0000 02BC 0001 FF93 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 18: Header Sample 3-3 (Third Packet)
图18：报头示例3-3（第三个数据包）
Fourth Packet: This packet has one tile, tile 2 1395 bytes
第四个数据包：这个数据包有一个磁贴，磁贴2 1395字节
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 0 | 0 |0| 255 | 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 2910 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF90 000A 0002 0000 0573 0001 FF93 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 0 | 0 |0| 255 | 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 2910 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF90 000A 0002 0000 0573 0001 FF93 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 19: Header Sample 3-4 (4th Packet)
图19：标题示例3-4（第4个数据包）
First packet: This packet will have the whole main header for the odd field 210 bytes
第一个数据包：该数据包将具有奇数字段210字节的整个主报头
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 1 | 3 | 0 |1| 255 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF4F FF51 002F 000 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 1 | 3 | 0 |1| 255 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF4F FF51 002F 000 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 20: Header Sample 4-1 (First Packet)
图20：报头示例4-1（第一个数据包）
Second packet: This packet will have the first part of the odd field's tile 1400 bytes
第二个数据包：这个数据包将有奇数字段的第一部分1400字节
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 1 | 0 | 0 |1| 255 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 210 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF90 000A 0000 0000 0578 0001 FF93 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 1 | 0 | 0 |1| 255 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 210 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF90 000A 0000 0000 0578 0001 FF93 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 21: Header Sample 4-2 (Second Packet)
图21：报头示例4-2（第二个数据包）
Third packet: This packet will have the second part of the odd field's tile 1400 bytes
第三个数据包：这个数据包将有奇数字段的第二部分1400字节
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 1 | 0 | 0 |1| 255 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 1610 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|7F04 E708 27D9 D11D 22CB ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 1 | 0 | 0 |1| 255 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 1610 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|7F04 E708 27D9 D11D 22CB ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 22: Header Sample 4-3 (Third Packet)
图22：报头示例4-3（第三个数据包）
Fourth packet: This packet will have the third part of the odd field's tile 1300 bytes
第四个数据包：这个数据包将有奇数字段的第三部分1300字节
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 1 | 0 | 0 |1| 255 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 3010 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|98BD EC9B 2826 DC62 D4AB ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 1 | 0 | 0 |1| 255 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 3010 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|98BD EC9B 2826 DC62 D4AB ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 23: Header Sample 4-4 (4th Packet)
图23：报头示例4-4（第4个数据包）
Fifth packet: This packet will have the whole main header for the even field 210 bytes
第五个数据包：此数据包将具有整个主报头，用于偶数字段210字节
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 2 | 3 | 0 |1| 255 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF4F FF51 002F 000 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 2 | 3 | 0 |1| 255 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF4F FF51 002F 000 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 24: Header Sample 4-5 (5th Packet)
图24：标题示例4-5（第5包）
Sixth packet: This packet will have the first part of the even field's tile 1400 bytes
第六个数据包：此数据包将包含偶数字段的第一部分1400字节
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 2 | 0 | 0 |1| 255 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 210 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF90 000A 0000 0000 0578 0001 FF93 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 2 | 0 | 0 |1| 255 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 210 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|FF90 000A 0000 0000 0578 0001 FF93 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 25: Header Sample 4-6 (6th Packet)
图25：标题示例4-6（第6包）
Seventh packet: This packet will have the second part of the even field's tile 1400 bytes
第七个数据包：这个数据包将包含偶数字段的第二部分1400字节
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 2 | 0 | 0 |1| 255 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 1610 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|626C 42F0 166B 6BD0 F8E1 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 2 | 0 | 0 |1| 255 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 1610 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|626C 42F0 166B 6BD0 F8E1 ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 26: Header Sample 4-7 (7th Packet)
图26：标题示例4-7（第7包）
Eighth packet: This packet will have the third part of the even field's tile 1300 bytes
第八个数据包：这个数据包将包含偶数字段的第三部分1300字节
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 2 | 0 | 0 |1| 255 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 3010 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|8114 41D5 18AB 4A1B ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 2 | 0 | 0 |1| 255 | 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 | 3010 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|8114 41D5 18AB 4A1B ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 27: Header Sample 4-8 (8th Packet)
图27：标题示例4-8（第8包）
Authors' Addresses
作者地址
Satoshi Futemma Sony Corporation 1-7-1 Konan Minato-ku Tokyo 108-0075 Japan
Satoshi Futemma索尼公司1-7-1日本东京河南Minato区108-0075
Phone: +81 3 6748-2111
EMail: satosi-f@sm.sony.co.jp
URI: http://www.sony.net/
Phone: +81 3 6748-2111
EMail: satosi-f@sm.sony.co.jp
URI: http://www.sony.net/
Eisaburo Itakura Sony Corporation 1-7-1 Konan Minato-ku Tokyo 108-0075 Japan
东谷荣三郎索尼公司1-7-1日本东京河南町108-0075
Phone: +81 3 6748-2111
EMail: itakura@sm.sony.co.jp
URI: http://www.sony.net/
Phone: +81 3 6748-2111
EMail: itakura@sm.sony.co.jp
URI: http://www.sony.net/
Andrew Leung Sony Corporation
梁建邦索尼公司
EMail: andrew@ualberta.net
EMail: andrew@ualberta.net
Full Copyright Statement
完整版权声明
Copyright (C) The IETF Trust (2008).
版权所有（C）IETF信托基金（2008年）。
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件及其包含的信息以“原样”为基础提供，贡献者、他/她所代表或赞助的组织（如有）、互联网协会、IETF信托基金和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Intellectual Property
知识产权
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息，请参见BCP 78和BCP 79。
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.