Technical Specification

MEF 14

Abstract Test Suite

for
Traffic Management Phase 1

November, 2005

MEF 14 © The Metro Ethernet Forum 2005. Any reproduction of this document, or any portion thereof, shall
contain the following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of
this document is authorized to modify any of the information contained herein.
 Disclaimer

The information in this publication is freely available for reproduction and use by any recipient
and is believed to be accurate as of its publication date. Such information is subject to change
without notice and the Metro Ethernet Forum (MEF) is not responsible for any errors. The MEF
does not assume responsibility to update or correct any information in this publication. No re-
presentation or warranty, expressed or implied, is made by the MEF concerning the complete-
ness, accuracy, or applicability of any information contained herein and no liability of any kind
shall be assumed by the MEF as a result of reliance upon such information.

The information contained herein is intended to be used without modification by the recipient or
user of this document. The MEF is not responsible or liable for any modifications to this docu-
ment made by any other party.

The receipt or any use of this document or its contents does not in any way create, by implication
or otherwise:

(a) any express or implied license or right to or under any patent, copyright, trademark or
trade secret rights held or claimed by any MEF member company which are or may be
associated with the ideas, techniques, concepts or expressions contained herein; nor

(b) any warranty or representation that any MEF member companies will announce any
product(s) and/or service(s) related thereto, or if such announcements are made, that such
announced product(s) and/or service(s) embody any or all of the ideas, technologies, or
concepts contained herein; nor

(c) any form of relationship between any MEF member companies and the recipient or user
of this document.

Implementation or use of specific Metro Ethernet standards or recommendations and MEF speci-
fications will be voluntary, and no company shall be obliged to implement them by virtue of par-
ticipation in the Metro Ethernet Forum. The MEF is a non-profit international organization acce-
lerating industry cooperation on Metro Ethernet technology. The MEF does not, expressly or
otherwise, endorse or promote any specific products or services.

© The Metro Ethernet Forum 2005. All Rights Reserved.

MEF 14 © The Metro Ethernet Forum 2005. Any reproduction of this document, or any portion thereof, shall
contain the following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of
this document is authorized to modify any of the information contained herein.
 Abstract Test Suite for Traffic Management Phase 1

Table of Contents
1. Abstract ................................................................................................................................ 1

2. Terminology......................................................................................................................... 1

3. Scope..................................................................................................................................... 4

4. Compliance Levels .............................................................................................................. 5

5. Introduction ......................................................................................................................... 5

6. Test Configuration .............................................................................................................. 7

7. Template for Abstract Test Cases for Traffic Management ........................................... 9

8. Abstract Test Cases for EVC Related Performance Service Attributes ...................... 10

9. Abstract Test Cases for Bandwidth Profiles Service Attributes .................................. 14

10. References .......................................................................................................................... 22

List of Figures
Figure 1; Relationship between different MEF Service Group documents and the Ethernet Services Test Definition
Documents ...........................................................................................................................................................5
Figure 2: Relationship between Ethernet Service Documents and Abstract Test Cases for Ethernet Services at the
UNI ......................................................................................................................................................................6
Figure 3: Test Configuration for Ethernet Services at the UNI .....................................................................................7
Figure 4: CE-VLAN ID/EVC Maps for the ingress and egress UNIs ..........................................................................8
Figure 5: Bandwidth Profile Service Attributes.............................................................................................................8
Figure 6: EVC Performance Service Attributes.............................................................................................................8

List of Test Cases

Test Case 1: Frame Delay Service Performance .......................................................................................................... 11
Test Case 2: Frame Delay Variation Service Performance .......................................................................................... 12
Test Case 3: Frame Loss Ratio Service Performance .................................................................................................. 13
Test Case 4: Bandwidth Profile Rate Enforcement when CIR > 0 and EIR = 0 .......................................................... 15
Test Case 5: Bandwidth Profile Rate Enforcement when CIR = 0 and EIR > 0 .......................................................... 16
Test Case 6: Bandwidth Profile Rate Enforcement when CIR > 0 and EIR > 0 .......................................................... 17
Test Case 7: Bandwidth Profile per Ingress UNI ......................................................................................................... 18
Test Case 8: Bandwidth Profile per EVC .................................................................................................................... 19
Test Case 9: Bandwidth Profile per Class of Service .................................................................................................. 20
Test Case 10: Multiple Bandwidth Profiles at the UNI ............................................................................................... 21

MEF 14 © The Metro Ethernet Forum 2005. Any reproduction of this document, or any portion thereof, shall Page i
contain the following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of
this document is authorized to modify any of the information contained herein.
 Abstract Test Suite for Traffic Management Phase 1

1. Abstract

This document defines the requirements and corresponding test procedures for Service Perfor-
mance and Bandwidth Profile Service Attributes that may be specified as part of a Service Level
Specification (SLS) for an Ethernet Service. Requirements are derived from Metro Ethernet Fo-
rum Technical Committee documents.

2. Terminology
All to One Bundling A UNI attribute in which all CE-VLAN IDs are associated with a
single EVC.
Bandwidth Profile A characterization of ingress Service Frame arrival times and
lengths at a reference point and a specification of the disposition
of each Service Frame based on its level of compliance with the
Bandwidth Profile. In this document the reference point is the
UNI.
Broadcast Service Frame A Service Frame that has the broadcast destination MAC ad-
dress.
Bundling A UNI attribute in which more than one CE-VLAN ID can be as-
sociated with an EVC.
CBS Committed Burst Size
CE Customer Edge
CE-VLAN CoS Customer Edge VLAN CoS
CE-VLAN ID Customer Edge VLAN ID
CE-VLAN ID Preservation An EVC attribute in which the CE-VLAN ID of an egress Service
Frame is identical in value to the CE-VLAN ID of the correspond-
ing ingress Service Frame.
CE-VLAN ID/EVC Map An association of CE-VLAN IDs with EVCs at a UNI.
CE-VLAN Tag Customer Edge VLAN Tag
CF Coupling Flag
CIR Committed Information Rate
Class of Service A set of Service Frames that have a commitment from the Ser-
vice Provider to receive a particular level of performance.
Class of Service Identifier Information derivable from a) the EVC to which the Service
Frame is mapped or b) the combination of the EVC to which the
Service Frame is mapped and a set of one or more CE-VLAN
CoS values.
CM Color Mode

MEF 14 © The Metro Ethernet Forum 2005. Any reproduction of this document, or any portion thereof, shall Page 1
contain the following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of
this document is authorized to modify any of the information contained herein.
 Abstract Test Suite for Traffic Management Phase 1

Color Mode CM is a Bandwidth Profile parameter. The Color Mode parameter

