1 / 9

Point-to-Multipoint Pseudo-Wire Encapsulation draft-raggarwa-pwe3-p2mp-pw-encaps-00.txt

Point-to-Multipoint Pseudo-Wire Encapsulation draft-raggarwa-pwe3-p2mp-pw-encaps-00.txt. R. Aggarwal (Juniper). What is a P2MP PW ?.

garron
Download Presentation

Point-to-Multipoint Pseudo-Wire Encapsulation draft-raggarwa-pwe3-p2mp-pw-encaps-00.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. Point-to-Multipoint Pseudo-Wire Encapsulationdraft-raggarwa-pwe3-p2mp-pw-encaps-00.txt R. Aggarwal (Juniper)

  2. What is a P2MP PW ? • A Point-to-Multipoint (P2MP) Pseudo Wire (PW) is a mechanism that emulates the essential attributes of a unidirectional P2MP Telecommunications service such as P2MP ATM over a Packet Switched Network (PSN). • Chartered in PWE3 WG • draft-ietf-pwe3-p2mp-pw-requirements

  3. Motivation • This document describes the encapsulation and data plane procedures for a P2MP PW. • These procedures are meant to be independent of the control plane or provisioning system used to signal/configure a P2MP PW • The control plane may be based on BGP • draft-raggarwa-l2vpn-p2mp-pw • The control plane may be based on LDP • draft-jounay-niger-pwe3-source-initiated-p2mp-pw • A provisioning system may be used instead of a control plane • Anything static seems to be in fashion these days

  4. Historical Context of the Draft • Comparison with draft-raggarwa-l2vpn-p2mp-pw-00.txt and draft-raggarwa-l2vpn-p2mp-pw-01.txt • Version 0/1 specified VPMS service definition • Now specified in draft-ietf-l2vpn-vpms-frmw requirements • Version 0/1 specified P2MP PW encapsulation and forwarding • Now specified in draft-raggarwa-pwe3-p2mp-pw-encaps • Version 0/1 specified BGP based VPMS A-D and P2MP PW signaling • Retained in draft-raggarwa-l2vpn-p2mp-pw-02.txt

  5. P2MP PW Semantics • A P2MP PW enables a root CE to send traffic to leaf CEs over a P2MP PSN • A root CE in a sender site sends traffic on one or more ACs to the root PE • The root PE delivers this traffic over a P2MP PW to one or more leaf PEs • Each leaf PE in turn delivers this traffic to one or more leaf CEs in a receiver site • A particular leaf CE may receive traffic from multiple sender CEs. • Traffic from different sender CEs is received by a leaf PE over unique P2MP PWs.

  6. Carrying P2MP PWs in P2MP PSN Tunnels • Its an architectural building block that state maintained by routers not directly connected to P2MP PW Attachment Circuits (ACs) does not grow linearly with the number of ACs • To achieve the above P2MP PWs must be carried over P2MP PSN Tunnels • P2MP PSN Tunnels MUST be signaled using P2MP RSVP-TE or P2MP LDP • Egress PEs MUST NOT advertise IMPLICIT NULL or EXPLICIT NULL for P2MP PSN Tunnels that are used to carry P2MP PW traffic.

  7. P2MP PW De-multiplexor • A P2MP PW de-multiplexor allows an egress PE to determine in the data plane, the P2MP PW for which the packet is intended. • MPLS upstream assigned labels as per RFC 5331 MUST be used as the P2MP PW de-multiplexor • MUST be assigned by the ingress PE and distributed to the egress PEs • The ingress PE MUST use this label as the bottom-most label while encapsulating a customer data packet in a P2MP PW. • Each of the egress PEs must be able to associate this inner label with the same P2MP PW and use it to de-multiplex the traffic received over the P2MP PSN tunnel

  8. P2MP PW Encapsulation • PW encapsulation types specified in RFC 4446 must be used • Encapsulation methods used in transporting of Layer 2 frames over tunnels must be the same as described in [RFC4448], [RFC4618], [RFC4619], and [RFC4717]. • May result in inserting a control-word in the P2MP PW encapsulation • Layer 2 MTU configured on all the access circuits connecting the CEs to PEs, for a given P2MP PW MUST be the same.

  9. De-multiplexing Procedures • De-multiplexing at the egress PEs • One P2MP PW to one P2MP LSP mapping • P2MP LSP label is sufficient to determine the P2MP PW and forward the packet • Multiple P2MP PWs to one P2MP LSP mapping • The P2MP LSP label determines the context table in which to look up the upstream assigned P2MP PW label • The P2MP PW label lookup determines the P2MP PW

More Related