draft-ietf-bess-evpn-vpls-seamless-integ-00.txt   draft-ietf-bess-evpn-vpls-seamless-integ-01.txt 
skipping to change at page 1, line 13 skipping to change at page 1, line 13
INTERNET-DRAFT Ali Sajassi INTERNET-DRAFT Ali Sajassi
Intended Status: Standard Track Samer Salam Intended Status: Standard Track Samer Salam
Cisco Cisco
Nick Del Regno Nick Del Regno
Verizon Verizon
Jorge Rabadan Jorge Rabadan
Alcatel-Lucent Alcatel-Lucent
Expires: August 20, 2015 February 20, 2015 Expires: August 15, 2018 February 15, 2018
(PBB-)EVPN Seamless Integration with (PBB-)VPLS (PBB-)EVPN Seamless Integration with (PBB-)VPLS
draft-ietf-bess-evpn-vpls-seamless-integ-00 draft-ietf-bess-evpn-vpls-seamless-integ-01
Abstract Abstract
This draft discusses the backward compatibility of the (PBB-)EVPN This draft discusses the backward compatibility of the (PBB-)EVPN
solution with (PBB-)VPLS and provides mechanisms for seamless solution with (PBB-)VPLS and provides mechanisms for seamless
integration of the two technologies in the same MPLS/IP network on a integration of the two technologies in the same MPLS/IP network on a
per-VPN-instance basis. per-VPN-instance basis.
Status of this Memo Status of this Memo
skipping to change at page 2, line 4 skipping to change at page 2, line 4
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/1id-abstracts.html http://www.ietf.org/1id-abstracts.html
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
Copyright and License Notice Copyright and License Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2018 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
(http://trustee.ietf.org/license-info) in effect on the date of (http://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 5, line 34 skipping to change at page 5, line 34
they were standard (PBB-)VPLS nodes. In other words, when the they were standard (PBB-)VPLS nodes. In other words, when the
discovery phase is complete, the (PBB-)EVPN PEs would have discovered discovery phase is complete, the (PBB-)EVPN PEs would have discovered
all the PEs in the VPN instance, and their associated capability: all the PEs in the VPN instance, and their associated capability:
(PBB-)EVPN or VPLS-only. Whereas the (PBB-)VPLS PEs would have (PBB-)EVPN or VPLS-only. Whereas the (PBB-)VPLS PEs would have
discovered all the PEs in the VPN instance, as if they were all VPLS- discovered all the PEs in the VPN instance, as if they were all VPLS-
only nodes. only nodes.
3.2 Forwarding Setup and Unicast Operation 3.2 Forwarding Setup and Unicast Operation
The procedures for forwarding setup and unicast operation on the The procedures for forwarding setup and unicast operation on the
(PBB-)VPLS PE are per [RFC4447] and [RFC7080]. (PBB-)VPLS PE are per [RFC8077] and [RFC7080].
The procedures for forwarding state setup and unicast operation on The procedures for forwarding state setup and unicast operation on
the (PBB-)EVPN PE are as follows: the (PBB-)EVPN PE are as follows:
- The (PBB-)EVPN PE must establish a pseudowire to a remote PE from - The (PBB-)EVPN PE must establish a pseudowire to a remote PE from
which it has received only a VPLS AD route, for the VPN instance in which it has received only a VPLS AD route, for the VPN instance in
question, and set up the label stack corresponding to the pseudowire question, and set up the label stack corresponding to the pseudowire
FEC. This PW is between B-components of PBB-EVPN PE and PBB-VPLS PE FEC. This PW is between B-components of PBB-EVPN PE and PBB-VPLS PE
per section 4 of [RFC7041]. per section 4 of [RFC7041].
skipping to change at page 6, line 39 skipping to change at page 6, line 39
3.3.1 Ingress Replication The procedures for multicast operation on the 3.3.1 Ingress Replication The procedures for multicast operation on the
(PBB-)VPLS PE, using ingress replication, are per [RFC4761], (PBB-)VPLS PE, using ingress replication, are per [RFC4761],
[RFC4762], and [RFC7080]. [RFC4762], and [RFC7080].
The procedures for multicast operation on the PBB-EVPN PE, for The procedures for multicast operation on the PBB-EVPN PE, for
ingress replication, are as follows: ingress replication, are as follows:
- The PBB-EVPN PE builds a replication sub-list per I-SID to all the - The PBB-EVPN PE builds a replication sub-list per I-SID to all the
remote PBB-EVPN PEs in a given VPN instance, as a result of the remote PBB-EVPN PEs in a given VPN instance, as a result of the
exchange of the EVPN Inclusive multicast routes, as described in exchange of the EVPN Inclusive multicast routes, as described in
[PBB-EVPN]. This will be referred to as sub-list A. It comprises MP2P [RFC7623]. This will be referred to as sub-list A. It comprises MP2P
tunnels used for delivering PBB-EVPN BUM traffic [EVPN]. tunnels used for delivering PBB-EVPN BUM traffic [RFC7432].
- The PBB-EVPN PE builds a replication sub-list per VPN instance to - The PBB-EVPN PE builds a replication sub-list per VPN instance to
all the remote PBB-VPLS PEs , as a result of the exchange of the VPLS all the remote PBB-VPLS PEs , as a result of the exchange of the VPLS
AD routes. This will be referred to as sub-list B. It comprises AD routes. This will be referred to as sub-list B. It comprises
pseudowires from the PBB-EVPN PE in question to all the remote PBB- pseudowires from the PBB-EVPN PE in question to all the remote PBB-
VPLS PEs in the same VPN instance. VPLS PEs in the same VPN instance.
- The PBB-EVPN PE may further prune sub-list B, on a per I-SID basis, - The PBB-EVPN PE may further prune sub-list B, on a per I-SID basis,
if [MMRP] is run over the PBB-VPLS network. This will be referred to if [MMRP] is run over the PBB-VPLS network. This will be referred to
as sub-list C. This list comprises a pruned set of the pseudowires in as sub-list C. This list comprises a pruned set of the pseudowires in
skipping to change at page 9, line 6 skipping to change at page 9, line 6
This document has no actions for IANA. This document has no actions for IANA.
9 References 9 References
9.1 Normative References 9.1 Normative References
[KEYWORDS] Bradner, S., "Key words for use in RFCs to Indicate [KEYWORDS] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC4448] Martini, L., Ed., Rosen, E., El-Aawar, N., and G. Heron, [RFC8077] Martini, et al., "Pseudowire Setup and Maintenance using
"Encapsulation Methods for Transport of Ethernet over MPLS the Label Distribution Protocol", RFC 8077, February 2017.
Networks", RFC 4448, April 2006.
[RFC4447] Martini, et al., "Pseudowire Setup and Maintenance using
the Label Distribution Protocol", draft-ietf-pwe3-
rfc4447bis-02.txt, October 2013.
[RFC7432] Sajassi et al., "BGP MPLS Based Ethernet VPN", RFC 7432, [RFC7432] Sajassi et al., "BGP MPLS Based Ethernet VPN", RFC 7432,
February, 2015. February, 2015.
[PBB-EVPN] Sajassi et al., "PBB-EVPN", draft-ietf-l2vpn-pbb-evpn- [RFC7623] Sajassi et al., "Provider Backbone Bridging Combined with
09.txt, work in progress, October, 2014. Ethernet VPN (PBB-EVPN)", RFC 7623, September, 2015.
[RFC4761] Kompella, K., Ed., and Y. Rekhter, Ed., "Virtual Private
LAN Service (VPLS) Using BGP for Auto-Discovery and
Signaling", RFC 4761, January 2007, <http://www.rfc-
editor.org/info/rfc4761>.
[RFC4762] Lasserre, M., Ed., and V. Kompella, Ed., "Virtual Private
LAN Service (VPLS) Using Label Distribution Protocol (LDP)
Signaling", RFC 4762, January 2007, <http://www.rfc-
editor.org/info/rfc4762>.
[RFC6074] Rosen et al., "Provisioning, Auto-Discovery, and Signaling
in Layer 2 Virtual Private Networks (L2VPNs)", RFC 6074,
January 2011.
9.2 Informative References 9.2 Informative References
[MMRP] Clause 10 of "IEEE Standard for Local and metropolitan area [MMRP] Clause 10 of "IEEE Standard for Local and metropolitan area
networks - Media Access Control (MAC) Bridges and Virtual Bridged networks - Media Access Control (MAC) Bridges and Virtual Bridged
Local Area Networks", IEEE Std 802.1Q, 2013. Local Area Networks", IEEE Std 802.1Q, 2013.
[RFC7041] Balus et al., "Extensions to VPLS PE model for Provider [RFC7041] Balus et al., "Extensions to VPLS PE model for Provider
Backbone Bridging", RFC 7041, November 2013. Backbone Bridging", RFC 7041, November 2013.
skipping to change at page 9, line 37 skipping to change at page 10, line 4
Backbone Bridging", RFC 7041, November 2013. Backbone Bridging", RFC 7041, November 2013.
[RFC7080] Sajassi et al., "VPLS Interoperability with Provider [RFC7080] Sajassi et al., "VPLS Interoperability with Provider
Backbone Bridges", RFC 7080, December, 2013. Backbone Bridges", RFC 7080, December, 2013.
Authors' Addresses Authors' Addresses
Ali Sajassi Ali Sajassi
Cisco Cisco
Email: sajassi@cisco.com Email: sajassi@cisco.com
Samer Salam Samer Salam
Cisco Cisco
595 Burrard Street, Suite 2123
Vancouver, BC V7X 1J1, Canada
Email: ssalam@cisco.com Email: ssalam@cisco.com
Nick Del Regno Nick Del Regno
Verizon Verizon
400 International Pkwy
Richardson, TX 75089, US
Email: nick.delregno@verizon.com Email: nick.delregno@verizon.com
Jorge Rabadan Jorge Rabadan
Alcatel-Lucent Nokia
400 International Pkwy Email: jorge.rabadan@nokia.com
Richardson, TX 75089, US
Email: jorge.rabadan@alcatel-lucent.com
 End of changes. 11 change blocks. 
20 lines changed or deleted 24 lines changed or added

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