Unified Communications Test Plan

blackstartΔίκτυα και Επικοινωνίες

26 Οκτ 2013 (πριν από 3 χρόνια και 7 μήνες)

473 εμφανίσεις

























Unified Communications Test Plan


Appendix E
-
4


Customer Edge Router (CER)


Detailed Test P
rocedures































(This page left intentionally blank.)


E
-
4

P


E
-
4
.1

INTRODUCTION


This section of the test plan addresses those

procedures necessary to test Customer Edge Routers
(CERs).
The CER performs Traffic Conditioning Services, Bandwidth Management Services, and Per
Hop Behavior (PHB) Management Services.
Figure E
-
4
-
1 depicts the deployed architecture for a
CER, and Figur
e E
-
4
-
2 through E
-
4
-
7 depict the CER test networks. In addition to testing,
demonstration or inspection of the system to verify requirements shall be carried

out. An analysis of
the vendor’s LoC shall be conducted to verify that those “L” requirements ha
ve been met.





LEGEND:

CER

-

Customer Edge Router

EBC

-

Edge Boundary Controller

EO


-

End Office

LSC

-

Local Session Controller




MFS

-

Multi
-
Function Switch

MFSS

-

Multi
-
Function Soft Switch

PBX

-

Private Branch Exchange

SMEO

-

Small End Office

WA
N

-

Wide Area Network


Figure E
-
4
-
1. Deployed Architecture



CER


MFS

SMEO

MFSS



MFS

MFSS

PBX

EO

MFS

EO

PBX

PBX

TACTICAL

WAN

EBC

EBC


CER

EBC

CE
R

EBC


CER

EBC

EBC


LSC

LSC

LSC

LSC

LSC

LSC



E
-
4

Q

E
-
X.
4
.2 ACRONYMS



802.3ab

IEEE Standard for Gigabit Ethernet over Copper

802.3ae

IEEE Standard for 10G Ethernet

802.3i

IEEE Standard for 10 Mbps Ethernet (10BaseT)

802.3u

IEEE Standard for 100
Mbps Ethernet (Fast Ethernet)

802.3z

IEEE Standard for Gigabit Ethernet

AES

Advanced Encryption Standard

AF

Assured Forwarding

AR

Aggregation Router

BGP

Border Gateway Protocol

BGP
-
4

Border Gateway Protocol 4

C

Conditional

CDR

Call Detail Record

CER

Custo
mer Edge Router

CM

Configuration Management

CR

Capability Requirement

DAD

Duplicate Address Detection

DCF

Data Collection Form

DD

Default Data

DHCP

Dynamic Host Configuration Protocol

DHCPv6

Dynamic Host Configuration Protocol for IPv6

DoS

Denial of Servic
e

DS3

Digital Signal Level 3

DSCP

Differentiated Services Code Point

E2E

End
-
to
-
End

EAP

Extensible Authentication Protocol

EBC

Edge Boundary Controller

ECN

Explicit Congestion Notification

EF

Expedited Forwarding

EI

End Instrument

EMS

Element Management Sy
stem

EO

End Office

ESP

Encapsulating Security Payload

F

FLASH

FCAPS

Fault, Configuration, Accounting, Performance, and

Security

FO

FLASH OVERRIDE

FR

Functional Requirement

GEI

Generic End Instrument

GRE

Generic Routing Encapsulation

H.323

ITU
-
T Standard P
rotocol Suite for Video Conferencing

HA

High Availability

HMAC

Hashed Message Authentication Code

HTD

High Throughput Data

I

IMMEDIATE

IA

Information Assurance

IATP

Information Assurance Test Plan

ICMP

Internet Control Message Protocol

IKE

Internet Key Exc
hange

IKEv1

Internet Key Exchange Version 1

IKEv2

Internet Key Exchange Version 2

IO

Interoperability

IP

Internet Protocol

IPSec

Internet Protocol Security

IPv4

Internet Protocol Version 4

IPv6

Internet Protocol Version 6

ISAKMP

Internet Security Associa
tion and Key Management

Protocol

IS
-
IS

Intermediate System to Intermediate System

IUT

Interface Under Test

kbps

Kilobits per Second

LA

Low Availability

LAN

Local Area Network

LLD

Low Latency Data

LOC

Letter of Compliance

LSC

Local Session Controller

MA

Me
dium Availability

Mbps

Megabits per Second

MFS

Multifunction Switch

MFSS

Multifunction Softswitch


MIB

Management Information Base

MIPv6

Mobile IP Version 6

MLD

Multicast Listener Discovery

MM

Multimedia

MOS

Mean Opinion Score

ms

Mi
lli
second

MTU

Maximum Tr
ansmission Unit

NEMO

Network Mobility

NLB

No Load Baseline

NM

Network Management

OA&M

Operations, Administration, and Maintenance

OSPF

Open Shortest Path First

OSPFv3

Open Shortest Path First Version 3

P

PRIORITY

PBX

Private Branch Exchange

PD

Preferred Da
ta

PHB

Per Hop Behavior

PM

Performance Management

PPP

Point
-
to
-
Point Protocol

QoS

Quality of Service

R

Required

R

Router

R

ROUTINE

RFC

Request For Comment

RTS

Real Time Services

SHA

Secure Hash Algorithm

SLAAC

Stateless Address Auto
-
Configuration

SMEO

Smal
l End Office

SNMP

Simple Network Management Protocol

SNMPv3

Simple Network Management Protocol Version 3

SPD

Security Policy Database

SPI

Security Parameter Index

SQF

System Quality Factors

SRTP

Secure Real
-
Time Transport Protocol

SSH

Secure Shell

SSHv2

Se
cure Shell Version 2

SUT

System Under Test

T1

T
-
Carrier 1

T3

T
-
Carrier 3

TCP

Transmission Control Protocol

TDM

Time Division Multiplexing

TMDE

Test, Measurement, and Diagnostic Equipment

UCR

Unified Capabilities Requirements

UDP

User Datagram Protocol

UPS

Uninterruptible Power Supply

URI

Uniform Resource Identifier

VLAN

Virtual Local Area Network

VTC

Video Teleconferencing

VVoIP

Voice and Video over Internet Protocol

WAN

Wide Area Network



E
-
4

R

E
-
4.
3

TEST METHODOLOGY


Testing of the CER will be conducted in
tw
o primary

configurations
, a standalone configuration and
an end
-
to
-
end configuration
.
Both configurations can vary depending upon the type of Interface
Under Test (IUT) and the method used by SUT for reliability.


Standalone testing will verify 4 and 8
queue models for
PHB

and basic functionality of CER
. F
igure
E
-
4
-
2 depicts the test network for standalone Ethernet
interface
testing.
F
igure E
-
4
-
3

depicts the test
network for standalone
TDM and serial

interface
testing
.



End
-
to
-
end testing will veri
fy the failover capabilities of the CER within Voice and Video over IP
network (VVoIP).


F
igure E
-
4
-
4 depicts the end
-
to
-
end test network using Ethernet

interfaces and a
single chassis to meet reliability requirements
.
F
igure E
-
4
-
5 depicts the end
-
to
-
end
test network
using TDM and serial interfaces

and a single chassis to meet reliability requirements
.
F
igure E
-
4
-
6

depicts the end
-
to
-
end test network using Ethernet

interfaces and a dual chassis to meet reliability
requirements
.
F
igure E
-
4
-
7

depicts the e
nd
-
to
-
end test network using TDM and serial interfaces

and
a dual chassis to meet reliability requirements
.


Table E
-
4
-
1 outlines the basic requirements and test methodology that will be use to verify the
requirement. Table E
-
4
-
2 outlines the capability

requirements (CRs) and functional requirements
(FRs) applicable to the
devices under test. Table E
-
4
-
3 details the required configuration for the 4
-
queue Per Hop Behavior approach. Table E
-
4
-
4 details the required configuration for the 8
-
queue
PHB appro
ach. Table E
-
4
-
5

contains the CER interoperability test procedures
.


For UCR Information Assurance (IA) requirements (section 5.4) that are applicable to the CER, Table
E
-
x
-
2 also reflects the applicable

test procedure.

For IA test procedures contained w
ithin the IA Test
plan (IATP)
-

RTS_IA_Test_Plan_February_09_Master.pdf
, the IATP test case is referenced. For
interoperability

test procedure references, this annex uses the nomenclature IO
-
#.





E
-
4

S
















LEGEND:

CER

-

Customer Edge Router

IUT

-

Interface Under Test

SUT

-

System Under Test

TMDE

-

Test, Measurement, and Diagnostic Equipment






Figure E
-
4
-
2. Standalone Configuration with Ethernet IUT








LEGEND:

AR

-

Aggregation Router

CER

Customer Edge Router


DS3

-

Digital Signal Level 3

IUT

-

Interface Under Test




SUT

-

System Under Test

T1

-

T
-
Carrier 1

T3

-

T
-
Carrier 3

TMDE

-

Test, Measurement, and Diagnostic Equipment



Figure E
-
4
-
3. Standalone Configuration with TDM/Serial IUT




CER

(SUT)

AR

TMDE

Loading

Interface(s)


IUT


T1

T3

DS
3

SERIAL


TMDE

CER

(SUT)

TMDE

IUT

Loading

Interface(s)

TMDE



E
-
4

T





LEGEND:

AR

-

Aggregation Router

BGP

-

Border Gateway Protocol

CER

-

Customer Edge Router

DS3

-

Digital Signal Level 3

eBGP
-

External Border Gateway Protocol

ISIS
-

Intermediate System to Intermediate System Protocol




OSPF

-

Open Shortest Path First


R

-

Router

SUT

-

System Under Test

T1

-

T
-
Carrier 1

T3

-

T
-
Carrier 3

TMDE

-

Test, Measurement, and Diagnostic Equipment



Figure E
-
4
-
4. E2E Configuration with Ethernet Interfaces and Single Chassis Reliability








LEGEND:

AR

-

Aggregation Router

BGP

-

Border Gateway Protocol

CER

-

Customer Edge Router

DS3

-

Digital Signal Level 3

eBGP
-

External Border Gateway Protocol

ISIS
-

Intermediate System to Intermediate System Protocol




OSPF

-

Open Shortest Path Firs
t


R

-

Router

SUT

-

System Under Test

T1

-

T
-
Carrier 1

T3

-

T
-
Carrier 3

TMDE

-

Test, Measurement, and Diagnostic Equipment



R1

R2

TMDE

TMDE

OSPF

WAN e
BGP
, IGP=ISIS


T1

T3

DS
3

SERIAL


T1

T3

DS
3

SERIAL


CER

(SUT)


AR1

AR2

CER

(SUT)

AR1

AR2

R1

R2

TMDE

OSPF

WAN e
BGP
, IGP=ISIS

TMDE



E
-
4

U

Figure E
-
4
-
5. E2E Configuration with TDM/Serial Interfaces and Single Chassis Reliability



E
-
4

V





LEGEND:

AR

-

Aggregation Router

BGP

-

Border Gateway Protocol

CER

-

Customer Edge Router

DS3

-

Digital Signal Level 3

eBGP
-

External Border Gateway Protocol

ISIS
-

Intermediate System to Intermediate System Protocol




OSPF

-

Open Shortest Path First


R

-

Router

SUT

-

System Under
Test

T1

-

T
-
Carrier 1

T3

-

T
-
Carrier 3

TMDE

-

Test, Measurement, and Diagnostic Equipment



Figure E
-
4
-
6. E2E Configuration with Ethernet Interfaces and Dual Chassis Reliability








LEGEND:

AR

-

Aggregation Router

BGP

-

Border Gateway Protocol

CER

-

Customer Edge Router

DS3

-

Digital Signal Level 3

eBGP
-

External Border Gateway Protocol

ISIS
-

Intermediate System to Intermediate System Protocol




OSPF

-

Open Shortest Path First


R

-

Router

SUT

-

System Under Test

T1

-

T
-
Carrier 1

T3

-

T
-
Carrie
r 3

TMDE

-

Test, Measurement, and Diagnostic Equipment



AR1

AR2

R1

R2

TMDE

OSPF

WAN e
BGP
, IGP=ISIS


TMDE

CER

(SUT)

CER

Active

Standby

R1

TMDE

T1

T3

DS
3

SERIAL


T1

T3

DS
3

SERIAL


AR1

AR2

CER

(SUT)

CER

Active


Standby


R2

TMDE

OSPF

WAN e
BGP
, IGP=ISIS




E
-
4



Figure E
-
4
-
7. E2E Configuration with TDM/Serial Interfaces and Dual Chassis Reliability



Table E
-
4
-
1. CER Test Requirements/Methodology


ID

Interface

Critical

(See
note 1)

UCR Ref

Threshold CR/FR

Requirements

(See note 2)

Remarks

CER

802.3i

Y

5.3.2.4.2,

5.3.2.14.9

1
-
5, 23
-
24, 29, 30, 34, 35
-
139


CER

802.3u

Y

5.3.2.4.2,

5.3.2.14.9

1
-
5, 23
-
24, 29, 30, 34, 35
-
139


CER

802.3z

Y

5.3.2.4.2,

5.3.2.14.9

1
-
5, 23
-
24, 29, 30, 34, 35
-
139


CER

802.3ab

N

5.3.2.14.9

1
-
5, 23
-
24, 29, 30, 34, 35
-
139


CER

802.3ae

N

5.3.2.14.9

1
-
5, 23
-
24, 29, 30, 34, 35
-
139


CER

Serial

N

5.3.2.14.9

1
-
5, 23
-
24, 29, 30, 34, 35
-
139


CER

T1

Y

5.3.2.14.9

1
-
5, 23
-
24, 29, 30, 34, 35
-
139


CER

E1

N

5.3.2.14.9

1
-
5, 23
-
24, 29, 30
, 34,

35
-
139


CER

DS
-
3

Y

5.3.2.14.9

1
-
5, 23
-
24, 29, 30, 34, 35
-
139


FRs/CRs

NA

Y

See Table E
-
4
-
2

6
-
22, 25
-
28, 31
-
33



NOTES:


1. Device under test need not provide non
-
critical (conditional) requirements; however, if provided all threshold ‘CR/FR’ require
ments
must be met.

2. CR/FR requirements are listed in Table E
-
4
-
2.


LEGEND:

CER

-

Customer Edge Router

CR

Capability Requirement

FR

Functional Requirement

ID

Identification

N

No


N

No

NA

Not Applicable

UCR

Unified capabilities Requirements

Y

Yes




E
-
4




T
able E
-
4
-
2. CER Capability/Functional Requirements


ID

Requirement

Ref

IO

IA

Remarks

CER Requirements

1


Traffic Conditioning based on DSCP queuing (R)

UCR 2008 5.3.2.14.1,

UCR 2008 5.3.3.3.4

X


IO
-
2 & 3

2


DSCP Services (R)

UCR 2008 5.3.2.14.1

UCR 2008
5.3.2.14.2

RFC 2475

RFC 2474

UCR 2008 5.3.3.3.2

UCR 2008 Table 5.3.3
-
1

X


IO
-
2 & 3

LOC

3


PHB (EF and AF) over 4 queues (R)

UCR 2008 5.3.2.14.3

RFC 3246

RFC 2597

UCR 2008 5.3.3.3.3

UCR 2008 Table 5.3.3
-
2

X


IO
-
2

LOC

4


PHB (EF and AF) over 8 queues (C)

UCR 2
008 5.3.2.14.3

RFC 3246

RFC 2597

UCR 2008 5.3.3.3.3

UCR 2008 Table 5.3.3
-
3

X


IO
-
3

LOC

5


Traffic Conditioning based on IP addresses, VLAN tags,
protocol port numbers (R)

UCR 2008 5.3.3.3.4

RFC 3246

X


LOC

LOC

6


LSC/MFSS Interface: Provide interface to MFSS
/LSC for
traffic conditioning and bandwidth allocation (C)

UCR 2008 5.3.2.14.4

UCR 2008 5.3.2.14.5

X


LOC

7


Network Management (NM): Support FCAPS (R)

UCR 2008 5.3.2.14.6

UCR 2008 5.3.2.17.3

UCR 2008 5.3.2.18.1

RFC 1215

RFC 1213

RFC 3418

X


IO
-
4

LOC

8


