Network Working Group B. Haberman
Request for Comments: 5186 Johns Hopkins University
Category: Informational J. Martin
Woven Systems
May 2008
Network Working Group B. Haberman
Request for Comments: 5186 Johns Hopkins University
Category: Informational J. Martin
Woven Systems
May 2008
Internet Group Management Protocol Version 3 (IGMPv3) / Multicast Listener Discovery Version 2 (MLDv2) and Multicast Routing Protocol Interaction
Internet组管理协议版本3（IGMPv3）/多播侦听器发现版本2（MLDv2）和多播路由协议交互
Status of This Memo
关于下段备忘
This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.
本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。本备忘录的分发不受限制。
Abstract
摘要
The definitions of the Internet Group Management Protocol Version 3 (IGMPv3) and Multicast Listener Discovery Version 2 (MLDv2) require new behavior within the multicast routing protocols. The additional source information contained in IGMPv3 and MLDv2 messages necessitates that multicast routing protocols manage and utilize the information. This document describes how multicast routing protocols will interact with these source-filtering group management protocols.
Internet组管理协议版本3（IGMPv3）和多播侦听器发现版本2（MLDv2）的定义要求在多播路由协议中有新的行为。IGMPv3和MLDv2消息中包含的附加源信息要求多播路由协议管理和利用这些信息。本文档描述了多播路由协议如何与这些源过滤组管理协议交互。
The definitions of IGMPv3 [IGMP3] and MLDv2 [MLDv2] require new behavior within the multicast routing protocols. The additional source information contained in IGMPv3 and MLDv2 messages necessitates that multicast routing protocols manage and utilize the information. This document will describe how multicast routing protocols will interpret information learned from these source-filtering group management protocols.
IGMPv3[IGMP3]和MLDv2[MLDv2]的定义要求在多播路由协议中有新的行为。IGMPv3和MLDv2消息中包含的附加源信息要求多播路由协议管理和利用这些信息。本文档将描述多播路由协议如何解释从这些源过滤组管理协议中获得的信息。
Existing multicast routing protocols utilize the group management database in determining if local members exist for a particular multicast group. With previous group management protocols, this database had one type of record indicating the group for which there was interest and the associated local interfaces.
现有的多播路由协议利用组管理数据库来确定特定多播组是否存在本地成员。对于以前的组管理协议，该数据库有一种类型的记录，指示感兴趣的组和相关的本地接口。
In the case of IGMPv3 and MLDv2, these routing protocols may now build multicast forwarding state based on the source filter information available for each multicast group that has local membership. This requires that the group management database have four record types. Only one record may exist for a given interface and a given multicast group.
在IGMPv3和MLDv2的情况下，这些路由协议现在可以基于可用于具有本地成员资格的每个多播组的源过滤器信息来构建多播转发状态。这要求组管理数据库具有四种记录类型。给定接口和给定多播组只能存在一条记录。
1. EXCLUDE <> The EXCLUDE <> record indicates interest in all sources destined to this group address for a set of local interfaces. It is equivalent to the single record type existing in previous versions of the group management protocols.
1. EXCLUDE<>EXCLUDE<>记录表示对一组本地接口的所有发送到此组地址的源感兴趣。它相当于以前版本的组管理协议中存在的单一记录类型。
2. INCLUDE <> The INCLUDE <> record indicates that there is no interest in any sources destined to this group address for a set of local interfaces.
2. INCLUDE<>INCLUDE<>记录表明，对于一组本地接口，对发送到此组地址的任何源不感兴趣。
3. EXCLUDE <list> The EXCLUDE <list> record indicates that there is interest in all sources other than the specifically listed sources for a set of local interfaces.
3. EXCLUDE<list>EXCLUDE<list>记录表示除了一组本地接口的特定列出的源之外，对所有源都感兴趣。
4. INCLUDE <list> The INCLUDE <list> record indicates that there is interest in only the specifically listed sources for a set of local interfaces.
4. INCLUDE<list>INCLUDE<list>记录表明，对于一组本地接口，只对特定列出的源感兴趣。
The records in the group management database should be utilized when generating forwarding state for a multicast group. If the source address in the multicast packet exists in the database for the specified multicast group and is in an INCLUDE list or is not listed in an EXCLUDE list, the multicast routing protocol should add the interface to the list of downstream interfaces; otherwise, it should not be added based on local group membership.
为多播组生成转发状态时，应使用组管理数据库中的记录。如果多播分组中的源地址存在于指定多播组的数据库中，并且在包含列表中或未在排除列表中列出，则多播路由协议应将该接口添加到下游接口列表中；否则，不应基于本地组成员身份添加它。
The Distance Vector Multicast Routing Protocol (DVMRP) [DVMRP] does not incorporate any knowledge of the multicast group's senders. Therefore, DVMRP will act only on the multicast group address contained in an IGMPv3 or MLDv2 report.
距离向量多播路由协议（DVMRP）[DVMRP]不包含多播组发送方的任何知识。因此，DVMRP将仅作用于IGMPv3或MLDv2报告中包含的多播组地址。
Future standardized versions of DVMRP may incorporate pruning and grafting messages similar to PIM-DM (discussed in Section 5). The rules defined in Section 5 can be applied in this situation.
DVMRP的未来标准化版本可能包含类似于PIM-DM的修剪和嫁接消息（在第5节中讨论）。第5节中定义的规则可适用于这种情况。
In Multicast Extensions to OSPF (MOSPF) [MOSPF], the consideration of source filter information in the group management database is limited to the building of forwarding state (discussed above). This is due to the flooding of group-membership-LSAs within MOSPF.
在OSPF（MOSPF）[MOSPF]的多播扩展中，组管理数据库中源过滤器信息的考虑仅限于转发状态的构建（如上所述）。这是由于MOSPF中的群体成员LSA泛滥。
The PIM-DM protocol [PIMDM] interaction with a source-filtering group management protocol is important in two areas: multicast distribution tree pruning and multicast distribution tree grafting. The following sections will describe the behavior needed in PIM-DM to interoperate with IGMPv3 and MLDv2.
PIM-DM协议[PIMDM]与源过滤组管理协议的交互在两个方面很重要：多播分发树修剪和多播分发树嫁接。以下部分将描述PIM-DM中与IGMPv3和MLDv2互操作所需的行为。
PIM-DM prune messages are initiated when a PIM-DM router determines that there are no entities interested in the data flowing on the (S,G) forwarding state. If the multicast router is running IGMPv3 or MLDv2, this is determined by the source S being in EXCLUDE state in the source filter for the destination G, or all interest in G being terminated for an existing (S,G) forwarding entry.
当PIM-DM路由器确定没有实体对（S，G）转发状态上的数据流感兴趣时，PIM-DM修剪消息被启动。如果多播路由器正在运行IGMPv3或MLDv2，则这是由目标G的源过滤器中的源S处于排除状态，或由现有（S，G）转发条目终止对G的所有兴趣决定的。
PIM-DM graft messages are sent in order to override an existing PIM-DM prune. In the case of IGMPv3 or MLDv2, this occurs when prune state exists for (S,G) and a state change occurs in which the source filter state for S changes to INCLUDE for the specified G.
发送PIM-DM嫁接消息是为了覆盖现有的PIM-DM修剪。在IGMPv3或MLDv2的情况下，当（S，G）存在删减状态并且发生状态更改时，会发生这种情况，其中S的源过滤器状态更改为包括指定的G。
A PIM-SM interaction takes place when a PM-SM [PIMSM] router receives an IGMP or MLD message regarding a group address that is in the Any Source Multicast (ASM) range. This range is defined as the entire multicast address space excluding the global SSM range [SSM] and any locally defined Source Specific space.
当PM-SM[PIMSM]路由器接收到关于任意源多播（ASM）范围内的组地址的IGMP或MLD消息时，PIM-SM交互发生。此范围定义为整个多播地址空间，不包括全局SSM范围[SSM]和任何本地定义的源特定空间。
PIM-SM join messages are initiated when a PIM-SM router determines that there are entities interested in a specific group or a specific source sending to the group. If this is due to an IGMPv3 or MLDv2 report with a zero-length EXCLUDE list, then the join is sent as a (*,G) join towards the RP.
当PIM-SM路由器确定存在对特定组感兴趣的实体或发送到该组的特定源时，PIM-SM加入消息将启动。如果这是由于具有零长度排除列表的IGMPv3或MLDv2报告造成的，则连接将作为（*，G）连接发送到RP。
If the join is triggered by an IGMPv3 or MLDv2 state change that affects source information, the PIM-SM join is sent as a (S,G) join towards the specific source. This behavior optimizes the join process, as well as facilitates the adoption of the SSM model. The generation of this (S,G) join can cause failures in architectures where leaf routers do not have global reachability, and thus, can be overridden by local policy. If this is the case, then all triggered joins are sent towards the RP as (*,G) joins. The router sending the (*,G) join is responsible for filtering the data as per the IGMPv3 database before forwarding.
如果连接是由影响源信息的IGMPv3或MLDv2状态更改触发的，则PIM-SM连接将作为（S，G）连接发送到特定源。这种行为优化了连接过程，并促进了SSM模型的采用。这种（S，G）连接的生成可能会在叶路由器不具有全局可达性的体系结构中导致故障，因此可以被本地策略覆盖。如果是这种情况，则所有触发的联接都将作为（*，G）联接发送到RP。发送（*，G）连接的路由器负责在转发之前根据IGMPv3数据库过滤数据。
PIM-SM prune messages are initiated when a PIM-SM router determines that there are no entities interested in a specific group, or a specific source sending to the group. If this is triggered by either receiving a report with an EXCLUDE or if a specific Source/Group times out, then an (S,G) prune is sent towards the upstream router. If all of the IGMPv3 or MLDv2 derived requests for a group time out, then (S,G) and (*,G) prunes are sent upstream as needed to stop all flow of traffic for that group.
当PIM-SM路由器确定不存在对特定组感兴趣的实体或发送到该组的特定源时，会启动PIM-SM修剪消息。如果这是通过接收带有排除的报告或特定源/组超时触发的，则向上游路由器发送（S，G）修剪。如果针对组超时的所有IGMPv3或MLDv2派生请求，则根据需要向上游发送（S，G）和（*，G）修剪，以停止该组的所有流量。
A PIM-SSM interaction takes place when a PIM-SM router receives an IGMPv3 or MLDv2 message regarding a group address that is in the Source Specific Multicast range. This behavior is not defined in this document, but rather in [PIMSM].
当PIM-SM路由器收到关于源特定多播范围内的组地址的IGMPv3或MLDv2消息时，PIM-SSM交互发生。此行为未在本文档中定义，而是在[PIMSM]中定义。
This document does not introduce any additional security issues above and beyond those already discussed in [PIMDM], [PIMSM], [IGMP3], and [MLDv2].
除[PIMDM]、[PIMSM]、[IGMP3]和[MLDv2]中已经讨论的安全问题外，本文档不介绍任何其他安全问题。
The authors would like to thank Murali Brahmadesam, Leonard Giuliano, and Hal Sandick for their feedback and suggestions.
作者要感谢Murali Brahmadesam、Leonard Giuliano和Hal Sandick的反馈和建议。
[IGMP3] Cain, B., Deering, S., Kouvelas, I., Fenner, B., and A. Thyagarajan, "Internet Group Management Protocol, Version 3", RFC 3376, October 2002.
[IGMP3]Cain，B.，Deering，S.，Kouvelas，I.，Fenner，B.，和A.Thyagarajan，“互联网组管理协议，第3版”，RFC 3376，2002年10月。
[MLDv2] Vida, R., Ed., and L. Costa, Ed., "Multicast Listener Discovery Version 2 (MLDv2) for IPv6", RFC 3810, June 2004.
[MLDv2]Vida，R.，Ed.，和L.Costa，Ed.，“IPv6的多播侦听器发现版本2（MLDv2）”，RFC 3810，2004年6月。
[DVMRP] Waitzman, D., Partridge, C., and S. Deering, "Distance Vector Multicast Routing Protocol", RFC 1075, November 1988.
[DVMRP]Waitzman，D.，Partridge，C.，和S.Deering，“距离向量多播路由协议”，RFC 1075，1988年11月。
[MOSPF] Moy, J., "Multicast Extensions to OSPF", RFC 1584, March 1994.
[MOSPF]Moy，J.，“OSPF的多播扩展”，RFC1584，1994年3月。
[PIMDM] Adams, A., Nicholas, J., and W. Siadak, "Protocol Independent Multicast - Dense Mode (PIM-DM): Protocol Specification (Revised)", RFC 3973, January 2005.
[PIMDM]Adams，A.，Nicholas，J.，和W.Siadak，“协议独立多播-密集模式（PIM-DM）：协议规范（修订版）”，RFC 3973，2005年1月。
[PIMSM] Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas, "Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)", RFC 4601, August 2006.
[PIMSM]Fenner，B.，Handley，M.，Holbrook，H.，和I.Kouvelas，“协议独立多播-稀疏模式（PIM-SM）：协议规范（修订版）”，RFC 4601，2006年8月。
[SSM] Holbrook, H. and B. Cain, "Source-Specific Multicast for IP", RFC 4607, August 2006.
[SSM]Holbrook，H.和B.Cain，“IP的源特定多播”，RFC 4607，2006年8月。
Authors' Addresses
作者地址
Brian Haberman The Johns Hopkins University Applied Physics Laboratory 11100 Johns Hopkins Road Laurel, MD 20723-6099 US
布莱恩·哈伯曼，约翰·霍普金斯大学应用物理实验室，美国马里兰州劳雷尔市约翰·霍普金斯路11100号，20723-6099
Phone: +1 443 778 1319
EMail: brian@innovationslab.net
Phone: +1 443 778 1319
EMail: brian@innovationslab.net
Jim Martin Woven Systems 2455 Augustine Drive, Suite 211 Santa Clara, CA 95054 US
Jim Martin Woven Systems美国加利福尼亚州圣克拉拉市奥古斯丁大道2455号211室95054
Phone: +1 408 654-8143
EMail: jim@wovensystems.com
Phone: +1 408 654-8143
EMail: jim@wovensystems.com
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.