Debian Codegraph @

rfc6625.html

raw
1 <pre>Internet Engineering Task Force (IETF) E. Rosen, Ed.
2 Request for Comments: 6625 Cisco Systems, Inc.
3 Updates: <a href="./rfc6514">6514</a> Y. Rekhter, Ed.
4 Category: Standards Track Juniper Networks, Inc.
5 ISSN: 2070-1721 W. Henderickx
6 Alcatel-Lucent
7 R. Qiu
8 Huawei
9 May 2012
10
11
12 <span class="h1">Wildcards in Multicast VPN Auto-Discovery Routes</span>
13
14 Abstract
15
16 In Multicast Virtual Private Networks (MVPNs), customer multicast
17 flows are carried in "tunnels" through a service provider's network.
18 The base specifications for MVPN define BGP multicast VPN "auto-
19 discovery routes" and specify how to use an auto-discovery route to
20 advertise the fact that an individual customer multicast flow is
21 being carried in a particular tunnel. However, those specifications
22 do not provide a way to specify, in a single such route, that
23 multiple customer flows are being carried in a single tunnel. Those
24 specifications also do not provide a way to advertise that a
25 particular tunnel is to be used by default to carry all customer
26 flows, except in the case where that tunnel is joined by all the
27 provider edge routers of the MVPN. This document eliminates these
28 restrictions by specifying the use of "wildcard" elements in the
29 customer flow identifiers. With wildcard elements, a single auto-
30 discovery route can refer to multiple customer flows or even to all
31 customer flows.
32
33 Status of This Memo
34
35 This is an Internet Standards Track document.
36
37 This document is a product of the Internet Engineering Task Force
38 (IETF). It represents the consensus of the IETF community. It has
39 received public review and has been approved for publication by the
40 Internet Engineering Steering Group (IESG). Further information on
41 Internet Standards is available in <a href="./rfc5741#section-2">Section&nbsp;2 of RFC 5741</a>.
42
43 Information about the current status of this document, any errata,
44 and how to provide feedback on it may be obtained at
45 <a href="http://www.rfc-editor.org/info/rfc6625">http://www.rfc-editor.org/info/rfc6625</a>.
46
47
48
49
50
51
52 <span class="grey">Rosen, 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="./rfc6625">RFC 6625</a> Wildcards in MVPN A-D Routes May 2012</span>
55
56
57 Copyright Notice
58
59 Copyright (c) 2012 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-3">3</a>
75 <a href="#section-1.1">1.1</a>. Terminology ................................................<a href="#page-3">3</a>
76 <a href="#section-1.2">1.2</a>. Wildcards in S-PMSI A-D Routes .............................<a href="#page-5">5</a>
77 <a href="#section-1.3">1.3</a>. Use Cases ..................................................<a href="#page-5">5</a>
78 <a href="#section-2">2</a>. Encoding of Wildcards ...........................................<a href="#page-7">7</a>
79 <a href="#section-3">3</a>. Finding the Matching S-PMSI A-D Route ...........................<a href="#page-8">8</a>
80 <a href="#section-3.1">3.1</a>. Finding the Match for Data Transmission ....................<a href="#page-8">8</a>
81 <a href="#section-3.2">3.2</a>. Finding the Match for Data Reception .......................<a href="#page-9">9</a>
82 <a href="#section-3.2.1">3.2.1</a>. Finding the Match for (C-S,C-G) .....................<a href="#page-9">9</a>
83 <a href="#section-3.2.2">3.2.2</a>. Finding the Wildcard Match for (C-*,C-G) ............<a href="#page-9">9</a>
84 <a href="#section-4">4</a>. Procedures for S-PMSI A-D Routes with Wildcards ................<a href="#page-10">10</a>
85 <a href="#section-4.1">4.1</a>. Procedures for All Kinds of Wildcards .....................<a href="#page-10">10</a>
86 <a href="#section-4.2">4.2</a>. Procedures for (C-*,C-G) S-PMSI A-D Routes ................<a href="#page-11">11</a>
87 <a href="#section-4.3">4.3</a>. Procedures for (C-S,C-*) S-PMSI A-D Routes ................<a href="#page-12">12</a>
88 <a href="#section-4.4">4.4</a>. Procedures for (C-*,C-*) S-PMSI A-D Routes ................<a href="#page-13">13</a>
89 <a href="#section-5">5</a>. Security Considerations ........................................<a href="#page-15">15</a>
90 <a href="#section-6">6</a>. Acknowledgments ................................................<a href="#page-15">15</a>
91 <a href="#section-7">7</a>. Normative References ...........................................<a href="#page-15">15</a>
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108 <span class="grey">Rosen, 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="./rfc6625">RFC 6625</a> Wildcards in MVPN A-D Routes May 2012</span>
111
112
113 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
114
115 In Multicast Virtual Private Networks (MVPNs), customer multicast
116 flows are carried in tunnels through a service provider's network.
117 The base specifications for MVPN define BGP multicast VPN
118 "auto-discovery routes" and specify how to use an auto-discovery
119 route to advertise the fact that an individual customer multicast
120 flow is being carried in a particular tunnel. However, those
121 specifications do not provide a way to specify, in a single such
122 route, that multiple customer flows are being carried in a single
123 tunnel. Those specifications also do not provide a way to advertise
124 that a particular tunnel is to be used by default to carry all
125 customer flows, except in the case where that tunnel is joined by all
126 the provider edge routers of the MVPN. This document eliminates
127 these restrictions by specifying the use of "wildcard" elements in
128 the customer flow identifiers. With wildcard elements, a single
129 auto-discovery route can refer to multiple customer flows or even to
130 all customer flows.
131
132 <span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Terminology</span>
133
134 This document uses terminology from [<a href="#ref-MVPN" title="&quot;Multicast in MPLS/BGP IP VPNs&quot;">MVPN</a>] and, in particular, uses
135 the prefixes "C-" and "P-", as specified in Section 3.1 of [<a href="#ref-MVPN" title="&quot;Multicast in MPLS/BGP IP VPNs&quot;">MVPN</a>], to
136 distinguish addresses in the "customer address space" from addresses
137 in the "provider address space". The following terminology and
138 acronyms are particularly important in this document:
139
140 - MVPN
141
142 Multicast Virtual Private Network -- a VPN [<a href="#ref-L3VPN" title="&quot;BGP/MPLS IP Virtual Private Networks (VPNs)&quot;">L3VPN</a>] in which
143 multicast service is offered.
144
145 - VRF
146
147 VPN Routing and Forwarding table [<a href="#ref-L3VPN" title="&quot;BGP/MPLS IP Virtual Private Networks (VPNs)&quot;">L3VPN</a>].
148
149 - SP
150
151 Service Provider.
152
153 - P-tunnel
154
155 A tunnel through the network of one or more SPs.
156
157 - C-S
158
159 Multicast Source. A multicast source address, in the address
160 space of a customer network.
161
162
163
164 <span class="grey">Rosen, 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="./rfc6625">RFC 6625</a> Wildcards in MVPN A-D Routes May 2012</span>
167
168
169 - C-G
170
171 Multicast Group. A multicast group address (destination
172 address) in the address space of a customer network.
173
174 - C-multicast flow or C-flow
175
176 A customer multicast flow. Each C-flow is identified by the
177 ordered pair (source address, group address), where each address
178 is in the customer's address space. The identifier of a
179 particular C-flow is usually written as (C-S,C-G).
180
181 - RP
182
183 A "Rendezvous Point", as defined in [<a href="#ref-PIM" title="&quot;Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)&quot;">PIM</a>].
184
185 - C-RP
186
187 A Rendezvous Point whose address is in the customer's address
188 space.
189
190 - Selective P-tunnel
191
192 A P-tunnel that is joined only by Provider Edge (PE) routers
193 that need to receive one or more of the C-flows that are
194 traveling through that P-tunnel.
195
196 - Inclusive P-tunnel
197
198 A P-tunnel that is joined by all PE routers that attach to sites
199 of a given MVPN.
200
201 - S-PMSI A-D route
202
203 Selective Provider Multicast Service Interface Auto-Discovery
204 route. Carried in BGP Update messages, these routes are used to
205 advertise the fact that particular C-flows are bound to (i.e.,
206 are traveling through) particular P-tunnels.
207
208 Familiarity with multicast concepts and terminology [<a href="#ref-PIM" title="&quot;Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)&quot;">PIM</a>] is also
209 presupposed.
210
211 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
212 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
213 document are to be interpreted as described in [<a href="./rfc2119" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">RFC2119</a>].
214
215
216
217
218
219
220 <span class="grey">Rosen, 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="./rfc6625">RFC 6625</a> Wildcards in MVPN A-D Routes May 2012</span>
223
224
225 <span class="h3"><a class="selflink" id="section-1.2" href="#section-1.2">1.2</a>. Wildcards in S-PMSI A-D Routes</span>
226
227 As specified in [<a href="#ref-MVPN" title="&quot;Multicast in MPLS/BGP IP VPNs&quot;">MVPN</a>] and [<a href="#ref-MVPN-BGP" title="&quot;BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs&quot;">MVPN-BGP</a>], an S-PMSI A-D route advertises
228 that a particular C-flow is bound to a particular selective P-tunnel.
229
230 The identifier of the specified C-flow, e.g., (C-S,C-G), is encoded
231 into the Network Layer Reachability Information (NLRI) of the S-PMSI
232 A-D route. The identifier of the specified P-tunnel is encoded into
233 an attribute (the "PMSI Tunnel Attribute") of the S-PMSI A-D route.
234 Each S-PMSI A-D route thus specifies a single C-flow. To bind
235 multiple C-flows to a single P-tunnel, it is necessary to advertise
236 one S-PMSI A-D route for each C-flow, specifying the same P-tunnel in
237 each such route.
238
239 This document defines OPTIONAL extensions to the procedures and
240 encodings specified in [<a href="#ref-MVPN" title="&quot;Multicast in MPLS/BGP IP VPNs&quot;">MVPN</a>] and [<a href="#ref-MVPN-BGP" title="&quot;BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs&quot;">MVPN-BGP</a>]. These extensions
241 enable a single S-PMSI A-D route to advertise that multiple
242 C-multicast flows are bound to a single P-tunnel.
243
244 The extensions specified in this document are based on the notion of
245 allowing the NLRI of an S-PMSI A-D route to contain a "wildcard". In
246 the NLRI encoding, a wildcard can replace the C-S, the C-G, or both.
247 We use the notation "C-*" to denote a wildcard. The extensions allow
248 the NLRI to encode three kinds of wildcards: (C-*,C-*), (C-S,C-*),
249 and (C-*,C-G).
250
251 By using wildcards, a PE may be able to reduce the number of S-PMSI
252 A-D routes it originates, thereby improving the scalability of the
253 control plane. There is, however, no impact on data plane
254 scalability, as the number of P-tunnels is not reduced.
255
256 Encoding and detailed procedures are specified in subsequent sections
257 of this document.
258
259 <span class="h3"><a class="selflink" id="section-1.3" href="#section-1.3">1.3</a>. Use Cases</span>
260
261 There are a number of situations in which it can be useful to use
262 wildcards in the NLRI of an S-PMSI A-D route.
263
264 - Using a selective P-tunnel as the default tunnel.
265
266 There are procedures in [<a href="#ref-MVPN" title="&quot;Multicast in MPLS/BGP IP VPNs&quot;">MVPN</a>] and [<a href="#ref-MVPN-BGP" title="&quot;BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs&quot;">MVPN-BGP</a>] that allow a PE to
267 advertise that it is going to use an inclusive P-tunnel as the
268 P-tunnel on which it will transmit all C-flows by "default".
269 However, those documents do not provide any way for a PE to
270 advertise that it is going to use a selective P-tunnel as the
271 P-tunnel on which it will transmit all C-flows by "default".
272 Using the extensions defined in this document, a PE can
273
274
275
276 <span class="grey">Rosen, 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="./rfc6625">RFC 6625</a> Wildcards in MVPN A-D Routes May 2012</span>
279
280
281 advertise that it is going to use a selective P-tunnel as its
282 default P-tunnel. It does so by advertising an S-PMSI A-D route
283 whose NLRI contains (C-*,C-*).
284
285 - Binding multiple C-flows traveling along a customer's Protocol
286 Independent Multicast - Sparse Mode (PIM-SM) shared tree to a
287 single P-tunnel.
288
289 A PE router may be connected to an MVPN site that contains a
290 customer RP (C-RP). The C-RP may be the root of one or more
291 shared trees. In multicast terminology, these are known as
292 (*,G) trees. By advertising a single S-PMSI A-D route whose
293 NLRI contains the (C-*,C-G) wildcard, the PE can bind all the
294 C-flows traveling along a customer's (*,G) tree to a single
295 P-tunnel. This use case applies only when C-G is a
296 non-bidirectional ASM (Any Source Multicast) group.
297
298 - Binding multiple C-flows with the same C-group address to a
299 single P-tunnel, even if each such C-flow is traveling along a
300 customer's PIM source tree.
301
302 A PE router may be connected to an MVPN site containing several
303 multicast sources that are all sending to a common multicast
304 group, along a customer's PIM source trees. Alternatively, the
305 PE may be connected to several sites, each containing at least
306 one source sending to the common multicast group. By
307 advertising a single S-PMSI A-D route whose NLRI contains
308 (C-*,C-G), the PE can bind these C-flows to a single P-tunnel.
309
310 This use case applies only when the C-group is a
311 non-bidirectional ASM group.
312
313 - Binding multiple C-flows with the same C-group address to a
314 single P-tunnel, when those C-flows are traveling along a
315 customer's BIDIR-PIM shared tree.
316
317 This use case applies only when the C-group is a BIDIR-PIM
318 group.
319
320 - Binding multiple C-flows from a given C-source to a given
321 P-tunnel, irrespective of whether those C-flows all have the
322 same C-group address.
323
324 This can be useful when the C-group addresses are SSM (Single
325 Source Multicast) addresses. Suppose, for example, that a given
326 source transmits multiple "channels" of information, each with
327
328
329
330
331
332 <span class="grey">Rosen, 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="./rfc6625">RFC 6625</a> Wildcards in MVPN A-D Routes May 2012</span>
335
336
337 its own C-group address. It may be desirable to bind all these
338 channels to a single P-tunnel, without having to advertise an
339 S-PMSI A-D route for each one.
340
341 Of course, a specific C-flow, (C-S,C-G), can always be assigned
342 individually to a particular P-tunnel by advertising an S-PMSI A-D
343 route whose NLRI contains (C-S,C-G).
344
345 In <a href="#section-4">Section 4</a>, we will sometimes speak of an S-PMSI A-D route being
346 ignored. When we say the route is "ignored", we do not mean that its
347 normal BGP processing is not done, but that the route is not
348 considered when determining which P-tunnel to use when receiving
349 multicast data, and that the MPLS label values it conveys are not
350 used. We will use "ignore" in quotes to indicate this meaning.
351
352 This document provides procedures only for the case where the
353 P-tunnels are "unidirectional", i.e., point-to-multipoint. The use
354 of "bidirectional" (multipoint-to-multipoint) P-tunnels is outside
355 the scope of this document.
356
357 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Encoding of Wildcards</span>
358
359 Per [<a href="#ref-MVPN-BGP" title="&quot;BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs&quot;">MVPN-BGP</a>] <a href="#section-4.3">Section 4.3</a>, the MCAST-VPN NLRI in an S-PMSI A-D route
360 is encoded as follows:
361
362 +-----------------------------------+
363 | RD (8 octets) |
364 +-----------------------------------+
365 | Multicast Source Length (1 octet) |
366 +-----------------------------------+
367 | Multicast Source (variable) |
368 +-----------------------------------+
369 | Multicast Group Length (1 octet) |
370 +-----------------------------------+
371 | Multicast Group (variable) |
372 +-----------------------------------+
373 | Originating Router's IP Addr |
374 +-----------------------------------+
375
376 where the "source length" and "group length" fields always have a
377 non-zero value. This document specifies that a "zero-length" source
378 or group represents the corresponding wildcard. Specifically,
379
380 - A source wildcard is encoded as a zero-length source field.
381 That is, the "multicast source length" field contains the value
382 0x00, and the "multicast source" field is omitted.
383
384
385
386
387
388 <span class="grey">Rosen, 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="./rfc6625">RFC 6625</a> Wildcards in MVPN A-D Routes May 2012</span>
391
392
393 - A group wildcard is encoded as a zero-length group field. That
394 is, the "multicast group length" field contains the value 0x00,
395 and the "multicast group" field is omitted.
396
397 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Finding the Matching S-PMSI A-D Route</span>
398
399 This section gives the precise rules for determining the S-PMSI A-D
400 route that is "matched" by a given (C-S,C-G) or (C-*,C-G). The
401 procedures in <a href="#section-4">Section 4</a> will make use of the matching rules defined
402 in this section.
403
404 All matching rules assume the context of a given VRF at a given PE.
405
406 The rules that a PE applies to find the S-PMSI A-D route that matches
407 a (C-S,C-G) C-flow that it needs to transmit are slightly different
408 than the rules it applies to find the S-PMSI A-D route that matches a
409 (C-S,C-G) C-flow that it needs to receive. These rules are specified
410 in Sections <a href="#section-3.1">3.1</a> and <a href="#section-3.2">3.2</a>, respectively.
411
412 The S-PMSI A-D route that is matched by a given (C-S,C-G) may change
413 over time, as the result of S-PMSI A-D routes being withdrawn or as a
414 result of new S-PMSI A-D routes being originated and/or advertised.
415 In particular, if (C-S,C-G) matches an S-PMSI A-D route whose NLRI
416 contains (C-*,C-*), the origination or reception of an S-PMSI A-D
417 route whose NLRI contains (C-S,C-G) may cause (C-S,C-G) to match the
418 latter route instead. Note also that the S-PMSI A-D route that
419 matches a given (C-S,C-G) is independent of the order in which the
420 routes were originated or received.
421
422 <span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Finding the Match for Data Transmission</span>
423
424 Consider a given PE; call it PE1. At any given time, for a given VRF
425 at PE1, there is a (possibly empty) set of S-PMSI A-D routes that PE1
426 has originated and advertised, but not withdrawn. We will refer to
427 these routes as "currently originated" by PE1. Suppose that PE1
428 needs to transmit a particular C-flow (C-S,C-G) to one or more other
429 PEs. We use the following algorithm to find the S-PMSI A-D route
430 that the C-flow "matches":
431
432 - If there is an S-PMSI A-D route currently originated by PE1,
433 whose NLRI contains (C-S,C-G), the (C-S,C-G) C-flow matches that
434 route.
435
436 - Otherwise, if there is an S-PMSI A-D route currently originated
437 by PE1, whose NLRI contains (C-S,C-*), AND if C-G is an SSM
438 group address, the (C-S,C-G) C-flow matches that route.
439
440
441
442
443
444 <span class="grey">Rosen, 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="./rfc6625">RFC 6625</a> Wildcards in MVPN A-D Routes May 2012</span>
447
448
449 - Otherwise, if there is an S-PMSI A-D route currently originated
450 by PE1, whose NLRI contains (C-*,C-G), AND if C-G is an ASM
451 group address, the (C-S,C-G) C-flow matches that route.
452
453 - Otherwise, if there is an S-PMSI A-D route currently originated
454 by PE1, whose NLRI contains (C-*,C-*), the (C-S,C-G) C-flow
455 matches that route.
456
457 <span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Finding the Match for Data Reception</span>
458
459 We refer to an S-PMSI A-D route as being "installed" (in a given VRF)
460 if it has been selected by the BGP decision process as the preferred
461 route for its NLRI.
462
463 An S-PMSI A-D route is considered to be "originated by a given PE" if
464 that PE's IP address is contained in the "Originating Router's IP
465 Address" field in the MCAST-VPN NLRI of the route.
466
467 <span class="h4"><a class="selflink" id="section-3.2.1" href="#section-3.2.1">3.2.1</a>. Finding the Match for (C-S,C-G)</span>
468
469 Suppose that a PE router (call it PE1) needs to receive (C-S,C-G),
470 and that PE1 has chosen another PE router (call it PE2) as the
471 "upstream PE" [<a href="#ref-MVPN" title="&quot;Multicast in MPLS/BGP IP VPNs&quot;">MVPN</a>] for that flow.
472
473 - If there is an installed S-PMSI A-D route originated by PE2,
474 whose NLRI contains (C-S,C-G), then (C-S,C-G) matches that
475 route.
476
477 - Otherwise, if there is an installed S-PMSI A-D route originated
478 by PE2, whose NLRI contains (C-S,C-*), AND if C-G is an SSM
479 multicast group address, then (C-S,C-G) matches that route.
480
481 - Otherwise, if there is an installed S-PMSI A-D route originated
482 by PE2, whose NLRI contains (C-*,C-G), AND if C-G is an ASM
483 multicast group address, then (C-S,C-G) matches that route.
484
485 - Otherwise, if there is an installed S-PMSI A-D route originated
486 by PE2, whose NLRI contains (C-*,C-*), then (C-S,C-G) matches
487 that route.
488
489 <span class="h4"><a class="selflink" id="section-3.2.2" href="#section-3.2.2">3.2.2</a>. Finding the Wildcard Match for (C-*,C-G)</span>
490
491 Suppose that a PE router (call it PE1) needs to receive (C-*,C-G)
492 traffic. Note that even if (C-*,C-G) matches a non-wildcard S-PMSI
493 A-D route (as detailed in Section 12.3 of [<a href="#ref-MVPN-BGP" title="&quot;BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs&quot;">MVPN-BGP</a>]), it may also
494 match one or more wildcard S-PMSI A-D routes, as specified below.
495
496
497
498
499
500 <span class="grey">Rosen, 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="./rfc6625">RFC 6625</a> Wildcards in MVPN A-D Routes May 2012</span>
503
504
505 If on PE1 there is an installed S-PMSI A-D route originated by PE2,
506 whose NLRI contains (C-*,C-G), then (C-*,C-G) matches this route if
507 one of the following conditions holds:
508
509 - PE1 determines that PE2 is the "upstream" PE [<a href="#ref-MVPN" title="&quot;Multicast in MPLS/BGP IP VPNs&quot;">MVPN</a>] for the C-RP
510 of C-G, or
511
512 - PE1 has installed one or more Source Active A-D routes for C-G
513 originated by PE2, and for at least one of these routes, PE1
514 does not have a corresponding (C-S,C-G) state, or
515
516 - C-G is a BIDIR-PIM group, or
517
518 - Source Active A-D routes are not being used.
519
520 If (C-*,C-G) does not match a (C-*,C-G) S-PMSI A-D route from PE2,
521 but PE1 has an installed (C-*,C-*) S-PMSI A-D route from PE2, then
522 (C-*,C-G) matches the (C-*,C-*) route if one of the following
523 conditions holds:
524
525 - PE1 determines that PE2 is the "upstream" PE [<a href="#ref-MVPN" title="&quot;Multicast in MPLS/BGP IP VPNs&quot;">MVPN</a>] for the C-RP
526 of C-G, or
527
528 - PE1 has installed one or more Source Active A-D routes for C-G
529 originated by PE2, and for at least one of these routes, PE1
530 does not have a corresponding (C-S,C-G) state, or
531
532 - C-G is a BIDIR-PIM group, or
533
534 - Source Active A-D routes are not being used.
535
536 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Procedures for S-PMSI A-D Routes with Wildcards</span>
537
538 <span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Procedures for All Kinds of Wildcards</span>
539
540 This document defines procedures for the following uses of the
541 wildcard in the NLRI of an S-PMSI A-D route:
542
543 - (C-*,C-G): Source wildcard, group specified.
544
545 - (C-S,C-*): Source specified, group wildcard.
546
547 - (C-*,C-*): Source wildcard, group wildcard.
548
549 All other wildcard functionality is outside the scope of this
550 document.
551
552
553
554
555
556 <span class="grey">Rosen, 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="./rfc6625">RFC 6625</a> Wildcards in MVPN A-D Routes May 2012</span>
559
560
561 The ability to originate S-PMSI A-D routes with a particular kind of
562 wildcard is OPTIONAL. However, if a PE has the ability to originate
563 S-PMSI A-D routes with a particular kind of wildcard, it MUST have
564 the ability to interpret and correctly process S-PMSI A-D routes with
565 that kind of wildcard, and it SHOULD have the ability to interpret
566 and correctly process all three kinds of wildcards.
567
568 For a given MVPN, A PE MUST NOT originate S-PMSI A-D routes with a
569 particular kind of wildcard unless it is known a priori that all PEs
570 attached to that MVPN have the ability to interpret and correctly
571 process that kind of wildcard.
572
573 The criteria for originating and withdrawing S-PMSI A-D routes with
574 wildcards are local to the originating PE.
575
576 As specified in [<a href="#ref-MVPN-BGP" title="&quot;BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs&quot;">MVPN-BGP</a>], an S-PMSI A-D route is carried in the
577 NLRI field of an MP_REACH_NLRI attribute (see [<a href="#ref-BGP-MP" title="&quot;Multiprotocol Extensions for BGP-4&quot;">BGP-MP</a>]). Every
578 S-PMSI A-D route has a particular address family (IPv4 or IPv6), as
579 specified in the Address Family Identifier (AFI) field of the
580 MP_REACH_NLRI attribute. A wildcard in a particular S-PMSI A-D route
581 always refers only to multicast flows of that same address family.
582
583 The procedures specified in this document apply only when the PMSI
584 Tunnel Attribute of an S-PMSI A-D route specifies a "unidirectional"
585 P-tunnel. The use of "bidirectional" P-tunnels (e.g., Multipoint-to-
586 Multipoint Label Switched Paths, BIDIR-PIM trees) is outside the
587 scope of this document.
588
589 In the following sections, an S-PMSI A-D route whose NLRI contains
590 (C-*,C-G), (C-S,C-*), or (C-*,C-*) will be referred to as a
591 "(C-*,C-G) route", a "(C-S,C-*) route", or a "(C-*,C-*)" route,
592 respectively.
593
594 <span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Procedures for (C-*,C-G) S-PMSI A-D Routes</span>
595
596 This document specifies the use of (C-*,C-G) S-PMSI A-D routes only
597 in the case where C-G is an ASM group address. Use of (C-*,C-G)
598 S-PMSI A-D routes where C-G is an SSM group address is outside the
599 scope of this document. If a PE receives a (C-*,C-G) S-PMSI A-D
600 route, and the PE can determine that C-G is an SSM group address, the
601 PE SHOULD "ignore" this S-PMSI A-D route.
602
603 By default, the set of Route Targets carried by a (C-*,C-G) S-PMSI
604 A-D route originated by a given VRF is the same as the set of Route
605 Targets carried in the (unicast) VPN-IP routes that originated from
606 that VRF. An implementation MUST allow the set of Route Targets
607
608
609
610
611
612 <span class="grey">Rosen, 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="./rfc6625">RFC 6625</a> Wildcards in MVPN A-D Routes May 2012</span>
615
616
617 carried by the (C-*,C-G) S-PMSI A-D route to be specified by
618 configuration. In the absence of a configured set of Route Targets,
619 the route MUST carry the default set of Route Targets.
620
621 If a PE needs to transmit packets of a (C-S,C-G) C-flow, and if
622 (C-S,C-G) matches a (C-*,C-G) S-PMSI A-D route according to the rules
623 of <a href="#section-3.1">Section 3.1</a>, then the PE MUST use the P-tunnel advertised in this
624 route for transmitting that C-flow. (Note that it is impossible for
625 a given (C-S,C-G) to match both a (C-*,C-G) wildcard and a (C-S,C-*)
626 wildcard.)
627
628 If PIM is being used as the PE-PE control protocol, then if the PE
629 has (C-*,C-G) and/or (C-S,C-G) state that matches (according to the
630 procedures of <a href="#section-3.2">Section 3.2</a>) an S-PMSI A-D route, the PE MUST join the
631 P-tunnel specified in the PMSI Tunnel Attribute of that route.
632
633 If BGP is being used as the PE-PE control protocol, then
634
635 - If a given PE has currently originated a C-multicast Shared Tree
636 Join for (C-*,C-G), and if (C-*,C-G) matches a (C-*,C-G) S-PMSI
637 A-D route, then the PE applies the procedures of <a href="#section-12.3">Section 12.3</a>
638 ("Receiving S-PMSI A-D Routes by PEs") of [<a href="#ref-MVPN-BGP" title="&quot;BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs&quot;">MVPN-BGP</a>] to that
639 S-PMSI A-D route.
640
641 - Otherwise (the given PE does not have a currently originated
642 C-multicast Shared Tree Join for (C-*,C-G)), if there are one or
643 more values of C-S for which the PE has a currently originated
644 Source Tree Join C-multicast route for (C-S,C-G), the PE MUST
645 join the tunnels advertised by the S-PMSI A-D routes that match
646 (according to <a href="#section-3.2">Section 3.2</a>) each such (C-S,C-G).
647
648 - Otherwise, the PE "ignores" the route.
649
650 <span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. Procedures for (C-S,C-*) S-PMSI A-D Routes</span>
651
652 This document covers the use of (C-S,C-*) S-PMSI A-D routes for only
653 the C-multicast flows where C-G is an SSM group address. Use of
654 (C-S,C-*) S-PMSI A-D routes for other C-multicast flows is outside
655 the scope of this document. Specifically, if a PE receives a
656 (C-S,C-*) S-PMSI A-D route, and the PE can determine that C-G is not
657 an SSM group address, the PE SHOULD "ignore" this S-PMSI A-D route.
658
659 By default, the set of Route Targets carried by a (C-S,C-*) S-PMSI
660 A-D route originated by a given VRF is an intersection between the
661 set of Route Targets carried in the Intra-AS I-PMSI A-D route that
662 originated from that VRF, and the set of Route Targets carried by the
663 unicast VPN-IP route to C-S originated from that VRF. An
664 implementation MUST allow the set of Route Targets carried by the
665
666
667
668 <span class="grey">Rosen, 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="./rfc6625">RFC 6625</a> Wildcards in MVPN A-D Routes May 2012</span>
671
672
673 (C-S,C-*) S-PMSI A-D route to be specified by configuration. In the
674 absence of a configured set of Route Targets, the route MUST carry
675 the default set of Route Targets.
676
677 If a PE needs to transmit packets of a (C-S,C-G) C-flow, and if
678 (C-S,C-G) matches a (C-S,C-*) S-PMSI A-D route according to the rules
679 of <a href="#section-3.1">Section 3.1</a>, then the PE MUST use the P-tunnel advertised in this
680 route for transmitting that C-flow. (Note that it is impossible for
681 a given (C-S,C-G) to match both a (C-*,C-G) wildcard and a (C-S,C-*)
682 wildcard.)
683
684 If PIM is being used as the PE-PE control protocol for distributing
685 C-multicast routing, and if a given PE needs to receive a (C-S,C-G)
686 flow, and if (C-S,C-G) matches the (C-S,C-*) S-PMSI A-D route
687 (according to the procedures of <a href="#section-3.2">Section 3.2</a>), then the PE MUST join
688 the P-tunnel specified in the PMSI Tunnel Attribute of that route.
689
690 If BGP is being used as the PE-PE control protocol for distributing
691 C-multicast routing, and if there is some (C-S,C-G) such that (a) the
692 PE has a currently originated (C-S,C-G) Source Tree Join C-multicast
693 route, AND (b) the given (C-S,C-G) matches (according to the
694 procedures of <a href="#section-3.2">Section 3.2</a>) a (C-S,C-*) S-PMSI A-D route, then PE1
695 applies the procedures of <a href="#section-12.3">Section 12.3</a> ("Receiving S-PMSI A-D Routes
696 by PEs") of [<a href="#ref-MVPN-BGP" title="&quot;BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs&quot;">MVPN-BGP</a>] to the matching S-PMSI A-D route.
697
698 <span class="h3"><a class="selflink" id="section-4.4" href="#section-4.4">4.4</a>. Procedures for (C-*,C-*) S-PMSI A-D Routes</span>
699
700 (C-*,C-*) S-PMSI A-D routes are used when, for a given MVPN, a PE has
701 a policy not to use an I-PMSI for carrying multicast data traffic
702 originated in the MVPN's site(s) connected to that PE. When the
703 (C-*,C-*) wildcard is used together with BGP C-multicast routing,
704 this results in the "S-PMSI only" model, where no I-PMSIs are used at
705 all for the given MVPN.
706
707 A (C-*,C-*) S-PMSI A-D route is originated for a given MVPN by a
708 given PE only if that PE has been provisioned with the policy to
709 do so.
710
711 When so provisioned, the PE MAY originate the (C-*,C-*) S-PMSI A-D
712 route as soon as it is enabled to support the given MVPN.
713 Alternatively, the PE MAY delay originating the route until one of
714 the following conditions holds:
715
716 - The PE-PE protocol for distributing C-multicast routing is PIM,
717 and for the given MVPN, the PE has some (C-S,C-G) or (C-*,C-G)
718 state for which the upstream interface is one of the VRF
719 interfaces for the given MVPN.
720
721
722
723
724 <span class="grey">Rosen, 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="./rfc6625">RFC 6625</a> Wildcards in MVPN A-D Routes May 2012</span>
727
728
729 - The PE-PE protocol for distributing C-multicast routing is BGP,
730 and the given PE has received and installed either of the
731 following:
732
733 * a Source Tree Join C-multicast route, with the C-S contained
734 in the route's NLRI being reachable via one of the given
735 MVPN's VRF interfaces, or
736
737 * a Shared Tree Join C-multicast route, with the C-RP carried in
738 that route being reachable via one of the given MVPN's VRF
739 interfaces.
740
741 By default, the set of Route Targets carried by a (C-*,C-*) S-PMSI
742 A-D route originated from a given VRF is the same as the set of Route
743 Targets carried in the VPN-IP unicast routes originated from that
744 VRF. An implementation MUST allow the set of Route Targets carried
745 by the (C-*,C-*) S-PMSI A-D route to be specified by configuration.
746 In the absence of a configured set of Route Targets, the route MUST
747 carry the default set of Route Targets, as specified above.
748
749 If a PE needs to transmit packets of a (C-S,C-G) C-flow, and if
750 (C-S,C-G) matches a (C-*,C-*) S-PMSI A-D route according to the rules
751 of <a href="#section-3.1">Section 3.1</a>, then the PE MUST use the P-tunnel advertised in this
752 route for transmitting that C-flow. (Note that it is impossible for
753 a given (C-S,C-G) to match both a (C-*,C-*) wildcard and any other
754 wildcard.)
755
756 If PIM is being used as the PE-PE control protocol for distributing
757 C-multicast routing, and if a given PE, say PE1, needs to receive a
758 (C-S,C-G) flow, and if (C-S,C-G) matches the (C-*,C-*) S-PMSI A-D
759 route (according to the procedures of <a href="#section-3.2">Section 3.2</a>), then PE1 MUST
760 join the P-tunnel specified in the PMSI Tunnel Attribute of that
761 route.
762
763 If BGP is being used as the PE-PE control protocol for distributing
764 C-multicast routing, then if (and only if) one of the following
765 conditions holds, the PE applies the procedures of <a href="#section-12.3">Section 12.3</a>
766 ("Receiving S-PMSI A-D Routes by PEs") of [<a href="#ref-MVPN-BGP" title="&quot;BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs&quot;">MVPN-BGP</a>] to the matching
767 S-PMSI A-D route. The conditions are as follows:
768
769 - The PE has a currently originated C-multicast Source Tree Join
770 route for (C-S,C-G) that matches (according to the procedures of
771 <a href="#section-3.2">Section 3.2</a>) the (C-*,C-*) S-PMSI A-D route, or
772
773 - The PE has a currently originated a C-multicast Shared Tree Join
774 route for (C-*,C-G) that matches (according to the procedures of
775 <a href="#section-3.2">Section 3.2</a>) the (C-*,C-*) S-PMSI A-D route.
776
777
778
779
780 <span class="grey">Rosen, 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="./rfc6625">RFC 6625</a> Wildcards in MVPN A-D Routes May 2012</span>
783
784
785 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span>
786
787 There are no additional security considerations beyond those of
788 [<a href="#ref-MVPN" title="&quot;Multicast in MPLS/BGP IP VPNs&quot;">MVPN</a>] and [<a href="#ref-MVPN-BGP" title="&quot;BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs&quot;">MVPN-BGP</a>].
789
790 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Acknowledgments</span>
791
792 The authors wish to thank Arjen Boers, Dongling Duan, Apoorva Karan,
793 Thomas Morin, Keyur Patel, Karthik Subramanian, and Kurt Windisch for
794 many helpful discussions.
795
796 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Normative References</span>
797
798 [<a id="ref-BGP-MP">BGP-MP</a>] Bates, T., Chandra, R., Katz, D., and Y. Rekhter,
799 "Multiprotocol Extensions for BGP-4", <a href="./rfc4760">RFC 4760</a>,
800 January 2007.
801
802 [<a id="ref-L3VPN">L3VPN</a>] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private
803 Networks (VPNs)", <a href="./rfc4364">RFC 4364</a>, February 2006.
804
805 [<a id="ref-MVPN">MVPN</a>] Rosen, E., Ed., and R. Aggarwal, Ed., "Multicast in
806 MPLS/BGP IP VPNs", <a href="./rfc6513">RFC 6513</a>, February 2012.
807
808 [<a id="ref-MVPN-BGP">MVPN-BGP</a>] Aggarwal, R., Rosen, E., Morin, T., and Y. Rekhter, "BGP
809 Encodings and Procedures for Multicast in MPLS/BGP IP
810 VPNs", <a href="./rfc6514">RFC 6514</a>, February 2012.
811
812 [<a id="ref-PIM">PIM</a>] Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas,
813 "Protocol Independent Multicast - Sparse Mode (PIM-SM):
814 Protocol Specification (Revised)", <a href="./rfc4601">RFC 4601</a>, August 2006.
815
816 [<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
817 Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836 <span class="grey">Rosen, 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="./rfc6625">RFC 6625</a> Wildcards in MVPN A-D Routes May 2012</span>
839
840
841 Authors' Addresses
842
843 Rahul Aggarwal
844 Arktan
845
846 EMail: [email protected]
847
848
849 Yiqun Cai
850 Microsoft
851 1065 La Avenida
852 Mountain View, CA 94043
853
854 EMail: [email protected]
855
856
857 Wim Henderickx
858 Alcatel-Lucent
859
860 EMail: [email protected]
861
862
863 Praveen Muley
864 Alcatel-Lucent
865
866 EMail: [email protected]
867
868
869 Ray (Lei) Qiu
870 2330 Central Expressway
871 Santa Clara, CA 95050
872 USA
873
874 EMail: [email protected]
875
876
877 Yakov Rekhter (editor)
878 Juniper Networks
879 1194 North Mathilda Ave.
880 Sunnyvale, CA 94089
881
882 EMail: [email protected]
883
884
885
886
887
888
889
890
891
892 <span class="grey">Rosen, 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="./rfc6625">RFC 6625</a> Wildcards in MVPN A-D Routes May 2012</span>
895
896
897 Eric C. Rosen (editor)
898 Cisco Systems, Inc.
899 1414 Massachusetts Avenue
900 Boxborough, MA 01719
901
902 EMail: [email protected]
903
904
905 IJsbrand Wijnands
906 Cisco Systems, Inc.
907 De kleetlaan 6a Diegem 1831
908 Belgium
909
910 EMail: [email protected]
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948 Rosen, et al. Standards Track [Page 17]
949 </pre>