Virginia Telehealth Network (VTN) Backbone Infrastructure Work Group ATM/Frame or MPLS

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

2. 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 Infrastructure Work Group

3. VPN is the way to go for VTN

4. 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 Applications and protocols can sway the decision to MPLS Infrastructure Work Group

5. Evolution of the Market Infrastructure Work Group

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

7. SprintLink SprintLink Abilene OC-12 OC-3 Network Virginia Backbone Washington ATM Switch Point to Point ATM Traffic Internet Traffic Only Washington 1 Washington 2 Point to Point ATM Traffic Internet Traffic Only Internet Traffic Only Internet Traffic Only Roanoke Richmond Internet Traffic Only Point to Point ATM Traffic Roanoke ATM Switch Richmond ATM Switch Infrastructure Work Group

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

9. 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 Infrastructure Work Group

10. 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) Infrastructure Work Group

11. 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. Infrastructure Work Group

12. Cost for each Class of Service Infrastructure Work Group

13. 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 Infrastructure Work Group

14. “[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 Infrastructure Work Group

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

16. 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 Frame Relay Network Edge MPLS Network MPLS VPNs (Layer 3) Infrastructure Work Group

17. 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 Infrastructure Work Group

18. 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 Infrastructure Work Group

19. Optimized Queuing Using QoS Video Traffic 1 1 Transmit ring LAN Traffic 2 2 1 1 3 2 2 Internet Traffic 3 3 3 Infrastructure Work Group

20. Why IPv6? • 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 Infrastructure Work Group

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

22. 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. Infrastructure Work Group

23. Summary of Considerations Infrastructure Work Group

24. 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 Pricing Elements Infrastructure Work Group

25. Example One Infrastructure Work Group

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

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

28. Example Requirements Infrastructure Work Group

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

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