NM:
Alarm Messages (R)

UCR 2008 5.3.2.17.3.1.1

X


IO
-
4

9


NM: Self
-
Detection of Fault Conditions (R)

UCR 2008 5.3.2.17.3.1.2

X


IO
-
4

10


NM: Alarm Notifications (R)

UCR 2008 5.3.2.17.3.1.3

X


IO
-
4

11


NM: Near
-
Real
-
Time Alarm Messages (R)

UCR 2008 5.3.2.17.3.1.4

X


IO
-
4

12


NM: SNMP Version 2 and Version 3 Format Alarm
Messages (R)

UCR 2008 5.3.2.17.3.1.5

X


IO
-
4

13


NM: IP Queue Control Capabilities (R)

UCR 2008 5.3.2.17.3.4.2.12

X


IO
-
2 & 3

14


NM Requirements (faults, CM, PM information) (R)

UCR 2008 5.3.2.18.1

RFC 121
5

RFC 1213

RFC 3418

X


IO
-
4

LOC

15


QOS queues must be readable and settable by the RTS
EMS

UCR 2008 5.3.2.18.1.1

X


IO
-
4

16


Standard CM MIB variables (R)

UCR 2008 5.3.2.18.1.2

UCR 2008 Table 5.3.2.18
-
1

X


IO
-
4

17


Standard PM MIB variables (R)

UCR 2008 5.3.2.1
8.1.3

UCR 2008 Table 5.3.2.18
-
2

X


IO
-
4

18


Standard TRAP’s (R)

UCR 2008 5.3.2.18.1.4

UCR 2008 Table 5.3.2.18
-
3

X


IO
-
4

19


High Availability 99.999% (R)

UCR 2008 5.3.2.14.7

UCR 2008 5.3.2.5.2

X


IO
-
1

Reliability Computation LOC

20


Medium Availability 99.99% w/
o SQF (R)

UCR 2008 5.3.2.14.7

UCR 2008 5.3.2.5.2

X


IO
-
1

Reliability Computation LOC

21


Medium Availability 99.99% w/SQF (C)

UCR 2008 5.3.2.14.7

UCR 2008 5.3.2.5.2

X


IO
-
1

Reliability Computation LOC

22


Low Availability 99.9% w/SQF (C)

UCR 2008 5.3.2.14.7

UC
R 2008 5.3.2.5.2

X


IO
-
1

Reliability Computation LOC

23


Performance Characteristics: Packet Transit Time: No more
than 2 msec transit time. (R)

UCR 2008 5.3.2.14.8

X


IO
-
2 & 3



E
-
4



T
able E
-
4
-
2. CER Capability/Functional Requirements


ID

Requirement

Ref

IO

IA

Remarks

24


Performance Characteristics: Full Duplex Line Rate
Throughput (R)

5.3.2.14.9

X


LOC

25


System Quality Factors (SQF) (R)

UCR 2008 5.3.2.14.7

UCR 2008 5.3.2.5.2

Telcordia GR
-
512
-
CORE

X


IO
-
1, 5 & 6

LOC

26


SQF: System Availability


Dual Power Supplies (R)

UCR 2008 5.3.2.14.7

UCR 2008 5.3.2.5.2.1 (1)

X


IO
-
1 & 5

27


SQF: System Availabil
ity
-

Dual Processors/Swappable
Sparing (Control Supervisors) (R)

UCR 2008 5.3.2.14.7

UCR 2008 5.3.2.5.2.1 (2)

X


IO
-
1 & 5

28


SQF: System Availability
-

Termination Sparing (R)

UCR 2008 5.3.2.14.7

UCR 2008 5.3.2.5.2.1 (3)

X


IO
-
1

29


SQF: System Availability
-

Redundancy Protocol Dynamic
Rerouting (R)

UCR 2008 5.3.2.14.7

UCR 2008 5.3.2.5.2.1 (4)

X


IO
-
1 & 5

30


SQF: System Availability
-

No Single Failure Point of more
than 96 users (R)

UCR 2008 5.3.2.14.7

UCR 2008 5.3.2.5.2.1 (5)

X


IO
-
1

31


SQF: System Availabil
ity
-

Switch Fabric or Backplane
Redundancy for Active Backplanes (R)

UCR 2008 5.3.2.14.7

UCR 2008 5.3.2.5.2.1 (6)

X


IO
-
1

32


SQF: System Availability
-

Software Upgrades and Patches
(R)

UCR 2008 5.3.2.14.7

UCR 2008 5.3.2.5.2.1 (7)

X


IO
-
6

33


SQF: System Ava
ilability
-

Backup Power Uninterruptible
Power Supply (UPS) Requirements (R)

UCR 2008 5.3.2.14.7

UCR 2008 5.3.2.5.2.1 (8)

X


LOC

34


SQF: System Availability
-

No Loss of Active Sessions and 5
Second Failover (R)

UCR 2008 5.3.2.14.7

UCR 2008 5.3.2.5.2.1 (9)

X


IO
-
5

IPv6 Requirements (Applicable to Routers)

35


IPv6 and IPv4 Dual Stack (R)

UCR 2008 5.3.5.4 (1)

RFC 4213

X

X

IATP Table E
-
15 Test Case 1,2

IO
-
2, 3, 5, 6

LOC

36


IPv6 Format (R)

UCR 2008 5.3.5.4 (2)

RFC 2460

RFC 5095

X

X

IATP Table E
-
15 Test Case 3

LOC

37


IPv6 Packet Transmission Frame Format (R)

UCR 2008 5.3.5.4 (3)

RFC 2464

X

X

IATP Table E
-
15 Test Case 4

LOC

38


IPv6 Path MTU Discovery (R)

UCR 2008 5.3.5.4.1 (4)

RFC 1981


X

LOC

IATP Table E
-
15 Test Case 5

39


IPv6 minimum MTU of 1280 bytes (R)

UCR 2
008 5.3.5.4.1 (5)

RFC 2460

RFC 5095


X

IATP Table E
-
15 Test Case 6

LOC

40


IPv6 Handling Path MTU Discovery “Packet Too Big”
Messages (C)

UCR 2008 5.3.5.4.1 (6)


X

IATP Table E
-
15 Test Case 7

41


IPv6 Address (R)

UCR 2008 5.3.5.4.3 (8)

RFC 4291

X

X

IATP Tab
le E
-
15 Test Case 12

LOC

42


IPv6 Scoped Address Architecture (RFC 4007)

UCR 2008 5.3.5.4.3 (9)

RFC 4007

X

X

IATP Table E
-
15 Test Case 13

LOC

43


IPv6 Scoped Address Architecture Scope Index Value (C)

UCR 2008 5.3.5.4.3 (9.1)

RFC 4007

X

X

IATP Table E
-
15 Tes
t Case 14

LOC

44


IPv6 DHCP (C)

UCR 2008 5.3.5.4.4 (10)

RFC 3315


X

IATP Table E
-
15 Test Case 15

LOC

45


IPv6 DHCPv6 Authentication Interaction (C)

UCR 2008 5.3.5.4.4 (10.3)

RFC 3118

RFC 3315


X

IATP Table E
-
15 Test Case 23

LOC

46


IPv6 Neighbor Discovery (R)

UCR 2008 5.3.5.4.5 (11)

RFC 2461

RFC 4861

X

X

IATP Table E
-
15 Test Case 24

LOC

47


IPv6 Neighbor Advertisement Override Flag Bit (R)

UCR 2008 5.3.5.4.5 (11.1)


X

IATP Table E
-
15 Test Case 25

48


IPv6 Neighbor Advertisement Entry Missing (R)

UCR 2008 5.3.5.4.
5 (11.3)


X

IATP Table E
-
15 Test Case 26

49


IPv6 Neighbor Advertisement Entry Incomplete (R)

UCR 2008 5.3.5.4.5 (11.4)


X

IATP Table E
-
15 Test Case 27

50


IPv6 Address Resolution Failure (R)

UCR 2008 5.3.5.4.5 (11.5)


X

IATP Table E
-
15 Test Case 28

51


IPv6 Red
irect Message Acceptance (C)

UCR 2008 5.3.5.4.5.1 (11.7)


X

IATP Table E
-
15 Test Case 30

52


IPv6 Redirect Message Update Destination Cache (C)

UCR 2008 5.3.5.4.5.1 (11.7.1)


X

IATP Table E
-
15 Test Case 31



E
-
4



T
able E
-
4
-
2. CER Capability/Functional Requirements


ID

Requirement

Ref

IO

IA

Remarks

53


IPv6 Redirect Message Create Cache Entry (C)

UCR 2
008 5.3.5.4.5.1 (11.7.2)


X

IATP Table E
-
15 Test Case 32

54


IPv6 Router Advertisement Verification and Log (R)

UCR 2008 5.3.5.4.5.2 (11.8)


X

IATP Table E
-
15 Test Case 33

55


IPv6 Router Advertisement MTU Value (R)

UCR 2008 5.3.5.4.5.2 (11.9)

RFC 2461

RFC 486
1


X

IATP Table E
-
15 Test Case 35

LOC

56


IPv6 Stateless Address Autoconfiguration (SLAAC) (C)

UCR 2008 5.3.5.4.6 (12)

RFC 2462

RFC 4862


X

IATP Table E
-
15 Test Case 36

LOC

57


IPv6 SLAAC Configuration Flag (C)

UCR 2008 5.3.5.4.6 (12.1.1)


X

IATP Table E
-
15
Test Case 38

58


IPv6 SLAAC Duplicate Address Detection (DAD) (C)

UCR 2008 5.3.5.4.6 (12.2)

RFC 2462

RFC 4862


X

IATP Table E
-
15 Test Case 39

LOC

59


IPv6 Manual Address Configuration (R)

UCR 2008 5.3.5.4.6 (12.3)


X

IATP Table E
-
15 Test Case 40

60


IPv6 Manage
d Address Configuration Flag (R)

UCR 2008 5.3.5.4.6 (12.4.1)



IATP Table E
-
15 Test Case 42

61


IPv6 Internet Control Message Protocol (ICMP) (R)

UCR 2008 5.3.5.4.7 (14)

RFC 4443

X

X

IATP Table E
-
15 Test Case 45

LOC

62


IPv6 ICMP Rate Limiting (R)

UCR 2008
5.3.5.4.7 (14.1)

X

X

IATP Table E
-
15 Test Case 46

63


IPv6 ICMP Destination Unreachable (R)

UCR 2008 5.3.5.4.7 (14.2)

X

X

IATP Table E
-
15 Test Case 47

64


IPv6 ICMP Echo Reply (R)

UCR 2008 5.3.5.4.7 (14.3)


X

IATP Table E
-
15 Test Case 48

65


IPv6 ICMP Validation

(R)

UCR 2008 5.3.5.4.7 (14.4)


X

IATP Table E
-
15 Test Case 49

66


IPv6 OSPF (R)

UCR 2008 5.3.5.4.8 (15)

RFC 2740

X

X

IATP Table E
-
15 Test Case 50

IO
-
5, 6

LOC

67


IPv6 OSPF IPSec (R)

UCR 2008 5.3.5.4.8 (15.1)


X

IATP Table E
-
15 Test Case 51

68


IPv6 OSPF IP Aut
hentication Header (R)

UCR 2008 5.3.5.4.8 (15.2)

RFC 2404


X

IATP Table E
-
15 Test Case 52

LOC

69


IPv6 OSPFv3 Interior Routing Functions (R)

UCR 2008 5.3.5.4.8 (15.3)

RFC 4552


X

IATP Table E
-
15 Test Case 53

LOC

70


IPv6 IS
-
IS (R)

UCR 2008 5.3.5.4.8 (15a)

RF
C 5308

X

X

IATP Table E
-
15 Test Case 54

LOC

71


IPv6 IS
-
IS RFC Support (R)

UCR 2008 5.3.5.4.8 (15a.1)

RFC 5304

RFC 5310


X

IATP Table E
-
15 Test Case 55

LOC

72


IPv6 Border Gateway Protocol (BGP) (C)

UCR 2008 5.3.5.4.8 (16)

RFC 1772

RFC 4271

X

X

IATP Table E
-
15 Test Case 56

IO
-
5, 6

LOC

73


IPv6 BGP
-
4 Multiprotocol Extensions for Inter
-
Domain
Routing (C)

UCR 2008 5.3.5.4.8 (16.1)

RFC 2545

X

X

IATP Table E
-
15 Test Case 57

LOC

74


IPv6 BGP
-
4 Multiprotocol Extensions (C)

UCR 2008 5.3.5.4.8 (17)

RFC 2858

RFC 4760

X

X

IATP Table E
-
15 Test Case 58

LOC

75


IPv6 Generic Routing Encapsulation (GRE) (C)

UCR 2008 5.3.5.4.8 (18)

RFC 2784

X

X

IATP Table E
-
15 Test Case 59

LOC

76


IPv6 Generic Packet Tunneling (C)

UCR 2008 5.3.5.4.8 (19)

RFC 2473

X

X

IATP Table E
-
15 Test Case 60

LOC

77


IPv6 Multicast Listener Discovery (MLD) (R)

UCR 2008 5.3.5.4.8 (20)

RFC 2710

RFC 3810


X

IATP Table E
-
15 Test Case 61

LOC

78


IPv6 Multicast Listener Discovery (MLD) (R)

UCR 2008 5.3.5.4.8 (20.1)

RFC 2711


X

IATP Table E
-
15 Test Case 62

LOC

79


IPv6 ML
D (R)

UCR 2008 5.3.5.4.8 (21)

RFC 2710


X

IATP Table E
-
15 Test Case 63

LOC

80


IPv6 IP Sec Security Architecture (R)

UCR 2008 5.3.5.4.9 (22)

RFC 2401

RFC 4301


X

IATP Table E
-
15 Test Case 64

LOC

81


IPv6 IP Sec Security Association Binding (R)

UCR 2008 5.3.5.
4.9 (22.1)


X

IATP Table E
-
15 Test Case 65

82


IPv6 IP Sec Processing Bypass (R)

UCR 2008 5.3.5.4.9 (22.2)


X

IATP Table E
-
15 Test Case 66

83


IPv6 IP Sec IPv4 Security Association Mixing (R)

UCR 2008 5.3.5.4.9 (22.3)


X

IATP Table E
-
15 Test Case 67



E
-
4



T
able E
-
4
-
2. CER Capability/Functional Requirements


ID

Requirement

Ref

IO

IA

Remarks

84


IPv6 IP
Sec Security Association Database (R)

UCR 2008 5.3.5.4.9 (22.4)


X

IATP Table E
-
15 Test Case 68

85


IPv6 IP Sec DSCP Security Assocation (R)

UCR 2008 5.3.5.4.9 (22.5)


X

IATP Table E
-
15 Test Case 69

86


IPv6 IP Sec Integrity and Confidentiality (R)

UCR 2008 5.
3.5.4.9 (22.6)


X

IATP Table E
-
15 Test Case 70

87


IPv6 IP Sec ICMP Notification (R)

UCR 2008 5.3.5.4.9 (22.7)


X

IATP Table E
-
15 Test Case 71

88


IPv6 IP Sec ICMP Response Rate Limitation (R)

UCR 2008 5.3.5.4.9 (22.7.1)


X

IATP Table E
-
15 Test Case 72

89


IPv6

IP Sec Explicit Congestion Notification (ECN) (R)

UCR 2008 5.3.5.4.9 (22.8)


X

IATP Table E
-
15 Test Case 73

90


IPv6 IP Sec Security Policy Database (SPD) (R)

UCR 2008 5.3.5.4.9 (22.9)


X

IATP Table E
-
15 Test Case 74

91


IPv6 IP Sec SPD Security Parameter Ind
ex (SPI) (R)

UCR 2008 5.3.5.4.9 (22.10)


X

IATP Table E
-
15 Test Case 75

92


IPv6 IP Sec Internet Key Exchange (IKE) (R)

UCR 2008 5.3.5.4.9 (22.11)


X

IATP Table E
-
15 Test Case 76

93


IPv6 IP Sec Encapsulating Security Payload (ESP) (R)

UCR 2008 5.3.5.4.9 (22.1
2)

RFC 4303


X

IATP Table E
-
15 Test Case 77

94


