Service Requirements for Optical VPNs - PowerPoint PPT Presentation

“ Service Requirements for Optical VPNs” <draft-ouldbrahim-ovpn-requirements-00.txt> Hamid Ould-Brahim (Nortel Networks) Yakov Rekhter (Juniper Networks) Luyuan Fang (AT&T) Yong Xue (UUNET/WorldCom) Ananth Nagarajan (Sprint) Eric Mannie (Ebone) Marco Carugi (France Telecom) 51 th IETF, London, August 2001

OVPN Reference Model P P CE1 CE2 PE2 PE1 CE5 CE4 Service Provider Optical Network(s) CE3 PE4 PE3 CE7 CE6 P P OVPN A OVPN B CE4 CE5 CE1 CE2 CE7 CE6 CE3

Optical VPN Network Reference Model L3VPN-1 Example: A CE for OVPNA Example: A CE for OVPNA L3VPN-1 A PE for layer- A PE for layer -3 VPN 1,2 3 VPN 1,2 (RFC2547, VR) (RFC2547, VR) CE CE L3VPN-2 P CE CE L3VPN-2 OVPN A P OVPN A PE1 PE2 Router CE OVPN B CE CE L2VPN A L 2 V P N A Service Provider Optical Network(s) OVPN B L2VPN B L2VPN B PE3 PE4 PE OVPN C P OVPN D P OVPN C OVPN D Ethernet VPN D CE SONET/SDH CE VPN D

Optical VPN Service - Example CE– –2 2 CE CE– CE –1 1 SONET SONET P P P P SONET SONET SONET SONET GigE GigE PE 2 PE 2 CE– –3 3 CE SONET SONET PE 1 PE 1 P SONET SONET P P P PE 3 PE 3 PE 4 CE– CE –5 5 PE 4 GigE GigE CE– CE –4 4 CE– –6 6 CE Gig Ethernet port VPN A SONET port VPN B SONET port VPN A The basic unit of the OVPN service is an optical or TDM connection between a pair of CEs, or to be more precise, between a port on one CE and a port on another CE.

OVPN – Customer’s view CE– –2 2 CE CE– CE –1 1 SONET SONET P P P P SONET SONET SONET SONET PE ONE 2 PE ONE 2 GigE GigE CE– –3 3 CE SONET SONET PE ONE 1 PE ONE 1 P SONET SONET P P P CE– CE –5 5 GigE GigE CE CE– –4 4 CE– –6 6 CE Gig Ethernet port VPN A (CE-6 and CE-3) SONET port VPN A (CE-5 and CE-3) SONET port VPN B (CE-1 and CE-2, CE2 and CE-4)

• Port-based scope. • S ome similarities between OVPNs and layer-3/ 2 VPNs with respect to VPN constructs. • OVPN architectures should be built from IP related building blocks. • General Requirements (some requirements) – The OVPN service S HOULD provide support for a broad spectrum of OVPN topologies, such as hub-and-spoke, full mesh, arbitrary, etc. • S ervice Provider Network Requirements – To provide OVPN service that scales to a large number of customers, no single component of the service provider networks should be required to maintain all the information about all the OVPNs. – S implified provisioning (e.g., when adding/ deleting a port to/ from a given OVPN). • Customer Requirements – Overlapping addresses – Constrained/ restricted connectivity. – Privacy/ independence with respect to addressing and routing. See the draft for more requirements

Optical VPNs to be part of PPVPN charter.