indicates whether the color-aware or color-blind property is em-
ployed by the Bandwidth Profile. It takes a value of “color-blind”
or “color-aware” only.
Color-aware A Bandwidth Profile property where a pre-determined level of
Bandwidth Profile compliance for each Service Frame is taken
into account when determining the level of compliance for each
Service Frame.
Color-blind A Bandwidth Profile property where a pre-determined level of
Bandwidth Profile compliance for each Service Frame, if present,
is ignored when determining the level of compliance for each
Service Frame.
Committed Burst Size CBS is a Bandwidth Profile parameter. It limits the maximum
number of bytes available for a burst of ingress Service Frames
sent at the UNI speed to remain CIR-conformant.
Committed Information CIR is a Bandwidth Profile parameter. It defines the average rate
Rate in bits/s of ingress Service Frames up to which the network deliv-
ers Service Frames and meets the performance objectives de-
fined by the CoS Service Attribute.
Coupling Flag CF is a Bandwidth Profile parameter. The Coupling Flag allows
the choice between two modes of operations of the rate en-
forcement algorithm. It takes a value of 0 or 1 only.
Customer Edge Equipment on the Subscriber side of the UNI.
Customer Edge VLAN CoS The user priority bits in the IEEE 802.1Q Tag in a Service Frame
that is either tagged or priority tagged.
Customer Edge VLAN ID The identifier derivable from the content of a Service Frame that
allows the Service Frame to be associated with an EVC at the
UNI.
Customer Edge VLAN Tag The IEEE 802.1Q Tag in a tagged Service Frame.
EBS Excess Burst Size
Egress Service Frame A Service Frame sent from the Service Provider network to the
CE.
EIR Excess Information Rate
E-LAN Service Ethernet LAN Service
E-Line Service Ethernet Line Service
Ethernet LAN Service An Ethernet Service Type distinguished by its use of a Multipoint-
to-Multipoint EVC.
Ethernet Line Service An Ethernet Service Type distinguished by its use of a Point-to-
Point EVC.
Ethernet Virtual Connec- An association of two or more UNIs that limits the exchange of
tion Service Frames to UNIs in the Ethernet Virtual Connection.

MEF 14 © The Metro Ethernet Forum 2005. Any reproduction of this document, or any portion thereof, shall Page 2
contain the following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of
this document is authorized to modify any of the information contained herein.
 Abstract Test Suite for Traffic Management Phase 1

EVC Ethernet Virtual Connection

Excess Burst Size EBS is a Bandwidth Profile parameter. It limits the maximum
number of bytes available for a burst of ingress Service Frames
sent at the UNI speed to remain EIR-conformant.
Excess Information Rate EIR is a Bandwidth Profile parameter. It defines the average rate
in bits/s of ingress Service Frames up to which the network may
deliver Service Frames without any performance objectives.
FD Frame Delay
FDV Frame Delay Variation
FLR Frame Loss Ratio
Frame Short for Ethernet frame.
Frame Delay The time required to transmit a Service Frame from source to
destination across the metro Ethernet network.
Frame Delay Performance A measure of the delays experienced by different Service
Frames belonging to the same CoS instance.
Frame Delay Variation The difference in delay of two Service Frames.
Frame Delay Variation A measure of the variation in the delays experienced by different
Performance Service Frames belonging to the same CoS instance.
Frame Loss Ratio Perfor- Frame Loss Ratio is a measure of the number of lost frames in-
mance side the MEN. Frame Loss Ratio is expressed as a percentage.
Ingress Service Frame A Service Frame sent from the CE into the Service Provider net-
work.
Layer 2 Control Protocol A Service Frame that is used for Layer 2 control, e.g., Spanning
Service Frame Tree Protocol.
Layer 2 Control Protocol The process by which a Layer 2 Control Protocol Service Frame
Tunneling is passed through the Service Provider network without being
processed and is delivered unchanged to the proper UNI(s).
Multicast Service Frame A Service Frame that has a multicast destination MAC address.
Multipoint-to-Multipoint An EVC with two or more UNIs. A Multipoint-to-Multipoint EVC
EVC with two UNIs is different from a Point-to-Point EVC because one
or more additional UNIs can be added to it.
Point-to-Point EVC An EVC with exactly 2 UNIs.
Service Frame An Ethernet frame transmitted across the UNI toward the Service
Provider or an Ethernet frame transmitted across the UNI toward
the Subscriber.
Service Level Agreement The contract between the Subscriber and Service Provider speci-
fying the agreed to service level commitments and related busi-
ness agreements.

MEF 14 © The Metro Ethernet Forum 2005. Any reproduction of this document, or any portion thereof, shall Page 3
contain the following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of
this document is authorized to modify any of the information contained herein.
 Abstract Test Suite for Traffic Management Phase 1

Service Level Specifica- The technical specification of the service level being offered by
tion the Service Provider to the Subscriber.
Service Multiplexing A UNI service attribute in which the UNI can be in more than one
EVC instance.
Service Provider The organization providing Ethernet Service(s).
SLA Service Level Agreement
SLS Service Level Specification
Subscriber The organization purchasing and/or using Ethernet Services.
UNI User Network Interface
Unicast Service Frame A Service Frame that has a unicast destination MAC address.
User Network Interface The physical demarcation point between the responsibility of the
Service Provider and the responsibility of the Subscriber.

3. Scope

This document defines the requirements and corresponding test procedures for Service Perfor-
mance and Bandwidth Profile Service Attributes that may be specified as part of a Service Level
Specification (SLS) for an Ethernet Service. As with MEF 9 Abstract Test Suite for Ethernet
Services at the UNI [3], the tests in this specification are defined from the point of view of the
Subscriber’s equipment that is used to access the services.

The requirements defined in this document are based on Sections 6.7 and 7.10 of MEF 10 Ether-
net Services Attributes Phase 1 [1]. Section 6.7 of MEF 10 [1] defines three EVC Related Per-
formance Service Attributes: Frame Delay Performance, Frame Delay Variation Performance,
and Frame Loss Ratio Performance. Section 7.10 of MEF 10 defines Bandwidth Profile Service
Attributes of an Ethernet Service at the UNI. Bandwidth Profiles Service Attributes are defined
per Ingress UNI, per EVC, and per Class of Service. Six parameters are applied to Bandwidth
Profiles: Committed Information Rate (CIR), Committed Burst Size (CBS), Excess Information
Rate (EIR), Excess Burst Size (EBS), Coupling Flag (CF) and Color Mode (CM). In the absence
of a standard way to color Service Frames, tests are not defined in relation to CF and CM para-
meters that may be applied to a Bandwidth Profile. Such tests may be added in the future when
Service Frame Coloring is further specified.

When combined with MEF 9 [3], this specification covers all of the EVC and UNI related Ser-
vice Attributes specified in MEF 10 [1]. Together they provide a comprehensive set of Test
Cases to determine the readiness of a Metro Ethernet Network (MEN) to deliver various Ethernet
Services, such as Ethernet Line (E-Line) and Ethernet LAN (E-LAN) services when Service Per-
formance and Bandwidth Profile Service Attributes are specified.

Implementation specifications are outside the scope of this document. This document may be
updated in the future to reflect new work in the MEF Technical Committee.

MEF 14 © The Metro Ethernet Forum 2005. Any reproduction of this document, or any portion thereof, shall Page 4
contain the following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of
this document is authorized to modify any of the information contained herein.
 Abstract Test Suite for Traffic Management Phase 1

4. Compliance Levels

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [5]. All key words must be in upper
case, bold text.

5. Introduction

This document completes MEF 9 [3] by adding requirements and test procedures for Service Per-
formance and Bandwidth Profile Service Attributes defined in MEF 10 [1]. As with MEF 9,
vendors can refer to the requirements and test procedures defined in this specification in the de-
velopment and commercial cycles of their products, carriers can use them to ensure that the net-
works they deploy will have the ability to deliver Ethernet Services that support Service Level
Specifications defined by the Technical Committee of the Metro Ethernet Forum and subscribers
can attach to the MEN knowing that the Ethernet Services they access satisfy criteria based on
accepted requirements and test procedures.

