draft-ietf-bess-evpn-prefix-advertisement-03.txt   draft-ietf-bess-evpn-prefix-advertisement-04.txt 
BESS Workgroup J. Rabadan, Ed. BESS Workgroup J. Rabadan, Ed.
Internet Draft W. Henderickx Internet Draft W. Henderickx
S. Palislamovic
Intended status: Standards Track Nokia Intended status: Standards Track Nokia
A. Isaac
J. Drake J. Drake
W. Lin W. Lin
Juniper Juniper
A. Sajassi A. Sajassi
Cisco Cisco
Expires: March 17, 2017 September 13, 2016 Expires: August 17, 2017 February 13, 2017
IP Prefix Advertisement in EVPN IP Prefix Advertisement in EVPN
draft-ietf-bess-evpn-prefix-advertisement-03 draft-ietf-bess-evpn-prefix-advertisement-04
Abstract Abstract
EVPN provides a flexible control plane that allows intra-subnet EVPN provides a flexible control plane that allows intra-subnet
connectivity in an IP/MPLS and/or an NVO-based network. In NVO connectivity in an IP/MPLS and/or an NVO-based network. In NVO
networks, there is also a need for a dynamic and efficient inter- networks, there is also a need for a dynamic and efficient inter-
subnet connectivity across Tenant Systems and End Devices that can be subnet connectivity across Tenant Systems and End Devices that can be
physical or virtual and may not support their own routing protocols. physical or virtual and may not support their own routing protocols.
This document defines a new EVPN route type for the advertisement of This document defines a new EVPN route type for the advertisement of
IP Prefixes and explains some use-case examples where this new route- IP Prefixes and explains some use-case examples where this new route-
skipping to change at page 2, line 4 skipping to change at page 1, line 44
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
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 March 17, 2017. This Internet-Draft will expire on August 17, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2017 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
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Introduction and problem statement . . . . . . . . . . . . . . 4 2. Introduction and problem statement . . . . . . . . . . . . . . 3
2.1 Inter-subnet connectivity requirements in Data Centers . . . 4 2.1 Inter-subnet connectivity requirements in Data Centers . . . 4
2.2 The requirement for a new EVPN route type . . . . . . . . . 7 2.2 The requirement for a new EVPN route type . . . . . . . . . 6
3. The BGP EVPN IP Prefix route . . . . . . . . . . . . . . . . . 8 3. The BGP EVPN IP Prefix route . . . . . . . . . . . . . . . . . 8
3.1 IP Prefix Route encoding . . . . . . . . . . . . . . . . . . 9 3.1 IP Prefix Route encoding . . . . . . . . . . . . . . . . . . 8
4. Benefits of using the EVPN IP Prefix route . . . . . . . . . . 11 4. Benefits of using the EVPN IP Prefix route . . . . . . . . . . 10
5. IP Prefix overlay index use-cases . . . . . . . . . . . . . . . 12 5. IP Prefix overlay index use-cases . . . . . . . . . . . . . . . 11
5.1 TS IP address overlay index use-case . . . . . . . . . . . . 12 5.1 TS IP address overlay index use-case . . . . . . . . . . . . 11
5.2 Floating IP overlay index use-case . . . . . . . . . . . . . 15 5.2 Floating IP overlay index use-case . . . . . . . . . . . . . 14
5.3 ESI overlay index ("Bump in the wire") use-case . . . . . . 16 5.3 ESI overlay index ("Bump in the wire") use-case . . . . . . 15
5.4 IP-VRF-to-IP-VRF model . . . . . . . . . . . . . . . . . . . 19 5.4 IP-VRF-to-IP-VRF model . . . . . . . . . . . . . . . . . . . 18
5.4.1 Interface-less IP-VRF-to-IP-VRF model . . . . . . . . . 20 5.4.1 Interface-less IP-VRF-to-IP-VRF model . . . . . . . . . 19
5.4.2 Interface-full IP-VRF-to-IP-VRF with core-facing IRB . . 23 5.4.2 Interface-full IP-VRF-to-IP-VRF with core-facing IRB . . 22
5.4.3 Interface-full IP-VRF-to-IP-VRF with unnumbered 5.4.3 Interface-full IP-VRF-to-IP-VRF with unnumbered
core-facing IRB . . . . . . . . . . . . . . . . . . . . 25 core-facing IRB . . . . . . . . . . . . . . . . . . . . 24
6. Conclusions . . . . . . . . . . . . . . . . . . . . . . . . . . 28 6. Conclusions . . . . . . . . . . . . . . . . . . . . . . . . . . 27
7. Conventions used in this document . . . . . . . . . . . . . . . 29 7. Conventions used in this document . . . . . . . . . . . . . . . 28
8. Security Considerations . . . . . . . . . . . . . . . . . . . . 29 8. Security Considerations . . . . . . . . . . . . . . . . . . . . 28
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 29 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 28
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 30 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 29
10.1 Normative References . . . . . . . . . . . . . . . . . . . 30 10.1 Normative References . . . . . . . . . . . . . . . . . . . 29
10.2 Informative References . . . . . . . . . . . . . . . . . . 30 10.2 Informative References . . . . . . . . . . . . . . . . . . 29
11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 29
11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 30 12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 29
12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 30 13. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 29
13. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 30
1. Terminology 1. Terminology
GW IP: Gateway IP Address GW IP: Gateway IP Address
IPL: IP address length IPL: IP address length
IRB: Integrated Routing and Bridging interface IRB: Integrated Routing and Bridging interface
ML: MAC address length ML: MAC address length
skipping to change at page 30, line 19 skipping to change at page 29, line 19
[RFC4364]Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private [RFC4364]Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private
Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364, February 2006, Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364, February 2006,
<http://www.rfc-editor.org/info/rfc4364>. <http://www.rfc-editor.org/info/rfc4364>.
[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, <http://www.rfc- VPN", RFC 7432, DOI 10.17487/RFC7432, February 2015, <http://www.rfc-
editor.org/info/rfc7432>. editor.org/info/rfc7432>.
[EVPN-INTERSUBNET] Sajassi et al., "IP Inter-Subnet Forwarding in
EVPN", draft-ietf-bess-evpn-inter-subnet-forwarding-03.txt, work in
progress, February, 2017
10.2 Informative References 10.2 Informative References
[EVPN-OVERLAY] Sajassi-Drake et al., "A Network Virtualization [EVPN-OVERLAY] Sajassi-Drake et al., "A Network Virtualization
Overlay Solution using EVPN", draft-ietf-bess-evpn-overlay-04.txt, Overlay Solution using EVPN", draft-ietf-bess-evpn-overlay-07.txt,
work in progress, June, 2016 work in progress, November, 2016
[EVPN-INTERSUBNET] Sajassi et al., "IP Inter-Subnet Forwarding in
EVPN", draft-ietf-bess-evpn-inter-subnet-forwarding-01.txt, work in
progress, October, 2015
11. Acknowledgments 11. Acknowledgments
The authors would like to thank Mukul Katiyar for their valuable The authors would like to thank Mukul Katiyar for their valuable
feedback and contributions. The following people also helped feedback and contributions. The following people also helped
improving this document with their feedback: Tony Przygienda and improving this document with their feedback: Tony Przygienda and
Thomas Morin. Thomas Morin.
12. Contributors 12. Contributors
In addition to the authors listed on the front page, the following In addition to the authors listed on the front page, the following
co-authors have also contributed to this document: co-authors have also contributed to this document:
Senthil Sathappan Senthil Sathappan
Florin Balus Florin Balus
Aldrin Isaac
Senad Palislamovic
13. Authors' Addresses 13. Authors' Addresses
Jorge Rabadan (Editor) Jorge Rabadan (Editor)
Nokia Nokia
777 E. Middlefield Road 777 E. Middlefield Road
Mountain View, CA 94043 USA Mountain View, CA 94043 USA
Email: jorge.rabadan@nokia.com Email: jorge.rabadan@nokia.com
Wim Henderickx Wim Henderickx
Nokia Nokia
Email: wim.henderickx@nokia.com Email: wim.henderickx@nokia.com
Aldrin Isaac
Juniper
Email: aisaac@juniper.net
Senad Palislamovic
Nokia
Email: senad.palislamovic@nokia.com
John E. Drake John E. Drake
Juniper Juniper
Email: jdrake@juniper.net Email: jdrake@juniper.net
Ali Sajassi Ali Sajassi
Cisco Cisco
Email: sajassi@cisco.com Email: sajassi@cisco.com
Wen Lin Wen Lin
Juniper Juniper
 End of changes. 16 change blocks. 
44 lines changed or deleted 35 lines changed or added

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