Ethernet OAM Update Overview & Technical Aspects Dinesh Mohan May 18, 2004

Ethernet OAM (May 18, 2004) [Dinesh Mohan] - 1 Brief Overview IEEE ITU-T Q.3/13 + MEF + IETF L2VPN WG Activities

Ethernet OAM (May 18, 2004) [Dinesh Mohan] - 2 Ethernet OAM Layering CEU-PE N-PE CEBBPPPP Device View Ethernet Layer Eth AccessMPLS CoreMPLS Access Customer Service Provider Example: network/service with Ethernet & other technologies The Ethernet Layer implies the visibility to Ethernet frames –BUT Flat! Difficult to manage and identify accountability

Ethernet OAM (May 18, 2004) [Dinesh Mohan] - 3 OAM Domain – Service/Network Eth AccessMPLS CoreMPLS Access Customer Service Provider Customer Domain Provider Domain Operator Domain Solution: OAM Domains Domains necessary to bound OAM Flows & OAM responsibilities

Ethernet OAM (May 18, 2004) [Dinesh Mohan] - 4 OAM Layering Introduced since: Multiple technologies involved in ITU-T IETF focuses on MPLS/IP and uses Ethernet as a service –draft-sajassi-mohan-l2vpn-vpls-fm-00.txt –draft-mohan-sajassi-l2vpn-vpls-pm-00.txt Need for Requirements and/or Framework documents: –Y.1730 – Ethernet OAM Requirements - Approved –MEF – MEF Service Requirements & Framework –L2VPN – tbd.

Ethernet OAM (May 18, 2004) [Dinesh Mohan] - 5 Maintenance Entity Points (MEP) & Maintenance Intermediate Points (MIP) Network OAM Service OAM Customer Domain Provider Domain Operator Domain Eth AccessMPLS CoreMPLS Access Customer Service Provider MPLS Domain Maintenance Entity Point Maintenance Intermediate Point PW/MPLS OAM MEPs initiate/terminate/react to all OAM flows MIPs react to some OAM flows MEPs & MIPs dependent on Business Models & Deployment Scenarios

Ethernet OAM (May 18, 2004) [Dinesh Mohan] - 6 Ethernet MEPs & MIPs Customer Equipment Operator A Bridges Operator B Bridges ETH ETY Another representation for positioning of MEPs and MIPs on devices with consideration for ingress and egress. Maintenance Entity Point Maintenance Intermediate Point

Ethernet OAM (May 18, 2004) [Dinesh Mohan] - 7 OAM Models

Ethernet OAM (May 18, 2004) [Dinesh Mohan] - 8 OAM Functionality a) Discovery –i) Service e.g. discover all PEs supporting common service instance –ii) Network e.g. discover all devices (PE and P) common to a domain b) CC – Continuity Check Multicast unidirectional heartbeat Use: Fault Detection, Performance Monitoring (delay variance, frame loss) c) Loopback – Connectivity Check Unicast and Multicast bi-directional request/response Unicast (e.g. ICMP ping) Use: Fault detection, verification, delay, delay variance, frameloss, Multicast Use: Discovery d) Traceroute Use: Fault Isolation e) FDI/RDI Use: E W Fault propagation, Alarm Suppression

Ethernet OAM (May 18, 2004) [Dinesh Mohan] - 9 Maintenance Entities Mapped Example MEs identified –2 Service Providers (SP1 & SP2) –SP2 has two domains (operators) –MEs 1,2,3,4 are required for Business relationship –MEs 5,6 are required for convenience Customer Service Provider 1. UNI_C-UNI_C ME 2. UNI_N-UNI_N ME 3. UNI ME SP 1SP 2 4. E-NNI ME 5. Inter-domain ME (SP) 6. Intra-domain ME 6. Intra-domain ME (Operator) UNI E-NNI

Ethernet OAM (May 18, 2004) [Dinesh Mohan] - 10 End-to-end OAM – 2 Models Provider End-to-end OAM? CE-CE (terminating UNIs) –2 Possible Models Strong-Trust E-NNI ME (3) + ME (2) + ME (3) Weak-Trust E-NNI ME (3) + ME (6) + ME (4) + ME (5) + ME(3) or ME (3) + ME (6) + ME (4) + ME (6) + ME(3) Customer Service Provider 1. UNI_C-UNI_C ME 2. UNI_N-UNI_N ME 3. UNI ME SP 1SP 2 4. E-NNI ME 5. Inter-domain ME (SP) 6. Intra-domain ME 6. Intra-domain ME (Operator) UNI E-NNI

Ethernet OAM (May 18, 2004) [Dinesh Mohan] - 11 OAM Functions mapped to MEs Customer Service Provider 1. a (i), b, c 2. a (i), b, c, d, e Specifically for ME (3) and ME (4) –IEEE 802.3ah EFM OAM can be used for network/link OAM when UNI/E-NNI is an Ethernet link –When single service carried across a link, network OAM can map to service OAM 3. a (i), b, c, e SP 1SP 2 3. a (i), b, c, e 4. a (i), b, c, e 5. a (ii), b, c, d, e 6. a (ii), b, c, d, e

Ethernet OAM (May 18, 2004) [Dinesh Mohan] - 12 Maintenance Entities – P2P Case All MEs may not be needed always MEPs realize Maintenance Entities (MEs)

Ethernet OAM (May 18, 2004) [Dinesh Mohan] - 13 Maintenance Entities – MP2MP Case All MEs may not be needed always MEPs realize Maintenance Entities (MEs)

Ethernet OAM (May 18, 2004) [Dinesh Mohan] - 14 Maintenance Entities – CPE based Network Demarcation Access All MEs may not be needed always ETH_FP Service. Provider Y Network Operator B User X UNI_C to UNI_C ME UNI_N to UNI_N ME Access Link ME ETH_TFP ETH_FP User X Access Link ME Extension Link ME User Location UNI_NP to UNI_NP ME UNI ETH_FP ETH Link Private NNI ETH_FP Network Operator A ETH Link NNI ETH_FP ETH FPP Link UNI ETH FPP Link ETH_TFP ETH_FP NDD

Ethernet OAM (May 18, 2004) [Dinesh Mohan] - 15 Maintenance Entities – CPE based Network Demarcation Access All MEs may not be needed always

Ethernet OAM (May 18, 2004) [Dinesh Mohan] - 16 Service/Network OAM – How does it come together? Ethernet link OAM PW/MPLS OAM EoSONET OAM Other OAM Network OAM Service OAM Transport Links Network Services OAM Interworking possible to utilize OAM across Layers However, each layer must support OAM capabilities independently