The definition of the requirements a MEN must satisfy to deliver Services to which Traffic and
Performance parameters are applied is tightly based on the MEF 10 [1]. The Ethernet Service
Definition Framework was created by the Metro Ethernet Forum (MEF) to provide the service
attributes and parameters to create an Ethernet service. The relationship between the Ethernet
Services Test Definition documents and the two MEF services documents is illustrated in Figure
1.

MEF 6 Ethernet
Services Definitions

MEF 10 Ethernet MEF 9 & MEF 14 Ethernet Ser-

Services Attributes Phase 1 vices Test Definitions

Figure 1: Relationship between different MEF Services Group documents and the Ethernet
Services Test Definition Documents

MEF 14 © The Metro Ethernet Forum 2005. Any reproduction of this document, or any portion thereof, shall Page 5
contain the following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of
this document is authorized to modify any of the information contained herein.
 Abstract Test Suite for Traffic Management Phase 1

The fundamental service constructs defined in MEF 10 [1] are Ethernet Service Types. These
have two types of Service Attributes associated with them, those associated with the UNI, and
those associated with the EVC. This specification defines requirements and test procedures
based on the Performance Service Attributes which are associated with the EVC and on the
Bandwidth Profile Service Attributes which are associated with the UNI. MEF 10 [1] also de-
fines the type of parameter values associated with each of these Service Attributes.

A conceptual schematic of the relationship between the MEF Technical Committee Ethernet
Services documents and the derived MEN requirements and correspondingly defined test defini-
tions is represented in Figure 2.

ETHERNET SERVICES MODEL

ETHERNET SERVICES DEFI-

NITIONS

ETHERNET SERVICES ATTRIBUTES

MODEL LEVEL

MEN REQUIREMENTS
ETHERNET SERVICES PARAME-
SERVICE LEVEL TERS

MEN REQUIREMENTS
ATTRIBUTE LEVEL
MODEL LEVEL
MEN REQUIREMENTS
TEST DEFINITIONS
PARAMETER LEVEL
SERVICE LEVEL
MEN REQUIREMENTS
TEST DEFINITIONS
ATTRIBUTE LEVEL

TEST DEFINTIONS
PARAMETER LEVEL

TEST DEFINITIONS

Figure 2: Relationship between Ethernet Service Documents and Abstract Test Cases for
Ethernet Services at the UNI

MEF 14 © The Metro Ethernet Forum 2005. Any reproduction of this document, or any portion thereof, shall Page 6
contain the following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of
this document is authorized to modify any of the information contained herein.
 Abstract Test Suite for Traffic Management Phase 1

6. Test Configuration

Although some tests may require very specific test configurations, most tests defined in this doc-
ument are to be executed by attaching the Ethernet interface or interfaces of a Tester to the
Ethernet interface or interfaces at the UNI. Since the UNI is the physical demarcation point
which delimits the responsibilities of the Subscriber and the Service Provider, the Tester attached
in this way sees a MEN from the point of view of the Subscriber’s equipment and can test a
MEN’s ability to offer Ethernet Services to the Subscriber. We schematically represent the at-
tachment of the Tester to the MEN in Figure 3

Test Configuration for Ethernet Services at the UNI

User Network User Network

Interface (UNI) Interface (UNI)

Testers gene- Testers gene-

rating Metro rating receiving
receiving moni- monitoring
Ethernet frames
toring Network
frames at the UNI
at the UNI

Testers physically attach to the MEN at the UNI

Testers may be attached to the MEN
at multiple UNIs

Figure 3: Test Configuration for Ethernet Services at the UNI

The Test Configuration for each Test Case describes the number of EVCs associating the number
of UNIs in the Test Case and the number of CE-VLAN IDs mapped to the EVCs. Testers are at-
tached to all UNIs in the configured EVCs in all Test Cases. CE-VLAN ID/EVC Maps are given
for each Test Case.

MEF 14 © The Metro Ethernet Forum 2005. Any reproduction of this document, or any portion thereof, shall Page 7
contain the following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of
this document is authorized to modify any of the information contained herein.
 Abstract Test Suite for Traffic Management Phase 1

In this document CE-VLAN ID/EVC Maps for the ingress and egress UNIs as in Figure 4, spe-
cific Bandwidth Profile Service Attributes as in Figure 5 and EVC Performance Service
Attributes as in Figure 6 are suggested for each Test Case.

INGRESS UNI ‘A’ EGRESS UNI ‘B’

CE-VLAN ID EVC CE-VLAN ID EVC
10 EVC 1 10 EVC 1
Use of other CE-VLAN IDs is permitted provided that configuration of the CE-VLAN
IDs conforms to MEF 10 [Ethernet Services Attributes Phase 1], Section 7.5.1

Figure 4: CE-VLAN ID/EVC Maps for the ingress and egress UNIs

Per Ingress UNI

UNI Bandwidth Profile Parameters
UNI A CIR A CBS A EIR A EBS A
Note 1 : (0 < CIR A ≤ UNI Speed), (CBS A ≥ maximum Service Frame size)

Figure 5: Bandwidth Profile Service Attributes

CoS Iden- Performance Ob-

EVC Performance Service Attributes
tifier jectives
Frame Delay (FD) Performance FD 1
1 Frame Delay Variation (FDV) Performance FDV 1
Frame Loss Ratio (FLR) Performance FLR 1

Figure 6: EVC Performance Service Attributes

MEF 14 © The Metro Ethernet Forum 2005. Any reproduction of this document, or any portion thereof, shall Page 8
contain the following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of
this document is authorized to modify any of the information contained herein.
 Abstract Test Suite for Traffic Management Phase 1

7. Template for Abstract Test Cases for Traffic Management

We adopt the following template for the definition of Abstract Test Cases for Management:
ABSTRACT TEST SUITE FOR TRAFFIC MANAGEMENT: PHASE 1
Test Name Name derived from reference document
A punctuated alphanumeric string assigned to each defined requirement and test procedure couple using the follow-
ing convention: ‘one to three letter abbreviated source document name’. ‘section number’ - ‘paragraph number in the
Test Definition ID section from which requirement is derived’. This number always figures as the last number of an ID. Ethernet Servic-
es Model=M; Ethernet Services Definitions=S. Example: M.6.1-4
Reference Doc-
Reference document and section (and paragraph when useful for clarity)
ument
Test Type Functional, Conformance, Interoperability or Performance
Test Status Mandatory, optional
Requirement
Brief description of the service requirement that the MEN MUST or SHOULD satisfy
Description
Test Object Succinct description of test purpose
Test Configura-
Succinct description of test bed configuration
tion

A sample VLAN ID/EVC Map is suggested. Variables augment it.

VLAN-ID/EVC INGRESS UNI ‘A’ EGRESS UNI ‘B’

Map CE-VLAN ID EVC CE-VLAN ID EVC
10 EVC 1 10 EVC 1
Use of other CE-VLAN IDs is permitted provided that configuration of the CE-VLAN
IDs conforms to MEF 10 [Ethernet Services Attributes Phase 1], Section 7.5.1

