Hierarchical VPNs, Neighbor Discovery and Broadcast Links in Virtual Router Approach

1. Hierarchical VPNs, Neighbor Discovery and Broadcast Links in Virtual Router Approach Karthik Muthukrishnan Senior Consulting Engineer Thomas Walsh Principal Network Consultant Lucent Technologies

2. IP VPN Motivation Realization of multiple private, geographically dispersed IP Networks (transparent and secure private IP interconnection) over a shared provider infrastructure

3. IP MPLS VPNs Emulate a Private Network Over a Shared IP Network Shared IP Network IP VPNsMotivation Branch/Regional Offices Remote Workers Internet Corporate Headquarters Customers, Suppliers • Layer 3 - Any to Any connectivity • Security, reliability, performance, management • No manual configuration of PVCs or tunnels

4. Customer AHeadquarters Customer B Dallas Branch Customer B Headquarters CE Router CE Router CE Router HQ VNP 20000 VNP 100 VNP 10 VNP 100 VNP 1000 Customer AVPN Customer BVPN VNP 10 VNP 20000 Boston LA VNP 20000 VNP 100 VNP 10000 VNP 10 VNP10 VNP 10 HQ VNP 10 CE Router CE Router CE Router Customer B LA Branch Customer A LA Branch Customer A Boston Branch Dallas LA Multiple IP VPNs Physical Topology View Logical VPN View PE PE P P PE PE

5. IP VPN Features • Private Addressing • Intranet • Extranet • Privacy • Multiple sites • Traffic engineering • IP enabled services(including voice)

6. What are Virtual Routers? • Each Virtual Router (VR) is a cross sectional slice of the hardware and software resources. • Each VR is NOT a separate operating system“task” • Resides only at edge of SP network • Logically equivalent to a physical router (filters, interfaces, routing ports, access lists, configuration, management, monitoring,) • VRs and physical routers in a VPN represent a private routing domain with defined points of connection to the rest of the world • VRs discover each other in the same way physical routers discover each other over a LAN • Use standard link level multicast • No need for an additional membership discovery scheme

7. Hierarchical VPNs [Carrier’s carrier]

8. IP VPN - Green Foods ParisOfficeGreen Foods BerlinOfficeGreenFoods Remote Workers PSTN/Cable/DSL/Wireless Boston Office Green Foods Omni Present Provider

9. IP VPN - Red Foods London Office Red Foods Omni Present Provider Paris Office Red Foods Internet PSTN/DSL/Cable/Wireless

10. Problem Statement • Omni present provider rarely present.. • Regional providers provide last mile service • National/International carriers provide global connectivity • Need bridge to connect regional and global carriers

11. London Office Red Foods Paris Office Green Foods London Provider Paris Provider Paris Office Red Foods Boston Provider Berlin Office Green Foods Boston Office Green Foods Hierarchical VPNs - Business Model International Provider Berlin Provider

12. London Office Red Foods Paris Office Green Foods London Provider Paris Provider Paris Office Red Foods VR VR VR VR VR VR Boston Provider Berlin Office Green Foods VR VR VR VR VR VR VR VR VR VR VR VR Boston Office Green Foods Hierarchical VPNs - Network Model International Provider Berlin Provider

13. Multi-Level Hierarchical VPNs Level 1 VPNs Level 0 VPN Level 1 VPNs VPN X VPN X VPN Y VPN Y VPN A VPN Z VPN Z Data within a Level 1 VPN is transported transparently across the Level 0 VPN Hierarchies can be extended to more than two Levels

14. London Office Red Foods Paris Office Green Foods London Provider Paris Provider Paris Office Red Foods VR VR VR VR VR VR Boston Provider Berlin Office Green Foods VR VR VR VR VR VR VR VR VR VR VR VR Hierarchical VPNs International Provider Berlin Provider Boston Office Green Foods

15. VR VR VR VR VR VPN LSP Tunnels Inter VR link Inter VR link Purple VPN’s LSP Tunnel Inter VR link

16. VR VR VR VR VR VR Inter VR Links Level 1 VPN Level 2 VPN Inter VR link Level 2 VPN Inter VR link

17. Inter VR Links • Supports hierarchical relationship • Level 1 .. Level 2 .. Level N VPNs • Supports peering relationship • Internet connectivity • Inter VPN [controlled] connectivity • Controlled by standard routing policies at both ends

18. Neighbor Discovery via Broadcast Links

19. Customer A Branch (Boston) Parts DB 165.1.1.1 VR-B IP Interface(150.1.1.1) IP Interface(150.1.1.2) Inter VR Broadcast Link VR-A IP Interface(150.1.1.3) VR-C Customer A’s Vendor Customer A HQ (Chicago) 185.1.1.1 Neighbor Discovery Switch-B Backbone address =150.202.77.2 Service Provider’sNetwork Switch-C internal Backbone address =150.202.79.12 Switch-A Backbone address =150.202.78.12

20. For more information • Muthukrishnan, K. et al, “A Core MPLS IP VPN Architecture”, RFC-2917, September 2000 • Muthukrishnan, K. et al, “A Core MPLS IP VPN Architecture”, <draft-muthukrishnan-rfc2917bis-00.txt>, work in progress in IETF • Kathirvelu, C. et al, “A Core MPLS IP VPN Link Broadcast and Virtual Router Discovery”, <draft-kathirvelu-corevpn-disc-00.txt>, work in progress in IETF • Kathirvelu, C. et al, “Hierarchical VPN over MPLS Transport”, <draft-kathirvelu-hiervpn-corevpn-00.txt>, work in progress in IETF • Draft ITU-T Recommendation Y.1311.1, Network Based IP VPN over MPLS Architecture

21. Thank you! Thomas Walsh tdwalsh@lucent.com Karthik Muthukrishnan mkarthik@lucent.com