90 likes | 226 Views
GVPNs: Generalized VPNs using BGP and GMPLS Toolkit draft-ouldbrahim-ppvpn-gvpn-bgpgmpls-06.txt. Hamid Ould-Brahim ( hbrahim@nortel.com ) Yakov Rekhter ( yakov@juniper.net ) (Editors). Contributors. Luyuan Fang (AT&T) Don Fedyk (Nortel) Peter Ashwood-Smith (Nortel)
E N D
GVPNs: Generalized VPNs using BGP and GMPLS Toolkitdraft-ouldbrahim-ppvpn-gvpn-bgpgmpls-06.txt Hamid Ould-Brahim (hbrahim@nortel.com) Yakov Rekhter (yakov@juniper.net) (Editors)
Contributors • Luyuan Fang (AT&T) • Don Fedyk (Nortel) • Peter Ashwood-Smith (Nortel) • Eric C. Rosen (Cisco) • Eric Mannie • John Drake (Boing) • Yong Xue • Riad Hartani (Caspian Networks) • Dimitri Papadimitrio (Alcatel) • Lou Berger (Movaz)
Draft Summary • Work started in 2001 on Optical VPNs services Evolved into Generalized VPNs through time. • The basic unit of GVPN service is a Label Switched Path (LSP) between two CEs across provider network. • Uses GMPLS (signaling only or both signaling and routing) and BGP as the discovery mechanism. • l1vpn is one type of GVPN services (when CE-PE interfaces are layer 1-based). • GVPN is a port-based VPN Model. • Reuses mechanisms already defined in layer (3,2) VPNs. • Two GVPN services defined (see next slides).
Service 1: Generalized Virtual Private Wire (GVPW) • Ability to establish private connections between CEs basic mode in the context of l1vpn. • Connectivity is done within a pre-configured port-topology. • Controlled by the customer • Configured at the provider network level • Customer may select any “connectivity” topology within the defined set (hub and spoke, full mesh, etc). • Service provider restricts customer’s connectivity topology to only the one in the set defined by the customer.
PE2 Customer Connectivity Topology P5 P4 P7 P6 P3 P1 P2 10.1.1.3 PE3 10.1.1.1 CE3 PE1 CE3 CE1 CE1 Service Provider Network 16.1.1.3 CE4 CE61 16.1.1.1 PE4 10.1.1.4 10.1.1.6 PE5 CE4 CE61 CE5 PE5 16.1.1.4 16.1.1.6 10.1.1.5 16.1.1.5 CE5 On-demand private connectivity within a VPN GMPLS UNI (overlay-draft) Private Addresses (on both sides of CE-PE link) CE: Router, Sonet/SDH, L2 switch Provider Addresses (for the same PE port not visible to the CEs)
GVPW Functions • Run a BGP auto-discovery mechanism • to allow the PEs to learn about the remote VPN ports and their corresponding provider addressing. • to allow the CE to auto-learn (when needed) the set of remote CE port addresses (to be used for signaling). • Once the discovery process is done, a CE initiates GMPLS path request to the attached PE for a given destination CE. • Using exclusively private addresses. • During signaling, switch private with provider addresses (referred as “shuffling” approach). • No need for VPN-ids in signaling between CE-PEs. • uses existing GMPLS signaling protocol
Service 2: Generalized Virtual Private Cross-Connect (GVPXC) • The service provider network appears as a GMPLS-enabled virtual private node • uses both GMPLS signaling and participates in distributing customer routing enhanced mode in the context of l1vpn. • Address the n square routing peering between CEs (across the l1vpn connections – for l1vpn) • Transparent integration of traffic engineering within the customer network
GVPXC-A 10.1.1.3 C1 10.1.1.2 C3 10.1.1.1 10.1.1.7 CE2 CE3 C4 10.1.1.8 C2 C5 CE4 C3 CE1 C7 Generalized Virtual Private Cross-connect (GVPXC) GMPLS enabled both at signaling and routing at CE-PE level Routing Adjacency OSPF-TE/ISIS (online) 10.1.1.4 10.1.1.6 GVPXC is addressed within the private network In such a way it reflects a normal LSR within the private network.
GVPXC Functions • Auto-Discovery mechanism • same as GVPW model. • Routing Considerations • Two deployments scenarios: Offline and online path computation. • For On-line path computation: • establish a routing adjacency with attached CEs (independent from the provider routing instance) • generate routing information with traffic engineering (TE) information for the set of CE-PE TE-links attached to the GVPXC, and • flood TE-Link routing information (such as the ones learnt from other customer network nodes) to the attached CEs using normal GMPLS routing procedures. • The approach for distributing “private” reachability within the provider network is similar to the virtual router approach used in layer-3 VPNs.