IP,%20VPN,%20MPLS%20og%20QoS

1

• IP, VPN, MPLS og QoS
• Hvor er vi og hvor går vi?

NORTIB 13 Februar 2001
Michael Engström IS Mentor Michael.engstrom_at_anzur.
com 47 913 24 140
2
Guesstimating the future
Predictions are hard

• especially those about the future
• Yogi Berra

3
Agenda

• Next Generation Networks
• VPNs
• Quality Of Service
• MPLS
• The Converging IP Network

4
Agenda

• Next Generation Networks
• VPNs
• Quality Of Service
• MPLS
• The Converging IP Network

5
Broadband Access Networks

• xDSL, Cable, Ethernet, Wireless, etc.
• What is Broadband
• Mbps or services ?
• Broadband Access does not mean Broadband Internet
  connectivity
• Internet is only one of many services
• Content and caching will provide high capacity
• Always on at a fixed low price? Buy it
  regardless...
• Different focus
• Consumer or Business
• Low cost and business user does not add up

6
Internet 2 Background

• 1995 NSF provided funding to MCI
• 1996 congestion struck the NAPs
• Proposal for direct connection to the VBNS
• HPC program founded
• Started in 1996 by 34 contributing universities
• More than 180 partners today
• Application focus
• Remote instrument control (telescopes,
  microscopes), high-performance distributed
  computation, and large-scale database navigation.
• Connections via VBNS or Abilene (UCAID)
• IP Over ATM, Packet Over Sonet (POS)

7
Technology Focus

• Security
• AAA
• Multicasting
• Streaming Video
• PIM Sparse Mode, MBGP, MSDP, MASC
• Quality Of Service /Qbone
• End-to-end vs. segment-only QoS
• Signaled vs. static provisioning
• Amount of state required by various approaches
• Level of granularity, precision, and strength of
  QoS guarantee
• Reliability and recovery dynamics
• DiffServ

8
GigaPops

• Layer 2 and Layer 3
• ATM, GigE, POS, etc.
• Local
• 3D design
• Shortest path at all times
• Unlimited scalability

9
GigaPops

• Layer 2 and Layer 3
• ATM, GigE, POS, etc.
• Distributed Arch
• 3D design
• Shortest path at all times
• Unlimited scalability

10
CAVE

• Open Cube
• Images projected on all walls and floor
• User with Light-weight Stereo 3D Glasses and RF
  mouse
• Remote vehicle design
• Dataflows
• control, text, audio, video, tracking, database,
  simulation, haptic, and rendering flows
• Requirements
• Latency, jitter, and bandwidth per flow

11
IPv6

• Driven by IETF and IPv6 Forum
• Compelling reasons
• Addressing
• Server-less auto configuration
• Scalability in routing
• Mobility
• QoS
• IPv4 has provided a number of workarounds
• Integration with IPv4
• Dual-stack, Tunneling or Translation
• 128 bit addressing
• Hierarchical approach
• TLA, NLA, SLA, Node Identifier

12
IPv6 Address Space

• 340,282,366,920,938,463,463,374,607,431,768,211,45
  6 unique addresses available
• 665,570,793,348,866,943,898,599 addresses per
  square meter assuming the earth surface is
  511,263,971,197,990 square meters).
• But we need hiearchies..
• Christian Huitema
• Pessimistic approach 1,564 addresses for each
  square meter of the surface of the planet Earth.
• The optimistic estimate would allow for
  3,911,873,538,269,506,102 addresses for each
  square meter of the surface of the planet Earth.

13
Agenda

• Next Generation Networks
• VPNs
• Quality Of Service
• MPLS
• The Converging IP Network

14
Virtual Private Networks

• The ability to use a shared media for private
  communications in a secure an reliable manner
• ATM, X.25, Frame Relay Layer 2 VPNs
• IP Based VPNs is transparent for the transmission
  layer
