1. Virginia Telehealth Network (VTN) Backbone Infrastructure Work Group ATM/Frame or MPLS September 21 2006

2. Infrastructure Work Group2 VTN Backbone Requirements All traffic will be IP based Must provide priority for Video, Images and Voice. (CoS or QoS) Users must be able to share a common backbone to reduce cost Connectivity must be any to any (Internet/Intranet like service) Must be able to transport IPv6 Must NOT be contract and carrier dependent

3. VPN is the way to go for VTN

4. Infrastructure Work Group4 Applications and protocols can sway the decision to MPLS Peer-to-peer driving any-to-any  Voice and video  Unified Communication (Messaging, Media and Web Conferencing) Non-IP protocols Broadcast or multicast Managing service quality with class of service  Layer 3 MPLS VPNs typically have robust CoS  Approach for QoS on Virtual Private Wire Service based on underlying encapsulation

5. Infrastructure Work Group5 Evolution of the Market

6. Infrastructure Work Group6 Forrester’s Business Technographics, May 2005 Yankee Group 2005 Metro Ethernet Survey Top VPN Considerations?

7. Infrastructure Work Group7 Network Virginia Backbone SprintLinkAbileneSprintLink Washington 1 Washington 2 RichmondRoanoke ATM Switch Richmond ATM Switch Washington ATM Switch Point to Point ATM Traffic Internet Traffic Only OC-3 OC-12

8. Infrastructure Work Group8 Customer Edge Access ATM Core ATM Switch Backbone T1, NxT1, T3, OC3 Other ATM networks ATM / Frame Relay

9. Infrastructure Work Group9 ATM / Frame Relay Services (Layer 2) Commercially available for more than 15 years Layer 2 service over a shared, private network Point-to-point switched service utilizing virtual connections Most enterprise implementations are hub and spoke ATM has a mature set of CoS capabilities Frame Relay / ATM Network

10. Infrastructure Work Group10 ATM CoS CoS Classes of Services  Constant Bit Rate (CBR)  Variable Bit Rate Real Time (VBR-rt)  Variable Bit Rate Non-Real Time (VBR-nrt)  Unspecified Bit Rate (UBR)

11. Infrastructure Work Group11 ATM Class of Service CBR (Constant Bit Rate) - Supported by a constant cell transfer rate, CBR is designed for applications that require stable bandwidth levels and low latency (in other words, those which cannot tolerate variances in delay or cell loss). Examples of applications that require CBR service include boardroom quality video and private line circuit emulation. VBR-rt (Variable Bit Rate Real-Time) - Designed for applications that require stable bandwidth levels and low-to-medium latency (in other words, those applications that cannot tolerate variances in delay or cell loss). Examples of applications that require VBR-rt service include desktop quality video and packetized voice applications. This service class can also carry SNA traffic. VBR-rt has a less stringent variance tolerance than CBR VBR-nrt (Variable Bit Rate Non-Real-Time) – This service category is designed for servicing bursty data applications such as e-mail, Internet and other LAN data applications. This service class can also carry SNA traffic, if the CDV is set within acceptable limits. UBR (Unspecified Bit Rate) - Unspecified Bit Rate (UBR) service is designed for data applications that do not require guarantees on when or if the data is delivered.

12. Infrastructure Work Group12 Cost for each Class of Service

13. Infrastructure Work Group13 The Future of Frame Relay and ATM Service providers and network equipment vendors are investing heavily in newer generation technologies Some service providers have announced an intent to decommission existing frame relay and ATM networks Service providers will begin evaluating which emerging technology would be the best next step

14. Infrastructure Work Group14 “[MPLS VPNs’] true strength lies in its flexibility: MPLS can provide the performance and dynamic bandwidth characteristics of Ethernet as well as the inherent resiliency of IP routing…Providers design these networks today with business customers in mind.” – Forrester Wave: North American MPLS Services, Q12006

15. Infrastructure Work Group15 Customer Edge Access MPLS Edge Router Private IP Core MPLS (IPv6) IP Core Provider Edge FR, ISDN, Dial or ATM T1, NxT1, T3, OC3 Other MPLS, ATM, and Frame networks (Internet 2) MPLS is becoming Industry Standard

16. Infrastructure Work Group16 MPLS Network Frame Relay Network Edge MPLS VPNs (Layer 3) Also known as RFC 4364 VPN, RFC 2547-bis VPN Commercially available for seven years IP-based service delivered over shared networks (public and private IP) Multipoint routed service Service typically can support multiple encapsulations to allow for seamless migration from other technologies Robust QoS utilizing DiffServ