Bandwidth Pro- Per Ingress UNI

file UNI Bandwidth Profile Parameters
UNI A CIR A CBS A EIR A EBS A
Note 1 : (0 < CIR A ≤ UNI Speed), (CBS A ≥ maximum Service Frame size)

CoS Iden- Performance Ob-

Service Perfor- EVC Performance Service Attributes
tifier jectives
mance
Frame Delay (FD) Performance FD 1
1 Frame Delay Variation (FDV) Performance FDV 1
Frame Loss Ratio (FLR) Performance FLR 1

Test Procedure Succinct description of the test procedure. CE-VLAN ID/EVC Maps are provided for all tests.
Units can be time units, rates and counts in integers such as milliseconds, frames per second and numbers of valid
Units frames. For the most part units used are defined in RFCs 2285, 2544, 2889.
Variables Variables such as number of UNIs, EVCs and CE-VLAN IDs and frame formats and lengths MUST be described.
Description of the textual, numerical and/or graphical format in which to display test results. Results can be Pass or
Results Fail.
Remarks Description of any particular observations that might effect the test result

MEF 14 © The Metro Ethernet Forum 2005. Any reproduction of this document, or any portion thereof, shall Page 9
contain the following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of
this document is authorized to modify any of the information contained herein.
 Abstract Test Suite for Traffic Management Phase 1

8. Abstract Test Cases for EVC Related Performance Service

Attributes

In this section we assume familiarity with the MEF 10 Ethernet Services Attributes Phase 1 [1]
and, in particular, its section 6.7 which defines EVC Related Performance Service Attributes.
Abstract Test Cases based on the EVC Related Performance Service Attributes described in the
MEF 10 [1] are defined. There are three Test Cases defined in this section.
Test Case 1: Frame Delay Service Performance
Test Case 2: Frame Delay Variation Service Performance
Test Case 3: Frame Loss Ratio Service Performance

MEF 14 © The Metro Ethernet Forum 2005. Any reproduction of this document, or any portion thereof, shall Page 10
contain the following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of
this document is authorized to modify any of the information contained herein.
 Abstract Test Suite for Traffic Management Phase 1

Test Case 1: Frame Delay Service Performance

ABSTRACT TEST SUITE FOR TRAFFIC MANAGEMENT: PHASE 1
Test Name Frame Delay Service Performance
Test Definition
ID
M.6.7.1
Reference Doc-
ument
MEF 10 [Ethernet Services Attributes Phase 1]
Test Type Conformance
Test Status Mandatory
For all Service Frames declared Green and associated with a particular Class of Service
Requirement
Identifier on a Point-to-Point EVC that arrive at the UNI during a time interval T, Frame Delay
Description
Performance MUST be less than or equal to the Frame Delay Performance Objective
Verify that for all Service Frames declared Green and associated with a particular Class of
Test Object Service Identifier on a Point-to-Point EVC that arrive at the UNI during a time interval T,
Frame Delay Performance is less than or equal to the Frame Delay Performance Objective
At least one EVC associating at least two UNIs is configured and at least one Bandwidth Pro-
Test
Configuration
file with CIR > 0 is associated with at least one of the UNIs. Testers are attached to all UNIs
in the configured EVCs

INGRESS UNI ‘A’ EGRESS UNI ‘B’

CE-VLAN ID EVC CE-VLAN ID EVC
VLAN-ID/EVC
10 EVC 1 10 EVC 1
Map
Use of other CE-VLAN IDs is permitted provided that configuration of the CE-VLAN IDs
conforms to MEF 10 [Ethernet Services Attributes Phase 1], Section 7.5.1.

Per Ingress UNI

Bandwidth UNI Bandwidth Profile Parameters
Profile UNI A CIR A CBS A EIR A EBS A
Note 1 : (0 < CIR A ≤ UNI Speed), (CBS A ≥ maximum Service Frame size)

CoS Iden- Performance Objec-

EVC Performance Service Attributes
tifier tives
Service
Performance Frame Delay (FD) Performance FD 1
1

Tester offers Service Frames at the ingress UNI into the configured EVCs and measures Frame Delay as the time
elapsed from the reception of the first bit of the ingress Service Frame declared Green until the transmission of the
Test Procedure last bit of the Service Frame at the egress UNI. Frame Delay Performance is then calculated for a time interval T, as
the P-Percentile of the Frame Delay for all Service Frames successfully delivered between the UNI pairs. Service
Frames may be offered at an average rate up to CIR A
Units Time units
Bandwidth Profile Parameters CIR A, CBS A , EIR A, EBS A,, UNIs interface Speed, number of EVCs per UNI, number
Variables and values of CE-VLAN IDs, number and values of CoS ID, time interval T, Performance Objective FD 1
Results Pass or fail
Remarks

MEF 14 © The Metro Ethernet Forum 2005. Any reproduction of this document, or any portion thereof, shall Page 11
contain the following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of
this document is authorized to modify any of the information contained herein.
 Abstract Test Suite for Traffic Management Phase 1

Test Case 2: Frame Delay Variation Service Performance

ABSTRACT TEST SUITE FOR TRAFFIC MANAGEMENT: PHASE 1
Test Name Frame Delay Variation Service Performance
Test Definition
M.6.7.3
ID
Reference Doc-
MEF 10 [Ethernet Services Attributes Phase 1]
ument
Test Type Conformance
Test Status Mandatory
For all Service Frames declared Green and associated with a particular Class of Service Identifier on a Point-to-Point
Requirement
EVC that arrive at the UNI during a time interval T, Frame Delay Variation Performance MUST be less than or equal
Description to the Frame Delay Variation Performance Objective
Verify that for all Service Frames declared Green and associated with a particular Class of Service Identifier on a
Test Object Point-to-Point EVC that arrive at the UNI during a time interval T, Frame Delay Variation Performance is less than or
equal to the Frame Delay Variation Performance Objective
Test At least one EVC associating at least two UNIs is configured and at least one Bandwidth Profile with CIR > 0 is as-
Configuration sociated with at least one of the UNIs. Testers are attached to all UNIs in the configured EVCs

INGRESS UNI ‘A’ EGRESS UNI ‘B’

CE-VLAN ID EVC CE-VLAN ID EVC
VLAN-ID/EVC
10 EVC 1 10 EVC 1
Map
Use of other CE-VLAN IDs is permitted provided that configuration of the CE-VLAN IDs
conforms to MEF 10 [Ethernet Services Attributes Phase 1], Section 7.5.1.

Per Ingress UNI

Bandwidth UNI Bandwidth Profile Parameters
Profile UNI A CIR A CBS A EIR A EBS A
Note 1 : (0 < CIR A ≤ UNI Speed), (CBS A ≥ maximum Service Frame size)

CoS Iden- Performance Objec-

EVC Performance Service Attributes
tifier tives
Service
Performance Frame Delay Variation (FDV) Performance FDV 1
1

Tester offers Service Frames at the ingress UNI into the configured EVCs and measures Frame Delay Variation as
the variation in the Frame Delay between a pair of Green Service Frames. Frame Delay Variation Performance is
then calculated for a time interval T, as the P-Percentile of the difference between the frame delays of a Service
Frame pair that satisfies the following two characteristics:
Test Procedure
1. The two Service Frames that comprise the pair arrive at the ingress UNI within the time interval T
2. The two Service Frames that comprise the pair arrive at the ingress UNI exactly Δt time units apart

