How to independently verify a carrier Ethernet (Layer 2) SLA

A carrier Ethernet SLA is written in frame loss ratio, frame delay and frame delay variation, per class of service. To verify it independently means measuring those metrics on the line yourself, rather than accepting the carrier's own report, and keeping the evidence to settle a dispute.

What a Layer 2 SLA is actually written in

Carrier Ethernet SLAs, following the MEF framework, are defined in frame loss ratio (FLR), frame delay (FD), frame delay variation (FDV) and availability, usually per class of service. These are the numbers the contract turns on, not “uptime.”

Why the carrier’s own report isn’t enough

The provider measures its own service and reports its own score. “SLA met” is a self-assessment, computed on the provider’s terms. When a credit is at stake, that is not a position a buyer wants to be in, and it’s the oldest asymmetry in the market.

How to measure Layer 2 independently

The L2 metrics can be measured without taking the carrier’s word for them, through ITU-T Y.1731 performance monitoring, IEEE 802.1ag continuity checks, TWAMP where the equipment speaks IP, or SNMP from the NID or CPE. The measurement is taken on the line itself, independent of the provider’s reporting.

Turning measurement into proof

Measurement alone starts an argument; measurement with its working attached tends to end one. Independent L2 measurements, recorded deterministically with the raw data, the contract terms and the calculation, become evidence that can be reproduced and defended, rather than a figure to be disputed.

How XVOLV does it

Parallax ingests the Layer 2 measurement, by polling Y.1731 or TWAMP, an API push, or the carrier’s own OAM, and brings it into the same deterministic evidence engine it uses for Layer 3, on the same circuit. The engine is source-agnostic: it computes the service level the same way whatever layer the measurement comes from, which is what makes the record layer-aware proof rather than a second, separate report. The result is an independent, reproducible record of what the Layer 2 service actually delivered. The method is set out in the white papers The Accountable Line and Proof by Rule.

Frequently asked questions

What is a MEF carrier Ethernet SLA?

A carrier Ethernet SLA defined under the MEF framework, written in frame loss ratio, frame delay and frame delay variation, usually per class of service, rather than in a single uptime figure. These are the metrics the contract and any credit turn on.

Can I verify it without the carrier's cooperation?

Yes. The Layer 2 metrics can be measured on the line independently, through Y.1731 performance monitoring, 802.1ag continuity checks, TWAMP where the equipment speaks IP, or SNMP from the NID or CPE, without relying on the carrier’s own reporting.

What equipment is needed to measure Y.1731?

Y.1731 performance monitoring is a function of carrier Ethernet equipment, the NID, CPE or a service-OAM-capable device at the service endpoints. Where the equipment speaks IP, TWAMP offers an alternative, and SNMP can read counters from the NID or CPE.

How is this different from the carrier's report?

The carrier’s report is a self-assessment: it measures its own service and scores it on its own terms. Independent verification measures the same metrics on the line yourself and records them deterministically, so the result is reproducible and defensible rather than a figure to be taken on trust.

Sources

• MEF, service OAM and carrier Ethernet SLA specifications. mef.net
• ITU-T Y.1731, OAM functions and mechanisms for Ethernet-based networks. itu.int
• RFC 5357, A Two-Way Active Measurement Protocol (TWAMP). rfc-editor.org