• Hip or Hype? More than encryption
• Security, Firewalls, Encryption, AAA, Intrusion,
  Detection, Active Audit, Tunneling, Quality of
  Service, Network Management
• Several distinctions
• Access, Intranet, Extranet
• VC, Overlay model or Peering
• IPsec and/or MPLS
• Multi FIB and QoS based VPNs (Virtual Routing)
• Peer based as opposed to connection oriented
• Watch out for complexity

Cost and ease of use are the compelling reasons
15
Outlook

• Today 30 of all VPNs are in-house. By 2004 90
  will be outsourced to Service Providers,
  minimizing the agony of management for the
  customer
• Cahners In-Stat 2000

IP VPN services market will grow from 2 billion
today to 17.6 billion by 2004 and IDC2000
The IP VPN services market will reach a total of
340 Billion USD by 2010, estimating a total of
280 Billion USD for the equipment
manufacturers Yankee Group 2000
16
VPN Leaders

• Lucent Technologies
• Springtide Networks
• CoSine Communications
• Nortel Networks
• Shasta Networks
• Cisco Systems
• Ennovate
• Quarry
• Unisphere
• Redback Networks
• Ellacoya
• Alcatel
• NorthChurch/Newbridge

17
SP VPN Winners 2000

• UUNET
• Genuity
• CPE
• Infonet
• Equant
• FR
• ATT
• MPLS

• MCI Worldcom
• GlobalOne
• Qwest
• SAVVIS
• IP over ATM/Shasta
• Core Express
• SSP
• SmartPipes
• Wholesale VPNs
• Pilot Network Services
• Aventail

18
Features to ask for

• Encryption
• Stateful Firewalls
• Content Steering/Load Balancing
• Network Address Translation
• LDAP or other mobility solution for VPDN
• FR Interworking

• Realtime SLA monitoring
• Private Portal Integration
• Service Provisioning
• Quality Of Service
• Multicast Support
• L2 Transparency

SP Based VPNs will (?) prevail
19
Agenda

• Next Generation Networks
• VPNs
• Quality Of Service
• MPLS
• The Converging IP Network

20
Capability today...

• The commodity Internet Offers Quality Of Service
  today

A poor Quality Of Service....
21
Defining QoS

• QoS Should be defined as the level of
  application-quality and availability from an
  end-user perspective

• Therefore you
• design a fault tolerant network
• use stabile SW code
• loadshare to maximize server throughput
• use Content Distribution to physically co-locate
  content with the end-user
• cache if possible/needed
• need bandwidth
• may prioritize traffic

22
QoS Not only for Multimedia

• Effect on network availability

Congestion related performance degradation has
been found to cause the majority of network
downtime costs
Michael Howard, President Infonetics Resaerch

• 1997 Infonetics Research
• Business Centric Network Management and Downtime
  Costs

23
SAP Response Time Evaluation

• SAP BW requirements for optimal operations varies
  between 20/60 kbps per session

6 sec
5 sec
4 sec
3 sec
2 sec
1 sec
SAP Only
SAP FTP
SAP FTP

• Cisco 1999
• Internal Whitepaper

24
Making it manageable

• Real-time applications
• Voice over IP, Video Conferencing, Video
  Telephony, Distance Learning
• Business Critical Applications
• SNA, SAP R/3, Oracle, Peoplesoft, Telnet
• Best effort Data Applications
• File Transfer, Email, Web

25
Traffic Classes
Integrated Access
Premium, Standard, Best Effort
Realtime
Guaranteed End-to-End Latency and Delivery
Critical
Guaranteed Delivery
Wasteable
Best-Effort Delivery
Classification
26
End-to-end
LAN Switch
Edge Router
CoreRouter

• QoS Is an End-to-end requirement
• Layer 2 and Layer 3
• Bandwidth will help you a lot
• QoS mechanisms kicks in when you need them
• QOS algorithms offer temporary relief only
• If you need more bandwidth you need more
  bandwidth
