draft-ietf-bess-evpn-prefix-advertisement-08.txt   draft-ietf-bess-evpn-prefix-advertisement-09.txt 
skipping to change at page 1, line 14 skipping to change at page 1, line 14
Internet Draft W. Henderickx Internet Draft W. Henderickx
Intended status: Standards Track Nokia Intended status: Standards Track Nokia
J. Drake J. Drake
W. Lin W. Lin
Juniper Juniper
A. Sajassi A. Sajassi
Cisco Cisco
Expires: April 23, 2018 October 20, 2017 Expires: May 25, 2018 November 21, 2017
IP Prefix Advertisement in EVPN IP Prefix Advertisement in EVPN
draft-ietf-bess-evpn-prefix-advertisement-08 draft-ietf-bess-evpn-prefix-advertisement-09
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 MPLS and/or NVO-based network. In some networks, connectivity in an MPLS and/or NVO-based network. In some networks,
there is also a need for a dynamic and efficient inter-subnet there is also a need for a dynamic and efficient inter-subnet
connectivity across Tenant Systems and End Devices that can be connectivity across Tenant Systems and End Devices that can be
physical or virtual and do not necessarily participate in dynamic physical or virtual and do not necessarily participate in dynamic
routing protocols. This document defines a new EVPN route type for routing protocols. This document defines a new EVPN route type for
the advertisement of IP Prefixes and explains some use-case examples the advertisement of IP Prefixes and explains some use-case examples
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 April 23, 2018. This Internet-Draft will expire on May 25, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 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
skipping to change at page 2, line 47 skipping to change at page 2, line 47
4.4 IP-VRF-to-IP-VRF Model . . . . . . . . . . . . . . . . . . . 20 4.4 IP-VRF-to-IP-VRF Model . . . . . . . . . . . . . . . . . . . 20
4.4.1 Interface-less IP-VRF-to-IP-VRF Model . . . . . . . . . 21 4.4.1 Interface-less IP-VRF-to-IP-VRF Model . . . . . . . . . 21
4.4.2 Interface-ful IP-VRF-to-IP-VRF with SBD IRB . . . . . . 24 4.4.2 Interface-ful IP-VRF-to-IP-VRF with SBD IRB . . . . . . 24
4.4.3 Interface-ful IP-VRF-to-IP-VRF with Unnumbered SBD IRB . 27 4.4.3 Interface-ful IP-VRF-to-IP-VRF with Unnumbered SBD IRB . 27
5. Conclusions . . . . . . . . . . . . . . . . . . . . . . . . . . 30 5. Conclusions . . . . . . . . . . . . . . . . . . . . . . . . . . 30
6. Conventions used in this document . . . . . . . . . . . . . . . 31 6. Conventions used in this document . . . . . . . . . . . . . . . 31
7. Security Considerations . . . . . . . . . . . . . . . . . . . . 31 7. Security Considerations . . . . . . . . . . . . . . . . . . . . 31
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 31 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 31
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 31 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 31
9.1 Normative References . . . . . . . . . . . . . . . . . . . . 31 9.1 Normative References . . . . . . . . . . . . . . . . . . . . 31
9.2 Informative References . . . . . . . . . . . . . . . . . . . 31 9.2 Informative References . . . . . . . . . . . . . . . . . . . 32
10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 32 10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 32
11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 32 11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 32
12. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 32 12. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 32
1. Terminology 1. Terminology
GW IP: Gateway IP Address. GW IP: Gateway IP Address.
IPL: IP address length. IPL: IP address length.
skipping to change at page 31, line 21 skipping to change at page 31, line 21
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC-2119 [RFC2119]. document are to be interpreted as described in RFC-2119 [RFC2119].
7. Security Considerations 7. Security Considerations
The security considerations discussed in [RFC7432] apply to this The security considerations discussed in [RFC7432] apply to this
document. document.
8. IANA Considerations 8. IANA Considerations
This document requests the allocation of value 5 in the "EVPN Route As requested by this document, value 5 in the "EVPN Route Types"
Types" registry defined by [RFC7432]: registry defined by [RFC7432] has been allocated:
Value Description Reference Value Description Reference
5 IP Prefix route [this document] 5 IP Prefix route [this document]
9. References 9. References
9.1 Normative References 9.1 Normative References
[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>.
[RFC7606]Chen, E., Scudder, J., Mohapatra, P., and K. Patel, "Revised [RFC7606] Chen, E., Scudder, J., Mohapatra, P., and K. Patel,
Error Handling for BGP UPDATE Messages", RFC 7606, August 2015, "Revised Error Handling for BGP UPDATE Messages", RFC 7606, August
<http://www.rfc-editor.org/info/rfc7606>. 2015, <http://www.rfc-editor.org/info/rfc7606>.
[RFC5512] Mohapatra, P. and E. Rosen, "The BGP Encapsulation
Subsequent Address Family Identifier (SAFI) and the BGP Tunnel
Encapsulation Attribute", RFC 5512, DOI 10.17487/RFC5512, April 2009,
<http://www.rfc-editor.org/info/rfc5512>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March
1997, <http://www.rfc-editor.org/info/rfc2119>.
9.2 Informative References 9.2 Informative References
[EVPN-INTERSUBNET] Sajassi et al., "IP Inter-Subnet Forwarding in [EVPN-INTERSUBNET] Sajassi et al., "IP Inter-Subnet Forwarding in
EVPN", draft-ietf-bess-evpn-inter-subnet-forwarding-03.txt, work in EVPN", draft-ietf-bess-evpn-inter-subnet-forwarding-03.txt, work in
progress, February, 2017 progress, February, 2017
[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-08.txt, Overlay Solution using EVPN", draft-ietf-bess-evpn-overlay-08.txt,
work in progress, March, 2017 work in progress, March, 2017
10. Acknowledgments 10. Acknowledgments
The authors would like to thank Mukul Katiyar and Jeffrey Zhang for The authors would like to thank Mukul Katiyar and Jeffrey Zhang for
their valuable feedback and contributions. The following people also their valuable feedback and contributions. The following people also
helped improving this document with their feedback: Tony Przygienda helped improving this document with their feedback: Tony Przygienda
and Thomas Morin. Special THANK YOU to Eric Rosen for his detailed and Thomas Morin. Special THANK YOU to Eric Rosen for his detailed
review, it really helped improve the readability and clarify the review, it really helped improve the readability and clarify the
 End of changes. 10 change blocks. 
13 lines changed or deleted 22 lines changed or added

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