IPv6 IP Sec ESP Anti
-
Replay (R)

UCR 2008 5.3.5.4.9 (22.12.1)


X

IATP Table E
-
15 Test Case 78

95


IPv6 IP Sec ESP Security Assocation (R)

UCR 2008 5.3.5.4.9 (22.12.2)


X

IATP Table E
-
15 Test Case 79

96


IPv6 IP Sec
Virtual Private Network Cryptographic
Algorithms (R)

UCR 2008 5.3.5.4.9 (22.13)

RFC 4308


X

IATP Table E
-
15 Test Case 80

LOC

97


IPv6 IP Sec AES
-
CBC with 128
-
bit Encryption (R)

UCR 2008 5.3.5.4.9 (22.13.1)


X

IATP Table E
-
15 Test Case 81

98


IPv6 IP Sec HMAC
-
S
HA1
-
96 AES
-
XCBC
-
MAC
-
96 (R)

UCR 2008 5.3.5.4.9 (22.13.2)


X

IATP Table E
-
15 Test Case 82

99


IPv6 IP Sec IKEv1 and IKEv2 (R)

UCR 2008 5.3.5.4.9 (22.14)

RFC 2409

RFC 4306


X

IATP Table E
-
15 Test Case 83

LOC

100


IPv6 IP Sec IKEv2 Maximum UDP Size (C)

UCR 2008 5.
3.5.4.9 (22.14.1)


X

IATP Table E
-
15 Test Case 84

101


IPv6 IP Sec IKE_SA DoS Prevention (C)

UCR 2008 5.3.5.4.9 (22.14.3)


X

IATP Table E
-
15 Test Case 85

102


IPv6 IP Sec IKEv2 Initial Message Rejection (C)

UCR 2008 5.3.5.4.9 (22.14.5)


X

IATP Table E
-
15 Test Ca
se 86

103


IPv6 IP Sec IKEv2 SA Closure (C)

UCR 2008 5.3.5.4.9 (22.14.6)


X

IATP Table E
-
15 Test Case 87

104


IPv6 IP Sec IKEv2 Extensible Authentication Protocol (EAP)
(C)

UCR 2008 5.3.5.4.9 (22.14.7)


X

IATP Table E
-
15 Test Case 88

105


IPv6 IP Sec IKEv2 Message
Response Limit (C)

UCR 2008 5.3.5.4.9 (22.14.8)


X

IATP Table E
-
15 Test Case 89

106


IPv6 IP Sec IKEv2 Temporary IP Address Rejection (C)

UCR 2008 5.3.5.4.9 (22.14.9)


X

IATP Table E
-
15 Test Case 90

107


IPv6 IP Sec IKEv2 Cryptographic Algorithm (C)

UCR 2008 5.3
.5.4.9 (22.14.10)

RFC 4307


X

IATP Table E
-
15 Test Case 91

LOC

108


IPv6 IP Sec IKEv2 VPN
-
B Suite (C)

UCR 2008 5.3.5.4.9 (22.14.11)

RFC 4308

RFC 4869


X

IATP Table E
-
15 Test Case 92

LOC

109


IPv6 IP Sec Extensions to the Internet IP Security Domain of
ISAKMP (R)

UCR 2008 5.3.5.4.9 (22.15)

RFC 2407


X

IATP Table E
-
15 Test Case 93

LOC

110


IPv6 IP Sec ISAKMP (R)

UCR 2008 5.3.5.4.9 (22.16)

RFC 2408


X

IATP Table E
-
15 Test Case 94

LOC

111


IPv6 IP Sec Authentication Header (R)

UCR 2008 5.3.5.4.9 (22.17)

RFC 4302


X

IATP Ta
ble E
-
15 Test Case 95

LOC

112


IPv6 IP Sec Manual Keying (R)

UCR 2008 5.3.5.4.9 (22.18)


X

IATP Table E
-
15 Test Case 96

113


IPv6 IP Sec ESP and AH Cryptographic Algorithm
Implementation (R)

UCR 2008 5.3.5.4.9 (22.19)

RFC 4305

RFC 4835


X

IATP Table E
-
15 Test Ca
se 97

LOC

114


IPv6 IP Sec IKEv1 Security Algorithm (R)

UCR 2008 5.3.5.4.9 (22.21)

RFC 4109


X

IATP Table E
-
15 Test Case 98

LOC

115


IPv6 SNMP MIB (C)

UCR 2008 5.3.5.4.10 (23)

RFC 4293

X

X

IATP Table E
-
15 Test Case 99

LOC

116


IPv6 SNMPv3 Management Framework (C)

UCR 2008 5.3.5.4.10 (23.1)

RFC 3411


X

IATP Table E
-
15 Test Case 100

LOC

117


IPv6 SNMPv3 Message Processing (C)

UCR 2008 5.3.5.4.10 (23.2)

RFC 3412


X

IATP Table E
-
15 Test Case 101

LOC

118


IPv6 SNMPv3 Applications (C)

UCR 2008 5.3.5.4.10 (23.3)

RFC 3413


X

IATP Table E
-
15 Test Case 102

LOC

119


IPv6 SNMP IP MIB (C)

UCR 2008 5.3.5.4.10 (24)

RFC 4293

X

X

IATP Table E
-
15 Test Case 103

LOC

120


IPv6 SNMP TCP MIB (C)

UCR 2008 5.3.5.4.10 (25)

RFC 4022

X

X

IATP Table E
-
15 Test Case 104

LOC



E
-
4



T
able E
-
4
-
2. CER Capability/Functional Requirements


ID

Requirement

Ref

IO

IA

Remarks

121


IPv6 SNMP UDP MIB (C)

U
CR 2008 5.3.5.4.10 (26)

RFC 4113

X

X

IATP Table E
-
15 Test Case 105

LOC

122


IPv6 SNMP IP Tunnel MIB (C)

UCR 2008 5.3.5.4.10 (27)

RFC 4087


X

IATP Table E
-
15 Test Case 106

LOC

123


IPv6 SNMP IP Forwarding MIB (C)

UCR 2008 5.3.5.4.10 (28)

RFC 4292


X

IATP Tabl
e E
-
15 Test Case 107

LOC

124


IPv6 Mobile IP Management MIB (C)

UCR 2008 5.3.5.4.10 (29)

RFC 4295


X

IATP Table E
-
15 Test Case 108

LOC

125


IPv6 SNMP Textual Conventions for IPv6 Flow Labels (C)

UCR 2008 5.3.5.4.10 (30)

RFC 3595


X

IATP Table E
-
15 Test Case
109

LOC

126


IPv6 SNMPv3 and IPSec (C)

UCR 2008 5.3.5.4.10 (31)

RFC 4807


X

IATP Table E
-
15 Test Case 110

LOC

127


IPv6 URI Syntax (C)

UCR 2008 5.3.5.4.10 (32)

RFC 3986


X

IATP Table E
-
15 Test Case 111

LOC

128


IPv6 Traffic Engineering Calculations (R)

UCR 2008 5
.3.5.4.11 (34)

X

X

IATP Table E
-
15 Test Case 113

LOC

129


IPv6 Traffic Engineering VoIP Subscribers (R)

UCR 2008 5.3.5.4.11 (35)

X

X

IATP Table E
-
15 Test Case 114

LOC

130


IPv6 Traffic Engineering Video Subscribers (R)

UCR 2008 5.3.5.4.11 (36)

X

X

IATP Table E
-
15 Test Case 115

LOC

131


IPv6 RADIUS (C)

UCR 2008 5.3.5.4.14 (47)

RFC 3162


X

IATP Table E
-
15 Test Case 129

LOC

132


IPv6 Home Agent Mobility Support (C)

UCR 2008 5.3.5.4.14 (48.1)

RFC 3775


X

IATP Table E
-
15 Test Case 131

LOC

133


IPv6 MIPv6 Mobile Node Secure
Signaling (C)

UCR 2008 5.3.5.4.14 (49)

RFC 3776

RFC 4877


X

IATP Table E
-
15 Test Case 132

LOC

134


IPv6 NEMO RFC Support (C)

UCR 2008 5.3.5.4.14 (51)

RFC 3963


X

IATP Table E
-
15 Test Case 133

LOC

135


IPv6 Differentiated Services (R)

UCR 2008 5.3.5.4.14 (52)

R
FC 2474

X

X

IATP Table E
-
15 Test Case 134

LOC

136


IPv6 Tunnel Broker RFC Support (C)

UCR 2008 5.3.5.4.14 (53)

RFC 3053


X

IATP Table E
-
15 Test Case 136

LOC

137


IPv6 Roaming Function (C)

UCR 2008 5.3.5.4.14 (54)

RFC 4282



X

IATP Table E
-
15 Test Case 137

LOC

138


IPv6 Point
-
to
-
Point Protocol (PPP) (C)

UCR 2008 5.3.5.4.14 (55)

RFC 2472

RFC 5072

X

X

IATP Table E
-
15 Test Case 138

LOC

139


Tactical CER requirements

UCR 2008 CH2 5.3.2.14.10



I
-
2 and LOC








E
-
4




Table
E
-
4
-
3. 4
-
Queue PHB Approach


Aggregated
Service

Class

Granular Service
Class

Priority/
Precedence

(see note)

DSCP

Base10

Queue

PHB

Network Control

Network Signaling
(OSPF, BGP IS
-
IS, etc.)


48

3

EF

Inelastic

Real
-
Time

User Signaling


40

Short Message

FO

32

Assured
Voice

FO

41

F

43

I

45

P

47

R

49

Assured Multimedia
Conferencing

FO

33

2

AF41

F

35

I

37

P

39

R

51

Preferred Elastic

Broadcast Video


24

AF42

Non
-
Assured Voice *


46

Multimedia

Streaming

(code points 34, 36, and
38 are for Non
-
Assure
d

Multimedia
Conferencing)

(The Non
-
Assured code
points appear in Queue
1)

FO

25

F

27

I

29

P

31

R

26

[28,30,34,36, 38]**

Low
-
Latency

Data

(IM, Chat, Presence)

FO

17

1

AF31

F

19

I

21

P

23

R

18 [20,22]**

High

Th
roughput

Data

FO

9

AF32

F

11

I

13

P

15

R

10

[12,14]**

OA&M

R

16

Elastic

Default


0

0

Default

Low Priority


8


LEGEND:

AF

-

Assured Forwarding

DSCP

-

Differentiated Services Code Point

EF

-

Expedited Forwarding

F

-

Flash

FO

-

Flash Override

I

-

Intermediate

IS
-
IS

-

Intermediate System
-
Intermediate System



OA&M

-

Operations, Administration, and Maintenance

OSPF

-

Open Shortest Path First

P

-

Priority

PHB

-

Per Hop Behavior

R

-

Routine

VTC

-

Video Teleconferencing

*For a defini
tion see Section A2


Glossary

** Code points in brackets are reserved for non
-
conformance
marking.




E
-
4




Table
E
-
4
-
4. 8
-
Queue PHB Approach


Granular Service Class

Priority/
Precedence

(see note)

DSCP

Base10

Queue

CER

PHB

Network Signaling (See Table Below
.)


48

7

EF

User Signaling

40

Short Message

FO

32

6

Assured Voice

FO

41

F

43

I

45

P

47

R

49

Assured Multimedia Conferencing

FO

33

5

AF41

F

35

I

37

P

39

R

51

Broadcast Video

NA

24

4

AF31

Non
-
Assured Voice*

NA

46

Multimedia Streaming (code points 34,
36, and 38 are for Non
-
Assured
Multimedia Conferencing)

(The Non
-
Assured code points appear in

Queue 4)

FO

25

F

27

I

29

P

31

R

26
[28,30,34,36,38]**

Low
-
Latency

Data

(IM, Chat, Presence)

FO

17

3

AF
21

F

19

I

21

P

23

R

18

[20,22]**

High

Throughput

Data

FO

9

2

AF12

F

11

I

13

P

15

R

10

[12,14]**

OA&M

NA

1
6

1

AF11

Best Effort

NA

0

0

Default

Low Priority

NA

8


LEGEND:

AF

-

Assured Forwarding

DSCP

-

Differentiated S
ervices Code Point

EF

-

Expedited Forwarding

F

-

Flash

FO

-

Flash Override

I

-

Intermediate

IS
-
IS

-

Intermediate System
-
Intermediate System



OA&M

-

Operations, Administration, and Maintenance

OSPF

-

Open Shortest Path First

P

-

Priority

PHB

-

Per Hop Beha
vior

R

-

Routine

VTC

-

Video Teleconferencing

*For a definition see Section A2


Glossary

** Code points in brackets are reserved for non
-
conformance
marking.




E
-
4



E
-
4
-
4.
Effective

Throughput and Serialization Delay


The Effective Throughput Calculator
is a
n Excel spreadsheet that
should be used to determine
the maximum concurrent voice and video sessions for each queue depending upon IUT type and
associated overhead. Configure TMDE pair to load each Interface Under Test (IUT) queue with the
maximum voice a
nd video sessions as specified without exceeding allocated bandwidth of each
queue. Verify that the TMDE sample size and payload size are equal to value in calculator. If the
TMDE values differ, then input values used by TMDE into calculator to determine

the proper
maximum sessions in queue prior to the utilization of the QoS features of the CER. For example: The
Calculator has L5 populated with the SRTP value of 12 Bytes. If SRTP is not being used, then
configure L5=0.

Per UCR,
serialization delay mu
st be

allowed for in
all CER latency measurements. It is the
fixed delay associated with clocking an IP frame onto a network interface. It directly depends

upon
the line rate of the IUT and the frame size. Serialization delay (ms) = Frame size (bits) /
Line rate
(kbps).

The serialization delay calculation is also performed by the Effective Throughput Calculator.
The
Effective Throughput Calculator

file should be co
-
located with the Unified Capabilities Generic
Test Procedures.
It is titled: “filename.x
ls”



E
-
4
-
5. Data Collection


This procedure is formatted such that printed copies can be used for data collection.
Additionally, a Data Collection Form (DCF) was created in an Microsoft Excel format for computer
based collection and storage. The DCF fil
e should be co
-
located with the Unified Capabilities
Generic Test Procedures. It is titled: “filename.xls”



E
-
4



Table E
-
4
-
5. CER
Test Procedures

(1)
Configuration, Compliance and Availability

REFERENCE:


UCR 2008, Sect. 5.3.2.14.7
(Availability);
5.3.2.5.2

(System Quality Factors);
5.3.2.5.2.2 (Availability/SQF, Maximum Downtime)

REQUIREMENT
: (Required)
High Availability with SQF
and

Medium Availability with
out

SQF.

(Conditional)

Medium Availability with SQF or Low availability

TEST SETUP:



1. Capture the

SUT’s configuration files and attach to the test plan or DCF.

2.
Provide documentation to support the
Reliability Computation c
ompliance
l
etter supplied

and
compliance with System Quality Factors.




CRITERIA:



High Availability
(HA)
CE Router
: T
he syst
em shall have an availability of 99.999 percent,
including scheduled hardware and software maintenance (non
-
availability of no more than 5
minutes per year). The system shall meet the requirements specified in UCR 2008, Section
5.3.2.5.2, System Quality Fa
ctors.

Medium Availability

(MA)

CE Router without SQF
: Availability =
99.99 percent

(
52.5 min
/
year).

Medium Availability

(MA)

CE Router with SQF
: Availability =
99.99 percent

(
52.5 min
/
year)

& SQF

Low Availability

(LA)

CE Router:

Availability =
99.9 perce
nt

(8.76 hours/
year).

NOTE: SQF’s associated with failover and software updates require additional testing in
subsequent procedures of this test plan.

PROCEDURE:

RESULTS:




HA

w/ SQF

MA

w/o SQF

MA

w/ SQF

LA

w/o SQF

1.

Capture the CER configuration inf
ormation on supported interfaces and queuing supported.

1.

Configuration data captured

YES/NO

YES/NO

YES/NO

YES/NO

2.

Review system diagram that was submitted to the test agency and verify that the components
and provisioned links are identical to physic
al system configured for test.

2.

Submitted system diagram components
and links match system under test.

YES/NO

YES/NO

YES/NO

YES/NO

3.

Dual Power Supplies: Verify redundant power supplies
each
have

