Mef 9
Mef 9
October 2004
MEF 9
The Metro Ethernet Forum 2004. Any reproduction of this document, or any portion thereof, shall contain the following statement !"eproduced with permission of the Metro Ethernet Forum.! #o user of this document is authori$ed to modify any of the information contained herein.
Disclai er The information in this pu%lication is freely a&aila%le for reproduction and use %y any recipient and is %elie&ed to %e accurate as of its pu%lication date. 'uch information is su%(ect to change without notice and the Metro Ethernet Forum )MEF* is not responsi%le for any errors. The MEF does not assume responsi%ility to update or correct any information in this pu%lication. #o representation or warranty, e+pressed or implied, is made %y the MEF concerning the completeness, accuracy, or applica%ility of any information contained herein and no lia%ility of any ,ind shall %e assumed %y the MEF as a result of reliance upon such information. The information contained herein is intended to %e used without modification %y the recipient or user of this document. The MEF is not responsi%le or lia%le for any modifications to this document made %y any other party. The receipt or any use of this document or its contents does not in any way create, %y implication or otherwise )a* any e+press or implied license or right to or under any patent, copyright, trademar, or trade secret rights held or claimed %y any MEF mem%er company which are or may %e associated with the ideas, techni-ues, concepts or e+pressions contained herein. nor )%* any warranty or representation that any MEF mem%er companies will announce any product)s* and/or ser&ice)s* related thereto, or if such announcements are made, that such announced product)s* and/or ser&ice)s* em%ody any or all of the ideas, technologies, or concepts contained herein. nor )c* any form of relationship %etween any MEF mem%er companies and the recipient or user of this document. 0mplementation or use of specific Metro Ethernet standards or recommendations and MEF specifications will %e &oluntary, and no company shall %e o%liged to implement them %y &irtue of participation in the Metro Ethernet Forum. The MEF is a non1profit international organi$ation accelerating industry cooperation on Metro Ethernet technology. The MEF does not, e+pressly or otherwise, endorse or promote any specific products or ser&ices. The Metro Ethernet Forum 2004. All "ights "eser&ed.
MEF 9
The Metro Ethernet Forum 2004. Any reproduction of this document, or any portion thereof, shall contain the following statement !"eproduced with permission of the Metro Ethernet Forum.! #o user of this document is authori$ed to modify any of the information contained herein.
2age i
Table of !ontents
"# Abstract############################################################################################################################################################################" 2# Ter inolo$%####################################################################################################################################################################" &# Sco'e################################################################################################################################################################################2 4# !o 'liance (evels##########################################################################################################################################################& )# Intro*uction#####################################################################################################################################################################& +# Test ,e* Sche atics#######################################################################################################################################################) -# Te 'late for Abstract Test !ases for Ethernet Services at the UNI#########################################################################+ .# Abstract Test !ases for Ethernet Services at the UNI for E/! Service Attributes#################################################9# Abstract Test !ases for Ethernet Services at the UNI for UNI Service Attributes################################################22 "0# Securit%########################################################################################################################################################################&+ ""# 0eferences####################################################################################################################################################################&+
(ist of Fi$ures
Fi$ure "1 0elationshi' bet2een *ifferent MEF Services 3rou' *ocu ents an* the Ethernet Services Test Definition *ocu ent##############################################################################################################################################################################4 Fi$ure 21 0elationshi' bet2een Ethernet Services Docu ents an* Abstract Test !ases for Ethernet Services at the UNI#######################################################################################################################################################################################) Fi$ure &1 Test ,e* for Ethernet Services at the UNI#######################################################################################################+
(ist of Tables
Table "1 Sa 'le !E4/(AN ID5E/! Ma'#######################################################################################################################+ Table 21 Test Definition Te 'late####################################################################################################################################-
MEF 9
The Metro Ethernet Forum 2004. Any reproduction of this document, or any portion thereof, shall contain the following statement !"eproduced with permission of the Metro Ethernet Forum.! #o user of this document is authori$ed to modify any of the information contained herein.
2age ii
"##################################################################################Abstract
This document defines the re-uirements and corresponding test procedures that determine the readiness of a Metro Ethernet #etwor, )ME#* to deli&er &arious Ethernet 'er&ices, such as Ethernet 3ine )E13ine* and Ethernet 3A# )E13A#* ser&ices. "e-uirements are deri&ed from Metro Ethernet Forum Technical 4ommittee documents.
2#
Ter inolo$%
A 5#0 attri%ute in which all 4E163A# 07s are associated with a single E64. A characteri$ation of ingress 'er&ice Frame arri&al times and lengths at the 5#0. A 'er&ice Frame that has the %roadcast destination MA4 address. A 5#0 attri%ute in which more than one 4E163A# 07 can %e associated with an E64. 4ustomer Edge 4ustomer Edge 63A# 4o' 4ustomer Edge 63A# 07 An E64 attri%ute in which the 4E163A# 07 of an egress 'er&ice Frame is identical in &alue to the 4E163A# 07 of the corresponding ingress ser&ice Frame. An association of 4E163A# 07s with E64s at a 5#0. 4ustomer Edge 63A# Tag A set of 'er&ice Frames that ha&e a commitment from the 'er&ice 2ro&ider to recei&e a particular le&el of performance. 0nformation deri&a%le from a 'er&ice Frame that allows the identification of the 4lass of 'er&ice instance that applies to the 'er&ice Frame. E-uipment on the 'u%scri%er side of the 5#0. The user priority %its in the 0EEE 802.9: Tag in a tagged 'er&ice Frame. The identifier deri&a%le from the content of a 'er&ice Frame that allows the 'er&ice Frame to %e associated with an E64 at the 5#0. The 0EEE 802.9: Tag in a tagged 'er&ice Frame. Ethernet 3A# 'er&ice
All to One ,un*lin$ ,an*2i*th 6rofile ,roa*cast Service Fra e ,un*lin$ !E !E4/(AN !oS !E4/(AN ID !E4/(AN ID 6reservation !E4/(AN ID5E/! Ma' !E4/(AN Ta$ !lass of Service !lass of Service I*entifier !usto er E*$e !usto er E*$e /(AN !oS !usto er E*$e /(AN ID !usto er E*$e /(AN Ta$ E4(AN Service
E4(ine Service E$ress Service Fra e Ethernet (AN Service Ethernet (ine Service Ethernet /irtual !onnection E/! Fra e In$ress Service Fra e
Ethernet 3ine 'er&ice A 'er&ice Frame sent from the 'er&ice 2ro&ider networ, to the 4E. An Ethernet 'er&ice Type distinguished %y its use of a Multipoint1to1 Multipoint E64. An Ethernet 'er&ice Type distinguished %y its use of a 2oint1to12oint E64. An association of two or more 5#0s that limits the e+change of 'er&ice Frames to 5#0s in the Ethernet 6irtual 4onnection. Ethernet 6irtual 4onnection 'hort for Ethernet frame. A 'er&ice Frame sent from the 4E into the 'er&ice 2ro&ider networ,.
(a%er 2 !ontrol A 'er&ice Frame that is used for 3ayer 2 control, e.g., 'panning Tree 'rotocol Service Fra e 2rotocol. (a%er 2 !ontrol 'rotocol Tunnelin$ MEN Multicast Service Fra e Multi'oint4to4 Multi'oint E/! 6oint4to46oint E/! Service Fra e Service Multi'le7in$ Service 6rovi*er Subscriber Tester UNI Unicast Service Fra e The process %y which a 3ayer 2 4ontrol protocol 'er&ice Frame is passed through the 'er&ice 2ro&ider networ, without %eing processed and deli&ered unchanged to the proper 5#0)s*. Metro Ethernet #etwor, A 'er&ice Frame that has a multicast destination MA4 address. An E64 with two or more 5#0s. An E64 with e+actly 2 5#0s. An Ethernet frame transmitted across the 5#0 toward the 'er&ice 2ro&ider or an Ethernet frame transmitted across the 5#0 toward the 'u%scri%er. A 5#0 ser&ice attri%ute in which the 5#0 can %e in more than one E64 instance. The organi$ation pro&iding Ethernet 'er&ice)s*. The organi$ation purchasing and/or using Ethernet 'er&ices. 'pecial e-uipment used to generate and monitor traffic for &erification purposes. 5ser #etwor, 0nterface A 'er&ice Frame that has a unicast destination MA4 address.
User Net2or8 Interface The physical demarcation point %etween the responsi%ility of the 'er&ice 2ro&ider and the responsi%ility of the 'u%scri%er.
&#
Sco'e
This document defines the re-uirements and corresponding test procedures to -ualify the a%ility of a Metro Ethernet #etwor, to deli&er Ethernet ser&ices, such as E13ine and E13A# ser&ices as defined
%y the Metro Ethernet Forum. The tests are defined from the point of &iew of the 'u%scri%er;s e-uipment that is used to access the ser&ices. The goals of the test definitions are three1fold. The first goal is to pro&ide test procedures to 'u%scri%ers to help them ensure the successful integration of Ethernet 'er&ices into their o&erall networ,ing infrastructures. The second goal is to pro&ide test definitions to host, switch, and router &endors allowing them to ensure that their products can %e used in the ME# to allow 'u%scri%ers to successfully access Ethernet 'er&ices. The third is to pro&ide 'er&ice 2ro&iders with a suite of tests that allow them to determine the a%ility of the ME# to offer Ethernet 'er&ices conformant to Metro Ethernet Forum specifications. The re-uirements defined in this document are %ased on 'ections < and = of the Metro Ethernet Forum Technical 4ommittee Ethernet 'er&ices Model document >Ethernet 'er&ices Model?. "e-uirements and test procedures to -ualify the readiness of a ME# to support further ser&ices, attri%utes and parameters will %e defined in su%se-uent re&isions. This document does not define methods for the measurement or monitoring of 'er&ice 3e&el 'pecifications )'3's* %ut it does define test procedures which determine the readiness of a ME# to deli&er &arious '3's defined in >Traffic and 2erformance 2arameters for Ethernet 'er&ice 3e&el 'pecifications?. This document does not re1define metrics or testing methods descri%ed in any of the standards documents already defined %y such groups as the @enchmar,ing Methodology Aor,ing Broup )@MAB* of the 0nternet Engineering Tas, Force )0ETF*, howe&er metrics used in this document conform to @MAB definitions. 0mplementation specifications are outside the scope of this document. This document may %e updated in the future to reflect new wor, in the MEF Technical 4ommittee.
4#
!o 'liance (evels
The ,ey words CMUSTD, CMUST NOTD, C0E9UI0EDD, CS:A((D, CS:A(( NOTD, CS:OU(DD, CS:OU(D NOTD, C0E!OMMENDEDD, CMA;D, and CO6TIONA(D in this document are to %e interpreted as descri%ed in "F4 299E. All ,ey words MUST %e use upper case, %old te+t.
)# Intro*uction
This document descri%es the re-uirements and corresponding test procedures to %e used when testing the a%ility of a ME# to deli&er Ethernet 'er&ices, such as the E13ine and E13A# ser&ices defined in >Ethernet 'er&ices 7efinitions?. 6endors can refer to such re-uirements and test procedures in the de&elopment and commercial cycles of their products, carriers can use them to ensure that the de&ices or systems they select to deploy in the ME# will result in the successful deli&ery of Ethernet 'er&ices and su%scri%ers can attach to the ME# ,nowing that the Ethernet ser&ices they access satisfy criteria %ased on accepted re-uirements and test procedures. The definition of the re-uirements a ME# must satisfy to deli&er Metro Ethernet ser&ices is tightly %ased on the MEF 9 >Ethernet 'er&ices Model?, >Ethernet 'er&ices 7efinitions? and >Traffic and 2erformance 7efinitions? documents of the Technical 4ommittee of the Metro Ethernet Forum. The Ethernet 'er&ice 7efinition Framewor, was created %y the Metro Ethernet Forum )MEF* to pro&ide the ser&ice attri%utes and parameters to create an Ethernet ser&ice. The relationship %etween this document and the three MEF ser&ices documents is illustrated in Figure 9.
Fi$ure "1 0elationshi' bet2een *ifferent MEF Services 3rou' *ocu ents an* the Ethernet Services Test Definition *ocu ent 6arious types of criteria can %e used to esta%lish the re-uirements a ME# must satisfy to deli&er Ethernet ser&ices. This document refers to four such criteria functional, conformance, interopera%ility and performance. Functional criteria A ME# will ha&e to satisfy certain well1defined functional criteria some of which can %e safely ta,en for granted and others which it will %e useful to test. An e+ample of the latter would %e that a ME# correctly filters @275s )@ridge 2rotocol 7ata 5nits* when configured to do so. 4onformance criteria A ME# must also satisfy certain well1defined conformance criteria. An e+ample of this is that a ME# MUST NOT deli&er frames to the 5#0 on which they originated 0nteropera%ility criteria A further criteria is interopera%ility. An e+ample of this would %e the a%ility of a de&ice to participate in the same ar%itrary ME# as the de&ice of another &endor or, more generally, of other &endors. 2erformance criteria A ME# must also meet certain performance criteria. An e+ample of this would %e the a%ility to successfully forward a certain percentile of frames without loss. Functional, conformance and interopera%ility test results are typically reported as Fpass; or Ffail;, whereas performance test results are generally reported in terms of frame counts, such as num%ers of lost frames. times, such as mean time to reco&er in milliseconds. and rates, such as frames per second forwarding rates. The fundamental ser&ice constructs defined in >Ethernet 'er&ices Model? are Ethernet 'er&ice Types. These ha&e two types of 'er&ice Attri%utes associated with them, those associated with the 5#0, and those associated with the E64. The >Ethernet 'er&ices Model? also defines the type of parameter &alues associated with each of the 'er&ice Attri%utes. 0n order to successfully deli&er Ethernet 'er&ices, a ME# must first satisfy certain general re-uirements that the deli&ery of any Ethernet 'er&ice Type, Ethernet 'er&ice Attri%utes and Ethernet 'er&ice Attri%ute 2arameters associated with an Ethernet 'er&ice implies. These general re-uirements
are deri&ed from the MEF >Ethernet 'er&ices Model?. A ME# deli&ering specific Ethernet 'er&ices must satisfy additional re-uirements %ased on >Ethernet 'er&ices 7efinitions? and >Traffic and 2erformance 7efinitions?. A conceptual schematic of the relationship %etween the MEF Technical 4ommittee Ethernet 'er&ices documents and the deri&ed ME# re-uirements and correspondingly defined test definitions is represented in Figure 2.
ET!ERNET ET!ERNET SERVICES SERVICES MODEL MODEL
ET!ERNET ET!ERNET SERVICES SERVICES DEFINITIONS DEFINITIONS
ET!ERNET ET!ERNET SERVICES SERVICES ATTRIBUTES ATTRIBUTES
ET!ERNET ET!ERNETSERVICES SERVICES ARAMETERS ARAMETERS
Fi$ure 21 0elationshi' bet2een Ethernet Services Docu ents an* Abstract Test !ases for Ethernet Services at the UNI
+#
Although some tests may re-uire &ery specific test %ed configurations, most tests defined in this document are to %e e+ecuted %y attaching the Ethernet interface or interfaces of a Tester to the Ethernet interface or interfaces at the 5#0. 'ince the 5#0 is the physical demarcation point which delimits the responsi%ilities of the 'u%scri%er and the 'er&ice 2ro&ider, the Tester attached in this way sees a ME# from the point of &iew of the 'u%scri%er;s e-uipment and can test a ME#;s a%ility to offer Ethernet 'er&ices to the 'u%scri%er. Ae schematically represent the attachment of the Tester to the ME# in Figure G.
Testers physically attach to the MEN at the UNI Testers may be attached to the MEN at multiple UNIs
Fi$ure &1 Test ,e* for Ethernet Services at the UNI The Test @ed 4onfiguration for each Test 4ase descri%es the num%er of E64s associating the num%er of 5#0s in the Test 4ase and the num%er of 4E163A# 07s mapped to the E64s. Testers are attached to all 5#0s in the configured E64s in all Test 4ases. 4E163A# 07/E64 Maps are gi&en for each Test 4ase. 0n this document 4E163A# 07/E64 Map for the ingress and egress 5#0s are suggested for each Test 4ase IN30ESS UNI <A= !E4/(AN ID E/! E30ESS UNI <,= !E4/(AN E/! ID 90 E649 90 E649 5se of other 4E163A# 07s may %e permitted pro&ided that configuration of the 4E163A# 07s conforms to MEF 9, 'ection =.H.9. Table "1 Sa 'le !E4/(AN ID5E/! Ma'
-# Te 'late for Abstract Test !ases for Ethernet Services at the UNI
Ae adopt the following template for the definition of A%stract Test 4ases for Ethernet 'er&ices at the 5#0
Test )efinition I)
#eference )ocument !ource Test Type Test !tatus #e*uirement )escription Test &b+ect Test ed $onfiguration
#ame deri&ed from reference document A punctuated alphanumeric string assigned to each defined re-uirement and test procedure couple using the following con&ention Fone to three letter a%%re&iated source document name;. Fsection num%er; 1 Fparagraph num%er in the section from which re-uirement is deri&ed;. This num%er always figures as the last num%er of an 07. Ethernet 'er&ices ModelIM. Ethernet 'er&ices 7efinitionsI'. Traffic and 2erformance 2arameters for '3'sIT. E+ample M.<.914 "eference document and section )and paragraph when useful for clarity* Functional, 4onformance, 0nteropera%ility or 2erformance Mandatory, optional @rief description of the ser&ice re-uirement that the ME# MUST or S:OU(D satisfy 'uccinct description of test purpose 'uccinct description of test %ed configuration A sample 63A# 07/E64 Map is suggested. 6aria%les augment the Map. IN30ESS UNI <A= E30ESS UNI <,= !E4/(AN ID E/! !E4/(AN E/! ID 90 E649 90 E649 5se of other 4E163A# 07s may %e permitted pro&ided that configuration of the 4E163A# 07s conforms to MEF 9, 'ection =.H.9. 'uccinct description of the test procedure. 4E163A# 07/E64 Maps are pro&ided for all tests. 5nits can %e time units, rates and counts in integers such as milliseconds, frames per second and num%ers of &alid frames. For the most part units used are defined in "F4s 228H, 2H44, 288E. 6aria%les such as num%er of 5#0s, E64s and 4E163A# 07s and frame formats and lengths MUST %e descri%ed. 7escription of the te+tual, numerical and/or graphical format in which to display test results. "esults can %e 2ass or Fail. 7escription of any particular o%ser&ations that might effect the test result
.# Abstract Test !ases for Ethernet Services at the UNI for E/! Service Attributes
0n this section we assume familiarity with the MEF 9 >Ethernet 'er&ices Model? and, in particular, its section < which defines E64 'er&ice Attri%utes. A%stract Test 4ases %ased on the E64 'er&ice Attri%utes descri%ed in the Model are defined. There are thirteen Test 4ases defined in this section. Test 4ase 9 #on1looping Frame 7eli&ery
Test 4ase 2 E64 3ea,age Test 4ase G 'ingle 4opy @roadcast, Multicast, 5n,nown 7A Frame 7eli&ery in M21to1M2 E64 Test 4ase 4 'er&ice Frame with 0n&alid F4' 7iscard Test 4ase H 'er&ice Frame 7iscard 3ayer 2 4ontrol 2rotocols Test 4ase < 'er&ice Frame 4onditional 7eli&ery Test 4ase = 'er&ice Frame Transparency Tag E+ception 9 Test 4ase 8 'er&ice Frame Transparency Tag E+ception 2 Test 4ase E 'er&ice Frame transparency Tag E+ception G Test 4ase 90 4E163A# 07 2reser&ation 5ntagged Test 4ase 99 4E163A# 07 2reser&ation Tagged Test 4ase 92 4E163A# 4o' 2reser&ation Test 4ase 9G E64 3ayer 2 4ontrol 2rotocol 2rocessing The detailed Test 4ase definitions follow.
(,"N/I)-E($ Map
(,"N/I)-E($ Map
UNI <!= !E4/(AN ID E/! 22 E642222 2G E64222G 2G E64222G G9 E64M22M290 G2 E64M22M299 G2 E64M22M299 9. 5se of other 4E163A# 07s is permitted pro&ided that configuration of the 4E163A# 07s conforms to MEF 9, 'ection =.H.9. 2. 5nicast, %roadcast, multicast and un,nown destination MA4 address frames offered into 2oint1to12oint E642 MUST NOT %e deli&ered %y the ME# at 5#0s FA; or F7;. G. 5nicast, %roadcast, multicast and un,nown destination MA4 address frames offered into Multipoint1to1Multipoint E6490 MUST NOT %e deli&ered %y the ME# at 5#0 F7;. Tester offers unicast, %roadcast, multicast and un,nown destination MA4 address frames to at least one less than the num%er of configured E64s. All E64s are monitored to &erify that unicast, %roadcast, multicast and un,nown destination MA4 address frames are only recei&ed at the 5#0s in the E64 or E64s on which the tester offers frames. #um%er of &alid frames 5nicast, multicast, %roadcast, frame lengths. #um%er of 5#0s. #um%er of E64s per 5#0. Type of E64 )2oint1to12oint and Multipoint1to1Multipoint*. #um%er of 4E163A# 07s. 4E163A# 07 for untagged and priority frames. 2ass or fail
Test !ase &1 Sin$le !o'% ,roa*cast> Multicast> Un8no2n DA Fra e Deliver% in M64to4M6 E/!
Test Name Test )efinition I) #eference )ocument !ource Test Type Test !tatus #e*uirement )escription Test &b+ect Test ed $onfiguration " !T#"$T TE!T $"!E! %&# ET'E#NET !E#(I$E! "T T'E UNI 'ingle 4opy @roadcast, Multicast, 5n,nown 7A Frame 7eli&ery in M21to1M2 E64 M.<.9.219 MEF 9 Ethernet 'er&ices Model, 2hase 9 Functional Mandatory Jnly one copy of %roadcast, multicast and un,nown destination MA4 address frames should %e deli&ered to the egress 5#0s on a M21to1M2 E64 6erify that the ME# deli&ers a single copy of %roadcast, multicast and un,nown destination MA4 address ser&ice frames to each of the egress 5#0s in a Multipoint1to1Multipoint E64 At least one E64 associating at least two 5#0s is configured and at least one 4E163A# 07 is mapped to the E64. Testers are attached to all 5#0s in the configured E64s. IN30ESS UNI <A= E30ESS UNI <,= !E4/(AN ID E/! !E4/(AN ID E/! G0 E649 G0 E649 IN30ESS UNI <!= !E4/(AN ID E/! G0 E649 5se of other 4E163A# 07s is permitted pro&ided that configuration of the 4E163A# 07s conforms to MEF 9, 'ection =.H.9. Tester offers %roadcast, multicast and un,nown destination MA4 address frames to an ingress 5#0 in the M21to1M2 E64 and &erifies that only one copy of each offered frame is deli&ered at the egress 5#0s in the M21to1M2 E64. #um%er of &alid frames M21to1M2 E64s. #um%er of 5#0s. #um%er of 4E163A# 07s. @roadcast, multicast, un,nown destination MA4 address frames. Frame lengths. 2ass or fail
(,"N/I)-E($ Map
(,"N/I)-E($ Map
(,"N/I)-E($ Map
(ariables
#esults #emarks
@ridge @loc, of protocols, BA"2 @loc, of protocols, All @ridges 2rotocol are mandatory 2ass or fail
(,"N/I)-E($ Map
Tester offers 'er&ice Frames at at least one ingress 5#0 to at least one Multipoint1to1Multipoint E64 and &erifies that they are deli&ered at the destination MA4 address ,nown %y the ME# to %e CatD the destination 5#0. #um%er of &alid frames #um%er of 5#0s. #um%er of E64s per 5#0. #um%er of 4E163A# 07s. 2ass or fail
(,"N/I)-E($ Map
(,"N/I)-E($ Map
Test ed $onfiguration
(,"N/I)-E($ Map
(,"N/I)-E($ Map
Test ed $onfiguration
(,"N/I)-E($ Map
(,"N/I)-E($ Map
Test &b+ect
Test ed $onfiguration
(,"N/I)-E($ Map
(ariables
#esults #emarks
9# Abstract Test !ases for Ethernet Services at the UNI for UNI Service Attributes
0n this section we again assume familiarity with the MEF 9 >Ethernet 'er&ices Model? and, in particular, its section = which defines 5#0 'er&ice Attri%utes. A%stract Test 4ases %ased on the 5#0 'er&ice Attri%utes descri%ed in the Model are defined. There are thirteen Test 4ases defined in this section. Test 4ase 94 Test 4ase 9H Test 4ase 9< Test 4ase 9= Test 4ase 98 Test 4ase 9E Test 4ase 20 Test 4ase 29 Test 4ase 22 Test 4ase 2G Test 4ase 24 Test 4ase 2H Test 4ase 2< 5#0 2hysical 3ayer 5#0 MA4 3ayer 5#0 'er&ice Multiple+ing of 2oint1to12oint E64s 5#0 'er&ice Multiple+ing of Multipoint1to1Multipoint E64s 5#0 'er&ice Multiple+ing of 2oint1to12oint and Multipoint1to1Multipoint E64s 4E163A# 07 for untagged and priority tagged 'er&ice Frames 4E163A# 07/E64 Map 'er&ice Frame 7iscard 5#0 E64 'upport Ma+imum #um%er of E64s 5#0 @undling and 4E163A# 07 2reser&ation 5#0 All to Jne @undling and 4E163A# 07 2reser&ation 5#0 3ayer 2 4ontrol 2rotocols 2rocessing 7iscard 5#0 3ayer 2 4ontrol 2rotocols 2rocessing 2eer
(,"N/I)-E($ Map
(ariables
#esults #emarks
(,"N/I)-E($ Map
(,"N/I)-E($ Map
(,"N/I)-E($ Map
Test !ase ".1 UNI Service Multi'le7in$ of 6oint4to46oint an* Multi'oint4to4Multi'oint E/!s
Test Name Test )efinition I) #eference )ocument !ource Test Type Test !tatus #e*uirement )escription Test &b+ect Test ed $onfiguration " !T#"$T TE!T $"!E! %&# ET'E#NET !E#(I$E! "T T'E UNI 5#0 'er&ice Multiple+ing of 2oint1to12oint and Multipoint1to1Multipoint E64s M.=.4 MEF 9 Ethernet 'er&ices Model, 2hase 9 4onformance Mandatory A 5#0 with the 'er&ice Multiple+ing attri%ute MUST %e configura%le to support multiple 2oint1 to12oint and Multipoint1to1Multipoint E64s. 6erify that a 5#0 with the 'er&ice Multiple+ing attri%ute can %e configured to support multiple 2oint1to12oint and Multipoint1to1Multipoint E64s. At least one Multipoint1to1Multipoint E64 is configured associating at least two 5#0s and at least one 2oint1to12oint E64 is configured associating two 5#0s at least one of which is in the Multipoint1to1Multipoint E64 and at least one 4E163A# 07 is mapped to each of the E64s. Testers are attached to all 5#0s in the configured E64s. UNI <A= UNI <,= !E4/(AN ID E/! !E4/(AN ID E/! 400 E649 400 E649 490 E642 490 E642 UNI <!= !E4/(AN ID E/! 490 E642 5se of other 4E163A# 07s is permitted pro&ided that configuration of the 4E163A# 07s conforms to MEF 9, 'ection =.H.9. Tester offers 'er&ice Frames into the E64s configured at the ingress 5#0s and &erifies that they are successfully deli&ered %y the ME# on the proper E64 at the egress 5#0. 'ince E64s are %i1 directional 'er&ice Frames should %e offered at all 5#0s in the E64. #um%er of &alid frames. #um%er of 2oint1to12oint and Multipoint1to1Multipoint E64s. #um%er of 5#0s. #um%er and &alues of 4E163A# 07s. 2ass or fail
(,"N/I)-E($ Map
Test !ase "91 !E4/(AN ID for Unta$$e* an* 6riorit% Ta$$e* Service Fra es
Test Name Test )efinition I) #eference )ocument !ource Test Type Test !tatus #e*uirement )escription Test &b+ect Test ed $onfiguration " !T#"$T TE!T $"!E! %&# ET'E#NET !E#(I$E! "T T'E UNI 4E163A# 07 for 5ntagged and 2riority Tagged 'er&ice Frames M.=.H.919 MEF 9 Ethernet 'er&ices Model, 2hase 9 4onformance Mandatory Ahen the 4E163A# 07 2reser&ation 'er&ice Attri%ute is not in force for an E64, egress 'er&ice Frames with the 4E163A# 07 &alue for untagged and priority tagged 'er&ice Frames MUST %e untagged. 6erify that when the 4E163A# 07 2reser&ation 'er&ice Attri%ute is not in force for an E64, egress 'er&ice Frames with the 4E163A# 07 &alue for untagged and priority tagged 'er&ice Frames are untagged at the egress 5#0. At least one E64 associating at least two 5#0s is configured for which the 4E163A# 07 2reser&ation 'er&ice Attri%ute is not in force and two 4E163A# 07s are mapped to the E64, one for untagged and priority tagged frames. Testers are attached to all 5#0s in the configured E64s. IN30ESS UNI <A= E30ESS UNI <,= !E4/(AN ID E/! !E4/(AN ID E/! H0 E649 90K E649 5se of other 4E163A# 07s is permitted pro&ided that 9. 4onfiguration of the 4E163A# 07s conforms to MEF 9, 'ection =.H.9. 2. The 4E163A# 07 at the ingress and egress 5#0s is the 4E163A# 07 for untagged and priority tagged 'er&ice Frames at those 5#0s. K The 4E163A# 07 for untagged and priority tagged 'er&ice Frames is configured to 90 at %oth ingress and egress 5#0s. Tester offers tagged, untagged and priority tagged 'er&ice Frames to the ingress 5#0 and &erifies that egress 'er&ice Frames with the 4E163A# 07 &alue for untagged and priority tagged 'er&ice Frames are untagged at the egress 5#0. #um%er of &alid frames 5ntagged and priority tagged 'er&ice Frames. #um%er of E64s per 5#0. Type of E64 )2oint1 to12oint and Multipoint1to1Multipoint*. #um%er of 5#0s. #um%er and &alues of 4E163A# 07s. 2ass or fail
(,"N/I)-E($ Map
(,"N/I)-E($ Map
(,"N/I)-E($ Map
Nu ber of E/!s
" !T#"$T TE!T $"!E! %&# ET'E#NET !E#(I$E! "T T'E UNI Ma+imum #um%er of E64s M.=.= MEF 9 Ethernet 'er&ices Model, 2hase 9 4onformance Jptional A 5#0 supports a ma+imum num%er of E64s greater than one. 7etermine the ma+imum num%er of E64s that are supported at the 5#0. Multiple E64s associating at least two 5#0s are configured and at least one 4E163A# 07 is mapped to the E64s. Testers are attached to all 5#0s in the configured E64s. UNI <A= !E4/(AN ID E/! 2 to 40EH E64s2140EH UNI <,= !E4/(AN ID E/! 2 to 40EH E64s2140EH
(,"N/I)-E($ Map
An iterati&e process may %e used to determine the ma+imum num%er of E64s supported at the 5#0. Testers offer 'er&ice Frames %idirectionally on the configured E64s at each 5#0 and &erify that the ME# deli&ers the corresponding 'er&ice Frames at the egress 5#0 on the same E64s. The ma+imum num%er of E64s supported at the 5#0 is gi&en %y the largest num%er of E64s o&er which 'er&ice Frames are successfully deli&ered to the egress 5#0)s* %y the ME#. #um%er of &alid frames. #um%er of 5#0s. #um%er of E64s per 5#0. Type of E64 )2oint1to12oint and Multipoint1to1 Multipoint*. #um%er and &alues of 4E163A# 07s. Ma+imum num%er of E64s
(,"N/I)-E($ Map
Test !ase 241 UNI All to One ,un*lin$ an* !E4/(AN ID 6reservation
Test Name Test )efinition I) #eference )ocument !ource Test Type Test !tatus #e*uirement )escription Test &b+ect Test ed $onfiguration " !T#"$T TE!T $"!E! %&# ET'E#NET !E#(I$E! "T T'E UNI 5#0 All to Jne @undling and 4E163A# 07 2reser&ation M.=.E19 MEF 9 Ethernet 'er&ices Model, 2hase 9 4onformance Mandatory Ahen a 5#0 has the All to Jne @undling attri%ute, all 4E163A# 07s MUST map to a single E64 at the 5#0 and the list of 4E163A# 07s mapped to the E64 MUST %e the same at each 5#0 in the E64. 6erify that when a 5#0 has the All to Jne @undling attri%ute, all 4E163A# 07s are mapped to a single E64 at the 5#0 and the list of 4E163A# 07s mapped to the E64 are the same at each 5#0 in the E64. An E64 associating at least two 5#0s is configured and two or more 4E163A# 07s are mapped to the E64. All 4E163A# 07s MUST %e mapped to the same E64. Testers are attached to all 5#0s in the configured E64s. UNI <A= UNI <,= !E4/(AN ID E/! !E4/(AN ID E/! <00 E649 <00 E649 <90 E649 <90 E649 5se of other 4E163A# 07s is permitted pro&ided that configuration of the 4E163A# 07s conforms to MEF 9, 'ection =.H.9. Testers offer 'er&ice Frames with all possi%le 4E163A# 07 &alues into the E64 at each 5#0 and &erify that the corresponding 'er&ice Frames are deli&ered %y the ME# at the other 5#0)s* on the same E64 with 4E163A# 07s preser&ed. #um%er of &alid frames #um%er of 5#0s. #um%er of E64s per 5#0. Type of E64 )2oint1to12oint and Multipoint1to1 Multipoint*. #um%er. 2ass or fail
(,"N/I)-E($ Map
(,"N/I)-E($ Map
(ariables
#esults #emarks
@ridge @loc, of protocols, BA"2 @loc, of protocols, All @ridges 2rotocol are mandatory. 2ass or fail
(,"N/I)-E($ Map
(ariables
#esults #emarks
"0# Securit%
'ecurity issues are not addressed in this document.
""# 0eferences
#eference #eference )etails
>9? Ethernet 'er&ices Model >2? Ethernet Traffic Management >G? 'er&ices 7efinitions >4? Metro Ethernet 'er&ices
MEF 9 CEthernet 'er&ices Model, 2hase 9D MEF H CTraffic Management 'pecification 2hase 9D MEF < CEthernet 'er&ices 7efinitionsD MEF CMetro Ethernet 'er&ices L A Technical J&er&iewD white paper, ". 'antitoro )0nformati&e* 0nformation technology L Telecommunications and information e+change %etween systems L 3ocal and metropolitan area networ,s L 'pecific re-uirements L 2art G 4arrier sense multiple access with collision detection )4'MA/47* access method and physical layer specifications, 8 March 2002. )#ormati&e* "F4 299E, CMey words for use in "F4s to 0ndicate "e-uirement 3e&elsD, '. @radner, http //www.ietf.org/rfc/rfc299E.t+t )#ormati&e* "F4 228H, C@enchmar,ing Terminology for 3A# 'witching 7e&icesD, ". Mande&ille, http //www.ietf.org/rfc/rfc228H.t+t "F4 2H44, C@enchmar,ing Methodology for #etwor, 0nterconnect 7e&icesD, '. @radner, N. Mc:uaid, http //www.ietf.org/rfc/rfc2H44.t+t "F4 288E, C@enchmar,ing Methodology for 3A# 'witching 7e&icesD, ". Mande&ille, N. 2erser, http //www.ietf.org/rfc/rfc288E.t+t
><? "F4 299E >=? "F4 228H >8? "F4 2H44 >E? "F4 288E