Service Frames may be offered at an average rate up to CIR A

Units Time units
Bandwidth Profile Parameters CIR A, CBS A , EIR A, EBS A,, UNIs interface Speed, number of EVCs per UNI, number
Variables and values of CE-VLAN IDs, number and values of CoS ID, time interval T, Performance Objective FDV 1
Results Pass or fail
Remarks

MEF 14 © The Metro Ethernet Forum 2005. Any reproduction of this document, or any portion thereof, shall Page 12
contain the following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of
this document is authorized to modify any of the information contained herein.
 Abstract Test Suite for Traffic Management Phase 1

Test Case 3: Frame Loss Ratio Service Performance

ABSTRACT TEST SUITE FOR TRAFFIC MANAGEMENT: PHASE 1
Test Name Frame Loss Ratio Service Performance
Test Definition
M.6.7.5
ID
Reference Doc-
MEF 10 [Ethernet Services Attributes Phase 1]
ument
Test Type Conformance
Test Status Mandatory
For all Service Frames declared Green and associated with a particular Class of Service Identifier on a Point-to-Point
Requirement
EVC that arrive at the UNI during a time interval T, Frame Loss Ratio Performance MUST be less than or equal to the
Description Frame Loss Ratio Performance Objective
Verify that for all Service Frames declared Green and associated with a particular Class of Service Identifier on a
Test Object Point-to-Point EVC that arrive at the UNI during a time interval T, Frame Loss Ratio Performance is less than or
equal to the Frame Loss Ratio Performance Objective
Test At least one EVC associating at least two UNIs is configured and at least one Bandwidth Profile with CIR > 0 is as-
Configuration sociated with at least one of the UNIs. Testers are attached to all UNIs in the configured EVCs

INGRESS UNI ‘A’ EGRESS UNI ‘B’

CE-VLAN ID EVC CE-VLAN ID EVC
VLAN-ID/EVC
10 EVC 1 10 EVC 1
Map
Use of other CE-VLAN IDs is permitted provided that configuration of the CE-VLAN IDs
conforms to MEF 10 [Ethernet Services Attributes Phase 1], Section 7.5.1.

Per Ingress UNI

Bandwidth UNI Bandwidth Profile Parameters
Profile UNI A CIR A CBS A EIR A EBS A
Note 1 : (0 < CIR A ≤ UNI Speed), (CBS A ≥ maximum Service Frame size)

CoS Iden- Performance Objec-

EVC Performance Service Attributes
tifier tives
Service
Performance 1 Frame Loss Ratio (FLR) Performance FLR 1

Tester offers Service Frames at the ingress UNI into the configured EVCs and over a time interval T counts the
number of Service Frames declared Green at the ingress UNI and successfully received at the egress UNI. Frame
Test Procedure Loss Ratio Performance is then calculated as the ratio, expressed as a percentage, of the number of Service Frames
declared Green not delivered at the egress UNI divided by the total number of such Service Frames. Service
Frames may be offered at an average rate up to CIR A
Units Number of Service Frames
Bandwidth Profile Parameters CIR A, CBS A , EIR A, EBS A,, UNIs interface Speed, number of EVCs per UNI, number
Variables and values of CE-VLAN IDs, number and values of CoS ID, time interval T, Performance Objective FLR 1
Results Pass or fail
Remarks

MEF 14 © The Metro Ethernet Forum 2005. Any reproduction of this document, or any portion thereof, shall Page 13
contain the following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of
this document is authorized to modify any of the information contained herein.
 Abstract Test Suite for Traffic Management Phase 1

9. Abstract Test Cases for Bandwidth Profiles Service Attributes

In this section we again assume familiarity with the MEF 10 [1] and, in particular, its section
7.10 which defines Bandwidth Profiles Service Attributes. Abstract Test Cases based on Band-
width Profiles Service Attributes described in the MEF 10 [1] are defined. There are seven Test
Cases defined in this section.

Test Case 4: Bandwidth Profile Rate Enforcement when CIR > 0 and EIR = 0
Test Case 5: Bandwidth Profile Rate Enforcement when CIR = 0 and EIR > 0
Test Case 6: Bandwidth Profile Rate Enforcement when CIR > 0 and EIR > 0
Test Case 7: Bandwidth Profile per Ingress UNI
Test Case 8: Bandwidth Profile per EVC
Test Case 9: Bandwidth Profile per Class of Service
Test Case 10: Multiple Bandwidth Profiles at the UNI

MEF 14 © The Metro Ethernet Forum 2005. Any reproduction of this document, or any portion thereof, shall Page 14
contain the following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of
this document is authorized to modify any of the information contained herein.
 Abstract Test Suite for Traffic Management Phase 1

Test Case 4: Bandwidth Profile Rate Enforcement when CIR > 0 and EIR = 0
ABSTRACT TEST SUITE FOR TRAFFIC MANAGEMENT: PHASE 1
Test Name Bandwidth Profile Rate Enforcement when CIR > 0 and EIR = 0
Test Definition
M.7.10.2.1-2
ID
Reference Doc-
MEF 10 [Ethernet Services Attributes Phase 1]
ument
Test Type Conformance
Test Status Mandatory
When a Bandwidth Profile is associated with a UNI, with a CIR > 0 and an EIR = 0, the amount of traffic delivered at
Requirement
the egress UNI MUST NOT exceed the amount of traffic accepted as Green (W G ) at the ingress UNI during a time
Description interval T, provided that the ingress traffic is greater than W G
Verify that when a Bandwidth Profile is associated with a UNI, with a CIR > 0 and an EIR = 0, the amount of traffic
Test Object delivered at the egress UNI does not exceed the amount of traffic accepted as Green (W G ) at the ingress UNI during
a time interval T, provided that the ingress traffic is greater than W G
Test At least one EVC associating at least two UNIs is configured and at least one Bandwidth Profile is applied at the UNI.
Configuration Testers are attached to all UNIs in the configured EVCs

INGRESS UNI ‘A’ EGRESS UNI ‘B’

CE-VLAN ID EVC CE-VLAN ID EVC
VLAN-ID/EVC
10 EVC 1 10 EVC 1
Map
Use of other CE-VLAN IDs is permitted provided that configuration of the CE-VLAN IDs
conforms to MEF 10 [Ethernet Services Attributes Phase 1], Section 7.5.1

Per Ingress UNI

UNI Bandwidth Profile Parameters
Bandwidth
UNI A CIR A CBS A EIR A EBS A
Profile
Note 1 : (0 < CIR A < UNI Speed), (CBS A ≥ maximum Service Frame size)
Note 2 : (EIR A = 0) and (EBS A = 0)

Service Not Specified

Performance
Tester offers Service Frames of length λ at an average rate greater than CIR A to the ingress UNI during a time inter-
val T and measures the number of Service Frames delivered at the egress UNI. The amount of traffic delivered at
the egress UNI must not exceed W G where:
Test Procedure
· W G is the amount of traffic accepted as Green over the time interval T that should be delivered to the egress
UNI
Units Number of valid Service Frames
Bandwidth Profile Parameters CIR A, CBS A , UNIs interface speed, number of UNIs, number of EVCs per UNI, type of
Variables EVC (Point-to-Point and Multipoint-to-Multipoint), number and values of CE-VLAN IDs, time interval T, number and
length λ of the offered Service Frames
Results Pass or fail
Remarks