a power capacity to support
the entire chassis’s elec
trical load

3.

Dual power supplies provided and each are
rated to support entire chassis

YES/NO

N/A

YES/NO

N/A

4.

Dual Processors/Swappable Sparing (Control Supervisors)
:

Verify t
he chassis support dual
active processors, or processor card automatic swap
pable sparing
.

4.

Dual Processor or Swappable Sparing
supported.

YES/NO

N/A

YES/NO

N/A

5.

Termination Sparing. The chassis shall support a (N+1) sparing capability for available 10/100
-
Mbps Ethernet modules used to terminate an IP voice or video subscribe
r.

5.

Termination sparing supported

YES/NO

N/A

YES/NO

N/A

6.

Redundancy Protocol
: Verify t
he routing equipment support
s

a protocol that allows for
dynamic rerouting of IP packets or Ethernet frames so that no single point of failure exists in the
Assured

Services subsystem.

6.

Redundancy protocols supported.

YES/NO

N/A

YES/NO

N/A

Record protocols:


7.

No Single Failure Point
: Verify that n
o single point shall exist in the subsystem that could
cause the loss of voice and/or video service to more than 9
6 voice or video EIs or GEIs.

7. No single point of failure exists in system.

YES/NO

N/A

YES/NO

N/A

8
.

Switch Fabric or Backplane Redundancy for Active Backplanes
: Verify that a
ctive switching
platforms within the subsystem components shall support a red
undant (1+1) switching fabric or
backplane. The second fabric’s backplane shall be in active standby so failure of the first
backplane shall not cause the loss of any ongoing events within the platform.

8.

System contains (1+1) switching fabric or
backpla
ne.

YES/NO

N/A

YES/NO

N/A

9.

Review the
reliability computation
compliance documentation

and verify the
system described
in the documentation
has
the

same components and configuration as the

SUT?

9.

SUT Components and Configuration are
same as reliability

model

YES/NO

YES/NO

YES/NO

YES/NO

10.

Verify that the Reliability Computation compliance letter assures that the maximum downtime
for IP network links is equal or less than 35 minutes per year.

10.

Reliability Computation meets IP link
downtime requireme
nts (35min/year)

YES/NO

N/A

YES/NO

N/A

11.

Do
the results of the calculations

show a reliability of 99.999% (high availability?

11.

Does the system meet reliability of 99.999?

YES/NO

N/A

N/A

N/A

12.

Do
the results of the calculations

show a reliability
of 99.99% (medium availabililty)?

12.

Does the system meet reliability of 99.99?


N/A

YES/NO

YES/NO

N/A

13.

Do
the results of the calculations

show a reliability of 99.9% (low availabililty)?

13.

Does the system meet reliability of 99.9?

N/A

N/A

N/A

YES
/NO

14.

Check the calculations for accuracy
.

14.

Verify that calculations are accurate.

YES/NO

YES/NO

YES/NO

YES/NO



E
-
4



Table E
-
4
-
5. CER
Test Procedures

(2)
Performance Characteristics & Traffic Conditioning, DSCP 4
-
queue PHB

REFERENCE:

5.3.2.14.1 (Traff
ic Cond.); 5.3.2.14.2 (DSCP); 5.3.3.3.2 (DSCP); 5.3.2.14.3 (PHB);
5.3.3.3.3 (PHB); 5.3.3.3.4 (DSCP Cond.); 5.3.2.14.8 (Latency); 5.3.3.5.4 (CE Jitter); 5.3.3.6.4
(Packet Loss); 5.3.3.15 (MOS); 5.3.2.17.3.4.2.12 (Queue Control)

REQUIREMENT
: (Required)
All


TEST SETUP:

Configure CER in configuration specified in Figure E
-
4
-
2 for Ethernet interfaces
and Figure E
-
4
-
3 for TDM and Serial interfaces. Configure the CER for traffic conditioning
(policing and shaping) on inbound and outbound traffic. Configure

Interface Under Test (IUT)
between SUT and TMDE 1. Configure loading interface(s) between SUT and TMDE 2 to exceed
the bandwidth of IUT. Configure the CER with 4 queues as specified in CRITERIA paragraph.
Configure TMDE to provide a bi
-
directional dual

stack (IPv4/IPv6) No Load Baseline (NLB) for
each queue of IUT as follows:

(a) Queue
-
0: Configure DD load for 100% of Queue
-
0 (25% of total IUT bandwidth) with DSCP=0.

(b) Queue
-
1: Configure PD load for 100% of Queue
-
1 (25% of total IUT bandwidth) with
D
SCP=23.

(c) Queue
-
2: Configure video load with a quantity of video sessions that does not exceed the
available bandwidth for Queue
-
2, including overhead Use DSCP=38.

(d) Queue
-
3: Configure EF voice load with a quantity of voice sessions that does not excee
d the
available bandwidth for Queue
-
3, including overhead. Use DSCP=48.


TEST SETUP NOTES
:

1. Use Effective Throughput Calculator to determine the quantity of IPv4 and IPv6 voice/video
performance pairs to fill up the respective queues without exceeding t
he bandwidth.

2. Voice/video performance pairs can be used in the data queues (with DSCP tagged the same as
the respective queues) to provide performance data for each queue.

3. If TMDE cannot provide a full performance measurement for each queue, then ass
ure that a
minimum of 1% of the bandwidth is configured as performance. The rest of the traffic can be a
non
-
performance load (with DSCP tagged the same as the respective queues)

As per 5.3.3.4
which states the queue shaping will be within 10% of the queu
e bandwidth. Example: A 25Mbps
queue must have a variance of not more than plus or minus 2.5Mbps.

CRITERIA:


Queue
-
0


Default Data (DD) queue (best effort):

Allocate 25% of available link to queue. Map
traffic with DSCP=0 to Queue
-
0. This is the onl
y queue authorized to burst to 100%.

Queue
-
1
-

Preferred Data (PD) queue:

(AF31 and AF32). Allocate 25% of available link to the
queue. Map DSCPs 9
-
11,13,15
-
19,21,23 to queue.

Queue
-
2
-

Interactive VTC and streaming multimedia (Video) queue:

(AF41 and AF4
2). Allocate
25% of available link to the queue. Map DSCPs 25
-
27,29,31,33
-
35,37
-
38 to queue.

Queue
-
3


Voice and Network Signaling / Expedited Forwarding (EF) Queue
. Allocate 25% of
available link to EF queue. Map DSCPs 40
-
48 to EF queue. Network Sig
naling (DSCP 48), user
signaling (DSCP 40) and voice traffic (DSCPs 41
-
43,45
-
46).


Latency
:
Latency requirements include tolerance for serialization delay which is affected by
packet size and IUT transmission rate. Use Effective Throughput Calculator for

Serialization delay
calculation. Latency average is required to be less than (2ms+Serialization delay) for any five
minute period.

Jitter
: Jitter average is required to be less than 3 ms for any five minute period.

Packet Loss
: Packet Loss average shoul
d be less than 0.05% for any five minute period for no
load scenario.

MOS
: 95% of the voice sessions must not have MOS results less than 4.0 for any five minute
period of time.

SCOPE:

This procedure must be conducted for every interface type supported b
y CER.


SUT CONFIGURATION FOR THIS PROCEDURE:

IUT Interface Type: __________________

PROCEDURE:

RESULTS:

1. Connect to CER and perform the following:

1a. Verify that queue control permits bandwidth allocations by amount or percentage per queue.

1b. Veri
fy that queue control permits drop probability configuration within each queue.

1c. Copy CER configuration and save for documentation (include queuing setup/config).



1a. Queue control permits bandwidth adjustment by amount or percentage

YES / NO

1b. Queu
e control permits drop probability configuration

YES / NO

1c. Documentation saved?

YES / NO


NOTES:











E
-
4



Table E
-
4
-
5. CER
Test Procedures


(2)
Performance Characteristics & DSCP Traffic Conditioning, DSCP 4
-
queue PHB (Continued)

PROCEDURE:

RESULTS
:

2
. Initiate NLB on all queues for 1 hour and record the performance data. Verify that the
performance measurements do not exceed requirements for any given five minute period of time

2
a.
Record performance data averages from

DD

traffic (
Queue
-
0
):

Late
ncy:

Highest :_________ms


Meets Req.

YES / NO

2
b.
Record performance data averages from

PD traffic (
Queue
-
1
):

Latency:

Highest :_________ms Meets Req.

YES / N
O

2
c.
Record performance data averages from

V
ideo traffic (
Queue
-
2
):

Latency:

Highest :_________ms Meets Req.

YES / NO

Jitter
:

Highest
--
5min avg
.:_________ ms

Meets Req.

YES /

NO

Packet

Loss:

Highest
--
5min avg
.:_________ Packets

Meets Req.

YES / NO

MOS: Lowest
--
5min avg.
: _________

Meets Req.

YES / NO

2
d.
Record performance data averages from

EF

traffic (
Qu
eue
-
3
):

Latency:

Highest :_________ms Meets Req.

YES / NO

Jitter
:

Highest
--
5min avg.:_________ ms Meets Req.

YES / NO

Packet

Loss:

Highest
--
5min avg.:_________ Packets

Meets Req.

YES / NO

MOS: Lowest
--
5min avg.: _________ Meets Req.

YES / NO


3. Stop NLB load.

4
.

Initiate
DD

load
to 4X of Queue
-
0 bandwidth (
bursting to 1
00% of IUT bandwidth), DSCP=0
.

5
.

In
itiate
PD load for 100% of
Q
ueue
-
1 bandwidth
, DSCP=23

(25% of total IUT bandwidth)
.


6.

Initiate Video load for 100% of
Q
ueue
-
2 bandwidth
, DSCP=38

(25% of total IUT bandwidth)
.



7.

I
nitiate EF load for 100% of
Q
ueue
-
3 bandwidth
, DSCP=48

(25% of total IUT

bandwidth)
.


3. NLB load stopped?

YES / NO

4
.


CER permits DD traffic to burst to 100% of IUT bandwidth.

YES / NO

5a.

Queue
-
0 DD traffic is reduced from 100% to 75%

YES / NO

5b.

Queue
-
1 PD traffic is 100%

YES / NO

6a.

Queue
-
0 DD traffic is reduced from

75% to 50%

YES / NO

6b.

Queue
-
1 PD traffic is 100%

YES / NO

6c.


Queue
-
2 Video traffic is 100%

YES / NO

7a.

Queue
-
0 DD traffic is reduced from 50% to 25%

YES / NO

7b.

Queue
-
1 PD traffic is 100%

YES / NO

7c.


Queue
-
2 Video traffic is 100%

YES / NO

7d.

Qu
eue
-
3 EF traffic is 100%

YES / NO

NOTES:














E
-
4



Table E
-
4
-
5. CER
Test Procedures


(2)
Performance Characteristics & DSCP Traffic Conditioning, DSCP 4
-
queue PHB (Continued)

PROCEDURE:

RESULTS:

8.

Allow load initiated in steps 4 to 7 to run for 1

hour and record the performance data. Verify
that the only packet loss occurs on DD load (Queue
-
0).
Additionally, traffic could be delayed in
Queue
-
0 as a result of traffic conditioning.

V
erify that

the performance measurements for the other
queues

do n
ot exceed requirements for any given five minute period of time


If DD load is equal to 4X of Queue
-
0 bandwidth

and all other loads are at 100% of the bandwidth
of their respective queues, then DD load (Queue
-
0) packet loss should equal
approximately 75%
o
f total Queue
-
0 load.

8
a.
Record performance data averages from

DD

traffic (
Queue
-
0
):

Latency:

Highest
.:_________
ms
(possible degradation)

Jitter
:

Highest .:__________ms



Meets Req.

YES / NO

Packet

Loss:

Highest
--
5min avg
.:_________ %

(approx 75% Loss)

8
b.
Record performance data averages from

PD traffic (
Queue
-
1
):

Latency:

Highest :_________ms Meets

Req.

YES / NO

Jitter
:

Highest
--

.:_________ ms Meets Req.

YES / NO

Packet

Loss:

Highest
.:_________ Packets Meets Req.

YES / NO

8
c.
Record performance data averages from

V
ideo traffic (
Queue
-
2
):

Latency:

Highest :_________ms Meets Req.

YES / NO

Jitter
:

Highest
--

.:_________ ms Meets Req.

YES / NO

Packet

Loss:

Highest
-


.:_________ Packets


Meets Req.

YES / NO

MOS: Lowest
--
5min avg.: _________ Meets Req.

YES / NO

8
d.
Record performance data averages from

EF

traffic (
Queue
-
3
):

Latency:

Highest :_____
____ms Meets Req.

YES / NO

Jitter
:

Highest
.:_________ ms Meets Req.

YES / NO

Packet

Loss:

Highest
--
5min avg.:_________ Packets Meets Req
.

YES / NO

MOS: Lowest
--
5min avg.: _________ Meets Req.

YES / NO


9.

Reduce DD load to 100% of Queue
-
0 bandwidth (25% of total IUT bandwidth). Increase PD
load to 2X of Queue
-
1 bandwidth (50% of total IUT

bandwidth). Maintain the Video and EF loads
at 100% of their respective queues and allow load to run for 1 hour. Verify that the only packet
loss occurs on PD load (Queue
-
1).
Additionally, traffic could be delayed in Queue
-
1 as a result of
traffic cond
itioning

V
erify that

the performance measurements for the other queues

do not
exceed requirements for any given five minute period of time..


If PD load is equal to 2X of Queue
-
1 bandwidth
, and the other loads are at 100% of the bandwidth
in their respec
tive queues, then
PD load (Q
ueue
-
1) packet loss should equal
approximately 50%
of total PD load..

9
a.
Record performance data averages from

DD

traffic (
Queue
-
0
):

Latency:

Highest :_________ms Meets Req.

YES
/ NO

Jitter
:

Highest
--
5min avg.:_________ ms Meets Req.

YES / NO

Packet

Loss:

Highest
--
5min avg.:_________ Packets Meets Req.

YES / NO

9
b.
Record performance data averages from

PD traffic (
Queue
-
1
):

La
tency:

Highest :_________ms Meets Req.

YES / NO

Jitter
:

Highest
--
5min avg.:_________ ms Meets Req.

YES / NO

Packet

Loss:

Highest
--
5min avg.:_________ Packets

Meets Req.

YES / NO

9
c.
Record performance data averages from

V
ideo traffic (
Queue
-
2
):

Latency:

Highest :_________ms Meets Req.

YES / NO

Jitter
:

Highest
.:_________ ms Mee
ts Req.

YES / NO

Packet

Loss:

Highest
--
5min avg.:_________ Packets Meets Req.

YES / NO

MOS: Lowest
--
5min avg.: _________ Meets Req.

YES / NO

9
d.
Record performance data averages from

EF

traffic (
Queue
-
3
):

Latency:

Highest :_________ms Meets Req.

YES / NO

Jitter
:

Highest
:_________ ms Meets Req.

YES / NO

Packet

Loss:

Highest
--
5min avg.:_________ Packets

Meets Req.

YES / NO

MOS: Lowest
--
5min avg.: _________ Meets Req.

YES / NO


NOTES:










E
-
4



Table E
-
4
-
5. CER
Test Procedures



(2)
Performance Characteristics & DSCP Traffic Conditioning
, DSCP 4
-
queue PHB (Continued)

PROCEDURE:

RESULTS:

10. Reduce PD load back to its NBL load value of 100 % bandwidth of Queue
-
1. Initiate NBL load
on all four queues and verify that load is running without performance loss.

11. Increase Video load (Queu
e
-
2) by adding 2X additional video session(s) (50% of total IUT
bandwidth). Run load for 1 hour and record the following performance data results. Verify that the
only packet loss occurs on Video load (Queue
-
2).
Additionally, traffic could be delayed an
d MOS
results effected in Queue
-
2 as a result of traffic conditioning

V
erify that

the performance
measurements for the other queues

do not exceed requirements for any given five minute period
of time.


If Video load is equal to 2X of Queue
-
2 bandwidth
, a
nd the other loads are at 100% of the
bandwidth in their respective queues, then
Video load (Q
ueue
-
2) packet loss should equal
approximately 50% of total Video load..






10. NBL returned to normal operation (total of 100% of IUT bandwidth) without


per
formance loss.

YES / NO

11
a.
Record performance data averages from

DD

traffic (
Queue
-
0
):

Latency: Highest _________ms

Meets Req.

YES / NO

Jitter: Highest _________ms


Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.:_________

Meets Req.

YES / NO

11
b.
Record performance data averages from

PD traffic (
Queue
-
1
):

Latency: Highest _________ms

Meets Req.

YES / NO

Jitter: Highest _________ms

Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.:_________

Mee
ts Req.

YES / NO

11c.

Record performance data averages from

V
ideo traffic (
Queue
-
2
):

Latency:

Highest
_________
(possible degradation)

Jitter: Highest _________ms


Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.:_________
(approx 50% Loss)

MOS: Lowest
--
5min avg.: _________

(pos
sible
degradation)

11
d.
Record performance data averages from

EF

traffic (
Queue
-
3
):

Latency:

Highest :_________ms Meets Req.

YES / NO

Jitter
:

Highest
--
5min avg.:_________ ms Me
ets Req.

YES / NO

Packet

Loss:

Highest
--
5min avg.:_________ Packets Meets Req.

YES / NO

MOS: Lowest
--
5min avg.: _________ Meets Req.

YES / NO

12. Reduce Video load back to its NBL l
oad value of 100 % bandwidth of Queue
-
2. Initiate NBL
load on all four queues and verify that load is running without performance loss.

13. Increase EF load (Queue
-
3) by adding 2X additional voice session(s) (50% of total IUT
bandwidth). Run load for 1 h
our and record the following performance data results. Verify that the
only packet loss occurs on EF load (Queue
-
3).
Additionally, traffic could be delayed and MOS
results effected in Queue
-
3 as a result of traffic conditioning

V
erify that

the performa
nce
measurements for the other queues

do not exceed requirements for any given five minute period
of time.


If EF load is equal to 2X of Queue
-
3 bandwidth
, and the other loads are at 100% of the bandwidth
in their respective queues, then EF

load (Q
ueue
-
3)
packet loss should equal
approximately 50% of
total EF load.





12. NBL returned to normal operation (total of 100% of IUT bandwidth) without


performance loss.

YES / NO

13
a.
Record performance data averages from

DD

traffic (
Queue
-
0
):

Latency: High
est _________ms

Meets Req.

YES / NO

Jitter: Highest _________ms

Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.:_________


Meets Req.

YES / NO

13
b.
Record performance data averages from

PD traffic (
Queue
-
1
):

Latency: Highest _________ms

Meets Req.

YES / NO

Jitter: Highest _________ms


Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.:_________

Meets Req.

YES / NO

13c.

Record performance data averages from

V
ideo traffic (
Queue
-
2
):

Latency:

Highest :_
________ms Meets Req.

YES / NO

Jitter
:

Highest
--
5min avg.:_________ ms Meets Req.

YES / NO

Packet

Loss:

Highest
--
5min avg.:_________ Packets Meets Req.

Y
ES / NO

MOS: Lowest
--
5min avg.: _________ Meets Req.

YES / NO

13
d.
Record performance data averages from

EF

traffic (
Queue
-
3
):

Latency:

Highest
--
5min avg.:

_______
__ms

(possi
ble degradation)

Jitter
:

Highest
.:
_________
Meets Req.

YES / NO

Packet

Loss:

Highest
--
5min avg.
:_________%


(approx 50% Loss)

MOS: Lowest
--
5min avg.: ___
____
__

(possible degradation)

NOTES:







E
-
4



Table E
-
4
-
5. CER
Test Procedures


(3)
Performance Characteristics & Traffic Conditioning, DSCP 8
-
Queue PHB

REFERENCE:

5.3.2.14.1 (Traffic Cond.); 5.3.2.14.2 (DSCP); 5.3.3.
3.2 (DSCP); 5.3.2.14.3
(PHB); 5.3.3.3.3 (PHB); 5.3.3.3.4 (DSCP Cond.); 5.3.2.14.8 (Latency); 5.3.3.5.4 (CE Jitter);
5.3.3.6.4 (Packet Loss); 5.3.3.15 (MOS); 5.3.2.17.3.4.2.12 (Queue Control)

REQUIREMENT
: (Conditional)
8
-
Queue PHB


(Required)
All Performanc
e Characteristics


TEST SETUP:

Configure CER in configuration specified in Figure E
-
4
-
2 for Ethernet interfaces
and Figure E
-
4
-
3 for TDM and Serial interfaces. Configure the CER for traffic conditioning
(policing and shaping) on inbound and outbound tra
ffic. Configure Interface Under Test (IUT)
between SUT and TMDE 1. Configure loading interface(s) between SUT and TMDE 2 to exceed
the bandwidth of IUT. Configure the CER with 8 queues as specified in CRITERIA paragraph.
Configure TMDE to provide a bi
-
directional dual stack (IPv4/IPv6) No Load Baseline (NLB) for
each queue of IUT as follows:

(a) Queue
-
0: Configure DD load for 100% of Queue
-
0 (12.5% of total IUT BW). Use DSCP=0.

(b) Queue
-
1: Configure OAM load for 100% of Queue
-
1 (12.5% of total IUT BW
). Use DSCP=10

(c) Queue
-
2: Configure HTD load for 100% of Queue
-
2 (12.5% of total IUT BW). Use DSCP=15.

(d) Queue
-
3: Configure EF load for 100% of Queue
-
3 (12.5% of total IUT BW). Use DSCP=48.

(e) Queue
-
4: Configure LLD load for 100% of Queue
-
4 (12.5%
of total IUT BW). Use DSCP=23.

(f) Queue
-
5: Configure MM load for 100% of Queue
-
5 (12.5% of total IUT BW). Use DSCP=31.

(g) Queue
-
6: Configure Video load with a quantity of video sessions that does not exceed the
available bandwidth for Queue
-
6, includi
ng overhead. Use DSCP=38.

(h) Queue
-
7: Configure VOICE voice load with a quantity of voice sessions that does not exceed
the available bandwidth for Queue
-
7, including overhead. Use DSCP=46.


TEST SETUP NOTES
:

1. Use Effective Throughput Calculator to de
termine the quantity of IPv4 and IPv6 voice/video
performance pairs to fill up the respective queues without exceeding the bandwidth.

2. Voice/video performance pairs can be used in the data queues (with DSCP tagged the same as
the respective queues) to pr
ovide performance data for each queue.

3. If TMDE cannot provide a full performance measurement for each queue, then assure that a
minimum of 1% of the bandwidth is configured as performance. The rest of the traffic can be a
non
-
performance load (with DSC
P tagged the same as the respective queues)

) As per 5.3.3.4
which states the queue shaping will be within 10% of the queue bandwidth. Example: A 25Mbps
queue must have a variance of not more than plus or minus 2.5Mbps.

