Internet Engineering Task Force R.S. Sharma, Ed. Internet-Draft A.B. Banerjee Intended status: Standards Track R.S. Sivaramu Expires: 25 December 2022 A.S. Sajassi Cisco Systems 23 June 2022 Multi-site EVPN based VXLAN using Border Gateways draft-sharma-multi-site-evpn-04 Abstract This document described the procedures for interconnecting two or more Network Virtualization Overlays (NVOs) via NVO over IP-only network. The solution interconnects Ethernet VPN network by using NVO with Ethernet VPN (EVPN) to facilitate the interconnect in a scalable fashion. The motivation is to support extension of Layer-2 and Layer-3, Unicast and Multicast, VPNs without having to rely on typical Data Center Interconnect (DCI) technologies like MPLS/VPLS. The requirements for the interconnect are similar to the ones specified in RFC7209 [RFC7209] "Requirements for Ethernet VPN (EVPN)". In particular, this document describes the difference of the Gateways (GWs) procedure and incremental functionality from [RFC9014] "Interconnect Solution for Ethernet VPN (EVPN) Overlay Networks", which this solution is interoperable with. This document is OBSOLETE and replaced by [SHARMA-BESS-MULTI-SITE]. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on 25 December 2022. Sharma, et al. Expires 25 December 2022 [Page 1] Internet-Draft Multi-site EVPN June 2022 Copyright Notice Copyright (c) 2022 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/ license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 2. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 3 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 4. Security Considerations . . . . . . . . . . . . . . . . . . . 3 5. References . . . . . . . . . . . . . . . . . . . . . . . . . 3 5.1. Normative References . . . . . . . . . . . . . . . . . . 3 5.2. Informative References . . . . . . . . . . . . . . . . . 3 Appendix A. Additional Stuff . . . . . . . . . . . . . . . . . . 3 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction This document described the procedures for interconnecting two or more Network Virtualization Overlays (NVOs) via NVO over IP-only network. The solution interconnects Ethernet VPN network by using NVO with Ethernet VPN (EVPN) to facilitate the interconnect in a scalable fashion. The motivation is to support extension of Layer-2 and Layer-3, Unicast and Multicast, VPNs without having to rely on typical Data Center Interconnect (DCI) technologies like MPLS/VPLS. The requirements for the interconnect are similar to the ones specified in RFC7209 [RFC7209] "Requirements for Ethernet VPN (EVPN)". In particular, this document describes the difference of the Gateways (GWs) procedure and incremental functionality from [RFC9014] "Interconnect Solution for Ethernet VPN (EVPN) Overlay Networks", which this solution is interoperable with. This document is OBSOLETE and replaced by [SHARMA-BESS-MULTI-SITE]. Sharma, et al. Expires 25 December 2022 [Page 2] Internet-Draft Multi-site EVPN June 2022 1.1. Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119]. 2. Acknowledgements This authors would like to thank Max Ardica, Lukas Krattiger, Anuj Mittal, Lilian Quan, Veera Ravinutala, Murali Garimella, Tarun Wadhwa for their review and comments. 3. IANA Considerations TBD. 4. Security Considerations TBD. 5. References 5.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . [SHARMA-BESS-MULTI-SITE] L. Krattiger et. al., "Multi-Site Solution for Ethernet VPN (EVPN) Overlay", 2022, . 5.2. Informative References [RFC7209] Sajassi, A., Aggarwal, R., Uttaro, J., Bitar, N., Henderickx, W., and A. Isaac, "Requirements for Ethernet VPN (EVPN)", RFC 7209, DOI 10.17487/RFC7209, May 2014, . Appendix A. Additional Stuff TBD. Authors' Addresses Sharma, et al. Expires 25 December 2022 [Page 3] Internet-Draft Multi-site EVPN June 2022 Rajesh Sharma (editor) Cisco Systems 170 W Tasman Drive San Jose, CA United States of America Email: rajshr@cisco.com Ayan Banerjee Cisco Systems 170 W Tasman Drive San Jose, CA United States of America Email: ayabaner@cisco.com Raghava Sivaramu Cisco Systems 170 W Tasman Drive San Jose, CA United States of America Email: raghavas@cisco.com Ali Sajassi Cisco Systems 170 W Tasman Drive San Jose, CA United States of America Email: sajassi@cisco.com Sharma, et al. Expires 25 December 2022 [Page 4]