MEF 14 © The Metro Ethernet Forum 2005. Any reproduction of this document, or any portion thereof, shall Page 15
contain the following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of
this document is authorized to modify any of the information contained herein.
 Abstract Test Suite for Traffic Management Phase 1

Test Case 5: Bandwidth Profile Rate Enforcement when CIR = 0 and EIR > 0
ABSTRACT TEST SUITE FOR TRAFFIC MANAGEMENT: PHASE 1
Test Name Bandwidth Profile Rate Enforcement when CIR = 0 and EIR > 0
Test Definition
M.7.10.2.1-2
ID
Reference Doc-
MEF 10 [Ethernet Services Attributes Phase 1]
ument
Test Type Conformance
Test Status Mandatory
When a Bandwidth Profile is associated with a UNI, with a CIR = 0 and an EIR > 0, the amount of traffic delivered at
Requirement
the egress UNI MUST NOT exceed the amount of traffic accepted as Yellow (W Y ) at the ingress UNI during a time
Description interval T, provided that the ingress traffic is greater than W Y
Verify that when a Bandwidth Profile is associated with a UNI, with a CIR = 0 and an EIR > 0, the amount of traffic
Test Object delivered at the egress UNI does not exceed the amount of traffic accepted as Yellow (W Y ) at the ingress UNI during
a time interval T, provided that the ingress traffic is greater than W Y
Test At least one EVC associating at least two UNIs is configured and at least one Bandwidth Profile is applied at the UNI.
Configuration Testers are attached to all UNIs in the configured EVCs

INGRESS UNI ‘A’ EGRESS UNI ‘B’

CE-VLAN ID EVC CE-VLAN ID EVC
VLAN-ID/EVC
10 EVC 1 10 EVC 1
Map
Use of other CE-VLAN IDs is permitted provided that configuration of the CE-VLAN IDs
conforms to MEF 10 [Ethernet Services Attributes Phase 1], Section 7.5.1

Per Ingress UNI

UNI Bandwidth Profile Parameters
Bandwidth
UNI A CIR A CBS A EIR A EBS A
Profile
Note 1 : (CIR A = 0) and (CBS A = 0)
Note 2 : (0 < EIR A < UNI Speed), (EBS A ≥ maximum Service Frame size)

Service Not Specified

Performance

Tester offers Service Frames of length λ at an average rate greater than EIR A to the ingress UNI during a time inter-
val T and measures the number of Service Frames delivered at the egress UNI. The amount of traffic delivered at
Test Procedure the egress UNI must not exceed W Y where:
· W Y is the amount of traffic accepted as Yellow over the time interval T that may be delivered to the egress UNI

Units Number of valid Service Frames

Bandwidth Profile Parameters EIR A, EBS A , UNIs interface speed, number of UNIs, number of EVCs per UNI, type of
Variables EVC (Point-to-Point and Multipoint-to-Multipoint), number and values of CE-VLAN IDs, time interval T, number and
length λ of the offered Service Frames
Results Pass or fail
Remarks

MEF 14 © The Metro Ethernet Forum 2005. Any reproduction of this document, or any portion thereof, shall Page 16
contain the following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of
this document is authorized to modify any of the information contained herein.
 Abstract Test Suite for Traffic Management Phase 1

Test Case 6: Bandwidth Profile Rate Enforcement when CIR > 0 and EIR > 0
ABSTRACT TEST SUITE FOR TRAFFIC MANAGEMENT: PHASE 1
Test Name Bandwidth Profile Rate Enforcement when CIR > 0 and EIR > 0
Test Definition
M.7.10.2.1-2
ID
Reference Doc-
MEF 10 [Ethernet Services Attributes Phase 1]
ument
Test Type Conformance
Test Status Mandatory
When a Bandwidth Profile is associated with a UNI, with a CIR > 0 and an EIR > 0, the amount of traffic delivered at
Requirement
the egress UNI MUST NOT exceed the amount of traffic accepted as Green (W G ) plus the amount of traffic accepted
Description as Yellow (W y ) at the ingress UNI during a time interval T, provided that the ingress traffic is greater than (W G + W y )
Verify that when a Bandwidth Profile is associated with a UNI, with a CIR > 0 and an EIR > 0, the amount of traffic
delivered at the egress UNI does not exceed the amount of traffic accepted as Green (W G ) plus the amount of traffic
Test Object accepted as Yellow (W y ) at the ingress UNI during a time interval T, provided that the ingress traffic is greater than
(W G + W y )
Test At least one EVC associating at least two UNIs is configured and at least one Bandwidth Profile is applied at the UNI.
Configuration Testers are attached to all UNIs in the configured EVCs

INGRESS UNI ‘A’ EGRESS UNI ‘B’

CE-VLAN ID EVC CE-VLAN ID EVC
VLAN-ID/EVC
10 EVC 1 10 EVC 1
Map
Use of other CE-VLAN IDs is permitted provided that configuration of the CE-VLAN IDs
conforms to MEF 10 [Ethernet Services Attributes Phase 1], Section 7.5.1

Per Ingress UNI

UNI Bandwidth Profile Parameters
Bandwidth
UNI A CIR A CBS A EIR A EBS A
Profile
Note 1 : (0 < CIR A < UNI Speed), (CBS A ≥ maximum Service Frame size)
Note 2 : (0 < EIR A < UNI Speed), (EBS A ≥ maximum Service Frame size)
Note 3 : (CIR A + EIR A < UNI Speed)

Service Not Specified

Performance
Tester offers Service Frames of length λ at an average rate greater than CIR A + EIR A to the ingress UNI during a
time interval T and measures the number of Service Frames delivered at the egress UNI. The amount of traffic deli-
vered at the egress UNI must not exceed (W G + W y ) where:

Test Procedure · W G is the amount of traffic accepted as Green over the time interval T that should be delivered to the
egress UNI
· W Y is the amount of traffic accepted as Yellow over the time interval T that may be delivered to the egress
UNI

Units Number of valid Service Frames

Bandwidth Profile Parameters CIR A, CBS A , EIR A, EBS A, UNIs interface speed, number of UNIs, number of EVCs per
Variables UNI, type of EVC (Point-to-Point and Multipoint-to-Multipoint), number and values of CE-VLAN IDs, time interval T,
number and length λ of the offered Service Frames
Results Pass or fail
Remarks

MEF 14 © The Metro Ethernet Forum 2005. Any reproduction of this document, or any portion thereof, shall Page 17
contain the following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of
this document is authorized to modify any of the information contained herein.
 Abstract Test Suite for Traffic Management Phase 1

Test Case 7: Bandwidth Profile per Ingress UNI