CRITERIA:

Queue
-
0


Default Data (
DD) queue (best effort):

Allocate 12.5% of available link to queue. Map
traffic with DSCP=0 to Queue
-
0. This is the only queue authorized to burst to 100%.

Queue
-
1


Operations, Administration, and Maintenance (OAM) queue:

(AF12). Allocate 12.5% of
ava
ilable link to the queue. Map DSCP 10 to queue.

Queue
-
2


High Throughput Data (HTD) queue:

(AF11). Allocate 12.5% of available link to the
queue. Map DSCPs 9,11,13,15 to queue.

Queue
-
3


Signaling/EF (EF) queue
. Allocate 12.5% of available link to EF qu
eue. Map DSCPs
40 (User Signaling) and 48 (Network Signaling) to queue

Queue
-
4


Low Latency Data (LLD) queue:

(AF21). Allocate 12.5% of available link to the queue.
Map DSCPs 17,19,21,23 to queue.

Queue
-
5


Multimedia Streaming (MM) queue:

(AF31, AF32
). Allocate 12.5% of available link to
the queue. Map DSCPs 25
-
27,29,31 to queue.

Queue
-
6
-

Interactive VTC and streaming multimedia (VIDEO) queue:

(AF41). Allocate 12.5% of
available link to the queue. Map DSCPs 33
-
35,37,38 to queue.

Queue
-
7


Voice/EF

(VOICE) queue
. Allocate 12.5% of available link to VOICE queue. Map
DSCPs 41
-
43,45
-
46 to VOICE queue.


Latency
:
Latency requirements include tolerance for serialization delay which is affected by
packet size and IUT transmission rate. Use Effective T
hroughput Calculator for Serialization delay
calculation. Latency average is required to be less than (2ms+Serialization delay) for any five
minute period.

Jitter
: Jitter average is required to be less than 3 ms for any five minute period.

Packet Loss
: P
acket Loss average should be less than 0.05% for any five minute period for no
load scenario.

MOS
: 95% of the voice sessions must not have MOS results less than 4.0 for any five minute
period of time.

SCOPE:

This procedure must be conducted for every in
terface type supported by CER.


SUT CONFIGURATION FOR THIS PROCEDURE:

IUT Interface Type: __________________

PROCEDURE:

RESULTS:

1. Connect to CER and perform the following:

1a. Verify that queue control permits bandwidth allocations by amount or percen
tage per queue.

1b. Verify that queue control permits drop probability configuration within each queue.

1c. Copy CER configuration and save for documentation (include queuing setup/config).



1a. Queue control permits bandwidth adjustment by amount or perc
entage

YES / NO

1b. Queue control permits drop probability configuration

YES / NO

1c. Documentation saved?


YES / NO

NOTES:








E
-
4



Table E
-
4
-
5. CER
Test Procedures


(3)
Performance Characteristics & Traffic Conditioning, DSCP 8
-
Queue PHB (Continued
)

PR
OCEDURE:

RESULTS:

2. Initiate NLB on all queues for 1 hour and record the performance data. Verify that the performance
measurements do not exceed requirements for any given five minute period of time.

































3. Stop NLB load.

4
.

Initiate DD load to 8X of Queue
-
0 bandwidth (bursting to 100% of IUT bandwidth), DSCP=0.

5.

Initiate
OAM load for 100% of Queue
-
1 bandwidth, DSCP=10 (12.5% of total IUT bandwidth)
.


6.

Initiate HTD load for 100% of Queue
-
2 bandwidth, DSCP=15
(12.5% of t
otal IUT bandwidth)
.


7.

Initiate EF load for 100% of Queue
-
3 bandwidth, DSCP=18
(12.5% of total IUT bandwidth)
.


8.

Initiate LLD load for 100% of Queue
-
4 bandwidth, DSCP=23
(12.5% of total IUT bandwidth)
.


9.

Initiate MM load for 100% of Queue
-
5 bandwid
th, DSCP=31
(12.5% of total IUT bandwidth)
.


10.

Initiate
VIDEO

load for 100% of Queue
-
6 bandwidth, DSCP=38
(12.5% of total IUT bandwidth)
.


11.

Initiate VOICE load for 100% of Queue
-
7 bandwidth, DSCP=48
(12.5% of total IUT bandwidth)
.


2a. Record perfo
rmance data averages from DD traffic (Queue
-
0):

Latency: Highest _________ms

Meets Req.

YES / NO

Jitter: Highest _________ms

Meets Req.

YES

/ NO

Packet Loss:

Highest
--
5min avg.:_________


Meets Req.

YES / NO

2b. Record performance data averages from OAM traffic (Queue
-
1):

Latency: Highest _________ms

Mee
ts Req.

YES / NO

Jitter: Highest _________ms

Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.:_________

Meets Req.

YES / NO

2c. Record performance data avera
ges from HTD traffic (Queue
-
2):

Latency: Highest _________ms

Meets Req.

YES / NO

Jitter: Highest _________ms

Meets Req.

YES / NO

Packet Los
s:

Highest
--
5min avg.:_________

Meets Req.

YES / NO

2d. Record performance data averages from EF traffic (Queue
-
3):

Latency: Highest _________ms

Meets Req.

YES / NO

Jitter: Highest _________ms

Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.:_________

Meets Req.

YES / NO

2e. Record performance data averages from LLD traf
fic (Queue
-
4):

Latency: Highest _________ms

Meets Req.

YES / NO

Jitter: Highest _________ms

Meets Req.

YES / NO

Packet Loss:

Highest
--
5min
avg.:_________

Meets Req.

YES / NO

2f. Record performance data averages from MM traffic (Queue
-
5
)

Latency: Highest _________ms

Meets Req.

YES / NO

Jitter: Highe
st _________ms

Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.:_________

Meets Req.

YES / NO

2g. Record performance data averages from
VIDEO

traffic (Queue
-
6):

L
atency: Highest _________ms

Meets Req.

YES / NO

Jitter: Highest _________ms

Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.:_________


Meets Req.

YES / NO

MOS: Lowest
--
5min avg.: _________


Meets Req.

YES / NO

2h. Record performance data averages from VOICE traffic (Queue
-
7):

Latency: Highest _________ms


Meets Req.

YES / NO

Jitter: Highest _________ms



Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.:_________



Meets Req.

YES / NO

MOS: Lowest
--
5min avg.: _________


Meets Req.

YES / NO

3. NLB load stopped?

YES / NO

4.

CER permits DD traffic to burst to 100% of IUT bandwidth.

YES / NO

5a.

Queue
-
0 (DD) traffic i
s reduced from 100% to 87.5%

YES / NO

5b.

Queue
-
1 traffic is 100%

YES / NO

6a.

Queue
-
0 (DD) traffic is reduced from 87.5% to 75%

YES / NO

6b.

Queue
-
1 and 2 traffic is 100%

YES / NO

7a.

Queue
-
0 (DD) traffic is reduced from 75% to 62.5%

YES / NO

7b.

Queue
-
1, 2, and 3 traffic is 100%

YES / NO

8a.

Queue
-
0 (DD) traffic is reduced from 62.5% to 50%

YES / NO

8b.

Queue
-
1, 2, 3, and 4 traffic is 100%

YES / NO

9a.

Queue
-
0 (DD) traffic is reduced from 50% to 37.5%

YES / NO

9b.

Queue
-
1, 2, 3, 4, and 5 traffic is 100
%

YES / NO

10a.

Queue
-
0 (DD) traffic is reduced from 37.5% to 25%

YES / NO

10b.

Queue
-
1, 2, 3, 4, 5 and 6 traffic is 100%

YES / NO

11a.

Queue
-
0 (DD) traffic is reduced from 25% to 12.5%

YES / NO

11b.

Queue
-
1, 2, 3, 4, 5, 6 and 7 traffic is 100%

YES / NO



E
-
4



Table E
-
4
-
5. CER
Test Procedures


(3)
Performance Characteristics & Traffic Conditioning, DSCP 8
-
Queue PHB (
Continued)

PROCEDURE:

RESULTS:

12.

Allow load initiated in steps 4 to 11 to run for 1 hour and record the performance data.


Verify that the onl
y packet loss occurs on DD load (Queue
-
0).
Additionally, traffic could be
delayed in Queue
-
0 as a result of traffic conditioning.

V
erify that

the performance measurements
for the other queues

do not exceed requirements for any given five minute period of
time


If DD load is equal to 8X of Queue
-
0 bandwidth

and all other loads are at 100% of the bandwidth
of their respective queues, then DD load (Queue
-
0) packet loss should equal
approximately 87.5%
of total Queue
-
0 load.

1
2a. Record performance data averag
es from DD traffic (
Queue
-
0
):

Latency: Highest _________ms

Meets Req.

YES / NO

Jitter: Highest _________ms

Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.
:_________


(Approx 87.5% Loss)


1
2b. Record performance data averages from
OAM

traffic (
Queue
-
1
):

Latency: Highest _________ms

Meets Req
.

YES / NO

Jitter: Highest _________ms

Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.
:_________

Meets Req.

YES / NO


1
2c. Record performance data averages
from HTD traffic (
Queue
-
2
):

Latency: Highest _________ms

Meets Req.

YES / NO

Jitter: Highest _________ms

Meets Req.

YES / NO

Packet Loss:

H
ighest
--
5min avg.
:_________

Meets Req.

YES / NO


1
2d. Record performance data averages from
EF

traffic (
Queue
-
3
):

Latency: Highest _________ms

Meets Req.

YES / NO

Ji
tter: Highest _________ms

Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.
:_________

Meets Req.

YES / NO