17. Infrastructure Work Group17 The Future of MPLS VPNs These services have hit critical mass for most service providers Providers continue to invest heavily in both network expansion and service surround  Simplified migrations from legacy technologies  Flexible network management options and customer reporting  Broadening suite of access options

18. Infrastructure Work Group18 Why QoS? Controls Latency sensitive data such as Video and Voice Admission control – bandwidth control and policy control Resource Allocation – Queuing and scheduling – Traffic flows and traffic classes Gatekeepers – Network administer – manages the pool of available bandwidth Types:  IP Precedence  Differentiated services (Diffserv)  Integrated services (IntservRSVP) QoS must be available all the way to the end equipment

19. Infrastructure Work Group19 Optimized Queuing Using QoS 11 Video Traffic 22 LAN Traffic 3 3 3 Internet Traffic 2 3 211 Transmit ring

20. Infrastructure Work Group20 Better Quality of service Better security services through VPNs Moves data packets across the backbone faster and more efficient IPv6 can implement multi-cast in the IP protocol unlike IPv4 IPv6 has a new class of service called “any cast” which routes data to and from the nearest host. "Shortest Route” IP protocol running on Internet 2 backbone Why IPv6?

21. Infrastructure Work Group21 Network Cost Efficiencies and Simplification Realized in MPLS Network Network Cost Efficiencies and Simplification MPLS Network Any-to-Any IP Connectivity (MPLS) Host #1Host #2 Traditional Frame Relay, ATM or Private Line Networks Host #1Host #2

22. Infrastructure Work Group22 IP over ATM Issues IP over ATM has the potential to create bottlenecks leading into the core resulting from the lack of segmentation and reassembly (SAR) functional on OC-48 and faster interfaces. IP over ATM results in an inefficient use of network bandwidth due to the traditional ATM cell tax. The IP differentiated Services (DiffServ) approach to class of service (CoS) does not map well to existing ATM quality of service (QoS) mechanisms. TCP/IP is an inherently inefficient protocol to run over an ATM transport, because the transmission of a single ACK requires not one but two ATM cells.

23. Infrastructure Work Group23 Summary of Considerations ATMMPLS Reliability/ Performance Yes Network SecurityYes Any to any connectivityNO only point to pointYes Multicasting capabilityNOYes DiffServNO only CoSYes (QoS) and can be changed on the fly Nx64k serviceNOYes ATM and Frame CompatibleOnly ATMLPWS – can do Frame and ATM Ethernet accessNOYES

24. Infrastructure Work Group24 Pricing Elements ATM (Network Virginia )  Local Loop  Port Speed (based on CoS) CBR VBRrt VBRnrt  Minimum Contract Period is one year (??) MPLS (VTN)  Local Loop  Port Speed with QoS included  Minimum Contract Period is 4 months

25. Infrastructure Work Group25 Example One

26. Infrastructure Work Group26 IP over ATM (Network Virginia) Router DATA Switch PSTN ISDN Video Infrastructure Gateway M C U Gatekeeper proxy MCU Router Regional Site A Main Site Router Regional Site B Router Regional Site C

27. Infrastructure Work Group27 Router DATA Switch Video Infrastructure Gateway M C U Gatekeeper proxy MCU Router Regional Site A Main Site Router Regional Site B Router Regional Site C VTN IP over MPLS (VTN)

28. Infrastructure Work Group28 Example Requirements ATMMPLS Site Site services Requested Site Bandwidth Requirements Local Loop Requirements Port Speed Requirements Local Loop Requirements Port Speed Requirements Main Site Two Video Channels 2 x 384kbps = 768kbps 2 x DS1 (1,544kbps) 1,544kbpsDS1 (1,544kbps) 768kbps Regional Site A One Video Channels 384kbps DS1 (1,544kbps) 1,544kbpsDS1 (1,544kbps) 384kbps Regional Site B Two Video Channels 2 x 384kbps = 768kbps 2 x DS1 (1,544kbps) 1,544kbpsDS1 (1,544kbps) 768kbps Regional Site C One Video Channels 384kbpsDS1 (1,544kbps) 1,544kbpsDS1 (1,544kbps) 384kbps TOTALS 2,304kbps9,254kbps6,176kbps 2,304kbps

29. Infrastructure Work Group29 Pricing Monthly Model The above cost are based on market rates

30. Infrastructure Work Group30 Yearly Cost Model The above costs are based on market rates