Virginia Telehealth Network (VTN) Backbone Infrastructure ...
-
Upload
networkingcentral -
Category
Documents
-
view
425 -
download
2
Transcript of Virginia Telehealth Network (VTN) Backbone Infrastructure ...
Virginia Telehealth Network(VTN) Backbone Infrastructure
Work Group ATM/Frame or MPLS
September 21 2006
Infrastructure Work Group 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
VPN is the way to go for VTN
Infrastructure Work Group 4
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
Infrastructure Work Group 5
Evolution of the Market
2003 2005 2006
ATM
FrameRelay
MPLS (VPN)
Infrastructure Work Group 6
0% 5% 10% 15% 20% 25% 30% 35% 40%
Availability
Scalability
Manageability
Cost
Reliability
Security
0% 10% 20% 30% 40% 50%
QoS
Security
Flexibility
Coverage
Cost
Reliability
Forrester’s Business Forrester’s Business Technographics, May 2005Technographics, May 2005
Yankee Group 2005 Yankee Group 2005 Metro Ethernet SurveyMetro Ethernet Survey
Top VPN Considerations?
Infrastructure Work Group 7
Network Virginia Backbone
SprintLink
Abilene
SprintLink
Washington 1
Washington 2
RichmondRoanoke
RoanokeATM Switch
RichmondATM Switch
WashingtonATM Switch
Point to Point ATM Traffic
Point to Point ATM Traffic
Point to Point ATM Traffic
Internet Traffic Only
Internet Traffic Only
Internet Traffic Only
Internet Traffic Only
Internet Traffic Only
OC-3
OC-12
Infrastructure Work Group 8
Customer Edge
Access ATM Core
ATM Switch
Backbone
T1, NxT1, T3, OC3
Other ATM networks
ATM / Frame Relay
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 / ATMNetwork
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
Cost $
CBR
VBRrt
VBRnrt
UBR
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 VPNs’] true strength lies in its flexibility: MPLS can provide the performance and MPLS can provide the performance and dynamic bandwidth characteristics of Ethernet dynamic bandwidth characteristics of Ethernet as well as the inherent resiliency of IP routing…as well as the inherent resiliency of IP routing…Providers design these networks today with Providers design these networks today with business customers in mind.”business customers in mind.”
– – Forrester Wave: North American Forrester Wave: North American MPLS Services, Q12006 MPLS Services, Q12006
Infrastructure Work Group 15
Customer Edge
AccessMPLSEdge
Router
Private IP Core
MPLS (IPv6) IP
CoreProvider Edge
FR, ISDN, Dial or ATM
T1, NxT1, T3, OC3
Other MPLS, ATM, and Frame
networks (Internet 2)
MPLS is becoming Industry Standard
Infrastructure Work Group 16
MPLS NetworkMPLS Network
Frame Relay Frame Relay Network EdgeNetwork 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
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
11VideoTraffic
22LAN
Traffic
33 3InternetTraffic
23 2 11
Transmitring
Infrastructure Work Group 20
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?
Infrastructure Work Group 21
Network Cost Efficiencies and Simplification Realized in MPLS Network
Network Cost Efficiencies and Simplification
MPLS Network
Any-to-Any IP Connectivity (MPLS)
Host #1 Host #2
Traditional Frame Relay, ATM or Private Line Networks
Host #1 Host #2
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
ATM MPLSReliability/
Performance
Yes Yes
Network Security Yes Yes
Any to any connectivity NO only point to point Yes
Multicasting capability NO Yes
DiffServ NO only CoS Yes (QoS) and can be changed on the fly
Nx64k service NO Yes
ATM and Frame Compatible Only ATM LPWS – can do Frame and ATM
Ethernet access NO YES
Infrastructure Work Group 24
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
Infrastructure Work Group 25
Example One
Infrastructure Work Group 26
IP over ATM (Network Virginia)
Router
DATA Switch
PSTNISDN
Video InfrastructureGateway
MCU
Gatekeeperproxy
MCURouter
Regional Site A
Main Site
Router
Regional Site B
RouterRegional Site C
Infrastructure Work Group 27
Router
DATA Switch
Video InfrastructureGateway
MCU
Gatekeeperproxy
MCURouter
Regional Site A
Main Site
Router
Regional Site B
RouterRegional Site C
VTN
IP over MPLS (VTN)
Infrastructure Work Group 28
Example Requirements
ATM MPLSSite Site services
RequestedSite
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,544kbps DS1 (1,544kbps)
768kbps
Regional Site A
One Video Channels
384kbps DS1 (1,544kbps)
1,544kbps DS1 (1,544kbps)
384kbps
Regional Site B
Two Video Channels
2 x 384kbps = 768kbps
2 x DS1 (1,544kbps)
1,544kbps DS1 (1,544kbps)
768kbps
Regional Site C
One Video Channels
384kbps DS1 (1,544kbps)
1,544kbps DS1 (1,544kbps)
384kbps
TOTALS 2,304kbps 9,254kbps 6,176kbps 6,176kbps 2,304kbps
Infrastructure Work Group 29
Pricing Monthly Model
$0
$1,000
$2,000
$3,000
$4,000
$5,000
$6,000
$7,000
$8,000
ATM MPLS
Local Loop
Port Charge
Total
The above cost are based on market rates
Infrastructure Work Group 30
Yearly Cost Model
$0
$10,000
$20,000
$30,000
$40,000
$50,000
$60,000
$70,000
$80,000
$90,000
ATM MPLS
The above costs are based on market rates