| rfc9135v2.txt | rfc9135.txt | |||
|---|---|---|---|---|
| Internet Engineering Task Force (IETF) A. Sajassi | Internet Engineering Task Force (IETF) A. Sajassi | |||
| Request for Comments: 9135 S. Salam | Request for Comments: 9135 S. Salam | |||
| Category: Standards Track S. Thoria | Category: Standards Track S. Thoria | |||
| ISSN: 2070-1721 Cisco Systems | ISSN: 2070-1721 Cisco Systems | |||
| J. Drake | J. Drake | |||
| Juniper | Juniper | |||
| J. Rabadan | J. Rabadan | |||
| Nokia | Nokia | |||
| September 2021 | October 2021 | |||
| Integrated Routing and Bridging in Ethernet VPN (EVPN) | Integrated Routing and Bridging in Ethernet VPN (EVPN) | |||
| Abstract | Abstract | |||
| Ethernet VPN (EVPN) provides an extensible and flexible multihoming | Ethernet VPN (EVPN) provides an extensible and flexible multihoming | |||
| VPN solution over an MPLS/IP network for intra-subnet connectivity | VPN solution over an MPLS/IP network for intra-subnet connectivity | |||
| among Tenant Systems and end devices that can be physical or virtual. | among Tenant Systems and end devices that can be physical or virtual. | |||
| However, there are scenarios for which there is a need for a dynamic | However, there are scenarios for which there is a need for a dynamic | |||
| and efficient inter-subnet connectivity among these Tenant Systems | and efficient inter-subnet connectivity among these Tenant Systems | |||
| skipping to change at line 1206 ¶ | skipping to change at line 1206 ¶ | |||
| bundling, each MAC-VRF consists of multiple bridge tables (e.g., one | bundling, each MAC-VRF consists of multiple bridge tables (e.g., one | |||
| bridge table per VLAN). The MAC-VRFs on an NVE for a given tenant | bridge table per VLAN). The MAC-VRFs on an NVE for a given tenant | |||
| are associated with an IP-VRF corresponding to that tenant (or IP-VPN | are associated with an IP-VRF corresponding to that tenant (or IP-VPN | |||
| instance) via their IRB interfaces. | instance) via their IRB interfaces. | |||
| Since VXLAN and NVGRE encapsulations require an inner Ethernet header | Since VXLAN and NVGRE encapsulations require an inner Ethernet header | |||
| (inner MAC SA/DA) and since a TS MAC address cannot be used for | (inner MAC SA/DA) and since a TS MAC address cannot be used for | |||
| inter-subnet traffic, the ingress NVE's MAC address is used as an | inter-subnet traffic, the ingress NVE's MAC address is used as an | |||
| inner MAC SA. The NVE's MAC address is the device MAC address, and | inner MAC SA. The NVE's MAC address is the device MAC address, and | |||
| it is common across all MAC-VRFs and IP-VRFs. This MAC address is | it is common across all MAC-VRFs and IP-VRFs. This MAC address is | |||
| advertised using the new EVPN EVPN Router's MAC Extended Community | advertised using the new EVPN Router's MAC Extended Community | |||
| (Section 8.1). | (Section 8.1). | |||
| Figure 6 below illustrates this scenario, where a given tenant (e.g., | Figure 6 below illustrates this scenario, where a given tenant (e.g., | |||
| an IP-VPN instance) has three subnets represented by MAC-VRF1, MAC- | an IP-VPN instance) has three subnets represented by MAC-VRF1, MAC- | |||
| VRF2, and MAC-VRF3 across two NVEs. There are five TSs that are | VRF2, and MAC-VRF3 across two NVEs. There are five TSs that are | |||
| associated with these three MAC-VRFs -- i.e., TS1, TS4, and TS5 are | associated with these three MAC-VRFs -- i.e., TS1, TS4, and TS5 are | |||
| on the same subnet (e.g., the same MAC-VRF/VLAN). TS1 and TS5 are | on the same subnet (e.g., the same MAC-VRF/VLAN). TS1 and TS5 are | |||
| associated with MAC-VRF1 on NVE1, while TS4 is associated with MAC- | associated with MAC-VRF1 on NVE1, while TS4 is associated with MAC- | |||
| VRF1 on NVE2. TS2 is associated with MAC-VRF2 on NVE1, and TS3 is | VRF1 on NVE2. TS2 is associated with MAC-VRF2 on NVE1, and TS3 is | |||
| associated with MAC-VRF3 on NVE2. MAC-VRF1 and MAC-VRF2 on NVE1 are, | associated with MAC-VRF3 on NVE2. MAC-VRF1 and MAC-VRF2 on NVE1 are, | |||
| skipping to change at line 1623 ¶ | skipping to change at line 1623 ¶ | |||
| DOI 10.17487/RFC8365, March 2018, | DOI 10.17487/RFC8365, March 2018, | |||
| <https://www.rfc-editor.org/info/rfc8365>. | <https://www.rfc-editor.org/info/rfc8365>. | |||
| [RFC9012] Patel, K., Van de Velde, G., Sangli, S., and J. Scudder, | [RFC9012] Patel, K., Van de Velde, G., Sangli, S., and J. Scudder, | |||
| "The BGP Tunnel Encapsulation Attribute", RFC 9012, | "The BGP Tunnel Encapsulation Attribute", RFC 9012, | |||
| DOI 10.17487/RFC9012, April 2021, | DOI 10.17487/RFC9012, April 2021, | |||
| <https://www.rfc-editor.org/info/rfc9012>. | <https://www.rfc-editor.org/info/rfc9012>. | |||
| [RFC9136] Rabadan, J., Ed., Henderickx, W., Drake, J., Lin, W., and | [RFC9136] Rabadan, J., Ed., Henderickx, W., Drake, J., Lin, W., and | |||
| A. Sajassi, "IP Prefix Advertisement in Ethernet VPN | A. Sajassi, "IP Prefix Advertisement in Ethernet VPN | |||
| (EVPN)", RFC 9136, DOI 10.17487/RFC9136, September 2021, | (EVPN)", RFC 9136, DOI 10.17487/RFC9136, October 2021, | |||
| <https://www.rfc-editor.org/info/rfc9136>. | <https://www.rfc-editor.org/info/rfc9136>. | |||
| 12.2. Informative References | 12.2. Informative References | |||
| [EVPN] Krattiger, L., Ed., Sajassi, A., Ed., Thoria, S., Rabadan, | [EVPN] Krattiger, L., Ed., Sajassi, A., Ed., Thoria, S., Rabadan, | |||
| J., and J. Drake, "EVPN Interoperability Modes", Work in | J., and J. Drake, "EVPN Interoperability Modes", Work in | |||
| Progress, Internet-Draft, draft-ietf-bess-evpn-modes- | Progress, Internet-Draft, draft-ietf-bess-evpn-modes- | |||
| interop-00, 26 May 2021, | interop-00, 26 May 2021, | |||
| <https://datatracker.ietf.org/doc/html/draft-ietf-bess- | <https://datatracker.ietf.org/doc/html/draft-ietf-bess- | |||
| evpn-modes-interop-00>. | evpn-modes-interop-00>. | |||
| [EXTENDED-MOBILITY] | [EXTENDED-MOBILITY] | |||
| Malhotra, N., Ed., Sajassi, A., Pattekar, A., Rabadan, J., | Malhotra, N., Ed., Sajassi, A., Pattekar, A., Rabadan, J., | |||
| Lingala, A., and J. Drake, "Extended Mobility Procedures | Lingala, A., and J. Drake, "Extended Mobility Procedures | |||
| for EVPN-IRB", Work in Progress, Internet-Draft, draft- | for EVPN-IRB", Work in Progress, Internet-Draft, draft- | |||
| ietf-bess-evpn-irb-extended-mobility-05, 15 March 2021, | ietf-bess-evpn-irb-extended-mobility-07, 2 October 2021, | |||
| <https://datatracker.ietf.org/doc/html/draft-ietf-bess- | <https://datatracker.ietf.org/doc/html/draft-ietf-bess- | |||
| evpn-irb-extended-mobility-05>. | evpn-irb-extended-mobility-07>. | |||
| [RFC4365] Rosen, E., "Applicability Statement for BGP/MPLS IP | [RFC4365] Rosen, E., "Applicability Statement for BGP/MPLS IP | |||
| Virtual Private Networks (VPNs)", RFC 4365, | Virtual Private Networks (VPNs)", RFC 4365, | |||
| DOI 10.17487/RFC4365, February 2006, | DOI 10.17487/RFC4365, February 2006, | |||
| <https://www.rfc-editor.org/info/rfc4365>. | <https://www.rfc-editor.org/info/rfc4365>. | |||
| [RFC5798] Nadas, S., Ed., "Virtual Router Redundancy Protocol (VRRP) | [RFC5798] Nadas, S., Ed., "Virtual Router Redundancy Protocol (VRRP) | |||
| Version 3 for IPv4 and IPv6", RFC 5798, | Version 3 for IPv4 and IPv6", RFC 5798, | |||
| DOI 10.17487/RFC5798, March 2010, | DOI 10.17487/RFC5798, March 2010, | |||
| <https://www.rfc-editor.org/info/rfc5798>. | <https://www.rfc-editor.org/info/rfc5798>. | |||
| skipping to change at line 1673 ¶ | skipping to change at line 1673 ¶ | |||
| 2014, <https://www.rfc-editor.org/info/rfc7365>. | 2014, <https://www.rfc-editor.org/info/rfc7365>. | |||
| [RFC7637] Garg, P., Ed. and Y. Wang, Ed., "NVGRE: Network | [RFC7637] Garg, P., Ed. and Y. Wang, Ed., "NVGRE: Network | |||
| Virtualization Using Generic Routing Encapsulation", | Virtualization Using Generic Routing Encapsulation", | |||
| RFC 7637, DOI 10.17487/RFC7637, September 2015, | RFC 7637, DOI 10.17487/RFC7637, September 2015, | |||
| <https://www.rfc-editor.org/info/rfc7637>. | <https://www.rfc-editor.org/info/rfc7637>. | |||
| [VXLAN-GPE] | [VXLAN-GPE] | |||
| Maino, F., Ed., Kreeger, L., Ed., and U. Elzur, Ed., | Maino, F., Ed., Kreeger, L., Ed., and U. Elzur, Ed., | |||
| "Generic Protocol Extension for VXLAN (VXLAN-GPE)", Work | "Generic Protocol Extension for VXLAN (VXLAN-GPE)", Work | |||
| in Progress, Internet-Draft, draft-ietf-nvo3-vxlan-gpe-11, | in Progress, Internet-Draft, draft-ietf-nvo3-vxlan-gpe-12, | |||
| 6 March 2021, <https://datatracker.ietf.org/doc/html/ | 22 September 2021, <https://datatracker.ietf.org/doc/html/ | |||
| draft-ietf-nvo3-vxlan-gpe-11>. | draft-ietf-nvo3-vxlan-gpe-12>. | |||
| Acknowledgements | Acknowledgements | |||
| The authors would like to thank Sami Boutros, Jeffrey Zhang, | The authors would like to thank Sami Boutros, Jeffrey Zhang, | |||
| Krzysztof Szarkowicz, Lukas Krattiger and Neeraj Malhotra for their | Krzysztof Szarkowicz, Lukas Krattiger and Neeraj Malhotra for their | |||
| valuable comments. The authors would also like to thank Linda | valuable comments. The authors would also like to thank Linda | |||
| Dunbar, Florin Balus, Yakov Rekhter, Wim Henderickx, Lucy Yong, and | Dunbar, Florin Balus, Yakov Rekhter, Wim Henderickx, Lucy Yong, and | |||
| Dennis Cai for their feedback and contributions. | Dennis Cai for their feedback and contributions. | |||
| Authors' Addresses | Authors' Addresses | |||
| End of changes. 6 change blocks. | ||||
| 8 lines changed or deleted | 8 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/ | ||||