< draft-snr-bess-pbb-evpn-isid-cmacflush-05.txt   draft-snr-bess-pbb-evpn-isid-cmacflush-06.txt >
BESS Workgroup J. Rabadan, Ed. BESS Workgroup J. Rabadan, Ed.
Internet Draft S. Sathappan Internet Draft S. Sathappan
Intended status: Standards Track K. Nagaraj Intended status: Standards Track K. Nagaraj
Nokia Nokia
M. Miyake M. Miyake
T. Matsuda T. Matsuda
Softbank Softbank
Expires: July 26, 2019 January 22, 2019 Expires: January 27, 2020 July 26, 2019
PBB-EVPN ISID-based CMAC-Flush PBB-EVPN ISID-based CMAC-Flush
draft-snr-bess-pbb-evpn-isid-cmacflush-05 draft-snr-bess-pbb-evpn-isid-cmacflush-06
Abstract Abstract
Provider Backbone Bridging (PBB) can be combined with Ethernet VPN Provider Backbone Bridging (PBB) can be combined with Ethernet VPN
(EVPN) to deploy ELAN services in very large MPLS networks (PBB- (EVPN) to deploy ELAN services in very large MPLS networks (PBB-
EVPN). Single-Active Multi-homing and per-ISID Load-Balancing can be EVPN). Single-Active Multi-homing and per-ISID Load-Balancing can be
provided to access devices and aggregation networks. In order to provided to access devices and aggregation networks. In order to
speed up the network convergence in case of failures on Single-Active speed up the network convergence in case of failures on Single-Active
Multi-Homed Ethernet Segments, PBB-EVPN defines a CMAC-Flush Multi-Homed Ethernet Segments, PBB-EVPN defines a CMAC-Flush
mechanism that works for different Ethernet Segment BMAC address mechanism that works for different Ethernet Segment BMAC address
skipping to change at page 2, line 7 skipping to change at page 2, line 7
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
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
This Internet-Draft will expire on July 26, 2019. This Internet-Draft will expire on January 27, 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
(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
skipping to change at page 2, line 40 skipping to change at page 2, line 40
4.1 ISID-based CMAC-Flush activation procedures . . . . . . . . 7 4.1 ISID-based CMAC-Flush activation procedures . . . . . . . . 7
4.2 CMAC-Flush generation . . . . . . . . . . . . . . . . . . . 7 4.2 CMAC-Flush generation . . . . . . . . . . . . . . . . . . . 7
4.3 CMAC-Flush process upon receiving a CMAC-Flush 4.3 CMAC-Flush process upon receiving a CMAC-Flush
notification . . . . . . . . . . . . . . . . . . . . . . . . 8 notification . . . . . . . . . . . . . . . . . . . . . . . . 8
5. Conclusions . . . . . . . . . . . . . . . . . . . . . . . . . . 8 5. Conclusions . . . . . . . . . . . . . . . . . . . . . . . . . . 8
6. Conventions used in this document . . . . . . . . . . . . . . . 9 6. Conventions used in this document . . . . . . . . . . . . . . . 9
7. Security Considerations . . . . . . . . . . . . . . . . . . . . 9 7. Security Considerations . . . . . . . . . . . . . . . . . . . . 9
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 9 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 9
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9
9.1 Normative References . . . . . . . . . . . . . . . . . . . . 9 9.1 Normative References . . . . . . . . . . . . . . . . . . . . 9
9.2 Informative References . . . . . . . . . . . . . . . . . . . 9 9.2 Informative References . . . . . . . . . . . . . . . . . . . 10
10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 9 10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10
11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 9 11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 10
17. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 10 17. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 10
1. Problem Statement 1. Problem Statement
[RFC7623] defines how Provider Backbone Bridging (PBB) can be [RFC7623] defines how Provider Backbone Bridging (PBB) can be
combined with Ethernet VPN (EVPN) to deploy ELAN services in very combined with Ethernet VPN (EVPN) to deploy ELAN services in very
large MPLS networks. [RFC7623] also describes how Single-Active large MPLS networks. [RFC7623] also describes how Single-Active
Multi-homing and per-ISID Load-Balancing can be provided to access Multi-homing and per-ISID Load-Balancing can be provided to access
devices and aggregation networks. When Access Ethernet/MPLS Networks devices and aggregation networks. When Access Ethernet/MPLS Networks
exists, [vES] describes how virtual ES can be associated to a group exists, [vES] describes how virtual ES can be associated to a group
skipping to change at page 9, line 15 skipping to change at page 9, line 15
6. Conventions used in this document 6. Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in "OPTIONAL" in this document are to be interpreted as described in
BCP14 [RFC2119] [RFC8174] when, and only when, they appear in all BCP14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
7. Security Considerations 7. Security Considerations
This section will be added in future versions. Security considerations described in [RFC7623] apply to this
document. In addition, this document suggests additional procedures,
that can be activated on a per ISID basis, and generate additional
BGP EVPN MAC/IP advertisements in the network. The format of these
additional MAC/IP routes is backwards compatible with [RFC7623]
procedures and should not create any issues on receiving PEs not
following this specification, however, the additional routes may
consume extra memory resources on the receiving systems. Because of
that, this feature should be activated only when necessary, and not
by default in any PBB-EVPN PE.
8. IANA Considerations 8. IANA Considerations
9. References 9. References
9.1 Normative References 9.1 Normative References
[RFC7623] Sajassi, A., Ed., Salam, S., Bitar, N., Isaac, A., and W. [RFC7623] Sajassi, A., Ed., Salam, S., Bitar, N., Isaac, A., and W.
Henderickx, "Provider Backbone Bridging Combined with Ethernet VPN Henderickx, "Provider Backbone Bridging Combined with Ethernet VPN
(PBB-EVPN)", RFC 7623, DOI 10.17487/RFC7623, September 2015, (PBB-EVPN)", RFC 7623, DOI 10.17487/RFC7623, September 2015,
<https://www.rfc-editor.org/info/rfc7623>. <https://www.rfc-editor.org/info/rfc7623>.
[RFC7432] Sajassi, A., Ed., Aggarwal, R., Bitar, N., Isaac, A., [RFC7432] Sajassi, A., Ed., Aggarwal, R., Bitar, N., Isaac, A.,
Uttaro, J., Drake, J., and W. Henderickx, "BGP MPLS-Based Ethernet Uttaro, J., Drake, J., and W. Henderickx, "BGP MPLS-Based Ethernet
VPN", RFC 7432, DOI 10.17487/RFC7432, February 2015, VPN", RFC 7432, DOI 10.17487/RFC7432, February 2015,
<https://www.rfc-editor.org/info/rfc7432>. <https://www.rfc-editor.org/info/rfc7432>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March
1997, <https://www.rfc-editor.org/info/rfc2119>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017,
<https://www.rfc-editor.org/info/rfc8174>.
9.2 Informative References 9.2 Informative References
[vES] Sajassi et al. "EVPN Virtual Ethernet Segment", draft-ietf- [vES] Sajassi et al. "EVPN Virtual Ethernet Segment", draft-ietf-
bess-evpn-virtual-eth-segment-04, work-in-progress, January, 2019. bess-evpn-virtual-eth-segment-04, work-in-progress, January, 2019.
10. Acknowledgments 10. Acknowledgments
The authors want to thank Vinod Prabhu, Sriram Venkateswaran, Laxmi The authors want to thank Vinod Prabhu, Sriram Venkateswaran, Laxmi
Padakanti, Ranganathan Boovaraghavan for their review and Padakanti, Ranganathan Boovaraghavan for their review and
contributions. contributions.
 End of changes. 6 change blocks. 
7 lines changed or deleted 24 lines changed or added

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