Internet Engineering Task Force (IETF) E. Rosen, Ed.
Request for Comments: 6625 Cisco Systems, Inc.
Updates: 6514 Y. Rekhter, Ed.
Category: Standards Track Juniper Networks, Inc.
ISSN: 2070-1721 W. Henderickx
Alcatel-Lucent
R. Qiu
Huawei
May 2012
Internet Engineering Task Force (IETF) E. Rosen, Ed.
Request for Comments: 6625 Cisco Systems, Inc.
Updates: 6514 Y. Rekhter, Ed.
Category: Standards Track Juniper Networks, Inc.
ISSN: 2070-1721 W. Henderickx
Alcatel-Lucent
R. Qiu
Huawei
May 2012
Wildcards in Multicast VPN Auto-Discovery Routes
多播VPN自动发现路由中的通配符
Abstract
摘要
In Multicast Virtual Private Networks (MVPNs), customer multicast flows are carried in "tunnels" through a service provider's network. The base specifications for MVPN define BGP multicast VPN "auto-discovery routes" and specify how to use an auto-discovery route to advertise the fact that an individual customer multicast flow is being carried in a particular tunnel. However, those specifications do not provide a way to specify, in a single such route, that multiple customer flows are being carried in a single tunnel. Those specifications also do not provide a way to advertise that a particular tunnel is to be used by default to carry all customer flows, except in the case where that tunnel is joined by all the provider edge routers of the MVPN. This document eliminates these restrictions by specifying the use of "wildcard" elements in the customer flow identifiers. With wildcard elements, a single auto-discovery route can refer to multiple customer flows or even to all customer flows.
在多播虚拟专用网络（MVPN）中，客户多播流通过服务提供商的网络在“隧道”中传输。MVPN的基本规范定义了BGP多播VPN“自动发现路由”，并指定了如何使用自动发现路由来公布单个客户多播流正在特定隧道中传输的事实。然而，这些规范并没有提供一种方法来规定在一条这样的路线中，在一条隧道中承载多个客户流。这些规范也没有提供一种方式来宣传默认情况下将使用特定隧道来承载所有客户流，除非该隧道由MVPN的所有提供商边缘路由器连接。本文档通过在客户流标识符中指定“通配符”元素的使用，消除了这些限制。使用通配符元素，单个自动发现路由可以引用多个客户流，甚至可以引用所有客户流。
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/rfc6625.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc6625.
Copyright Notice
版权公告
Copyright (c) 2012 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2012 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许可证中所述的无担保。
Table of Contents
目录
1. Introduction ....................................................3
1.1. Terminology ................................................3
1.2. Wildcards in S-PMSI A-D Routes .............................5
1.3. Use Cases ..................................................5
2. Encoding of Wildcards ...........................................7
3. Finding the Matching S-PMSI A-D Route ...........................8
3.1. Finding the Match for Data Transmission ....................8
3.2. Finding the Match for Data Reception .......................9
3.2.1. Finding the Match for (C-S,C-G) .....................9
3.2.2. Finding the Wildcard Match for (C-*,C-G) ............9
4. Procedures for S-PMSI A-D Routes with Wildcards ................10
4.1. Procedures for All Kinds of Wildcards .....................10
4.2. Procedures for (C-*,C-G) S-PMSI A-D Routes ................11
4.3. Procedures for (C-S,C-*) S-PMSI A-D Routes ................12
4.4. Procedures for (C-*,C-*) S-PMSI A-D Routes ................13
5. Security Considerations ........................................15
6. Acknowledgments ................................................15
7. Normative References ...........................................15
1. Introduction ....................................................3
1.1. Terminology ................................................3
1.2. Wildcards in S-PMSI A-D Routes .............................5
1.3. Use Cases ..................................................5
2. Encoding of Wildcards ...........................................7
3. Finding the Matching S-PMSI A-D Route ...........................8
3.1. Finding the Match for Data Transmission ....................8
3.2. Finding the Match for Data Reception .......................9
3.2.1. Finding the Match for (C-S,C-G) .....................9
3.2.2. Finding the Wildcard Match for (C-*,C-G) ............9
4. Procedures for S-PMSI A-D Routes with Wildcards ................10
4.1. Procedures for All Kinds of Wildcards .....................10
4.2. Procedures for (C-*,C-G) S-PMSI A-D Routes ................11
4.3. Procedures for (C-S,C-*) S-PMSI A-D Routes ................12
4.4. Procedures for (C-*,C-*) S-PMSI A-D Routes ................13
5. Security Considerations ........................................15
6. Acknowledgments ................................................15
7. Normative References ...........................................15
In Multicast Virtual Private Networks (MVPNs), customer multicast flows are carried in tunnels through a service provider's network. The base specifications for MVPN define BGP multicast VPN "auto-discovery routes" and specify how to use an auto-discovery route to advertise the fact that an individual customer multicast flow is being carried in a particular tunnel. However, those specifications do not provide a way to specify, in a single such route, that multiple customer flows are being carried in a single tunnel. Those specifications also do not provide a way to advertise that a particular tunnel is to be used by default to carry all customer flows, except in the case where that tunnel is joined by all the provider edge routers of the MVPN. This document eliminates these restrictions by specifying the use of "wildcard" elements in the customer flow identifiers. With wildcard elements, a single auto-discovery route can refer to multiple customer flows or even to all customer flows.
在多播虚拟专用网络（MVPN）中，客户多播流通过服务提供商的网络在隧道中传输。MVPN的基本规范定义了BGP多播VPN“自动发现路由”，并指定了如何使用自动发现路由来公布单个客户多播流正在特定隧道中传输的事实。然而，这些规范并没有提供一种方法来规定在一条这样的路线中，在一条隧道中承载多个客户流。这些规范也没有提供一种方式来宣传默认情况下将使用特定隧道来承载所有客户流，除非该隧道由MVPN的所有提供商边缘路由器连接。本文档通过在客户流标识符中指定“通配符”元素的使用，消除了这些限制。使用通配符元素，单个自动发现路由可以引用多个客户流，甚至可以引用所有客户流。
This document uses terminology from [MVPN] and, in particular, uses the prefixes "C-" and "P-", as specified in Section 3.1 of [MVPN], to distinguish addresses in the "customer address space" from addresses in the "provider address space". The following terminology and acronyms are particularly important in this document:
本文件使用[MVPN]中的术语，尤其是[MVPN]第3.1节中规定的前缀“C-”和“P-”，以区分“客户地址空间”中的地址与“提供商地址空间”中的地址。以下术语和首字母缩略词在本文件中尤为重要：
- MVPN
- MVPN
Multicast Virtual Private Network -- a VPN [L3VPN] in which multicast service is offered.
多播虚拟专用网——提供多播服务的VPN[L3VPN]。
- VRF
- VRF
VPN Routing and Forwarding table [L3VPN].
VPN路由和转发表[L3VPN]。
- SP
- 服务提供商
Service Provider.
服务提供商。
- P-tunnel
- P型隧道
A tunnel through the network of one or more SPs.
通过一个或多个SP的网络的隧道。
- C-S
- C-S
Multicast Source. A multicast source address, in the address space of a customer network.
多播源。客户网络地址空间中的多播源地址。
- C-G
- C-G
Multicast Group. A multicast group address (destination address) in the address space of a customer network.
多播组。客户网络地址空间中的多播组地址（目标地址）。
- C-multicast flow or C-flow
- C-多播流还是C-流
A customer multicast flow. Each C-flow is identified by the ordered pair (source address, group address), where each address is in the customer's address space. The identifier of a particular C-flow is usually written as (C-S,C-G).
客户多播流。每个C流由有序对（源地址、组地址）标识，其中每个地址位于客户的地址空间中。特定C流的标识符通常写为（C-S，C-G）。
- RP
- 反相
A "Rendezvous Point", as defined in [PIM].
[PIM]中定义的“会合点”。
- C-RP
- C-RP
A Rendezvous Point whose address is in the customer's address space.
地址在客户地址空间中的集合点。
- Selective P-tunnel
- 选择性P隧道
A P-tunnel that is joined only by Provider Edge (PE) routers that need to receive one or more of the C-flows that are traveling through that P-tunnel.
仅由提供商边缘（PE）路由器连接的P隧道，该路由器需要接收通过该P隧道的一个或多个C流。
- Inclusive P-tunnel
- 包容性P隧道
A P-tunnel that is joined by all PE routers that attach to sites of a given MVPN.
由连接到给定MVPN站点的所有PE路由器连接的P隧道。
- S-PMSI A-D route
- S-PMSI A-D路由
Selective Provider Multicast Service Interface Auto-Discovery route. Carried in BGP Update messages, these routes are used to advertise the fact that particular C-flows are bound to (i.e., are traveling through) particular P-tunnels.
选择性提供者多播服务接口自动发现路由。在BGP更新消息中，这些路由用于通告特定C流绑定到（即通过）特定P隧道的事实。
Familiarity with multicast concepts and terminology [PIM] is also presupposed.
还需要熟悉多播概念和术语[PIM]。
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 [RFC2119].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照[RFC2119]中所述进行解释。
As specified in [MVPN] and [MVPN-BGP], an S-PMSI A-D route advertises that a particular C-flow is bound to a particular selective P-tunnel.
如[MVPN]和[MVPN-BGP]中所述，S-PMSI A-D路由通告特定C流绑定到特定选择性P隧道。
The identifier of the specified C-flow, e.g., (C-S,C-G), is encoded into the Network Layer Reachability Information (NLRI) of the S-PMSI A-D route. The identifier of the specified P-tunnel is encoded into an attribute (the "PMSI Tunnel Attribute") of the S-PMSI A-D route. Each S-PMSI A-D route thus specifies a single C-flow. To bind multiple C-flows to a single P-tunnel, it is necessary to advertise one S-PMSI A-D route for each C-flow, specifying the same P-tunnel in each such route.
指定的C流的标识符，例如（C-S，C-g），被编码到S-PMSI A-D路由的网络层可达性信息（NLRI）中。指定P隧道的标识符被编码到S-PMSI A-D路由的属性（“PMSI隧道属性”）中。因此，每个S-PMSI A-D路由指定一个C-flow。要将多个C-flow绑定到单个P-tunnel，需要为每个C-flow发布一个S-PMSI a-D路由，并在每个此类路由中指定相同的P-tunnel。
This document defines OPTIONAL extensions to the procedures and encodings specified in [MVPN] and [MVPN-BGP]. These extensions enable a single S-PMSI A-D route to advertise that multiple C-multicast flows are bound to a single P-tunnel.
本文件定义了[MVPN]和[MVPN-BGP]中规定的程序和编码的可选扩展。这些扩展使单个S-PMSI a-D路由能够通告多个C多播流绑定到单个P隧道。
The extensions specified in this document are based on the notion of allowing the NLRI of an S-PMSI A-D route to contain a "wildcard". In the NLRI encoding, a wildcard can replace the C-S, the C-G, or both. We use the notation "C-*" to denote a wildcard. The extensions allow the NLRI to encode three kinds of wildcards: (C-*,C-*), (C-S,C-*), and (C-*,C-G).
本文档中指定的扩展基于允许S-PMSI A-D路由的NLRI包含“通配符”的概念。在NLRI编码中，通配符可以替换C-S、C-G或两者。我们使用符号“C-*”来表示通配符。扩展允许NLRI编码三种通配符：（C-*，C-*），（C-S，C-*）和（C-*，C-G）。
By using wildcards, a PE may be able to reduce the number of S-PMSI A-D routes it originates, thereby improving the scalability of the control plane. There is, however, no impact on data plane scalability, as the number of P-tunnels is not reduced.
通过使用通配符，PE可以减少其发起的S-PMSI a-D路由的数量，从而提高控制平面的可伸缩性。但是，这对数据平面的可伸缩性没有影响，因为P隧道的数量没有减少。
Encoding and detailed procedures are specified in subsequent sections of this document.
本文件后续章节中规定了编码和详细程序。
There are a number of situations in which it can be useful to use wildcards in the NLRI of an S-PMSI A-D route.
在许多情况下，在S-PMSI a-D路由的NLRI中使用通配符非常有用。
- Using a selective P-tunnel as the default tunnel.
- 使用选择性P通道作为默认通道。
There are procedures in [MVPN] and [MVPN-BGP] that allow a PE to advertise that it is going to use an inclusive P-tunnel as the P-tunnel on which it will transmit all C-flows by "default". However, those documents do not provide any way for a PE to advertise that it is going to use a selective P-tunnel as the P-tunnel on which it will transmit all C-flows by "default". Using the extensions defined in this document, a PE can
[MVPN]和[MVPN-BGP]中有一些程序允许PE宣布它将使用一个包含性P隧道作为P隧道，在“默认情况下”，它将在该P隧道上传输所有C流。然而，这些文件并没有为PE提供任何方式来宣传其将使用选择性P隧道作为P隧道，在“默认情况下”在其上传输所有C流。使用本文档中定义的扩展，PE可以
advertise that it is going to use a selective P-tunnel as its default P-tunnel. It does so by advertising an S-PMSI A-D route whose NLRI contains (C-*,C-*).
宣传它将使用选择性P通道作为其默认P通道。它通过宣传其NLRI包含（C-*，C-*）的S-PMSI A-D路由来实现。
- Binding multiple C-flows traveling along a customer's Protocol Independent Multicast - Sparse Mode (PIM-SM) shared tree to a single P-tunnel.
- 将沿着客户的协议独立多播稀疏模式（PIM-SM）共享树的多个C流绑定到单个P隧道。
A PE router may be connected to an MVPN site that contains a customer RP (C-RP). The C-RP may be the root of one or more shared trees. In multicast terminology, these are known as (*,G) trees. By advertising a single S-PMSI A-D route whose NLRI contains the (C-*,C-G) wildcard, the PE can bind all the C-flows traveling along a customer's (*,G) tree to a single P-tunnel. This use case applies only when C-G is a non-bidirectional ASM (Any Source Multicast) group.
PE路由器可以连接到包含客户RP（C-RP）的MVPN站点。C-RP可以是一个或多个共享树的根。在多播术语中，这些树称为（*，G）树。通过宣传其NLRI包含（C-*，C-G）通配符的单个S-PMSI a-D路由，PE可以将沿着客户（*，G）树的所有C流绑定到单个P隧道。此用例仅适用于C-G是非双向ASM（任何源多播）组的情况。
- Binding multiple C-flows with the same C-group address to a single P-tunnel, even if each such C-flow is traveling along a customer's PIM source tree.
- 将具有相同C组地址的多个C流绑定到单个P隧道，即使每个这样的C流沿着客户的PIM源树移动。
A PE router may be connected to an MVPN site containing several multicast sources that are all sending to a common multicast group, along a customer's PIM source trees. Alternatively, the PE may be connected to several sites, each containing at least one source sending to the common multicast group. By advertising a single S-PMSI A-D route whose NLRI contains (C-*,C-G), the PE can bind these C-flows to a single P-tunnel.
PE路由器可以连接到MVPN站点，该MVPN站点包含多个多播源，这些多播源沿着客户的PIM源树发送到公共多播组。或者，PE可以连接到多个站点，每个站点包含至少一个发送到公共多播组的源。通过宣传NLRI包含（C-*，C-G）的单个S-PMSI a-D路由，PE可以将这些C流绑定到单个P隧道。
This use case applies only when the C-group is a non-bidirectional ASM group.
此用例仅在C组为非双向ASM组时适用。
- Binding multiple C-flows with the same C-group address to a single P-tunnel, when those C-flows are traveling along a customer's BIDIR-PIM shared tree.
- 当多个C流沿着客户的BIDIR-PIM共享树移动时，将具有相同C组地址的多个C流绑定到单个P隧道。
This use case applies only when the C-group is a BIDIR-PIM group.
此用例仅适用于C组为BIDIR-PIM组的情况。
- Binding multiple C-flows from a given C-source to a given P-tunnel, irrespective of whether those C-flows all have the same C-group address.
- 将多个C流从给定的C源绑定到给定的P隧道，而不管这些C流是否都具有相同的C组地址。
This can be useful when the C-group addresses are SSM (Single Source Multicast) addresses. Suppose, for example, that a given source transmits multiple "channels" of information, each with
当C组地址是SSM（单源多播）地址时，这非常有用。例如，假设一个给定的源传输多个信息“通道”，每个通道都有
its own C-group address. It may be desirable to bind all these channels to a single P-tunnel, without having to advertise an S-PMSI A-D route for each one.
它自己的C组地址。可能需要将所有这些信道绑定到单个P隧道，而不必为每个P隧道宣传S-PMSI a-D路由。
Of course, a specific C-flow, (C-S,C-G), can always be assigned individually to a particular P-tunnel by advertising an S-PMSI A-D route whose NLRI contains (C-S,C-G).
当然，通过宣传其NLRI包含（C-S，C-G）的S-PMSI a-D路线，可以始终将特定的C-flow（C-S，C-G）单独分配给特定的P-tunnel。
In Section 4, we will sometimes speak of an S-PMSI A-D route being ignored. When we say the route is "ignored", we do not mean that its normal BGP processing is not done, but that the route is not considered when determining which P-tunnel to use when receiving multicast data, and that the MPLS label values it conveys are not used. We will use "ignore" in quotes to indicate this meaning.
在第4节中，我们有时会提到忽略S-PMSI A-D路由。当我们说路由被“忽略”时，我们并不是说它的正常BGP处理没有完成，而是说在确定接收多播数据时使用哪个P隧道时没有考虑路由，并且没有使用它传递的MPLS标签值。我们将在引号中使用“忽略”来表示这一含义。
This document provides procedures only for the case where the P-tunnels are "unidirectional", i.e., point-to-multipoint. The use of "bidirectional" (multipoint-to-multipoint) P-tunnels is outside the scope of this document.
本文件仅提供P型隧道为“单向”即点对多点的情况下的程序。“双向”（多点对多点）P-隧道的使用不在本文件范围内。
Per [MVPN-BGP] Section 4.3, the MCAST-VPN NLRI in an S-PMSI A-D route is encoded as follows:
根据[MVPN-BGP]第4.3节，S-PMSI A-D路由中的MCAST-VPN NLRI编码如下：
+-----------------------------------+
| RD (8 octets) |
+-----------------------------------+
| Multicast Source Length (1 octet) |
+-----------------------------------+
| Multicast Source (variable) |
+-----------------------------------+
| Multicast Group Length (1 octet) |
+-----------------------------------+
| Multicast Group (variable) |
+-----------------------------------+
| Originating Router's IP Addr |
+-----------------------------------+
+-----------------------------------+
| RD (8 octets) |
+-----------------------------------+
| Multicast Source Length (1 octet) |
+-----------------------------------+
| Multicast Source (variable) |
+-----------------------------------+
| Multicast Group Length (1 octet) |
+-----------------------------------+
| Multicast Group (variable) |
+-----------------------------------+
| Originating Router's IP Addr |
+-----------------------------------+
where the "source length" and "group length" fields always have a non-zero value. This document specifies that a "zero-length" source or group represents the corresponding wildcard. Specifically,
其中“源长度”和“组长度”字段始终具有非零值。本文档指定“零长度”源或组表示相应的通配符。明确地
- A source wildcard is encoded as a zero-length source field. That is, the "multicast source length" field contains the value 0x00, and the "multicast source" field is omitted.
- 源通配符编码为零长度源字段。也就是说，“多播源长度”字段包含值0x00，“多播源”字段被省略。
- A group wildcard is encoded as a zero-length group field. That is, the "multicast group length" field contains the value 0x00, and the "multicast group" field is omitted.
- 组通配符编码为零长度组字段。也就是说，“多播组长度”字段包含值0x00，“多播组”字段被省略。
This section gives the precise rules for determining the S-PMSI A-D route that is "matched" by a given (C-S,C-G) or (C-*,C-G). The procedures in Section 4 will make use of the matching rules defined in this section.
本节给出了确定由给定（C-S，C-G）或（C-*，C-G）“匹配”的S-PMSI A-D路由的精确规则。第4节中的程序将使用本节中定义的匹配规则。
All matching rules assume the context of a given VRF at a given PE.
所有匹配规则都假定给定PE上给定VRF的上下文。
The rules that a PE applies to find the S-PMSI A-D route that matches a (C-S,C-G) C-flow that it needs to transmit are slightly different than the rules it applies to find the S-PMSI A-D route that matches a (C-S,C-G) C-flow that it needs to receive. These rules are specified in Sections 3.1 and 3.2, respectively.
PE用于查找与其需要传输的（C-S，C-G）C-flow匹配的S-PMSI a-D路由的规则与用于查找与其需要接收的（C-S，C-G）C-flow匹配的S-PMSI a-D路由的规则略有不同。这些规则分别在第3.1节和第3.2节中规定。
The S-PMSI A-D route that is matched by a given (C-S,C-G) may change over time, as the result of S-PMSI A-D routes being withdrawn or as a result of new S-PMSI A-D routes being originated and/or advertised. In particular, if (C-S,C-G) matches an S-PMSI A-D route whose NLRI contains (C-*,C-*), the origination or reception of an S-PMSI A-D route whose NLRI contains (C-S,C-G) may cause (C-S,C-G) to match the latter route instead. Note also that the S-PMSI A-D route that matches a given (C-S,C-G) is independent of the order in which the routes were originated or received.
与给定（C-S，C-G）匹配的S-PMSI A-D路由可能会随着时间的推移而改变，这是由于S-PMSI A-D路由被撤回或由于新的S-PMSI A-D路由被发起和/或公布。特别是，如果（C-S，C-G）匹配NLRI包含（C-*，C-*）的S-PMSI A-D路由，则其NLRI包含（C-S，C-G）的S-PMSI A-D路由的发起或接收可能导致（C-S，C-G）与后一路由匹配。还请注意，与给定（C-S，C-G）匹配的S-PMSI A-D路由独立于路由发起或接收的顺序。
Consider a given PE; call it PE1. At any given time, for a given VRF at PE1, there is a (possibly empty) set of S-PMSI A-D routes that PE1 has originated and advertised, but not withdrawn. We will refer to these routes as "currently originated" by PE1. Suppose that PE1 needs to transmit a particular C-flow (C-S,C-G) to one or more other PEs. We use the following algorithm to find the S-PMSI A-D route that the C-flow "matches":
考虑一个给定的体育；叫它PE1。在任何给定时间，对于PE1处的给定VRF，有一组（可能是空的）S-PMSI a-D路由，PE1已发起并公布，但未撤回。我们将这些路线称为PE1的“当前起源”。假设PE1需要将特定的C流（C-S，C-G）传输到一个或多个其他PE。我们使用以下算法查找C流“匹配”的S-PMSI A-D路由：
- If there is an S-PMSI A-D route currently originated by PE1, whose NLRI contains (C-S,C-G), the (C-S,C-G) C-flow matches that route.
- 如果存在PE1当前发起的S-PMSI A-D路由，其NLRI包含（C-S，C-G），则（C-S，C-G）C-flow与该路由匹配。
- Otherwise, if there is an S-PMSI A-D route currently originated by PE1, whose NLRI contains (C-S,C-*), AND if C-G is an SSM group address, the (C-S,C-G) C-flow matches that route.
- 否则，如果存在由PE1当前发起的S-PMSI A-D路由，其NLRI包含（C-S，C-*），并且如果C-G是SSM组地址，则（C-S，C-G）C-flow与该路由匹配。
- Otherwise, if there is an S-PMSI A-D route currently originated by PE1, whose NLRI contains (C-*,C-G), AND if C-G is an ASM group address, the (C-S,C-G) C-flow matches that route.
- 否则，如果有一个S-PMSI A-D路由当前由PE1发起，其NLRI包含（C-*，C-G），并且如果C-G是ASM组地址，则（C-S，C-G）C-flow与该路由匹配。
- Otherwise, if there is an S-PMSI A-D route currently originated by PE1, whose NLRI contains (C-*,C-*), the (C-S,C-G) C-flow matches that route.
- 否则，如果有一个S-PMSI A-D路由当前由PE1发起，其NLRI包含（C-*，C-*），则（C-S，C-G）C流与该路由匹配。
We refer to an S-PMSI A-D route as being "installed" (in a given VRF) if it has been selected by the BGP decision process as the preferred route for its NLRI.
如果BGP决策过程选择S-PMSI A-D路由作为其NLRI的首选路由，则我们将其称为“已安装”（在给定VRF中）。
An S-PMSI A-D route is considered to be "originated by a given PE" if that PE's IP address is contained in the "Originating Router's IP Address" field in the MCAST-VPN NLRI of the route.
如果S-PMSI A-D路由的IP地址包含在该路由的MCAST-VPN NLRI中的“始发路由器的IP地址”字段中，则该路由被视为“由给定PE发起”。
Suppose that a PE router (call it PE1) needs to receive (C-S,C-G), and that PE1 has chosen another PE router (call it PE2) as the "upstream PE" [MVPN] for that flow.
假设一个PE路由器（称为PE1）需要接收（C-S，C-G），并且PE1选择了另一个PE路由器（称为PE2）作为该流的“上游PE”[MVPN]。
- If there is an installed S-PMSI A-D route originated by PE2, whose NLRI contains (C-S,C-G), then (C-S,C-G) matches that route.
- 如果存在由PE2发起的已安装的S-PMSI A-D路由，其NLRI包含（C-S，C-G），则（C-S，C-G）与该路由匹配。
- Otherwise, if there is an installed S-PMSI A-D route originated by PE2, whose NLRI contains (C-S,C-*), AND if C-G is an SSM multicast group address, then (C-S,C-G) matches that route.
- 否则，如果存在由PE2发起的已安装的S-PMSI A-D路由，其NLRI包含（C-S，C-*），并且如果C-G是SSM多播组地址，则（C-S，C-G）匹配该路由。
- Otherwise, if there is an installed S-PMSI A-D route originated by PE2, whose NLRI contains (C-*,C-G), AND if C-G is an ASM multicast group address, then (C-S,C-G) matches that route.
- 否则，如果存在由PE2发起的已安装的S-PMSI A-D路由，其NLRI包含（C-*，C-G），并且如果C-G是ASM多播组地址，则（C-S，C-G）与该路由匹配。
- Otherwise, if there is an installed S-PMSI A-D route originated by PE2, whose NLRI contains (C-*,C-*), then (C-S,C-G) matches that route.
- 否则，如果存在由PE2发起的已安装的S-PMSI A-D路由，其NLRI包含（C-*，C-*），则（C-S，C-G）与该路由匹配。
Suppose that a PE router (call it PE1) needs to receive (C-*,C-G) traffic. Note that even if (C-*,C-G) matches a non-wildcard S-PMSI A-D route (as detailed in Section 12.3 of [MVPN-BGP]), it may also match one or more wildcard S-PMSI A-D routes, as specified below.
假设一个PE路由器（称为PE1）需要接收（C-*，C-G）流量。注意，即使（C-*，C-G）匹配非通配符S-PMSI a-D路由（详见[MVPN-BGP]第12.3节），也可能匹配一个或多个通配符S-PMSI a-D路由，如下所述。
If on PE1 there is an installed S-PMSI A-D route originated by PE2, whose NLRI contains (C-*,C-G), then (C-*,C-G) matches this route if one of the following conditions holds:
如果在PE1上安装了由PE2发起的S-PMSI A-D路由，其NLRI包含（C-*，C-G），则（C-*，C-G）与该路由匹配，前提是以下条件之一成立：
- PE1 determines that PE2 is the "upstream" PE [MVPN] for the C-RP of C-G, or
- PE1确定PE2是C-G的C-RP的“上游”PE[MVPN]，或
- PE1 has installed one or more Source Active A-D routes for C-G originated by PE2, and for at least one of these routes, PE1 does not have a corresponding (C-S,C-G) state, or
- PE1已经为PE2发起的C-G安装了一个或多个源活动A-D路由，并且对于这些路由中的至少一个，PE1没有相应的（C-S，C-G）状态，或者
- C-G is a BIDIR-PIM group, or
- C-G是BIDIR-PIM集团，或
- Source Active A-D routes are not being used.
- 未使用源活动A-D路由。
If (C-*,C-G) does not match a (C-*,C-G) S-PMSI A-D route from PE2, but PE1 has an installed (C-*,C-*) S-PMSI A-D route from PE2, then (C-*,C-G) matches the (C-*,C-*) route if one of the following conditions holds:
如果（C-*，C-G）与来自PE2的（C-*，C-G）S-PMSI a-D路线不匹配，但PE1已安装了来自PE2的（C-*，C-*）S-PMSI a-D路线，则如果以下条件之一成立，则（C-*，C-G）与（C-*，C-*）路线匹配：
- PE1 determines that PE2 is the "upstream" PE [MVPN] for the C-RP of C-G, or
- PE1确定PE2是C-G的C-RP的“上游”PE[MVPN]，或
- PE1 has installed one or more Source Active A-D routes for C-G originated by PE2, and for at least one of these routes, PE1 does not have a corresponding (C-S,C-G) state, or
- PE1已经为PE2发起的C-G安装了一个或多个源活动A-D路由，并且对于这些路由中的至少一个，PE1没有相应的（C-S，C-G）状态，或者
- C-G is a BIDIR-PIM group, or
- C-G是BIDIR-PIM集团，或
- Source Active A-D routes are not being used.
- 未使用源活动A-D路由。
This document defines procedures for the following uses of the wildcard in the NLRI of an S-PMSI A-D route:
本文件定义了S-PMSI A-D路由NLRI中通配符的以下使用程序：
- (C-*,C-G): Source wildcard, group specified.
- （C-*，C-G）：源通配符，指定的组。
- (C-S,C-*): Source specified, group wildcard.
- （C-S，C-*）：指定的源，组通配符。
- (C-*,C-*): Source wildcard, group wildcard.
- （C-*，C-*）：源通配符，组通配符。
All other wildcard functionality is outside the scope of this document.
所有其他通配符功能不在本文档范围内。
The ability to originate S-PMSI A-D routes with a particular kind of wildcard is OPTIONAL. However, if a PE has the ability to originate S-PMSI A-D routes with a particular kind of wildcard, it MUST have the ability to interpret and correctly process S-PMSI A-D routes with that kind of wildcard, and it SHOULD have the ability to interpret and correctly process all three kinds of wildcards.
使用特定类型的通配符创建S-PMSI A-D路由的能力是可选的。但是，如果PE能够使用特定类型的通配符创建S-PMSI a-D路由，则它必须能够使用该类型的通配符解释和正确处理S-PMSI a-D路由，并且它应该能够解释和正确处理所有三种类型的通配符。
For a given MVPN, A PE MUST NOT originate S-PMSI A-D routes with a particular kind of wildcard unless it is known a priori that all PEs attached to that MVPN have the ability to interpret and correctly process that kind of wildcard.
对于给定的MVPN，PE不得使用特定类型的通配符发起S-PMSI a-D路由，除非事先知道连接到该MVPN的所有PE都能够解释和正确处理该类型的通配符。
The criteria for originating and withdrawing S-PMSI A-D routes with wildcards are local to the originating PE.
使用通配符发起和撤销S-PMSI A-D路由的标准是发起PE的本地标准。
As specified in [MVPN-BGP], an S-PMSI A-D route is carried in the NLRI field of an MP_REACH_NLRI attribute (see [BGP-MP]). Every S-PMSI A-D route has a particular address family (IPv4 or IPv6), as specified in the Address Family Identifier (AFI) field of the MP_REACH_NLRI attribute. A wildcard in a particular S-PMSI A-D route always refers only to multicast flows of that same address family.
如[MVPN-BGP]中所述，S-PMSI A-D路由在MP_REACH_NLRI属性的NLRI字段中携带（请参见[BGP-MP]）。每个S-PMSI A-D路由都有一个特定的地址族（IPv4或IPv6），如MP_REACH_NLRI属性的地址族标识符（AFI）字段中所指定。特定S-PMSI A-D路由中的通配符始终仅指同一地址族的多播流。
The procedures specified in this document apply only when the PMSI Tunnel Attribute of an S-PMSI A-D route specifies a "unidirectional" P-tunnel. The use of "bidirectional" P-tunnels (e.g., Multipoint-to-Multipoint Label Switched Paths, BIDIR-PIM trees) is outside the scope of this document.
本文件中规定的程序仅适用于S-PMSI A-D路线的PMSI隧道属性指定“单向”P隧道的情况。“双向”P-隧道（例如，多点到多点标签交换路径、BIDIR-PIM树）的使用不在本文件范围内。
In the following sections, an S-PMSI A-D route whose NLRI contains (C-*,C-G), (C-S,C-*), or (C-*,C-*) will be referred to as a "(C-*,C-G) route", a "(C-S,C-*) route", or a "(C-*,C-*)" route, respectively.
在以下章节中，其NLRI包含（C-*，C-G）、（C-S，C-*）或（C-*，C-*）的S-PMSI A-D路线将分别称为“（C-*，C-G）路线、“C-S，C-*）路线”或“（C-*，C-*）”路线。
This document specifies the use of (C-*,C-G) S-PMSI A-D routes only in the case where C-G is an ASM group address. Use of (C-*,C-G) S-PMSI A-D routes where C-G is an SSM group address is outside the scope of this document. If a PE receives a (C-*,C-G) S-PMSI A-D route, and the PE can determine that C-G is an SSM group address, the PE SHOULD "ignore" this S-PMSI A-D route.
本文件规定仅在C-G是ASM组地址的情况下使用（C-*，C-G）S-PMSI A-D路由。如果C-G是SSM组地址，则使用（C-*，C-G）S-PMSI A-D路由不在本文件范围内。如果PE接收到（C-*，C-G）S-PMSI a-D路由，并且PE可以确定C-G是SSM组地址，则PE应“忽略”该S-PMSI a-D路由。
By default, the set of Route Targets carried by a (C-*,C-G) S-PMSI A-D route originated by a given VRF is the same as the set of Route Targets carried in the (unicast) VPN-IP routes that originated from that VRF. An implementation MUST allow the set of Route Targets
默认情况下，由给定VRF发起的（C-*，C-G）S-PMSI a-D路由携带的路由目标集与由该VRF发起的（单播）VPN-IP路由携带的路由目标集相同。实现必须允许路由目标集
carried by the (C-*,C-G) S-PMSI A-D route to be specified by configuration. In the absence of a configured set of Route Targets, the route MUST carry the default set of Route Targets.
由配置指定的（C-*，C-G）S-PMSI A-D路线承载。如果没有一组已配置的路由目标，则路由必须包含一组默认路由目标。
If a PE needs to transmit packets of a (C-S,C-G) C-flow, and if (C-S,C-G) matches a (C-*,C-G) S-PMSI A-D route according to the rules of Section 3.1, then the PE MUST use the P-tunnel advertised in this route for transmitting that C-flow. (Note that it is impossible for a given (C-S,C-G) to match both a (C-*,C-G) wildcard and a (C-S,C-*) wildcard.)
如果PE需要传输（C-S，C-G）C-flow的数据包，并且根据第3.1节的规则，如果（C-S，C-G）与（C-*，C-G）S-PMSI a-D路由匹配，则PE必须使用该路由中公布的P-tunnel来传输该C-flow。（请注意，给定的（C-S，C-G）不可能同时匹配（C-*，C-G）通配符和（C-S，C-*）通配符。）
If PIM is being used as the PE-PE control protocol, then if the PE has (C-*,C-G) and/or (C-S,C-G) state that matches (according to the procedures of Section 3.2) an S-PMSI A-D route, the PE MUST join the P-tunnel specified in the PMSI Tunnel Attribute of that route.
如果PIM被用作PE-PE控制协议，则如果PE具有（C-*，C-G）和/或（C-S，C-G）状态，且与S-PMSI A-D路由匹配（根据第3.2节的程序），则PE必须加入该路由的PMSI隧道属性中指定的P隧道。
If BGP is being used as the PE-PE control protocol, then
如果BGP用作PE-PE控制协议，则
- If a given PE has currently originated a C-multicast Shared Tree Join for (C-*,C-G), and if (C-*,C-G) matches a (C-*,C-G) S-PMSI A-D route, then the PE applies the procedures of Section 12.3 ("Receiving S-PMSI A-D Routes by PEs") of [MVPN-BGP] to that S-PMSI A-D route.
- 如果给定PE当前已为（C-*，C-G）发起C-多播共享树连接，并且如果（C-*，C-G）匹配（C-*，C-G）S-PMSI a-D路由，则PE将[MVPN-BGP]第12.3节（“PEs接收S-PMSI a-D路由”）中的程序应用于该S-PMSI a-D路由。
- Otherwise (the given PE does not have a currently originated C-multicast Shared Tree Join for (C-*,C-G)), if there are one or more values of C-S for which the PE has a currently originated Source Tree Join C-multicast route for (C-S,C-G), the PE MUST join the tunnels advertised by the S-PMSI A-D routes that match (according to Section 3.2) each such (C-S,C-G).
- 否则（给定PE没有针对（C-*，C-G）的当前起源的C-多播共享树连接），如果存在一个或多个C-S值，且PE具有针对（C-S，C-G）的当前起源的源树连接C-多播路由，则PE必须加入由匹配的S-PMSI a-D路由公布的隧道（根据第3.2节）每一个这样的（C-S，C-G）。
- Otherwise, the PE "ignores" the route.
- 否则，PE将“忽略”路由。
This document covers the use of (C-S,C-*) S-PMSI A-D routes for only the C-multicast flows where C-G is an SSM group address. Use of (C-S,C-*) S-PMSI A-D routes for other C-multicast flows is outside the scope of this document. Specifically, if a PE receives a (C-S,C-*) S-PMSI A-D route, and the PE can determine that C-G is not an SSM group address, the PE SHOULD "ignore" this S-PMSI A-D route.
本文档介绍了（C-S，C-*）S-PMSI A-D路由仅用于C-G为SSM组地址的C-multicast流。对于其他C-多播流使用（C-S，C-*）S-PMSI A-D路由不在本文档范围内。具体而言，如果PE接收到（C-S，C-*）S-PMSI a-D路由，并且PE可以确定C-G不是SSM组地址，则PE应该“忽略”该S-PMSI a-D路由。
By default, the set of Route Targets carried by a (C-S,C-*) S-PMSI A-D route originated by a given VRF is an intersection between the set of Route Targets carried in the Intra-AS I-PMSI A-D route that originated from that VRF, and the set of Route Targets carried by the unicast VPN-IP route to C-S originated from that VRF. An implementation MUST allow the set of Route Targets carried by the
默认情况下，由给定VRF发起的（C-S，C-*）S-PMSI a-D路由携带的路由目标集是由该VRF发起的帧内AS I-PMSI a-D路由携带的路由目标集与由该VRF发起的单播VPN-IP路由携带到C-S的路由目标集之间的交集。实现必须允许
(C-S,C-*) S-PMSI A-D route to be specified by configuration. In the absence of a configured set of Route Targets, the route MUST carry the default set of Route Targets.
（C-S，C-*）S-PMSI A-D路由由配置指定。如果没有一组已配置的路由目标，则路由必须包含一组默认路由目标。
If a PE needs to transmit packets of a (C-S,C-G) C-flow, and if (C-S,C-G) matches a (C-S,C-*) S-PMSI A-D route according to the rules of Section 3.1, then the PE MUST use the P-tunnel advertised in this route for transmitting that C-flow. (Note that it is impossible for a given (C-S,C-G) to match both a (C-*,C-G) wildcard and a (C-S,C-*) wildcard.)
如果PE需要传输（C-S，C-G）C-flow的数据包，并且根据第3.1节的规则，如果（C-S，C-G）与（C-S，C-*）S-PMSI a-D路由匹配，则PE必须使用该路由中公布的P隧道来传输该C-flow。（请注意，给定的（C-S，C-G）不可能同时匹配（C-*，C-G）通配符和（C-S，C-*）通配符。）
If PIM is being used as the PE-PE control protocol for distributing C-multicast routing, and if a given PE needs to receive a (C-S,C-G) flow, and if (C-S,C-G) matches the (C-S,C-*) S-PMSI A-D route (according to the procedures of Section 3.2), then the PE MUST join the P-tunnel specified in the PMSI Tunnel Attribute of that route.
如果PIM用作PE-PE控制协议，用于分发C多播路由，并且如果给定PE需要接收（C-S，C-G）流，并且如果（C-S，C-G）匹配（C-S，C-*）S-PMSI a-D路由（根据第3.2节的过程），则PE必须加入该路由的PMSI隧道属性中指定的P隧道。
If BGP is being used as the PE-PE control protocol for distributing C-multicast routing, and if there is some (C-S,C-G) such that (a) the PE has a currently originated (C-S,C-G) Source Tree Join C-multicast route, AND (b) the given (C-S,C-G) matches (according to the procedures of Section 3.2) a (C-S,C-*) S-PMSI A-D route, then PE1 applies the procedures of Section 12.3 ("Receiving S-PMSI A-D Routes by PEs") of [MVPN-BGP] to the matching S-PMSI A-D route.
如果BGP用作PE-PE控制协议，用于分发C-多播路由，并且如果存在一些（C-S，C-G），使得（a）PE具有当前起源的（C-S，C-G）源树加入C-多播路由，并且（b）给定的（C-S，C-G）匹配（根据第3.2节的程序）a（C-S，C-*）S-PMSI a-D路由，然后，PE1将[MVPN-BGP]第12.3节（“PEs接收S-PMSI A-D路由”）的程序应用于匹配的S-PMSI A-D路由。
(C-*,C-*) S-PMSI A-D routes are used when, for a given MVPN, a PE has a policy not to use an I-PMSI for carrying multicast data traffic originated in the MVPN's site(s) connected to that PE. When the (C-*,C-*) wildcard is used together with BGP C-multicast routing, this results in the "S-PMSI only" model, where no I-PMSIs are used at all for the given MVPN.
（C-*，C-*）对于给定的MVPN，PE具有不使用I-PMSI来承载源自连接到该PE的MVPN站点的多播数据流量的策略时，使用S-PMSI A-D路由。当（C-*，C-*）通配符与BGP C-多播路由一起使用时，这将导致“仅S-PMSI”模型，其中对于给定的MVPN根本不使用I-PMSI。
A (C-*,C-*) S-PMSI A-D route is originated for a given MVPN by a given PE only if that PE has been provisioned with the policy to do so.
（C-*，C-*）S-PMSI A-D路由是由给定的PE为给定的MVPN发起的，前提是该PE已经设置了这样做的策略。
When so provisioned, the PE MAY originate the (C-*,C-*) S-PMSI A-D route as soon as it is enabled to support the given MVPN. Alternatively, the PE MAY delay originating the route until one of the following conditions holds:
当如此设置时，PE可在其被启用以支持给定MVPN时立即发起（C-*，C-*）S-PMSI A-D路由。或者，PE可以延迟发起路由，直到以下条件之一保持：
- The PE-PE protocol for distributing C-multicast routing is PIM, and for the given MVPN, the PE has some (C-S,C-G) or (C-*,C-G) state for which the upstream interface is one of the VRF interfaces for the given MVPN.
- 用于分发C多播路由的PE-PE协议是PIM，对于给定的MVPN，PE具有一些（C-S，C-G）或（C-*，C-G）状态，对于这些状态，上游接口是给定MVPN的VRF接口之一。
- The PE-PE protocol for distributing C-multicast routing is BGP, and the given PE has received and installed either of the following:
- 用于分发C多播路由的PE-PE协议为BGP，且给定PE已接收并安装以下任一协议：
* a Source Tree Join C-multicast route, with the C-S contained in the route's NLRI being reachable via one of the given MVPN's VRF interfaces, or
* 源树连接C多播路由，路由NLRI中包含的C-S可通过给定MVPN的VRF接口之一访问，或
* a Shared Tree Join C-multicast route, with the C-RP carried in that route being reachable via one of the given MVPN's VRF interfaces.
* 共享树连接C多播路由，该路由中携带的C-RP可通过给定MVPN的VRF接口之一访问。
By default, the set of Route Targets carried by a (C-*,C-*) S-PMSI A-D route originated from a given VRF is the same as the set of Route Targets carried in the VPN-IP unicast routes originated from that VRF. An implementation MUST allow the set of Route Targets carried by the (C-*,C-*) S-PMSI A-D route to be specified by configuration. In the absence of a configured set of Route Targets, the route MUST carry the default set of Route Targets, as specified above.
默认情况下，源自给定VRF的（C-*，C-*）S-PMSI a-D路由携带的路由目标集与源自该VRF的VPN-IP单播路由携带的路由目标集相同。实现必须允许通过配置指定（C-*，C-*）S-PMSI A-D路由携带的路由目标集。如果没有一组已配置的路由目标，则该路由必须包含一组默认路由目标，如上所述。
If a PE needs to transmit packets of a (C-S,C-G) C-flow, and if (C-S,C-G) matches a (C-*,C-*) S-PMSI A-D route according to the rules of Section 3.1, then the PE MUST use the P-tunnel advertised in this route for transmitting that C-flow. (Note that it is impossible for a given (C-S,C-G) to match both a (C-*,C-*) wildcard and any other wildcard.)
如果PE需要传输（C-S，C-G）C-flow的数据包，并且根据第3.1节的规则，如果（C-S，C-G）与（C-*，C-*）S-PMSI a-D路由匹配，则PE必须使用该路由中公布的P隧道来传输该C-flow。（请注意，给定的（C-S，C-G）不可能同时匹配（C-*，C-*）通配符和任何其他通配符。）
If PIM is being used as the PE-PE control protocol for distributing C-multicast routing, and if a given PE, say PE1, needs to receive a (C-S,C-G) flow, and if (C-S,C-G) matches the (C-*,C-*) S-PMSI A-D route (according to the procedures of Section 3.2), then PE1 MUST join the P-tunnel specified in the PMSI Tunnel Attribute of that route.
如果PIM被用作分发C多播路由的PE-PE控制协议，并且如果给定的PE（例如PE1）需要接收（C-S，C-G）流，并且如果（C-S，C-G）匹配（C-*，C-*）S-PMSI a-D路由（根据第3.2节的程序），则PE1必须加入该路由的PMSI隧道属性中指定的P隧道。
If BGP is being used as the PE-PE control protocol for distributing C-multicast routing, then if (and only if) one of the following conditions holds, the PE applies the procedures of Section 12.3 ("Receiving S-PMSI A-D Routes by PEs") of [MVPN-BGP] to the matching S-PMSI A-D route. The conditions are as follows:
如果BGP用作PE-PE控制协议，用于分发C-多播路由，则如果（且仅当）以下条件之一成立，则PE将[MVPN-BGP]第12.3节（“PEs接收S-PMSI A-D路由”）中的程序应用于匹配的S-PMSI A-D路由。条件如下：
- The PE has a currently originated C-multicast Source Tree Join route for (C-S,C-G) that matches (according to the procedures of Section 3.2) the (C-*,C-*) S-PMSI A-D route, or
- PE具有（C-S，C-G）的当前起源C-多播源树连接路由，该路由与（C-*，C-*）S-PMSI a-D路由匹配（根据第3.2节的程序），或
- The PE has a currently originated a C-multicast Shared Tree Join route for (C-*,C-G) that matches (according to the procedures of Section 3.2) the (C-*,C-*) S-PMSI A-D route.
- PE当前为（C-*，C-G）创建了一个C-多播共享树连接路由，该路由与（C-*，C-*）S-PMSI a-D路由相匹配（根据第3.2节的程序）。
There are no additional security considerations beyond those of [MVPN] and [MVPN-BGP].
除了[MVPN]和[MVPN-BGP]之外，没有其他安全注意事项。
The authors wish to thank Arjen Boers, Dongling Duan, Apoorva Karan, Thomas Morin, Keyur Patel, Karthik Subramanian, and Kurt Windisch for many helpful discussions.
作者希望感谢Arjen Boers、Duan Dongling、Apoorva Karan、Thomas Morin、Keyur Patel、Karthik Subramanian和Kurt Windisch进行了许多有益的讨论。
[BGP-MP] Bates, T., Chandra, R., Katz, D., and Y. Rekhter, "Multiprotocol Extensions for BGP-4", RFC 4760, January 2007.
[BGP-MP]Bates，T.，Chandra，R.，Katz，D.，和Y.Rekhter，“BGP-4的多协议扩展”，RFC 4760，2007年1月。
[L3VPN] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private Networks (VPNs)", RFC 4364, February 2006.
[L3VPN]Rosen，E.和Y.Rekhter，“BGP/MPLS IP虚拟专用网络（VPN）”，RFC 4364，2006年2月。
[MVPN] Rosen, E., Ed., and R. Aggarwal, Ed., "Multicast in MPLS/BGP IP VPNs", RFC 6513, February 2012.
[MVPN]Rosen，E.，Ed.，和R.Aggarwal，Ed.，“MPLS/BGP IP VPN中的多播”，RFC 6513，2012年2月。
[MVPN-BGP] Aggarwal, R., Rosen, E., Morin, T., and Y. Rekhter, "BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs", RFC 6514, February 2012.
[MVPN-BGP]Aggarwal，R.，Rosen，E.，Morin，T.，和Y.Rekhter，“MPLS/BGP IP VPN中的BGP编码和多播过程”，RFC 6514，2012年2月。
[PIM] Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas, "Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)", RFC 4601, August 2006.
[PIM]Fenner，B.，Handley，M.，Holbrook，H.，和I.Kouvelas，“协议独立多播-稀疏模式（PIM-SM）：协议规范（修订版）”，RFC 4601，2006年8月。
[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月。
Authors' Addresses
作者地址
Rahul Aggarwal Arktan
拉胡尔·阿加瓦尔·阿尔坦
EMail: raggarwa_1@yahoo.com
EMail: raggarwa_1@yahoo.com
Yiqun Cai Microsoft 1065 La Avenida Mountain View, CA 94043
加利福尼亚州拉维尼达山景大道1065号益群蔡微软94043
EMail: yiqunc@microsoft.com
EMail: yiqunc@microsoft.com
Wim Henderickx Alcatel-Lucent
Wim亨德里克斯阿尔卡特朗讯
EMail: wim.henderickx@alcatel-lucent.be
EMail: wim.henderickx@alcatel-lucent.be
Praveen Muley Alcatel-Lucent
Praveen Muley阿尔卡特朗讯
EMail: Praveen.Muley@alcatel-lucent.com
EMail: Praveen.Muley@alcatel-lucent.com
Ray (Lei) Qiu 2330 Central Expressway Santa Clara, CA 95050 USA
美国加利福尼亚州圣克拉拉中央高速公路2330号，邮编95050
EMail: rayq@huawei.com
EMail: rayq@huawei.com
Yakov Rekhter (editor) Juniper Networks 1194 North Mathilda Ave. Sunnyvale, CA 94089
Yakov Rekhter（编辑）Juniper Networks 1194北马蒂尔达大道桑尼维尔，加利福尼亚州94089
EMail: yakov@juniper.net
EMail: yakov@juniper.net
Eric C. Rosen (editor) Cisco Systems, Inc. 1414 Massachusetts Avenue Boxborough, MA 01719
Eric C.Rosen（编辑）思科系统公司，马萨诸塞州伯斯堡马萨诸塞大道1414号，邮编01719
EMail: erosen@cisco.com
EMail: erosen@cisco.com
IJsbrand Wijnands Cisco Systems, Inc. De kleetlaan 6a Diegem 1831 Belgium
IJsbrand Wijlands Cisco Systems，Inc.De kleetlaan 6a Diegem 1831比利时
EMail: ice@cisco.com
EMail: ice@cisco.com