draft-ietf-bess-evpn-proxy-arp-nd-07.txt   draft-ietf-bess-evpn-proxy-arp-nd-08.txt 
skipping to change at page 1, line 15 skipping to change at page 1, line 15
K. Nagaraj K. Nagaraj
Intended status: Informational G. Hankins Intended status: Informational G. Hankins
Nokia Nokia
T. King T. King
DE-CIX DE-CIX
Expires: January 9, 2020 July 8, 2019 Expires: January 9, 2020 July 8, 2019
Operational Aspects of Proxy-ARP/ND in EVPN Networks Operational Aspects of Proxy-ARP/ND in EVPN Networks
draft-ietf-bess-evpn-proxy-arp-nd-07 draft-ietf-bess-evpn-proxy-arp-nd-08
Abstract Abstract
The EVPN MAC/IP Advertisement route can optionally carry IPv4 and The EVPN MAC/IP Advertisement route can optionally carry IPv4 and
IPv6 addresses associated with a MAC address. Remote PEs can use this IPv6 addresses associated with a MAC address. Remote PEs can use this
information to reply locally (act as proxy) to IPv4 ARP requests and information to reply locally (act as proxy) to IPv4 ARP requests and
IPv6 Neighbor Solicitation messages (or 'unicast-forward' them to the IPv6 Neighbor Solicitation messages (or 'unicast-forward' them to the
owner of the MAC) and reduce/suppress the flooding produced by the owner of the MAC) and reduce/suppress the flooding produced by the
Address Resolution procedure. This EVPN capability is extremely Address Resolution procedure. This EVPN capability is extremely
useful in Internet Exchange Points (IXPs) and Data Centers (DCs) with useful in Internet Exchange Points (IXPs) and Data Centers (DCs) with
skipping to change at page 21, line 36 skipping to change at page 21, line 36
Converting Network Protocol Addresses to 48.bit Ethernet Address for Converting Network Protocol Addresses to 48.bit Ethernet Address for
Transmission on Ethernet Hardware", STD 37, RFC 826, DOI Transmission on Ethernet Hardware", STD 37, RFC 826, DOI
10.17487/RFC0826, November 1982, <https://www.rfc- 10.17487/RFC0826, November 1982, <https://www.rfc-
editor.org/info/rfc826>. editor.org/info/rfc826>.
[RFC6820] Narten, T., Karir, M., and I. Foo, "Address Resolution [RFC6820] Narten, T., Karir, M., and I. Foo, "Address Resolution
Problems in Large Data Center Networks", RFC 6820, DOI Problems in Large Data Center Networks", RFC 6820, DOI
10.17487/RFC6820, January 2013, <https://www.rfc- 10.17487/RFC6820, January 2013, <https://www.rfc-
editor.org/info/rfc6820>. editor.org/info/rfc6820>.
[RFC7342] Dunbar, L., Kumari, W., and I. Gashinsky, "Practices for
Scaling ARP and Neighbor Discovery (ND) in Large Data Centers",
RFC 7342, DOI 10.17487/RFC7342, August 2014, <https://www.rfc-
editor.org/info/rfc7342>.
[RFC3971] Arkko, J., Ed., Kempf, J., Zill, B., and P. Nikander, [RFC3971] Arkko, J., Ed., Kempf, J., Zill, B., and P. Nikander,
"SEcure Neighbor Discovery (SEND)", RFC 3971, DOI 10.17487/RFC3971, "SEcure Neighbor Discovery (SEND)", RFC 3971, DOI 10.17487/RFC3971,
March 2005, <https://www.rfc-editor.org/info/rfc3971>. March 2005, <https://www.rfc-editor.org/info/rfc3971>.
[RFC5227] Cheshire, S., "IPv4 Address Conflict Detection", RFC 5227, [RFC5227] Cheshire, S., "IPv4 Address Conflict Detection", RFC 5227,
DOI 10.17487/RFC5227, July 2008, <https://www.rfc- DOI 10.17487/RFC5227, July 2008, <https://www.rfc-
editor.org/info/rfc5227>. editor.org/info/rfc5227>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March
 End of changes. 2 change blocks. 
6 lines changed or deleted 1 lines changed or added

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