Piotr Zuraniewski, piotr.zuraniewski@tno.

nl
Borgert van der Kluit, borgert.vanderkluit@tno.nl
Erik Ruiter, erik.ruiter@surfsara.nl

Carrier Ethernet: QoS and OAM features Freek Dijkstra, freek.dijkstra@surfsara.nl

Richa Malhotra, richa.malhotra@surfnet.nl
Michel Mandjes, m.r.h.mandjes@uva.nl

Quality of Service (QoS) Example: two Customers with different requirements sharing a link –
With Carrier Ethernet, multiple achievement of bandwidth guarantees (QoS) and delay monitoring (via OAM)
classes of service can be offered, • Customer 1 starts transmission; • Customer 2 starts transmission; he can take over up to • Customer 1 stops transmission;
• Up to 100Mbps of his traffic is 80Mbps capacity (guaranteed, but no more than this); • Customer 2 can transfer up to
for example: transported • Customer 1 can now transfer up to 20Mbps (guaranteed); 80Mbps but no more;
• 20 Mbps is guaranteed and the rest • Rest of Customer 1 traffic is dropped (best-effort) • 20Mbps of free capacity is left
• High Priority: Guaranteed (up to link capacity) is best-effort
bandwidth, minimal delay and

link capacity used [%]

100
jitter (e.g., lightpath) 80

(cumulative)
60
• Low Priority: Bandwidth with 40
partial guarantees (e.g., 20
0
regular IP connection) 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40

Customer 1 Customer 2 time [m]

congestion phase
SLA monitoring using OAM 25

With Carrier Ethernet, customers can be

2-way delay [ms]

20

offered: 15

10
• More detailed reports on Service
5
Level Agreement (SLA) Key
0 Larger packet sizes
Performance Indicators, such as loss, 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40
jitter, delay, availability time [m]
Customer 1 Customer 2
• Near real-time insight into end-to-
end and intermediate link status • Congestion results in queue building up and thus delay
• …or any combination of these two in • Packet size increase results in even larger queue (in bytes) and then higher delays
an effective and (cost) efficient • By using OAM measurements, Customers can verify if delay still meets SLA
implementation