Service Requirements for Optical VPNs - - PowerPoint PPT Presentation

“Service Requirements for Optical VPNs”

<draft-ouldbrahim-ovpn-requirements-00.txt>

51th IETF, London, August 2001

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)

OVPN Reference Model

CE4 CE6 CE5 CE7

OVPN B

CE1 CE3 CE2

OVPN A

PE1 PE4 PE2 PE3

P P P P

CE1 CE3 CE2 CE4 CE6 CE5 CE7

Service Provider Optical Network(s)

Service Provider Optical Network(s)

PE

CE CE CE

Optical VPN Network Reference Model

VPN D VPN D

OVPN C OVPN C

PE1 P P P P PE2

L 2 V P N A

PE4 PE3

OVPN A OVPN B

L3VPN-1 L3VPN-2 OVPN D OVPN D CE CE L2VPN B L2VPN A L2VPN B CE CE

OVPN A

L3VPN-1 L3VPN-2

Example: A CE for OVPNA Example: A CE for OVPNA A PE for layer A PE for layer-

• 3 VPN 1,2

3 VPN 1,2 (RFC2547, VR) (RFC2547, VR)

CE CE Ethernet

SONET/SDH Router

OVPN B

P P P P P P

PE 2 PE 2 PE 1 PE 1 CE CE– –1 1 CE CE– –5 5 CE CE– –4 4 CE CE– –2 2 CE CE– –3 3

P P

Optical VPN Service - Example

SONET SONET SONET SONET SONET SONET

PE 3 PE 3

SONET SONET GigE GigE

PE 4 PE 4

SONET SONET GigE GigE

Gig Ethernet port VPN A SONET port VPN A SONET port VPN B

CE CE– –6 6

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.

P P P P P P

PE ONE 2 PE ONE 2 PE ONE 1 PE ONE 1 CE CE– –1 1 CE CE– –5 5 CE CE– –4 4 CE CE– –2 2 CE CE– –3 3

P P

OVPN – Customer’s view

SONET SONET SONET SONET SONET SONET SONET SONET GigE GigE SONET SONET GigE GigE

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)

CE CE– –6 6

• Port-based scope.
• S
• me 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.