draft-ietf-bess-evpn-irb-mcast-02.txt   draft-ietf-bess-evpn-irb-mcast-03.txt 
BESS W. Lin BESS W. Lin
Internet-Draft Z. Zhang Internet-Draft Z. Zhang
Intended status: Standards Track J. Drake Intended status: Standards Track J. Drake
Expires: July 27, 2019 E. Rosen, Ed. Expires: February 17, 2020 E. Rosen, Ed.
Juniper Networks, Inc. Juniper Networks, Inc.
J. Rabadan J. Rabadan
Nokia Nokia
A. Sajassi A. Sajassi
Cisco Systems Cisco Systems
January 23, 2019 August 16, 2019
EVPN Optimized Inter-Subnet Multicast (OISM) Forwarding EVPN Optimized Inter-Subnet Multicast (OISM) Forwarding
draft-ietf-bess-evpn-irb-mcast-02 draft-ietf-bess-evpn-irb-mcast-03
Abstract Abstract
Ethernet VPN (EVPN) provides a service that allows a single Local Ethernet VPN (EVPN) provides a service that allows a single Local
Area Network (LAN), comprising a single IP subnet, to be divided into Area Network (LAN), comprising a single IP subnet, to be divided into
multiple "segments". Each segment may be located at a different multiple "segments". Each segment may be located at a different
site, and the segments are interconnected by an IP or MPLS backbone. site, and the segments are interconnected by an IP or MPLS backbone.
Intra-subnet traffic (either unicast or multicast) always appears to Intra-subnet traffic (either unicast or multicast) always appears to
the endusers to be bridged, even when it is actually carried over the the endusers to be bridged, even when it is actually carried over the
IP or MPLS backbone. When a single "tenant" owns multiple such LANs, IP or MPLS backbone. When a single "tenant" owns multiple such LANs,
skipping to change at page 2, line 4 skipping to change at page 2, line 4
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 27, 2019. This Internet-Draft will expire on February 17, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 46 skipping to change at page 2, line 46
2.1. Supplementary Broadcast Domain . . . . . . . . . . . . . 17 2.1. Supplementary Broadcast Domain . . . . . . . . . . . . . 17
2.2. Detecting When a Route is About/For/From a Particular BD 18 2.2. Detecting When a Route is About/For/From a Particular BD 18
2.3. Use of IRB Interfaces at Ingress PE . . . . . . . . . . . 21 2.3. Use of IRB Interfaces at Ingress PE . . . . . . . . . . . 21
2.4. Use of IRB Interfaces at an Egress PE . . . . . . . . . . 23 2.4. Use of IRB Interfaces at an Egress PE . . . . . . . . . . 23
2.5. Announcing Interest in (S,G) . . . . . . . . . . . . . . 23 2.5. Announcing Interest in (S,G) . . . . . . . . . . . . . . 23
2.6. Tunneling Frames from Ingress PE to Egress PEs . . . . . 24 2.6. Tunneling Frames from Ingress PE to Egress PEs . . . . . 24
2.7. Advanced Scenarios . . . . . . . . . . . . . . . . . . . 25 2.7. Advanced Scenarios . . . . . . . . . . . . . . . . . . . 25
3. EVPN-aware Multicast Solution Control Plane . . . . . . . . . 26 3. EVPN-aware Multicast Solution Control Plane . . . . . . . . . 26
3.1. Supplementary Broadcast Domain (SBD) and Route Targets . 26 3.1. Supplementary Broadcast Domain (SBD) and Route Targets . 26
3.2. Advertising the Tunnels Used for IP Multicast . . . . . . 27 3.2. Advertising the Tunnels Used for IP Multicast . . . . . . 27
3.2.1. Constructing Routes for the SBD . . . . . . . . . . . 27 3.2.1. Constructing Routes for the SBD . . . . . . . . . . . 28
3.2.2. Ingress Replication . . . . . . . . . . . . . . . . . 28 3.2.2. Ingress Replication . . . . . . . . . . . . . . . . . 28
3.2.3. Assisted Replication . . . . . . . . . . . . . . . . 29 3.2.3. Assisted Replication . . . . . . . . . . . . . . . . 29
3.2.4. BIER . . . . . . . . . . . . . . . . . . . . . . . . 29 3.2.4. BIER . . . . . . . . . . . . . . . . . . . . . . . . 30
3.2.5. Inclusive P2MP Tunnels . . . . . . . . . . . . . . . 31 3.2.5. Inclusive P2MP Tunnels . . . . . . . . . . . . . . . 31
3.2.5.1. Using the BUM Tunnels as IP Multicast Inclusive 3.2.5.1. Using the BUM Tunnels as IP Multicast Inclusive
Tunnels . . . . . . . . . . . . . . . . . . . . . 31 Tunnels . . . . . . . . . . . . . . . . . . . . . 31
3.2.5.2. Using Wildcard S-PMSI A-D Routes to Advertise 3.2.5.2. Using Wildcard S-PMSI A-D Routes to Advertise
Inclusive Tunnels Specific to IP Multicast . . . 32 Inclusive Tunnels Specific to IP Multicast . . . 32
3.2.6. Selective Tunnels . . . . . . . . . . . . . . . . . . 33 3.2.6. Selective Tunnels . . . . . . . . . . . . . . . . . . 33
3.3. Advertising SMET Routes . . . . . . . . . . . . . . . . . 34 3.3. Advertising SMET Routes . . . . . . . . . . . . . . . . . 34
4. Constructing Multicast Forwarding State . . . . . . . . . . . 36 4. Constructing Multicast Forwarding State . . . . . . . . . . . 36
4.1. Layer 2 Multicast State . . . . . . . . . . . . . . . . . 36 4.1. Layer 2 Multicast State . . . . . . . . . . . . . . . . . 36
4.1.1. Constructing the OIF List . . . . . . . . . . . . . . 37 4.1.1. Constructing the OIF List . . . . . . . . . . . . . . 37
4.1.2. Data Plane: Applying the OIF List to an (S,G) Frame . 38 4.1.2. Data Plane: Applying the OIF List to an (S,G) Frame . 38
4.1.2.1. Eligibility of an AC to Receive a Frame . . . . . 38 4.1.2.1. Eligibility of an AC to Receive a Frame . . . . . 38
4.1.2.2. Applying the OIF List . . . . . . . . . . . . . . 38 4.1.2.2. Applying the OIF List . . . . . . . . . . . . . . 39
4.2. Layer 3 Forwarding State . . . . . . . . . . . . . . . . 40 4.2. Layer 3 Forwarding State . . . . . . . . . . . . . . . . 40
5. Interworking with non-OISM EVPN-PEs . . . . . . . . . . . . . 41 5. Interworking with non-OISM EVPN-PEs . . . . . . . . . . . . . 41
5.1. IPMG Designated Forwarder . . . . . . . . . . . . . . . . 43 5.1. IPMG Designated Forwarder . . . . . . . . . . . . . . . . 43
5.2. Ingress Replication . . . . . . . . . . . . . . . . . . . 44 5.2. Ingress Replication . . . . . . . . . . . . . . . . . . . 44
5.2.1. Ingress PE is non-OISM . . . . . . . . . . . . . . . 45 5.2.1. Ingress PE is non-OISM . . . . . . . . . . . . . . . 45
5.2.2. Ingress PE is OISM . . . . . . . . . . . . . . . . . 47 5.2.2. Ingress PE is OISM . . . . . . . . . . . . . . . . . 47
5.3. P2MP Tunnels . . . . . . . . . . . . . . . . . . . . . . 48 5.3. P2MP Tunnels . . . . . . . . . . . . . . . . . . . . . . 48
6. Traffic to/from Outside the EVPN Tenant Domain . . . . . . . 48 6. Traffic to/from Outside the EVPN Tenant Domain . . . . . . . 48
6.1. Layer 3 Interworking via EVPN OISM PEs . . . . . . . . . 48 6.1. Layer 3 Interworking via EVPN OISM PEs . . . . . . . . . 49
6.1.1. General Principles . . . . . . . . . . . . . . . . . 48 6.1.1. General Principles . . . . . . . . . . . . . . . . . 49
6.1.2. Interworking with MVPN . . . . . . . . . . . . . . . 51 6.1.2. Interworking with MVPN . . . . . . . . . . . . . . . 52
6.1.2.1. MVPN Sources with EVPN Receivers . . . . . . . . 53 6.1.2.1. MVPN Sources with EVPN Receivers . . . . . . . . 53
6.1.2.1.1. Identifying MVPN Sources . . . . . . . . . . 53 6.1.2.1.1. Identifying MVPN Sources . . . . . . . . . . 53
6.1.2.1.2. Joining a Flow from an MVPN Source . . . . . 54 6.1.2.1.2. Joining a Flow from an MVPN Source . . . . . 54
6.1.2.2. EVPN Sources with MVPN Receivers . . . . . . . . 56 6.1.2.2. EVPN Sources with MVPN Receivers . . . . . . . . 56
6.1.2.2.1. General procedures . . . . . . . . . . . . . 56 6.1.2.2.1. General procedures . . . . . . . . . . . . . 56
6.1.2.2.2. Any-Source Multicast (ASM) Groups . . . . . . 57 6.1.2.2.2. Any-Source Multicast (ASM) Groups . . . . . . 58
6.1.2.2.3. Source on Multihomed Segment . . . . . . . . 58 6.1.2.2.3. Source on Multihomed Segment . . . . . . . . 58
6.1.2.3. Obtaining Optimal Routing of Traffic Between MVPN 6.1.2.3. Obtaining Optimal Routing of Traffic Between MVPN
and EVPN . . . . . . . . . . . . . . . . . . . . 59 and EVPN . . . . . . . . . . . . . . . . . . . . 59
6.1.2.4. Selecting the MEG SBD-DR . . . . . . . . . . . . 59 6.1.2.4. Selecting the MEG SBD-DR . . . . . . . . . . . . 60
6.1.3. Interworking with 'Global Table Multicast' . . . . . 60 6.1.3. Interworking with 'Global Table Multicast' . . . . . 60
6.1.4. Interworking with PIM . . . . . . . . . . . . . . . . 60 6.1.4. Interworking with PIM . . . . . . . . . . . . . . . . 60
6.1.4.1. Source Inside EVPN Domain . . . . . . . . . . . . 61 6.1.4.1. Source Inside EVPN Domain . . . . . . . . . . . . 61
6.1.4.2. Source Outside EVPN Domain . . . . . . . . . . . 62 6.1.4.2. Source Outside EVPN Domain . . . . . . . . . . . 62
6.2. Interworking with PIM via an External PIM Router . . . . 63 6.2. Interworking with PIM via an External PIM Router . . . . 63
7. Using an EVPN Tenant Domain as an Intermediate (Transit) 7. Using an EVPN Tenant Domain as an Intermediate (Transit)
Network for Multicast traffic . . . . . . . . . . . . . . . . 64 Network for Multicast traffic . . . . . . . . . . . . . . . . 64
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 66 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 67
9. Security Considerations . . . . . . . . . . . . . . . . . . . 67 9. Security Considerations . . . . . . . . . . . . . . . . . . . 67
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 67 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 67
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 67 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 67
11.1. Normative References . . . . . . . . . . . . . . . . . . 67 11.1. Normative References . . . . . . . . . . . . . . . . . . 67
11.2. Informative References . . . . . . . . . . . . . . . . . 69 11.2. Informative References . . . . . . . . . . . . . . . . . 69
Appendix A. Integrated Routing and Bridging . . . . . . . . . . 71 Appendix A. Integrated Routing and Bridging . . . . . . . . . . 71
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 76 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 76
1. Introduction 1. Introduction
skipping to change at page 19, line 33 skipping to change at page 19, line 33
* the route MUST NOT carry any RT that is associated with an * the route MUST NOT carry any RT that is associated with an
ordinary BD other than BD1. ordinary BD other than BD1.
o If the route is about the SBD, the route MUST carry the SBD-RT, o If the route is about the SBD, the route MUST carry the SBD-RT,
and MUST NOT carry any RT that is associated with any other BD. and MUST NOT carry any RT that is associated with any other BD.
o As detailed in subsequent sections, under certain circumstances a o As detailed in subsequent sections, under certain circumstances a
route that is about BD1 may carry both the RT of BD1 and also the route that is about BD1 may carry both the RT of BD1 and also the
SBD-RT. SBD-RT.
The IMET route for the SBD MUST carry an Multicast Flags Extended
Community, in which an "OISM SBD" flag is set.
When receiving an IMET, SMET, S-PMSI or Leaf route, it is necessary When receiving an IMET, SMET, S-PMSI or Leaf route, it is necessary
for the receiving PE to determine the BD to which the route belongs. for the receiving PE to determine the BD to which the route belongs.
This is done by examining the RTs carried by the route, as well as This is done by examining the RTs carried by the route, as well as
the Tag ID field of the route's NLRI. There are several cases to the Tag ID field of the route's NLRI. There are several cases to
consider. Some of these cases are error cases that arise when the consider. Some of these cases are error cases that arise when the
route has not been properly constructed. route has not been properly constructed.
When one of the error cases is detected, the route MUST be regarded When one of the error cases is detected, the route MUST be regarded
as a malformed route, and the "treat-as-withdraw" procedure of as a malformed route, and the "treat-as-withdraw" procedure of
[RFC7606] MUST be applied. Note though that these error cases are [RFC7606] MUST be applied. Note though that these error cases are
skipping to change at page 67, line 5 skipping to change at page 67, line 16
IANA is requested to assign new flags in the "Multicast Flags IANA is requested to assign new flags in the "Multicast Flags
Extended Community Flags" registry. These flags are: Extended Community Flags" registry. These flags are:
o IPMG o IPMG
o MEG o MEG
o PEG o PEG
o OISM SBD
o OISM-supported
9. Security Considerations 9. Security Considerations
This document uses protocols and procedures defined in the normative This document uses protocols and procedures defined in the normative
references, and inherits the security considerations of those references, and inherits the security considerations of those
references. references.
This document adds flags or Extended Communities (ECs) to a number of This document adds flags or Extended Communities (ECs) to a number of
BGP routes, in order to signal that particular nodes support the BGP routes, in order to signal that particular nodes support the
OISM, IPMG, MEG, and/or PEG functionalities that are defined in this OISM, IPMG, MEG, and/or PEG functionalities that are defined in this
document. Incorrect addition, removal, or modification of those document. Incorrect addition, removal, or modification of those
 End of changes. 13 change blocks. 
13 lines changed or deleted 20 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/