• Prioritization can be an option to buying more
  bandwidth in the WAN

Edge Router
LAN Switch
27
DiffServ

• IETF Standard
• RFC2430, 2474, 2475, 2597, 2598, 2638, 2963,
  2983, 2998
• Operates at Layer 3 only
• Does not provide Hard QoS or methods for actual
  delivery of function
• Usage of the Diff Serv field
• 64 classes (6 out of 8 bits)
• IP Precedence of the TOS octet mapped to DiffServ
• Supersedes IPV4 and IPV6 TOS field definitions
• Granularity issues
• Host or router marking
• Dynamic marking based on COPS requests
• Pre-conditioning
• Shaping / Policing
• Allows for aggregates

28
Diffserv architecture
PHB based on Code Point
DS Boundary Node
Classification (Conditioning)
Diffserv Domain
Behavior (CP) Aggregate
Traffic
Multi Field
Diffserv Domain
Inclusion of non-DS-compliant nodes within a DS
domain may result in unpredictable performance
and may impede the ability to satisfyservice
level agreements (SLAs) RFC2475
29
Diffserv Traffic Conditioner
Meter
Classifier
Shaper
Marker/Dropper
Traffic

• Classifier
• Selector of action
• Shaper
• Temporary delay of traffic to conform to TCA

• Meter
• Measure in- or out-of profile behavior
• Marker
• CP setting
• Dropper
• Discard based on meter feedback and/or CP setting

30
RSVP and the Intserv Model

• IETF Standard
• RFC1633, 1727, 2210, 2213, 2214, 2215, 2382,
  2688, 2689, 2815, 2998, 3006
• Specified in 1994
• Defines a framework for the Integrated model
• Components
• Packet scheduler
• Classifier
• Admission Control
• Reservation Setup Protocol
• Scalability Issues

31
Intserv Framework
Routing Agent
Reservation Setup Agent
MgmtAgent
Backend SW
AdmissionControl
FIB
Traffic Control Database
Classifier
Traffic
Fwd path
32
RSVP

• IETF Standard
• RFC2205, 2206, 2207, 2208, 2209, 2210, 2379,
  2380, 2382, 2490, 2745, 2746, 2747, 2749, 2750,
  2752, 2752, 2814
• Transport level protocol
• Application level signalling only (Microflow
  Reservations)
• Much like ICMP
• Unidirectional reservation in transport path
  nodes
• Receiver responsibility
• Independent of routing protocols
• Hence support for MC, OSPF, IS-IS, IPv4 and IPv6
• Vendor might implement Proxy RSVP
• Prevent misuse as well as enabling of reservation
  for non-RSVP capable clients

Request
33
An end-to-end framework for QoS

• Intserv over Diffserv networks
• Can be viewed as complementary technologies
• RSVP
• Explicit and dynamic vs. static signaling
• Allows for intelligent host decisions
• Resource requests can be re-directed to PBN
  servers
• Diffserv
• Dynamic adjustment of traffic management controls
  of PHB relating to current application needs
• RSVP Signaling mapped to PBN and a Intserv
  capable Diffserv core should provide necessary
  QoS functionality
• Requires pre-conditioning

34
Agenda

• Next Generation Networks
• VPNs
• Quality Of Service
• MPLS
• The Converging IP Network

35
MultiProtocol Label Switching
MPLS

• A specification for layer 3 switching from the
  IETF. Similar to Cisco's tag switching, MPLS uses
  labels, or tags, that contain forwarding
  information, which are attached to IP packets by
  a router that sits at the edge of the network
  known as a label edge router (LER). The routers
  in the core of the network, known as label switch
  routers (LSRs), examine the label more quickly
  than if they had to look up destination addresses
  in a routing table.When fully implemented on
  the Internet, MPLS is expected to deliver the
  quality of service (QoS) required to adequately
  support realtime voice and video as well as
  service level agreeements (SLAs) that guarantee
  bandwidth. Following in the tradition of the
  "dumb network," MPLS enables more decisions to be
  made at the periphery of the network.

