< draft-gmsm-bess-evpn-bfd-02.txt   draft-gmsm-bess-evpn-bfd-03.txt >
INTERNET-DRAFT V. Govindan INTERNET-DRAFT V. Govindan
Intended status: Proposed Standard M. Mudigonda Intended status: Proposed Standard M. Mudigonda
A. Sajassi A. Sajassi
Cisco Systems Cisco Systems
G. Mirsky G. Mirsky
ZTE ZTE
D. Eastlake D. Eastlake
Huawei Technologies Futurewei Technologies
Expires: August 20, 2019 February 21, 2019 Expires: January 5, 2020 July 6, 2019
Fault Management for EVPN networks Fault Management for EVPN networks
draft-gmsm-bess-evpn-bfd-02 draft-gmsm-bess-evpn-bfd-03
Abstract Abstract
This document specifies proactive, in-band network OAM mechanisms to This document specifies proactive, in-band network OAM mechanisms to
detect loss of continuity and miss-connection faults that affect detect loss of continuity and miss-connection faults that affect
unicast and multi-destination paths (used by Broadcast, Unknown unicast and multi-destination paths (used by Broadcast, Unknown
Unicast and Multicast traffic) in an Ethernet VPN (EVPN) network. Unicast and Multicast traffic) in an Ethernet VPN (EVPN) network.
The mechanisms specified in the draft are based on the widely adopted The mechanisms specified in the draft are based on the widely adopted
Bidirectional Forwarding Detection (BFD) protocol. Bidirectional Forwarding Detection (BFD) protocol.
skipping to change at page 3, line 9 skipping to change at page 3, line 9
Normative References......................................16 Normative References......................................16
Informative References....................................18 Informative References....................................18
Authors' Addresses........................................19 Authors' Addresses........................................19
Internet-Draft Fault Management for EVPN Internet-Draft Fault Management for EVPN
1. Introduction 1. Introduction
[salam-bess-evpn-oam-req-frmwk] outlines the OAM requirements of [ietf-bess-evpn-oam-req-frmwk] outlines the OAM requirements of
Ethernet VPN networks (EVPN [RFC7432]). This document specifies Ethernet VPN networks (EVPN [RFC7432]). This document specifies
mechanisms for proactive fault detection at the network (overlay) mechanisms for proactive fault detection at the network (overlay)
layer of EVPN. The mechanisms proposed in the draft use the widely layer of EVPN. The mechanisms proposed in the draft use the widely
adopted Bidirectional Forwarding Detection (BFD [RFC5880]) protocol. adopted Bidirectional Forwarding Detection (BFD [RFC5880]) protocol.
EVPN fault detection mechanisms need to consider unicast traffic EVPN fault detection mechanisms need to consider unicast traffic
separately from Broadcast, Unknown Unicast, and Multicast (BUM) separately from Broadcast, Unknown Unicast, and Multicast (BUM)
traffic since they map to different Forwarding Equivalency Classes traffic since they map to different Forwarding Equivalency Classes
(FECs) in EVPN. Hence this document proposes different fault (FECs) in EVPN. Hence this document proposes different fault
detection mechanisms to suit each type, for unicast traffic using BFD detection mechanisms to suit each type, for unicast traffic using BFD
[RFC5880] and for BUM traffic using BFD or [ietf-bfd-multipoint- [RFC5880] and for BUM traffic using BFD or [RFC8563] depending on
active-tail] depending on whether an MP2P or P2MP tunnel is being whether an MP2P or P2MP tunnel is being used.
used.
Packet loss and packet delay measurement are out of scope for this Packet loss and packet delay measurement are out of scope for this
document. document.
1.1 Terminology 1.1 Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all 14 [RFC2119] [RFC8174] when, and only when, they appear in all
skipping to change at page 4, line 5 skipping to change at page 3, line 54
EVI - EVPN Instance EVI - EVPN Instance
EVPN - Ethernet VPN [RFC7432] EVPN - Ethernet VPN [RFC7432]
FEC - Forwarding Equivalency Class FEC - Forwarding Equivalency Class
GAL - Generic Associated Channel Label [RFC5586] GAL - Generic Associated Channel Label [RFC5586]
LSM - Label Switched Multicast (P2MP) LSM - Label Switched Multicast (P2MP)
Internet-Draft Fault Management for EVPN
LSP - Label Switched Path LSP - Label Switched Path
Internet-Draft Fault Management for EVPN
MP2P - Multi-Point to Point MP2P - Multi-Point to Point
OAM - Operations Administration, and Maintenance OAM - Operations Administration, and Maintenance
P2MP - Point to Multi-Point (LSM) P2MP - Point to Multi-Point (LSM)
PE - Provider Edge PE - Provider Edge
VXLAN - Virtual eXtesible Local Area Network (VXLAN) [RFC7348] VXLAN - Virtual eXtesible Local Area Network (VXLAN) [RFC7348]
skipping to change at page 5, line 25 skipping to change at page 5, line 25
o BUM traffic using Multi-point-to-Point (MP2P) tunnels (ingress o BUM traffic using Multi-point-to-Point (MP2P) tunnels (ingress
replication). replication).
o BUM traffic using Point-to-Multipoint (P2MP) tunnels (Label o BUM traffic using Point-to-Multipoint (P2MP) tunnels (Label
Switched Multicast (LSM)). Switched Multicast (LSM)).
o MPLS and VXLAN encapsulation. o MPLS and VXLAN encapsulation.
This document does not discuss BFD mechanisms for: This document does not discuss BFD mechanisms for:
o EVPN variants like PBB-EVPN [RFC7623]. This will be addressed o EVPN variants like PBB-EVPN [RFC7623]. It is intended to
in future versions. address this in future versions.
o Integrated Routing and Bridging (IRB) solution based on EVPN o Integrated Routing and Bridging (IRB) solution based on EVPN
[ietf-bess-evpn-inter-subnet-forwarding]. This will be [ietf-bess-evpn-inter-subnet-forwarding]. It is intended to
addressed in future versions. address this in future versions.
o EVPN using other encapsulations such as NVGRE and MPLS over GRE o EVPN using other encapsulations such as NVGRE or MPLS over GRE
[RFC8365]. [RFC8365].
o BUM traffic using MP2MP tunnels. o BUM traffic using MP2MP tunnels.
This specification specifies procedures for BFD asynchronous mode. This specification specifies procedures for BFD asynchronous mode.
BFD demand mode is outside the scope of this specification except as BFD demand mode is outside the scope of this specification except as
it is used in [ietf-bfd-multipoint-active-tail]. The use of the Echo it is used in [RFC8563]. The use of the Echo function is outside the
function is outside the scope of this specification. scope of this specification.
Internet-Draft Fault Management for EVPN Internet-Draft Fault Management for EVPN
3. Motivation for Running BFD at the EVPN Network Layer 3. Motivation for Running BFD at the EVPN Network Layer
The choice of running BFD at the network layer of the OAM model for The choice of running BFD at the network layer of the OAM model for
EVPN [salam-bess-evpn-oam-req-frmwk] was made after considering the EVPN [ietf-bess-evpn-oam-req-frmwk] was made after considering the
following: following:
o In addition to detecting link failures in the EVPN network, BFD o In addition to detecting link failures in the EVPN network, BFD
sessions at the network layer can be used to monitor the sessions at the network layer can be used to monitor the
successful setup of MP2P and P2MP EVPN tunnels transporting successful setup of MP2P and P2MP EVPN tunnels transporting
Unicast and BUM traffic such as label programming. The scope of Unicast and BUM traffic such as label programming. The scope of
reachability detection covers the ingress and the egress EVPN PE reachability detection covers the ingress and the egress EVPN PE
nodes and the network connecting them. nodes and the network connecting them.
o Monitoring a representative set of path(s) or a particular path o Monitoring a representative set of path(s) or a particular path
among the multiple paths available between two EVPN PE nodes could among the multiple paths available between two EVPN PE nodes could
be done by exercising entropy mechanisms such as entropy labels, be done by exercising entropy mechanisms such as entropy labels,
when they are used, or VXLAN source ports. However, paths that when they are used, or VXLAN source ports. However, paths that
cannot be realized by entropy variations cannot be monitored. cannot be realized by entropy variations cannot be monitored.
Fault monitoring requirements outlined by Fault monitoring requirements outlined by
[salam-bess-evpn-oam-req-frmwk] are addressed by the mechanisms [ietf-bess-evpn-oam-req-frmwk] are addressed by the mechanisms
proposed by this draft. proposed by this draft.
BFD testing between EVPN PE nodes does not guarantee that the EVPN BFD testing between EVPN PE nodes does not guarantee that the EVPN
service is functioning. (This can be monitored at the service level, service is functioning. (This can be monitored at the service level,
that is CE to CE.) For example, an egress EVPN-PE could understand that is CE to CE.) For example, an egress EVPN-PE could understand
EVPN labeling received but could switch data to an incorrect EVPN labeling received but could switch data to an incorrect
interface. However, BFD testing in the EVPN Network Layer does interface. However, BFD testing in the EVPN Network Layer does
provide additional confidence that data transported using those provide additional confidence that data transported using those
tunnels will reach the expected egress node. When BFD testing in the tunnels will reach the expected egress node. When BFD testing in the
EVPN overlay fails, that can be used as an indication of a Loss-of- EVPN overlay fails, that can be used as an indication of a Loss-of-
skipping to change at page 8, line 43 skipping to change at page 8, line 43
addresses for MPLS or VXLAN. The BFD discriminator to be used is addresses for MPLS or VXLAN. The BFD discriminator to be used is
distributed by BGP as specified in Section 7. Once the BFD session distributed by BGP as specified in Section 7. Once the BFD session
for the EVPN label is UP, the BFD systems terminating the BFD session for the EVPN label is UP, the BFD systems terminating the BFD session
MUST NOT change the local discriminator values of the BFD Control MUST NOT change the local discriminator values of the BFD Control
packets they generate, unless they first bring down the session as packets they generate, unless they first bring down the session as
specified in [RFC5884]. specified in [RFC5884].
5.2 P2MP Tunnels (Label Switched Multicast) 5.2 P2MP Tunnels (Label Switched Multicast)
Fault detection for BUM traffic distributed using a P2MP tunnel uses Fault detection for BUM traffic distributed using a P2MP tunnel uses
active tail multipoint BFD [ietf-bfd-multipoint-active-tail] in one active tail multipoint BFD [RFC8563] in one of the three scenarios
of the three scenarios providing head notification (see Section 5.2 providing head notification (see Section 5.2 of [RFC8563]).
of [ietf-bfd-multipoint-active-tail]).
For MPLS encapsulation of the head to tails BFD, Label Switched For MPLS encapsulation of the head to tails BFD, Label Switched
Multicast is used. For VXLAN encapsulation, BFD is delivered to the Multicast is used. For VXLAN encapsulation, BFD is delivered to the
tails through underlay multicast using an outer multicast IP address. tails through underlay multicast using an outer multicast IP address.
Internet-Draft Fault Management for EVPN Internet-Draft Fault Management for EVPN
6. BFD Packet Encapsulation 6. BFD Packet Encapsulation
The sections below describe the MPLS and VXLAN encapsulations of BFD The sections below describe the MPLS and VXLAN encapsulations of BFD
for EVPN OAM use. for EVPN OAM use.
6.1 MPLS Encapsulation 6.1 MPLS Encapsulation
This section describes use of the Generic Associated Channel Label This section describes use of the Generic Associated Channel Label
(GAL) for BFD encapsulation in MPLS based EVPN OAM. (GAL) for BFD encapsulation in MPLS based EVPN OAM.
6.1.1 Unicast 6.1.1 Unicast
The packet initially contains the following labels: LSP label The packet initially contains the following labels: LSP label
(transport), the optional entropy label and the EVPN Unicast label. (transport), the optional entropy label, and the EVPN Unicast label.
The G-ACh type is set to TBD1. The G-ACh payload of the packet MUST The G-ACh type is set to TBD1. The G-ACh payload of the packet MUST
contain the destination L2 header (in overlay space) followed by the contain the destination L2 header (in overlay space) followed by the
IP header that encapsulates the BFD packet. The MAC address of the IP header that encapsulates the BFD packet. The MAC address of the
inner packet is used to validate the <EVI, MAC> in the receiving inner packet is used to validate the <EVI, MAC> in the receiving
node. node.
- The destination MAC MUST be the dedicated MAC TBD-A (see Section - The destination MAC MUST be the dedicated MAC TBD-A (see Section
9) or the MAC address of the destination PE. 9) or the MAC address of the destination PE.
- The destination IP address MUST be in the 127.0.0.0/8 range for - The destination IP address MUST be in the 127.0.0.0/8 range for
IPv4 or in the 0:0:0:0:0:FFFF:7F00:0/104 range for IPv6. IPv4 or in the 0:0:0:0:0:FFFF:7F00:0/104 range for IPv6.
skipping to change at page 10, line 50 skipping to change at page 10, line 50
+ BFD Control Packet + | + BFD Control Packet + |
/ / | / / |
/... .../ --------------- /... .../ ---------------
6.1.2 Ingress Replication 6.1.2 Ingress Replication
The packet initially contains the following labels: LSP label The packet initially contains the following labels: LSP label
(transport), the optional entropy label, the BUM label, and the split (transport), the optional entropy label, the BUM label, and the split
horizon label [RFC7432] (where applicable). The G-ACh type is set to horizon label [RFC7432] (where applicable). The G-ACh type is set to
TBD1. The G-ACh payload of the packet is as described in Section TBD1. The G-ACh payload of the packet is as described in Section
6.1.2. 6.1.1.
Internet-Draft Fault Management for EVPN Internet-Draft Fault Management for EVPN
6.1.3 LSM (Label Switched Multicast, P2MP) 6.1.3 LSM (Label Switched Multicast, P2MP)
The encapsulation is the same as in Section 6.1.2 for ingress The encapsulation is the same as in Section 6.1.2 for ingress
replication except that the transport label identifies the P2MP replication except that the transport label identifies the P2MP
tunnel, in effect the set of tail PEs, rather than identifying a tunnel, in effect the set of tail PEs, rather than identifying a
single destination PE at the end of an MP2P tunnel. single destination PE at the end of an MP2P tunnel.
6.2 VXLAN Encapsulation 6.2 VXLAN Encapsulation
This section describes the use of the VXLAN [RFC7348] for BFD This section describes the use of the VXLAN [RFC7348] for BFD
encapsulation in VXLAN based EVPN OAM. This specification conforms to encapsulation in VXLAN based EVPN OAM. This specification conforms to
[ietf-bfd-vxlan]. [ietf-bfd-vxlan].
6.2.1 Unicast 6.2.1 Unicast
The outer and inner IP headers have a unicast source IP address of The outer and inner IP headers have a unicast source IP address of
the BFD message source and the destination IP address the BFD message the BFD message source and a destination IP address of the BFD
destination message destination
The destination UDP port MUST be 3784 [RFC5881]. The source port MUST The destination UDP port MUST be 3784 [RFC5881]. The source port MUST
be in the range 49152 through 65535. If the BFD source has multiple be in the range 49152 through 65535. If the BFD source has multiple
IP addresses, entropy MAY be further obtained by using any of those IP addresses, entropy MAY be further obtained by using any of those
addresses assuming the source is prepared for responses directed to addresses assuming the source is prepared for responses directed to
the IP address used. the IP address used.
The Your BFD discriminator is the value distributed for this unicast The Your BFD discriminator is the value distributed for this unicast
OAM purpose by the destination using BGP as specified in Section 7 or OAM purpose by the destination using BGP as specified in Section 7 or
is exchanged out-of-band or through some other means outside the is exchanged out-of-band or through some other means outside the
skipping to change at page 12, line 17 skipping to change at page 12, line 17
<---------- 4 bytes ----------> <---------- 4 bytes ---------->
+-------------------------------+ --- +-------------------------------+ ---
| Destination MAC Address | | | Destination MAC Address | |
+ +---------------+ | + +---------------+ |
| | | | | | | |
+---------------+ + L2 Header +---------------+ + L2 Header
| Source MAC Address | | | Source MAC Address | |
+-------------------------------+ | +-------------------------------+ |
| VLAN Tag | | | VLAN Tag | |
+---------------+---------------+ | +---------------+---------------+ |
| IP4 Ethertype | | |IP4/6 Ethertype| |
+---------------+---------------+ --- +---------------+---------------+ ---
/ / / /
/... IP4 Header .../ /... IP4/6 Header .../
/ / / /
+-------------------------------+ +-------------------------------+
| | | |
+ UDP Header + + UDP Header +
| | | |
+-------------------------------+ +-------------------------------+
| | | |
+ VXLAN Header + + VXLAN Header +
| | | |
+-------------------------------+ --- +-------------------------------+ ---
skipping to change at page 14, line 20 skipping to change at page 14, line 20
follows using the BGP-BFD Attribute as specified in follows using the BGP-BFD Attribute as specified in
[ietf-bess-mvpn-fast-failover]. This attribute is included with [ietf-bess-mvpn-fast-failover]. This attribute is included with
appropriate EVPN routes as follows: appropriate EVPN routes as follows:
Unicast: MAC/IP Advertisement Route [RFC7432]. Unicast: MAC/IP Advertisement Route [RFC7432].
MP2P Tunnel: Inclusive Multicast Ethernet Tag Route [RFC7432]. MP2P Tunnel: Inclusive Multicast Ethernet Tag Route [RFC7432].
P2MP: TBD P2MP: TBD
[Need more text on BFD session reacting to the new advertisement and [Need more text on BFD sessions reacting to the new advertisement
withdrawal of the BGP-BFD Attribute.] and withdrawal of the BGP-BFD Attribute.]
8. Scalability Considerations 8. Scalability Considerations
The mechanisms proposed by this draft could affect the packet load on The mechanisms proposed by this draft could affect the packet load on
the network and its elements especially when supporting the network and its elements especially when supporting
configurations involving a large number of EVIs. The option of configurations involving a large number of EVIs. The option of
slowing down or speeding up BFD timer values can be used by an slowing down or speeding up BFD timer values can be used by an
administrator or a network management entity to maintain the overhead administrator or a network management entity to maintain the overhead
incurred due to fault monitoring at an acceptable level. incurred due to fault monitoring at an acceptable level.
skipping to change at page 16, line 11 skipping to change at page 16, line 11
suggestions: suggestions:
Mach Chen Mach Chen
Internet-Draft Fault Management for EVPN Internet-Draft Fault Management for EVPN
Normative References Normative References
[ietf-bess-evpn-inter-subnet-forwarding] Sajassi, A., Salam, S., [ietf-bess-evpn-inter-subnet-forwarding] Sajassi, A., Salam, S.,
Thoria, S., Rekhter, Y., Drake, J., Yong, L., and L. Thoria, S., Rekhter, Y., Drake, J., Yong, L., and L.
Dunbar, "Integrated Routing and Bridging in EVPN", draft- Dunbar, "Integrated Routing and Bridging in EVPN",
ietf-bess-evpn-inter-subnet-forwarding-05 (work in draft-ietf-bess-evpn-inter-subnet-forwarding-08, work in
progress), October 2015. progress, March 2019.
[ietf-bfd-multipoint-active-tail] Katz, D., Ward, D., and J. [ietf-bess-mvpn-fast-failover] Morin, T., Kebler, R., Mirsky, G.,
Networks, "BFD Multipoint Active Tails.", draft-ietf-bfd- "Multicast VPN fast upstream failover",
multipoint-active-tail-09 (work in progress), May 2016. draft-ietf-bess-mvpn-fast-failover-05 (work in progress),
February 2019.
[ietf-bfd-vxlan] Pallagatti, S., Paragiri, S., Govindan, V., [ietf-bfd-vxlan] Pallagatti, S., Paragiri, S., Govindan, V.,
Mudigonda, M., G. Mirsky, "BFD for VXLAN", draft-ietf-bfd- Mudigonda, M., G. Mirsky, "BFD for VXLAN",
vxlan-03 (work in progress), October 2018. draft-ietf-bfd-vxlan-07 (work in progress), May 2019.
[ietf-bess-mvpn-fast-failover] Morin, T., Kebler, R., Mirsky, G.,
"Multicast VPN fast upstream failover", draft-ietf-bess-
mvpn-fast-failover (work in progress), November 2018.
[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 Requirement Levels", BCP 14, RFC 2119, DOI
10.17487/RFC2119, March 1997, <http://www.rfc- 10.17487/RFC2119, March 1997, <http://www.rfc-
editor.org/info/rfc2119>. editor.org/info/rfc2119>.
[RFC4385] Bryant, S., Swallow, G., Martini, L., and D. McPherson, [RFC4385] Bryant, S., Swallow, G., Martini, L., and D. McPherson,
"Pseudowire Emulation Edge-to-Edge (PWE3) Control Word for "Pseudowire Emulation Edge-to-Edge (PWE3) Control Word for
Use over an MPLS PSN", RFC 4385, DOI 10.17487/RFC4385, Use over an MPLS PSN", RFC 4385, DOI 10.17487/RFC4385,
February 2006, <http://www.rfc-editor.org/info/rfc4385>. February 2006, <http://www.rfc-editor.org/info/rfc4385>.
skipping to change at page 17, line 4 skipping to change at page 16, line 54
(BFD) for IPv4 and IPv6 (Single Hop)", RFC 5881, DOI (BFD) for IPv4 and IPv6 (Single Hop)", RFC 5881, DOI
10.17487/RFC5881, June 2010, <https://www.rfc- 10.17487/RFC5881, June 2010, <https://www.rfc-
editor.org/info/rfc5881>. editor.org/info/rfc5881>.
[RFC5883] Katz, D. and D. Ward, "Bidirectional Forwarding Detection [RFC5883] Katz, D. and D. Ward, "Bidirectional Forwarding Detection
(BFD) for Multihop Paths", RFC 5883, DOI 10.17487/RFC5883, (BFD) for Multihop Paths", RFC 5883, DOI 10.17487/RFC5883,
June 2010, <https://www.rfc-editor.org/info/rfc5883>. June 2010, <https://www.rfc-editor.org/info/rfc5883>.
[RFC5884] Aggarwal, R., Kompella, K., Nadeau, T., and G. Swallow, [RFC5884] Aggarwal, R., Kompella, K., Nadeau, T., and G. Swallow,
"Bidirectional Forwarding Detection (BFD) for MPLS Label "Bidirectional Forwarding Detection (BFD) for MPLS Label
Internet-Draft Fault Management for EVPN
Switched Paths (LSPs)", RFC 5884, DOI 10.17487/RFC5884, Switched Paths (LSPs)", RFC 5884, DOI 10.17487/RFC5884,
June 2010, <https://www.rfc-editor.org/info/rfc5884>. June 2010, <https://www.rfc-editor.org/info/rfc5884>.
Internet-Draft Fault Management for EVPN
[RFC6790] Kompella, K., Drake, J., Amante, S., Henderickx, W., and L. [RFC6790] Kompella, K., Drake, J., Amante, S., Henderickx, W., and L.
Yong, "The Use of Entropy Labels in MPLS Forwarding", RFC Yong, "The Use of Entropy Labels in MPLS Forwarding", RFC
6790, DOI 10.17487/RFC6790, November 2012, <http://www.rfc- 6790, DOI 10.17487/RFC6790, November 2012, <http://www.rfc-
editor.org/info/rfc6790>. editor.org/info/rfc6790>.
[RFC7348] Mahalingam, M., Dutt, D., Duda, K., Agarwal, P., Kreeger, [RFC7348] Mahalingam, M., Dutt, D., Duda, K., Agarwal, P., Kreeger,
L., Sridhar, T., Bursell, M., and C. Wright, "Virtual L., Sridhar, T., Bursell, M., and C. Wright, "Virtual
eXtensible Local Area Network (VXLAN): A Framework for eXtensible Local Area Network (VXLAN): A Framework for
Overlaying Virtualized Layer 2 Networks over Layer 3 Overlaying Virtualized Layer 2 Networks over Layer 3
Networks", RFC 7348, DOI 10.17487/RFC7348, August 2014, Networks", RFC 7348, DOI 10.17487/RFC7348, August 2014,
skipping to change at page 18, line 5 skipping to change at page 17, line 51
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119
Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May
2017, <https://www.rfc-editor.org/info/rfc8174>. 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8365] Sajassi, A., Ed., Drake, J., Ed., Bitar, N., Shekhar, R., [RFC8365] Sajassi, A., Ed., Drake, J., Ed., Bitar, N., Shekhar, R.,
Uttaro, J., and W. Henderickx, "A Network Virtualization Uttaro, J., and W. Henderickx, "A Network Virtualization
Overlay Solution Using Ethernet VPN (EVPN)", RFC 8365, DOI Overlay Solution Using Ethernet VPN (EVPN)", RFC 8365, DOI
10.17487/RFC8365, March 2018, <https://www.rfc- 10.17487/RFC8365, March 2018, <https://www.rfc-
editor.org/info/rfc8365>. editor.org/info/rfc8365>.
[RFC8563] Katz, D., Ward, D., Pallagatti, S., Ed., and G. Mirsky,
Ed., "Bidirectional Forwarding Detection (BFD) Multipoint
Active Tails", RFC 8563, DOI 10.17487/RFC8563, April 2019,
<https://www.rfc-editor.org/info/rfc8563>.
Internet-Draft Fault Management for EVPN Internet-Draft Fault Management for EVPN
Informative References Informative References
[salam-bess-evpn-oam-req-frmwk] Salam, S., Sajassi, A., Aldrin, S., [ietf-bess-evpn-oam-req-frmwk] Salam, S., Sajassi, A., Aldrin, S., J.
and J. Drake, "EVPN Operations, Administration and Drake, and D. Eastlake, "EVPN Operations, Administration
Maintenance Requirements and Framework", draft-salam-bess- and Maintenance Requirements and Framework",
evpn-oam-req-frmwk-00 (work in progress), May 2018. draft-ietf-bess-evpn-oam-req-frmwk-00, work in progress,
February 2019.
[RFC5920] Fang, L., Ed., "Security Framework for MPLS and GMPLS [RFC5920] Fang, L., Ed., "Security Framework for MPLS and GMPLS
Networks", RFC 5920, DOI 10.17487/RFC5920, July 2010, Networks", RFC 5920, DOI 10.17487/RFC5920, July 2010,
<https://www.rfc-editor.org/info/rfc5920>. <https://www.rfc-editor.org/info/rfc5920>.
Internet-Draft Fault Management for EVPN Internet-Draft Fault Management for EVPN
Authors' Addresses Authors' Addresses
Vengada Prasad Govindan Vengada Prasad Govindan
 End of changes. 26 change blocks. 
48 lines changed or deleted 48 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/