1 / 7

Signaling: Identifying PW Endpoints

This article explores PWE3 signaling in PPVPN provisioning, focusing on identifying and connecting forwarders using the Martini signaling framework. It discusses the current limitations and proposes solutions for VPLS, Distributed VPLS, VPWS Full Mesh, and Switched Connections. The goal is to generalize the method of identifying remote forwarders and improve the flexibility and scalability of PPVPN provisioning.

aliceallen
Download Presentation

Signaling: Identifying PW Endpoints

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Signaling: Identifying PW Endpoints • L2VPNs can be built over PWE3 PseudoWires • L2VPN/PWE3 framework: signaling connects two “Forwarders”. • “Martini signaling”: to connect 2 Forwarders by a PW: • Provision a 32-bit “name” (VCid) • Configure each Forwarder with VCid • Each Forwarder independently initiates unidirectional LSP

  2. Problem • Presupposes provisioning model • each PW individually provisioned at each PE device • No support for many PPVPN provisioning models • No integration with L2VPN auto-discovery • Solution: • Generalize method of identifying remote Forwarder • Allow either Forwarder to be the initiator, the other to be the responder

  3. Example 1: VPLS • Forwarders id’ed by VPN-id • Current VPLS proposals reuse “Martini” VCid field as VPN-id • Problem: 32-bit VCid field just too short, esp. inter-provider : • All VPN-id proposals use 7-8 bytes, some use arbitrarily long strings • Current proposals not viable in long term

  4. U-PE N-PE U-PE N-PE 2: Distributed VPLS • Provisioning model: • U-PE learns # of PWs it needs per VPLS • N-PE learns # of PWs per VPLS per remote N-PE and per local U-PE • Cannot be done with just VCid or VPN-id

  5. 3: VPWS Full Mesh “Colored Pools” • Provisioning model: • Assign a VPN-id • Number CEs from 1-n • For each CE, set up n PWs, such that PWk leads to CEk • Cross-connect so PWk from CEj matches PWj from CEk • Identifier must include VPN-id, local CE number, remote CE number

  6. 4: Switched Connections • E.g., connecting ATM SVC to PW • PW setup must be initiated from one side, not from both • Remote endpoint identifier must include addressing information

  7. Going Forward • Ensure PWE3 signaling is general enough for PPVPN use (PWE3 draft?) • Specify use of PWE3 signaling for various provisioning models (PPVPN draft?)

More Related