Provider Opportunities for Enterprise MPLS

1. Provider Opportunities for Enterprise MPLS APRICOT 2006, Perth Matt Kolon [matt@juniper.net]

2. NGN Challenges Opportunities for network infrastructure savings • Essential Application and service support • New and legacy requirements • Quality • Ensure appropriate QoS and reliability • Convergence with Virtualization • Lower capex and opex by network optimization MPLS addresses all three of these challenges!

3. Collapse traffic onto a single infrastructure, but maintain separation, privacy, policy Each stream, group, service or application gets the required QoS, availability, etc. Next-generation and legacy interfaces, services, apps supported without changes MPLS Addresses Enterprise Challenges In three critical NGN areas, MPLS helps: Services: Policy: Connectivity:

4. Connectivity: Convergence with Virtualization • More services on fewer networks saves money • Convergence requires QoS, VPNs, traffic engineering, L1 and 2 support, etc. • Services never want to be converged • Differences in QoS requirements, routing, availability, privacy, regulatory needs • Each service should experience its network as custom-built for it • How can we help customers converge, but not seem to from a service point of view?

5. CoC MPLS CE-CE IPsec MPLS VPNs PE-CE IPsec CoC MPLS Inter-AS MPLS Many uses for MPLS in the Enterprise • Simple ATM or Frame VPN replacement • Outsourced IP VPN • Internet access links • Point-to-point TDM replacement circuits • Hierarchical VPN carriage or peering • Layered security element • Hybrid carrier/enterprise network

6. Acctg Internet Sales Mktg Acctg Ops ATM Ops PSTN / TDM Sales Mktg Ops Sales Different Networks for Different Apps

7. Acctg IP / MPLS Sales Mktg Acctg Ops TDM VPNs ATM Ops Internet Sales Mktg Ops Sales MPLS supports virtualized convergence Not really a “cloud” any more, is it?

8. Service Quality through Policy Service Quality through Policy • Essential applications require highly available service, usually with good QoS • Virtualization ensures separation of services, yet each service needs its own treatment: • Traditional QoS (delay, bandwidth, loss, etc) • Availability (network resilience) • Security (privacy, separation) • MPLS supports both standards-based and unique solutions in these three critical areas • Without attention to service quality, no converged network can meet business goals

9. Service Quality Mechanisms Determinism / Planning Traffic Engineering DS-TE Availability Secondary Paths Fast Reroute Fast IGPs BFD QoS Diffserv Multifield Classification Filter-based Forwarding Security Policing Firewalls Monitoring Policy Application Deterministic Routing Separate MPLS paths or VPNs

10. Application and Service Support • Native service environments preserve investments • Enterprise networks are always in flux • Old applications and services phasing out, new ones phasing in • Any convergence solutions must flexibly support this condition of continual change • Support must sometimes be generic (e.g. Internet, IP) and sometimes specific (e.g. ATM CES, TDM) • MPLS supports specific applications with standards-based, partner, and proprietary solutions

11. Native Service Environments Capable of low-cost and flexible reconfiguration and migration Next Gen Services IP Routing L3VPNs Transparent LANs P2P Ethernet Interfaces ATM Frame Ethernet Serial Any speed Legacy Services TDM DLSW PWE3 Solutions Frame / ATM VPNs

12. Acctg Ops Sales Sales Acctg Ops MPLS Paths and VPNs • MPLS labels are assigned to identify a path, location, or both • Locations and paths together create VPNs • Enterprises can use VPNs to subdivide networks in whatever way works best for them: • By application • By service • By user group • By security level

13. pptp ipsec Hybrid Enterprise / Provider MPLS • MPLS VPNs have been a very successful service for many providers • Enterprises use these services when they are more cost-effective than building their own VPNs • Enterprises who build their own MPLS VPNs can link them with providers’, thus creating a hybrid • Remote workers and non-MPLS offices may access the combined MPLS network via encrypted tunnels

14. Carrier of Carrier MPLS • Geographically distributed enterprises often have “islands” of network services requiring interconnection • Providers offer “carrier-of-carrier” services to their MPLS customers, both carriers and enterprises • MPLS interconnection exists for services at layers 1, 2, and 3 (e.g. pseudowires, Ethernet, ATM, IP, etc.) • MPLS networks may also be linked by dark fiber, private lines, or other “non-MPLS” methods

15. Summary: Benefits of MPLS in the NGN • All business applications are supported • Legacy or NextGen, critical to best-effort • Each application is assured the experience (security, availability, performance) it requires • Converged networks that “seem” separate • One bill for one network infrastructure from your provider, yet many services / apps • One network to manage, control, secure, maintain, and regulate

16. Thanks! Matt Kolon [matt@juniper.net]

17. MPLS Technology 101 • MPLS uses small labels (placed after the L2 header) to switch traffic along a path • These paths co-existwith and dependon IP, and are set up and maintained by RSVP and LDP • IP routing and forwarding proceeds as normal using standard protocols and procedures • Multiple tags can be used to tunnel paths inside each other, or to identify endpoints • That’s it! Routers use this infrastructure to build MPLS-based services like VPNs