SES E-VPL Member Deployment for NJEDge.Net Verizon Business Ethernet Solutions Presented By Joseph O’Leary Sales Engineer Higher Education segment for Verizon Business

Ethernet Services - Summary

Verizon Switched Ethernet Service Types Verizon Ethernet LAN (E-LAN) Service MP2MP EVC, designed for bridge or router CEs Connectionless, any-to-any connectivity Transparent (VLAN tag preservation, L2CP tunneling) ‘All-to-One Bundled’ UNIs Service performance objectives E - UNI CE (Switch/Router) Verizon Ethernet Virtual Private Line (EVPL) Service P2P EVC, designed for router CEs Non-transparent service ‘Service Multiplexed’ UNI – one or more EVCs per UNI Service performance guarantees CE (Router) Possible 10GigE ICB in 2004 E-LAN is the current SES service type. With E-LAN, the Tunneled UNI provides "All-to-one bundling, i.e., all customer VLANs get tunneled through Verizon multipoint EVC (VLAN). Applications/Customers: LAN Interconnection: Government, Financial, Education, Medical

EVPL Metro Switched Ethernet Service HQ LAN CPE NID Verizon Metro Network Customer’s Virtual Network Ethernet Switch Customer Site A Dedicated Fiber Pair Redundant Management Links Data Services Network Operations( DSNOC) Customer Site C Customer Site B 10 M 100 M GigE (1000 M) LAN Service Connection Point Customer Equipment (*MNS Opportunity) Key Characteristics QoS options available Shared Ethernet switches Backbone: Multiple GigE links Dedicated fiber access Network Interface Device (NID) Customer virtual networks (VLAN) IOF

EVPL Metro Switched Ethernet Service Customer network Customer has three EVPL Premier UNIs and two EVCs, as shown below EVC-1: single CoS <EVPL-B> = <70 Mbps> EVC-2: multi-CoS <EVPL-RT, EVPL-PD> = <20Mbps, 50Mbps> Switch port configured as ‘Premier Access Line, tagged’ Switch port configured as ‘Premier Access Line, untagged’ E-UNI 100M SES Network E-UNI 1G CE 6509 6509 NID VLAN-ID=123 EVC-1 A1 A3 VLAN-ID=456 EVC-2 6509 All customer traffic is ‘tagged’ All customer traffic is ‘untagged’ E-UNI 100M A2 Note: For EVC-2, switch looks at {VLAN_ID + CoS (p-bit)} of each incoming service frame - frames must be ‘tagged’

Marking & CoS with SES-EVPL

IP Precedence and DiffServ Code Points Version Length ToS Byte Len ID Offset TTL Proto FCS IP SA IP DA Data IPv4 Packet 7 6 5 4 3 2 1 Standard IPv4 IP Precedence Unused DiffServ Code Point (DSCP) IP ECN DiffServ Extensions IPv4: Three most significant bits of ToS byte are called IP Precedence (IPP) - other bits unused DiffServ: Six most significant bits of ToS byte are called DiffServ Code Point (DSCP) - remaining two bits used for flow control DSCP is backward-compatible with IP Precedence DiffServ Class Selector (DSCS) also uses 3 most significant bits • IP Type of Service Byte—As Layer 2 media often changes as packets traverse from source to destination, a more ubiquitous classification would occur at Layer 3. The second byte in an IPv4 packet is the Type of Service (ToS) byte. The first three bits of the ToS byte alone are referred to as the IP Precedence (IPP) bits. These same three bits, in conjunction with the next three bits, are known collectively as the DSCP bits. The IP Precedence bits, like 802.1p CoS bits, allow for only 8 values of marking (0-7). IPP values 6 and 7 are generally reserved for network control traffic (such as routing). IPP value 5 is recommended for voice. IPP value 4 is shared by video conferencing and streaming video. IPP value 3 is for call-signaling. IPP values 1 and 2 can be used for data applications. IPP value 0 is the default marking value. Many enterprises find IPP marking to be overly restrictive and limiting, favoring instead the 6-Bit/64-value DSCP marking model (as defined further on the next slide) The last two bits of the IP ToS byte have been defined for use as IP Explicit Congestion Notification bits (in RFC 3168); in this manner TCP receivers can signal senders to slow down their transmission rates if the network is congested (without such signaling, traffic would have to be dropped before TCP senders would adjust their transmission rates) Source: Cisco training material