ABSTRACT TEST SUITE FOR TRAFFIC MANAGEMENT: PHASE 1
Test Name Bandwidth Profile per Ingress UNI
Test Definition
M.7.10.3
ID
Reference Doc-
MEF 10 [Ethernet Services Attributes Phase 1]
ument
Test Type Conformance
Test Status Mandatory
Requirement When a per Ingress UNI Bandwidth Profile is associated with a UNI, the Bandwidth Profile MUST be applied to all
Description ingress Service Frames at that UNI
Verify that when a per Ingress UNI Bandwidth Profile is associated with a UNI, the Bandwidth Profile is applied to all
Test Object ingress Service Frames at that UNI
At least two EVCs associating at least two UNIs are configured such that each associated UNI is in at least two
Test
EVCs and at least one CE-VLAN ID is mapped per EVC. A per Ingress UNI Bandwidth Profile is associated with at
Configuration least one of the UNIs. Testers are attached to all UNIs in the configured EVCs

INGRESS UNI ‘A’ EGRESS UNI ‘B’

CE-VLAN ID EVC CE-VLAN ID EVC
VLAN-ID/EVC 10 EVC 1 10 EVC 1
Map 12 EVC 2 12 EVC 2
Use of other CE-VLAN IDs is permitted provided that configuration of the CE-VLAN IDs
conforms to MEF 10 [Ethernet Services Attributes Phase 1], Section 7.5.1

Per Ingress UNI

UNI Bandwidth Profile Parameters
Bandwidth UNI A CIR A CBS A EIR A EBS A
Profile
Note 1 : (0 < CIR A < UNI Speed), (CBS A ≥ maximum Service Frame size)

Service
Not Specified
Performance
Tester offers Service Frames of length λ into the configured EVCs at the ingress UNI and verifies that over a time
interval T at least one Service Frame from each of the EVCs is delivered at the associated egress UNIs. Service
Frames are offered at equal average rates into each of the configured EVCs at the ingress UNI, at an aggregate
average rate greater than the CIR A. Tester also verifies that the amount of traffic delivered at the egress UNI does
not exceed (W G + W Y ) where:
Test Procedure
· W G is the amount of traffic accepted as Green over the time interval T that should be delivered to the
egress UNI
· W Y is the amount of traffic accepted as Yellow over the time interval T that may be delivered to the egress
UNI

Units Number of valid Service Frames

Bandwidth Profile Parameters CIR A, CBS A, EIR A, EBS A , UNIs interface speed, number of UNIs, number of EVCs per
Variables UNI, type of EVC (Point-to-Point and Multipoint-to-Multipoint), number and values of CE-VLAN IDs, time interval T,
number and length λ of the offered Service Frames
Results Pass or fail
Remarks

MEF 14 © The Metro Ethernet Forum 2005. Any reproduction of this document, or any portion thereof, shall Page 18
contain the following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of
this document is authorized to modify any of the information contained herein.
 Abstract Test Suite for Traffic Management Phase 1

Test Case 8: Bandwidth Profile per EVC

ABSTRACT TEST SUITE FOR TRAFFIC MANAGEMENT: PHASE 1
Test Name Bandwidth Profile per EVC
Test Definition
M.7.10.4
ID
Reference Doc-
MEF 10 [Ethernet Services Attributes Phase 1]
ument
Test Type Conformance
Test Status Mandatory
Requirement When a UNI is associated with a per EVC Bandwidth Profile, the Bandwidth Profile MUST be applied to all ingress
Description Service Frames at the UNI on that EVC
Verify that when a UNI is associated with a per EVC Bandwidth Profile, the Bandwidth Profile is applied to all ingress
Test Object Service Frames at the UNI on that EVC
At least two EVCs associating at least two UNIs are configured such that each associated UNI is in at least two of
Test
the same EVCs and at least one CE-VLAN ID is mapped per EVC. A per EVC Bandwidth Profile is associated with
Configuration at least one of the UNIs. Testers are attached to all UNIs in the configured EVCs

INGRESS UNI ‘A’ EGRESS UNI ‘B’

CE-VLAN ID EVC CE-VLAN ID EVC
VLAN-ID/EVC 10 EVC 1 10 EVC 1
Map 12 EVC 2 12 EVC 2
Use of other CE-VLAN IDs is permitted provided that configuration of the CE-VLAN IDs
conforms to MEF 10 [Ethernet Services Attributes Phase 1], Section 7.5.1

Per EVC
EVC Bandwidth Profile Parameters
EVC 1 CIR 1 CBS 1 EIR 1 EBS 1
Bandwidth
EVC 2 CIR 2 CBS 2 EIR 2 EBS 2
Profile
Note 1 : (CIR 1 = 0), (CBS 1 = 0) and (EIR 1 = 0) and (EBS 1 = 0)
Note 2 : (0 < CIR 2 < UNI Speed), (CBS 2 ≥ maximum Service Frame size)
Note 3 : (∑CIR < UNI Speed)

Service
Not Specified
Performance
Tester offers Service Frames of length λ into the configured EVCs at the ingress UNI during a time interval T, at an
aggregate average rate in excess of the sum of the CIRs of all the configured EVCs and measures the number of
Service Frames delivered at the egress UNI. For EVC 1 , the amount of traffic delivered at the egress UNI must be 0
and for every other configured EVC, the amount of traffic delivered at the egress UNI must not exceed (W G + W Y )
where:
Test Procedure
· W G is the amount of traffic accepted as Green over the time interval T that should be delivered to the
egress UNI
· W Y is the amount of traffic accepted as Yellow over the time interval T that may be delivered to the egress
UNI

Units Number of valid Service Frames

Bandwidth Profile Parameters CIR 2, CBS 2, EIR 2, EBS 2, UNIs interface speed, number of UNIs, number of EVCs per
Variables UNI, type of EVC (Point-to-Point and Multipoint-to-Multipoint), number and values of CE-VLAN IDs, time interval T,
number and length λ of the offered Service Frames
Results Pass or fail
Remarks

MEF 14 © The Metro Ethernet Forum 2005. Any reproduction of this document, or any portion thereof, shall Page 19
contain the following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of
this document is authorized to modify any of the information contained herein.
 Abstract Test Suite for Traffic Management Phase 1

Test Case 9: Bandwidth Profile per Class of Service

ABSTRACT TEST SUITE FOR TRAFFIC MANAGEMENT: PHASE 1
Test Name Bandwidth Profile per Class of Service
Test Definition
M.7.10.5
ID
Reference Doc-
MEF 10 [Ethernet Services Attributes Phase 1]
ument
Test Type Conformance
Test Status Mandatory
Requirement When a UNI is associated with a per Class of Service Bandwidth Profile, the Bandwidth Profile MUST be applied to
Description all ingress Service Frames at the UNI with that specific Class of Service Identifier
Verify that when a UNI is associated with a per Class of Service Bandwidth Profile, the Bandwidth Profile is applied
Test Object to all ingress Service Frames at the UNI with that specific Class of Service Identifier
At least one EVC associating at least two UNIs is configured and at least one CE-VLAN ID is mapped per EVC. A
Test Configura- per Class of Service Bandwidth Profile is associated with at least one of the UNIs. At least two CoS Identifiers are
tion used to identify the Class of Service applicable to the Service Frames offered at the UNI. Testers are attached to all
UNIs in the configured EVCs

INGRESS UNI ‘A’ EGRESS UNI ‘B’

CE-VLAN ID EVC CE-VLAN ID EVC
VLAN-ID/EVC 10 EVC 1 10 EVC 1
Map Use of other CE-VLAN IDs is permitted provided that configuration of the CE-VLAN IDs
conforms to MEF 10 [Ethernet Services Attributes Phase 1], Section 7.5.1

Per Class of Service

