--- 1/draft-ietf-bess-evpn-ipvpn-interworking-00.txt 2019-09-02 08:13:20.311045327 -0700 +++ 2/draft-ietf-bess-evpn-ipvpn-interworking-01.txt 2019-09-02 08:13:20.359046538 -0700 @@ -1,31 +1,33 @@ BESS Workgroup J. Rabadan, Ed. Internet Draft Nokia Intended status: Standards Track A. Sajassi, Ed. Cisco E. Rosen + Individual + J. Drake W. Lin Juniper J. Uttaro AT&T A. Simpson Nokia -Expires: September 7, 2019 March 6, 2019 +Expires: March 5, 2020 September 2, 2019 EVPN Interworking with IPVPN - draft-ietf-bess-evpn-ipvpn-interworking-00 + draft-ietf-bess-evpn-ipvpn-interworking-01 Abstract EVPN is used as a unified control plane for tenant network intra and inter-subnet forwarding. When a tenant network spans not only EVPN domains but also domains where IPVPN provides inter-subnet forwarding, there is a need to specify the interworking aspects between both EVPN and IPVPN domains, so that the end to end tenant connectivity can be accomplished. This document specifies how EVPN should interwork with VPN-IPv4/VPN-IPv6 and IPv4/IPv6 BGP families @@ -45,21 +47,21 @@ 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." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html - This Internet-Draft will expire on September 7, 2019. + This Internet-Draft will expire on March 5, 2020. Copyright Notice Copyright (c) 2019 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 (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -80,26 +82,26 @@ 4.2. Uniform-Propagation-Mode . . . . . . . . . . . . . . . . . 12 4.3. Aggregation of Routes and Path Attribute Propagation . . . 13 5. Route Selection Process between EVPN and other ISF SAFIs . . . 14 6. Composite PE Procedures . . . . . . . . . . . . . . . . . . . . 15 7. Gateway PE Procedures . . . . . . . . . . . . . . . . . . . . . 17 8. Interworking Use-Cases . . . . . . . . . . . . . . . . . . . . 19 9. Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . 21 10. Conventions used in this document . . . . . . . . . . . . . . 21 11. Security Considerations . . . . . . . . . . . . . . . . . . . 21 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 - 13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 21 - 13.1. Normative References . . . . . . . . . . . . . . . . . . . 21 + 13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 22 + 13.1. Normative References . . . . . . . . . . . . . . . . . . . 22 13.2. Informative References . . . . . . . . . . . . . . . . . . 22 - 14. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 22 - 15. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 22 - 16. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 22 + 14. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 23 + 15. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 23 + 16. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 23 1. Introduction and Problem Statement EVPN is used as a unified control plane for tenant network intra and inter-subnet forwarding. When a tenant network spans not only EVPN domains but also domains where IPVPN provides inter-subnet forwarding, there is a need to specify the interworking aspects between both EVPN and IPVPN domains, so that the end to end tenant connectivity can be accomplished. This document specifies how EVPN should interwork with VPN-IPv4/VPN-IPv6 and IPv4/IPv6 BGP families @@ -118,22 +120,29 @@ types must be propagated to other domains using different SAFIs. Some aspects of that propagation must be clarified. Examples of these aspects or procedures across BGP families are: route selection, loop prevention or BGP Path attribute propagation. The Interworking PE concepts are defined in section 2, and the rest of the document describes the interaction between Interworking PEs and other PEs for end-to-end inter-subnet forwarding. 2. Terminology and Interworking PE Components - This section summarizes the terminology related to the "Interworking - PE" concept that will be used throughout the rest of the document. + The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", + "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and + "OPTIONAL" in this document are to be interpreted as described in BCP + 14 [RFC2119] [RFC8174] when, and only when, they appear in all + capitals, as shown here. + + In addition, this section summarizes the terminology related to the + "Interworking PE" concept that will be used throughout the rest of + the document. +-------------------------------------------------------------+ | | | +------------------+ Interworking PE | | Attachment | +------------------+ | | Circuit(AC1) | | +----------+ | MPLS/NVO tnl ----------------------*Bridge | | +------ | | | |Table(BT1)| | +-----------+ / \ \ MPLS/NVO tnl +-------->| *---------* |<--> | Eth | -------+ | | | |Eth-Tag x + |IRB1| | \ / / @@ -927,52 +937,67 @@ 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here. 11. Security Considerations This section will be added in future versions. 12. IANA Considerations This document defines a new BGP path attribute known as the BGP - Domain Path (D-PATH) attribute and requests IANA to assign a new - attribute code type from the "BGP Path Attributes" subregistry under - the "Border Gateway Protocol (BGP) Parameters" registry. + Domain Path (D-PATH) attribute. + + IANA has assigned a new attribute code type from the "BGP Path + Attributes" subregistry under the "Border Gateway Protocol (BGP) + Parameters" registry: + + Path Attribute Value Code Reference + -------------------- ------------------------ --------------- + 36 BGP Domain Path (D-PATH) [This document] 13. References 13.1. Normative References [RFC7432] Sajassi, A., Ed., Aggarwal, R., Bitar, N., Isaac, A., Uttaro, J., Drake, J., and W. Henderickx, "BGP MPLS-Based Ethernet VPN", RFC 7432, DOI 10.17487/RFC7432, February 2015, . [RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A Border Gateway Protocol 4 (BGP-4)", RFC 4271, DOI 10.17487/RFC4271, January 2006, . + [RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private + Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364, February 2006, + . + + [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate + Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March + 1997, . + + [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC + 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, + . + 13.2. Informative References [RFC4360] Sangli, S., Tappan, D., and Y. Rekhter, "BGP Extended Communities Attribute", RFC 4360, DOI 10.17487/RFC4360, February 2006, . [IP-PREFIX] Rabadan et al., "IP Prefix Advertisement in EVPN", draft-ietf-bess-evpn-prefix-advertisement-11, May, 2018. [INTER-SUBNET] Sajassi et al., "IP Inter-Subnet Forwarding in EVPN", - draft-ietf-bess-evpn-inter-subnet-forwarding-05.txt, work in - progress, July, 2018 - - [ENCAP-ATT] Rosen et al., "The BGP Tunnel Encapsulation Attribute", - draft-ietf-idr-tunnel-encaps-10.txt, work in progress, August, 2018. + draft-ietf-bess-evpn-inter-subnet-forwarding-08.txt, work in + progress, March, 2019. [RFC6472] Kumari, W. and K. Sriram, "Recommendation for Not Using AS_SET and AS_CONFED_SET in BGP", BCP 172, RFC 6472, DOI 10.17487/RFC6472, December 2011, . 14. Acknowledgments 15. Contributors @@ -976,29 +1001,29 @@ 15. Contributors 16. Authors' Addresses Jorge Rabadan (editor) Nokia 777 E. Middlefield Road Mountain View, CA 94043 USA Email: jorge.rabadan@nokia.com + Ali Sajassi (editor) Cisco 170 West Tasman Drive San Jose, CA 95134, US EMail: sajassi@cisco.com Eric C. Rosen - Juniper Networks, Inc. - EMail: erosen@juniper.net + EMail: erosen52@gmail.com John Drake Juniper Networks, Inc. EMail: jdrake@juniper.net Wen Lin Juniper Networks, Inc. EMail: wlin@juniper.net Jim Uttaro