EVPL Services Domain Service Multiplexed UNI EVPL EVCs All UNIs in a given domain must be ‘Service Multiplexed’ Service Multiplexed UNI Offered only for 100M and 1000M UNIs (not 10M) Two types: ‘Untagged’ OR ‘Tagged’ (can’t be both on same UNI) CAC rules apply to UNI...more on this later... EVPL EVCs Customer gets ability to order an EVC with up to three CoS Separate speeds for each CoS For EVC order requiring 1 CoS  ‘VLAN ID’ is used to identify the CoS For EVC order with 2 or 3 CoS  2 options ‘EVC+CoS’ (VLAN ID + p-bit value) ‘EVC+DSCP’ could be used to identify the CoS on the EVC (only for EVCs connecting two untagged UNIs) L2CPs: All L2CPs are discarded at the UNI

Local Enterprise, EVPL-EVC, Multiple CoS Customer network Customer has three EVPL Premier UNIs and two EVCs, as shown below EVC-1: single CoS <EVPL-B> = <70 Mbps> EVC-2: multi-CoS <EVPL-RT, EVPL-PD> = <20Mbps, 50Mbps> Service Multiplexed, tagged Service Multiplexed, untagged E-UNI 100M SES Network E-UNI 1G CE 6509 6509 NID VLAN-ID=123 EVC-1 A1 A3 VLAN-ID=456 EVC-2 6509 All customer traffic is ‘tagged’ All customer traffic is ‘untagged’ E-UNI 100M A2 Note: For EVC-2, switch looks at {VLAN_ID + CoS (p-bit)} of each incoming service frame - frames must be ‘tagged’

EVPL Considerations EVPL is designed for customers using routers to access the service...Bridge CEs may not work correctly... All traffic is policed on these UNIs  CE can’t burst to line rate CE must police/shape traffic to coordinate with the Bandwidth Profile of the service Traffic exceeding the BWP is dropped by the policer More on this later... Connection Admission Control (CAC) rules limit the number of EVCs and the aggregate bandwidth per CoS on a given UNI

SES EVPL CoS ID, Tagged UNI Service multiplexed UNI, Premier Access Line, Tagged Two CoS ID options per EVC EVC: a given EVC (VLAN ID) –single CoS EVC + CoS: a given CoS (p-bit value) on a given EVC – multiple CoS Note: CoS ID options per EVC are independent, i.e., both can coexist on same UNI – see right EVC1 EVPL-RT or EVPL-PD or EVPL-B CE-VLAN CoS 5,6 CE-VLAN CoS 2 UNI EVC2 EVPL-RT CE-VLAN CoS 0 EVPL-PD EVPL-B

CoS Speeds Summary Allowable CoS Speeds per EVC, by Service Type Class of Service (CoS) EVPL Services Premier Access Line FE (100M) GE (1000M) Real-time (RT) 1-50 Mbps 1-100 Mbps Priority Data (PD) 1-500 Mbps Basic (B) 1-1000 Mbps EVPL CoS Speeds Low speed: 1 to 9 Mbps, in 1M steps Medium speed: 10 to 90 Mbps, in 10M steps High speed: 100-1000 Mbps, in 100M steps

UNI Connection Admission Control (CAC) Rules UNI CAC rules are built into Provisioning System Service Multiplexed UNI - see table below CAC Rules for Service Multiplexed UNI UNI speed Max # EVCs RT (50%) PD (85%) RT+PD (85%) Basic (500%) 100M 10 50 Mbps 85 Mbps 500 Mbps 1G 75 850 Mbps 5000 Mbps

EVPL CoS ID Values Customer CoS (p-bit) Value EVPL-EVC Multi-Service Scenarios Customer CoS (p-bit) Value EVPL-RT EVPL-PD EVPL-B {RT + PD + B} 5,6 2 0,1,3,4,7 {RT + PD} 0,1,2,3,4,7 N/A {RT + B} {PD + B} 0,1,3,4,5,6,7

TYPICAL(SEGP): TODAY PVC #1 /IP/VPN/ “EXTRANET” PVC #2 X Internet 1 (I1) X Member-to-Member Data Member-to-Member Video Internet 2 (I2)

TYPICAL(SEGP): TOMORROW EVC #1/ Best Effort CoS Priority Data CoS Internet 1 (I1) X Member-to-Member Data Member-to-Member Prioritized Video Internet 2 (I2) Member-to-Member Non-Prioritized Video

SAMPLE EVC Sizing EXAMPLE 1: Today: IP/VPN = 4 Mbps; Internet = 6 Mbps Tomorrow: EVC/BE= 10 Mbps; EVC/PD = 2 Mbps Internet Contract: 6 Mbps EXAMPLE 2: Today: IP/VPN = 10 Mbps; Internet = 10 Mbps Tomorrow: EVC/BE = 20 Mbps; EVC/PD = 6 Mbps Internet Contract: 12 Mbps