CoS Iden- CE-VLAN
EVC Bandwidth Profile Parameters
tifier CoS
Bandwidth 1 1 CIR 11 CBS 11 EIR 11 EBS 11
EVC 1
Profile 2 7 CIR 12 CBS 12 EIR 12 EBS 12
Note 1 : (CIR 11 = 0), (CBS 11 = 0) and (EIR 11 = 0) and (EBS 11 = 0)
Note 2 : (0 < CIR 12 < UNI Speed), (CBS 12 ≥ maximum Service Frame size)
Note 3 : (∑CIR < UNI Speed)

Service
Not Specified
Performance
Tester offers Service Frames of length λ into the configured EVCs at the ingress UNI during a time interval T, at an
aggregate average rate in excess of the sum of the CIRs of all the configured CoS IDs and measures the number of
Service Frames delivered at the egress UNI. For CoS ID 1, the amount of traffic delivered at the egress UNI must be
0 and for every other configured CoS ID, the amount of traffic delivered at the egress UNI must not exceed
(W G + W Y ) where:
Test Procedure
· W G is the amount of traffic accepted as Green over the time interval T that should be delivered to the
egress UNI
· W Y is the amount of traffic accepted as Yellow over the time interval T that may be delivered to the egress
UNI

Units Number of valid Service Frames

Bandwidth Profile Parameters CIR 12, CBS 12, EIR 12, EBS 12, UNIs interface Speed, number of UNIs, number of EVCs
per UNI, number of CoS Identifiers per EVC, type of EVC (Point-to-Point and Multipoint-to-Multipoint), number and
Variables values of CE-VLAN IDs, number and values of CE-VLAN CoS, time interval T, number and length λ of the offered
Service Frames
Results Pass or fail
Remarks

MEF 14 © The Metro Ethernet Forum 2005. Any reproduction of this document, or any portion thereof, shall Page 20
contain the following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of
this document is authorized to modify any of the information contained herein.
 Abstract Test Suite for Traffic Management Phase 1

Test Case 10: Multiple Bandwidth Profiles at the UNI

ABSTRACT TEST SUITE FOR TRAFFIC MANAGEMENT: PHASE 1
Test Name Multiple Bandwidth Profiles at the UNI
Test Definition
M.7.10.6
ID
Reference Doc-
MEF 10 [Ethernet Services Attributes Phase 1]
ument
Test Type Conformance
Test Status Optional
Requirement
Multiple models of Bandwidth Profile application MAY exist simultaneously at the UNI
Description
Test Object Verify that multiple models of Bandwidth Profile application can exist simultaneously at the UNI
At least two EVCs associating at least two UNIs are configured such that each associated UNI is in at least two of
Test the same EVCs and at least one CE-VLAN ID is mapped per EVC. A per EVC Bandwidth Profile and a per Class of
Configuration Service Bandwidth Profile are associated with at least one of the UNIs. Testers are attached to all UNIs in the confi-
gured EVCs

INGRESS UNI ‘A’ EGRESS UNI ‘B’

CE-VLAN ID EVC CE-VLAN ID EVC
VLAN-ID/EVC 10 EVC 1 10 EVC 1
Map 12 EVC 2 12 EVC 2
Use of other CE-VLAN IDs is permitted provided that configuration of the CE-VLAN IDs
conforms to MEF 10 [Ethernet Services Attributes Phase 1], Section 7.5.1

Per EVC
EVC Bandwidth Profile Parameters
EVC 1 CIR 1 CBS 1 EIR 1 EBS 1
Note 1 : (0 < CIR 1 < UNI Speed), (CBS 1 ≥ maximum Service Frame size)

Bandwidth Per Class of Service

Profile EVC
CoS Iden- CE-VLAN
Bandwidth Profile Parameters
tifier CoS
1 1 CIR 21 CBS 21 EIR 21 EBS 21
EVC 2
2 7 CIR 22 CBS 22 EIR 22 EBS 22
Note 2 : (CIR 21 = 0), (CBS 21 = 0) and (EIR 21 = 0), (EBS 21 = 0)
Note 3 : (0 < CIR 22 < UNI Speed), (CBS 22 ≥ maximum Service Frame size)
Note 4 : (∑CIR < UNI Speed)
Service
Not Specified
Performance
Tester offers Service Frames of length λ into the configured EVCs at the ingress UNI during a time interval T, at an
aggregate average rate in excess of the sum of the CIRs of all the configured EVCs and CoS IDs and measures the
number of Service Frames delivered at the egress UNI. For CoS ID 1, the amount of traffic delivered at the egress
UNI must be 0 and for every other configured EVC and CoS ID, the amount of traffic delivered at the egress UNI
must not exceed (W G + W Y ) where:
Test Procedure
· W G is the amount of traffic accepted as Green over the time interval T that should be delivered to the
egress UNI
· W Y is the amount of traffic accepted as Yellow over the time interval T that may be delivered to the egress
UNI

Units Number of valid Service Frames

Bandwidth Profile Parameters CIR 1, CBS 1, EIR 1, EBS 1, CIR 22, CBS 22, EIR 22, EBS 22, UNIs interface Speed, number of
UNIs, number of EVCs per UNI, number of CoS Identifiers per EVC, type of EVC (Point-to-Point and Multipoint-to-
Variables Multipoint), number and values of CE-VLAN IDs, number and values of CE-VLAN CoS, time interval T, number and
length λ of the offered Service Frames
Results Pass or fail
Remarks

MEF 14 © The Metro Ethernet Forum 2005. Any reproduction of this document, or any portion thereof, shall Page 21
contain the following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of
this document is authorized to modify any of the information contained herein.
 Abstract Test Suite for Traffic Management Phase 1

10. References
Reference Reference Details
[1] Ethernet Services
MEF 10 [Ethernet Services Attributes Phase 1]
Attributes Phase 1
[2] Services Definitions MEF 6 [Ethernet Services Definitions]
[3] Abstract Test Suite
for Ethernet Services at MEF 9 [Abstract Test Suite for Ethernet Services at the UNI]
the UNI

Information technology – Telecommunications and information exchange

between systems – Local and metropolitan area networks – Specific re-
[4] IEEE 802.3 – 2002 quirements – Part 3: Carrier sense multiple access with collision detection
(CSMA/CD) access method and physical layer specifications, 8 March
2002. (Normative)

RFC 2119, “Key words for use in RFCs to Indicate Requirement Levels”,
[5] RFC 2119
S. Bradner, http://www.ietf.org/rfc/rfc2119.txt (Normative)
RFC 2285, “Benchmarking Terminology for LAN Switching Devices”, R.
[6] RFC 2285
Mandeville, http://www.ietf.org/rfc/rfc2285.txt
RFC 2544, “Benchmarking Methodology for Network Interconnect Devic-
[7] RFC 2544
es”, S. Bradner, J. McQuaid, http://www.ietf.org/rfc/rfc2544.txt
RFC 2889, “Benchmarking Methodology for LAN Switching Devices”, R.
[8] RFC 2889
Mandeville, J. Perser, http://www.ietf.org/rfc/rfc2889.txt

MEF 14 © The Metro Ethernet Forum 2005. Any reproduction of this document, or any portion thereof, shall Page 22
contain the following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of
this document is authorized to modify any of the information contained herein.