draft-ietf-bess-evpn-na-flags-01.txt   draft-ietf-bess-evpn-na-flags-02.txt 
BESS Workgroup J. Rabadan, Ed. BESS Workgroup J. Rabadan, Ed.
Internet Draft S. Sathappan Internet Draft S. Sathappan
K. Nagaraj K. Nagaraj
Intended status: Standards Track Nokia Intended status: Standards Track Nokia
Expires: October 11, 2018 April 9, 2018 Expires: April 22, 2019 October 19, 2018
Propagation of IPv6 Neighbor Advertisement Flags in EVPN Propagation of IPv6 Neighbor Advertisement Flags in EVPN
draft-ietf-bess-evpn-na-flags-01 draft-ietf-bess-evpn-na-flags-02
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 and ARP requests and IPv6 Neighbor Solicitation messages and
reduce/suppress the flooding produced by the Address Resolution reduce/suppress the flooding produced by the Address Resolution
procedure. However, if the Neighbor information is learnt via EVPN, procedure. However, if the Neighbor information is learnt via EVPN,
the PE would not know if a particular IPv6->MAC pair belongs to a the PE would not know if a particular IPv6->MAC pair belongs to a
skipping to change at page 2, line 13 skipping to change at page 2, line 13
and may be updated, replaced, or obsoleted by other documents and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as reference at any 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 October 11, 2018. This Internet-Draft will expire on April 22, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 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
skipping to change at page 2, line 42 skipping to change at page 2, line 42
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The EVPN Neighbor Discovery (ND) Extended Community . . . . . . 3 2. The EVPN Neighbor Discovery (ND) Extended Community . . . . . . 3
3. Use of the EVPN ND Extended Community . . . . . . . . . . . . . 4 3. Use of the EVPN ND Extended Community . . . . . . . . . . . . . 4
4. Conventions used in this document . . . . . . . . . . . . . . . 4 4. Conventions used in this document . . . . . . . . . . . . . . . 4
5. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 5
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5
7.1. Normative References . . . . . . . . . . . . . . . . . . . 5 7.1. Normative References . . . . . . . . . . . . . . . . . . . 5
7.2. Informative References . . . . . . . . . . . . . . . . . . 5 7.2. Informative References . . . . . . . . . . . . . . . . . . 5
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 5 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 5 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction 1. Introduction
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 and ARP requests and IPv6 Neighbor Solicitation messages and
reduce/suppress the flooding produced by the Address Resolution reduce/suppress the flooding produced by the Address Resolution
procedure. However, if the Neighbor information is learned via EVPN, procedure. However, if the Neighbor information is learned via EVPN,
the PE would not know if a particular IPv6->MAC pair belongs to a the PE would not know if a particular IPv6->MAC pair belongs to a
skipping to change at page 4, line 50 skipping to change at page 4, line 50
IPv6 address. IPv6 address.
A PE that implements the proxy-ND function SHOULD have an A PE that implements the proxy-ND function SHOULD have an
administrative option to define the default Flag to be used in case administrative option to define the default Flag to be used in case
no EVPN ND Extended Community is received for a given IPv6->MAC no EVPN ND Extended Community is received for a given IPv6->MAC
entry. entry.
4. Conventions used in this document 4. Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
document are to be interpreted as described in RFC-2119 [RFC2119]. "OPTIONAL" in this document are to be interpreted as described in
BCP14 [RFC2119] [RFC8174] when, and only when, they appear in all
In this document, these words will appear with that interpretation capitals, as shown here.
only when in ALL CAPS. Lower case uses of these words are not to be
interpreted as carrying RFC-2119 significance.
In this document, the characters ">>" preceding an indented line(s)
indicates a compliance requirement statement using the key words
listed above. This convention aids reviewers in quickly identifying
or finding the explicit compliance requirements of this RFC.
5. Security Considerations 5. Security Considerations
The same security considerations described in [RFC7432] apply to this The same security considerations described in [RFC7432] apply to this
document. document.
6. IANA Considerations 6. IANA Considerations
This document requests the registration of a new EVPN Extended This document requests the registration of a new EVPN Extended
Community sub-type: Community sub-type:
skipping to change at page 5, line 42 skipping to change at page 5, line 35
[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, <https://www.rfc- 10.17487/RFC4861, September 2007, <https://www.rfc-
editor.org/info/rfc4861>. editor.org/info/rfc4861>.
[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, VPN", RFC 7432, DOI 10.17487/RFC7432, February 2015,
<https://www.rfc-editor.org/info/rfc7432>. <https://www.rfc-editor.org/info/rfc7432>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March
1997, <https://www.rfc-editor.org/info/rfc2119>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC2119
Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017,
<https://www.rfc-editor.org/info/rfc8174>.
7.2. Informative References 7.2. Informative References
8. Acknowledgments 8. Acknowledgments
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
Nokia Nokia
701 E. Middlefield Road 701 E. Middlefield Road
Mountain View, CA 94043 USA Mountain View, CA 94043 USA
 End of changes. 8 change blocks. 
16 lines changed or deleted 17 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/