36
Multi Protocol Label Switching
IP-Packet
1 Packet enters LER and Label1 is pushed

• MPLS Background
• Standardized by the IETF (RFC3031 - RFC3038)
• Based on Cisco Systems Tag Switching
• Very quickly revised by Juha Häinänen
• Forwarding based on Labels
• Packets are switched, not routed
• FIB translated into Label Forwarding Entries
• Labels are mapped to Forward Equivalency Classes
• Privacy and QoS of ATM, Frame Relay
• Flexibility and Scalability of IP

2 Labeled (1) packet enters LSR1. Label Lookup
is performed and labeL is swapped to L2
3 Labeled (2) packet enters LSR2. Label Lookup
is performed and labeL is swapped to L3
4 Labeled (3) packet enters LSR3. Label Lookup
is performed and labeL is swapped to L4
5 Packet enters LER and Label 4 is popped
IP-Packet
37
Agenda

• Next Generation Networks
• VPNs
• Quality Of Service
• MPLS
• The Converging IP Network

38
MPLS and applications

• An enabling platform for privacy and quality
  assurance across (a) public Internet

MPLS IP Routing Control
MPLS Multicast IP Routing Control
MPLS/VPN Routing Control
MPLS Traffic Engineering Control
MPLS Quality Of Service Control
Label Information Fwd Base
39
The Integrated Access Promise

• End-Customer Site with
• 8 Voice Channels (512K with PCM)
• 512K Data access
• 256K Internet Access
• 128K Video Conferencing
• 4 Access Lines will cost 3.589 Euro/month
• 1 Integrated E1 Access costs 1.251 Euro/m
• 65 Savings gt Margin and Competitive position

40
Basic Components of MPLS-VPNs

• Total path include
• Customer Edge (CE) router, Provider Edge (PE)
  router, Provider Router (P)
• MPLS is used for forwarding Packets in the
  Backbone
• Provides a level of Security equivalent to
  Frame-relay and ATM
• Supports Private IP Addressing in customer
  VPNs
• BGP4 is used for the constrained distribution of
  VPN Routing information and VPN Labels
• Creates a Forwarding table per VPN in each Edge
  Router serving that VPN.

41
MPLS VPN Packet Forwarding

• Logically separate forwarding table for each VPN
• Routing information based on extended (VPN-IP)
  addresses
• MPLS binds VPN-IP routes to label switched paths

42
MPLS QoS

• MPLS LSP can be prepended by a RSVP request
• Enables Traffic Engineering
• Traffic or Resource oriented
• Separate Fwd path from IGP selected path
• Conditioning
• Drop probability
• BW allocation and latency control
• Encoded in CoS field in lable header
• Aggregated flows in one LSP is called a trunk
• A LSP can consist of many Trunks
• HW/SW layer algorithms will provide the necessary
  guarantees
• Drop probability, BW and Latency guarantees
• Inter Provider SLAs, IPS
• Technology exisits. Procedures not (?)

43
Summary

• QoS and VPN will be available within the next 2
  years in the Internet with various span
• QoS in the SP area will be implemented using
  DiffServ in the foreseeable future
• RSVP/Intserv integration should offer better
  scalability
• MPLS VPN is likely to succeed
• Versatility
• Ease of use, cost and market dynamics
• QoS based VPNs is possible with MPLS
• Plan for IPv6
• DWDM and new carriers will have severe impact on
  pricing structure
• Bandwidth might become virtually free (?) but the
  services will cost
• Inter SP services for MC, VPNs and QoS will
  happen within 2-5 years

44

• Thank you!

http//www.anzur.com/presentations
Michael Engström IS Mentor Michael.engstrom_at_anzur.
com 47 913 24 140