draft-ietf-bess-evpn-proxy-arp-nd-00.txt   draft-ietf-bess-evpn-proxy-arp-nd-01.txt 
skipping to change at page 1, line 17 skipping to change at page 1, line 17
G. Hankins G. Hankins
Nokia Nokia
T. King T. King
D. Melzer D. Melzer
DE-CIX DE-CIX
E. Nordmark E. Nordmark
Arista Networks Arista Networks
Expires: October 6, 2016 April 4, 2016 Expires: April 6, 2017 October 3, 2016
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-00 draft-ietf-bess-evpn-proxy-arp-nd-01
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 October 6, 2015. This Internet-Draft will expire on April 6, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 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 3, line 5 skipping to change at page 3, line 5
4.3. Unicast-forward Sub-Function . . . . . . . . . . . . . . . 12 4.3. Unicast-forward Sub-Function . . . . . . . . . . . . . . . 12
4.4. Maintenance Sub-Function . . . . . . . . . . . . . . . . . 12 4.4. Maintenance Sub-Function . . . . . . . . . . . . . . . . . 12
4.5. Flooding (to Remote PEs) Reduction/Suppression . . . . . . 13 4.5. Flooding (to Remote PEs) Reduction/Suppression . . . . . . 13
4.6. Duplicate IP Detection . . . . . . . . . . . . . . . . . . 14 4.6. Duplicate IP Detection . . . . . . . . . . . . . . . . . . 14
5. Solution Benefits . . . . . . . . . . . . . . . . . . . . . . . 16 5. Solution Benefits . . . . . . . . . . . . . . . . . . . . . . . 16
6. Deployment Scenarios . . . . . . . . . . . . . . . . . . . . . 16 6. Deployment Scenarios . . . . . . . . . . . . . . . . . . . . . 16
6.1. All Dynamic Learning . . . . . . . . . . . . . . . . . . . 17 6.1. All Dynamic Learning . . . . . . . . . . . . . . . . . . . 17
6.2. Dynamic Learning with Proxy-ARP/ND . . . . . . . . . . . . 17 6.2. Dynamic Learning with Proxy-ARP/ND . . . . . . . . . . . . 17
6.3. Hybrid Dynamic Learning and Static Provisioning with 6.3. Hybrid Dynamic Learning and Static Provisioning with
Proxy-ARP/ND . . . . . . . . . . . . . . . . . . . . . . . 17 Proxy-ARP/ND . . . . . . . . . . . . . . . . . . . . . . . 17
6.4 All Static Provisioning with Proxy-ARP/ND . . . . . . . . . 17 6.4 All Static Provisioning with Proxy-ARP/ND . . . . . . . . . 18
6.5 Deployment Scenarios in IXPs . . . . . . . . . . . . . . . . 18 6.5 Deployment Scenarios in IXPs . . . . . . . . . . . . . . . . 18
6.6 Deployment Scenarios in DCs . . . . . . . . . . . . . . . . 19 6.6 Deployment Scenarios in DCs . . . . . . . . . . . . . . . . 19
7. Conventions Used in this Document . . . . . . . . . . . . . . . 19 7. Conventions Used in this Document . . . . . . . . . . . . . . . 19
8. Security Considerations . . . . . . . . . . . . . . . . . . . . 20 8. Security Considerations . . . . . . . . . . . . . . . . . . . . 20
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 20 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 20
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20
10.1. Normative References . . . . . . . . . . . . . . . . . . . 20 10.1. Normative References . . . . . . . . . . . . . . . . . . . 20
10.2. Informative References . . . . . . . . . . . . . . . . . . 21 10.2. Informative References . . . . . . . . . . . . . . . . . . 21
11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 21 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 21
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 22 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 22
skipping to change at page 17, line 24 skipping to change at page 17, line 24
shutdown. PEs do not intercept ARP/ND requests and flood all shutdown. PEs do not intercept ARP/ND requests and flood all
requests, as in a conventional layer-2 network. While no ARP/ND requests, as in a conventional layer-2 network. While no ARP/ND
mitigation is used in this scenario, the IXP can still take advantage mitigation is used in this scenario, the IXP can still take advantage
of EVPN features such as control plane learning and all-active of EVPN features such as control plane learning and all-active
multihoming in the peering network. Existing mitigation solutions, multihoming in the peering network. Existing mitigation solutions,
such as the ARP-Sponge daemon [ARP-Sponge] MAY also be used in this such as the ARP-Sponge daemon [ARP-Sponge] MAY also be used in this
scenario. scenario.
Although this option does not require any of the procedures described Although this option does not require any of the procedures described
in this document, it is added as baseline/default option for in this document, it is added as baseline/default option for
completeness. completeness. This option is equivalent to VPLS as far as ARP/ND is
concerned. The options described in 6.2, 6.3 and 6.4 are only
possible in EVPN networks in combination with their Proxy-ARP/ND
capabilities.
6.2. Dynamic Learning with Proxy-ARP/ND 6.2. Dynamic Learning with Proxy-ARP/ND
This scenario minimizes flooding while enabling dynamic learning of This scenario minimizes flooding while enabling dynamic learning of
IP->MAC entries. The Proxy-ARP/ND function is enabled in the MAC-VRFs IP->MAC entries. The Proxy-ARP/ND function is enabled in the MAC-VRFs
of the EVPN PEs, so that the PEs intercept and respond to CE of the EVPN PEs, so that the PEs intercept and respond to CE
requests. requests.
The solution MAY further reduce the flooding of the ARP/ND messages The solution MAY further reduce the flooding of the ARP/ND messages
in the EVPN network by snooping ARP/ND messages issued by the CEs. in the EVPN network by snooping ARP/ND messages issued by the CEs.
skipping to change at page 21, line 36 skipping to change at page 21, line 40
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-snr-bess-evpn- of IPv6 Neighbor Advertisement Flags in EVPN", draft-snr-bess-evpn-
na-flags-02, Work in Progress, July 2015. na-flags-04, Work in Progress, July 2016.
[Euro-IX BCP] https://www.euro-ix.net/pages/28/1/bcp_ixp.html [Euro-IX BCP] https://www.euro-ix.net/pages/28/1/bcp_ixp.html
11. Acknowledgments 11. Acknowledgments
The authors want to thank Ranganathan Boovaraghavan, Sriram The authors want to thank Ranganathan Boovaraghavan, Sriram
Venkateswaran, Manish Krishnan, Seshagiri Venugopal, Tony Przygienda Venkateswaran, Manish Krishnan, Seshagiri Venugopal, Tony Przygienda,
and Robert Raszuk for their review and contributions. Thank you to Robert Raszuk and Iftekhar Hussain for their review and
Oliver Knapp as well, for his detailed review. contributions. Thank you to Oliver Knapp as well, for his detailed
review.
Authors' Addresses 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
Senthil Sathappan Senthil Sathappan
 End of changes. 7 change blocks. 
9 lines changed or deleted 13 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/