draft-ietf-bess-evpn-proxy-arp-nd-03.txt   draft-ietf-bess-evpn-proxy-arp-nd-04.txt 
skipping to change at page 1, line 15 skipping to change at page 1, line 15
K. Nagaraj K. Nagaraj
Intended status: Informational W. Henderickx Intended status: Informational W. Henderickx
G. Hankins G. Hankins
Nokia Nokia
T. King T. King
D. Melzer D. Melzer
DE-CIX DE-CIX
E. Nordmark E. Nordmark
Arista Networks Individual
Expires: April 7, 2018 October 4, 2017 Expires: October 11, 2018 April 9, 2018
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-03 draft-ietf-bess-evpn-proxy-arp-nd-04
Abstract Abstract
The MAC/IP Advertisement route specified in [RFC7432] can optionally The MAC/IP Advertisement route specified in [RFC7432] can optionally
carry IPv4 and IPv6 addresses associated with a MAC address. Remote carry IPv4 and IPv6 addresses associated with a MAC address. Remote
PEs can use this information to reply locally (act as proxy) to IPv4 PEs can use this information to reply locally (act as proxy) to IPv4
ARP requests and IPv6 Neighbor Solicitation messages (or 'unicast- ARP requests and IPv6 Neighbor Solicitation messages (or 'unicast-
forward' them to the owner of the MAC) and reduce/suppress the forward' them to the owner of the MAC) and reduce/suppress the
flooding produced by the Address Resolution procedure. This EVPN flooding produced by the Address Resolution procedure. This EVPN
capability is extremely useful in Internet Exchange Points (IXPs) and capability is extremely useful in Internet Exchange Points (IXPs) and
skipping to change at page 2, line 15 skipping to change at page 2, line 15
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." The list material or to cite them other than as "work in progress." The list
of current Internet-Drafts can be accessed at 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 7, 2018. This Internet-Draft will expire on October 11, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2018 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
skipping to change at page 20, line 39 skipping to change at page 20, line 39
security. security.
9. IANA Considerations 9. IANA Considerations
No IANA considerations. No IANA considerations.
10. References 10. References
10.1. Normative References 10.1. Normative References
[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,
editor.org/info/rfc7432>. <https://www.rfc-editor.org/info/rfc7432>.
[RFC4861]Narten, T., Nordmark, E., Simpson, W., and H. Soliman, [RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman,
"Neighbor Discovery for IP version 6 (IPv6)", RFC 4861, DOI "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861, DOI
10.17487/RFC4861, September 2007, <http://www.rfc- 10.17487/RFC4861, September 2007, <https://www.rfc-
editor.org/info/rfc4861>. editor.org/info/rfc4861>.
[RFC0826]Plummer, D., "Ethernet Address Resolution Protocol: Or [RFC0826] Plummer, D., "Ethernet Address Resolution Protocol: Or
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, <http://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, <http://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 [RFC7342] Dunbar, L., Kumari, W., and I. Gashinsky, "Practices for
Scaling ARP and Neighbor Discovery (ND) in Large Data Centers", Scaling ARP and Neighbor Discovery (ND) in Large Data Centers",
RFC 7342, DOI 10.17487/RFC7342, August 2014, <http://www.rfc- RFC 7342, DOI 10.17487/RFC7342, August 2014, <https://www.rfc-
editor.org/info/rfc7342>. 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, <http://www.rfc-editor.org/info/rfc3971>. March 2005, <https://www.rfc-editor.org/info/rfc3971>.
[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,
editor.org/info/rfc7432>. <https://www.rfc-editor.org/info/rfc7432>.
[RFC5227]Cheshire, S., "IPv4 Address Conflict Detection", RFC 5227, [RFC5227] Cheshire, S., "IPv4 Address Conflict Detection", RFC 5227,
DOI 10.17487/RFC5227, July 2008, <http://www.rfc- DOI 10.17487/RFC5227, July 2008, <https://www.rfc-
editor.org/info/rfc5227>. editor.org/info/rfc5227>.
10.2. Informative References 10.2. Informative References
[ARP-Sponge] Wessel M. and Sijm N., Universiteit van Amsterdam, [ARP-Sponge] Wessel M. and Sijm N., Universiteit van Amsterdam,
"Effects of IPv4 and IPv6 address resolution on AMS-IX and the ARP "Effects of IPv4 and IPv6 address resolution on AMS-IX and the ARP
Sponge", July 2009. Sponge", July 2009.
[EVPN-ND-FLAGS] Sathappan S., Nagaraj K. and Rabadan J., "Propagation [EVPN-ND-FLAGS] Sathappan S., Nagaraj K. and Rabadan J., "Propagation
of IPv6 Neighbor Advertisement Flags in EVPN", draft-ietf-bess-evpn- of IPv6 Neighbor Advertisement Flags in EVPN", draft-ietf-bess-evpn-
 End of changes. 20 change blocks. 
23 lines changed or deleted 23 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/