1
2e. Record performance data averages from LLD traf
fic (
Queue
-
4
):

Latency: Highest _________ms


Meets Req.

YES / NO

Jitter: Highest _________ms

Meets Req.

YES / NO

Packet Loss:

Highest
--
5min
avg.
:_________


Meets Req.

YES / NO


1
2f. Record performance data averages from MM traffic (
Queue
-
5
):

Latency: Highest _________ms

Meets Req.

YES / NO

Jitter: Hi
ghest _________ms

Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.
:_________

Meets Req.

YES / NO


1
2g. Record performance data averages from
VIDEO

traffic (
Queue
-
6
):

Latency: Highest _________ms


Meets Req.

YES / NO

Jitter: Highest _________ms

Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.
:______
___

Meets Req.

YES / NO

MOS: Lowest
--
5min avg.: _________


Meets Req.

YES / NO


1
2h. Record performance data averages from
VOICE

traffic (
Queue
-
7
):

Latency: Highest _____
____ms

Meets Req.

YES / NO

Jitter: Highest _________ms

Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.
:_________


Meets Req.

YES / NO

MOS: Lowest
--
5min avg.: _________



Meets Req.

YES / NO

NOTES:








E
-
4



Table E
-
4
-
5. CER
Test Procedures


(3)
Performance Characteristics & Traffic Conditioning, DSCP 8
-
Queue PHB (Con
tinued
)

PROCEDURE:

RESULTS:

13.

Reduce DD load to 100% of Queue
-
0 bandwidth (12.5% of total IUT bandwidth). Increase
OAM load to 3X of Queue
-
1 bandwidth (37.5% of total IUT bandwidth). Maintain the all other
loads at 100% of their respective queues and

allow load to run for 1 hour.


Verify that the only packet loss occurs in Queue
-
1.
Additionally, traffic could be delayed in Queue
-
1 as a result of traffic conditioning

V
erify that

the performance measurements for the other
queues

do not exceed requi
rements for any given five minute period of time..


If OAM load is equal to 3X of Queue
-
1 bandwidth
, and the other loads are at 100% of the
bandwidth in their respective queues, then OAM

load (Q
ueue
-
1) packet loss should equal
approximately 66% of total lo
ad.

13
a. Record performance data averages from DD traffic (
Queue
-
0
):

Latency: Highest _________ms

Meets Req.

YES / NO

Jitter: Highest _________ms


Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.
:_________

Meets Req.

YES / NO


13
b. Record performance data averages from
OAM

traffic (
Queue
-
1
):

Latency: Highest _________ms


(possible degradation)

Jitter: Highest _________ms

Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.
:_________


(Approx. 66%

Loss)


13
c. Record performance data averages from HTD traffic (
Queue
-
2
):

Latency: Highest _________ms

Meets Req.

YES / NO

Jitter: Highest _________ms


Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.
:_________

Meets Req.

YES / NO


13
d. Record performance data averages from
EF

traffic (
Queue
-
3
):

Latency: Highest _________ms


Meets Req.

YES / NO

Jitter: Highest _________ms

Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.
:_________


Meets Req.

YES / NO


13
e.
Record performance data averages from LLD traffic (
Queue
-
4
):

Latency: Highest _________ms

Meets Req.

YES / NO

Jitter: Highest _________ms

M
eets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.
:_________

Meets Req.

YES / NO


13
f. Record performance data averages from MM traffic (
Queue
-
5
):

Latency: Highest _________ms


Meets Req.

YES / NO

Jitter: Highest _________ms

Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.
:_________

Meets Req.

YES / NO


13
g. Record perfor
mance data averages from
VIDEO

traffic (
Queue
-
6
):

Latency: Highest _________ms

Meets Req.

YES / NO

Jitter: Highest _________ms

Meets Req.

Y
ES / NO

Packet Loss:

Highest
--
5min avg.
:_________

Meets Req.

YES / NO

MOS: Lowest
--
5min avg.: _________

Meets Req.

YES / NO


13
h. Record performance data averages from
VOICE

traffic (
Queue
-
7
):

Latency: Highest _________ms

Meets Req.

YES / NO

Jitter: Highest _________ms

Meets Req.

YES / NO

Packet Loss:

Highest
--
5
min avg.
:_________


Meets Req.

YES / NO

MOS: Lowest
--
5min avg.: _________


Meets Req.

YES / NO

NOTES:








E
-
4



Table E
-
4
-
5. CER
Test Procedures


(3)
Performance Characteristic
s & Traffic Conditioning, DSCP 8
-
Queue PHB (Continued
)

PROCEDURE:

RESULTS:

14.

Reduce OAM load to 100% of Queue
-
1 bandwidth (12.5% of total IUT bandwidth). Increase
HTD load to 3X of Queue
-
2 bandwidth (37.5% of total IUT bandwidth). Maintain the all ot
her loads
at 100% of their respective queues and allow load to run for 1 hour. Verify that the only packet
loss occurs in Queue
-
2.
Additionally, traffic could be delayed in Queue
-
2 as a result of traffic
conditioning

V
erify that

the performance measure
ments for the other queues

do not exceed
requirements for any given five minute period of time..


If HTD load is equal to 3X of Queue
-
2 bandwidth
, and the other loads are at 100% of the
bandwidth in their respective queues, then HTD

load (Q
ueue
-
2) packet l
oss should equal
approximately 66% of total load.

14
a. Record performance data averages from DD traffic (
Queue
-
0
):

Latency: Highest _________ms

Meets Req.

YES / NO

Jitter: Highest _________ms


Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.
:_________

Meets Req.

YES / NO


14
b. Record performance data averages from
OAM

traffic (
Queue
-
1
):

Latency: Highe
st _________ms

Meets Req.

YES / NO

Jitter: Highest _________ms

Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.
:_________



Meets Req.

YES / NO


14
c. Record performance data averages from HTD traffic (
Queue
-
2
):

Latency: Highest _________ms

(possible degradation)

Jitter: Highest _________ms


Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.
:_________


(Approx. 66%

Loss)


14
d. Record performance data averages from
EF

traffic (
Queue
-
3
):

Latency: H
ighest _________ms

Meets Req.

YES / NO

Jitter: Highest _________ms

Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.
:_________


Meets Req.

YES / NO


14
e. Record performance data averages from LLD traffic (
Queue
-
4
):

Latency: Highest _________ms

Meets Req.

YES / NO

Jitter: Highest _________ms


Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.
:_________

Meets Req.

YES / NO


14
f. Record performance data averages from MM traffic (
Queue
-
5
):

Latency: Highest ______
___ms

Meets Req.

YES / NO

Jitter: Highest _________ms

Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.
:_________


Meets Req.

YES / NO


14
g. Record performance data averages from
VIDEO

traffic (
Queue
-
6
):

Latency: Highest _________ms

Meets Req.

YES / NO

Jitter: Highest _________ms


Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.
:_________

Meets Req.

YES / NO

MOS: Lowest
--
5min avg.: _________

Meets Req.

YES / NO


14
h
. Record performance data averages from
VOICE

traffic (
Queue
-
7
):

Latency: Highest _________ms

Meets Req.

YES / NO

Jitter: Highest _________ms


Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.
:_________

Meets Req.

YES / NO

MOS: Lowest
--
5min avg.: _________

Meets Req.

YES / NO

NOTES:








E
-
4



Table E
-
4
-
5. CER
Te
st Procedures


(3)
Performance Characteristics & Traffic Conditioning, DSCP 8
-
Queue PHB (Continued
)

PROCEDURE:

RESULTS:

15.

Reduce HTD load to 100% of Queue
-
2 bandwidth (12.5% of total IUT bandwidth). Increase
EF load to 3X of Queue
-
3 bandwidth (37.5% o
f total IUT bandwidth). Maintain the all other loads
at 100% of their respective queues and allow load to run for 1 hour. Verify that the only packet
loss occurs in Queue
-
3.
Additionally, traffic could be delayed in Queue
-
3 as a result of traffic
condit
ioning

V
erify that

the performance measurements for the other queues

do not exceed
requirements for any given five minute period of time..


If EF load is equal to 3X of Queue
-
3 bandwidth
, and the other loads are at 100% of the bandwidth
in their respecti
ve queues, then EF
load (Q
ueue
-
3) packet loss should equal
approximately 66% of
total load.

15
a. Record performance data averages from DD traffic (
Queue
-
0
):

Latency: Highest _________ms

Meets Req.

YES

/ NO

Jitter: Highest _________ms

Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.
:_________


Meets Req.

YES / NO


15
b. Record performance data averages from
OAM

traffic (
Queue
-
1
):

Latency: Highest _________ms

Meets Req.

YES / NO

Jitter: Highest _________ms

Meets Req.

YES / NO

Packet Loss:

Highes
t
--
5min avg.
:_________


Meets Req.

YES / NO


15
c. Record performance data averages from HTD traffic (
Queue
-
2
):

Latency: Highest _________ms

Meets Req.

YES / NO

Jitter
: Highest _________ms

Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.
:_________


Meets Req.

YES / NO


15
d. Record performance data averages from
EF

traffic (
Queue
-
3
):

Latency: Highest _________ms

(possible degradation)

Jitter: Highest _________ms

Meets Req.

YES / NO

Packet Loss:

Highest
--
5m
in avg.
:_________


(Approx. 66% Loss)


15
e. Record performance data averages from LLD traffic (
Queue
-
4
):

Latency: Highest _________ms

Meets Req.

YES / NO

Ji
tter: Highest _________ms

Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.
:_________


Meets Req.

YES / NO


15
f. Record performance data averages from MM traff
ic (
Queue
-
5
):

Latency: Highest _________ms

Meets Req.

YES / NO

Jitter: Highest _________ms

Meets Req.

YES / NO

Packet Loss:

Highest
--
5min a
vg.
:_________


Meets Req.

YES / NO


15
g. Record performance data averages from
VIDEO

traffic (
Queue
-
6
):

Latency: Highest _________ms

Meets Req.

YES / NO

Jitter:
Highest _________ms

Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.
:_________


Meets Req.

YES / NO

MOS: Lowest
--
5min avg.: _________

Meets Req.

YES / NO


15
h. Record performance data averages from
VOICE

traffic (
Queue
-
7
):

Latency: Highest _________ms

Meets Req.

YES / NO

Jitter: Highest _________ms


Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.
:_________


Meets Req.

YES / NO

MOS: Lowest
--
5min avg.: _________

Meets Req.

YE
S / NO

NOTES:









E
-
4



Table E
-
4
-
5. CER
Test Procedures


(3)
Performance Characteristics & Traffic Conditioning, DSCP 8
-
Queue PHB (Continued
)

PROCEDURE:

RESULTS:

16.

Reduce EF load to 100% of Queue
-
3 bandwidth (12.5% of total IUT bandwidth). Increase L
LD
load to 3X of Queue
-
4 bandwidth (37.5% of total IUT bandwidth). Maintain the all other loads at
100% of their respective queues and allow load to run for 1 hour. Verify that the only packet loss
occurs in Queue
-
4.
Additionally, traffic could be delay
ed in Queue
-
4 as a result of traffic
conditioning

V
erify that

the performance measurements for the other queues

do not exceed
requirements for any given five minute period of time..


If LLD load is equal to 3X of Queue
-
4 bandwidth
, and the other loads ar
e at 100% of the
bandwidth in their respective queues, then LLD
load (Q
ueue
-
4) packet loss should equal
approximately 66% of total load.

16
a. Record performance data averages from DD traffic (
Queue
-
0
):

Latency: Highest _________ms


Meets Req.

YES / NO

Jitter: Highest _________ms

Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.
:_________


Meets Req.

YES / NO


16
b. Record performance data averages from
OAM

traffic (
Queue
-
1
):

Latency: Highest _________ms

Meets Req.

YES / NO

Jitter: Highest _________ms


Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.
:_________


Meets Req.

YES / NO


16
c. Record performance data averages from HTD traffic (
Queue
-
2
):

Latency: Highest _________ms


Meets Req.

YES / NO

Jitter: Highest _________ms

Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.
:_________


Meets Req.

YES / NO


16
d. Recor
d performance data averages from
EF

traffic (
Queue
-
3
):

Latency: Highest _________ms

Meets Req.

YES / NO

Jitter: Highest _________ms

Meets R
eq.

YES / NO

Packet Loss:

Highest
--
5min avg.
:_________


Meets Req.

YES / NO


16
e. Record performance data averages from LLD traffic (
Queue
-
4
):

Latency: Highest _________ms


(possible degradation)

Jitter: Highest _________ms

Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.
:_________


(Approx. 66% Loss)


16
f. R
ecord performance data averages from MM traffic (
Queue
-
5
):

Latency: Highest _________ms

Meets Req.

YES / NO

Jitter: Highest _________ms

Mee
ts Req.

YES / NO

Packet Loss:

Highest
--
5min avg.
:_________


Meets Req.

YES / NO


16
g. Record performance data averages from
VIDEO

traffic (
Queue
-
6
):

Latency: Highest _________ms


Meets Req.

YES / NO

Jitter: Highest _________ms

Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.
:_________


Meets Req.

YES / NO

MOS:
Lowest
--
5min avg.: _________

Meets Req.

YES / NO


16
h. Record performance data averages from
VOICE

traffic (
Queue
-
7
):

Latency: Highest _________ms

Meets Req.

YES / N
O

Jitter: Highest _________ms

Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.
:_________


Meets Req.

YES / NO

MOS: Lowest
--
5min avg.: _________


Meets Req.

YES / NO

NOTES:








E
-
4



Table E
-
4
-
5. CER
Test Procedures


(3)
Performance Characteristics & Traffic Conditioning, DSCP 8
-
Queue PHB (Continued
)

PROCEDURE:

RESULTS:

17.

Reduce LLD load to 100% of Queue
-
4 bandwid
th (12.5% of total IUT bandwidth). Increase
MM load to 3X of Queue
-
5 bandwidth (37.5% of total IUT bandwidth). Maintain the all other loads
at 100% of their respective queues and allow load to run for 1 hour. Verify that the only packet
loss occurs in Q
ueue
-
5.
Additionally, traffic could be delayed in Queue
-
5 as a result of traffic
conditioning

V
erify that

the performance measurements for the other queues

do not exceed
requirements for any given five minute period of time..


If MM load is equal to 3X
of Queue
-
5 bandwidth
, and the other loads are at 100% of the bandwidth
in their respective queues, then MM
load (Q
ueue
-
5) packet loss should equal
approximately 66%
of total load.

17
a. Record performance data averages from DD traffic (
Queue
-
0
):

Latency:

Highest _________ms

Meets Req.

YES / NO

Jitter: Highest _________ms

Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.
:_________


Meets Req.

YES / NO


17
b. Record performance data averages from
OAM

traffic (
Queue
-
1
):

Latency: Highest _________ms

Meets Req.

YES / NO

Jitter: Highest _________ms


Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.
:_________


Meets Req.

YES / NO


17
c. Record performance data averages from HTD traffic (
Queue
-
2
):

Latency: Highest _
________ms

Meets Req.

YES / NO

Jitter: Highest _________ms

Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.
:_________



Meets Req.

YES / NO


17
d. Record performance data averages from
EF

traffic (
Queue
-
3
):

Latency: Highest _________ms

Meets Req.

YES / NO

Jitter: Highest _________ms


Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.
:_________


Meets Req.

YES / NO


17
e. Record performance data averages from LLD traffic (
Queue
-
4
):

Latency: Highest _________ms


Meets Req.

YES / NO

Jitter: Highest _________ms

Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.
:_________


M
eets Req.

YES / NO


17
f. Record performance data averages from MM traffic (
Queue
-
5
):

Latency: Highest _________ms

(possible degradation)

Jitter: Highest _________ms


Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.
:_________


(Approx. 66% Loss)


17
g. Record performance data averages from
VIDEO

traffic (
Queue
-
6
):

Latency: Highest ________
_ms

Meets Req.

YES / NO

Jitter: Highest _________ms

Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.
:_________



Meets Req.

YES / NO

MOS: Lowest
--
5min avg.: _________

Meets Req.

YES / NO


17
h. Record performance data averages from
VOICE

traffic (
Queue
-
7
):

Latency: Highest _________ms


Meets Req.

YES / NO

Jitter: Highest _________ms

Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.
:_________


Meets Req.

YES / NO

MOS:

Lowest
--
5min avg.: _________

Meets Req.

YES / NO

NOTES:









E
-
4



Table E
-
4
-
5. CER
Test Procedures


(3)
Performance Characteristics & Traffic Conditioning, DSCP 8
-
Queue PHB (Continued
)

PROCEDURE:

RESULTS:

18.

Reduce MM load to 100% of Queue
-
5 bandwidth (12.5% of total IUT bandwidth). Increase
VIDEO

load to 3X of Queue
-
6 bandwidth (37.5% of total IUT bandwidth). Maintain the all other
loads at 100% of their respective queues and allow load to run for 1 hour.

Verify that the only
packet loss occurs in Queue
-
6.
Additionally, traffic could be delayed and MOS results effected in
Queue
-
6 as a result of traffic conditioning

V
erify that

the performance measurements for the
other queues

do not exceed requirements
for any given five minute period of time..


If
VIDEO

load is equal to 3X of Queue
-
6 bandwidth
, and the other loads are at 100% of the
bandwidth in their respective queues, then Video
load (Q
ueue
-
6) packet loss should equal
approximately 66% of total load.

18
a. Record performance data averages from DD traffic (
Queue
-
0
):

Latency: Highest _________ms

Meets Req.

YES / NO

Jitter: Highest _________ms


Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.
:_________


Meets Req.

YES / NO


18
b. Record performance data averages from
OAM

traffic (
Queue
-
1
):

Latency: Highest _________ms


Meets Req.

YES / NO

Jitter: Highest _________ms

Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.
:_________


Meets Req.

YES / NO


18
c. Record p
erformance data averages from HTD traffic (
Queue
-
2
):

Latency: Highest _________ms

Meets Req.

YES / NO

Jitter: Highest _________ms

Meets Req
.

YES / NO

Packet Loss:

Highest
--
5min avg.
:_________

Meets Req.

YES / NO


18
d. Record performance data averages from
EF

traffic (
Queue
-
3
):

Latency: Highest _________ms

Meets Req.

YES / NO

Jitter: Highest _________ms

Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.
:_________

Meets Req.

YES / NO


18
e. Record performance d
ata averages from LLD traffic (
Queue
-
4
):

Latency: Highest _________ms
Meets Req.

YES / NO

Jitter: Highest _________ms

Meets Req.

YES / NO

P
acket Loss:

Highest
--
5min avg.
:_________


Meets Req.

YES / NO


18
f. Record performance data averages from MM traffic (
Queue
-
5
):

Latency: Highest _________ms


Meets Re
q.

YES / NO

Jitter: Highest _________ms

Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.
:_________

Meets Req.

YES / NO


18
g. Record performance data averages

from
VIDEO

traffic (
Queue
-
6
):

Latency: Highest _________ms

(possible degradation)

Jitter: Highest _________ms

Meets Req.

YES / NO

Pac
ket Loss:

Highest
--
5min avg.
:_________


(Approx. 66% Loss)

MOS: Lowest
--
5min avg.: _________


(possible
degradation)


18
h. Record performance data averages f
rom
VOICE

traffic (
Queue
-
7
):

Latency: Highest _________ms

Meets Req.

YES / NO

Jitter: Highest _________ms

Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.
:_________

Meets Req.

YES / NO

MOS: Lowest
--
5min avg.: _________

Meets Req.

YES / NO

NOTES:









E
-
4



Table E
-
4
-
5. CER
Test Procedures


(3)
Performance Char
acteristics & Traffic Conditioning, DSCP 8
-
Queue PHB (Continued
)

PROCEDURE:

RESULTS:

19.

Reduce VIDEO load to 100% of Queue
-
6 bandwidth (12.5% of total IUT bandwidth). Increase
VOICE load to 3X of Queue
-
7 bandwidth (37.5% of total IUT bandwidth). Maint
ain the all other
loads at 100% of their respective queues and allow load to run for 1 hour. Verify that the only
packet loss occurs in Queue
-
7.
Additionally, traffic could be delayed and MOS results effected in
Queue
-
7 as a result of traffic conditionin
g

V
erify that

the performance measurements for the
other queues

do not exceed requirements for any given five minute period of time..


If VOICE load is equal to 3X of Queue
-
7 bandwidth
, and the other loads are at 100% of the
bandwidth in their respective

queues, then Video
load (Q
ueue
-
7) packet loss should equal
approximately 66% of total load.

19
a. Record performance data averages from DD traffic (
Queue
-
0
):

Latency: Highest _________ms



Meets Req.

YE
S / NO

Jitter: Highest _________ms

Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.
:_________



Meets Req.

YES / NO


19
b. Record performance data averages from

OAM

traffic (
Queue
-
1
):

Latency: Highest ___
______ms


Meets Req.

YES / NO

Jitter: Highest _________ms

Meets Req.

YES / NO

Packet Loss:

Highe
st
--
5min avg.
:_________



Meets Req.

YES / NO


19
c. Record performance data averages from HTD traffic (
Queue
-
2
):

Latency: Highest _________ms



Meets Req.

YES / NO

Jitte
r: Highest _________ms

Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.
:_________



Meets Req.

YES / NO


19
d. Record performance data averages from
EF

traffic
(
Queue
-
3
):

Latency: Highest _________ms



Meets Req.

YES / NO

Jitter: Highest _________ms

Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.
:_________



Meets Req.

YES / NO

19
e. Record performance data averages from LLD traffic (
Queue
-
4
):

Latency: Highest _________ms



Meets Req.

YES / NO

Jitter: Highes
t _________ms

Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.
:_________




Meets Req.

YES / NO


19
f. Record performance data averages from MM traffic (
Queue
-
5
):

Lat
ency: Highest _________ms

Meets Req.

YES / NO

Jitter: Highest _________ms

Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.
:_________



Meets Req.

YES / NO


19
g. Record performance data averages from
VIDEO

traffic (
Queue
-
6
):

Latency: Highest _________ms

Meets Req.

YES / NO

Jitter: Highest _________
ms

Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.
:_________


Meets Req.

YES / NO

MOS: Lowest
--
5min avg.: _________


Meets Req.

YES / NO


19
h. Record performance data averages from
VOICE

traffic (
Queue
-
7
):

Latency: Highest _________ms

(possible degradation)

Jitter: Highest _________ms


Meets Req.

YES / NO

Packet Loss:

Highest
--
5min avg.
:_________


(Approx. 66% Loss)

MOS: Lowest
--
5min avg.: _________



(poss
ible degradation)

NOTES:









E
-
4




Table E
-
4
-
5. CER
Test Procedures

(continued)

(4) Network Management

REFERENCE:


UCR 2008, Sect. 5.3.2.14.6 (Net Mgmt); 5.3.2.17 (Mgmt of Net Apps); Figure
5.3.2.17
-
1 (Net App Mgmt Model); 5.3.2.18.1 (MIBs, TRAPs); 5
.3.2.17.3.1 (Fault Management)

REQUIREMENT
: (Required)

TEST SETUP:


Connect to the CER using a Management Console or Network Management system.


1. Using NM port (IP (R)) or serial (C)) login to the CER.

2. Enable SNMP
v
2
or SNMPv3
.



DIAGRAM
:

PROC
EDURE:

RESULTS:

1.

Verify that the SUT can support the simultaneous access and function of a remote Network
Management system and a local Management Console.

2.

Verify that the CER QOS queues are readable and settable by the RTS EMS.

3.

Verify that non
standard (vendor
-
specific) CM and PM information is presented as private
vendor MIBs, as defined by the applicable RFCs.

4.

Fault. From the mgmt console or NM system, perform the following functions:

4a.

display system info using show commands

4b.

test

network connectivity

4c.

determine memory and interface status

4d.

log system error messages

4e.

enable debug operations

4f.

Verify that fault management alarms are distinguishable from administrative log messages.

4g.

The CER detects its own fault condi
tions and generates alarm notifications within 5 sec.

4h.

Send SNMP (v2) alarms to NM system


4i.

Send SNMP (v3) alarms to NM system

5. Configuration.

5a. verify and determine OS versions.

5b. save running config file.

5c. load config from previously

saved version.

5d. from the NM system, send the CER remote commands.

6. Accounting: Track network usage by interface.

7. Performance.

7a. measure network effectiveness of interface/link by frame, packets delivered.

7b. monitor behavior of protocol
(TCP versus UDP)

7c. verify throughput, response time and line utilization statistics.



8. Security (see IATP)

1.

Simultaneous operation permitted

YES / NO


2.

The CER QOS queues are readable and settable by the RTS EMS.

YES / NO

3.

Verify that nonsta
ndard (vendor
-
specific) CM and PM information is presented as


private vendor MIBs, as defined by the applicable RFCs.

YES / NO

4.

Fault. CER supports:

4a.

show commands

YES / NO

4b.

network traceability

YES / NO

4c.

interface status

YES / NO

4d.

error
logs

YES / NO

4e.

debug

YES / NO

4f.

A
larms are distinguishable from administrative log messages

YES / NO

4g.

Alarm detection and notification occur within 5 sec.

YES / NO

4h.

SNMP (v2) alarm format supported

YES / NO

4i.

SNMP (v3) alarm format supporte
d

YES / NO

5.

Configuration. CER supports:

5a.

OS info verification

YES / NO

5b.

config file saving

YES / NO

5c.

manual config loading

YES / NO

5d.

remote commands

YES / NO

6.

Accounting. CER supports bandwidth utilization statistics

YES / NO

7.

Perform
ance. CER supports:

7a.

network performance statistics.

YES / NO

7b.

protocol monitoring

YES / NO

7c.

throughput statistics

YES / NO


response time statistics

YES / NO


Line/interface utilization statistics

YES / NO

8.

IA Test plan for CER was conducte
d to assure IA compliance

YES / NO

9. Using a Management Information Base (MIB) Browser verify the following MIBs are available

Iso. > org. > dod. > internet. > mgmt. > mib
-
2.


(rmon; system; interfaces; at; ip;
icmp; tcp; udp; egp; transmission;
snmp)


9. Following MIBs are available:

MIB

INCL?

MIB

INCL?


MIB

INCL?

rmon

YES/NO

system

YES/NO

interfaces

YES/NO

at

YES/NO

ip

YES/NO

icmp

YES/NO

tcp

YES/NO

udp

YES/NO

egp

YES/NO

transmission

YES/NO

snmp

YES/NO










NOTES:



Local
Console

(Serial)

CER

(SUT)

Remote

Console

(IP)



E
-
4



Table E
-
4
-
5. CER

Test Procedures

(continued)

(4) Network Management

(Continued
)

PROCEDURE:

RESULTS:

10. Verify the CER includes the standard CM MIB variables.






10. Following CM MIBs are available:

CM MIB

INCL?

CM MIB

INCL?

CM MIB

INCL?

sysDescr

YES/NO

sysLocation

Y
ES/NO

sysName

YES/NO

sysContact

YES/NO

ifDescr

YES/NO

ifIndex

YES/NO

ifSpeed

YES/NO

ifType

YES/NO

ifPhysAddress

YES/NO

ifAdminStatus

YES/NO

sysUpTime

YES/NO

ifOperStatus

YES/NO


11. Verify the CER includes the standard PM MIB variables.


11. Following

PM MIBs are available:




PM MIB

INCL?

PM MIB

INCL?

PM MIB

INCL?

ifInErrors

YES/NO

ifLastChange

YES/NO

ipInDiscards

YES/NO

ifMtu

YES/NO

ifInNUcastPkts

YES/NO

ipInReceives

YES/NO

ifInUcastPkts

YES/NO

ifInUnknownProtos

YES/NO

ipOutDiscards

YES/NO

ifOutDi
scards

YES/NO

ifOutErrors

YES/NO

ipOutRequests

YES/NO

ifOutNUcastPkts

YES/NO

ifOutUcastPkts

YES/NO

ipInHdrErrors

YES/NO

ipForwarding

YES/NO

ipForwDatagrams

YES/NO

ipInDelivers

YES/NO

ipInAddrErrors

YES/NO

ipInUndnownProtos

YES/NO

ipOutNoRoutes

YES/NO

12. Verify that the CER includes the required standard TRAP’s

12. TRAP’s Verified:

TRAP NAME

ENTERPRISE ID

INCL?

ColdStart

1.3.6.6.3.1.1.5.1

YES / NO

WarmStart

1.3.6.6.3.1.1.5.2

YES / NO

LinkDown

1.3.6.6.3.1.1.5.3

YES / NO

LinkUp

1.3.6.6.3.1.1.5.4

YES

/ NO

Authentication Failure

1.3.6.6.3.1.1.5.5

YES / NO


NOTES:










E
-
4



Table E
-
4
-
5. CER
Test Procedures

(continued)

(5) System Quality Factors
-

Reliability / Failover

REFERENCE:


UCR 2008, Sect. 5.3.2.14.7

(Availability)
, 5.3.2.5.2

(SQF)



REQ
UIREMENT
: (Required)

TEST SETUP:



TEST CASE 1:
Single Chassis Reliability
.

Configure CER in configuration specified in Figure E
-
4
-
4 for Ethernet interfaces.

Configure CER in configuration specified in Figure E
-
4
-
5 for TDM and Serial interfaces.


TEST
CASE 2:
Duplicate System Reliability
.

Configure CER in configuration specified in Figure E
-
4
-
6 for Ethernet interfaces.

Configure CER in configuration specified in Figure E
-
4
-
7 for TDM and Serial interfaces.


Test Configuration:

1. Configure the CER per
the test configuration specified above as associated with the method of
reliability and interface type. Conduct the procedure for the TEST CASE supported by SUT. All
routers used in test setup must be APL certified products running a current APL certifie
d software
version.

2. Configure the LAN side Ethernet link pair to a router using OSPF.

3. Configure the WAN side interfaces to Aggregation Routers using BGP.

4.
Using TMDE

and two APL certified routers with redundant interfaces
, set up a
bi
-
directional
d
ual
stack (IPv4/IPv6)
VoIP media stream from
ingress to egress of the CER through each of the WAN
interfaces. (dual routing)

CRITERIA
:



TEST CASE 1:
Single Chassis Reliability
.
The SUT employs a
single
modular chassis to meet the
reliability requirement
. The SUT will have built back up capability e.g., processors, power
supplies, etc.)
.


TEST CASE 2:
Duplicate System Reliability
.
The SUT employs a duplicate system to meet the
requirement. The duplicate system may be in hot standby mode or active mod
e. The system,
primary and secondary, must be sized to meet the engineered traffic load. The secondary system
must be capable of taking over the functions of the primary system when the primary fails. Failure
of the primary and resulting takeover of the
secondary must not result in any loss of service.



SCOPE:

This procedure must be conducted for every interface type supported by CER
.

PROCEDURE:

RESULTS:

TEST CASE 1:

1. Break one of the WAN links in each of the OSPF link pairs.

2.
Verify that a
ll call sessions remain active.

3. Measure time for media path rerouting; verify reroute < 5

sec.

4.
Reconnect OSPF link.

5
. Break one of the WAN links in each of the
BGP

link pairs.

6
.
Verify that all call sessions remain active.

7
. Measure time for
media path rerouting; verify reroute < 5

sec.

8
.
Reconnect BGP link.

9
. Repeat for all
devices (SPFs, GBIC, cards, etc) and interface types supported by SUT
.

10
. Fail Processor on all devices supporting dual processors through software and verify media
s
tream remains active with no errors.

11.
. Pull a Processor on all devices supporting dual processors and verify media stream remains
active with no errors.

12
. Replace processor.

13
. Pull second processor; verify media stream remain active and no errors
recorded.

14
. Verify power supply failover capability. Pull one of the Power supplies and verify no disruption
of service.

15
. Replace power supply.

16
. Pull second power supply and verify no disruption of service.

TEST CASE 1:

For Test Procedures 1
-
1
6

verify that media stream remains active, that there is no disruption of
service and reroute
< 5

sec
.
Record results in table below.

If failover process is greater than 5
sec, then document it as a failure
.


Device

/ Interface Type

Time Measured for Rerout
e After Failover

OSPF
LPs

BGP LPs

Processor

Power















































NOTES:








E
-
4



Table E
-
4
-
5. CER
Test Procedures

(continued)

(5) System Quality Factors
-

Reliability / Failover

