Debian Codegraph @

rfc7900.html

raw
1 <pre>Internet Engineering Task Force (IETF) Y. Rekhter, Ed.
2 Request for Comments: 7900 E. Rosen, Ed.
3 Updates: <a href="./rfc6513">6513</a>, <a href="./rfc6514">6514</a>, <a href="./rfc6625">6625</a> Juniper Networks, Inc.
4 Category: Standards Track R. Aggarwal
5 ISSN: 2070-1721 Arktan
6 Y. Cai
7 Alibaba Group
8 T. Morin
9 Orange
10 June 2016
11
12
13 <span class="h1">Extranet Multicast in BGP/IP MPLS VPNs</span>
14
15 Abstract
16
17 Previous RFCs specify the procedures necessary to allow IP multicast
18 traffic to travel from one site to another within a BGP/MPLS IP VPN
19 (Virtual Private Network). However, it is sometimes desirable to
20 allow multicast traffic whose source is in one VPN to be received by
21 systems that are in another VPN. This is known as a "Multicast VPN
22 (MVPN) extranet". This document updates RFCs 6513, 6514, and 6625 by
23 specifying the procedures that are necessary in order to provide
24 extranet MVPN service.
25
26 Status of This Memo
27
28 This is an Internet Standards Track document.
29
30 This document is a product of the Internet Engineering Task Force
31 (IETF). It represents the consensus of the IETF community. It has
32 received public review and has been approved for publication by the
33 Internet Engineering Steering Group (IESG). Further information on
34 Internet Standards is available in <a href="./rfc7841#section-2">Section&nbsp;2 of RFC 7841</a>.
35
36 Information about the current status of this document, any errata,
37 and how to provide feedback on it may be obtained at
38 <a href="http://www.rfc-editor.org/info/rfc7900">http://www.rfc-editor.org/info/rfc7900</a>.
39
40
41
42
43
44
45
46
47
48
49
50
51
52 <span class="grey">Rekhter, et al. Standards Track [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
55
56
57 Copyright Notice
58
59 Copyright (c) 2016 IETF Trust and the persons identified as the
60 document authors. All rights reserved.
61
62 This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
63 Provisions Relating to IETF Documents
64 (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
65 publication of this document. Please review these documents
66 carefully, as they describe your rights and restrictions with respect
67 to this document. Code Components extracted from this document must
68 include Simplified BSD License text as described in Section 4.e of
69 the Trust Legal Provisions and are provided without warranty as
70 described in the Simplified BSD License.
71
72 Table of Contents
73
74 <a href="#section-1">1</a>. Introduction ....................................................<a href="#page-4">4</a>
75 <a href="#section-1.1">1.1</a>. Terminology ................................................<a href="#page-4">4</a>
76 <a href="#section-1.2">1.2</a>. Scope ......................................................<a href="#page-7">7</a>
77 <a href="#section-1.2.1">1.2.1</a>. Customer Multicast Control Protocols ................<a href="#page-7">7</a>
78 <a href="#section-1.2.2">1.2.2</a>. Provider Multicast Control Protocols ................<a href="#page-7">7</a>
79 <a href="#section-1.3">1.3</a>. Clarification on Use of Route Distinguishers ...............<a href="#page-8">8</a>
80 <a href="#section-1.4">1.4</a>. Overview ...................................................<a href="#page-9">9</a>
81 <a href="#section-2">2</a>. Extranets and Overlapping Address Spaces .......................<a href="#page-12">12</a>
82 <a href="#section-2.1">2.1</a>. Ambiguity: P-Tunnel with Extranet/Non-extranet Flows ......<a href="#page-14">14</a>
83 <a href="#section-2.2">2.2</a>. Ambiguity: P-Tunnel with Multiple Extranet Flows ..........<a href="#page-16">16</a>
84 <a href="#section-2.3">2.3</a>. Preventing Misdelivery in These Scenarios .................<a href="#page-18">18</a>
85 <a href="#section-2.3.1">2.3.1</a>. Do Not Deliver Packets from the Wrong P-tunnel .....<a href="#page-18">18</a>
86 <a href="#section-2.3.2">2.3.2</a>. Policies to Prevent Ambiguity on a P-Tunnel ........<a href="#page-20">20</a>
87 <a href="#section-3">3</a>. Extranet Transmission Models ...................................<a href="#page-21">21</a>
88 <a href="#section-3.1">3.1</a>. Transmitting an Extranet C-Flow on a Single PMSI ..........<a href="#page-21">21</a>
89 <a href="#section-3.1.1">3.1.1</a>. Without Extranet Separation ........................<a href="#page-22">22</a>
90 <a href="#section-3.1.2">3.1.2</a>. With Extranet Separation ...........................<a href="#page-22">22</a>
91 <a href="#section-3.2">3.2</a>. Transmitting an Extranet C-Flow over Multiple PMSIs .......<a href="#page-23">23</a>
92 <a href="#section-4">4</a>. Distribution of Routes That Match C-S/C-RP Addresses ...........<a href="#page-23">23</a>
93 <a href="#section-4.1">4.1</a>. UMH-Eligible Routes .......................................<a href="#page-23">23</a>
94 <a href="#section-4.1.1">4.1.1</a>. Extranet Separation ................................<a href="#page-24">24</a>
95 <a href="#section-4.2">4.2</a>. Distribution of Unicast Routes Matching C-RPs and DRs .....<a href="#page-25">25</a>
96 <a href="#section-4.3">4.3</a>. Route Targets and Ambiguous UMH-Eligible Routes ...........<a href="#page-26">26</a>
97 <a href="#section-4.4">4.4</a>. Dynamically Marking Extranet Routes .......................<a href="#page-27">27</a>
98 <a href="#section-4.4.1">4.4.1</a>. The Extranet Source Extended Community .............<a href="#page-27">27</a>
99 4.4.2. Distribution of Extranet Source Extended
100 Community ..........................................<a href="#page-29">29</a>
101 <a href="#section-4.5">4.5</a>. The Extranet Separation Extended Community ................<a href="#page-30">30</a>
102
103
104
105
106
107
108 <span class="grey">Rekhter, et al. Standards Track [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
111
112
113 <a href="#section-5">5</a>. Origination and Distribution of BGP A-D Routes .................<a href="#page-30">30</a>
114 <a href="#section-5.1">5.1</a>. Route Targets of UMH-Eligible Routes and A-D Routes .......<a href="#page-30">30</a>
115 <a href="#section-5.2">5.2</a>. Considerations for Particular Inclusive Tunnel Types ......<a href="#page-33">33</a>
116 <a href="#section-5.2.1">5.2.1</a>. RSVP-TE P2MP or Ingress Replication ................<a href="#page-33">33</a>
117 <a href="#section-5.2.2">5.2.2</a>. Ingress Replication ................................<a href="#page-34">34</a>
118 <a href="#section-6">6</a>. When PIM Is the PE-PE C-Multicast Control Plane ................<a href="#page-35">35</a>
119 <a href="#section-6.1">6.1</a>. Provisioning VRFs with RTs ................................<a href="#page-36">36</a>
120 <a href="#section-6.1.1">6.1.1</a>. Incoming and Outgoing Extranet RTs .................<a href="#page-36">36</a>
121 <a href="#section-6.1.2">6.1.2</a>. UMH-Eligible Routes and RTs ........................<a href="#page-37">37</a>
122 6.1.3. PIM C-Instance Reverse Path Forwarding
123 Determination ......................................<a href="#page-37">37</a>
124 <a href="#section-6.2">6.2</a>. "Single PMSI per C-Flow" Model ............................<a href="#page-38">38</a>
125 <a href="#section-6.2.1">6.2.1</a>. Forming the MI-PMSIs ...............................<a href="#page-38">38</a>
126 <a href="#section-6.2.2">6.2.2</a>. S-PMSIs ............................................<a href="#page-41">41</a>
127 <a href="#section-6.2.3">6.2.3</a>. Sending PIM Control Packets ........................<a href="#page-42">42</a>
128 <a href="#section-6.2.4">6.2.4</a>. Receiving PIM Control Packets ......................<a href="#page-43">43</a>
129 <a href="#section-6.2.5">6.2.5</a>. Sending and Receiving Data Packets .................<a href="#page-43">43</a>
130 <a href="#section-6.3">6.3</a>. "Multiple PMSIs per C-Flow" Model .........................<a href="#page-43">43</a>
131 <a href="#section-6.3.1">6.3.1</a>. Forming the MI-PMSIs ...............................<a href="#page-44">44</a>
132 <a href="#section-7">7</a>. When BGP Is the PE-PE C-Multicast Control Plane ................<a href="#page-46">46</a>
133 <a href="#section-7.1">7.1</a>. Originating C-Multicast Routes ............................<a href="#page-46">46</a>
134 <a href="#section-7.2">7.2</a>. Originating A-D Routes without Extranet Separation ........<a href="#page-47">47</a>
135 <a href="#section-7.2.1">7.2.1</a>. Intra-AS I-PMSI A-D Routes .........................<a href="#page-47">47</a>
136 <a href="#section-7.2.2">7.2.2</a>. S-PMSI A-D Routes ..................................<a href="#page-47">47</a>
137 <a href="#section-7.2.3">7.2.3</a>. Source Active A-D Routes ...........................<a href="#page-48">48</a>
138 <a href="#section-7.2.3.1">7.2.3.1</a>. When Inter-Site Shared Trees Are Used .....<a href="#page-48">48</a>
139 7.2.3.2. When Inter-Site Shared Trees Are
140 Not Used ..................................<a href="#page-49">49</a>
141 <a href="#section-7.3">7.3</a>. Originating A-D Routes with Extranet Separation ...........<a href="#page-49">49</a>
142 <a href="#section-7.3.1">7.3.1</a>. Intra-AS I-PMSI A-D Routes .........................<a href="#page-49">49</a>
143 <a href="#section-7.3.2">7.3.2</a>. S-PMSI A-D Routes ..................................<a href="#page-50">50</a>
144 <a href="#section-7.3.3">7.3.3</a>. Source Active A-D Routes ...........................<a href="#page-52">52</a>
145 <a href="#section-7.4">7.4</a>. Determining the Expected P-Tunnel for a C-Flow ............<a href="#page-52">52</a>
146 <a href="#section-7.4.1">7.4.1</a>. (C-S,C-G) S-PMSI A-D Routes ........................<a href="#page-54">54</a>
147 <a href="#section-7.4.2">7.4.2</a>. (C-S,C-*) S-PMSI A-D Routes ........................<a href="#page-54">54</a>
148 <a href="#section-7.4.3">7.4.3</a>. (C-*,C-G) S-PMSI A-D Routes ........................<a href="#page-55">55</a>
149 <a href="#section-7.4.4">7.4.4</a>. (C-*,C-*) S-PMSI A-D Routes ........................<a href="#page-56">56</a>
150 <a href="#section-7.4.5">7.4.5</a>. I-PMSI A-D Routes ..................................<a href="#page-56">56</a>
151 <a href="#section-7.5">7.5</a>. Packets Arriving from the Wrong P-Tunnel ..................<a href="#page-57">57</a>
152 <a href="#section-8">8</a>. Multiple Extranet VRFs on the Same PE ..........................<a href="#page-57">57</a>
153 <a href="#section-9">9</a>. IANA Considerations ............................................<a href="#page-58">58</a>
154 <a href="#section-10">10</a>. Security Considerations .......................................<a href="#page-59">59</a>
155 <a href="#section-11">11</a>. References ....................................................<a href="#page-61">61</a>
156 <a href="#section-11.1">11.1</a>. Normative References .....................................<a href="#page-61">61</a>
157 <a href="#section-11.2">11.2</a>. Informative References ...................................<a href="#page-62">62</a>
158 Acknowledgments ...................................................<a href="#page-64">64</a>
159 Contributors ......................................................<a href="#page-64">64</a>
160 Authors' Addresses ................................................<a href="#page-65">65</a>
161
162
163
164 <span class="grey">Rekhter, et al. Standards Track [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
167
168
169 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
170
171 Previous RFCs [<a href="./rfc6513" title="&quot;Multicast in MPLS/BGP IP VPNs&quot;">RFC6513</a>] [<a href="./rfc6514" title="&quot;BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs&quot;">RFC6514</a>] specify the procedures necessary to
172 allow IP multicast traffic to travel from one site to another within
173 a BGP/MPLS IP VPN (Virtual Private Network). However, it is
174 sometimes desirable to allow multicast traffic whose source is in one
175 VPN to be received by systems that are in another VPN. This is known
176 as an "extranet Multicast VPN (MVPN)". This document specifies the
177 procedures that are necessary in order to provide extranet MVPN
178 functionality.
179
180 This document updates RFCs 6513, 6514, and 6625 by specifying the
181 procedures that are necessary in order to provide extranet MVPN
182 service.
183
184 <span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Terminology</span>
185
186 This document uses terminology from [<a href="./rfc6513" title="&quot;Multicast in MPLS/BGP IP VPNs&quot;">RFC6513</a>] and in particular uses
187 the prefixes "C-" and "P-" as specified in <a href="./rfc6513#section-3.1">Section&nbsp;3.1 of [RFC6513]</a>,
188 and "A-D routes" for "auto-discovery routes".
189
190 The term "Upstream Multicast Hop" (UMH) is used as defined in
191 [<a href="./rfc6513" title="&quot;Multicast in MPLS/BGP IP VPNs&quot;">RFC6513</a>].
192
193 The term "UMH-eligible route" is used to mean "route eligible for UMH
194 determination", as defined in <a href="./rfc6513#section-5.1.1">Section&nbsp;5.1.1 of [RFC6513]</a>. We will
195 say that a given UMH-eligible route or unicast route "matches" a
196 given IP address, in the context of a given Virtual Routing and
197 Forwarding table (VRF), if the address prefix of the given route is
198 the longest match in that VRF for the given IP address. We will
199 sometimes say that a route "matches" a particular host if the route
200 matches an IP address of the host.
201
202 We follow the terminology of <a href="./rfc6625#section-3.2">Section&nbsp;3.2 of [RFC6625]</a> when talking of
203 a "Selective Provider Multicast Service Interface" (S-PMSI) A-D route
204 being "installed". That is, we say that an S-PMSI A-D route is
205 "installed" (in a given VRF) if it has been selected by the BGP
206 decision process as the preferred route for its Network Layer
207 Reachability Information (NLRI). We also follow the terminology of
208 <a href="./rfc6625#section-3.2">Section&nbsp;3.2 of [RFC6625]</a> when saying that an S-PMSI A-D route has
209 been "originated by a given PE"; this means that the given Provider
210 Edge's (PE's) IP address is contained in the Originating Router's IP
211 Address field in the NLRI of the route.
212
213
214
215
216
217
218
219
220 <span class="grey">Rekhter, et al. Standards Track [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
223
224
225 We use the following additional terminology and notation:
226
227 o Extranet C-source: a multicast source, in a given VPN, that is
228 allowed by policy to send multicast traffic to receivers that are
229 in other VPNs.
230
231 o Extranet C-receiver: a multicast receiver, in a given VPN, that is
232 allowed by policy to receive multicast traffic from extranet
233 C-sources that are in other VPNs.
234
235 o Extranet C-flow: a multicast flow (with a specified C-source
236 address and C-group address) with the following properties: its
237 source is an extranet C-source, and it is allowed by policy to
238 have extranet C-receivers.
239
240 o Extranet C-group: a multicast group address that is in the
241 "Any-Source Multicast" (ASM) group address range and that is
242 allowed by policy to have extranet C-sources and extranet
243 C-receivers that are not all in the same VPN. Note that we will
244 sometimes refer to "Source-Specific Multicast (SSM) C-group
245 addresses" (i.e., C-group addresses in the SSM group address
246 range) but will never call them "extranet C-groups".
247
248 N.B.: Any source of traffic for an extranet C-group is considered
249 to be an extranet C-source, and any receiver of traffic addressed
250 to an extranet C-group is considered to be an extranet C-receiver.
251
252 o Extranet C-RP: a multicast Rendezvous Point (RP) for an extranet
253 C-group; it is allowed by policy to receive PIM Register messages
254 [<a href="./rfc7761" title="&quot;Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)&quot;">RFC7761</a>] from outside its VPN and to send multicast data packets
255 to extranet C-receivers outside its VPN.
256
257 o Host(C-S,A): the host (or, if C-S is an "anycast address", the set
258 of hosts) denoted by the address C-S in the context of VPN-A. For
259 example, if a particular C-source in VPN-A has address C-S, then
260 Host(C-S,A) refers to that C-source.
261
262 o "SAFI n" route: a BGP route whose Address Family Identifier (AFI)
263 is either 1 (IPv4) or 2 (IPv6) and whose Subsequent Address Family
264 Identifier (SAFI) is "n".
265
266 o PTA: PMSI Tunnel Attribute [<a href="./rfc6514" title="&quot;BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs&quot;">RFC6514</a>].
267
268
269
270
271
272
273
274
275
276 <span class="grey">Rekhter, et al. Standards Track [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
279
280
281 Note that a given extranet C-source is not necessarily allowed to
282 transmit to every extranet C-receiver; policy determines which
283 extranet C-sources are allowed to transmit to which extranet
284 C-receivers. However, in the case of an extranet (ASM) C-group, all
285 transmitters to the group are allowed to transmit to all the
286 receivers of the group, and all the receivers of the group are
287 allowed to receive from all transmitters to the group.
288
289 We say that a given VRF "contains" or "has" a multicast C-source (or
290 that the C-source is "in" the VRF) if that C-source is in a site
291 connected to that VRF and the VRF originates a UMH-eligible route
292 (see <a href="#section-4">Section 4</a>) that matches the address of the C-source.
293
294 We say that a given VRF "contains" or "has" a multicast C-receiver
295 (or that the C-receiver is "in" the VRF) if that C-receiver is in a
296 site connected to that VRF.
297
298 We say that a given VRF "contains" or "has" the C-RP for a given ASM
299 group (or that the C-RP is "in" the VRF) if that C-RP is in a site
300 connected to that VRF and the VRF originates a unicast route and a
301 (possibly different, possibly the same) UMH-eligible route (see
302 <a href="#section-4">Section 4</a>) whose respective address prefixes match the C-RP address.
303
304 [<a id="ref-RFC6513">RFC6513</a>] allows a set of "P-tunnels" (defined in <a href="./rfc6513#section-3.2">Section&nbsp;3.2 of
305 [RFC6513]</a>) to be aggregated together and transported via an outer
306 P-tunnel; i.e., it allows for the use of hierarchical Label Switched
307 Paths (LSPs) as P-tunnels. A two-level hierarchical LSP, for
308 example, can be thought of as a set of "inner tunnels" aggregated
309 into an outer tunnel. In this document, when we speak of a P-tunnel,
310 we are always speaking of the innermost P-tunnel, i.e., of a P-tunnel
311 at the lowest hierarchical level. P-tunnels are identified in the
312 PMSI Tunnel attributes ("PTAs" in this document) [<a href="./rfc6514" title="&quot;BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs&quot;">RFC6514</a>] of BGP
313 auto-discovery (A-D) routes. Two PTAs that have the same Tunnel Type
314 and Tunnel Identifier fields but different MPLS label fields are thus
315 considered to identify two different P-tunnels. (That is, for the
316 purposes of this document, the MPLS label included in the PTA, if
317 any, is considered to be part of the tunnel identifier.)
318
319 We say that the NLRI of a BGP S-PMSI A-D route or Source Active A-D
320 route contains (C-S,C-G) if its Multicast Source field contains C-S
321 and its Multicast Group field contains C-G. If either or both of
322 these fields are encoded as a wildcard, we will say that the NLRI
323 contains (C-*,C-*) (both fields encoded as wildcards), (C-*,C-G)
324 (Multicast Source field encoded as a wildcard), or (C-S,C-*)
325 (Multicast Group field encoded as a wildcard).
326
327
328
329
330
331
332 <span class="grey">Rekhter, et al. Standards Track [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
335
336
337 We use the term "VPN security violation" to refer to any situation in
338 which a packet is delivered to a particular VPN, even though, by
339 policy, it should not be delivered to that VPN.
340
341 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
342 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
343 "OPTIONAL" in this document are to be interpreted as described in
344 [<a href="./rfc2119" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">RFC2119</a>].
345
346 <span class="h3"><a class="selflink" id="section-1.2" href="#section-1.2">1.2</a>. Scope</span>
347
348 <span class="h4"><a class="selflink" id="section-1.2.1" href="#section-1.2.1">1.2.1</a>. Customer Multicast Control Protocols</span>
349
350 This document presumes that the VPN customer is using PIM - Sparse
351 Mode (PIM-SM) [<a href="./rfc7761" title="&quot;Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)&quot;">RFC7761</a>] as the multicast control protocol at the
352 customer sites. PIM-SM may be used in either the ASM service model
353 or the SSM service model; this document covers both cases. Support
354 for other customer IP multicast control protocols (e.g., [<a href="./rfc5015" title="&quot;Bidirectional Protocol Independent Multicast (BIDIR-PIM)&quot;">RFC5015</a>],
355 PIM - Dense Mode) is outside the scope of this document. Support for
356 the use of MPLS multicast control protocols (e.g., [<a href="./rfc6388" title="&quot;Label Distribution Protocol Extensions for Point- to-Multipoint and Multipoint-to-Multipoint Label Switched Paths&quot;">RFC6388</a>]
357 [<a href="./rfc4875" title="&quot;Extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) for Point-to- Multipoint TE Label Switched Paths (LSPs)&quot;">RFC4875</a>]) by customer sites is also outside the scope of this
358 document.
359
360 When a VPN customer uses ASM, the customer routers need to be able to
361 map from a C-group address to a C-RP address. These mappings can be
362 provisioned in each router, or they can be discovered dynamically
363 through protocols such as the Bootstrap Router (BSR) mechanism
364 [<a href="./rfc5059" title="&quot;Bootstrap Router (BSR) Mechanism for Protocol Independent Multicast (PIM)&quot;">RFC5059</a>]. However, it cannot be assumed that such protocols will
365 automatically work in the context of an extranet. Discussion of the
366 use of such protocols in an extranet is outside the scope of this
367 document.
368
369 <span class="h4"><a class="selflink" id="section-1.2.2" href="#section-1.2.2">1.2.2</a>. Provider Multicast Control Protocols</span>
370
371 [<a id="ref-RFC6513">RFC6513</a>] allows either PIM or BGP to be used as the protocol for
372 distributing customer multicast routing information. Except where
373 otherwise specified, such as in Sections <a href="#section-6">6</a> and <a href="#section-7">7</a>, the procedures of
374 this document cover both cases.
375
376
377
378
379
380
381
382
383
384
385
386
387
388 <span class="grey">Rekhter, et al. Standards Track [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
391
392
393 <span class="h3"><a class="selflink" id="section-1.3" href="#section-1.3">1.3</a>. Clarification on Use of Route Distinguishers</span>
394
395 [<a id="ref-RFC4364">RFC4364</a>] requires that every VRF be associated with one or more
396 Route Distinguishers (RDs). Each VPN-IPv4 or VPN-IPv6 route that is
397 exported from a particular VRF contains, in its NLRI, an RD that is
398 associated with that VRF.
399
400 [<a id="ref-RFC4364">RFC4364</a>] allows a given RD to be associated with more than one VRF,
401 as long as all the VRFs associated with that RD belong to the same
402 VPN. However, in the most common deployment model, each RD is
403 associated with one and only one VRF. [<a href="./rfc6513" title="&quot;Multicast in MPLS/BGP IP VPNs&quot;">RFC6513</a>] and [<a href="./rfc6514" title="&quot;BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs&quot;">RFC6514</a>]
404 presuppose this deployment model. That is, [<a href="./rfc6513" title="&quot;Multicast in MPLS/BGP IP VPNs&quot;">RFC6513</a>] and [<a href="./rfc6514" title="&quot;BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs&quot;">RFC6514</a>]
405 presuppose that every RD is associated with one and only one VRF. We
406 will call this the "unique VRF per RD" condition.
407
408 [<a id="ref-RFC6514">RFC6514</a>] defines the MCAST-VPN address family, which has a number of
409 route types. Each Intra-Autonomous System (Intra-AS) "Inclusive
410 Provider Multicast Service Interface" (I-PMSI) A-D route, S-PMSI A-D
411 route, and Source Active A-D route, when exported from a given VRF,
412 contains, in its NLRI, an RD that is associated with the VRF.
413 [<a href="./rfc6513" title="&quot;Multicast in MPLS/BGP IP VPNs&quot;">RFC6513</a>] and [<a href="./rfc6514" title="&quot;BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs&quot;">RFC6514</a>] also discuss a class of routes known as
414 "UMH-eligible" routes; when a UMH-eligible route is exported from a
415 given VRF, its NLRI contains an RD of the VRF.
416
417 [<a id="ref-RFC6514">RFC6514</a>] also defines MCAST-VPN routes whose NLRIs do not contain an
418 RD of the VRF from which they are exported: the C-multicast Join
419 routes and the Leaf A-D routes.
420
421 Those route types that, when exported from a given VRF, contain (in
422 their NLRIs) an RD of the VRF, will be known in this document as
423 "local-RD routes".
424
425 Given the "unique VRF per RD" condition, if one sees that two
426 local-RD routes have the same RD, one can infer that the two routes
427 originated from the same VRF. This inference can be drawn even if
428 the two routes do not have the same SAFI, as long as the two routes
429 are both local-RD routes.
430
431 This document builds upon [<a href="./rfc6513" title="&quot;Multicast in MPLS/BGP IP VPNs&quot;">RFC6513</a>] and [<a href="./rfc6514" title="&quot;BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs&quot;">RFC6514</a>]; therefore, the
432 "unique VRF per RD" condition is REQUIRED.
433
434 [<a id="ref-RFC6514">RFC6514</a>] presupposes a further requirement on the use of RDs in the
435 local-RD routes exported from a given VRF. Suppose that a given VRF
436 exports a Source Active A-D route containing (C-S,C-G). That VRF
437 will also export a UMH-eligible route matching C-S. [<a href="./rfc6514" title="&quot;BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs&quot;">RFC6514</a>]
438 presupposes that the UMH-eligible route and the Source Active A-D
439 route have the same RD.
440
441
442
443
444 <span class="grey">Rekhter, et al. Standards Track [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
447
448
449 In most cases, not only is a given RD associated with only a single
450 VRF, but a given VRF is associated with only a single RD. We will
451 call this the "unique RD per VRF" condition. When this condition
452 holds, all the local-RD routes exported from a given VRF will have
453 the same RD. This ensures that the presupposition of the previous
454 paragraph will hold, i.e., that the RD in a Source Active A-D route
455 exported from a given VRF will have the same RD as the corresponding
456 UMH-eligible route exported from the same VRF.
457
458 <a href="#section-7.3">Section 7.3</a> of this document describes a procedure known as "extranet
459 separation". When extranet separation is NOT being used, it is
460 REQUIRED by this document that the "unique RD per VRF" condition
461 hold. This ensures that all the local-RD routes exported from a
462 given VRF will have the same RD.
463
464 When extranet separation is used, a VRF that contains both extranet
465 sources and non-extranet sources MUST be configured with two RDs.
466 One of these RDs is known as the "default RD", and the other is known
467 as the "extranet RD". It MUST be known by configuration which RD is
468 the default RD and which is the extranet RD.
469
470 When a VRF is configured with only one RD, we will refer to that RD
471 as the "default RD".
472
473 In general, local-RD routes exported from a given VRF will contain
474 the default RD. However, when extranet separation is used, some of
475 the local-RD routes exported from the VRF will contain the
476 extranet RD. Details concerning the exported routes that contain
477 the extranet RD can be found in Sections <a href="#section-4.1">4.1</a> and <a href="#section-7.3">7.3</a>.
478
479 Note that the "unique VRF per RD" condition applies to the
480 extranet RD as well as the default RD. That is, a given extranet RD
481 is associated with a unique VRF.
482
483 <span class="h3"><a class="selflink" id="section-1.4" href="#section-1.4">1.4</a>. Overview</span>
484
485 Consider two VPNs, VPN-S and VPN-R, each of which supports MVPN
486 functionality as specified in [<a href="./rfc6513" title="&quot;Multicast in MPLS/BGP IP VPNs&quot;">RFC6513</a>] and/or [<a href="./rfc6514" title="&quot;BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs&quot;">RFC6514</a>]. In the
487 simplest configuration, VPN-S is a collection of VRFs, each of which
488 is configured with a particular Route Target (RT) value (call it
489 "RT-S") as its import RT and as its export RT. Similarly, VPN-R is a
490 collection of VRFs, each of which is configured with a particular RT
491 value (call it "RT-R") as its import RT and as its export RT.
492
493
494
495
496
497
498
499
500 <span class="grey">Rekhter, et al. Standards Track [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
503
504
505 In this configuration, multicast C-receivers contained in a VPN-R VRF
506 cannot receive multicast data traffic from multicast C-sources
507 contained in a VPN-S VRF. If it is desired to allow this, one needs
508 to create an MVPN "extranet". Creating an extranet requires
509 procedures in addition to those specified in [<a href="./rfc6513" title="&quot;Multicast in MPLS/BGP IP VPNs&quot;">RFC6513</a>], [<a href="./rfc6514" title="&quot;BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs&quot;">RFC6514</a>],
510 and [<a href="./rfc6625" title="&quot;Wildcards in Multicast VPN Auto-Discovery Routes&quot;">RFC6625</a>]; this document specifies these additional procedures.
511
512 In the example above, the additional procedures will allow a selected
513 set of routes exported from the VPN-S VRFs (i.e., from the VRFs
514 containing extranet C-sources) to be imported into the VPN-R VRFs
515 (i.e., into the VRFs containing extranet C-receivers). These routes
516 include the routes that are to be eligible for use as UMH routes (see
517 <a href="./rfc6513#section-5.1">Section&nbsp;5.1 of [RFC6513]</a>) in the extranet, as well as a selected set
518 of BGP A-D routes (Intra-AS I-PMSI A-D routes, S-PMSI A-D routes, and
519 Source Active A-D routes). Importing these routes into the VPN-R
520 VRFs makes it possible to determine, in the context of a VPN-R VRF,
521 that a particular C-multicast Join needs to be delivered to a
522 particular VPN-S VRF. It also makes it possible to determine, in the
523 context of a VPN-R VRF, the P-tunnel through which the aforementioned
524 VPN-S VRF sends a particular C-flow.
525
526 Depending on the type of P-tunnel used, it may also be necessary for
527 Leaf A-D routes to be exported by one or more VPN-R VRFs and imported
528 into a VPN-S VRF.
529
530 There are no extranet-specific procedures governing the use and
531 distribution of BGP C-multicast routes.
532
533 If PIM is used as the PE-PE protocol for distributing C-multicast
534 routing information, additional BGP A-D routes must be exported from
535 the VPN-R VRFs and imported into the VPN-S VRFs, so that the VPN-S
536 VRFs can join the P-tunnels that the VPN-R VRFs use for sending PIM
537 control messages. Details can be found in <a href="#section-6">Section 6</a>.
538
539 The simple example above describes an extranet created from two
540 MVPNs, one of which contains extranet C-sources and one of which
541 contains extranet C-receivers. However, the procedures described in
542 this document allow for much more complicated scenarios.
543
544 For instance, an extranet may contain extranet C-sources and/or
545 extranet C-receivers from an arbitrary number of VPNs, not just from
546 two VPNs. An extranet C-receiver in VPN-R may be allowed to receive
547 multicast traffic from extranet C-sources in VPN-A, VPN-B, and VPN-C.
548 Similarly, extranet C-sources in VPN-S may be allowed to send
549 multicast traffic to multicast C-receivers that are in VPN-A, VPN-B,
550 VPN-C, etc.
551
552
553
554
555
556 <span class="grey">Rekhter, et al. Standards Track [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
559
560
561 A given VPN customer may desire that only some of its multicast
562 C-sources be treated as extranet C-sources. This can be accomplished
563 by appropriate provisioning of the import and export RTs of that
564 customer's VRFs (as well as the VRFs of other VPNs that contain
565 extranet C-receivers for extranet C-flows of the given customer).
566
567 A given VPN customer may desire that some of its extranet C-sources
568 can transmit only to a certain set of VPNs while other of its
569 extranet C-sources can transmit only to a different set of VPNs.
570 This can be accomplished by provisioning the VRFs to export different
571 routes with different RTs.
572
573 In all these cases, the VPN customers set the policies, and the
574 Service Provider (SP) implements the policies by the way it
575 provisions the import and export RTs of the VRFs. It is assumed that
576 the customer communicates to the SP the set of extranet C-source
577 addresses and the set of VPNs to which each C-source can transmit.
578 (Recall that every C-source that can transmit to an extranet C-group
579 is an extranet C-source and must be able to transmit to any VPN that
580 has receivers for that group. This must be taken into account when
581 the provisioning is done.) This customer/SP communication is part of
582 the service provisioning process and is outside the scope of this
583 document.
584
585 It is possible that an extranet C-source will transmit both extranet
586 C-flows and non-extranet C-flows. However, if extranet C-receiver
587 C-R can receive extranet C-flows from extranet C-source C-S, the
588 procedures of this document do not prevent C-R from requesting and
589 receiving the non-extranet flows that are transmitted by C-S.
590 Therefore, allowing an extranet C-source to transmit non-extranet
591 C-flows is NOT RECOMMENDED. However, the SP has no control over the
592 set of C-flows transmitted by a given C-source and can do no more
593 than communicate this recommendation to its customers.
594 (Alternatively, the customer and SP may coordinate on setting up
595 filters to prevent unauthorized flows from being sent to a customer
596 site; such a procedure is outside the scope of this document.) See
597 <a href="#section-10">Section 10</a> ("Security Considerations") for additional discussion of
598 this issue.
599
600 Whenever a VPN is provisioned, there is a risk that errors in
601 provisioning may result in an unintended cross-connection of VPNs.
602 This would create a security problem for the customers. When
603 provisioning an extranet, attention to detail is particularly
604 important, as an extranet intentionally cross-connects VPNs. Care
605 must always be taken to ensure that the cross-connections are
606 according to the policy agreed upon by the SP and its customers.
607
608
609
610
611
612 <span class="grey">Rekhter, et al. Standards Track [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
615
616
617 Additionally, if one is connecting two VPNs that have overlapping
618 address spaces, one has to be sure that the inter-VPN traffic neither
619 originates from nor is destined to the part of the address space that
620 is in the overlap. Other problems that can arise due to overlapping
621 address spaces are discussed in <a href="#section-2">Section 2</a>.
622
623 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Extranets and Overlapping Address Spaces</span>
624
625 As specified in [<a href="./rfc4364" title="&quot;BGP/MPLS IP Virtual Private Networks (VPNs)&quot;">RFC4364</a>], the address space of one VPN may overlap
626 with the address space of another. A given address may be
627 "ambiguous" in that it denotes one system within VPN-A and a
628 different system within VPN-B. In the notation of <a href="#section-1.1">Section 1.1</a>,
629 if an address C-S is ambiguous between VPN-A and VPN-B, then
630 Host(C-S,A) != Host(C-S,B). However, any given address C-S MUST be
631 unambiguous (i.e., MUST denote a single system) in the context of a
632 given VPN.
633
634 When a set of VRFs belonging to different VPNs are combined into an
635 extranet, it is no longer sufficient for an address to be unambiguous
636 only within the context of a single VPN:
637
638 1. Suppose that C-S is the address of a given extranet C-source
639 contained in VPN-A. Now consider the set of VPNs
640 {VPN-B, VPN-C, ...} containing extranet C-receivers that are
641 allowed by policy to receive extranet C-flows from VPN-A's C-S.
642 The address C-S MUST be unambiguous among this entire set of VPNs
643 {VPN-A, VPN-B, VPN-C, ...}; i.e., Host(C-S,A) == Host(C-S,B) ==
644 Host(C-S,C).
645
646 The implication is that C-S in VPN-A is not necessarily an
647 extranet C-source for all VPNs that contain extranet C-receivers;
648 policy MUST be used to ensure that C-S is an extranet C-source
649 for a given VPN, say VPN-B, only if C-S is unambiguous between
650 VPN-A and VPN-B.
651
652 2. If a given VRF contains extranet C-receivers for a given extranet
653 C-source, then the address of this C-source MUST be unambiguous
654 among all the extranet C-sources for which there are C-receivers
655 in the VRF. This is true whether or not C-sources are in VRFs
656 that belong to the same VPN or different VPNs.
657
658 The implication is that if C-S in VRF-X is ambiguous with C-S in
659 VRF-Y, then there MUST NOT be any VRF, say VRF-Z, containing
660 C-receivers that are allowed by policy to receive extranet
661 C-flows from both C-S in VRF-X and C-S in VRF-Y.
662
663
664
665
666
667
668 <span class="grey">Rekhter, et al. Standards Track [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
671
672
673 Note: A VPN customer may be using anycast addresses. An anycast
674 address is intentionally ambiguous, as it denotes a set of systems
675 rather than a single system. In this document, we will consider an
676 anycast address to be unambiguous in a given context as long as it
677 denotes the same set of systems whenever it occurs in that context.
678
679 A multicast C-group address, say C-G, may also be ambiguous in that
680 it may be used for one multicast group in VPN-A and for an entirely
681 different multicast group in VPN-B. If a set of MVPNs are combined
682 into an extranet and C-G is an extranet C-group, it is necessary to
683 ensure that C-G is unambiguous among the entire set of VPNs whose
684 VRFs contain extranet C-sources, C-RPs, and/or extranet C-receivers
685 for that C-group. This may require, as part of the provisioning
686 process, customer/SP communication that is outside the scope of this
687 document.
688
689 Subject to these restrictions, the SP has complete control over the
690 distribution of routes in an MVPN. This control is exerted by
691 provisioning either (1) the export RTs on the VRFs that originate the
692 routes (i.e., the VRFs that contain the extranet C-sources) or
693 (2) the import RTs on the VRFs that receive the routes (i.e., the
694 VRFs that contain the extranet C-receivers), or both.
695
696 Some of the rules and restrictions on provisioning the RTs are
697 applicable to all extranets; these are specified in <a href="#section-4">Section 4</a>.
698 Sections <a href="#section-6">6</a> and <a href="#section-7">7</a> list additional rules and restrictions that are
699 applicable only to particular extranet scenarios.
700
701 Even if all the RTs are provisioned according to the above rules and
702 restrictions, it is still possible for a single P-tunnel to contain
703 multicast data packets whose source and/or group addresses are
704 ambiguous in the context of the set of PEs that receive data from the
705 P-tunnel. That is, the above rules and restrictions are necessary,
706 but not sufficient, to prevent address ambiguity from causing
707 misdelivery of traffic. To prevent such misdelivery, additional
708 procedures or policies must be used.
709
710 Sections <a href="#section-2.1">2.1</a> and <a href="#section-2.2">2.2</a> describe scenarios in which a given P-tunnel may
711 carry data packets with ambiguous addresses. The additional
712 procedures and policies needed to prevent misdelivery of data in
713 those scenarios are outlined in <a href="#section-2.3">Section 2.3</a>. (The detailed
714 procedures described in Sections <a href="#section-6">6</a> and <a href="#section-7">7</a> incorporate the
715 considerations discussed in <a href="#section-2.3">Section 2.3</a>.)
716
717
718
719
720
721
722
723
724 <span class="grey">Rekhter, et al. Standards Track [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
727
728
729 <span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Ambiguity: P-Tunnel with Extranet/Non-extranet Flows</span>
730
731 In the following, we will use the notation "VRF A-n" to mean "VRF n
732 of VPN-A".
733
734 If VPN-A and VPN-B have overlapping address spaces and are part of
735 the same extranet, then the following problem may exist, as
736 illustrated in Figure 1.
737
738 C-S2(A) C-S1 Join(C-S2(A),G)
739 \ / /
740 \ / /
741 +-------+---+ P1: (C-S1,G), (C-S2(A),G) +---+--------+
742 |VRF A-1| |---------------------------------| |VRF A-2 |
743 +-------+PE1| |PE2+--------+
744 |VRF B-1| |---------------------------------| |VRF B-2 |
745 +-------+---+ P2: (C-S2(B),G) +---+--------+
746 / / \
747 / / \
748 C-S2(B) Join(C-S2(B),G) Join(C-S1,G)
749
750 Figure 1: Ambiguity of Extranet and Non-extranet Source Address
751
752 Suppose that:
753
754 o C-G is an SSM C-group used in VPN-A and VPN-B.
755
756 o VRF A-1, on PE1, contains an extranet C-source, with IP address
757 C-S1, that is allowed to have receivers in VPN-B. VRF A-1 thus
758 exports to VPN-B a UMH-eligible route matching C-S1.
759
760 o In addition, VRF A-1 contains a non-extranet C-source with IP
761 address C-S2. VRF A-1 exports a UMH-eligible route matching C-S2
762 to other VPN-A VRFs but NOT to VPN-B.
763
764 o VRF B-1, also on PE1, contains a non-extranet C-source with IP
765 address C-S2. A UMH-eligible route matching C-S2 is thus exported
766 from VRF B-1 to other VRFs in VPN-B.
767
768 o Host(C-S2,A) != Host(C-S2,B). That is, C-S2 is an ambiguous
769 address in any extranet that contains both VPN-A VRFs and VPN-B
770 VRFs.
771
772 o VRF B-2, on some other PE, say PE2, requests the multicast flow
773 (C-S1,C-G). In the context of VRF B-2, C-S1 matches the route
774 exported from VRF A-1. Thus, B-2's request to receive the
775 (C-S1,C-G) flow is transmitted to VRF A-1.
776
777
778
779
780 <span class="grey">Rekhter, et al. Standards Track [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
783
784
785 o VRF A-1 responds to VRF B-2's request for (C-S1,C-G) traffic by
786 transmitting that traffic on P-tunnel P1.
787
788 o VRF B-2 joins P-tunnel P1 in order to receive the (C-S1,C-G)
789 traffic.
790
791 o VRF A-2, on PE2, requests the (non-extranet) multicast flow
792 (C-S2,C-G). In the context of VRF A-2, C-S2 matches the route
793 exported from VRF A-1. Thus, A-2's request to receive the
794 (C-S2,C-G) traffic is transmitted to VRF A-1.
795
796 o VRF A-1 responds to VRF A-2's request for (C-S2,C-G) traffic by
797 transmitting that traffic on P-tunnel P1.
798
799 o VRF A-2 joins P-tunnel P1 in order to receive the (C-S2,C-G)
800 traffic.
801
802 o VRF B-2 requests the (non-extranet) multicast flow (C-S2,C-G). In
803 the context of VRF B-2, C-S2 matches the route exported from VRF
804 B-1. Thus, B-2's request to receive the (C-S2,C-G) flow is
805 transmitted to VRF B-1.
806
807 o VRF B-1 responds to VRF B-2's request for (C-S2,C-G) traffic by
808 transmitting that traffic on P-tunnel P2.
809
810 o VRF B-2 joins P-tunnel P2.
811
812 Since VRF B-2 has joined P-tunnel P1 and P-tunnel P2, it will receive
813 (C-S2,C-G) traffic on both P-tunnels. The (C-S2,C-G) traffic that
814 VRF B-2 needs to receive is traveling on P-tunnel P2; this (C-S2,C-G)
815 traffic must be forwarded by B-2 to any attached customer sites that
816 have C-receivers for it. But B-2 MUST discard the (C-S2,C-G) traffic
817 that it receives on P1, as this is not the traffic that it has
818 requested. If the (C-S2,C-G) traffic arriving on P1 were forwarded
819 to B-2's customer sites, the C-receivers would not be able to
820 distinguish the two flows, and the result would be a corrupted data
821 stream.
822
823 Note that the procedures of <a href="./rfc6513#section-9.1.1">Section&nbsp;9.1.1 of [RFC6513]</a> ("Discarding
824 Packets from Wrong PE") will not cause VRF B-2 to discard the
825 (C-S2,C-G) traffic that arrives on tunnel P1, because P1 and P2 have
826 the same upstream PE.
827
828 Therefore, it is necessary to EITHER (1) prevent the above scenario
829 from occurring OR (2) ensure that multicast data packets will be
830 discarded if they arrive on the wrong P-tunnel (even if they arrive
831 from the expected PE). See <a href="#section-2.3">Section 2.3</a> for further discussion of
832 this issue.
833
834
835
836 <span class="grey">Rekhter, et al. Standards Track [Page 15]</span></pre>
837 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
838 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
839
840
841 <span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. Ambiguity: P-Tunnel with Multiple Extranet Flows</span>
842
843 Figure 2 illustrates another example of how overlapping address
844 spaces may cause a problem.
845
846 C-S2(A2D) C-S1(A2C) Join(C-S2(A2D),G)
847 \ / /
848 \ / /
849 +-------+---+ P1: (C-S1(A2C),G), (C-S2(A2D),G)+---+--------+
850 |VRF A-1| |---------------------------------| |VRF D-1 |
851 +-------+PE1| |PE2+--------+
852 |VRF B-1| |---------------------------------| |VRF C-1 |
853 +-------+---+ P2: (C-S2(B2C),G) +---+--------+
854 / / \
855 / / \
856 C-S2(B2C) / \
857 Join Join
858 (C-S2(B2C),G) (C-S1(A2C),G)
859
860 Figure 2: Ambiguity of Extranet Source Addresses
861
862 Suppose that:
863
864 o C-G is an SSM C-group address that is used in VPN-A, VPN-B, VPN-C,
865 and VPN-D.
866
867 o VRF A-1, on PE1, contains an extranet C-source, with IP address
868 C-S1, that is allowed by policy to have C-receivers in VPN-C (but
869 not in VPN-D). VRF A-1 thus exports a UMH-eligible route matching
870 C-S1 to VPN-C.
871
872 o In addition, VRF A-1 contains an extranet C-source, with IP
873 address C-S2, that is allowed by policy to have C-receivers in
874 VPN-D (but not in VPN-C). VRF A-1 thus exports a UMH-eligible
875 route matching C-S2 to VPN-D.
876
877 o VRF B-1, also on PE1, contains an extranet C-source, with IP
878 address C-S2, that is allowed by policy to have C-receivers in
879 VPN-C (but not in VPN-D). VRF B-1 thus exports a UMH-eligible
880 route matching C-S2 to VPN-C.
881
882 o Host(C-S2,A) != Host(C-S2,B). That is, C-S2 is an ambiguous
883 address in any extranet that contains both VPN-A VRFs and
884 VPN-B VRFs.
885
886
887
888
889
890
891
892 <span class="grey">Rekhter, et al. Standards Track [Page 16]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
894 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
895
896
897 o VRF C-1, on some other PE, say PE2, requests the extranet
898 multicast flow (C-S1,C-G). In the context of VRF C-1, C-S1
899 matches the route exported from VRF A-1. Thus, C-1's request to
900 receive the (C-S1,C-G) flow is transmitted to VRF A-1.
901
902 o VRF A-1 responds to VRF C-1's request for (C-S1,C-G) traffic by
903 transmitting that traffic on P-tunnel P1.
904
905 o VRF C-1 joins P-tunnel P1 in order to receive the (C-S1,C-G)
906 traffic.
907
908 o VRF C-1 requests the extranet multicast flow (C-S2,C-G). In the
909 context of VRF C-1, C-S2 matches the route exported from VRF B-1.
910 Thus, C-1's request to receive the (C-S2,C-G) flow is transmitted
911 to VRF B-1.
912
913 o VRF B-1 responds by transmitting its (C-S2,C-G) traffic on
914 P-tunnel P2.
915
916 o VRF C-1 joins P-tunnel P2 in order to receive the (C-S2,C-G)
917 traffic.
918
919 o VRF D-1, on PE2, requests the extranet multicast flow (C-S2,C-G).
920 In the context of VRF D-1, C-S2 matches the route exported from
921 VRF A-1. Thus, D-1's request to receive the (C-S2,C-G) flow is
922 transmitted to VRF A-1.
923
924 o VRF A-1 responds by transmitting its (C-S2,C-G) traffic on
925 P-tunnel P1.
926
927 o VRF D-1 joins P-tunnel P1 in order to receive the (C-S2,C-G)
928 traffic.
929
930 In this example, VRF A-1 has chosen to use the same P-tunnel, P1, to
931 carry both its (C-S2,C-G) traffic and the (C-S1,C-G) traffic. VRF
932 C-1 has joined tunnel P1 in order to receive the (C-S1,C-G) traffic
933 from VRF A-1, which means that VRF C-1 will also receive the unwanted
934 (C-S2,C-G) traffic from P1. VRF C-1 is also expecting (C-S2,C-G)
935 traffic from VRF B-1; this traffic will be received from P2. Thus,
936 VRF C-1 is receiving (C-S2,C-G) traffic on both tunnels, and both
937 C-flows arrive from the expected PE, PE1.
938
939 Therefore, it is necessary to EITHER (1) prevent the above scenario
940 from occurring OR (2) ensure that VRF C-1 discards any (C-S,C-G)
941 traffic that arrives from the wrong P-tunnel. See <a href="#section-2.3">Section 2.3</a> for
942 further discussion of this issue.
943
944
945
946
947
948 <span class="grey">Rekhter, et al. Standards Track [Page 17]</span></pre>
949 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
950 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
951
952
953 Note that the ambiguity described in this section (<a href="#section-2.2">Section 2.2</a>) would
954 not occur if C-G were an (ASM) extranet C-group. In that case, the
955 scenario would violate the rule, given previously in <a href="#section-2">Section 2</a>,
956 requiring that all sources sending to a particular ASM extranet
957 C-group must have addresses that are unambiguous over all the MVPNs
958 receiving traffic for that C-group.
959
960 <span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. Preventing Misdelivery in These Scenarios</span>
961
962 There are two ways to prevent the scenarios discussed in Sections <a href="#section-2.1">2.1</a>
963 and 2.2 from resulting in misdelivery of data; these techniques are
964 discussed in Sections <a href="#section-2.3.1">2.3.1</a> and <a href="#section-2.3.2">2.3.2</a>, respectively.
965
966 <span class="h4"><a class="selflink" id="section-2.3.1" href="#section-2.3.1">2.3.1</a>. Do Not Deliver Packets from the Wrong P-tunnel</span>
967
968 Consider a particular C-flow that has receivers in a particular VRF.
969 Sections <a href="#section-6">6</a> and <a href="#section-7">7</a> describe a set of procedures that enable an egress
970 PE to determine the "expected P-tunnel" for that C-flow in the
971 context of that VRF. If a PE receives packets of the C-flow (as
972 determined by the IP source and/or destination address of the
973 packet), it checks to see if the packet was received on the expected
974 P-tunnel for that VRF. If so, the packet is delivered to the VRF
975 (and thus to the C-flow's receivers in that VRF). If not, the packet
976 is not delivered to the VRF.
977
978 Note that at a given egress PE, the wrong P-tunnel for one VRF may be
979 the correct P-tunnel for another.
980
981 These procedures, if applied at every PE that joins a given P-tunnel,
982 are sufficient to prevent misdelivery of traffic in the scenarios
983 discussed in Sections <a href="#section-2.1">2.1</a> and <a href="#section-2.2">2.2</a>.
984
985 IF these procedures cannot be applied by every PE that is attached to
986 a given extranet, then the policies of <a href="#section-2.3.2">Section 2.3.2</a> MUST be applied
987 at every VRF containing C-sources for that extranet.
988
989 In some cases, however, it may be safe to deliver packets that arrive
990 from other than the expected P-tunnel. Suppose that it is known that
991 every packet gets transmitted on only a single P-tunnel. (This will
992 be the case if the "single PMSI per C-flow" transmission model,
993 discussed in <a href="#section-3.1">Section 3.1</a>, is being used.) Suppose also that it is
994 known that T1 and T2 carry only packets that arrived at the same
995 ingress PE, over one or more VRF interfaces that are associated with
996 the same VRF (i.e., that there is a particular VRF that is the
997 ingress VRF for ALL the packets carried by T1 or T2). In this case,
998 if T1 is the expected P-tunnel for a given (C-S,C-G), it is NOT
999 necessary to discard (S,G) packets that arrive over T2.
1000
1001
1002
1003
1004 <span class="grey">Rekhter, et al. Standards Track [Page 18]</span></pre>
1005 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
1006 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
1007
1008
1009 It is not always possible to determine whether two P-tunnels are
1010 carrying packets from the same ingress VRF. However, in some cases,
1011 this can be determined by examination of the A-D routes in which the
1012 tunnels have been advertised.
1013
1014 Consider the following example:
1015
1016 o Tunnel T1 is a Point-to-Multipoint (P2MP) multipoint Label
1017 Distribution Protocol (mLDP) or RSVP-TE P-tunnel advertised in an
1018 Intra-AS I-PMSI A-D route (call it "R1").
1019
1020 o Tunnel T2 is a P2MP mLDP or RSVP-TE P-tunnel advertised in an
1021 S-PMSI A-D route (call it "R2").
1022
1023 o The respective NLRIs of R1 and R2 contain the same RD value.
1024
1025 o The MPLS Label field of R1's PTA is zero, and the MPLS label value
1026 of R2's PTA is zero.
1027
1028 In this example, it can be concluded that T1 and T2 are carrying
1029 packets from the same ingress VRF. Thus, if T1 is the expected
1030 P-tunnel for a (C-S,C-G) flow, (S,G) packets from T2 can be safely
1031 delivered to the egress VRF; they do not need to be discarded.
1032 Similarly, if T2 is the expected P-tunnel for a (C-S,C-G) flow, (S,G)
1033 packets from T1 can be safely delivered to the egress VRF.
1034
1035 Another example is the following:
1036
1037 o Tunnel T3 is a P2MP mLDP or RSVP-TE P-tunnel advertised in a
1038 (C-*,C-*) S-PMSI A-D route (call it "R3").
1039
1040 o Tunnel T4 is a P2MP mLDP or RSVP-TE P-tunnel advertised in a
1041 (C-S,C-G) S-PMSI A-D route (call it "R4").
1042
1043 o The respective NLRIs of R3 and R4 contain the same RD value.
1044
1045 o The MPLS Label field of R3's PTA is zero, and the MPLS label value
1046 of R4's PTA is zero.
1047
1048 In this example, it can be concluded that T3 and T4 are carrying
1049 packets from the same ingress VRF. Thus, if T3 is the expected
1050 P-tunnel for a (C-S,C-G) flow, (S,G) packets from T4 can be safely
1051 delivered to the egress VRF; they do not need to be discarded.
1052 Similarly, if T4 is the expected P-tunnel for a (C-S,C-G) flow,
1053 (S,G) packets from T3 can be safely delivered to the egress VRF.
1054
1055
1056
1057
1058
1059
1060 <span class="grey">Rekhter, et al. Standards Track [Page 19]</span></pre>
1061 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
1062 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
1063
1064
1065 When Ingress Replication (IR) P-tunnels are being used, please see
1066 [<a href="#ref-MVPN-IR" title="&quot;Ingress Replication Tunnels in Multicast VPN&quot;">MVPN-IR</a>], especially <a href="#section-7">Section 7</a> ("The PTA's 'MPLS Label' Field") for
1067 a discussion of how to determine when packets from other than the
1068 expected P-tunnel must be discarded.
1069
1070 <span class="h4"><a class="selflink" id="section-2.3.2" href="#section-2.3.2">2.3.2</a>. Policies to Prevent Ambiguity on a P-Tunnel</span>
1071
1072 For P-tunnels that are advertised in S-PMSI A-D routes whose NLRI
1073 contains (C-S,C-G) or (C-S,C-*), the ambiguities described in
1074 Sections <a href="#section-2.1">2.1</a> and <a href="#section-2.2">2.2</a> can be prevented by provisioning a policy that
1075 assigns, to such P-tunnels, only flows from the same C-source.
1076
1077 However, it is not always possible to determine, through inspection
1078 of the control messages, whether this policy has been deployed. For
1079 instance, suppose that (1) a given VRF has imported a set of S-PMSI
1080 A-D routes, (2) each route in the set has bound only a single
1081 (C-S1,C-G1) to a single P-tunnel, and (3) each route in the set
1082 identifies a different P-tunnel in its PTA than the P-tunnel
1083 identified by the PTA of any other route in the set. One cannot
1084 infer from this that there is no ambiguity, as the same P-tunnel may
1085 also have been advertised in an S-PMSI A-D route that is not imported
1086 by the given VRF, and that S-PMSI A-D route may have bound
1087 (C-S2,C-G2) to the P-tunnel, where C-S1 != C-S2.
1088
1089 Therefore, in order to determine that a given P-tunnel (advertised in
1090 a (C-S,C-G) or (C-S,C-*) S-PMSI A-D route) carries only C-flows from
1091 a single C-source, a PE must have a priori knowledge (through
1092 provisioning) that this policy has been deployed. In the remainder
1093 of this document, we will refer to this policy as the "single
1094 C-source per (C-S,C-G) or (C-S,C-*) P-tunnel" policy. Note that this
1095 policy is only applicable to P-tunnels that are advertised only in
1096 (C-S,C-G) or (C-S,C-*) S-PMSI A-D routes.
1097
1098 Of course, if a P-tunnel is advertised in (a) an I-PMSI A-D route,
1099 (b) an S-PMSI A-D route whose NLRI contains (C-*,C-*), or (c) an
1100 S-PMSI A-D route whose NLRI contains (C-*,C-G), then it is always
1101 possible for the P-tunnel to contain traffic from multiple C-sources;
1102 there is no policy that can prevent that.
1103
1104 However, if a P-tunnel advertised in a (C-*,C-G) S-PMSI A-D route
1105 contains only traffic addressed to a single C-G, the address
1106 uniqueness rules of <a href="#section-2">Section 2</a> prevent the C-source addresses from
1107 being ambiguous; the set of C-sources transmitting to a particular
1108 extranet C-group address must be unambiguous over the set of MVPNs
1109 that have receivers for that C-group. So, for P-tunnels that are
1110 advertised in (C-*,C-G) S-PMSI A-D routes, the ambiguities described
1111 in Sections <a href="#section-2.1">2.1</a> and <a href="#section-2.2">2.2</a> can be prevented by provisioning a policy
1112
1113
1114
1115
1116 <span class="grey">Rekhter, et al. Standards Track [Page 20]</span></pre>
1117 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
1118 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
1119
1120
1121 that assigns to such P-tunnels only flows to the same extranet
1122 C-group. We will refer to this policy as the "single C-group per
1123 (C-*,C-G) P-tunnel" policy.
1124
1125 These considerations can be summarized as follows. IF the procedures
1126 referenced in <a href="#section-2.3.1">Section 2.3.1</a> cannot be applied, then the PEs MUST be
1127 provisioned so that all of the following conditions hold true for the
1128 VRFs that contain extranet C-sources:
1129
1130 o the "single C-source per (C-S,C-G) or (C-S,C-*) P-tunnel" policy
1131 is provisioned,
1132
1133 o either no (C-*,C-G) S-PMSI A-D routes are advertised or the
1134 "single C-group per (C-*,C-G) P-tunnel" policy is provisioned,
1135
1136 o no P-tunnels are advertised in I-PMSI A-D routes, and
1137
1138 o no (C-*,C-*) S-PMSI A-D routes are advertised.
1139
1140 <a href="#section-3">Section 3</a> of this document describes a procedure known as "extranet
1141 separation". When extranet separation is used, the ambiguity
1142 described in <a href="#section-2.1">Section 2.1</a> is prevented. However, the ambiguity
1143 described in <a href="#section-2.2">Section 2.2</a> is not prevented by extranet separation.
1144 Therefore, the use of extranet separation is not a sufficient
1145 condition for avoiding the use of the procedures discussed in
1146 <a href="#section-2.3.1">Section 2.3.1</a>. Extranet separation is, however, implied by the
1147 policies discussed in this section (<a href="#section-2.3.2">Section 2.3.2</a>).
1148
1149 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Extranet Transmission Models</span>
1150
1151 This document specifies several "extranet transmission" models. A
1152 given VRF containing extranet C-sources or C-receivers MUST use only
1153 one of these models. Further, if VRF-S contains extranet C-sources,
1154 VRF-R contains extranet C-receivers, and it is allowed by policy for
1155 an extranet C-receiver in VRF-R to receive a C-flow from an extranet
1156 C-source in VRF-S, then VRF-S and VRF-R MUST use the same extranet
1157 transmission model. The model used by a given VRF is determined by
1158 provisioning.
1159
1160 <span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Transmitting an Extranet C-Flow on a Single PMSI</span>
1161
1162 In one extranet transmission model, which we call the "transmitting
1163 an extranet C-flow on a single PMSI" model or, more simply, the
1164 "single PMSI per C-flow" model, a PE transmitting a packet of an
1165 extranet C-flow transmits it on only a single PMSI. If the PMSI is
1166 instantiated by a multicast P-tunnel, this means that the PE
1167 transmits the packet on a single P-tunnel. Of course, if the PE is a
1168 replication point for that multicast P-tunnel, the packet is
1169
1170
1171
1172 <span class="grey">Rekhter, et al. Standards Track [Page 21]</span></pre>
1173 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
1174 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
1175
1176
1177 transmitted more than once by the PE. Similarly, if the PMSI is
1178 instantiated by IR, each packet may be transmitted multiple times.
1179 It is still the case, though, that the packet is transmitted only on
1180 one PMSI.
1181
1182 This document provides procedures for supporting this transmission
1183 model using either BGP or PIM as the PE-PE C-multicast control
1184 protocol.
1185
1186 There are two variants of this transmission model: "without extranet
1187 separation" and "with extranet separation".
1188
1189 <span class="h4"><a class="selflink" id="section-3.1.1" href="#section-3.1.1">3.1.1</a>. Without Extranet Separation</span>
1190
1191 In this variant, multicast data traffic from extranet C-sources and
1192 from non-extranet C-sources may be carried in the same P-tunnel.
1193
1194 This document provides procedures for supporting this variant using
1195 either BGP or PIM as the PE-PE C-multicast control protocol.
1196
1197 <span class="h4"><a class="selflink" id="section-3.1.2" href="#section-3.1.2">3.1.2</a>. With Extranet Separation</span>
1198
1199 In this variant, multicast data traffic from extranet C-sources and
1200 from non-extranet C-sources are never carried in the same P-tunnel.
1201 Under certain circumstances, this can reduce the amount of multicast
1202 data traffic that is delivered unnecessarily to certain PE routers.
1203 It also eliminates the ambiguity discussed in <a href="#section-2.1">Section 2.1</a>.
1204
1205 By definition, when extranet separation is used, the following rule
1206 MUST be applied:
1207
1208 Traffic from extranet C-sources MUST NOT be carried in the same
1209 P-tunnel as traffic from non-extranet C-sources.
1210
1211 This rule does not impact those VRFs that contain only non-extranet
1212 C-sources, nor does it impact those VRFs that contain only extranet
1213 C-sources. However, if a particular VRF contains both kinds of
1214 C-sources, it will need to advertise some P-tunnels that are used for
1215 carrying only extranet C-flows and some that are used only for
1216 carrying non-extranet C-flows.
1217
1218 This document provides procedures for supporting extranet separation
1219 when BGP is used as the PE-PE C-multicast control protocol. Support
1220 for extranet separation using PIM as the PE-PE C-multicast control
1221 protocol is outside the scope of this document.
1222
1223
1224
1225
1226
1227
1228 <span class="grey">Rekhter, et al. Standards Track [Page 22]</span></pre>
1229 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
1230 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
1231
1232
1233 <span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Transmitting an Extranet C-Flow over Multiple PMSIs</span>
1234
1235 The second extranet transmission model is called the "transmitting an
1236 extranet C-flow over multiple PMSIs" model or, more simply, the
1237 "multiple PMSIs per C-flow" model. In this model, a PE may transmit
1238 the packets of an extranet C-flow on several different PMSIs.
1239
1240 Support for extranet separation with this model is outside the scope
1241 of this document.
1242
1243 This document provides procedures for supporting this transmission
1244 model when PIM is used as the PE-PE C-multicast control protocol.
1245 Support for this transmission model when BGP is used as the PE-PE
1246 C-multicast control protocol is outside the scope of this document.
1247
1248 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Distribution of Routes That Match C-S/C-RP Addresses</span>
1249
1250 <span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. UMH-Eligible Routes</span>
1251
1252 As described in <a href="./rfc6513#section-5.1">Section&nbsp;5.1 of [RFC6513]</a>, in order for a C-flow
1253 (C-S,C-G) to be carried across the SP backbone, a VRF that has
1254 multicast receivers for that C-flow must import a route that matches
1255 C-S, and this route must be "eligible for UMH selection". In this
1256 document, we will refer to these routes as "UMH-eligible extranet
1257 C-source routes".
1258
1259 The UMH-eligible extranet C-source routes do not necessarily have to
1260 be unicast routes; they MAY be SAFI 129 routes (see <a href="./rfc6513#section-5.1.1">Section&nbsp;5.1.1 of
1261 [RFC6513]</a>). For example, suppose that one wants a VPN-R C-receiver
1262 to be able to receive extranet C-flows from C-sources in VPN-S but
1263 does not want any VPN-R system to be able to send unicast traffic to
1264 those C-sources. One can achieve this by using SAFI 129 routes as
1265 the UMH-eligible routes exported from VPN-S and imported by VPN-R.
1266 Since SAFI 129 routes are used only for UMH determination and not for
1267 unicast routing, this allows the multicast traffic to be forwarded
1268 properly but does not create unicast routes to the C-sources.
1269
1270 If a customer is using PIM-SM in the ASM model and one or more
1271 customer sites have C-receivers that are allowed by policy to join a
1272 (C-*,C-G) tree, where C-G is an extranet C-group, then any VRF with
1273 C-receivers for that group MUST import a UMH-eligible route that
1274 matches C-RP, where C-RP is the Rendezvous Point (RP) address
1275 for C-G.
1276
1277 The UMH-eligible extranet C-source and C-RP routes do not have to be
1278 "host routes". That is, they can be routes whose IPv4 address
1279 prefixes are not 32 bits in length or whose IPv6 address prefixes are
1280 not 128 bits in length. So, it is possible for a UMH-eligible
1281
1282
1283
1284 <span class="grey">Rekhter, et al. Standards Track [Page 23]</span></pre>
1285 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
1286 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
1287
1288
1289 extranet C-source route to match the address of an extranet C-source
1290 and to also match the address of a non-extranet C-source. However,
1291 if such a route is exported from a VPN-S VRF and imported by a VPN-R
1292 VRF, VPN-R receivers will be able to receive C-flows from any
1293 non-extranet C-sources whose addresses match that route. To prevent
1294 this, the VPN-S VRF SHOULD be provisioned such that it will NOT
1295 export a UMH-eligible route that matches (in the context of the VPN-R
1296 VRF) both extranet C-sources and non-extranet C-sources. Failure to
1297 follow this rule may result in a VPN security violation. (See
1298 <a href="#section-10">Section 10</a>.)
1299
1300 In general, one does not want ALL the routes from the VPN-S VRFs to
1301 be exported to all the VPN-R VRFs, as only a subset of the routes in
1302 the VPN-S VRFs will be UMH-eligible extranet C-source routes. Route
1303 distribution is, as is always the case for a BGP/MPLS IP VPN
1304 [<a href="./rfc4364" title="&quot;BGP/MPLS IP Virtual Private Networks (VPNs)&quot;">RFC4364</a>], controlled by Route Targets (RTs). A variety of route
1305 distribution policies can be created by appropriately provisioning
1306 the import and export RTs of the various VRFs.
1307
1308 For example, the VPN-S VRFs that contain extranet C-sources could be
1309 configured to apply an export RT whose value is "RT-A-extranet" to
1310 the routes that match the extranet C-sources. The VPN-R VRFs that
1311 contain extranet C-receivers allowed to receive extranet C-flows
1312 from VPN-S extranet C-sources could then be configured with
1313 "RT-A-extranet" as an import RT.
1314
1315 Arbitrarily complex policies can be created by suitable manipulation
1316 of the import and export RTs.
1317
1318 <span class="h4"><a class="selflink" id="section-4.1.1" href="#section-4.1.1">4.1.1</a>. Extranet Separation</span>
1319
1320 If extranet separation is being used and a given VRF is exporting
1321 UMH-eligible routes for both extranet C-sources and non-extranet
1322 C-sources, then the VRF MUST be configured not only with its
1323 default RD but also with an extranet RD. The exported UMH-eligible
1324 routes MUST contain the extranet RD in their NLRIs.
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340 <span class="grey">Rekhter, et al. Standards Track [Page 24]</span></pre>
1341 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span>
1342 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
1343
1344
1345 <span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Distribution of Unicast Routes Matching C-RPs and DRs</span>
1346
1347 Consider a C-source, C-S, that may transmit to a particular extranet
1348 C-group, C-G.
1349
1350 In order to follow the procedures of [<a href="./rfc7761" title="&quot;Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)&quot;">RFC7761</a>],
1351
1352 o The "first-hop designated router (DR)" for C-S needs to be able to
1353 unicast PIM Register messages to a C-RP that services C-G.
1354
1355 o The C-RPs servicing C-G need to be able to unicast PIM
1356 Register-Stop messages to the DR for C-S.
1357
1358 It follows that if a VRF contains C-S but does not contain a C-RP for
1359 C-G, then the VRF MUST import a unicast route matching a C-RP for
1360 C-G. Note that the unicast route matching the C-RP is needed whether
1361 or not the VRF has also imported a SAFI 129 route matching the C-RP.
1362 (If the VRF also contains receivers for C-G and UMH determination is
1363 being done using SAFI 129 routes, both a unicast route and a SAFI 129
1364 matching C-RP route are needed.)
1365
1366 Similarly, if a VRF contains a C-RP for C-G but does not contain C-S,
1367 the VRF MUST import a unicast route matching the DR for C-S. Note
1368 that the unicast route matching the DR for C-S is needed even if UMH
1369 determination is being done using SAFI 129 routes; in that case, if
1370 the VRF also contains receivers for C-G, it needs to import a
1371 SAFI 129 route matching C-S and a unicast route matching the DR
1372 for C-S.
1373
1374 If, for a particular extranet C-group, C-G, the customer is using
1375 "anycast-RP" [<a href="./rfc3446" title="&quot;Anycast Rendevous Point (RP) mechanism using Protocol Independent Multicast (PIM) and Multicast Source Discovery Protocol (MSDP)&quot;">RFC3446</a>] [<a href="./rfc4610" title="&quot;Anycast-RP Using Protocol Independent Multicast (PIM)&quot;">RFC4610</a>] or the Multicast Source Discovery
1376 Protocol (MSDP) [<a href="./rfc3618" title="&quot;Multicast Source Discovery Protocol (MSDP)&quot;">RFC3618</a>], then all the C-RPs serving C-G need to
1377 send unicast messages to each other. Thus, any VRF that contains a
1378 C-RP for C-G needs to import unicast routes matching ALL the other
1379 C-RPs that serve C-G.
1380
1381 The need to distribute these unicast routes is usually not a problem
1382 as long as all the C-sources and C-RPs for C-G are in the same MVPN.
1383 If, however, the C-sources are not all in the same MVPN, great care
1384 must be taken to ensure that the unicast routes mentioned above are
1385 properly distributed.
1386
1387 There may be scenarios in which all the C-sources for C-G are in the
1388 same MVPN, but there are receivers in different VPNs, and some or all
1389 of the VPNs with receivers have their own C-RPs for C-G. In this
1390 case, care must be taken to ensure that the C-RPs can all unicast to
1391 each other.
1392
1393
1394
1395
1396 <span class="grey">Rekhter, et al. Standards Track [Page 25]</span></pre>
1397 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span>
1398 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
1399
1400
1401 <span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. Route Targets and Ambiguous UMH-Eligible Routes</span>
1402
1403 This section imposes a constraint on the way RTs are assigned to
1404 (a) UMH-eligible routes and (b) the BGP A-D routes that advertise
1405 P-tunnels (i.e., BGP A-D routes that contain a PTA). The constraint
1406 specified here applies to any extranet for which the ambiguity
1407 described in <a href="#section-2.2">Section 2.2</a> is possible. (The conditions under which
1408 such ambiguity is possible are also described in <a href="#section-2.2">Section 2.2</a>.)
1409
1410 We want to ensure that, in any given VRF, the UMH-eligible route
1411 matching a given extranet C-source has an RT in common with every BGP
1412 A-D route that advertises a P-tunnel that may be used to carry
1413 extranet multicast traffic from that C-source. We also want to
1414 ensure that the UMH-eligible route matching a given extranet C-source
1415 does not have any RT in common with any BGP A-D route that advertises
1416 a P-tunnel that may be used to carry any multicast traffic from a
1417 different C-source that has the same IP address. This enables us to
1418 determine whether traffic that appears to be from the given C-source
1419 is really arriving on the wrong P-tunnel and hence is really from a
1420 different C-source with the same IP address.
1421
1422 Suppose that an IP address C-S is used in VPN-A as the address of one
1423 system and used in VPN-B as the address of a different system. In
1424 this case, one or more VPN-A VRFs may export a VPN-IP route whose
1425 NLRI is &lt;RD1,S&gt;, and one or more VPN-B VRFs may export a VPN-IP route
1426 whose NLRI is &lt;RD2,S&gt;, where RD1 != RD2. Consider two routes -- R1
1427 and R2 -- for which the following conditions all hold:
1428
1429 o R1 and R2 are UMH-eligible extranet C-source or C-RP routes, or
1430 are unicast routes matching a C-RP.
1431
1432 o R1 is exported from a VRF of VPN-A, while R2 is exported from a
1433 VRF of a different VPN, say VPN-B.
1434
1435 o R1's NLRI specifies IP address prefix S/n.
1436
1437 o R2's NLRI specifies IP address prefix S/m.
1438
1439 o m &gt;= n (S/m is either the same as or more specific than S/n).
1440
1441 o There is some host address H such that:
1442
1443 * H denotes a different system in VPN-A than in VPN-B, and
1444
1445 * H/m == S/m (so either S/m or S/n might be a longest match for H
1446 in some VRF).
1447
1448
1449
1450
1451
1452 <span class="grey">Rekhter, et al. Standards Track [Page 26]</span></pre>
1453 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span>
1454 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
1455
1456
1457 We impose the following constraint: RTs MUST be assigned in such a
1458 way that R1 and R2 do not have any RT in common.
1459
1460 (This constraint is not as onerous as it may seem. Typically, R1 and
1461 R2 would not have an RT in common, as that might result in their
1462 being imported into the same VRF, making the address H ambiguous in
1463 that VRF.)
1464
1465 Sections <a href="#section-6">6</a> and <a href="#section-7">7</a> specify procedures for determining if a received
1466 C-flow has been received over the expected P-tunnel. Those
1467 procedures will not work if this constraint is violated. (The
1468 constraint described in this section is necessary, but not
1469 sufficient, for the procedures of Sections <a href="#section-6">6</a> and <a href="#section-7">7</a> to work;
1470 additional constraints that cover the assignment of RTs to BGP A-D
1471 routes are given in subsequent sections.)
1472
1473 <span class="h3"><a class="selflink" id="section-4.4" href="#section-4.4">4.4</a>. Dynamically Marking Extranet Routes</span>
1474
1475 <span class="h4"><a class="selflink" id="section-4.4.1" href="#section-4.4.1">4.4.1</a>. The Extranet Source Extended Community</span>
1476
1477 Sections <a href="#section-4.1">4.1</a>, <a href="#section-4.2">4.2</a>, and <a href="#section-4.3">4.3</a> place specific requirements on the way in
1478 which certain VPN-IP routes are distributed. In order to ensure that
1479 these requirements are met, a VPN customer must tell its SP which
1480 routes are the matching routes for extranet C-sources and C-RPs.
1481 This may be done as part of the provisioning process. Note that this
1482 does not necessarily require customer/provider interaction every time
1483 the customer adds a new extranet C-source or C-RP, but only when the
1484 IP address of the new C-source or C-RP does not match an existing
1485 route that is already being distributed as a VPN-IP extranet route.
1486 Nevertheless, it seems worthwhile to support an OPTIONAL mechanism
1487 that allows a customer to dynamically mark certain routes as being
1488 extranet routes.
1489
1490 To facilitate this, we define a new Transitive Opaque Extended
1491 Community (see [<a href="./rfc4360" title="&quot;BGP Extended Communities Attribute&quot;">RFC4360</a>], [<a href="./rfc7153" title="&quot;IANA Registries for BGP Extended Communities&quot;">RFC7153</a>], and <a href="#section-9">Section 9</a> of this document):
1492 the Extranet Source Extended Community. When a Customer Edge (CE)
1493 router advertises (via BGP) a route to a PE router and the AFI/SAFI
1494 of the route is 1/1, 1/2, 1/4, 2/1, 2/2, or 2/4, the Extranet Source
1495 Extended Community MAY be attached to the route. The value field of
1496 the Extended Community MUST be set to zero. By placing this Extended
1497 Community on a particular route, a CE router indicates to a PE router
1498 that the procedures of Sections <a href="#section-4.1">4.1</a>, <a href="#section-4.2">4.2</a>, and <a href="#section-4.3">4.3</a> are to be applied
1499 to that route. That is, the CE router may use this Extended
1500 Community to indicate to the PE router that a particular route is to
1501 be treated as a route that matches the address of an extranet source
1502 and is to be exported accordingly to other VPNs. A PE router that
1503 interprets this Extended Community MUST ignore the contents of the
1504 value field.
1505
1506
1507
1508 <span class="grey">Rekhter, et al. Standards Track [Page 27]</span></pre>
1509 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span>
1510 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
1511
1512
1513 Whether a CE router uses the Extranet Source Extended Community is
1514 determined by the configuration of the CE router. If used, the set
1515 of routes to which the Extended Community is attached is also
1516 determined by configuration of the CE. Note that a particular PE
1517 router may or may not support the use of the Extranet Source Extended
1518 Community by a particular CE router; this is determined by the
1519 service agreement between the SP and its customer.
1520
1521 If a CE is advertising SAFI 2 routes to the PE as the UMH-eligible
1522 extranet C-source and C-RP routes and the CE is using the Extranet
1523 Source Extended Community, it is important that the CE attach that
1524 Extended Community to the SAFI 2 routes, rather than just to the
1525 corresponding SAFI 1 routes. Otherwise, extranet receivers may not
1526 be able to join the (C-S,C-G) or (C-*,C-G) multicast trees.
1527
1528 However, if the C-sources and the C-RPs for a given extranet C-group
1529 are not all in the same VPN, the Extended Community would also have
1530 to be attached to the SAFI 1 routes that match the C-RP addresses and
1531 to the SAFI 1 routes that match the addresses of the first-hop
1532 designated routers for all the C-sources. Otherwise, the first-hop
1533 routers might not be able to send PIM Register messages to the C-RPs,
1534 and the C-RPs might not be able to send PIM Register-Stop messages to
1535 the first-hop routers.
1536
1537 While this Extended Community allows a customer to inform the SP
1538 dynamically that certain routes are "extranet routes", it does not
1539 allow a customer to control the set of RTs that the route will carry
1540 when it is redistributed as a VPN-IP route. Thus, it is only useful
1541 when all the extranet routes from a given VRF are exported with
1542 exactly the same set of RTs. (cf. <a href="./rfc4364#section-4.3.1">Section&nbsp;4.3.1 of [RFC4364]</a>, which
1543 does provide a mechanism that, if properly supported by the SP,
1544 allows the customer to determine the set of RTs carried by a VPN-IP
1545 route.) A CE SHOULD NOT attach the Extranet Source Extended
1546 Community to any route for which it uses another method of specifying
1547 the RTs to be carried by that route. A CE SHOULD NOT attach the
1548 Extranet Source Extended Community to a route unless all the extranet
1549 routes from the CE's VPN are intended to carry the same set of RTs.
1550
1551 A PE SHOULD ignore the Extranet Source Extended Community if it
1552 appears on a route that the CE should not have put it on. A PE that
1553 ignores the Extranet Source Extended Community SHOULD NOT follow the
1554 procedures of <a href="#section-4.4.2">Section 4.4.2</a>.
1555
1556 Note that misconfiguration on the CE router can result in the
1557 Extranet Source Extended Community being mistakenly attached to a
1558 route that is not intended to be exported as an extranet route. This
1559 could result in a VPN security violation.
1560
1561
1562
1563
1564 <span class="grey">Rekhter, et al. Standards Track [Page 28]</span></pre>
1565 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span>
1566 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
1567
1568
1569 <span class="h4"><a class="selflink" id="section-4.4.2" href="#section-4.4.2">4.4.2</a>. Distribution of Extranet Source Extended Community</span>
1570
1571 Suppose that a PE receives from a CE a route (call it "R") with the
1572 Extranet Source Extended Community. The PE must determine (via the
1573 considerations discussed in <a href="#section-4.4.1">Section 4.4.1</a>) whether it should ignore
1574 that Extended Community on route R; if it should ignore the Extended
1575 Community, the procedures described in this section are not followed.
1576
1577 Otherwise, when the PE originates a VPN-IP route corresponding to
1578 route R, the PE MUST attach this Extended Community to that route.
1579
1580 A Route Reflector MUST NOT add or remove the Extranet Source Extended
1581 Community from the VPN-IP routes reflected by the Route Reflector,
1582 including the case where VPN-IP routes received via Internal BGP
1583 (IBGP) are reflected to External BGP (EBGP) peers (inter-AS
1584 option (c); see <a href="./rfc4364#section-10">Section&nbsp;10 of [RFC4364]</a>). The value of the Extended
1585 Community MUST NOT be changed by the Route Reflector.
1586
1587 When re-advertising VPN-IP routes, Autonomous System Border Routers
1588 (ASBRs) MUST NOT add/remove the Extranet Source Extended Community
1589 from these routes. This includes inter-AS options (b) and (c) (see
1590 <a href="./rfc4364#section-10">Section&nbsp;10 of [RFC4364]</a>). The value of the Extended Community
1591 MUST NOT be changed by the ASBRs.
1592
1593 When a PE advertises (via BGP) IP routes to a CE, these routes
1594 MUST NOT carry the Extranet Source Extended Community unless the
1595 PE-CE connection is actually an inter-AS option (a) connection (see
1596 <a href="./rfc4364#section-10">Section&nbsp;10 of [RFC4364]</a>). When the PE-CE connection is not an
1597 inter-AS option (a) connection, a CE that receives an IP route with
1598 the Extranet Source Extended Community MUST remove it from the route
1599 before re-advertising the route.
1600
1601 The rules for attaching the Extranet Source Extended Community to a
1602 VPN-IP route, and the rules for propagating that Extended Community,
1603 are needed in order to support the scenario in which a VPN contains
1604 an option (a) interconnect (see <a href="./rfc4364#section-10">Section&nbsp;10 of [RFC4364]</a>). At the
1605 option (a) interconnect, the VPN-IP route gets translated back to an
1606 IP route, and the RTs are stripped off before the IP route is
1607 propagated. If the Extranet Source Extended Community has also been
1608 stripped off, there is no way for the router at the other end of the
1609 option (a) interconnect to know that the route represents an extranet
1610 source. Thus, the technique of using the Extranet Source Extended
1611 Community to dynamically signal that a particular route represents an
1612 extranet source will not work correctly across an option (a)
1613 interconnect unless the rules in this section are followed.
1614
1615
1616
1617
1618
1619
1620 <span class="grey">Rekhter, et al. Standards Track [Page 29]</span></pre>
1621 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span>
1622 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
1623
1624
1625 <span class="h3"><a class="selflink" id="section-4.5" href="#section-4.5">4.5</a>. The Extranet Separation Extended Community</span>
1626
1627 We define a new Transitive Opaque Extended Community: the Extranet
1628 Separation Extended Community (see [<a href="./rfc4360" title="&quot;BGP Extended Communities Attribute&quot;">RFC4360</a>], [<a href="./rfc7153" title="&quot;IANA Registries for BGP Extended Communities&quot;">RFC7153</a>], and
1629 <a href="#section-9">Section 9</a> of this document). This Extended Community is used only
1630 when extranet separation is being used. Its value field MUST be set
1631 to zero upon origination, MUST be ignored upon reception, and MUST be
1632 passed unchanged by intermediate routers. A Route Reflector MUST NOT
1633 add or remove the Extranet Separation Extended Community from the
1634 routes it reflects, including the case where routes received via IBGP
1635 are reflected to EBGP peers (inter-AS option (c); see <a href="./rfc4364#section-10">Section&nbsp;10 of
1636 [RFC4364]</a>).
1637
1638 If a VRF has been provisioned to use extranet separation and that VRF
1639 has been provisioned to transmit any extranet C-flows on a P-tunnel
1640 that it advertises in an I-PMSI A-D route or a (C-*,C-*) S-PMSI A-D
1641 route, then any UMH-eligible routes that are exported from that VRF
1642 following the procedures of Sections <a href="#section-4.1">4.1</a>, <a href="#section-4.2">4.2</a>, and <a href="#section-4.3">4.3</a> MUST carry the
1643 Extranet Separation Extended Community. In addition, if an I-PMSI
1644 A-D route and/or (C-*,C-*) S-PMSI A-D route exported from that VRF is
1645 used to carry extranet traffic, that A-D route MUST also carry the
1646 Extranet Separation Extended Community. Further details may be found
1647 in Sections <a href="#section-7.3">7.3</a>, <a href="#section-7.4.4">7.4.4</a>, and <a href="#section-7.4.5">7.4.5</a>.
1648
1649 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Origination and Distribution of BGP A-D Routes</span>
1650
1651 Except where otherwise specified, this section describes procedures
1652 and restrictions that are independent of the PE-PE C-multicast
1653 control protocol.
1654
1655 <span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Route Targets of UMH-Eligible Routes and A-D Routes</span>
1656
1657 Suppose that there is an extranet C-flow such that:
1658
1659 o The extranet C-source of that C-flow is in VRF A-1.
1660
1661 o One or more extranet C-receivers of that C-flow are in VRF B-1.
1662
1663 In this case, VRF A-1 MUST export a UMH-eligible route that matches
1664 the extranet C-source address, and VRF B-1 MUST import that route.
1665 In addition, VRF A-1 MUST export an Intra-AS I-PMSI A-D route or an
1666 S-PMSI A-D route specifying the P-tunnel through which it will send
1667 the data traffic of the given extranet C-flow, and VRF B-1 MUST
1668 import that route. If BGP is the PE-PE C-multicast control protocol,
1669 then under certain conditions (as specified in [<a href="./rfc6514" title="&quot;BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs&quot;">RFC6514</a>]), VRF A-1
1670 may also need to export a Source Active A-D route specifying that it
1671 contains a source of the given C-flow, and VRF B-1 must import that
1672 Source Active A-D route. That is, in order for VRF B-1 to receive a
1673
1674
1675
1676 <span class="grey">Rekhter, et al. Standards Track [Page 30]</span></pre>
1677 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span>
1678 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
1679
1680
1681 C-flow from a given extranet C-source contained in VRF A-1, VRF A-1
1682 MUST export a set of A-D routes that are "about" that source, and VRF
1683 B-1 MUST import them.
1684
1685 One way to ensure this is to provision an RT that is carried by all
1686 the routes exported from VRF A-1 that are "about" a given extranet
1687 C-source and also provision this RT as an import RT at any VRF (such
1688 as VRF B-1) that is allowed to receive extranet flows from that
1689 source.
1690
1691 If the "single PMSI per C-flow" transmission model is being used
1692 (with or without extranet separation), there is an additional
1693 requirement, stated below, regarding the way RTs are provisioned, as
1694 the RTs carried by a UMH-eligible route that matches a given extranet
1695 C-source may need to be used to identify the A-D routes that are
1696 "about" that source.
1697
1698 Consider the following scenario:
1699
1700 o IP address S is the address of one system in VPN-A and the address
1701 of a different system in VPN-B.
1702
1703 o VRF A-1 on PE1 exports UMH-eligible route R1, which is a matching
1704 route for S.
1705
1706 o VRF A-1 on PE1 exports an A-D route P1 whose PTA identifies a
1707 P-tunnel through which VRF A-1 may send traffic whose C-source is
1708 S, where one of the following conditions holds:
1709
1710 * P1 is an I-PMSI A-D route, OR
1711
1712 * P1 is an S-PMSI A-D route whose NLRI contains (C-*,C-*) or
1713 (C-*,C-G), OR
1714
1715 * P1 is an S-PMSI A-D route whose NLRI contains (C-S,C-G) or
1716 (C-S,C-*), BUT the "single C-source per (C-S,C-G) or (C-S,C-*)
1717 P-tunnel" policy is not provisioned, OR
1718
1719 * P1 is a Source Active A-D route whose NLRI contains (C-S,C-G).
1720
1721
1722
1723
1724
1725
1726
1727
1728
1729
1730
1731
1732 <span class="grey">Rekhter, et al. Standards Track [Page 31]</span></pre>
1733 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span>
1734 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
1735
1736
1737 o VRF B-1 on PE1 exports a UMH-eligible route R2, which is a
1738 matching route for S.
1739
1740 o VRF B-1 on PE1 exports an A-D route P2 whose PTA identifies a
1741 P-tunnel on which VRF B-1 may send traffic whose C-source is S,
1742 where one of the following conditions holds:
1743
1744 * P2 is an I-PMSI A-D route, OR
1745
1746 * P2 is an S-PMSI A-D route whose NLRI specifies (C-*,C-*) or
1747 (C-*,C-G), OR
1748
1749 * P2 is an S-PMSI A-D whose NLRI specifies (C-S,C-G) or
1750 (C-S,C-*), BUT the "single C-source per (C-S,C-G) or (C-S,C-*)
1751 P-tunnel" policy is not provisioned, OR
1752
1753 * P2 is a Source Active A-D route whose NLRI contains (C-S,C-G).
1754
1755 As implied by the rules of <a href="#section-4.1">Section 4.1</a>, there MUST NOT be any RT that
1756 is common to both R1 and R2. In addition, the following set of rules
1757 for RT assignment MUST be followed when extranets are supported.
1758 These rules support all the extranet transmission models described in
1759 this specification:
1760
1761 o There MUST NOT be any RT that is carried by both P1 and P2.
1762
1763 o The intersection of the set of RTs carried by P1 and the set of
1764 RTs carried by R1 MUST be non-null, and any VRF that imports both
1765 P1 and R1 MUST be configured with an import RT from this
1766 intersection.
1767
1768 o The intersection of the set of RTs carried by P2 and the set of
1769 RTs carried by R2 MUST be non-null, and any VRF that imports both
1770 P2 and R2 MUST be configured with an import RT from this
1771 intersection.
1772
1773
1774
1775
1776
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788 <span class="grey">Rekhter, et al. Standards Track [Page 32]</span></pre>
1789 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-33" ></span>
1790 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
1791
1792
1793 Suppose that VRF C-1 on PE2 imports P1 and R1 from VRF A-1 while also
1794 importing P2 from VRF B-1. Since
1795
1796 o R1 is VRF C-1's route to S,
1797
1798 o R1 has an RT in common with P1, and
1799
1800 o R1 has no RT in common with P2,
1801
1802 it can be concluded that VRF C-1 should expect that multicast traffic
1803 from S will arrive on the P-tunnel specified in P1. See Sections <a href="#section-6">6</a>
1804 and 7 for more details on determining the expected P-tunnel for a
1805 given extranet C-flow.
1806
1807 While the assignment of import and export RTs to routes is a
1808 deployment and provisioning issue rather than a protocol issue, it
1809 should be understood that failure to follow these rules is likely to
1810 result in VPN security violations.
1811
1812 <span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Considerations for Particular Inclusive Tunnel Types</span>
1813
1814 An Inclusive Tunnel (sometimes referred to as an "Inclusive Tree";
1815 see <a href="./rfc6513#section-2.1.1">Section&nbsp;2.1.1 of [RFC6513]</a>) is a tunnel that, by default, carries
1816 all the multicast traffic of a given MVPN that enters the backbone
1817 network via a particular PE. An Inclusive Tunnel is advertised in
1818 the PTA of an I-PMSI A-D route.
1819
1820 <span class="h4"><a class="selflink" id="section-5.2.1" href="#section-5.2.1">5.2.1</a>. RSVP-TE P2MP or Ingress Replication</span>
1821
1822 This section applies when Inclusive Tunnels are created using either
1823 RSVP-TE P2MP or IR.
1824
1825 Suppose that a VRF, say VRF-S, contains a given extranet C-source
1826 C-S, and VRF-S advertises in its Intra-AS I-PMSI A-D route either a
1827 P2MP RSVP-TE P-tunnel or an IR P-tunnel to carry extranet traffic.
1828
1829 In order for VRF-S to set up the P2MP RSVP-TE or IR P-tunnel, it must
1830 know all the PEs that are leaf nodes of the P-tunnel, and to learn
1831 this it must import an Intra-AS I-PMSI A-D route from every VRF that
1832 needs to receive data through that tunnel.
1833
1834 Therefore, if VRF-R contains an extranet C-receiver that is allowed
1835 by policy to receive extranet flows from C-S, the RT(s) carried by
1836 the Intra-AS I-PMSI A-D routes originated by VRF-R MUST be such that
1837 those Intra-AS I-PMSI A-D routes will be imported into VRF-S.
1838
1839
1840
1841
1842
1843
1844 <span class="grey">Rekhter, et al. Standards Track [Page 33]</span></pre>
1845 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-34" ></span>
1846 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
1847
1848
1849 In the case of IR, this has the following consequence: if an egress
1850 PE has n VRFs with receivers for a flow that VRF-S transmits on its
1851 I-PMSI, that egress PE will receive n copies of the same packet, one
1852 for each of the n VRFs.
1853
1854 Note that <a href="./rfc6514#section-9.1.1">Section&nbsp;9.1.1 of [RFC6514]</a> prohibits the "Leaf Information
1855 Required" flag from being set in the PTA of an Intra-AS I-PMSI A-D
1856 route. If this prohibition is ever removed, the requirement of this
1857 section will apply only if VRF-S does not set that flag.
1858
1859 <span class="h4"><a class="selflink" id="section-5.2.2" href="#section-5.2.2">5.2.2</a>. Ingress Replication</span>
1860
1861 This section applies only when Inclusive Tunnels are created via IR.
1862
1863 [<a id="ref-RFC6513">RFC6513</a>] and [<a href="./rfc6514" title="&quot;BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs&quot;">RFC6514</a>] specify procedures that allow I-PMSIs to be
1864 instantiated by IR. The concept of an IR P-tunnel, and the
1865 procedures for supporting IR P-tunnels, are explained more fully in
1866 [<a href="#ref-MVPN-IR" title="&quot;Ingress Replication Tunnels in Multicast VPN&quot;">MVPN-IR</a>]. An IR P-tunnel can be thought of as a P2MP tree in which
1867 a packet is transmitted from one node on the tree to another by being
1868 encapsulated and sent through a unicast tunnel.
1869
1870 As discussed in <a href="#section-2">Section 2</a>, when I-PMSIs are used to support
1871 extranets, egress PEs MUST have the ability to discard customer
1872 multicast data packets that arrive on the wrong P-tunnel. When
1873 I-PMSIs are instantiated by IR, this implies that the following two
1874 procedures MUST be followed:
1875
1876 1. One of the following three procedures MUST be followed:
1877
1878 a. the "Single Forwarder Selection" procedures of <a href="./rfc6513#section-9.1.2">Section&nbsp;9.1.2
1879 of [RFC6513]</a>
1880
1881 b. the "native PIM methods" of <a href="./rfc6513#section-9.1.3">Section&nbsp;9.1.3 of [RFC6513]</a>
1882
1883 c. the unicast encapsulation used to transmit packets along the
1884 IR P-tunnel is such as to enable the receiving node to
1885 identify the transmitting node (note that this would not be
1886 the case if, for example, the unicast tunnels were MP2P LSPs)
1887
1888 and
1889
1890 2. If a PE assigns an MPLS label value in the PTA of an Intra-AS or
1891 Inter-AS I-PMSI A-D route that it originates, that label value
1892 MUST NOT appear in the PTA of any other I-PMSI or S-PMSI A-D
1893 route originated by the same PE.
1894
1895
1896
1897
1898
1899
1900 <span class="grey">Rekhter, et al. Standards Track [Page 34]</span></pre>
1901 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-35" ></span>
1902 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
1903
1904
1905 Failure to follow these procedures would make it impossible to
1906 discard packets that arrive on the wrong P-tunnel and thus could lead
1907 to duplication of data.
1908
1909 If it is desired to support extranets while also using IR to
1910 instantiate the PMSIs, an alternative is to use (C-*,C-*) S-PMSIs
1911 instead of I-PMSIs. (See [<a href="./rfc6625" title="&quot;Wildcards in Multicast VPN Auto-Discovery Routes&quot;">RFC6625</a>], as well as Sections <a href="#section-7.2.2">7.2.2</a>,
1912 7.3.2, and 7.4.4 of this document.) This has much the same effect in
1913 the data plane, and there are no restrictions on the type of unicast
1914 tunnel that can be used for instantiating S-PMSIs.
1915
1916 <a href="./rfc6513#section-6.4.5">Section&nbsp;6.4.5 of [RFC6513]</a> describes a way to support VPNs using
1917 I-PMSIs that are instantiated by IR, using no S-PMSIs, but using
1918 "explicit tracking" to ensure that a C-flow goes only to egress PEs
1919 that have receivers for it. This document does not provide
1920 procedures to support extranets using that model.
1921
1922 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. When PIM Is the PE-PE C-Multicast Control Plane</span>
1923
1924 As specified in [<a href="./rfc6513" title="&quot;Multicast in MPLS/BGP IP VPNs&quot;">RFC6513</a>], when PIM is used as the PE-PE C-multicast
1925 control plane for a particular MVPN, there is a "Multidirectional
1926 Inclusive Provider Multicast Service Interface" (MI-PMSI) for that
1927 MVPN, and all the PEs of that MVPN must be able to send and receive
1928 on that MI-PMSI. Associated with each VRF of the MVPN is a PIM
1929 C-instance, and the PIM C-instance treats the MI-PMSI as if it were a
1930 LAN interface. That is, the "ordinary" PIM procedures run over the
1931 MI-PMSI just as they would over a real LAN interface, except that the
1932 data-plane and control-plane "Reverse Path Forwarding (RPF) checks"
1933 need to be modified. <a href="./rfc6513#section-5.2">Section&nbsp;5.2 of [RFC6513]</a> specifies the RPF
1934 check modifications for non-extranet MVPN service.
1935
1936 For example, suppose that there are two VPNs: VPN-S and VPN-R. In
1937 the absence of extranet support, all the VRFs of VPN-S are connected
1938 via one MI-PMSI (call it "the VPN-S MI-PMSI"), and all the VRFs of
1939 VPN-R are connected via another ("the VPN-R MI-PMSI"). If we want to
1940 provide extranet service in which the extranet C-sources are attached
1941 to some set of VPN-S VRFs while the extranet C-receivers are attached
1942 to some set of VPN-R VRFs, then we have two choices:
1943
1944 1. either the VPN-R VRFs need to join the VPN-S MI-PMSI, or
1945
1946 2. the VPN-S VRFs need to join the VPN-R MI-PMSI.
1947
1948 The first choice is used to support the "single PMSI per C-flow"
1949 transmission model. The second choice is used to support the
1950 "multiple PMSIs per C-flow" transmission model.
1951
1952
1953
1954
1955
1956 <span class="grey">Rekhter, et al. Standards Track [Page 35]</span></pre>
1957 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-36" ></span>
1958 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
1959
1960
1961 Procedures for both models are described below.
1962
1963 To support these models, it must be possible to determine which
1964 I-PMSI A-D routes are associated with the VPN-S I-PMSI and which
1965 I-PMSI A-D routes are associated with the VPN-R I-PMSI. Procedures
1966 are given for assigning RTs to these routes in a way that makes this
1967 determination possible.
1968
1969 Both models allow the use of S-PMSIs to carry multicast data traffic.
1970 If a VRF containing receivers can receive from multiple MI-PMSIs,
1971 each S-PMSI must be uniquely associated with a particular MI-PMSI.
1972 Procedures are given for assigning RTs to these routes in a way that
1973 makes this determination possible.
1974
1975 All the procedures specified in Sections <a href="#section-3">3</a>, <a href="#section-4">4</a>, and <a href="#section-5">5</a> still apply.
1976
1977 Note that there are no special extranet procedures for Inter-AS
1978 I-PMSI A-D routes or for Leaf A-D routes. Source Active A-D routes
1979 are not used when PIM is the PE-PE C-multicast protocol.
1980
1981 <span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Provisioning VRFs with RTs</span>
1982
1983 <span class="h4"><a class="selflink" id="section-6.1.1" href="#section-6.1.1">6.1.1</a>. Incoming and Outgoing Extranet RTs</span>
1984
1985 In the absence of extranet service, suppose that each VRF of a given
1986 VPN (call it "VPN-S") is configured with RT-S as its import and
1987 export RT, and that each VRF of a second VPN (call it "VPN-R") is
1988 configured with RT-R as its import and export RT. We will refer to
1989 RT-S and RT-R as "non-extranet RTs".
1990
1991 Now suppose that VPN-S contains some extranet C-sources and VPN-R
1992 contains some extranet C-receivers that are allowed by policy to
1993 receive extranet C-flows from the VPN-S extranet C-sources.
1994
1995 To set up this S-to-R extranet, provisioning an additional RT (call
1996 it "RT-S-to-R") whose value is, in general, distinct from RT-S and
1997 RT-R is REQUIRED.
1998
1999 A VPN-S VRF that contains extranet C-sources allowed to transmit to
2000 VPN-R MUST be configured with RT-S-to-R as an "Outgoing Extranet RT".
2001
2002 A VPN-R VRF that contains extranet C-receivers allowed to receive
2003 packets from VPN-S MUST be configured with RT-S-to-R as an "Incoming
2004 Extranet RT".
2005
2006 Note that the terms "Incoming" and "Outgoing" in this context refer
2007 to the direction of multicast data packets relative to the VRF.
2008
2009
2010
2011
2012 <span class="grey">Rekhter, et al. Standards Track [Page 36]</span></pre>
2013 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-37" ></span>
2014 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
2015
2016
2017 The Incoming Extranet RTs and Outgoing Extranet RTs that are
2018 configured for a given VRF serve as import RTs for that VRF. They
2019 also serve as export RTs, but only for specific routes as specified
2020 in <a href="#section-6.1.2">Section 6.1.2</a> below.
2021
2022 Note that any VRF that contains both extranet C-sources and extranet
2023 C-receivers MUST be configured with both Outgoing Extranet RTs and
2024 Incoming Extranet RTs.
2025
2026 A VRF MAY be configured with more than one Incoming Extranet RT
2027 and/or Outgoing Extranet RT.
2028
2029 If it happens to be the case that all C-sources in VPN-S are extranet
2030 C-sources allowed to transmit to VPN-R, then VPN-S VRFs MAY be
2031 configured such that RT-S is both a non-extranet RT and an Outgoing
2032 Extranet RT, and VPN-R VRFs MAY be configured such that RT-S is an
2033 Incoming Extranet RT.
2034
2035 <span class="h4"><a class="selflink" id="section-6.1.2" href="#section-6.1.2">6.1.2</a>. UMH-Eligible Routes and RTs</span>
2036
2037 Suppose that R1 is a route exported from a VPN-S VRF and matching an
2038 extranet C-source that is allowed by policy to transmit to VPN-R. In
2039 that case, R1 MUST carry the Outgoing Extranet RT used for the S-to-R
2040 extranet. This will cause the route to be imported into the VPN-R
2041 VRFs that have extranet C-receivers that are allowed by policy to
2042 receive from VPN-S.
2043
2044 The rules of <a href="#section-4">Section 4</a> regarding RTs and ambiguous addresses still
2045 apply.
2046
2047 <span class="h4"><a class="selflink" id="section-6.1.3" href="#section-6.1.3">6.1.3</a>. PIM C-Instance Reverse Path Forwarding Determination</span>
2048
2049 Suppose that a PIM control message (call it "M") is received by a
2050 given VRF (call it "VRF-V") from a particular P-tunnel T. In order
2051 to process control message M, the PIM C-instance associated with
2052 VRF-V may need to do an "RPF determination" (see <a href="./rfc6513#section-5.2.2">Section&nbsp;5.2.2 of
2053 [RFC6513]</a>) for a particular IP prefix S. RPF determination is based
2054 upon the rules for UMH selection as specified in <a href="./rfc6513#section-5.1">Section&nbsp;5.1 of
2055 [RFC6513]</a>.
2056
2057
2058
2059
2060
2061
2062
2063
2064
2065
2066
2067
2068 <span class="grey">Rekhter, et al. Standards Track [Page 37]</span></pre>
2069 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-38" ></span>
2070 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
2071
2072
2073 This document specifies an additional constraint on the UMH selection
2074 procedure. When doing RPF determination for a PIM control message
2075 received over a P-tunnel, a route matching prefix S is not considered
2076 to be eligible for UMH selection unless there is an RT (call it
2077 "RT1"), configured as one of VRF-V's Outgoing Extranet RTs, such that
2078 the following two conditions both hold:
2079
2080 1. The route matching S is exported from VRF-V carrying RT1, and
2081
2082 2. An I-PMSI A-D route advertising P-tunnel T (in its PTA) has been
2083 imported into VRF-V, and that I-PMSI A-D route carries RT1.
2084
2085 <span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. "Single PMSI per C-Flow" Model</span>
2086
2087 In this model, if a VPN-S VRF has extranet multicast C-sources and a
2088 VPN-R VRF has extranet multicast C-receivers allowed by policy to
2089 receive from the C-sources in the VPN-S VRF, then the VPN-R VRF joins
2090 the MI-PMSI that VPN-S uses for its non-extranet traffic.
2091
2092 <span class="h4"><a class="selflink" id="section-6.2.1" href="#section-6.2.1">6.2.1</a>. Forming the MI-PMSIs</span>
2093
2094 Consider a VPN-S VRF that has extranet C-sources. Per [<a href="./rfc6513" title="&quot;Multicast in MPLS/BGP IP VPNs&quot;">RFC6513</a>],
2095 each VPN-S VRF must originate an Intra-AS I-PMSI A-D route containing
2096 a PTA specifying the P-tunnel to be used as part of the VPN-S
2097 MI-PMSI. In the absence of extranet service, this route carries the
2098 VRF's non-extranet RT, RT-S. When extranet service is provided
2099 (using the "single PMSI per C-flow" model), this route MUST also
2100 carry each of the VRF's Outgoing Extranet RTs.
2101
2102 Consider a VPN-R VRF that has extranet C-receivers. Per [<a href="./rfc6513" title="&quot;Multicast in MPLS/BGP IP VPNs&quot;">RFC6513</a>],
2103 each VPN-R VRF must originate an Intra-AS I-PMSI A-D route containing
2104 a PTA specifying the P-tunnel to be used as part of the VPN-R
2105 MI-PMSI. This route carries the VRF's non-extranet RT, RT-R. When
2106 extranet service is provided (using the "single PMSI per C-flow"
2107 model), the VPN-R VRF MUST also originate one or more additional
2108 Intra-AS I-PMSI A-D routes. It MUST originate one additional
2109 Intra-AS I-PMSI A-D route for each Incoming Extranet RT with which it
2110 has been configured; each such route will carry exactly one of the
2111 configured Incoming Extranet RTs.
2112
2113 Note that when a VRF originates more than one Intra-AS I-PMSI A-D
2114 route, each of them MUST contain a different RD in its NLRI. In
2115 addition, we add the requirement that any pair of such routes
2116 MUST NOT contain an RT in common.
2117
2118
2119
2120
2121
2122
2123
2124 <span class="grey">Rekhter, et al. Standards Track [Page 38]</span></pre>
2125 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-39" ></span>
2126 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
2127
2128
2129 A VRF with extranet C-sources MUST join the P-tunnels advertised in
2130 the imported I-PMSI A-D routes that carry its non-extranet RT or any
2131 of its Outgoing Extranet RTs. This set of P-tunnels will be treated
2132 as instantiating a single MI-PMSI; the associated PIM C-instance will
2133 treat that MI-PMSI as a single LAN and will run PIM procedures on
2134 that LAN, as specified in [<a href="./rfc6513" title="&quot;Multicast in MPLS/BGP IP VPNs&quot;">RFC6513</a>]. The fact that the MI-PMSI
2135 attaches to VRFs of different VPNs is not known to the PIM C-instance
2136 of the VRF containing the sources.
2137
2138 A VRF with extranet C-receivers MUST join the P-tunnels advertised in
2139 all the imported I-PMSI A-D routes. The set of P-tunnels advertised
2140 in the I-PMSI A-D routes that carry a particular Incoming Extranet RT
2141 are treated as instantiating a particular MI-PMSI. So, a VRF with
2142 C-receivers will "see" several MI-PMSIs, one corresponding to the
2143 non-extranet, and as many as one for each configured Incoming
2144 Extranet RT. The PIM C-instance associated with the VRF will treat
2145 each of these MI-PMSIs as a separate LAN interface.
2146
2147 As an example, suppose that:
2148
2149 o All VPN-R VRFs are configured with RT-R as a non-extranet import
2150 and export RT, and
2151
2152 o VPN-R VRFs with extranet receivers are configured with RT-S-to-R
2153 as an Incoming Extranet RT, and
2154
2155 o VPN-S VRFs with extranet transmitters are configured with:
2156
2157 * RT-S as a non-extranet import and export RT
2158
2159 * a list of IP addresses that are the addresses of the extranet
2160 sources
2161
2162 * RT-S-to-R as an Outgoing Extranet RT
2163
2164 VPN-S VRFs will then export UMH-eligible routes matching extranet
2165 C-sources, and these routes will carry both RT-S and RT-S-to-R. Each
2166 VPN-S VRF will also export an Intra-AS I-PMSI A-D route that carries
2167 both RT-S and RT-S-to-R.
2168
2169 VPN-R VRFs will originate and export two Intra-AS I-PMSI A-D routes:
2170 one carrying RT-R and one carrying RT-S-to-R. The Intra-AS I-PMSI
2171 A-D route with RT-S-to-R will be imported into the VPN-S VRFs.
2172
2173 VPN-R will regard all the I-PMSI A-D routes it has exported or
2174 imported with RT-S-to-R as part of a single MI-PMSI. VPN-R will
2175 regard all the I-PMSI A-D routes it has exported or imported with
2176 RT-R as part of a second MI-PMSI. The PIM C-instance associated with
2177
2178
2179
2180 <span class="grey">Rekhter, et al. Standards Track [Page 39]</span></pre>
2181 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-40" ></span>
2182 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
2183
2184
2185 a VPN-R VRF will treat the two MI-PMSIs as two separate LAN
2186 interfaces. However, the VPN-S VRFs will regard all the I-PMSI A-D
2187 routes imported with RT-S or RT-S-to-R as establishing only a single
2188 MI-PMSI. One can think of this as follows: the VPN-R VRFs have
2189 joined the VPN-S MI-PMSI as well as the VPN-R MI-PMSI.
2190
2191 Extranets consisting of more than two VPNs are easily supported as
2192 follows. Suppose that there are three VPNs: VPN-A, VPN-B, and VPN-C.
2193 VPN-A and VPN-B have extranet C-sources, and VPN-C contains receivers
2194 for both VPN-A extranet C-sources and VPN-B extranet C-sources. In
2195 this case, the VPN-C VRFs that have receivers for both VPN-A and
2196 VPN-B sources may be provisioned as follows. These VPN-C VRFs may be
2197 provisioned with RT-C as a non-extranet RT, and with RT-A-to-C and
2198 RT-B-to-C as Incoming Extranet RTs. In this case, the VPN-C VRFs
2199 that are so provisioned will originate three Intra-AS I-PMSI A-D
2200 routes (each with a different RD in its NLRI), each of which carries
2201 exactly one of the three RTs just mentioned. The VPN-B VRFs with
2202 extranet C-sources will be provisioned with RT-B-to-C as an Outgoing
2203 Extranet RT, and the VPN-A VRFs will be provisioned with RT-A-to-C as
2204 an Outgoing Extranet RT. The result will be that the PIM C-instance
2205 associated with a VPN-C VRF will see three LAN interfaces: one for
2206 the non-extranet and one for each of the two extranets. This
2207 generalizes easily to the case where there are VPN-C receivers in
2208 n different extranets (i.e., receiving extranet flows whose sources
2209 are in n different VPNs).
2210
2211 Suppose again that there are three VPNs -- VPN-A, VPN-B, and VPN-C --
2212 but in this example VPN-A is the only one with extranet sources while
2213 VPN-B and VPN-C both have receivers for the VPN-A extranet sources.
2214 This can be provisioned as either one extranet or two extranets.
2215
2216 To provision it as one extranet, the VPN-A VRFs are configured with
2217 one Outgoing Extranet RT (call it "RT-A-extranet"). The VPN-B and
2218 VPN-C VRFs with extranet receivers will be provisioned with
2219 RT-A-extranet as the Incoming Extranet RT. Thus, the VPN-B and VPN-C
2220 VRFs will each originate two Intra-AS I-PMSI A-D routes: one for the
2221 non-extranet and one for the extranet. From a given VRF, the
2222 Intra-AS I-PMSI A-D route for the extranet will carry RT-A-extranet
2223 but will not share any RT with the non-extranet A-D routes exported
2224 from the same VRF.
2225
2226 The result is that the VPN-B and VPN-C VRFs each belong to two
2227 MI-PMSIs: one for the extranet and one for the intranet. The MI-PMSI
2228 for the extranet attaches VPN-A VRFs, VPN-B VRFs, and VPN-C VRFs.
2229
2230
2231
2232
2233
2234
2235
2236 <span class="grey">Rekhter, et al. Standards Track [Page 40]</span></pre>
2237 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-41" ></span>
2238 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
2239
2240
2241 Alternatively, one could provision the VPN-A VRFs so that some
2242 UMH-eligible extranet source routes carry an RT that we will call
2243 "RT-A-to-B" and some carry an RT that we will call "RT-A-to-C". The
2244 VPN-A VRFs would be configured with both of these as Outgoing
2245 Extranet RTs. To allow an extranet flow from a VPN-A source to have
2246 both VPN-B and VPN-C receivers, the UMH-eligible route for that
2247 source would carry both RTs. VPN-B VRFs (but not VPN-C VRFs) would
2248 be provisioned with RT-A-to-B as an Incoming Extranet RT. VPN-C VRFs
2249 (but not VPN-B VRFs) would be provisioned with RT-A-to-C as an
2250 Incoming Extranet RT.
2251
2252 Following the rules above, if any VPN-A extranet source is to have
2253 both VPN-B and VPN-C receivers, the VPN-B and VPN-C VRFs will each
2254 originate two I-PMSI A-D routes: one for the extranet and one for the
2255 non-extranet. The single Intra-AS I-PMSI A-D route originated by the
2256 VPN-A VRFs will have both RT-A-to-B and RT-A-to-C among its RTs (as
2257 well as VPN-A's non-extranet RT). The extranet I-PMSI A-D route
2258 originated from a VPN-B VRF would have RT-A-to-B, and the extranet
2259 I-PMSI A-D route originated from a VPN-C VRF would have RT-A-to-C.
2260
2261 If a given VRF contains both extranet C-receivers and extranet
2262 C-sources, the procedures described above still work, as the VRF will
2263 be configured with both Incoming Extranet RTs and Outgoing Extranet
2264 RTs; the VRF functions as both a VPN-S VRF and a VPN-R VRF.
2265
2266 <span class="h4"><a class="selflink" id="section-6.2.2" href="#section-6.2.2">6.2.2</a>. S-PMSIs</span>
2267
2268 When PIM is used as the PE-PE C-multicast control plane, every S-PMSI
2269 is considered to be part of the "emulated LAN" that "corresponds" to
2270 a particular MI-PMSI.
2271
2272 When the bindings of C-flows to particular S-PMSIs are announced via
2273 S-PMSI Join messages (<a href="./rfc6513#section-7">Section&nbsp;7 of [RFC6513]</a>) sent on the MI-PMSI,
2274 the S-PMSI is considered to be part of the same LAN interface as the
2275 corresponding MI-PMSI.
2276
2277 When the bindings of C-flows to particular S-PMSIs are announced via
2278 S-PMSI A-D routes, any S-PMSI A-D route exported from that VRF MUST
2279 have an RT in common with exactly one of the Intra-AS A-D routes
2280 exported from that VRF, and this MUST be one of the VRF's Outgoing
2281 Extranet RTs. Further, the S-PMSI A-D route MUST NOT have an RT in
2282 common with any other Intra-AS A-D route exported from a VRF on the
2283 same PE. A given S-PMSI A-D route will be considered to "correspond"
2284 to the MI-PMSI of the Intra-AS I-PMSI A-D route (originated from the
2285 same PE) with which it shares an RT.
2286
2287
2288
2289
2290
2291
2292 <span class="grey">Rekhter, et al. Standards Track [Page 41]</span></pre>
2293 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-42" ></span>
2294 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
2295
2296
2297 The MI-PMSI that corresponds to a given S-PMSI is determined as
2298 follows:
2299
2300 o If (1) there is an Intra-AS I-PMSI A-D route originated by the
2301 same PE that originated the S-PMSI A-D route, (2) those two routes
2302 have an RT in common, and (3) that RT is one of the VRF's Incoming
2303 Extranet RTs, then the S-PMSI corresponds to the I-PMSI associated
2304 with that Intra-AS I-PMSI A-D route.
2305
2306 o Otherwise, if (1) there is an Inter-AS I-PMSI A-D route originated
2307 in the same AS as the S-PMSI A-D route, (2) those two routes have
2308 an RT in common, and (3) that RT is one of the VRF's Incoming
2309 Extranet RTs, then the S-PMSI corresponds to the I-PMSI associated
2310 with that Inter-AS I-PMSI A-D route.
2311
2312 o Otherwise, there must be a configuration error (a violation of the
2313 requirements of Sections <a href="#section-3">3</a>, <a href="#section-4">4</a>, and <a href="#section-5">5</a> of this document).
2314
2315 When wildcard S-PMSIs are used, the rules given in [<a href="./rfc6625" title="&quot;Wildcards in Multicast VPN Auto-Discovery Routes&quot;">RFC6625</a>] for
2316 determining whether a given S-PMSI A-D route is a "match for
2317 reception" to a given (C-S,C-G) or (C-*,C-G) are modified as follows:
2318
2319 A given S-PMSI A-D route MUST NOT be considered to be a "match for
2320 reception" for a given (C-S,C-G) or (C-*,C-G) state UNLESS that
2321 S-PMSI A-D route "corresponds" (as defined above) to the MI-PMSI
2322 that is the incoming interface for the given state.
2323
2324 The rules given in [<a href="./rfc6625" title="&quot;Wildcards in Multicast VPN Auto-Discovery Routes&quot;">RFC6625</a>] for determining whether a given S-PMSI
2325 A-D route is a "match for transmission" are unchanged.
2326
2327 <span class="h4"><a class="selflink" id="section-6.2.3" href="#section-6.2.3">6.2.3</a>. Sending PIM Control Packets</span>
2328
2329 Suppose that a PE, say PE1, receives a PIM Join(S,G) from a CE, over
2330 a VRF interface that is associated with a VPN-R VRF. The PE does the
2331 RPF check for S by looking up S in the VPN-R VRF. The PIM C-instance
2332 associated with that VRF must determine the correct P-tunnel over
2333 which to send a PIM Join(S,G) to other PEs.
2334
2335 To do this, PE1 finds, in the VRF associated with the interface over
2336 which the Join was received, the selected UMH route for S, following
2337 the procedures of <a href="./rfc6513#section-5.1">Section&nbsp;5.1 of [RFC6513]</a>. PE1 determines the set
2338 of RTs carried by that route. PE1 then checks to see if there is an
2339 Intra-AS I-PMSI A-D route, currently originated by PE1, that has an
2340 RT in common with the selected UMH route for S.
2341
2342
2343
2344
2345
2346
2347
2348 <span class="grey">Rekhter, et al. Standards Track [Page 42]</span></pre>
2349 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-43" ></span>
2350 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
2351
2352
2353 If the rules of Sections <a href="#section-3">3</a>, <a href="#section-4">4</a>, and <a href="#section-5">5</a> have been followed, each of
2354 PE1's selected UMH routes will share an RT with a single one of PE1's
2355 currently originated Intra-AS I-PMSI A-D routes. If this is so, the
2356 Join is sent on the P-tunnel advertised in the PTA of that route.
2357 Otherwise, the Join MUST NOT be sent.
2358
2359 In essence, this procedure makes the RPF check for C-S resolve to the
2360 MI-PMSI that is serving as the next-hop "interface" to C-S.
2361
2362 If a PE receives a PIM Join(*,G) from a CE, the procedure for doing
2363 the RPF check is the same, except that the selected UMH route will be
2364 a route to the C-RP associated with the C-G group.
2365
2366 <span class="h4"><a class="selflink" id="section-6.2.4" href="#section-6.2.4">6.2.4</a>. Receiving PIM Control Packets</span>
2367
2368 When a PIM C-instance receives a PIM control message from a P-tunnel,
2369 it needs to identify the message's incoming interface. This incoming
2370 interface is the MI-PMSI of which the P-tunnel is a part.
2371
2372 <span class="h4"><a class="selflink" id="section-6.2.5" href="#section-6.2.5">6.2.5</a>. Sending and Receiving Data Packets</span>
2373
2374 The rules for choosing the PMSI on which to send a multicast data
2375 packet are as specified in [<a href="./rfc6513" title="&quot;Multicast in MPLS/BGP IP VPNs&quot;">RFC6513</a>] and [<a href="./rfc6625" title="&quot;Wildcards in Multicast VPN Auto-Discovery Routes&quot;">RFC6625</a>], with one new
2376 restriction: a VPN-S VRF always transmits a multicast data packet
2377 either on the VPN-S MI-PMSI or on an S-PMSI that corresponds to the
2378 VPN-S MI-PMSI. From the perspective of the PIM C-instance, there is
2379 only one outgoing interface.
2380
2381 When a PIM C-instance receives a multicast data packet from a given
2382 P-tunnel and that P-tunnel is being used to instantiate an MI-PMSI,
2383 the MI-PMSI of which the P-tunnel is a part (see Sections <a href="#section-6.2.1">6.2.1</a> and
2384 6.2.2) is considered to be the packet's incoming interface. If the
2385 packet is received on a P-tunnel that was advertised in an S-PMSI A-D
2386 route, the packet's incoming interface is the MI-PMSI to which that
2387 S-PMSI route corresponds, as defined in <a href="#section-6.2.2">Section 6.2.2</a>. Ordinary PIM
2388 rules for data-plane RPF checks apply.
2389
2390 Following ordinary PIM procedures, packets arriving from an
2391 unexpected incoming interface are discarded. This eliminates any
2392 problems due to the ambiguities described in Sections <a href="#section-2.1">2.1</a> and <a href="#section-2.2">2.2</a>.
2393
2394 <span class="h3"><a class="selflink" id="section-6.3" href="#section-6.3">6.3</a>. "Multiple PMSIs per C-Flow" Model</span>
2395
2396 In this model, if a VPN-S VRF has extranet multicast C-sources and a
2397 VPN-R VRF has extranet multicast C-receivers allowed by policy to
2398 receive from the C-sources in the VPN-S VRF, then the VPN-S VRF joins
2399 the MI-PMSI that VPN-R uses for its non-extranet traffic.
2400
2401
2402
2403
2404 <span class="grey">Rekhter, et al. Standards Track [Page 43]</span></pre>
2405 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-44" ></span>
2406 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
2407
2408
2409 In the "single PMSI per C-flow" transmission model (as described in
2410 <a href="#section-6.2">Section 6.2</a>), a PE that needs to transmit a multicast data packet to
2411 a set of other PEs transmits the packet on a single PMSI. This means
2412 that if a packet needs to be transmitted from a VPN-A VRF and
2413 received at a VPN-B VRF and a VPN-C VRF, there must be some P-tunnel
2414 from which the VPN-B and VPN-C VRFs can both receive packets.
2415
2416 In the "multiple PMSIs per C-flow" transmission model, a PE that
2417 needs to transmit a multicast data packet to a set of other PEs may
2418 transmit the packet on several different PMSIs. (Of course, any
2419 given packet is transmitted only once on a given P-tunnel.) For
2420 example, if a C-flow (C-S,C-G) has a VPN-A C-source, a VPN-B
2421 receiver, and a VPN-C receiver, there could be one PMSI that the
2422 VPN-A VRF uses to transmit the packet to the VPN-B VRFs and
2423 another PMSI that the VPN-A VRF uses to transmit the packet to the
2424 VPN-C VRFs.
2425
2426 <span class="h4"><a class="selflink" id="section-6.3.1" href="#section-6.3.1">6.3.1</a>. Forming the MI-PMSIs</span>
2427
2428 Consider a VPN-R VRF that has extranet C-receivers. Per [<a href="./rfc6513" title="&quot;Multicast in MPLS/BGP IP VPNs&quot;">RFC6513</a>],
2429 each VPN-R VRF must originate an Intra-AS I-PMSI A-D route containing
2430 a PTA specifying the P-tunnel to be used as part of the VPN-R
2431 MI-PMSI. In the absence of extranet service, this route carries the
2432 VRF's non-extranet RT, RT-R. When extranet service is provided
2433 (using the "single PMSI per C-flow" model), this route MUST also
2434 carry each of the VRF's Incoming Extranet RTs.
2435
2436 Consider a VPN-S VRF that has extranet C-sources. Per [<a href="./rfc6513" title="&quot;Multicast in MPLS/BGP IP VPNs&quot;">RFC6513</a>],
2437 each VPN-S VRF must originate an Intra-AS I-PMSI A-D route containing
2438 a PTA specifying the P-tunnel to be used as part of the VPN-S
2439 MI-PMSI. This route carries the VRF's non-extranet RT, RT-S. When
2440 extranet service is provided using the "multiple PMSIs per C-flow"
2441 model, the VPN-S VRF MUST also originate one or more additional
2442 Intra-AS I-PMSI A-D routes. It MUST originate one additional
2443 Intra-AS I-PMSI A-D route for each Outgoing Extranet RT with which it
2444 has been configured; each such route will have a distinct RD and will
2445 carry exactly one of the configured Outgoing Extranet RTs.
2446
2447 As with the "single PMSI per C-flow" transmission model, VRFs
2448 containing extranet C-receivers need to import UMH-eligible extranet
2449 C-source routes from VRFs containing C-sources. This is ensured by
2450 the rules of Sections <a href="#section-3">3</a>, <a href="#section-4">4</a>, and <a href="#section-5">5</a>.
2451
2452 However, in the "multiple PMSIs per C-flow" model, a VRF containing
2453 only C-receivers originates only a single Intra-AS I-PMSI A-D route
2454 carrying the non-extranet RT and all the Incoming Extranet RTs.
2455
2456
2457
2458
2459
2460 <span class="grey">Rekhter, et al. Standards Track [Page 44]</span></pre>
2461 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-45" ></span>
2462 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
2463
2464
2465 When a VRF containing C-receivers imports Intra-AS I-PMSI A-D routes
2466 that carry the non-extranet RT or one of the Incoming Extranet RTs,
2467 the P-tunnels specified in the PTA of all such routes are considered
2468 to be part of the same MI-PMSI. That is, the associated PIM
2469 C-instance will treat them as part of a single interface.
2470
2471 In this model, it is the VRF containing extranet C-sources that MUST
2472 originate multiple Intra-AS I-PMSI A-D routes. Each such route MUST
2473 have a distinct RD, and the set of RTs carried by any one of these
2474 routes MUST be disjoint from the set carried by any other. There
2475 MUST be one such route for each of the VRF's Outgoing Extranet RTs,
2476 and each such route MUST carry exactly one of the VRF's Outgoing
2477 Extranet RTs. The VRFs containing extranet C-sources MUST also
2478 import all the A-D routes originated by the VRFs containing extranet
2479 C-receivers. If a set of originated and/or imported Intra-AS I-PMSI
2480 A-D routes have an RT in common and that RT is one of the VRF's
2481 Outgoing Export RTs, then those routes are considered to be "about"
2482 the same MI-PMSI. The PIM C-instance of the VRF treats each MI-PMSI
2483 as a LAN interface.
2484
2485 In effect, if VPN-S has only extranet C-sources and VPN-R has only
2486 extranet C-receivers, this model has the VPN-S VRFs join the VPN-R
2487 MI-PMSI. The VPN-S VRFs will thus be attached to multiple MI-PMSIs,
2488 while the VPN-R VRFs are attached to only one. The fact that the
2489 VPN-R MI-PMSI is attached to VPN-S VRFs is not known to the PIM
2490 C-instance at the VPN-R VRFs.
2491
2492 If a VPN-A VRF has extranet C-sources allowed to send to C-receivers
2493 in a VPN-B VRF and the VPN-B VRF has C-sources allowed to send to
2494 C-receivers in the VPN-A VRF, the above procedures still work as
2495 specified.
2496
2497 Following normal PIM procedures, when the PIM C-instance at a VRF
2498 with extranet C-sources receives a Join(C-S,C-G) or a Join(C-*,C-G)
2499 over an MI-PMSI, it may create (C-S,C-G) or (C-*,C-G) state, and the
2500 MI-PMSI over which the Join was received may be added to the set of
2501 outgoing interfaces for that multicast state. If n MI-PMSIs are
2502 added to the outgoing interface list for a particular multicast
2503 state, a multicast data packet may need to be replicated n times and
2504 transmitted once on each of the n MI-PMSIs.
2505
2506 Since all of the multicast data packets received from another PE are
2507 received over a single emulated LAN, it is not necessary to have any
2508 special procedures to determine a packet's incoming interface. The
2509 ambiguities described in Sections <a href="#section-2.1">2.1</a> and <a href="#section-2.2">2.2</a> do not occur, because a
2510 VPN-R VRF can only receive multicast data traffic that has been
2511 requested by a VPN-R VRF.
2512
2513
2514
2515
2516 <span class="grey">Rekhter, et al. Standards Track [Page 45]</span></pre>
2517 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-46" ></span>
2518 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
2519
2520
2521 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. When BGP Is the PE-PE C-Multicast Control Plane</span>
2522
2523 This document assumes that if BGP is used as the PE-PE C-multicast
2524 control plane, the "single PMSI per C-flow" model is used.
2525 Procedures for providing the "multiple PMSIs per C-flow" model with
2526 BGP C-multicast are outside the scope of this document.
2527
2528 When BGP is used as the C-multicast control plane, the "single PMSI
2529 per C-flow" model may be used either with or without extranet
2530 separation. (Recall that "extranet separation" means that no
2531 P-tunnel can carry traffic from both extranet sources and
2532 non-extranet sources.) In either case, the data traffic may be
2533 carried on Inclusive Tunnels only, Selective Tunnels only (known as
2534 the "S-PMSI only" model), or a combination of Inclusive Tunnels and
2535 Selective Tunnels. This is determined by provisioning. The
2536 procedures specified below support all three choices.
2537
2538 Note that there are no special extranet procedures for Inter-AS
2539 I-PMSI A-D routes or for Leaf A-D routes.
2540
2541 <span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. Originating C-Multicast Routes</span>
2542
2543 This section applies whether extranet separation is used or not.
2544
2545 When it is necessary to originate a C-multicast Source Tree Join for
2546 (C-S,C-G), a PE must follow the procedures of <a href="#section-11.1.3">Section 11.1.3</a>
2547 ("Constructing the Rest of the C-Multicast Route") of [<a href="./rfc6514" title="&quot;BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs&quot;">RFC6514</a>] to
2548 find the selected UMH route for C-S. When it is necessary to
2549 originate a C-multicast Shared Tree Join for (C-*,C-G), where C-G is
2550 an ASM group, a PE must follow the procedures of that section to find
2551 the selected UMH route for C-G's C-RP.
2552
2553 <a href="./rfc6514#section-11.1.3">Section&nbsp;11.1.3 of [RFC6514]</a> specifies how information from the
2554 selected UMH route is used to find an Intra-AS I-PMSI A-D route or an
2555 Inter-AS I-PMSI A-D route. Information from that I-PMSI A-D route is
2556 then used to construct part of the C-multicast route.
2557
2558 For extranets, the rules given in <a href="#section-7.4.5">Section 7.4.5</a> of this document are
2559 used to find the Inter-AS I-PMSI A-D route or an Intra-AS I-PMSI A-D
2560 route that "corresponds" to the selected UMH route; the rules in
2561 <a href="#section-7.4.5">Section 7.4.5</a> replace the rules given in <a href="./rfc6514#section-11.1.3">Section&nbsp;11.1.3 of [RFC6514]</a>
2562 for finding the Inter-AS or Intra-AS I-PMSI A-D route.
2563
2564 Information from this I-PMSI A-D route is then used, as specified in
2565 <a href="./rfc6514#section-11.1.3">Section&nbsp;11.1.3 of [RFC6514]</a>, to construct the C-multicast route.
2566
2567
2568
2569
2570
2571
2572 <span class="grey">Rekhter, et al. Standards Track [Page 46]</span></pre>
2573 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-47" ></span>
2574 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
2575
2576
2577 <span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. Originating A-D Routes without Extranet Separation</span>
2578
2579 <span class="h4"><a class="selflink" id="section-7.2.1" href="#section-7.2.1">7.2.1</a>. Intra-AS I-PMSI A-D Routes</span>
2580
2581 Consider a VRF (call it "VRF-S") that contains extranet C-sources and
2582 exports UMH-eligible routes matching those C-sources. The VRF may
2583 also originate and export an Intra-AS I-PMSI A-D route.
2584
2585 As specified in [<a href="./rfc6514" title="&quot;BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs&quot;">RFC6514</a>], if exactly one Intra-AS I-PMSI A-D route
2586 is originated by and exported from VRF-S, the RTs carried by that
2587 route MUST be chosen such that every VRF that imports a UMH-eligible
2588 route from VRF-S also imports this Intra-AS I-PMSI A-D route.
2589
2590 If inclusive P-tunnels are being used to carry extranet C-flows,
2591 there are additional requirements on the way the RTs carried by the
2592 Intra-AS I-PMSI A-D routes must be chosen, as specified in the
2593 following paragraph.
2594
2595 If VRF-S is using inclusive P-tunnels but is not using extranet
2596 separation, there is one inclusive P-tunnel rooted at VRF-S, and this
2597 tunnel carries both extranet and non-extranet C-flows. This
2598 Inclusive Tunnel is identified in the PTA of the Intra-AS I-PMSI A-D
2599 route originated from VRF-S. The set of RTs carried by this Intra-AS
2600 I-PMSI A-D route MUST be chosen so as to ensure that every VRF that
2601 imports a UMH-eligible route from this VRF-S also imports this
2602 Intra-AS I-PMSI A-D route. Further, the set of RTs carried by this
2603 Intra-AS I-PMSI A-D route MUST be chosen such that it has at least
2604 one RT in common with every UMH-eligible route that is exported from
2605 the VRF.
2606
2607 <span class="h4"><a class="selflink" id="section-7.2.2" href="#section-7.2.2">7.2.2</a>. S-PMSI A-D Routes</span>
2608
2609 Let R-SP be an S-PMSI A-D route that is exported from VRF-S. Suppose
2610 that R-SP is used to bind some or all of the extranet C-flows from a
2611 given extranet C-source to a given selective P-tunnel. Let R-UMH be
2612 a UMH-eligible route that is exported from VRF-S and matches the
2613 given extranet C-source. In that case, R-SP and R-UMH MUST have at
2614 least one RT in common. Further, the RTs carried by these two routes
2615 MUST be such that every VRF that imports R-UMH also imports R-SP.
2616 These rules apply whether or not R-SP uses wildcards [<a href="./rfc6625" title="&quot;Wildcards in Multicast VPN Auto-Discovery Routes&quot;">RFC6625</a>].
2617
2618
2619
2620
2621
2622
2623
2624
2625
2626
2627
2628 <span class="grey">Rekhter, et al. Standards Track [Page 47]</span></pre>
2629 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-48" ></span>
2630 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
2631
2632
2633 An implementation MUST allow the set of RTs carried by the S-PMSI A-D
2634 routes to be specified by configuration. In the absence of such
2635 configuration, an S-PMSI A-D route originated by a given VRF, say
2636 VRF-X, MUST carry a default set of RTs, as specified by the following
2637 rules:
2638
2639 1. By default, an S-PMSI A-D route originated by VRF-X for a given
2640 (C-S,C-G) or (C-S,C-*) carries the same RT(s) as the UMH-eligible
2641 route originated by VRF-X that matches C-S.
2642
2643 2. By default, an S-PMSI A-D route originated by VRF-X for a given
2644 (C-*,C-G) carries as its RTs a set union of all RT(s) of the
2645 UMH-eligible route(s) matching the multicast C-sources contained
2646 in VRF-X that could originate traffic for that C-G. Moreover, if
2647 the VRF contains (as defined in <a href="#section-1.1">Section 1.1</a>) the C-RP of C-G,
2648 then this set union also includes the RT(s) of the UMH-eligible
2649 route matching C-RP and the RT(s) of the unicast VPN-IP route
2650 matching C-RP.
2651
2652 3. By default, if a (C-*,C-*) S-PMSI A-D route originated by VRF-X
2653 is to be used for both extranet and non-extranet traffic, it
2654 carries the same RTs that would be carried (as specified in
2655 <a href="#section-7.2.1">Section 7.2.1</a>) by an I-PMSI A-D route originated by VRF-X if that
2656 I-PMSI A-D route were advertising an inclusive P-tunnel for
2657 carrying both extranet and non-extranet traffic. In general, a
2658 given VRF would not originate both (a) an S-PMSI A-D route
2659 advertising a (C-*,C-*) selective P-tunnel for both extranet and
2660 non-extranet traffic and (b) an I-PMSI A-D route advertising an
2661 inclusive P-tunnel for both extranet and non-extranet traffic, as
2662 the inclusive P-tunnel would not get used in that case.
2663
2664 <span class="h4"><a class="selflink" id="section-7.2.3" href="#section-7.2.3">7.2.3</a>. Source Active A-D Routes</span>
2665
2666 <span class="h5"><a class="selflink" id="section-7.2.3.1" href="#section-7.2.3.1">7.2.3.1</a>. When Inter-Site Shared Trees Are Used</span>
2667
2668 This section applies when inter-site shared trees are used, as
2669 specified in <a href="./rfc6514#section-13">Section&nbsp;13 of [RFC6514]</a>.
2670
2671 If VRF-S exports a Source Active A-D route that contains C-S in the
2672 Multicast Source field of its NLRI and VRF-S also exports a
2673 UMH-eligible route matching C-S, the Source Active A-D route MUST
2674 carry at least one RT in common with the UMH-eligible route. The RT
2675 MUST be chosen such that the following condition holds: if a VRF, say
2676 VRF-R, contains an extranet C-receiver allowed by policy to receive
2677 extranet traffic from C-S, then VRF-R imports both the UMH-eligible
2678 route and the Source Active A-D route.
2679
2680
2681
2682
2683
2684 <span class="grey">Rekhter, et al. Standards Track [Page 48]</span></pre>
2685 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-49" ></span>
2686 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
2687
2688
2689 By default, a Source Active A-D route for a given (C-S,C-G), exported
2690 by a given VRF, carries the same set of RTs as the UMH-eligible route
2691 matching C-S that is exported from that VRF.
2692
2693 <span class="h5"><a class="selflink" id="section-7.2.3.2" href="#section-7.2.3.2">7.2.3.2</a>. When Inter-Site Shared Trees Are Not Used</span>
2694
2695 This section applies when inter-site shared trees are not used, as
2696 specified in <a href="./rfc6514#section-14">Section&nbsp;14 of [RFC6514]</a>.
2697
2698 Suppose that a VRF, say VRF-X, contains the C-RP for a given extranet
2699 C-group, say C-G. If C-S is an active source for C-G, then,
2700 following the procedures of <a href="./rfc6514#section-14.1">Section&nbsp;14.1 of [RFC6514]</a>, VRF-X may
2701 export a Source Active A-D route that contains C-S in the Multicast
2702 Source field of its NLRI. With the following text, this document
2703 replaces the rule specified in <a href="./rfc6514#section-14.1">Section&nbsp;14.1 of [RFC6514]</a> for
2704 constructing the RT(s) carried by such a route: VRF-X MUST be
2705 configured such that the Source Active A-D route for (C-S,C-G)
2706 carries the same set of RTs as the UMH-eligible route matching C-S
2707 that is exported from the VRF(s) containing C-S. This way, if a VRF,
2708 say VRF-R, contains an extranet C-receiver allowed by policy to
2709 receive extranet traffic from C-S, then VRF-R imports both the
2710 UMH-eligible route and the Source Active A-D route.
2711
2712 <span class="h3"><a class="selflink" id="section-7.3" href="#section-7.3">7.3</a>. Originating A-D Routes with Extranet Separation</span>
2713
2714 If a VRF contains both extranet C-sources and non-extranet C-sources,
2715 it MUST be configured with both a default RD and an extranet RD (see
2716 <a href="#section-1.3">Section 1.3</a>). The use of these RDs is explained in the following
2717 subsections.
2718
2719 <span class="h4"><a class="selflink" id="section-7.3.1" href="#section-7.3.1">7.3.1</a>. Intra-AS I-PMSI A-D Routes</span>
2720
2721 This section applies when VRF-S is using extranet separation AND when
2722 VRF-S is using an inclusive P-tunnel to carry some or all of the
2723 extranet C-flows that it needs to transmit to other VRFs.
2724
2725 If VRF-S contains both extranet C-sources and non-extranet C-sources,
2726 and inclusive P-tunnels are used to carry both extranet C-flows and
2727 non-extranet C-flows, then there MUST be two Inclusive Tunnels from
2728 VRF-S, one of which is to be used only to carry extranet C-flows (the
2729 "extranet inclusive P-tunnel") and one of which is to be used only to
2730 carry non-extranet C-flows (the "non-extranet inclusive P-tunnel").
2731
2732
2733
2734
2735
2736
2737
2738
2739
2740 <span class="grey">Rekhter, et al. Standards Track [Page 49]</span></pre>
2741 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-50" ></span>
2742 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
2743
2744
2745 In this case, the VRF MUST originate two Intra-AS I-PMSI A-D routes.
2746 Their respective NLRIs MUST of course have different RDs. One of the
2747 Intra-AS I-PMSI A-D routes identifies the extranet inclusive P-tunnel
2748 in its PTA. This route MUST have the VRF's extranet RD in its NLRI.
2749 The other route identifies the non-extranet inclusive P-tunnel in its
2750 PTA. This route MUST have the VRF's default RD in its PTA.
2751
2752 If VRF-S uses an inclusive P-tunnel for carrying extranet traffic but
2753 does not use an inclusive P-tunnel for carrying non-extranet traffic,
2754 then of course only a single Intra-AS I-PMSI A-D route need be
2755 originated. The PTA of this route identifies the "extranet inclusive
2756 P-tunnel". The NLRI of that route MUST contain the VRF's
2757 extranet RD.
2758
2759 An Intra-AS I-PMSI A-D route whose PTA identifies an extranet
2760 inclusive P-tunnel MUST carry the Extranet Separation Extended
2761 Community defined in <a href="#section-4.5">Section 4.5</a>.
2762
2763 The RTs carried by an Intra-AS I-PMSI A-D route whose PTA identifies
2764 the "extranet inclusive P-tunnel" MUST be chosen such that the
2765 following condition holds: if a VRF (call it "VRF-R") imports a
2766 UMH-eligible route from VRF-S and that route matches an extranet
2767 C-source, then VRF-R also imports that Intra-AS I-PMSI A-D route.
2768
2769 Note that when extranet separation is used, it is possible to use an
2770 inclusive P-tunnel for non-extranet traffic while using only
2771 selective P-tunnels for extranet traffic. It is also possible to use
2772 an inclusive P-tunnel for extranet traffic while using only selective
2773 P-tunnels for non-extranet traffic.
2774
2775 <span class="h4"><a class="selflink" id="section-7.3.2" href="#section-7.3.2">7.3.2</a>. S-PMSI A-D Routes</span>
2776
2777 Let R-SP be an S-PMSI A-D route that is exported from VRF-S. Suppose
2778 that R-SP is used to bind some or all of the extranet C-flows from a
2779 given extranet C-source to a given selective P-tunnel. Let R-UMH be
2780 a UMH-eligible route that is exported from VRF-S and matches the
2781 given extranet C-source. In that case, R-SP and R-UMH MUST have at
2782 least one RT in common. Further, the RTs carried by these two routes
2783 MUST be such that every VRF that imports R-UMH also imports R-SP.
2784 These rules apply whether or not R-SP uses wildcards [<a href="./rfc6625" title="&quot;Wildcards in Multicast VPN Auto-Discovery Routes&quot;">RFC6625</a>].
2785
2786
2787
2788
2789
2790
2791
2792
2793
2794
2795
2796 <span class="grey">Rekhter, et al. Standards Track [Page 50]</span></pre>
2797 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-51" ></span>
2798 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
2799
2800
2801 The following rules, specific to the use of extranet separation,
2802 apply:
2803
2804 o A selective P-tunnel MUST NOT carry C-flows from both extranet and
2805 non-extranet C-sources.
2806
2807 o If it is desired to use a (C-*,C-*) S-PMSI to carry extranet
2808 traffic and also use a (C-*,C-*) S-PMSI to carry non-extranet
2809 traffic, then two (C-*,C-*) S-PMSI A-D routes MUST be originated.
2810 These two routes MUST have different RDs in their respective NLRI
2811 fields, and their respective PTAs MUST identify different
2812 P-tunnels. If the route advertises a P-tunnel that carries only
2813 non-extranet traffic, the route's NLRI MUST contain the VRF's
2814 default RD. If the route advertises a P-tunnel that carries only
2815 extranet traffic, the route's NLRI MUST contain the VRF's
2816 extranet RD.
2817
2818 o In the following cases, an S-PMSI A-D route exported from the VRF
2819 MUST have the VRF's extranet RD in its NLRI:
2820
2821 * The S-PMSI A-D route is a (C-S,C-G) or a (C-S,C-*) S-PMSI A-D
2822 route, and C-S is an extranet C-source.
2823
2824 * The S-PMSI A-D route is a (C-*,C-G) S-PMSI A-D route, and C-G
2825 is an extranet C-group.
2826
2827 In all other cases, a (C-S,C-G), (C-S,C-*), or (C-*,C-G) S-PMSI
2828 A-D route MUST have the VRF's default RD in its NLRI.
2829
2830 o A (C-*,C-*) S-PMSI A-D route advertising a P-tunnel that is used
2831 to carry extranet traffic MUST carry the Extranet Separation
2832 Extended Community defined in <a href="#section-4.5">Section 4.5</a>.
2833
2834 An implementation MUST allow the set of RTs carried by the S-PMSI A-D
2835 routes to be specified by configuration. In the absence of such
2836 configuration, an S-PMSI A-D route originated by a given VRF, say
2837 VRF-X, MUST carry a default set of RTs, as specified by the following
2838 rules:
2839
2840 1. Rule 1 of <a href="#section-7.2.2">Section 7.2.2</a> applies.
2841
2842 2. By default, if C-G is an extranet C-group, rule 2 of
2843 <a href="#section-7.2.2">Section 7.2.2</a> applies.
2844
2845 3. By default, if a (C-*,C-*) S-PMSI A-D route originated by VRF-X
2846 is to be used for extranet traffic, it carries the same RTs that
2847 would be carried (as specified in <a href="#section-7.3.1">Section 7.3.1</a>) by an I-PMSI A-D
2848 route originated by VRF-X if that I-PMSI A-D route were
2849
2850
2851
2852 <span class="grey">Rekhter, et al. Standards Track [Page 51]</span></pre>
2853 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-52" ></span>
2854 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
2855
2856
2857 advertising an inclusive P-tunnel for carrying extranet traffic.
2858 In general, a given VRF would not originate both an S-PMSI A-D
2859 route advertising a (C-*,C-*) selective P-tunnel for extranet
2860 traffic and an I-PMSI A-D route advertising an inclusive P-tunnel
2861 for extranet traffic, as the inclusive P-tunnel would not get
2862 used in that case.
2863
2864 <span class="h4"><a class="selflink" id="section-7.3.3" href="#section-7.3.3">7.3.3</a>. Source Active A-D Routes</span>
2865
2866 The procedures of <a href="#section-7.2.3">Section 7.2.3</a> apply.
2867
2868 However, if a Source Active A-D route is exported from a given VRF
2869 and the route contains C-S, where C-S is an extranet C-source, then
2870 the RD of the route's NLRI MUST be the extranet RD of the VRF.
2871 Otherwise, the RD is the default RD of the VRF.
2872
2873 <span class="h3"><a class="selflink" id="section-7.4" href="#section-7.4">7.4</a>. Determining the Expected P-Tunnel for a C-Flow</span>
2874
2875 This section applies whether extranet separation is used or not.
2876
2877 In the context of a VRF with receivers for a particular C-flow, a PE
2878 must determine the P-tunnel over which packets of that C-flow are
2879 expected to arrive. This is done by finding an I-PMSI or S-PMSI A-D
2880 route that "matches" the flow. The matching A-D route will contain a
2881 PTA that specifies the P-tunnel being used to carry the traffic of
2882 that C-flow. We will refer to this P-tunnel as the "expected
2883 P-tunnel" for the C-flow. (Note that, per [<a href="#ref-MVPN-IR" title="&quot;Ingress Replication Tunnels in Multicast VPN&quot;">MVPN-IR</a>], if the PTA
2884 specifies a tunnel of type "Ingress Replication" (IR), the identifier
2885 of the P-tunnel is actually the NLRI of the I-PMSI or S-PMSI A-D
2886 route. If the PTA specifies a tunnel type other than IR, the
2887 identifier of the P-tunnel is found in the Tunnel Identifier field of
2888 the PTA.)
2889
2890 A PE that needs to receive a given (C-S,C-G) or (C-*,C-G) C-flow MUST
2891 join the expected P-tunnel for that C-flow, and the PE MUST remain
2892 joined to the P-tunnel as long as (1) the PE continues to need to
2893 receive the given C-flow and (2) the P-tunnel continues to remain the
2894 expected P-tunnel for that C-flow. Procedures for joining and
2895 leaving a tunnel depend, of course, on the tunnel type.
2896
2897 If a PTA specifies a non-zero MPLS label for a tunnel that is not an
2898 IR tunnel, then the PE originating the A-D route containing that PTA
2899 is advertising an aggregate P-tunnel. The aggregate P-tunnel can be
2900 thought of as an outer P-tunnel multiplexing some number of inner
2901 P-tunnels. The inner P-tunnels are demultiplexed by means of the
2902 MPLS label in the PTA. In this document, when we talk of the
2903 "expected P-tunnel" in the context of an aggregate P-tunnel, we refer
2904
2905
2906
2907
2908 <span class="grey">Rekhter, et al. Standards Track [Page 52]</span></pre>
2909 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-53" ></span>
2910 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
2911
2912
2913 to a particular inner P-tunnel, not to the outer P-tunnel. It is
2914 this "inner P-tunnel" that is the expected P-tunnel for a given
2915 C-flow.
2916
2917 In order to find the expected P-tunnel for a given C-flow, the
2918 upstream PE of the C-flow is first determined. Then, the S-PMSI A-D
2919 routes originated by that PE are examined, and their NLRIs compared
2920 to the (C-S/C-RP,C-G) of the flow, to see if there is a "match for
2921 reception". (If there is no S-PMSI A-D route that matches a given
2922 C-flow, the expected P-tunnel for that C-flow may have been
2923 advertised in an I-PMSI A-D route; see <a href="#section-7.4.5">Section 7.4.5</a>.)
2924
2925 The rules for determining, in non-extranet cases, whether a given
2926 C-flow is a "match for reception" for a given S-PMSI A-D route are
2927 given in <a href="./rfc6625#section-3.2">Section&nbsp;3.2 of [RFC6625]</a>. Note that we use the terms
2928 "installed" and "originated" as they are defined in <a href="./rfc6625#section-3.2">Section&nbsp;3.2 of
2929 [RFC6625]</a>. (See also <a href="#section-1.1">Section 1.1</a> of this document.)
2930
2931 This specification provides additional rules for determining whether
2932 a given S-PMSI A-D route is a "match for reception" for a given
2933 (C-S/C-RP,C-G). Note that these rules all assume the context of a
2934 particular VRF into which the A-D route has been imported.
2935
2936 The rules given in [<a href="./rfc6625" title="&quot;Wildcards in Multicast VPN Auto-Discovery Routes&quot;">RFC6625</a>] for determining whether a given S-PMSI
2937 A-D route is a "match for transmission" remain unchanged.
2938
2939 Suppose that a PE has originated a C-multicast Shared Tree Join for
2940 (C-*,C-G) but has not originated a C-multicast Source Tree Join for
2941 (C-S,C-G). Suppose also that the PE has received and installed a
2942 Source Active A-D route for (C-S,C-G). As described in <a href="./rfc6514#section-13.2">Section&nbsp;13.2
2943 of [RFC6514]</a>, the PE must receive the (C-S,C-G) traffic from the
2944 tunnel the originator of the installed Source Active A-D route uses
2945 for sending (C-S,C-G).
2946
2947 The originator of the installed Source Active A-D route is determined
2948 as follows:
2949
2950 1. Look at the "UMH Route Candidate Set" for C-S, as defined in
2951 <a href="./rfc6513#section-5.1.3">Section&nbsp;5.1.3 of [RFC6513]</a>.
2952
2953 2. From that set, select a subset of UMH routes to C-S, such that
2954 each route in the subset has at least one RT in common with the
2955 Source Active A-D route and at least one of the RTs in common is
2956 an import RT of the VRF.
2957
2958 3. From that subset, find the route whose RD is the same as the RD
2959 from the NLRI of the Source Active A-D route.
2960
2961
2962
2963
2964 <span class="grey">Rekhter, et al. Standards Track [Page 53]</span></pre>
2965 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-54" ></span>
2966 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
2967
2968
2969 4. The upstream PE is the PE identified in the VRF Route Import
2970 Extended Community of that route.
2971
2972 5. The upstream AS is the AS identified in the Source AS Extended
2973 Community of that route.
2974
2975 If step 2 results in an empty set or step 3 fails to find a route,
2976 then the upstream PE of the Source Active A-D route cannot be
2977 determined, and it is necessary to act as if the Source Active A-D
2978 route had not been installed. (A subsequent change to the UMH Route
2979 Candidate Set for C-S may require that a new attempt be made to
2980 determine the upstream PE.)
2981
2982 Once the upstream PE is determined, the P-tunnel over which the flow
2983 is expected is determined according to the procedures already
2984 described in this section.
2985
2986 <span class="h4"><a class="selflink" id="section-7.4.1" href="#section-7.4.1">7.4.1</a>. (C-S,C-G) S-PMSI A-D Routes</span>
2987
2988 When extranet functionality is being provided, an S-PMSI A-D route
2989 whose NLRI contains (C-S,C-G) is NOT considered to be a "match for
2990 reception" for a given C-flow (C-S,C-G) unless one of the following
2991 conditions holds (in addition to the conditions specified in
2992 [<a href="./rfc6625" title="&quot;Wildcards in Multicast VPN Auto-Discovery Routes&quot;">RFC6625</a>]):
2993
2994 o the "single C-source per (C-S,C-G) or (C-S,C-*) P-tunnel" is
2995 provisioned, or
2996
2997 o the selected UMH route for C-S has at least one RT in common with
2998 the S-PMSI A-D route, and at least one of the common RTs is an
2999 import RT of the VRF.
3000
3001 <span class="h4"><a class="selflink" id="section-7.4.2" href="#section-7.4.2">7.4.2</a>. (C-S,C-*) S-PMSI A-D Routes</span>
3002
3003 When extranet functionality is being provided, an S-PMSI A-D route
3004 whose NLRI contains (C-S,C-*) is NOT considered to be a "match for
3005 reception" for a given C-flow (C-S,C-G) unless one of the following
3006 conditions holds (in addition to the conditions specified in
3007 [<a href="./rfc6625" title="&quot;Wildcards in Multicast VPN Auto-Discovery Routes&quot;">RFC6625</a>]):
3008
3009 o the "single C-source per (C-S,C-G) or (C-S,C-*) P-tunnel" is
3010 provisioned, or
3011
3012 o the selected UMH route for C-S has at least one RT in common with
3013 the S-PMSI A-D route, and at least one of the common RTs is an
3014 import RT of the VRF.
3015
3016
3017
3018
3019
3020 <span class="grey">Rekhter, et al. Standards Track [Page 54]</span></pre>
3021 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-55" ></span>
3022 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
3023
3024
3025 <span class="h4"><a class="selflink" id="section-7.4.3" href="#section-7.4.3">7.4.3</a>. (C-*,C-G) S-PMSI A-D Routes</span>
3026
3027 When extranet functionality is being provided, an S-PMSI A-D route
3028 whose NLRI contains (C-*,C-G) is NOT considered to be a "match for
3029 reception" for a given C-flow (C-S,C-G) in a given VRF unless either
3030 condition 1 or condition 2 below holds (in addition to the conditions
3031 specified in [<a href="./rfc6625" title="&quot;Wildcards in Multicast VPN Auto-Discovery Routes&quot;">RFC6625</a>]):
3032
3033 1. The given VRF has currently originated a C-multicast Shared Tree
3034 Join route for (C-*,C-G), and
3035
3036 a. (C-*,C-G) matches an installed (C-*,C-G) S-PMSI A-D route
3037 (according to [<a href="./rfc6625" title="&quot;Wildcards in Multicast VPN Auto-Discovery Routes&quot;">RFC6625</a>]) in the given VRF, and
3038
3039 b. either
3040
3041 i. the "single C-group per (C-*,C-G) P-tunnel" policy has
3042 been provisioned, or
3043
3044 ii. the RTs of that S-PMSI A-D route form a non-empty
3045 intersection with the RTs carried in the VRF's
3046 selected UMH route for C-RP of that C-G, or
3047
3048 iii. installed in the VRF is at least one (C-S,C-G) Source
3049 Active A-D route that was originated by the same PE as
3050 the (C-*,C-G) S-PMSI A-D route.
3051
3052 2. The given VRF does not have a currently originated C-multicast
3053 Shared Tree Join for (C-*,C-G), but
3054
3055 a. there are one or more values for C-S for which the VRF has a
3056 currently originated Source Tree Join C-multicast route for
3057 (C-S,C-G), and
3058
3059 b. the (C-* C-G) S-PMSI A-D route matches (according to
3060 [<a href="./rfc6625" title="&quot;Wildcards in Multicast VPN Auto-Discovery Routes&quot;">RFC6625</a>]) each such (C-S,C-G), and
3061
3062 c. either
3063
3064 i. the "single C-group per (C-*,C-G) P-tunnel" policy has
3065 been provisioned, or
3066
3067 ii. the RTs of that S-PMSI A-D route form a non-empty
3068 intersection with the RTs carried in the VRF's selected
3069 UMH routes for each such C-S
3070
3071
3072
3073
3074
3075
3076 <span class="grey">Rekhter, et al. Standards Track [Page 55]</span></pre>
3077 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-56" ></span>
3078 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
3079
3080
3081 If a VRF has an installed (C-*,C-G) S-PMSI A-D route but does not
3082 have a (C-S,C-G) or (C-*,C-G) multicast state that matches that
3083 route for reception, the procedures of <a href="#section-12.3">Section 12.3</a> ("Receiving
3084 S-PMSI A-D Routes by PEs") of [<a href="./rfc6514" title="&quot;BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs&quot;">RFC6514</a>] are not invoked for that
3085 route. If those multicast states are created at some later time
3086 when the route is still installed, the procedures of <a href="./rfc6514#section-12.3">Section&nbsp;12.3
3087 of [RFC6514]</a> are invoked at that time.
3088
3089 <span class="h4"><a class="selflink" id="section-7.4.4" href="#section-7.4.4">7.4.4</a>. (C-*,C-*) S-PMSI A-D Routes</span>
3090
3091 A (C-*,C-*) S-PMSI A-D route (call it "R-AD") is NOT considered to be
3092 a "match for reception" for a given C-flow (C-S,C-G) or (C-*,C-G)
3093 unless the following conditions hold (in addition to the conditions
3094 specified in [<a href="./rfc6625" title="&quot;Wildcards in Multicast VPN Auto-Discovery Routes&quot;">RFC6625</a>]):
3095
3096 o The selected UMH route (call it "R-UMH") for C-S or for C-G's
3097 C-RP, respectively, has at least one RT in common with R-AD, and
3098 at least one of the common RTs is an import RT of the VRF.
3099
3100 o Either R-AD and R-UMH both carry the Extranet Separation Extended
3101 Community or neither carries the Extranet Separation Extended
3102 Community.
3103
3104 <span class="h4"><a class="selflink" id="section-7.4.5" href="#section-7.4.5">7.4.5</a>. I-PMSI A-D Routes</span>
3105
3106 If a particular egress VRF in a particular egress PE contains no
3107 matching S-PMSI A-D routes for a particular C-flow, then the C-flow
3108 is expected to arrive (at that egress VRF) on an inclusive P-tunnel.
3109
3110 Suppose that an egress PE has originated a (C-S,C-G) C-multicast
3111 Source Tree Join. Let R-UMH be the selected UMH route (in the given
3112 egress VRF) for C-S. As specified in [<a href="./rfc6514" title="&quot;BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs&quot;">RFC6514</a>], the selected
3113 upstream PE for (C-S,C-G) is determined from the VRF Route Import
3114 Extended Community of R-UMH, and the "selected upstream AS" for the
3115 flow is determined from the Source AS Extended Community of R-UMH.
3116
3117 Suppose that an egress PE has originated a (C-*,C-G) C-multicast
3118 Shared Tree Join but has not originated a (C-S,C-G) C-multicast
3119 Source Tree Join. If the egress VRF does not have a (C-S,C-G) Source
3120 Active A-D route installed, the selected upstream PE is determined
3121 from the VRF Route Import Extended Community of the installed
3122 UMH-eligible route matching C-RP, where C-RP is the RP for the group
3123 C-G. The selected upstream AS for the flow is determined from the
3124 Source AS Extended Community of that route. If the egress VRF does
3125 have a (C-S,C-G) Source Active A-D route installed, the selected
3126 upstream PE and upstream AS are determined as specified in
3127 <a href="#section-7.4">Section 7.4</a>. In either case, let R-UMH be the installed UMH-eligible
3128 route matching C-S.
3129
3130
3131
3132 <span class="grey">Rekhter, et al. Standards Track [Page 56]</span></pre>
3133 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-57" ></span>
3134 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
3135
3136
3137 The inclusive P-tunnel that is expected to be carrying a particular
3138 C-flow is found as follows:
3139
3140 o If the selected upstream AS is the local AS or segmented Inter-AS
3141 P-tunnels are not being used to instantiate I-PMSIs, then look in
3142 the VRF for an installed Intra-AS I-PMSI A-D route, R-AD, such
3143 that (a) R-AD is originated by the selected upstream PE, (b) R-AD
3144 has at least one RT in common with R-UMH, (c) at least one of the
3145 common RTs is an import RT of the local VRF, and (d) either R-AD
3146 and R-UMH both carry the Extranet Separation Extended Community or
3147 neither carries the Extranet Separation Extended Community.
3148
3149 The PTA of R-AD specifies the P-tunnel over which the traffic of
3150 the given C-flow is expected.
3151
3152 o If the selected upstream AS is not the local AS and segmented
3153 Inter-AS P-tunnels are being used to instantiate I-PMSIs, then
3154 look in the VRF for an installed Inter-AS I-PMSI A-D route, R-AD,
3155 such that (a) the Source AS field of R-AD's NLRI contains the AS
3156 number of the selected upstream AS, (b) R-AD has at least one RT
3157 in common with R-UMH, (c) at least one of the common RTs is an
3158 import RT of the local VRF, and (d) either R-AD and R-UMH both
3159 carry the Extranet Separation Extended Community or neither
3160 carries the Extranet Separation Extended Community.
3161
3162 The PTA of R-AD specifies the P-tunnel over which the traffic of
3163 the given C-flow is expected.
3164
3165 <span class="h3"><a class="selflink" id="section-7.5" href="#section-7.5">7.5</a>. Packets Arriving from the Wrong P-Tunnel</span>
3166
3167 Any packets that arrive on a P-tunnel other than the expected
3168 P-tunnel (as defined in <a href="#section-7.4">Section 7.4</a>) MUST be discarded unless it is
3169 known that all the packets carried by both P-tunnels are from the
3170 same ingress VRF. (See <a href="#section-2.3.1">Section 2.3.1</a> for a more detailed discussion
3171 of when to discard packets from other than the expected P-tunnel.)
3172 Note that packets arriving on the wrong P-tunnel are to be discarded
3173 even if they are arriving from the expected PE.
3174
3175 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Multiple Extranet VRFs on the Same PE</span>
3176
3177 When multiple VRFs that contain extranet receivers for a given
3178 extranet source are present on the same PE, this PE becomes a single
3179 leaf of the P-tunnel used for sending (multicast) traffic from that
3180 source to these extranet receivers. The PE MUST be able to replicate
3181 this traffic to the multiple VRFs. Specific procedures for doing so
3182 are local to the PE and are outside the scope of this document.
3183
3184
3185
3186
3187
3188 <span class="grey">Rekhter, et al. Standards Track [Page 57]</span></pre>
3189 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-58" ></span>
3190 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
3191
3192
3193 Two or more VRFs on the same PE may import the same S-PMSI A-D route.
3194 If this S-PMSI A-D route contains a PTA that has its "Leaf
3195 Information Required" flag set, it may be necessary for the PE to
3196 originate a Leaf A-D route whose NLRI is computed from the NLRI of
3197 the S-PMSI A-D route. (Details are provided in [<a href="./rfc6514" title="&quot;BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs&quot;">RFC6514</a>].) Note
3198 that for a given S-PMSI A-D route, the PE can originate only one
3199 corresponding Leaf A-D route, even if the S-PMSI A-D route is
3200 imported into multiple VRFs. This Leaf A-D route can thus be thought
3201 of as originating from several VRFs. It MUST NOT be withdrawn by the
3202 PE until there are no longer any VRFs originating it.
3203
3204 [<a id="ref-RFC6514">RFC6514</a>] specifies conditions under which a PE originates a
3205 C-multicast Source Tree Join or a C-multicast Shared Tree Join, based
3206 on the (*,G) and (S,G) states associated with a given VRF. It also
3207 specifies the procedure for computing the NLRI of each such route.
3208 While a given PE may contain two or more VRFs that have (extranet)
3209 receivers for the same extranet C-flow, the PE cannot originate more
3210 than one BGP route with a given NLRI. If there are multiple VRFs,
3211 each of which has state that is sufficient to cause a given
3212 C-multicast route to be originated, the route can be thought of as
3213 originating from several VRFs. It MUST NOT be withdrawn by the PE
3214 until there is no longer any VRF with multicast state sufficient to
3215 cause the route to be originated.
3216
3217 For a given extranet, the site(s) that contains the extranet
3218 source(s) and the site(s) that contains the extranet receiver(s) may
3219 be connected to the same PE. In this scenario, the procedures by
3220 which (multicast) traffic from these sources is delivered to these
3221 receivers are local to the PE and are outside the scope of this
3222 document.
3223
3224 An implementation MUST support multiple extranet VRFs on a PE.
3225
3226 <span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. IANA Considerations</span>
3227
3228 IANA has allocated two new codepoints from the "First Come First
3229 Served" [<a href="./rfc5226" title="">RFC5226</a>] range of the "Transitive Opaque Extended Community
3230 Sub-Types" registry (under the top-level registry "Border Gateway
3231 Protocol (BGP) Extended Communities" registry).
3232
3233 o Extranet Source Extended Community (0x04)
3234
3235 o Extranet Separation Extended Community (0x05)
3236
3237
3238
3239
3240
3241
3242
3243
3244 <span class="grey">Rekhter, et al. Standards Track [Page 58]</span></pre>
3245 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-59" ></span>
3246 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
3247
3248
3249 <span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Security Considerations</span>
3250
3251 The security considerations of [<a href="./rfc6513" title="&quot;Multicast in MPLS/BGP IP VPNs&quot;">RFC6513</a>] and [<a href="./rfc6514" title="&quot;BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs&quot;">RFC6514</a>] are
3252 applicable.
3253
3254 As is the case with any application of technology based upon
3255 [<a href="./rfc4364" title="&quot;BGP/MPLS IP Virtual Private Networks (VPNs)&quot;">RFC4364</a>], misconfiguration of the RTs may result in VPN security
3256 violations (i.e., may result in a packet being delivered to a VPN
3257 where, according to policy, it is not supposed to go).
3258
3259 In those cases where the set of extranet sources of a particular VRF
3260 are manually configured, improper configuration of the VRF can result
3261 in VPN security violations -- traffic from a host that is not an
3262 extranet source may be treated as if it were traffic from an extranet
3263 source.
3264
3265 <a href="#section-4.4">Section 4.4</a> specifies the optional use of a new Extended Community --
3266 the Extranet Source Extended Community. Security considerations
3267 regarding the use and distribution of that Extended Community are
3268 discussed in that section.
3269
3270 The procedures of this document do not provide encryption of the data
3271 flows that are sent across the SP backbone network. Hence, these
3272 procedures do not by themselves ensure the privacy or integrity of
3273 the data against attacks on the backbone network.
3274
3275 In general, different VPNs are allowed to have overlapping IP address
3276 spaces; i.e., a host in one VPN may have the same IP address as a
3277 host in another. This is safe because the customer routes from a
3278 given VPN do not pass into other VPNs. Even if there are overlapping
3279 address spaces among VPNs, the routes that are known at any given VPN
3280 site are unambiguous, as long as the address space of that VPN is
3281 unambiguous. However, this is not necessarily true when extranet
3282 service is provided. If an extranet C-receiver in VPN-R is to be
3283 able to receive multicast traffic from an extranet C-source in VPN-S,
3284 then the address of the VPN-S extranet C-source must be imported into
3285 one or more VPN-R VRFs. If that address is also the address of a
3286 VPN-R non-extranet C-source, then a system attempting to receive an
3287 extranet C-flow from the VPN-R extranet C-source may instead receive
3288 a non-extranet C-flow from the VPN-S C-source. Otherwise, a VPN
3289 security violation may result.
3290
3291 That is, when provisioning an extranet between two VPNs that have
3292 overlapping address spaces, one must ensure that the IP addresses of
3293 the extranet sources and the extranet receivers are not from the
3294 overlapping part of the address space. This document specifies that
3295 if a route is imported into a given VRF, all addresses that match
3296 that route must be unambiguous in the context of that VRF. Improper
3297
3298
3299
3300 <span class="grey">Rekhter, et al. Standards Track [Page 59]</span></pre>
3301 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-60" ></span>
3302 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
3303
3304
3305 provisioning of the extranet source addresses or improper
3306 provisioning of the RTs may cause this rule to be violated and may
3307 result in a VPN security violation.
3308
3309 It is possible that a given multicast C-source is the source of
3310 multiple flows, some of which are intended to be extranet C-flows and
3311 some of which are intended to be non-extranet flows. However, the
3312 procedures of this document will allow any C-receiver that is able to
3313 receive the extranet C-flows from a given C-source to also receive
3314 the non-extranet C-flows from that source. As a result, VPN security
3315 violations may result if any system is a C-source for both extranet
3316 and non-extranet C-flows. However, the set of C-flows transmitted by
3317 a given C-source is not under the control of the SP. SPs who offer
3318 the extranet MVPN service must make sure that this potential for VPN
3319 security violations is clearly understood by the customers who
3320 administer the C-sources.
3321
3322 This specification does not require that UMH-eligible routes be "host
3323 routes"; they may be less specific routes. So, it is possible for
3324 the NLRI of a UMH-eligible route to contain an address prefix that
3325 matches the address of both an extranet C-source and a non-extranet
3326 C-source. If such a route is exported from a VPN-S VRF and imported
3327 by a VPN-R VRF, C-receivers contained in VPN-R will be able to
3328 receive C-flows from the non-extranet C-sources whose addresses match
3329 that route. This may result in VPN security violations. Service
3330 providers who offer the extranet MVPN service must make sure that
3331 this is clearly understood by the customers who administer the
3332 distribution of routes from CE routers to PE routers.
3333
3334 If the address ambiguities described in Sections <a href="#section-2.1">2.1</a> and <a href="#section-2.2">2.2</a> are not
3335 prohibited by deployment of the policies described in <a href="#section-2.3.2">Section 2.3.2</a>,
3336 VRFs must be able to discard traffic that arrives on the wrong
3337 P-tunnel (as specified in Sections <a href="#section-2.3.1">2.3.1</a> and <a href="#section-7.5">7.5</a>). Otherwise, VPN
3338 security violations may occur.
3339
3340
3341
3342
3343
3344
3345
3346
3347
3348
3349
3350
3351
3352
3353
3354
3355
3356 <span class="grey">Rekhter, et al. Standards Track [Page 60]</span></pre>
3357 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-61" ></span>
3358 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
3359
3360
3361 <span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. References</span>
3362
3363 <span class="h3"><a class="selflink" id="section-11.1" href="#section-11.1">11.1</a>. Normative References</span>
3364
3365 [<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
3366 Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>,
3367 DOI 10.17487/RFC2119, March 1997,
3368 &lt;<a href="http://www.rfc-editor.org/info/rfc2119">http://www.rfc-editor.org/info/rfc2119</a>&gt;.
3369
3370 [<a id="ref-RFC4360">RFC4360</a>] Sangli, S., Tappan, D., and Y. Rekhter, "BGP Extended
3371 Communities Attribute", <a href="./rfc4360">RFC 4360</a>, DOI 10.17487/RFC4360,
3372 February 2006, &lt;<a href="http://www.rfc-editor.org/info/rfc4360">http://www.rfc-editor.org/info/rfc4360</a>&gt;.
3373
3374 [<a id="ref-RFC4364">RFC4364</a>] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private
3375 Networks (VPNs)", <a href="./rfc4364">RFC 4364</a>, DOI 10.17487/RFC4364,
3376 February 2006, &lt;<a href="http://www.rfc-editor.org/info/rfc4364">http://www.rfc-editor.org/info/rfc4364</a>&gt;.
3377
3378 [<a id="ref-RFC6513">RFC6513</a>] Rosen, E., Ed., and R. Aggarwal, Ed., "Multicast in
3379 MPLS/BGP IP VPNs", <a href="./rfc6513">RFC 6513</a>, DOI 10.17487/RFC6513,
3380 February 2012, &lt;<a href="http://www.rfc-editor.org/info/rfc6513">http://www.rfc-editor.org/info/rfc6513</a>&gt;.
3381
3382 [<a id="ref-RFC6514">RFC6514</a>] Aggarwal, R., Rosen, E., Morin, T., and Y. Rekhter, "BGP
3383 Encodings and Procedures for Multicast in MPLS/BGP IP
3384 VPNs", <a href="./rfc6514">RFC 6514</a>, DOI 10.17487/RFC6514, February 2012,
3385 &lt;<a href="http://www.rfc-editor.org/info/rfc6514">http://www.rfc-editor.org/info/rfc6514</a>&gt;.
3386
3387 [<a id="ref-RFC6625">RFC6625</a>] Rosen, E., Ed., Rekhter, Y., Ed., Hendrickx, W., and R.
3388 Qiu, "Wildcards in Multicast VPN Auto-Discovery Routes",
3389 <a href="./rfc6625">RFC 6625</a>, DOI 10.17487/RFC6625, May 2012,
3390 &lt;<a href="http://www.rfc-editor.org/info/rfc6625">http://www.rfc-editor.org/info/rfc6625</a>&gt;.
3391
3392 [<a id="ref-RFC7153">RFC7153</a>] Rosen, E. and Y. Rekhter, "IANA Registries for BGP
3393 Extended Communities", <a href="./rfc7153">RFC 7153</a>, DOI 10.17487/RFC7153,
3394 March 2014, &lt;<a href="http://www.rfc-editor.org/info/rfc7153">http://www.rfc-editor.org/info/rfc7153</a>&gt;.
3395
3396 [<a id="ref-RFC7761">RFC7761</a>] Fenner, B., Handley, M., Holbrook, H., Kouvelas, I.,
3397 Parekh, R., Zhang, Z., and L. Zheng, "Protocol Independent
3398 Multicast - Sparse Mode (PIM-SM): Protocol Specification
3399 (Revised)", STD 83, <a href="./rfc7761">RFC 7761</a>, DOI 10.17487/RFC7761,
3400 March 2016, &lt;<a href="http://www.rfc-editor.org/info/rfc7761">http://www.rfc-editor.org/info/rfc7761</a>&gt;.
3401
3402
3403
3404
3405
3406
3407
3408
3409
3410
3411
3412 <span class="grey">Rekhter, et al. Standards Track [Page 61]</span></pre>
3413 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-62" ></span>
3414 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
3415
3416
3417 <span class="h3"><a class="selflink" id="section-11.2" href="#section-11.2">11.2</a>. Informative References</span>
3418
3419 [<a id="ref-MVPN-IR">MVPN-IR</a>] Rosen, E., Ed., Subramanian, K., and Z. Zhang, "Ingress
3420 Replication Tunnels in Multicast VPN", Work in Progress,
3421 <a href="./draft-ietf-bess-ir-03">draft-ietf-bess-ir-03</a>, April 2016.
3422
3423 [<a id="ref-RFC3446">RFC3446</a>] Kim, D., Meyer, D., Kilmer, H., and D. Farinacci, "Anycast
3424 Rendevous Point (RP) mechanism using Protocol Independent
3425 Multicast (PIM) and Multicast Source Discovery Protocol
3426 (MSDP)", <a href="./rfc3446">RFC 3446</a>, DOI 10.17487/RFC3446, January 2003,
3427 &lt;<a href="http://www.rfc-editor.org/info/rfc3446">http://www.rfc-editor.org/info/rfc3446</a>&gt;.
3428
3429 [<a id="ref-RFC3618">RFC3618</a>] Fenner, B., Ed., and D. Meyer, Ed., "Multicast Source
3430 Discovery Protocol (MSDP)", <a href="./rfc3618">RFC 3618</a>,
3431 DOI 10.17487/RFC3618, October 2003,
3432 &lt;<a href="http://www.rfc-editor.org/info/rfc3618">http://www.rfc-editor.org/info/rfc3618</a>&gt;.
3433
3434 [<a id="ref-RFC4610">RFC4610</a>] Farinacci, D. and Y. Cai, "Anycast-RP Using Protocol
3435 Independent Multicast (PIM)", <a href="./rfc4610">RFC 4610</a>,
3436 DOI 10.17487/RFC4610, August 2006,
3437 &lt;<a href="http://www.rfc-editor.org/info/rfc4610">http://www.rfc-editor.org/info/rfc4610</a>&gt;.
3438
3439 [<a id="ref-RFC4875">RFC4875</a>] Aggarwal, R., Ed., Papadimitriou, D., Ed., and S.
3440 Yasukawa, Ed., "Extensions to Resource Reservation
3441 Protocol - Traffic Engineering (RSVP-TE) for Point-to-
3442 Multipoint TE Label Switched Paths (LSPs)", <a href="./rfc4875">RFC 4875</a>,
3443 DOI 10.17487/RFC4875, May 2007,
3444 &lt;<a href="http://www.rfc-editor.org/info/rfc4875">http://www.rfc-editor.org/info/rfc4875</a>&gt;.
3445
3446 [<a id="ref-RFC5015">RFC5015</a>] Handley, M., Kouvelas, I., Speakman, T., and L. Vicisano,
3447 "Bidirectional Protocol Independent Multicast
3448 (BIDIR-PIM)", <a href="./rfc5015">RFC 5015</a>, DOI 10.17487/RFC5015,
3449 October 2007, &lt;<a href="http://www.rfc-editor.org/info/rfc5015">http://www.rfc-editor.org/info/rfc5015</a>&gt;.
3450
3451 [<a id="ref-RFC5059">RFC5059</a>] Bhaskar, N., Gall, A., Lingard, J., and S. Venaas,
3452 "Bootstrap Router (BSR) Mechanism for Protocol Independent
3453 Multicast (PIM)", <a href="./rfc5059">RFC 5059</a>, DOI 10.17487/RFC5059,
3454 January 2008, &lt;<a href="http://www.rfc-editor.org/info/rfc5059">http://www.rfc-editor.org/info/rfc5059</a>&gt;.
3455
3456
3457
3458
3459
3460
3461
3462
3463
3464
3465
3466
3467
3468 <span class="grey">Rekhter, et al. Standards Track [Page 62]</span></pre>
3469 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-63" ></span>
3470 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
3471
3472
3473 [<a id="ref-RFC5226">RFC5226</a>] Narten, T. and H. Alvestrand, "Guidelines for Writing an
3474 IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc5226">RFC 5226</a>,
3475 DOI 10.17487/RFC5226, May 2008,
3476 &lt;<a href="http://www.rfc-editor.org/info/rfc5226">http://www.rfc-editor.org/info/rfc5226</a>&gt;.
3477
3478 [<a id="ref-RFC6388">RFC6388</a>] Wijnands, IJ., Ed., Minei, I., Ed., Kompella, K., and B.
3479 Thomas, "Label Distribution Protocol Extensions for Point-
3480 to-Multipoint and Multipoint-to-Multipoint Label Switched
3481 Paths", <a href="./rfc6388">RFC 6388</a>, DOI 10.17487/RFC6388, November 2011,
3482 &lt;<a href="http://www.rfc-editor.org/info/rfc6388">http://www.rfc-editor.org/info/rfc6388</a>&gt;.
3483
3484
3485
3486
3487
3488
3489
3490
3491
3492
3493
3494
3495
3496
3497
3498
3499
3500
3501
3502
3503
3504
3505
3506
3507
3508
3509
3510
3511
3512
3513
3514
3515
3516
3517
3518
3519
3520
3521
3522
3523
3524 <span class="grey">Rekhter, et al. Standards Track [Page 63]</span></pre>
3525 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-64" ></span>
3526 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
3527
3528
3529 Acknowledgments
3530
3531 The authors wish to thank DP Ayyadevara, Robert Kebler, Padmini
3532 Misra, Rayen Mohanty, Maria Napierala, Karthik Subramanian, and Kurt
3533 Windisch for their contributions to this work.
3534
3535 We also wish to thank Lizhong Jin and Rishabh Parekh for their
3536 reviews and comments.
3537
3538 Special thanks to Jeffrey (Zhaohui) Zhang for his careful review and
3539 for providing the ASCII art appearing in <a href="#section-2">Section 2</a>.
3540
3541 Contributors
3542
3543 Below is a list of other contributing authors, in alphabetical order:
3544
3545 Wim Henderickx
3546 Nokia
3547 Copernicuslaan 50
3548 Antwerp 2018
3549 Belgium
3550
3551 Email: [email protected]
3552
3553
3554 Praveen Muley
3555 Nokia
3556
3557 Email: [email protected]
3558
3559
3560 Ray Qiu
3561 Juniper Networks, Inc.
3562 1194 North Mathilda Avenue
3563 Sunnyvale, CA 94089
3564 United States
3565
3566 Email: [email protected]
3567
3568
3569 IJsbrand Wijnands
3570 Cisco Systems, Inc.
3571 De Kleetlaan 6a
3572 Diegem 1831
3573 Belgium
3574
3575 Email: [email protected]
3576
3577
3578
3579
3580 <span class="grey">Rekhter, et al. Standards Track [Page 64]</span></pre>
3581 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-65" ></span>
3582 <span class="grey"><a href="./rfc7900">RFC 7900</a> Extranet Multicast in BGP/IP MPLS VPNs June 2016</span>
3583
3584
3585 Authors' Addresses
3586
3587 Yakov Rekhter (editor)
3588 Juniper Networks, Inc.
3589 1194 North Mathilda Avenue
3590 Sunnyvale, CA 94089
3591 United States
3592
3593
3594 Eric C. Rosen (editor)
3595 Juniper Networks, Inc.
3596 10 Technology Park Drive
3597 Westford, Massachusetts 01886
3598 United States
3599
3600 Email: [email protected]
3601
3602
3603 Rahul Aggarwal
3604 Arktan
3605
3606 Email: [email protected]
3607
3608
3609 Yiqun Cai
3610 Alibaba Group
3611 400 S El Camino Real #400
3612 San Mateo, CA 94402
3613 United States
3614
3615 Email: [email protected]
3616
3617
3618 Thomas Morin
3619 Orange
3620 2 Avenue Pierre-Marzin
3621 22307 Lannion Cedex
3622 France
3623
3624 Email: [email protected]
3625
3626
3627
3628
3629
3630
3631
3632
3633
3634
3635
3636 Rekhter, et al. Standards Track [Page 65]
3637 </pre>