1 / 9

MPLS Carriage in Single PW: Goals & Requirements

Explore the goals and requirements for MPLS in a single PW, including decoupling control protocols, addressing overhead concerns, and distinguishing MPLS transport methods. Considerations and additional requirements for seamless integration are discussed.

kgrays
Download Presentation

MPLS Carriage in Single PW: Goals & Requirements

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. Generic PWs? { balus, bryant, mcpherson, pan, stein }

  2. Carriage in single PW… • MPLS (below bottom label) • IPv4 • IPv6 • Compressed header (TCP/UDP/RTP)? • IS-IS • Another PW • Other?

  3. Network Topology T-PE T-PE IP(v4,v6),IS-IS,MPLS,OAM over PW S-PE S-PE Applicability: Carrier of Carrier, Access Gateway to Service PoP Gateway

  4. Goals & Requirements • Decouple control protocols from that of the SP (SP and customer don’t want to integrate MPLS signaling protocols - e.g., LDP) • Can’t always employ PW type associated with AC type: • Overhead (payload & state, e.g., PPP) • Interworking w/different AC types • Undefined AC types

  5. Goals & Requirements (cont) • Distinguish MPLS carried in PWs from classical MPLS • Implications/Considerations of PW CW and ECMP • MPLS relies on IP for signaling, can’t ignore bootstrapping function

  6. Additional Consideration • CW always required (e.g., Always use 0000 nibble for data, VCCV indicated as usual) • SS & MS considerations • L2VPN requirements (IPLS)

  7. Extraneous Considerations • ITU move to divorce MPLS from IP and replace with perhaps PNNI (George?) • MPLS Forum UNI w/RSVP (GMPLS-only)? • L2TPv3 (have IP PW today) • L2VPN requirements

  8. Payload Considerations • Self-describing payload • How? • Registry • PPP • EtherType • New?

  9. Request to make WG item • Applicability/requirements ID • Arch/framework ID • Protocol Work..

More Related