(Continued
)

PROCEDURE:

RESULTS:

TEST CASE 2
:

1. Break one of the WAN links in each of the OSPF link pairs.

2.
Verify that all call sessions remain active.

3. Measure time for media path rerouting; verify reroute < 5

sec.

4.
Reconnect OSPF link.

5
. Break one of the WAN links in eac
h of the
BGP

link pairs.

6
.
Verify that all call sessions remain active.

7
. Measure time for media path rerouting; verify reroute < 5

sec.

8
.
Reconnect BGP link.

9
. Repeat for all
devices (SPFs, GBIC, cards, etc) and interface types supported by SUT
.

1
0. With the primary active and secondary in standby, turn off the primary.

11. Verify that all call sessions are active.

12. Turn on the primary CER.

13. Turn off secondary CER.

14. Verify that primary is active and controlling sessions.

15. Verify n
o lost call sessions.


TEST CASE 2:

For Test Procedures 1
-
15,
verify that media stream remains active, that there is no disruption of
service and reroute
< 5

sec
.
Record results in table below
.
If failover process is greater than 5
sec, then document i
t as a failure
.


Device

/ Interface Type

Time Measured for Reroute After Failover

OSPF
LPs

BGP LPs

Processor

Power
















































NOTES:























E
-
4



Table E
-
4
-
5. CER
Test Procedures

(continued)

(6) S
ystem Quality Factors
-

Configuration Changes

REFERENCE:


UCR 2008, Sect. 5.3.2.14.7

(Availability)
, 5.3.2.5.2

(SQF)



REQUIREMENT
: (Required)

TEST SETUP:



TEST CASE 1:
Single Chassis Reliability
.

Configure CER in configuration specified in Figur
e E
-
4
-
4 for Ethernet interfaces.

Configure CER in configuration specified in Figure E
-
4
-
5 for TDM and Serial interfaces.


TEST CASE 2:
Duplicate System Reliability
.

Configure CER in configuration specified in Figure E
-
4
-
6 for Ethernet interfaces.

Configu
re CER in configuration specified in Figure E
-
4
-
7 for TDM and Serial interfaces.


Test Configuration:

1. Configure the CER per the test configuration specified above as associated with the method of
reliability and interface type. Conduct the procedure fo
r the TEST CASE supported by SUT. All
routers used in test setup must be APL certified products running a current APL certified software
version.

2. Configure the LAN side Ethernet link pair to a router using OSPF.

3. Configure the WAN side interfaces to
Aggregation Routers using BGP.

4.
Using TMDE

and two APL certified routers with redundant interfaces
, set up a
bi
-
directional
dual
stack (IPv4/IPv6)
VoIP media stream from
ingress to egress of the CER through each of the WAN
interfaces. (dual routing)

5. C
onfigure 4
-
queue NLB as specified in procedure IO
-
2.

CRITERIA
:

The SUT must be capable of implementing software configuration changes or patch upgrades
without loss of service. There are two possible implementation configuration scenarios, modular
or red
undant system, that may be implemented to meet the requirement.


TEST CASE 1:
Single Chassis Reliability
.
The SUT employs a
single
modular chassis to meet the
reliability requirement. The SUT will have built back up capability e.g., processors, power
sup
plies, etc.)
.


TEST CASE 2:
Duplicate System Reliability
.
The SUT employs a duplicate system to meet the
requirement. The duplicate system may be in hot standby mode or active mode. The system,
primary and secondary, must be sized to meet the engineer
ed traffic load. The secondary system
must be capable of taking over the functions of the primary system when the primary fails. Failure
of the primary and resulting takeover of the secondary must not result in any loss of service.


SCOPE:

This proced
ure must be conducted for every interface type supported by CER
.

PROCEDURE:

RESULTS:

TEST CASE 1
:

1. Run 4
-
queue NLB for 30 minutes and verify that results are within expected requirements.

2. While the system is operational, make configuration changes

to the primary processing core.
Change BW allocation to the 4 queues from 25% each to: 40% EF, 30% to AF41/AF42 queue,
20% to AF31/AF32 queue, and 10% to Best effort.

3. Implement updated changes to the CER without ‘reboot’ or loss of service.

4. Re
-
r
un test procedure 1 to verify configuration updates.

5. While the CER is operational, apply an update patch to the system without reboot or loss of
service.


TEST CASE 1
:

1. 4
-
queue NLB configured properly and runs without errors.

YES / NO

2.

Config cha
nged to 4 queues with 40%, 30%, 20% and 10%.

YES / NO



3.

Changes updates without reboot or loss of service.

YES / NO

4. Queuing functional as re
-
configured..

YES / NO

5. Patch applied without reboot or loss of service.

YES / NO


TEST CASE 2
:

1. Ru
n 4
-
queue NLB configuration for 30 minutes and verify that results are within requirements.

2. While the system is operational, make configuration changes to the primary CER. Change BW
allocation to the 4 queues from 25% each to: 40% EF, 30% to AF41/AF42

queue, 20% to
AF31/AF32 queue, and 10% to Best effort.

3. Implement updated changes to the CER with ‘reboot’.

4. Ensure secondary system takes over operation without or loss of service.

5. Re
-
run test procedure 1 to verify configuration updates.

6. A
pply an update patch to the secondary CER (now acting as primary).

7. Reboot the secondary CER (now acting as primary).

8. Ensure primary CER takes over control without loss of service.

TEST CASE 2
:

1. 4
-
queue NLB configured properly and runs without er
rors.

YES / NO

2.

Config changed to 4 queues with 40%, 30%, 20% and 10%.

YES / NO



3.

Changes updates with reboot or loss of service.

YES / NO

4. Secondary CER takes over without loss of service.

YES / NO

5. Queuing functional as re
-
configured..

YES

/ NO

6. Patch applied.

YES / NO

7. Reboot successful.

YES / NO

8. Primary CER functioning; no loss of service.

YES / NO

NOTES:








E
-
4





Table E
-
4
-
6. CER Requirements Summary


Specifications

Features

References

Required (R)

Conditional (C)

Physical

Ports

Serial Port

EIA/TIA

R

10BaseT UTP

IEEE 802.3i

C

100BaseT UTP

IEEE 802.3u

R

1000BASE
-
T UTP

IEEE 802.3ab

C

1000BASE
-
X Fiber

IEEE 802.3z

R

10GBase

IEEE 802.3ae

C

Port Parameters

Auto
-
negotiation

IEEE 802.3

R

Force mode

IEEE 802.3

R

Flow Control

IEEE 802.3x

R

Filtering

RFC 1812

R

Link Aggregation

802.3ad

R

Spanning Tree Protocol

IEEE 802.1D

R

Multiple Spanning Tree Protocol

IEEE 802.1s

R

Rapid Reconfiguration of Spanning Tree

802.1w

R

Port Based Access Control on line sig
n

IEEE 802.1x

R

CoS Parameters

Traffic classes

IEEE 802.1D/Q

R

DSCP

RFC 2474

(see Note 1)

R


VLANs

Port based

IEEE 802.1Q

R

MAC based

Protocol based

IPv4

Protocols



Internet Protocol, Version 4 (IPv4)

RFC 791

R

ARP Table

RFC 903

R

ICMP

R
FC 950

R

FTP

RFC 959

R

RIPv1, RIPv2 (IP/IPX)

RFC

1058

C

DVMRP V3 (Distance Vectoring)

RFC 1075

C

Multicast Forwarding

RFC 1112

C

IS
-
IS

RFC 1195

R

NSLP (IPX)

RFC 1234

C

ICMP (PING)

RFCs 1256

R

NTP


RFC 1305

R

PPP

RFC 1332

R

CIDR MIB (In
ter
-
Domain Routing)

RFC 1519

C

PPP Extensions

RFC 1570

R

RIP MIB (Routing Management Info)

RFC 1724

C

URLs

RFC 1738

R

Border Gateway Protocol (BGP 4)

RFC 1771

R

BGP

RFC 1772

R

IP

RFC 1812

R

OSPF

RFC 1850

R

PPP Link Quality

RFC 1989

R

PPP
Multi
-
Link

RFC 1990

R

PPP Handshake

RFC 1994

R

BGP Communities

RFC 1997

R



E
-
4




Table E
-
4
-
6. CER Requirements Summary

Specifications

Features

References

Required (R)

Conditional (C)

IPv4

Protocols

(continued)

SNMPv2

RFC 2011

C

ISO Transport

RFC 2126

R

DHCP

RFC 2131

R

DHCP and BOOTP

RFC 2132

R

RSVP

RFC 2205

C

RSVP extensions

RFC 2207

C

RSVP with IntServ

RFC 2210

C

IntServ

RFC 2215

C

OSPF v2

RFC 2328

C

VRRP

RFC 2338

R

BGP Route Flap

RFC 2439

R

DiffServ

RFCS 2474
and

2475

R

TCP cong
estion control

RFC 2581

R

Traffic using MPLS

RFC 2702

R

Multi
-
protocol Extensions for BGP 4

RFC 2858

C

Route refresh

RFC 2918

R

Policy Core Information

RFC 3060

R

Carrying label info

RFC 3107

R

ECN

RFC 3168

R

Bridging Control Protocol

IEEE 80
2.1D/Q;

RFC 3518

C

Expedited PHB

RFC 3246

R

BGP

RFC 4271

R

MTU for IPv6

RFC 1981

R

IPv6

Protocols

FTP Extensions

RFC 2428

R

Internet Protocol, Version 6 (IPv6)

RFC 2460

R

Neighbor Discovery

RFC 2461

R

IPv6 stateless addresses

RFC 2462

R

Tra
nsmission of IPv6

RFC 2464

R

MIBs

RFC 2465

R

MIBs

RFC 2466

R

PPP for IPv6

RFC 2472

R

Generic packet tunneling

RFC 2473

R

DiffServ

RFC 2474

R

IPv6 over ATM

RFC 2492

R

BGP for IPv6

RFC 2545

R

MLD for IPv6

RFC 2710

R

OSPF for IPv6

RFC 2740

R

Routing

RFC 2784

R

Multi
-
protocol extensions

RFC 2858

R

MPLS VPN

RFC 2917

R

IPv6 Tunnel Broker

RFC 3053

C

RADIUS

RFC 3162

R

ECN for IPv4 and IPv6

RFC 3168

C



E
-
4




Table E
-
4
-
6. CER Requirements Summary


Specifications

Features

References

Required

(R)

Conditional (C)

IPv6

Protocols

(continued)

DHCP for IPv6

RFC 3315

C

Textual conventions for flow label

RFC 3595

C

Mobility support in IPv6

RFC 3775

R

IPSec to protect mobile IPv6 signaling

RFC 3776

R

Default address

RFC 3484

R

MldV2 for IPv
6

RFC 3810

R

NEMO basic support

RFC 3963

R

URI generic syntax

RFC 3986

C

IPv6 scoped address

RFC 4007

R

MIB for TCP

RFC 4022

C

IP tunnel MIB

RFC 4087

C

IKE algorithms

RFC 4109

R

MIB for UDP

RFC 4113

C

Transition mechanisms

RFC 4213

R

BGP
-
4

RFC 4271

R

IPv6 addressing

RFC 4291

R

IP forward MIB

RFC 4292

C

MIB for IP

RFC 4293

C

Mobile IP management MIB

RFC 4295

R

Cryptographic suites

RFC 4308

R

ICMP

RFC 4443

R

Mulitprotocol extensions for BGP
-
4

RFC 4760

R

IPv6 neighbor discovor
y

RFC 4861

R

SLAAC

RFC 4862

R

IPv6 over PPP

RFC 5072

R

Depreciation of type 0 IPv6 headers

RFC 5095

C

Routing IPv6 with IS
-
IS

RFC 5308

R

QoS

DiffServ PHBs

RFCs 3246,2597

R

Minimum 4 hardware queues

DoD CoS/QoS WG

R

FIFO

RFC 3670

C

WFQ (Weig
hted Fair Queuing)

RFC 3662

C (see Note 2)

CQ (Custom Queuing)

RFC 3670

C (see Note 2)

PQ (Priority Queuing)

RFC 1046

C (see Note 2)

CB
-
WFQ (Class
-
Based Weighted
Queuing)

RFC 3366

C (see Note 2)

Network
Monitoring

SNMP

RFCs 1157

R

SNMP

RFCs 2206

R

SNMP

RFC 3411

R

SNMP

RFC 3412

R

SNMP

RFC 3413

R

Traps

RFC 1215

R

RMON (Remote Monitoring)

RFC 2819

R



E
-
4



Table E
-
4
-
6. CER Requirements Summary

(continued)


Specifications

Features

References

Required (R)

Conditional (C)

Security

Kerberos

RFC 1
510

R

FTP Security

RFC 2228

R

TLS

RFC 2246

R

BGP Security

RFC 2385

R

IPSEC VPN

RFCs 2401

C

HMAC
-
MD5

RFC 2403

R

HMAC
-
SHA

RFC 2404

R

ISAKMP

RFC 2407

R

ISAKMP

RFC 2408

R

IKE

RFC 2409

R

PPP Triple DES

RFC 2420

R

Public Key

RFC 2560

R

G
eneric Security

RFC 2743

R

Attack Detection

RFC 2827

R

Secret Key Transaction

RFC 2845

R

Line Trace

RFC 2925

R

X.509

RFC 3161

R

Syslog

RFC 3195; Note 3

R

Security model

RFC 3413

R

IKE

RFC 3526

R

AES

RFC 3566

R

AES Cipher

RFC 3602

R

Audi
t Capability

RFC 3624

R

AES
-
128

RFC 3664

R

ESP

RFC 3686

R

Authentication

RFC 3702

R

Crypto message

RFC 3852

R

Security architecture

RFC 4301

R

IP authentication header

RFC 4302

R

IP Encapsulating Security

RFC 4303

R

Cryptographic Algorithm

RFC 4305

R

IKEv2

RFC 4306

R

Crypto algorithms for IKEv2

RFC 4307

C

IPSec security policy database config MIB

RFC 4807

C

Crypto algorithm for ESP AH

RFC 4835

R

Suite B crypto for IPSec

RFC 4869

R

MIPv6 with IKE2 and revised IPSec

RFC 4877

R

IS
-
IS generic crypto authentication

RFC 5310

R

Access Control

RFC 2820

R

Access Control

IEEE 802.1x

R

Secure Remote Management

SSH2

R



E
-
4



Table

E
-
4
-
6
. CER Requirements Summary (continued)


NOTES:

1. DSCP: Differentiated Services Code Point, or DiffServ

Code Point. A marker in the header of each IP packet that prompts
network routers to apply differentiated grades of service to various packet streams, forwarding them according to different P
er
-
Hop
Behaviors (PHBs)

2.One of these queuing mechanisms is req
uired to implement EF PHB

3. RFC 1213 (MIB
-
II), RFC 1493 (Bridge MIB), RFC 1757 (RMON), RFC 1724 (RIP MIB), RFC 2096 (CIDR MIB), RFC 2674 (VLAN
MIB), Traps.


LEGEND:

CIDR



Classless Inter
-
Domain Routing

CoS



Class of Service

DSCP



DiffServ Code Point

DiffServ



Differentiated Services

DVMRP



Distance Vector Multicast Routing Protocol

EIA



Electronics Industries Alliance

FIFO



First
-
in First
-
out

ICMP



Internet Control Message Protocol

IETF



Internet Engineering Task Force

IGMP



Internet Group Mult
icast Protocol

IP



Internet Protocol

IPv4



IP version 4

IPv6



IP version 6


IEEE



Institute of Electrical and Electronic Engineers Inc.

JTA



Joint Technical Architecture

LAN



Local Area Network


MIB



Management Information Base

MOSPF



Multicast OSP
F

NSLP



Netware Link Services Protocol

OSPF



Open Shortest Path First

PHB



Per Hop Behavior

PING



Packet Internet Groper

QoS



Quality of Service

RFC



Request For Comment

RIP



Routing Information Protocol

RMON



Remote Monitoring

SNMP



Simple Networ
k Management Protocol

TIA



Telecommunications Industry Association

TOS



Type of Service

UTP



Unshielded Twisted Pair

VLAN



Virtual LAN








































E
-
4




























(This page left intentionally blank.)