Transcript PPT Version
draft-jounay-pwe3-p2mp-pw-requirements-00.txt IETF 68 PWE3 Working Group Prague, March 2007 F. Jounay, P. Niger, France Telecom Y. Kamite, NTT Communications S. Delord, Uecomm L. Wang,Telenor L. Martini, Cisco Corp. G. Heron, Tellabs Motivation Identified applications that would be better addressed by a P2MP PW rather than by n x P2P PWs Necessity to collect requirements for P2MP PW definition This draft aims at describing First the needs, i.e. identified use cases Secondly the requirements for • the setup and maintenance of P2MP PW • the security, scalability, etc Today the PWE3 WG charter is limited to P2P PW "A pseudowire emulates a point-to-point link over an IP/MPLS network, and provides a single service which is perceived by its user as an unshared link or circuit of the chosen service." Use Cases for P2MP PW TDM-based Use Cases Adaptive Clock Distribution and Recovery E.g: Mobile backhauling, n stations to be synchronized from the controller • 1 P2MP TDM PW rather than n P2P TDM PW Pros: Provisioning, "VoIP-like traffic" bandwidth savings ATM-based Use Cases Broadcast TV over ATM E.g.: Wholesale services over an IP/MPLS network addressing ATM-based endpoints (source and destinations), e.g. ATM based DSLAMs • 1 P2MP ATM PW rather than n P2P ATM PW Pros: Bandwidth savings, dynamic "P2MP ATM circuit" Ethernet-based Use Cases Broadcast TV over Ethernet VPWS instead of VPLS (VPLS already addressed in [VPLS MCAST REQ]) E.g.: Wholesale services requires NSP transparency wrt IP customer's layer • VPWS P2MP: Cross-connect mode (Use of P2MP PW, without VSI features) Pros: Bandwidth savings P2MP PW framework (1/2) Point-to-Multipoint SS-PW PW over P2MP LSP • Source or Leaf-initiated • PW Upstream Label Assignment P2MP PW framework (2/2) Point-to-Multipoint MS-PW PW segment over P2P LSP (Downstream Label Assignment) PW segment over P2MP LSP (Upstream Label Assignment required) To be discussed TOC of the V00 1. Introduction 5. P2MP MS-PW Requirements 1.1. Problem Statement 5.1. P2MP MS-PW Pseudowire Reference Model 1.2. Scope of the document 5.2. P2MP SS-PW Underlying Layer 2. Definition 5.3. P2MP MS-PW Signaling Requirements 2.1. Acronyms 5.3.1. PW Addresses Routing 2.2. Terminology 5.3.2. P2MP MS-PW Setup Mechanisms 3. Use Cases for P2MP PW 3.1. TDM-based Use Case 3.2. ATM-based Use Case 3.3. Ethernet-based Use Case 3.3.1. P2MP PW for VPLS 3.3.2. P2MP PW for Ethernet-based VPWS 5.3.3. Leaf Grafting / Pruning 5.3.4. Explicit Routing 5.4. Failure Reporting 5.5. Protection and Restoration 5.6. Advertisement of P2MP Capability 5.7. Scalability 4. P2MP SS-PW Requirements 5.8. Order of Magnitude 4.1. P2MP SS-PW Reference Model 6. Manageability considerations 4.2. P2MP SS-PW Underlying Layer 7. Backward Compatibility 4.3. P2MP SS-PW Signaling Requirements 8. Security Considerations 9. IANA Considerations 4.3.1. P2MP SS-PW Setup Mechanisms 4.3.2. Leaf Grafting / Pruning 4.4. Failure Reporting and Processing 4.5. Advertisement of P2MP Capability 4.6. Scalability 4.7 Order of Magnitude Further Steps Any WG feedback welcome Interest for this work ? Comments on draft version 00 Other Use Cases, additional requirements : transfer plane, signaling, security, etc Solution drafts Two proposed versions of solution draft posted prior to the meeting • First versions, so opened for discussion • Example of procedures for leaf and source initiated P2MP PW set up Charter review ? Is a charter update necessary to work this new topic ? If yes is it possible to start work on this topic in parallel to a charter review ?