Internet Engineering Task Force (IETF) K. Kobayashi
Request for Comments: 6469 AICS, RIKEN
Obsoletes: 3189 K. Mishima
Category: Standards Track Keio University
ISSN: 2070-1721 S. Casner
Packet Design
C. Bormann
Universitaet Bremen TZI
December 2011
Internet Engineering Task Force (IETF) K. Kobayashi
Request for Comments: 6469 AICS, RIKEN
Obsoletes: 3189 K. Mishima
Category: Standards Track Keio University
ISSN: 2070-1721 S. Casner
Packet Design
C. Bormann
Universitaet Bremen TZI
December 2011
RTP Payload Format for DV (IEC 61834) Video
DV（IEC 61834）视频的RTP有效负载格式
Abstract
摘要
This document specifies the packetization scheme for encapsulating the compressed digital video data streams commonly known as "DV" into a payload format for the Real-Time Transport Protocol (RTP). This document obsoletes RFC 3189.
本文件规定了将压缩数字视频数据流（通常称为“DV”）封装为实时传输协议（RTP）的有效载荷格式的打包方案。本文件废除RFC 3189。
Status of This Memo
关于下段备忘
This is an Internet Standards Track document.
这是一份互联网标准跟踪文件。
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。有关互联网标准的更多信息，请参见RFC 5741第2节。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6469.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc6469.
Copyright Notice
版权公告
Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2011 IETF信托基金和确定为文件作者的人员。版权所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English.
本文件可能包含2008年11月10日之前发布或公开的IETF文件或IETF贡献中的材料。控制某些材料版权的人员可能未授予IETF信托允许在IETF标准流程之外修改此类材料的权利。在未从控制此类材料版权的人员处获得充分许可的情况下，不得在IETF标准流程之外修改本文件，也不得在IETF标准流程之外创建其衍生作品，除了将其格式化以RFC形式发布或将其翻译成英语以外的其他语言。
Table of Contents
目录
1. Introduction ....................................................3
1.1. Terminology ................................................4
2. RTP Payload Format ..............................................4
2.1. The DV Format Encoding .....................................4
2.2. RTP Header Usage ...........................................5
2.3. Payload Structures .........................................6
3. Payload Format Parameters .......................................7
3.1. Media Type Registration ....................................7
3.1.1. Media Type Registration for DV Video ................8
3.1.2. Media Type Registration for DV Audio ................9
3.2. SDP Parameters ............................................11
3.2.1. Mapping of Payload Type Parameters to SDP ..........11
3.2.2. Usage with the SDP Offer/Answer Model ..............12
3.3. Examples ..................................................12
3.3.1. Example for Unbundled Streams ......................13
3.3.2. Example for Bundled Streams ........................13
4. Security Considerations ........................................14
5. Congestion Control .............................................14
6. IANA Considerations ............................................14
7. Major Changes from RFC 3189 ....................................15
8. Interoperability with Previous Implementations .................15
9. Acknowledgment .................................................16
10. References ....................................................16
10.1. Normative References .....................................16
10.2. Informative References ...................................17
1. Introduction ....................................................3
1.1. Terminology ................................................4
2. RTP Payload Format ..............................................4
2.1. The DV Format Encoding .....................................4
2.2. RTP Header Usage ...........................................5
2.3. Payload Structures .........................................6
3. Payload Format Parameters .......................................7
3.1. Media Type Registration ....................................7
3.1.1. Media Type Registration for DV Video ................8
3.1.2. Media Type Registration for DV Audio ................9
3.2. SDP Parameters ............................................11
3.2.1. Mapping of Payload Type Parameters to SDP ..........11
3.2.2. Usage with the SDP Offer/Answer Model ..............12
3.3. Examples ..................................................12
3.3.1. Example for Unbundled Streams ......................13
3.3.2. Example for Bundled Streams ........................13
4. Security Considerations ........................................14
5. Congestion Control .............................................14
6. IANA Considerations ............................................14
7. Major Changes from RFC 3189 ....................................15
8. Interoperability with Previous Implementations .................15
9. Acknowledgment .................................................16
10. References ....................................................16
10.1. Normative References .....................................16
10.2. Informative References ...................................17
This document specifies payload formats for encapsulating both consumer- and professional-use Digital Video (DV) format data streams into the Real-Time Transport Protocol (RTP) [RFC3550]. DV compression audio and video formats were designed for a recording format on helical-scan magnetic tape media. The DV standards for consumer-market devices, the IEC 61883 and 61834 series, cover many aspects of consumer-use digital video, including mechanical specifications of a cassette, magnetic recording format, error correction on the magnetic tape, Discrete Cosine Transform (DCT) video encoding format, and audio encoding format [IEC61834]. The digital interface part of IEC 61883 defines an interface on the IEEE 1394 system [IEC61883][IEEE1394]. This specification set supports several video formats: SD-VCR (Standard Definition), HD-VCR (High Definition), SDL-VCR (Standard Definition - Long), PALPlus, DVB (Digital Video Broadcast), and ATV (Advanced Television). North American formats are indicated with a number of lines and "/60", while European formats use "/50". DV standards extended for professional use were published by the Society of Motion Picture and Television Engineers (SMPTE) as 314M and 370M, for different sampling systems, higher color resolution, and higher bit rates [SMPTE314M][SMPTE370M].
本文件规定了将消费者和专业人士使用的数字视频（DV）格式数据流封装到实时传输协议（RTP）[RFC3550]中的有效载荷格式。DV压缩音频和视频格式是为螺旋扫描磁带介质上的记录格式而设计的。消费者市场设备的DV标准IEC 61883和61834系列涵盖消费者使用数字视频的许多方面，包括盒式磁带的机械规格、磁记录格式、磁带纠错、离散余弦变换（DCT）视频编码格式和音频编码格式[IEC61834]。IEC 61883的数字接口部分定义了IEEE 1394系统[IEC61883][IEEE1394]上的接口。本规范集支持多种视频格式：SD-VCR（标准清晰度）、HD-VCR（高清晰度）、SDL-VCR（标准清晰度-长）、Perpllus、DVB（数字视频广播）和ATV（高级电视）。北美格式用许多行和“/60”表示，而欧洲格式用“/50”表示。电影和电视工程师协会（SMPTE）发布了专业使用的DV标准，分别为314M和370M，用于不同的采样系统、更高的颜色分辨率和更高的比特率[SMPTE314M][SMPTE370M]。
In summary, there are two kinds of DV, one for consumer use and the other for professional. The original "DV" specification designed for consumer-use digital VCRs is approved as the IEC 61834 standard set. The specifications for professional DV are published as SMPTE 314M and 370M. Both encoding formats are based on consumer DV and used in SMPTE D-7, D-9, and D-12 video systems. The RTP payload format specified in this document supports IEC 61834 consumer DV and professional SMPTE 314M and 370M (DV-based) formats.
总之，有两种DV，一种供消费者使用，另一种供专业人士使用。最初为消费者使用的数字录像机设计的“DV”规范被批准为IEC 61834标准集。专业DV规范发布为SMPTE 314M和370M。这两种编码格式均基于消费者DV，并用于SMPTE D-7、D-9和D-12视频系统。本文件中规定的RTP有效载荷格式支持IEC 61834消费者DV和专业SMPTE 314M和370M（基于DV）格式。
IEC 61834 also includes magnetic tape recording for digital TV broadcasting systems (such as DVB and ATV) that use MPEG2 encoding. The payload format for encapsulating MPEG2 into RTP has already been defined in RFC 2250 [RFC2250] and elsewhere.
IEC 61834还包括使用MPEG2编码的数字电视广播系统（如DVB和ATV）的磁带记录。RFC 2250[RFC2250]和其他地方已经定义了将MPEG2封装到RTP中的有效负载格式。
Consequently, the payload specified in this document will support six video formats of the IEC standard: SD-VCR (525/60, 625/50), HD-VCR (1125/60, 1250/50), and SDL-VCR (525/60, 625/50). It also supports eight of the SMPTE standards: 314M 25 Mbit/s (525/60, 625/50), 314M 50 Mbit/s (525/60, 625/50), and 370M 100 Mbit/s (1080/60i, 1080/50i, 720/60p, and 720/50p). In the future, it can be extended into other video formats managed by the 80-byte DV Digital Interface Format (DIF) block.
因此，本文件中规定的有效载荷将支持IEC标准的六种视频格式：SD-VCR（525/60625/50）、HD-VCR（1125/601250/50）和SDL-VCR（525/60625/50）。它还支持八种SMPTE标准：314M 25Mbit/s（525/60625/50）、314M 50Mbit/s（525/60625/50）和370M 100Mbit/s（1080/60i、1080/50i、720/60p和720/50p）。将来，它可以扩展到由80字节DV数字接口格式（DIF）块管理的其他视频格式。
Throughout this specification, we make extensive use of the terminology of IEC and SMPTE standards. The reader should consult the original references for definitions of these terms.
在本规范中，我们广泛使用了IEC和SMPTE标准的术语。读者应查阅原始参考文献，了解这些术语的定义。
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]中所述进行解释。
The DV format only uses the DCT compression technique within each frame, contrasted with the interframe compression of the MPEG video standards [ISO/IEC11172][ISO/IEC13818]. All video data, including audio and other system data, is managed within the picture frame unit of video.
DV格式仅在每个帧内使用DCT压缩技术，与MPEG视频标准[ISO/IEC11172][ISO/IEC13818]的帧间压缩形成对比。所有视频数据，包括音频和其他系统数据，都在视频的图片帧单元内进行管理。
The DV video encoding is composed of a three-level hierarchical structure, i.e., DCT super block, DCT macro block, and DCT block. A picture frame is divided into rectangle- or clipped-rectangle-shaped DCT super blocks. DCT super blocks are divided into 27 rectangle- or square-shaped DCT macro blocks, and each DCT macro block consists of a number of DCT blocks. Each DCT block consists of 8x8 pixels and represents a rectangle region for each color, Y, Cb, and Cr.
DV视频编码由三级层次结构组成，即DCT超块、DCT宏块和DCT块。图片帧被划分为矩形或剪裁的矩形DCT超级块。DCT超级块被划分为27个矩形或方形DCT宏块，每个DCT宏块由多个DCT块组成。每个DCT块由8x8像素组成，代表每种颜色、Y、Cb和Cr的矩形区域。
Audio data is encoded in Pulse Code Modulation (PCM) format. The sampling frequency is 32 kHz, 44.1 kHz, or 48 kHz and the quantization is 12-bit non-linear, 16-bit linear, or 20-bit linear. The number of channels may be up to 8. Only certain combinations of these parameters are allowed, depending upon the video format; the restrictions are specified in each document [IEC61834][SMPTE314M] [SMPTE370M].
音频数据以脉冲编码调制（PCM）格式编码。采样频率为32 kHz、44.1 kHz或48 kHz，量化为12位非线性、16位线性或20位线性。通道数最多可为8个。根据视频格式，仅允许这些参数的某些组合；各文件[IEC61834][SMPTE314M][SMPTE370M]中规定了限制条件。
A frame of data in the DV format stream is divided into several "DIF sequences". A DIF sequence is composed of an integral number of 80-byte DIF blocks. A DIF block is the primitive unit for all treatment of DV streams. Each DIF block contains a 3-byte ID header that specifies the type of the DIF block and its position in the DIF sequence. Five types of DIF blocks are defined: DIF sequence header, Subcode, Video Auxiliary (VAUX) information, Audio, and Video. Audio DIF blocks are composed of 5 bytes of Audio Auxiliary (AAUX) data and 72 bytes of audio data.
DV格式流中的数据帧被划分为若干“DIF序列”。DIF序列由整数个80字节的DIF块组成。DIF块是所有DV流处理的基本单元。每个DIF块都包含一个3字节的ID头，用于指定DIF块的类型及其在DIF序列中的位置。定义了五种类型的DIF块：DIF序列头、子码、视频辅助（VAUX）信息、音频和视频。音频DIF块由5字节的音频辅助（AAUX）数据和72字节的音频数据组成。
Each RTP packet starts with the RTP header as defined in RFC 3550 [RFC3550]. No additional payload-format-specific header is required for this payload format.
每个RTP数据包以RFC 3550[RFC3550]中定义的RTP报头开始。此有效负载格式不需要额外的有效负载格式特定标头。
The RTP header fields that have a meaning specific to the DV format are described as follows:
具有DV格式特定含义的RTP头字段描述如下：
Payload type (PT): The payload type is dynamically assigned by means outside the scope of this document. If multiple DV encoding formats are to be used within one RTP session, then multiple dynamic payload types MUST be assigned, one for each DV encoding format. The sender MUST change to the corresponding payload type whenever the encoding format is changed.
有效负载类型（PT）：有效负载类型通过本文档范围之外的方式动态分配。如果要在一个RTP会话中使用多个DV编码格式，则必须分配多个动态负载类型，每个DV编码格式一个。每当编码格式更改时，发送方必须更改为相应的有效负载类型。
Timestamp: 32-bit 90 kHz timestamp representing the time at which the first data in the frame was sampled. All RTP packets within the same video frame MUST have the same timestamp. The timestamp SHOULD increment by a multiple of the nominal interval for one DV frame time, as given in the following table:
时间戳：32位90 kHz时间戳，表示帧中第一个数据的采样时间。同一视频帧内的所有RTP数据包必须具有相同的时间戳。时间戳应增加一个DV帧时间的标称间隔的倍数，如下表所示：
+----------+----------------+---------------------------------------+
| Mode | Frame rate | Increase of 90 kHz timestamp per DV |
| | (Hz) | frame |
+----------+----------------+---------------------------------------+
| 525-60 | 29.97 | 3003 |
| 625-50 | 25 | 3600 |
| 1125-60 | 30 | 3000 |
| 1250-50 | 25 | 3600 |
| 1080-60i | 29.97 | 3003 |
| 1080-50i | 25 | 3600 |
| 720-60p | 59.94 | 3003(*) |
| 720-50p | 50 | 3600(*) |
+----------+----------------+---------------------------------------+
+----------+----------------+---------------------------------------+
| Mode | Frame rate | Increase of 90 kHz timestamp per DV |
| | (Hz) | frame |
+----------+----------------+---------------------------------------+
| 525-60 | 29.97 | 3003 |
| 625-50 | 25 | 3600 |
| 1125-60 | 30 | 3000 |
| 1250-50 | 25 | 3600 |
| 1080-60i | 29.97 | 3003 |
| 1080-50i | 25 | 3600 |
| 720-60p | 59.94 | 3003(*) |
| 720-50p | 50 | 3600(*) |
+----------+----------------+---------------------------------------+
(*) Note that even in the 720-line DV system, the data in two video frames shall be processed within one DV frame duration of the 1080- line system. Audio data and subcode data in the 720-line system are processed in the same way as the 1080-line system. Therefore, in the 720-line system, the timestamp increase given in the third column corresponds to two video frames time.
（*）注意，即使在720线DV系统中，两个视频帧中的数据也应在1080线系统的一个DV帧持续时间内处理。720线系统中的音频数据和子代码数据的处理方式与1080线系统相同。因此，在720行系统中，在第三列中给出的时间戳增加对应于两个视频帧时间。
Marker bit (M): The marker bit of the RTP fixed header is set to one on the last packet of a video frame; on other packets, it MUST be zero. The M bit allows the receiver to know that it has received the last packet of a frame so it can display the image without waiting for the first packet of the next frame to arrive to detect the frame
标记位（M）：RTP固定报头的标记位在视频帧的最后一个分组上设置为1；在其他数据包上，它必须为零。M位允许接收机知道它已经接收到帧的最后一个分组，因此它可以显示图像，而无需等待下一帧的第一个分组到达以检测帧
change. However, detection of a frame change MUST NOT rely on the marker bit since the last packet of the frame might be lost. Detection of a frame change MUST be based on a difference in the RTP timestamp.
改变然而，帧变化的检测不能依赖于标记位，因为帧的最后一个分组可能丢失。帧变化的检测必须基于RTP时间戳的差异。
Integral DIF blocks are placed into the RTP payload beginning immediately after the RTP header. Any number of DIF blocks may be packed into one RTP packet, but all DIF blocks in one RTP packet MUST be from the same video frame. DIF blocks from the next video frame MUST NOT be packed into the same RTP packet even if more payload space remains. This requirement stems from the fact that the transition from one video frame to the next is indicated by a change in the RTP timestamp. It also reduces the processing complexity on the receiver. Since the RTP payload contains an integral number of DIF blocks, the length of the RTP payload will be a multiple of 80 bytes.
整体DIF块被放置在RTP有效负载中，从RTP头之后立即开始。可以将任意数量的DIF块打包到一个RTP包中，但一个RTP包中的所有DIF块必须来自同一视频帧。来自下一视频帧的DIF块不得打包到同一RTP数据包中，即使还有更多有效负载空间。这一要求源于这样一个事实，即从一个视频帧到下一个视频帧的转换由RTP时间戳的变化表示。它还降低了接收机上的处理复杂度。由于RTP有效负载包含整数个DIF块，因此RTP有效负载的长度将是80字节的倍数。
Audio and video data may be transmitted as one bundled RTP stream or in separate RTP streams (unbundled). The choice MUST be indicated as part of the assignment of the dynamic payload type and MUST remain unchanged for the duration of the RTP session to avoid complicated procedures of sequence number synchronization. The RTP sender could omit the DIF sequence header and subcode DIF blocks from a stream when the information either is known from out-of-band sources or is not required for the application. Note that time code in DIF blocks is mandatory for professional video applications. When unbundled audio and video streams are sent, any DIF sequence header and subcode DIF blocks MUST be included and sent in the video stream.
音频和视频数据可以作为一个捆绑的RTP流或在单独的RTP流（非捆绑）中传输。选择必须作为动态有效负载类型分配的一部分进行指示，并且在RTP会话期间必须保持不变，以避免复杂的序列号同步过程。当信息从带外源已知或应用程序不需要时，RTP发送方可以从流中省略DIF序列头和子码DIF块。请注意，对于专业视频应用程序，DIF块中的时间代码是必需的。在发送未绑定的音频和视频流时，必须在视频流中包括并发送任何DIF序列头和子码DIF块。
DV streams include "source" and "source control" packs that carry information indispensable for proper decoding, such as video signal type, frame rate, aspect ratio, picture position, quantization of audio sampling, number of audio samples in a frame, number of audio channels, audio channel assignment, and language of the audio. However, describing all of these attributes with a signaling protocol would require large descriptions to enumerate all the combinations. Therefore, no Session Description Protocol (SDP) [RFC4566] parameters for these attributes are defined in this document. Instead, the RTP sender MUST transmit at least those VAUX (Video Auxiliary) DIF blocks and/or audio DIF blocks with AAUX (Audio Auxiliary) information bytes that include "source" and "source control" packs containing the indispensable information for decoding.
DV流包括“源”和“源控制”包，它们携带正确解码所必需的信息，例如视频信号类型、帧速率、纵横比、图片位置、音频采样的量化、帧中音频采样的数量、音频通道的数量、音频通道分配和音频语言。然而，用信令协议描述所有这些属性需要大量的描述来枚举所有的组合。因此，本文档中未定义这些属性的会话描述协议（SDP）[RFC4566]参数。相反，RTP发送方必须传输至少那些VAUX（视频辅助）DIF块和/或音频DIF块，其中AAUX（音频辅助）信息字节包括包含解码所需信息的“源”和“源控制”包。
In the case of one bundled stream, DIF blocks for both audio and video are packed into RTP packets in the same order as they were encoded.
在一个捆绑流的情况下，音频和视频的DIF块按照编码顺序打包到RTP包中。
In the case of an unbundled stream, only the header, subcode, video, and VAUX DIF blocks are sent within the video stream. Audio is sent in a different stream if desired, using a different RTP payload type. It is also possible to send audio duplicated in a separate stream, in addition to bundling it in with the video stream.
在非绑定流的情况下，仅在视频流中发送头、子代码、视频和VAUX DIF块。如果需要，音频将使用不同的RTP有效负载类型以不同的流发送。除了将音频与视频流捆绑在一起之外，还可以发送在单独流中复制的音频。
When using unbundled mode, it is RECOMMENDED that the audio stream data be extracted from the DIF blocks and repackaged into the corresponding RTP payload format for the audio encoding (DAT12, L16, L20) [RFC3551][RFC3190] in order to maximize interoperability with non-DV-capable receivers while maintaining the original source quality.
当使用非绑定模式时，建议从DIF块提取音频流数据，并将其重新打包为相应的RTP有效负载格式，用于音频编码（DAT12、L16、L20）[RFC3551][RFC3190]，以便在保持原始源质量的同时最大限度地提高与不支持DV的接收机的互操作性。
In the case of unbundled transmission that is compelled to use both audio and video in the DV format, the same timestamp SHOULD be used for both audio and video data within the same frame to simplify the lip synchronization effort on the receiver. Lip synchronization may also be achieved using reference timestamps passed in RTP Control Protocol (RTCP) as described in [RFC3550]. In this case, the audio stream uses the 90 kHz clock rate, and the timestamp uses the same clock rate as the video.
在强制使用DV格式的音频和视频的非绑定传输的情况下，相同帧内的音频和视频数据应使用相同的时间戳，以简化接收器上的lip同步工作。还可以使用在RTP控制协议（RTCP）中传递的参考时间戳来实现Lip同步，如[RFC3550]中所述。在这种情况下，音频流使用90khz时钟速率，时间戳使用与视频相同的时钟速率。
The sender MAY reduce the video frame rate by discarding the video data and VAUX DIF blocks for some of the video frames. The RTP timestamp MUST still be incremented to account for the discarded frames. The sender MAY alternatively reduce bandwidth by discarding video data DIF blocks for portions of the image that are unchanged from the previous image. To enable this bandwidth reduction, receivers SHOULD implement an error-concealment strategy to accommodate lost or missing DIF blocks, e.g., repeating the corresponding DIF block from the previous image.
发送方可以通过丢弃一些视频帧的视频数据和VAUX-DIF块来降低视频帧速率。RTP时间戳仍然必须增加，以考虑丢弃的帧。发送方可替代地通过丢弃与先前图像相同的图像部分的视频数据DIF块来减少带宽。为了实现这种带宽减少，接收机应实施错误隐藏策略，以适应丢失或丢失的DIF块，例如，重复前一图像中的相应DIF块。
This section specifies the parameters that MAY be used to select optional features of the payload format and certain features of the bitstream. The parameters are specified here as part of the media type registration for the DV encoding. A mapping of the parameters into the Session Description Protocol (SDP) [RFC4566] is also provided for applications that use SDP. Equivalent parameters could be defined elsewhere for use with control protocols that do not use SDP.
本节规定了可用于选择有效负载格式的可选特征和比特流的某些特征的参数。此处指定的参数是DV编码的媒体类型注册的一部分。还为使用SDP的应用程序提供了参数到会话描述协议（SDP）[RFC4566]的映射。可以在其他地方定义等效参数，以便与不使用SDP的控制协议一起使用。
This registration is done using the template defined in RFC 4288 [RFC4288] and following RFC 4855 [RFC4855].
此注册使用RFC 4288[RFC4288]中定义的模板和RFC 4855[RFC4855]中定义的模板完成。
Type name: video
类型名称：视频
Subtype name: DV
子类型名称：DV
Required parameters:
所需参数：
encode: type of DV format. Permissible values for encode are: SD-VCR/525-60 SD-VCR/625-50 HD-VCR/1125-60 HD-VCR/1250-50 SDL-VCR/525-60 SDL-VCR/625-50 314M-25/525-60 314M-25/625-50 314M-50/525-60 314M-50/625-50 370M/1080-60i 370M/1080-50i 370M/720-60p 370M/720-50p 306M/525-60 (for backward compatibility) 306M/625-50 (for backward compatibility)
编码：DV格式的类型。编码的允许值为：SD-VCR/525-60 SD-VCR/625-50 HD-VCR/1125-60 HD-VCR/1250-50 SDL-VCR/525-60 SDL-VCR/625-50 314M-25/525-60 314M-25/625-50 314M-50/625-60 314M-50/625-50 370M/1080-60i 370M/1080-50i 370M/720-60p 370M/525-60（向后兼容性）306M/525-50（向后兼容性）
Optional parameters:
可选参数：
audio: whether the DV stream includes audio data or not. Permissible values for audio are bundled and none. Defaults to none.
音频：DV流是否包含音频数据。音频的允许值是捆绑的，没有。默认为“无”。
Encoding considerations:
编码注意事项：
DV video can be transmitted with RTP as specified in RFC 6469 (this document). Other transport methods are not specified.
DV视频可以按照RFC 6469（本文件）的规定使用RTP传输。未指定其他运输方法。
Security considerations:
安全考虑：
See Section 4 of RFC 6469 (this document).
参见RFC 6469（本文件）第4节。
Interoperability considerations: Interoperability with previous implementations is discussed in Section 8.
互操作性注意事项：第8节讨论了与以前实现的互操作性。
Public specifications:
公开规格：
IEC 61834 Standard SMPTE 314M SMPTE 370M RFC 6469 (this document) SMPTE 306M (for backward compatibility)
IEC 61834标准SMPTE 314M SMPTE 370M RFC 6469（本文件）SMPTE 306M（用于向后兼容性）
Applications that use this media type: Audio and video streaming and conferencing tools.
使用此媒体类型的应用程序：音频和视频流媒体以及会议工具。
Additional information: NONE
其他信息：无
Person & email address to contact for further information:
联系人和电子邮件地址，以获取更多信息：
Katsushi Kobayashi ikob@riken.jp
小林克寿ikob@riken.jp
Intended usage: COMMON
预期用途：普通
Restrictions on usage: This media type depends on RTP framing and hence is only defined for transfer via RTP [RFC3550]. Transfer within other framing protocols is not defined at this time.
使用限制：此媒体类型取决于RTP帧，因此仅定义为通过RTP传输[RFC3550]。此时未定义其他帧协议内的传输。
Author:
作者：
Katsushi Kobayashi
小林克寿
Change controller:
更改控制器：
IETF Audio/Video Transport working group delegated from the IESG
IESG授权的IETF音频/视频传输工作组
Type name: audio
类型名称：音频
Subtype name: DV
子类型名称：DV
Required parameters:
所需参数：
encode: type of DV format. Permissible values for encode are: SD-VCR/525-60 SD-VCR/625-50 HD-VCR/1125-60 HD-VCR/1250-50 SDL-VCR/525-60 SDL-VCR/625-50
编码：DV格式的类型。编码的允许值为：SD-VCR/525-60 SD-VCR/625-50 HD-VCR/1125-60 HD-VCR/1250-50 SDL-VCR/525-60 SDL-VCR/625-50
314M-25/525-60 314M-25/625-50 314M-50/525-60 314M-50/625-50 370M/1080-60i 370M/1080-50i 370M/720-60p 370M/720-50p 306M/525-60 (for backward compatibility) 306M/625-50 (for backward compatibility)
314M-25/525-60 314M-25/625-50 314M-50/525-60 314M-50/625-50 370M/1080-60i 370M/1080-50i 370M/720-60p 370M/720-50p 306M/525-60（用于向后兼容性）306M/625-50（用于向后兼容性）
Optional parameters:
可选参数：
audio: whether the DV stream includes audio data or not. Permissible values for audio are bundled and none. Defaults to none.
音频：DV流是否包含音频数据。音频的允许值是捆绑的，没有。默认为“无”。
Encoding considerations:
编码注意事项：
DV audio can be transmitted with RTP as specified in RFC 6469 (this document). Other transport methods are not specified.
DV音频可以按照RFC 6469（本文件）的规定使用RTP传输。未指定其他运输方法。
Security considerations:
安全考虑：
See Section 4 of RFC 6469 (this document).
参见RFC 6469（本文件）第4节。
Interoperability considerations: Interoperability with previous implementations is discussed in Section 8.
互操作性注意事项：第8节讨论了与以前实现的互操作性。
Published specifications:
公布的规格：
IEC 61834 Standard SMPTE 314M SMPTE 370M RFC 6469 (this document) SMPTE 306M (for backward compatibility).
IEC 61834标准SMPTE 314M SMPTE 370M RFC 6469（本文件）SMPTE 306M（用于向后兼容性）。
Applications that use this media type: Audio and video streaming and conferencing tools.
使用此媒体类型的应用程序：音频和视频流媒体以及会议工具。
Additional information: NONE
其他信息：无
Person & email address to contact for further information:
联系人和电子邮件地址，以获取更多信息：
Katsushi Kobayashi ikob@riken.jp
小林克寿ikob@riken.jp
Intended usage: COMMON
预期用途：普通
Restrictions on usage: This media type depends on RTP framing and hence is only defined for transfer via RTP [RFC3550]. Transfer within other framing protocols is not defined at this time.
使用限制：此媒体类型取决于RTP帧，因此仅定义为通过RTP传输[RFC3550]。此时未定义其他帧协议内的传输。
Author:
作者：
Katsushi Kobayashi
小林克寿
Change controller:
更改控制器：
IETF Audio/Video Transport working group delegated from the IESG
IESG授权的IETF音频/视频传输工作组
The information carried in the media type specification has a specific mapping to fields in the Session Description Protocol (SDP), which is commonly used to describe RTP sessions. When SDP is used to specify sessions employing the DV encoding, the mapping is as follows:
媒体类型规范中包含的信息与会话描述协议（SDP）中的字段具有特定映射，SDP通常用于描述RTP会话。当使用SDP指定采用DV编码的会话时，映射如下：
o The media type ("video") goes in SDP "m=" as the media name.
o 媒体类型（“视频”）以SDP“m=”作为媒体名称。
o The media subtype ("DV") goes in SDP "a=rtpmap" as the encoding name. The RTP clock rate in "a=rtpmap" MUST be 90000, which for the payload format defined in this document is a 90 kHz clock.
o 媒体子类型（“DV”）以SDP“a=rtpmap”作为编码名称。“a=rtpmap”中的RTP时钟频率必须为90000，对于本文件中定义的有效负载格式，该频率为90 kHz时钟。
o Any remaining parameters go in the SDP "a=fmtp" attribute by copying them directly from the media type string as a semicolon-separated list of parameter=value pairs.
o 通过直接从媒体类型字符串中以分号分隔的参数=值对列表形式复制其余参数，将其放入SDP“a=fmtp”属性中。
In the DV video payload format, the "a=fmtp" line will be used to show the encoding type within the DV video and will be used as below:
在DV视频有效载荷格式中，“a=fmtp”行将用于显示DV视频中的编码类型，并将按如下方式使用：
a=fmtp:<payload type> encode=<DV-video encoding>
a=fmtp:<payload type> encode=<DV-video encoding>
The required parameter "encode" specifies which type of DV format is used. The DV format name will be one of the following values:
所需参数“encode”指定使用哪种类型的DV格式。DV格式名称将是以下值之一：
SD-VCR/525-60 SD-VCR/625-50 HD-VCR/1125-60 HD-VCR/1250-50 SDL-VCR/525-60 SDL-VCR/625-50 314M-25/525-60
SD-VCR/525-60 SD-VCR/625-50 HD-VCR/1125-60 HD-VCR/1250-50 SDL-VCR/525-60 SDL-VCR/625-50 314M-25/525-60
314M-25/625-50 314M-50/525-60 314M-50/625-50 370M/1080-60i 370M/1080-50i 370M/720-60p 370M/720-50p 306M/525-60 (for backward compatibility) 306M/625-50 (for backward compatibility)
314M-25/625-50 314M-50/525-60 314M-50/625-50 370M/1080-60i 370M/1080-50i 370M/720-60p 370M/720-50p 306M/525-60（用于向后兼容性）306M/625-50（用于向后兼容性）
In order to show whether or not the audio data is bundled into the DV stream, a format-specific parameter is defined:
为了显示音频数据是否捆绑到DV流中，定义了特定于格式的参数：
a=fmtp:<payload type> encode=<DV-video encoding> audio=<audio
bundled>
a=fmtp:<payload type> encode=<DV-video encoding> audio=<audio
bundled>
The optional parameter "audio" will be one of the following values:
可选参数“audio”将是以下值之一：
bundled none (default)
捆绑无（默认）
If the fmtp "audio" parameter is not present, then audio data MUST NOT be bundled into the DV video stream.
如果fmtp“audio”参数不存在，则不得将音频数据捆绑到DV视频流中。
The following considerations apply when using SDP offer/answer procedures [RFC3264] to negotiate the use of the DV payload in RTP:
当使用SDP提供/应答程序[RFC3264]协商RTP中DV有效负载的使用时，以下注意事项适用：
o The "encode" parameter can be used for sendrecv, sendonly, and recvonly streams. Each encode type MUST use a separate payload type number.
o “encode”参数可用于sendrecv、sendonly和RecVoOnly流。每个编码类型必须使用单独的有效负载类型编号。
o Any unknown parameter in an offer MUST be ignored by the receiver and MUST NOT be included in the answer.
o 接收方必须忽略报价中的任何未知参数，且不得将其包含在答案中。
In an offer for unbundled streams, the group attribute as defined in the Session Description Protocol (SDP) Grouping Framework [RFC5888] can be used in order to associate the related audio and video. The example usage of SDP grouping is detailed in [RFC5888].
在非绑定流的报价中，可以使用会话描述协议（SDP）分组框架[RFC5888]中定义的组属性来关联相关音频和视频。SDP分组的示例用法详见[RFC5888]。
Some example SDP session descriptions utilizing DV encoding formats follow.
下面是使用DV编码格式的一些示例SDP会话描述。
When using unbundled mode, the RTP streams for video and audio will be sent separately to different ports or different multicast groups. When unbundled audio and video streams are sent, SDP carries several "m=" lines, one for each media type of the session (see [RFC4566]).
使用非绑定模式时，视频和音频的RTP流将分别发送到不同的端口或不同的多播组。发送未绑定的音频和视频流时，SDP会携带多条“m=”行，会话的每种媒体类型对应一条（请参见[RFC4566]）。
An example SDP description using these attributes is:
使用这些属性的SDP说明示例如下：
v=0
o=ikob 2890844526 2890842807 IN IP4 192.0.2.1
s=POI Seminar
i=A Seminar on how to make Presentations on the Internet
u=http://www.example.net/~ikob/POI/index.html
e=ikob@example.net (Katsushi Kobayashi)
c=IN IP4 233.252.0.1/127
t=2873397496 2873404696
m=audio 49170 RTP/AVP 112
a=rtpmap:112 L16/32000/2
m=video 50000 RTP/AVP 113
a=rtpmap:113 DV/90000
a=fmtp:113 encode=SD-VCR/525-60 audio=none
v=0
o=ikob 2890844526 2890842807 IN IP4 192.0.2.1
s=POI Seminar
i=A Seminar on how to make Presentations on the Internet
u=http://www.example.net/~ikob/POI/index.html
e=ikob@example.net (Katsushi Kobayashi)
c=IN IP4 233.252.0.1/127
t=2873397496 2873404696
m=audio 49170 RTP/AVP 112
a=rtpmap:112 L16/32000/2
m=video 50000 RTP/AVP 113
a=rtpmap:113 DV/90000
a=fmtp:113 encode=SD-VCR/525-60 audio=none
This describes a session where audio and video streams are sent separately. The session is sent to a multicast group 233.252.0.1. The audio is sent using L16 format, and the video is sent using SD-VCR 525/60 format, which corresponds to NTSC format in consumer DV.
这描述了音频和视频流分别发送的会话。会话被发送到多播组233.252.0.1。音频使用L16格式发送，视频使用SD-VCR 525/60格式发送，该格式对应于消费者DV中的NTSC格式。
When sending a bundled stream, all the DIF blocks including system data will be sent through a single RTP stream.
当发送捆绑流时，包括系统数据在内的所有DIF块将通过单个RTP流发送。
An example SDP description for a bundled DV stream is:
捆绑DV流的示例SDP描述为：
v=0
o=ikob 2890844526 2890842807 IN IP4 192.0.2.1
s=POI Seminar
i=A Seminar on how to make Presentations on the Internet
u=http://www.example.net/~ikob/POI/index.html
e=ikob@example.net (Katsushi Kobayashi)
c=IN IP4 233.252.0.1/127
t=2873397496 2873404696
m=video 49170 RTP/AVP 112 113
a=rtpmap:112 DV/90000
a=fmtp:112 encode=SD-VCR/525-60 audio=bundled
a=fmtp:113 encode=314M-50/525-60 audio=bundled
v=0
o=ikob 2890844526 2890842807 IN IP4 192.0.2.1
s=POI Seminar
i=A Seminar on how to make Presentations on the Internet
u=http://www.example.net/~ikob/POI/index.html
e=ikob@example.net (Katsushi Kobayashi)
c=IN IP4 233.252.0.1/127
t=2873397496 2873404696
m=video 49170 RTP/AVP 112 113
a=rtpmap:112 DV/90000
a=fmtp:112 encode=SD-VCR/525-60 audio=bundled
a=fmtp:113 encode=314M-50/525-60 audio=bundled
This SDP record describes a session where audio and video streams are sent bundled. The session is sent to a multicast group 233.252.0.1. The video is sent using both 525/60 consumer DV and SMPTE standard 314M 50 Mbit/s formats, when the payload type is 112 and 113, respectively.
此SDP记录描述捆绑发送音频和视频流的会话。会话被发送到多播组233.252.0.1。当有效负载类型分别为112和113时，使用525/60消费者DV和SMPTE标准314M 50 Mbit/s格式发送视频。
RTP packets using the payload format defined in this specification are subject to the security considerations discussed in the RTP specification [RFC3550] and any appropriate RTP profile. This implies that confidentiality of the media streams is achieved by encryption. Because the data compression used with this payload format is applied end-to-end, encryption may be performed after compression so there is no conflict between the two operations.
使用本规范中定义的有效负载格式的RTP数据包应遵守RTP规范[RFC3550]和任何适当RTP配置文件中讨论的安全注意事项。这意味着媒体流的机密性是通过加密实现的。由于与此有效负载格式一起使用的数据压缩是端到端应用的，因此可以在压缩之后执行加密，因此两个操作之间没有冲突。
A potential denial-of-service threat exists for data encodings using compression techniques that have non-uniform receiver-end computational load. The attacker can inject pathological datagrams into the stream that are complex to decode and cause the receiver to be overloaded. However, this encoding does not exhibit any significant non-uniformity.
使用压缩技术的数据编码存在潜在的拒绝服务威胁，这种压缩技术具有非均匀的接收端计算负载。攻击者可以向流中注入难以解码的病理数据报，并导致接收器过载。然而，这种编码并没有表现出任何显著的非均匀性。
As with any IP-based protocol, in some circumstances, a receiver may be overloaded simply by the receipt of too many packets, either desired or undesired. Network-layer authentication may be used to discard packets from undesired sources, but the processing cost of the authentication itself may be too high. In a multicast environment, mechanisms for joining and pruning of specific sources are specified in IGMPv3, Multicast Listener Discovery Version 2 (MLDv2) [RFC3376][RFC3810] or Lightweight-IGMPv3 (LW-IGMPv3), LW-MLDv2 [RFC5790] and in multicast routing protocols to allow a receiver to select which sources are allowed to reach it [RFC4607].
与任何基于IP的协议一样，在某些情况下，接收机可能仅仅因为接收了太多的数据包而过载，不管是想要的还是不想要的。网络层认证可用于丢弃来自不希望的源的数据包，但认证本身的处理成本可能过高。在多播环境中，在IGMPv3、多播侦听器发现版本2（MLDv2）[RFC3376][RFC3810]或轻量级IGMPv3（LW-IGMPv3）、LW-MLDv2[RFC5790]和多播路由协议中指定了加入和修剪特定源的机制，以允许接收机选择允许哪些源到达它[RFC4607]。
The general congestion control considerations for transporting RTP data apply; see RTP [RFC3550] and any applicable RTP profile like Audio-Visual Profile (AVP) [RFC3551].
传输RTP数据的一般拥塞控制注意事项适用；请参阅RTP[RFC3550]和任何适用的RTP配置文件，如视听配置文件（AVP）[RFC3551]。
This document obsoletes [RFC3189], and some registration forms have been updated by this document. The registration forms (based on the RFC 4855 [RFC4855] definition) for the media types for both video and audio are shown in Section 3.1.
本文件废除了[RFC3189]，一些登记表已通过本文件更新。视频和音频媒体类型的登记表（基于RFC 4855[RFC4855]定义）如第3.1节所示。
The changes from [RFC3189] are:
[RFC3189]的变化如下：
1. Specified that support for SMPTE 306M is only for backward interoperability, since it is covered by SMPTE 314M format.
1. 指定对SMPTE 306M的支持仅用于向后互操作性，因为它包含在SMPTE 314M格式中。
2. Added SMPTE 370M 100 Mbit/s High Definition Television (HDTV) (1080/60i, 1080/50i, 720/60p, and 720/50p) format.
2. 增加了SMPTE 370M 100 Mbit/s高清电视（HDTV）（1080/60i、1080/50i、720/60p和720/50p）格式。
3. Incorporated the Source-Specific Multicast (SSM) specification for avoiding overloaded traffic source in multicast usage. Added a reference to the Source-Specific Multicast (SSM) specification as a way to reduce unwanted traffic in a multicast application.
3. 合并了源特定多播（SSM）规范，以避免多播使用中的过载流量源。添加了对源特定多播（SSM）规范的引用，作为减少多播应用程序中不需要的通信量的一种方法。
4. Clarified the case where a sender omits subcode DIF block data from the stream.
4. 澄清了发送方从流中省略子代码DIF块数据的情况。
5. Added considerations for the offer/answer model.
5. 为提供/应答模型添加了注意事项。
6. Revised media types registration form based on new registration rule [RFC4855].
6. 基于新注册规则[RFC4855]修订的媒体类型注册表。
In this section, we discuss interoperability with implementations based on [RFC3189], which is obsoleted by this document.
在本节中，我们将讨论与基于[RFC3189]的实现的互操作性，该实现已被本文档淘汰。
[RFC3189] regards SMPTE 306M [SMPTE306M] and SMPTE 314M [SMPTE314M] as different encoding formats, although the format of SMPTE 306M is already covered by SMPTE 314M. Therefore, this document recommends that the definition depending on SMPTE 306M SHOULD NOT be used, and SMPTE 314M SHOULD be used instead. An RTP application could handle a stream identified in SMPTE 306M encoding as SMPTE 314M encoding instead.
[RFC3189]将SMPTE 306M[SMPTE 306M]和SMPTE 314M[SMPTE 314M]视为不同的编码格式，尽管SMPTE 314M已经涵盖了SMPTE 306M的格式。因此，本文件建议不使用取决于SMPTE 306M的定义，而应使用SMPTE 314M。RTP应用程序可以处理SMPTE 306M编码中标识为SMPTE 314M编码的流。
An offer MAY include SMPTE 306M encoding coming from a legacy system, and receivers SHOULD support this value.
报价可能包括来自遗留系统的SMPTE 306M编码，接收机应支持该值。
If an initial offer that did not include SMPTE 306M was rejected, the offerer MAY try a new offer with SMPTE 306M. For this case, an RTP application MAY handle a stream identified in SMPTE 306M encoding as SMPTE 314M encoding instead.
如果不包括SMPTE 306M的初始报价被拒绝，报价人可以尝试使用SMPTE 306M的新报价。对于这种情况，RTP应用程序可以处理SMPTE 306M编码中标识为SMPTE 314M编码的流。
In addition, the SDP examples in [RFC3189] provide incorrect SDP "a=fmtp" attribute usage.
此外，[RFC3189]中的SDP示例提供了不正确的SDP“a=fmtp”属性用法。
Thanks to Akimichi Ogawa, a former author of this document.
感谢本文件的前作者小川秋美。
[IEC61834] IEC, "IEC 61834, Helical-scan digital video cassette recording system using 6,35 mm magnetic tape for consumer use (525-60, 625-50, 1125-60 and 1250-50 systems)".
[IEC61834]IEC，“IEC 61834，使用6.35mm磁带的消费者用螺旋扫描数字盒式录像系统（525-60、625-50、1125-60和1250-50系统）”。
[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月。
[RFC3190] Kobayashi, K., Ogawa, A., Casner, S., and C. Bormann, "RTP Payload Format for 12-bit DAT Audio and 20- and 24-bit Linear Sampled Audio", RFC 3190, January 2002.
[RFC3190]Kobayashi，K.，Ogawa，A.，Casner，S.，和C.Bormann，“12位DAT音频和20位和24位线性采样音频的RTP有效负载格式”，RFC 31902002年1月。
[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月。
[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月。
[RFC3551] Schulzrinne, H. and S. Casner, "RTP Profile for Audio and Video Conferences with Minimal Control", STD 65, RFC 3551, July 2003.
[RFC3551]Schulzrinne，H.和S.Casner，“具有最小控制的音频和视频会议的RTP配置文件”，STD 65，RFC 3551，2003年7月。
[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月。
[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月。
[RFC4855] Casner, S., "Media Type Registration of RTP Payload Formats", RFC 4855, February 2007.
[RFC4855]Casner，S.，“RTP有效负载格式的媒体类型注册”，RFC 48552007年2月。
[RFC5888] Camarillo, G. and H. Schulzrinne, "The Session Description Protocol (SDP) Grouping Framework", RFC 5888, June 2010.
[RFC5888]Camarillo，G.和H.Schulzrinne，“会话描述协议（SDP）分组框架”，RFC 5888，2010年6月。
[SMPTE306M] SMPTE, "SMPTE 306M, 6.35-mm Type D-7 Component Format - Video Compression at 25Mb/s - 525/60 and 625/50".
[SMPTE306M]SMPTE，“SMPTE306M，6.35-mm D-7型组件格式-25Mb/s的视频压缩-525/60和625/50”。
[SMPTE314M] SMPTE, "SMPTE 314M, Data Structure for DV-Based Audio and Compressed Video - 25 and 50Mb/s".
[SMPTE314M]SMPTE，“SMPTE314M，基于DV的音频和压缩视频数据结构-25和50Mb/s”。
[SMPTE370M] SMPTE, "SMPTE 370M, Data Structure for DV-Based Audio, Data and Compressed Video at 100 Mb/s 1080/ 60i, 1080/50i, 720/60p, and 720/50p".
[SMPTE370M]SMPTE，“SMPTE370M，100MB/s 1080/60i、1080/50i、720/60p和720/50p下基于DV的音频、数据和压缩视频的数据结构”。
[IEC61883] IEC, "IEC 61883, Consumer audio/video equipment - Digital interface".
[IEC61883]IEC，“IEC 61883，消费者音频/视频设备-数字接口”。
[IEEE1394] IEEE, "IEEE Std 1394-1995, Standard for a High Performance Serial Bus".
[IEEE1394]IEEE，“IEEE标准1394-1995，高性能串行总线标准”。
[ISO/IEC11172] ISO/IEC, "ISO/IEC 11172, Coding of moving pictures and associated audio for digital storage media up to about 1,5 Mbit/s".
[ISO/IEC11172]ISO/IEC，“ISO/IEC 11172，高达约1.5 Mbit/s的数字存储媒体的运动图像和相关音频编码”。
[ISO/IEC13818] ISO/IEC, "ISO/IEC 13818, Generic coding of moving pictures and associated audio information".
[ISO/IEC13818]ISO/IEC，“ISO/IEC 13818，运动图像和相关音频信息的通用编码”。
[RFC2250] Hoffman, D., Fernando, G., Goyal, V., and M. Civanlar, "RTP Payload Format for MPEG1/MPEG2 Video", RFC 2250, January 1998.
[RFC2250]Hoffman，D.，Fernando，G.，Goyal，V.，和M.Civanlar，“MPEG1/MPEG2视频的RTP有效载荷格式”，RFC 2250，1998年1月。
[RFC3189] Kobayashi, K., Ogawa, A., Casner, S., and C. Bormann, "RTP Payload Format for DV (IEC 61834) Video", RFC 3189, January 2002.
[RFC3189]Kobayashi，K.，Ogawa，A.，Casner，S.，和C.Bormann，“DV（IEC 61834）视频的RTP有效载荷格式”，RFC 3189，2002年1月。
[RFC3376] Cain, B., Deering, S., Kouvelas, I., Fenner, B., and A. Thyagarajan, "Internet Group Management Protocol, Version 3", RFC 3376, October 2002.
[RFC3376]Cain，B.，Deering，S.，Kouvelas，I.，Fenner，B.，和A.Thyagarajan，“互联网组管理协议，第3版”，RFC 3376，2002年10月。
[RFC3810] Vida, R. and L. Costa, "Multicast Listener Discovery Version 2 (MLDv2) for IPv6", RFC 3810, June 2004.
[RFC3810]Vida，R.和L.Costa，“IPv6多播侦听器发现版本2（MLDv2）”，RFC 3810，2004年6月。
[RFC4607] Holbrook, H. and B. Cain, "Source-Specific Multicast for IP", RFC 4607, August 2006.
[RFC4607]Holbrook，H.和B.Cain，“IP的源特定多播”，RFC4607，2006年8月。
[RFC5790] Liu, H., Cao, W., and H. Asaeda, "Lightweight Internet Group Management Protocol Version 3 (IGMPv3) and Multicast Listener Discovery Version 2 (MLDv2) Protocols", RFC 5790, February 2010.
[RFC5790]Liu，H.，Cao，W.，和H.Asaeda，“轻量级Internet组管理协议版本3（IGMPv3）和多播侦听器发现版本2（MLDv2）协议”，RFC 57902010年2月。
Authors' Addresses
作者地址
Katsushi Kobayashi Advanced Institute for Computational Science, RIKEN 7-1-26 Minatojima-minami Chuo-ku, Kobe, Hyogo 760-0045 Japan
日本兵库县神户市Minatojima minami Chuo ku里肯7-1-26小林善纪计算科学高级研究所760-0045
EMail: ikob@riken.jp
EMail: ikob@riken.jp
Kazuhiro Mishima Keio University 5322 Endo Fujisawa, Kanagawa 252-8520 Japan
三岛和弘庆应大学5322藤泽内，神奈川252-8520日本
EMail: three@sfc.wide.ad.jp
EMail: three@sfc.wide.ad.jp
Stephen L. Casner Packet Design 2455 Augustine Drive Santa Clara, CA 95054 United States
美国加利福尼亚州圣克拉拉奥古斯丁大道2455号Stephen L.Casner包装设计公司，邮编95054
EMail: casner@acm.org
EMail: casner@acm.org
Carsten Bormann Universitaet Bremen TZI Postfach 330440 D-28334, Bremen Germany
德国不来梅卡斯滕·鲍曼大学邮政学院330440 D-28334
Phone: +49 421 218 63921
Fax: +49 421 218 7000
EMail: cabo@tzi.org
Phone: +49 421 218 63921
Fax: +49 421 218 7000
EMail: cabo@tzi.org