1 / 11

Multi-Segment Pseudowire Setup & Maintenance using LDP draft-balus-mh-pw-control-protocol-02.txt

Multi-Segment Pseudowire Setup & Maintenance using LDP draft-balus-mh-pw-control-protocol-02.txt. Authors David McDysan (MCI), Mike Duckett (Bellsouth), Yeongil Seo (Korea Telecom), Yuichiro Wada (NTT Communications). Andy Malis (Tellabs), Chris Metz (Cisco),

quemby-dale
Download Presentation

Multi-Segment Pseudowire Setup & Maintenance using LDP draft-balus-mh-pw-control-protocol-02.txt

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. Multi-Segment Pseudowire Setup & Maintenance using LDPdraft-balus-mh-pw-control-protocol-02.txt Authors David McDysan (MCI), Mike Duckett (Bellsouth), Yeongil Seo (Korea Telecom), Yuichiro Wada (NTT Communications) Andy Malis (Tellabs), Chris Metz (Cisco), Paul Doolan (Mangrove), Ping Pan (Hammerhead), Prayson Pate (Overture), Vasile Radoaca (Consultant) Florin Balus, Mike Loomis, Jeff Sugimoto (Nortel)

  2. Key Principles – draft-balus-mh-pw… • Develop MS-PW Solution as a Super Set of SS-PW procedures • SS-PW, VPLS Implementations, Deployments based on LDP Signaling • Re-use Signaling Procedures, Current Addressing • Operational Consistency, Familiarity with SS-PWs • Same Service Management, Provisioning Models... • OSS Touches at only U-PEs • Add Minimal Changes to satisfy the MS-PW Requirements • Easily applicable to existing LDP-VPLS Implementations Extend existing PW Signaling Protocol

  3. MS PW Requirements Addressed • Dynamic Creation of MS-PW • IP addressing but encoding supports other address types (e.g., NSAP, IPv6) • Same Forward and Reverse Path… • Automatic Determination of intermediate S-PEs • S-PE_hop-by-S-PE_hop selection based on regular IP Routing Procedures • Minimal OSS “touches” - at only U-PE(s) • Supports A/D, single or double sided provisioning as per draft-ietf-l2vpn-signaling • Operational Consistency with SS-PW • Support for both L2FECs • Signaling of Quantity and Quality of Service • Resiliency Procedures • Supports OAM capability negotiation

  4. Provisioning Fault Accounting Billing MS-PW Operational Consistency with SS-PWsRe-use of Existing Information Model, OAM Procedures for SS-PW Service Provisioning Service Instance: (AGI, SAII, TAII) Remote Peer: PE Loopback PW LDP PE 1 PE 2 VF VF U-PE 1 S-PE U-PE 2 SP VF VF MS PW LDP LDP Service Provisioning Service Instance: (AGI, SAII, TAII) Remote Peer: U-PE Loopback

  5. LSPa12 = (IP1, L2FEC, IP2) PWa LSPa21 = (IP2, L2FEC, IP1) PW Information Model – [PW Control] LDP PE 1 PE 2 VFx VFy • Unique Endpoint ID • “Prefix 1, AI x” – [PW Ctrl] • Unique Endpoint ID • “Prefix 2, AI y” – [PW Ctrl] Originator PE: Destination PE is one “E-LDP hop” away Receiving PE: Source U-PE Prefix derived from local E-LDP Session

  6. LSPa12 = (IP1, L2FEC, IP2) MS-PWa LSPa21 = (IP2, L2FEC, IP1) • Unique Endpoint ID • “Prefix 1, AI x” – [PW Ctrl] • Unique Endpoint ID • “Prefix 2, AI y” – [PW Ctrl] MS-PW Information Model SS-PW SS-PW U-PE 1 S-PE U-PE 2 SP VFx VFy S-PE LDP LDP Originator (U-)PE: Destination PE is more than one “E-LDP hop” away Receiving NE: Source (U-)PE Prefix can not be derived from local LDP Session Solution: U-PE Prefixes to be carried in the Signaling Messages

  7. SAII TAII How to carry sU-PE, dU-PE Prefixes?Two possibilities, orthogonal to the procedures described in the draft 1’. Use the Generalized ID - PW FEC 129 Complete Address Information in one TLV FEC TLV Label TLV • Source U-PE “Prefix” – Identifies the Originating U-PE • Allows peer discovery or verification • Destination U-PE “Prefix” – Identifies the Remote U-PE • Enables S-PE to automatically determine Next “PW Segment” Other TLVs …. MS PW TLV 1. Use a Separate MS-PW TLV Accommodates also PW FEC 128 (PWID) Implementations Ready to mandate implementation of PW FEC 129 for MS-PWs? Ready to start assigning AII Types – see draft-metz-aii-aggregate?

  8. 4. On receipt of the LM: use destination U-PE to find the next signaling hop. 30. 22. 5. SS-PWb LSP Fwd 3. SS-PWa LSP Fwd 7. SS-PWb LSP Rev 8. SS-PWa LSP Rev • Reverse Path Signaled through previously used LDP Sessions • To guarantee Bi-directionality of individual PW Segments MS PWs using E2E LDP Signaling – Operational WalkthroughHighlighting only the Steps Specific to MS PW • 1b. U-PE2 is provisioned with • AGI = 40, SAII=100, TAII=200 • Destination PE = IP1 • 1. U-PE1 is provisioned with • AGI = 40, SAII=100, TAII=200 • Destination PE = IP2 6. On receipt of the LM: check Destination U-PE = itself. Verify Source Address against provisioned Destination U-PE. 2. U-PE1 Use dU-PE to find next signaling hop. U-PE2 U-PE1 S-PE1 P P P LDP1 LDP2

  9. Related Procedures • Determining Next Signaling Hop • Static Provisioning - Default Gateway/Summarized Prefixes • BGP AD - See [L2VPN SIGN] Procedures for LDP-VPLS • QoS TLVs may be included in the Signaling Message • TSPEC format for Quantity Of Service, DiffServ TLV for Quality of Service • CAC Executed Against the Tunnel to Originator of the Local LDP Session • Resiliency • Re-routing around Failure • OAM Negotiation • End-to-end Capability Negotiation between U-PEs – VCCV Ping, BFD

  10. Next Steps • Do we still need support in the Information Model for PW FEC 128? • PW Protection Options (e.g. 1:1)

  11. Summary – draft-balus-mh-pw… • Addresses the Signaling Requirements for MS-PWs • MS-PW Solution as a Super Set of SS-PW Procedures • Operational Consistency, Familiarity with SS-PWs • Minimal Changes to Existing PW Signaling • Easily Applicable to existing LDP-VPLS Implementations Make it a WG Draft

More Related