draft-ietf-bess-evpn-irb-mcast-01.txt   draft-ietf-bess-evpn-irb-mcast-02.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: January 17, 2019 E. Rosen, Ed. Expires: July 27, 2019 E. Rosen, Ed.
Juniper Networks, Inc. Juniper Networks, Inc.
J. Rabadan J. Rabadan
Nokia Nokia
A. Sajassi A. Sajassi
Cisco Systems Cisco Systems
July 16, 2018 January 23, 2019
EVPN Optimized Inter-Subnet Multicast (OISM) Forwarding EVPN Optimized Inter-Subnet Multicast (OISM) Forwarding
draft-ietf-bess-evpn-irb-mcast-01 draft-ietf-bess-evpn-irb-mcast-02
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 January 17, 2019. This Internet-Draft will expire on July 27, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 58, line 8 skipping to change at page 58, line 8
[RFC7761]. This means that the MEG SBD-DR must know the identity of [RFC7761]. This means that the MEG SBD-DR must know the identity of
the Rendezvous Point (RP) for each group, must send Register messages the Rendezvous Point (RP) for each group, must send Register messages
to the Rendezvous Point, etc. to the Rendezvous Point, etc.
If the MEG SBD-DR is to be the FHR for the Tenant Domain, it must see If the MEG SBD-DR is to be the FHR for the Tenant Domain, it must see
all the multicast traffic that is sourced from within the domain and all the multicast traffic that is sourced from within the domain and
destined to an ASM group address. The MEG can ensure this by destined to an ASM group address. The MEG can ensure this by
originating an SBD-SMET route for (*,*). originating an SBD-SMET route for (*,*).
(As a possible optimization, an SBD-SMET route for (*, "any ASM (As a possible optimization, an SBD-SMET route for (*, "any ASM
group"), or even (*, "any ASM group that might have MVPN sources") group") may be defined in a future revision of this draft.)
may be defined in a future revision of this draft.)
In some deployment scenarios, it may be preferred that the MEG that In some deployment scenarios, it may be preferred that the MEG that
receives the (S,G) traffic over an AC be the one provides the FHR receives the (S,G) traffic over an AC be the one provides the FHR
functionality. This behavior is OPTIONAL. If this option is used, functionality. This behavior is OPTIONAL. If this option is used,
it MUST be ensured that the MEG DR does not provide the FHR it MUST be ensured that the MEG DR does not provide the FHR
functionality for (S,G) traffic that is attached to another MEG; FHR functionality for (S,G) traffic that is attached to another MEG; FHR
functionality for (S,G) traffic from a particular source S MUST be functionality for (S,G) traffic from a particular source S MUST be
provided by only a single router. provided by only a single router.
Other deployment scenarios are also possible. For example, one might Other deployment scenarios are also possible. For example, one might
skipping to change at page 67, line 33 skipping to change at page 67, line 33
discussions with Aldrin Isaac on EVPN multicast optimizations. discussions with Aldrin Isaac on EVPN multicast optimizations.
11. References 11. References
11.1. Normative References 11.1. Normative References
[DF-Election-Framework] [DF-Election-Framework]
Rabadan, J., Mohanty, S., Sajassi, A., Drake, J., Nagaraj, Rabadan, J., Mohanty, S., Sajassi, A., Drake, J., Nagaraj,
K., and S. Sathappan, "Framework for EVPN Designated K., and S. Sathappan, "Framework for EVPN Designated
Forwarder Election Extensibility", internet-draft draft- Forwarder Election Extensibility", internet-draft draft-
ietf-bess-evpn-df-election-framework-03.txt, May 2018. ietf-bess-evpn-df-election-framework-07.txt, December
2018.
[EVPN-AR] Rabadan, J., Ed., "Optimized Ingress Replication solution [EVPN-AR] Rabadan, J., Ed., "Optimized Ingress Replication solution
for EVPN", internet-draft ietf-bess-evpn-optimized-ir- for EVPN", internet-draft ietf-bess-evpn-optimized-ir-
03.txt, Febryary 2018. 06.txt, October 2018.
[EVPN-BUM] [EVPN-BUM]
Zhang, Z., Lin, W., Rabadan, J., and K. Patel, "Updates on Zhang, Z., Lin, W., Rabadan, J., and K. Patel, "Updates on
EVPN BUM Procedures", internet-draft ietf-bess-evpn-bum- EVPN BUM Procedures", internet-draft ietf-bess-evpn-bum-
procedure-updates-03.txt, April 2018. procedure-updates-05.txt, December 2018.
[EVPN-IRB] [EVPN-IRB]
Sajassi, A., Salam, S., Thoria, S., Drake, J., and J. Sajassi, A., Salam, S., Thoria, S., Drake, J., and J.
Rabadan, "Integrated Routing and Bridging in EVPN", Rabadan, "Integrated Routing and Bridging in EVPN",
internet-draft draft-ietf-bess-evpn-inter-subnet- internet-draft draft-ietf-bess-evpn-inter-subnet-
forwarding-04.txt, July 2018. forwarding-05.txt, July 2018.
[EVPN_IP_Prefix] [EVPN_IP_Prefix]
Rabadan, J., Henderickx, W., Drake, J., Lin, W., and A. Rabadan, J., Henderickx, W., Drake, J., Lin, W., and A.
Sajassi, "IP Prefix Advertisement in EVPN", internet- Sajassi, "IP Prefix Advertisement in EVPN", internet-
draft ietf-bess-evpn-prefix-advertisement-11.txt, May draft ietf-bess-evpn-prefix-advertisement-11.txt, May
2018. 2018.
[IGMP-Proxy] [IGMP-Proxy]
Sajassi, A., Thoria, S., Patel, K., Yeung, D., Drake, J., Sajassi, A., Thoria, S., Patel, K., Yeung, D., Drake, J.,
and W. Lin, "IGMP and MLD Proxy for EVPN", internet-draft and W. Lin, "IGMP and MLD Proxy for EVPN", internet-draft
skipping to change at page 69, line 20 skipping to change at page 69, line 20
[EVPN-BIER] [EVPN-BIER]
Zhang, Z., Przygienda, T., Sajassi, A., and J. Rabadan, Zhang, Z., Przygienda, T., Sajassi, A., and J. Rabadan,
"EVPN BUM Using BIER", internet-draft ietf-bier-evpn- "EVPN BUM Using BIER", internet-draft ietf-bier-evpn-
01.txt, April 2018. 01.txt, April 2018.
[EVPN-DF-WEIGHTED] [EVPN-DF-WEIGHTED]
Rabadan, J., Sathappan, S., Przygienda, T., Lin, W., Rabadan, J., Sathappan, S., Przygienda, T., Lin, W.,
Drake, J., Sajassi, A., and S. Mohanty, "Preference-based Drake, J., Sajassi, A., and S. Mohanty, "Preference-based
EVPN DF Election", internet-draft ietf-bess-evpn-pref-df- EVPN DF Election", internet-draft ietf-bess-evpn-pref-df-
01.txt, April 2018. 03.txt, December 2018.
[RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private [RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private
Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364, February Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364, February
2006, <https://www.rfc-editor.org/info/rfc4364>. 2006, <https://www.rfc-editor.org/info/rfc4364>.
[RFC6513] Rosen, E., Ed. and R. Aggarwal, Ed., "Multicast in MPLS/ [RFC6513] Rosen, E., Ed. and R. Aggarwal, Ed., "Multicast in MPLS/
BGP IP VPNs", RFC 6513, DOI 10.17487/RFC6513, February BGP IP VPNs", RFC 6513, DOI 10.17487/RFC6513, February
2012, <https://www.rfc-editor.org/info/rfc6513>. 2012, <https://www.rfc-editor.org/info/rfc6513>.
[RFC6514] Aggarwal, R., Rosen, E., Morin, T., and Y. Rekhter, "BGP [RFC6514] Aggarwal, R., Rosen, E., Morin, T., and Y. Rekhter, "BGP
skipping to change at page 76, line 18 skipping to change at page 76, line 18
Please be aware that his document modifies the semantics, described Please be aware that his document modifies the semantics, described
in the previous paragraph, of sending/receiving multicast traffic on in the previous paragraph, of sending/receiving multicast traffic on
an IRB interface. This is explained in Section 1.5.1 and subsequent an IRB interface. This is explained in Section 1.5.1 and subsequent
sections. sections.
Authors' Addresses Authors' Addresses
Wen Lin Wen Lin
Juniper Networks, Inc. Juniper Networks, Inc.
10 Technology Park Drive
Westford, Massachusetts 01886
United States
EMail: wlin@juniper.net EMail: wlin@juniper.net
Zhaohui Zhang Zhaohui Zhang
Juniper Networks, Inc. Juniper Networks, Inc.
10 Technology Park Drive
Westford, Massachusetts 01886
United States
EMail: zzhang@juniper.net EMail: zzhang@juniper.net
John Drake John Drake
Juniper Networks, Inc. Juniper Networks, Inc.
1194 N. Mathilda Ave
Sunnyvale, CA 94089
United States
EMail: jdrake@juniper.net EMail: jdrake@juniper.net
Eric C. Rosen (editor) Eric C. Rosen (editor)
Juniper Networks, Inc. Juniper Networks, Inc.
10 Technology Park Drive
Westford, Massachusetts 01886
United States
EMail: erosen@juniper.net EMail: erosen52@gmail.com
Jorge Rabadan Jorge Rabadan
Nokia Nokia
777 E. Middlefield Road
Mountain View, CA 94043
United States
EMail: jorge.rabadan@nokia.com EMail: jorge.rabadan@nokia.com
Ali Sajassi Ali Sajassi
Cisco Systems Cisco Systems
170 West Tasman Drive
San Jose, CA 95134
United States
EMail: sajassi@cisco.com EMail: sajassi@cisco.com
 End of changes. 18 change blocks. 
14 lines changed or deleted 31 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/