draft-ietf-bess-evpn-oam-req-frmwk-03.txt   draft-ietf-bess-evpn-oam-req-frmwk-04.txt 
INTERNET-DRAFT Samer Salam INTERNET-DRAFT Samer Salam
Intended Status: Informational Ali Sajassi Intended Status: Informational Ali Sajassi
Cisco Cisco
Sam Aldrin Sam Aldrin
Google Google
John E. Drake John E. Drake
Juniper Juniper
Donald Eastlake Donald Eastlake
Futurewei Futurewei
Expires: January 2, 2021 July 3, 2020 Expires: January 7, 2021 July 8, 2020
EVPN Operations, Administration and Maintenance EVPN Operations, Administration and Maintenance
Requirements and Framework Requirements and Framework
draft-ietf-bess-evpn-oam-req-frmwk-03 draft-ietf-bess-evpn-oam-req-frmwk-04
Abstract Abstract
This document specifies the requirements and reference framework for This document specifies the requirements and reference framework for
Ethernet VPN (EVPN) Operations, Administration and Maintenance (OAM). Ethernet VPN (EVPN) Operations, Administration and Maintenance (OAM).
The requirements cover the OAM aspects of EVPN and PBB-EVPN. The The requirements cover the OAM aspects of EVPN and PBB-EVPN. The
framework defines the layered OAM model encompassing the EVPN service framework defines the layered OAM model encompassing the EVPN service
layer, network layer and underlying Packet Switched Network (PSN) layer, network layer and underlying Packet Switched Network (PSN)
transport layer. transport layer.
skipping to change at page 4, line 5 skipping to change at page 3, line 43
3.2.1 Packet Loss.........................................14 3.2.1 Packet Loss.........................................14
3.2.2 Packet Delay........................................15 3.2.2 Packet Delay........................................15
4. Security Considerations................................16 4. Security Considerations................................16
5. Acknowledgements.......................................16 5. Acknowledgements.......................................16
6. IANA Considerations....................................16 6. IANA Considerations....................................16
Normative References......................................17 Normative References......................................17
Informative References....................................18 Informative References....................................18
Authors' Addresses........................................19
INTERNET-DRAFT EVPN OAM Requirements/Framework INTERNET-DRAFT EVPN OAM Requirements/Framework
1. Introduction 1. Introduction
This document specifies the requirements and defines a reference This document specifies the requirements and defines a reference
framework for Ethernet VPN (EVPN) Operations, Administration and framework for Ethernet VPN (EVPN) Operations, Administration and
Maintenance (OAM, [RFC6291]). In this context, we use the term EVPN Maintenance (OAM, [RFC6291]). In this context, we use the term EVPN
OAM to loosely refer to the OAM functions required for and/or OAM to loosely refer to the OAM functions required for and/or
applicable to [RFC7432] and [RFC7623]. applicable to [RFC7432] and [RFC7623].
skipping to change at page 8, line 43 skipping to change at page 8, line 43
analogous to VCCV [RFC5085] in the case of VPLS/VPWS. It provides analogous to VCCV [RFC5085] in the case of VPLS/VPWS. It provides
mechanisms to check the correct operation of the data plane, as well mechanisms to check the correct operation of the data plane, as well
as a mechanism to verify the data plane against the control plane. as a mechanism to verify the data plane against the control plane.
This includes the ability to perform fault detection and diagnostics This includes the ability to perform fault detection and diagnostics
on: on:
- the MP2P tunnels used for the transport of unicast traffic between - the MP2P tunnels used for the transport of unicast traffic between
PEs. EVPN allows for three different models of unicast label PEs. EVPN allows for three different models of unicast label
assignment: label per EVI, label per <ESI, Ethernet Tag> and label assignment: label per EVI, label per <ESI, Ethernet Tag> and label
per MAC address. In all three models, the label is bound to an EVPN per MAC address. In all three models, the label is bound to an EVPN
Unicast FEC. Unicast FEC. EVPN Network OAM MUST provide mechanisms to check the
operation of the data plane and verify that operation against the
EVPN Network OAM MUST provide mechanisms to check the operation of control plane view.
the data plane and verify that operation against the control plane
view.
- the MP2P tunnels used for aliasing unicast traffic destined to a - the MP2P tunnels used for aliasing unicast traffic destined to a
multi-homed Ethernet Segment. The three label assignment models, multi-homed Ethernet Segment. The three label assignment models,
discussed above, apply here as well. In all three models, the label discussed above, apply here as well. In all three models, the label
is bound to an EVPN Aliasing FEC. EVPN Network OAM MUST provide is bound to an EVPN Aliasing FEC. EVPN Network OAM MUST provide
mechanisms to check the operation of the data plane and verify that mechanisms to check the operation of the data plane and verify that
operation against the control plane view. operation against the control plane view.
- the multicast tunnels (either MP2P or P2MP) used for the transport
INTERNET-DRAFT EVPN OAM Requirements/Framework INTERNET-DRAFT EVPN OAM Requirements/Framework
- the multicast tunnels (either MP2P or P2MP) used for the transport
of broadcast, unknown unicast and multicast traffic between PEs. In of broadcast, unknown unicast and multicast traffic between PEs. In
the case of ingress replication, a label is allocated per EVI or the case of ingress replication, a label is allocated per EVI or
per <EVI, Ethernet Tag> and is bound to an EVPN Multicast FEC. In per <EVI, Ethernet Tag> and is bound to an EVPN Multicast FEC. In
the case of LSM, and more specifically aggregate inclusive trees, the case of LSM, and more specifically aggregate inclusive trees,
again a label may be allocated per EVI or per <EVI, Ethernet Tag> again a label may be allocated per EVI or per <EVI, Ethernet Tag>
and is bound to the tunnel FEC. and is bound to the tunnel FEC.
- the correct operation of the ESI split-horizon filtering function. - the correct operation of the ESI split-horizon filtering function.
In EVPN, a label is allocated per multi-homed Ethernet Segment for In EVPN, a label is allocated per multi-homed Ethernet Segment for
the purpose of performing the access split-horizon enforcement. The the purpose of performing the access split-horizon enforcement. The
label is bound to an EVPN Ethernet Segment. label is bound to an EVPN Ethernet Segment.
- the correct operation of the DF filtering function. - the correct operation of the DF filtering function. EVPN Network
OAM MUST provide mechanisms to check the operation of the data
EVPN Network OAM MUST provide mechanisms to check the operation of plane and verify that operation against the control plane view for
the data plane and verify that operation against the control plane the DF filtering function.
view for the DF filtering function.
EVPN network OAM mechanisms MUST provide in-band management EVPN network OAM mechanisms MUST provide in-band monitoring
capabilities. As such, OAM messages MUST be encoded so that they capabilities. As such, OAM messages MUST be encoded so that they
exhibit identical entropy characteristics to data traffic. exhibit identical entropy characteristics to data traffic in order
that they share the same fate.
EVPN network OAM SHOULD provide both proactive and on-demand EVPN network OAM SHOULD provide both proactive and on-demand
mechanisms of monitoring the data plane operation and data plane mechanisms of monitoring the data plane operation and data plane
conformance to the state of the control plane. conformance to the state of the control plane.
2.4 Transport OAM for EVPN 2.4 Transport OAM for EVPN
The transport OAM protocol depends on the nature of the underlying The transport OAM protocol depends on the nature of the underlying
transport technology in the PSN. MPLS OAM mechanisms [RFC8029] transport technology in the PSN. MPLS OAM mechanisms [RFC8029]
[RFC6425] as well as ICMP [RFC792] are applicable, depending on [RFC6425] as well as ICMP [RFC792] are applicable, depending on
 End of changes. 9 change blocks. 
15 lines changed or deleted 16 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/