1 / 9

Matthew Bocci (Alcatel) Stewart Bryant (Cisco)

An Architecture for Multi-Segment Pseudo Wire Emulation Edge-to-Edge draft-bocci-bryant-pwe3-ms-pw-architecture-00.txt. Matthew Bocci (Alcatel) Stewart Bryant (Cisco). Objectives & Key Issues. Objectives Document the main network scenarios for MS-PW applicability

pascha
Télécharger la présentation

Matthew Bocci (Alcatel) Stewart Bryant (Cisco)

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. An Architecture for Multi-Segment Pseudo Wire Emulation Edge-to-Edgedraft-bocci-bryant-pwe3-ms-pw-architecture-00.txt Matthew Bocci (Alcatel) Stewart Bryant (Cisco) draft-bocci-bryant-ms-pw-architecture-00.txt

  2. Objectives & Key Issues • Objectives • Document the main network scenarios for MS-PW applicability • Define architectural framework: • Specify which protocol functions that we need • Key Issues • Applicability of MS-PWE3 vs. L2VPN • Protocol Layering Model • Network reference Models • PE Reference Model • Protocol Stack Reference Model • Gaps draft-bocci-bryant-ms-pw-architecture-00.txt

  3. U-PE U-PE MS-PW S-PE S-PE U-PE U-PE Applicability & Domain of MS PWE3 • A MS-PW is a single PW that for technical or administrative reasons is segmented into a number of concatenated hops. • From perspective of U-PE, MS-PW is indistinguishable from SS-PW. • MS-PW abstracts complex PWs from the construction of a L2VPN • PWE3 does not do: PSN tunnel setup, PSN tunnel maintenance and routing, U-PE discovery • PWE3 does do: S-PE selection to reach a U-PE draft-bocci-bryant-ms-pw-architecture-00.txt

  4. Protocol Layering Model • Same as RFC 3985 except: • Pseudo-wires may be considered to be a separate layer to the PSN tunnel. • Independent of the PSN tunnel routing, operations, signalling and maintenance. • Design of PW domains should not imply the underlying PSN routing domains are the same. • MS-PW will reuse protocols of the PSN draft-bocci-bryant-ms-pw-architecture-00.txt

  5. Network Reference Models • Intra-provider & inter-provider Native |<-----------Pseudo Wire----------->| Native Service | | Service (AC) | |<-PSN1-->| |<-PSN2-->| | (AC) | V V V V V V | | +----+ +-----+ +----+ +----+ | |UPE1|=========|SPE1 |=========|UPE2| | +----+ | |-------|....PW.Seg't1........PW Seg't3.....|----------| | | CE1| | | | | | | | | |CE2 | | |-------|....PW.Seg't2.......|PW Seg't4.....|----------| | +----+ | | |=========| |=========| | | +----+ ^ +----+ +-----+ +----+ ^ | Provider Edge 1 ^ Provider Edge 2 | | | | | | | | PW switching point | | | |<------------------- Emulated Service ------------------>| draft-bocci-bryant-ms-pw-architecture-00.txt

  6. PE Reference Model • Pre-processing in U-PEs as RFC 3985 • Processing in S-PEs: • No native service processing • Egress PW label mapping based on ingress label • Static or dynamic config • 1:1 mapping between ingress and egress PW +------------------------------------------+ | S-PE Device | +------------------------------------------+ Ingress | | | | Egress PW instance | Single | | Single | PW Instance <==========>X PW Instance + Forwarder + PW Instance X<==========> | | | | +------------------------------------------+ draft-bocci-bryant-ms-pw-architecture-00.txt

  7. Protocol Stack Reference Model Remove PSN1 demuxAdd PSN2 demuxApply policies +----------------+ +----------------+ |Emulated Service| |Emulated Service| |(e.g., TDM, ATM)|<======= Emulated Service =======>|(e.g., TDM, ATM)| +----------------+ +----------------+ | Payload | | Payload | | Encapsulation |<== Multi-segment Pseudo Wire ===>| Encapsulation | +----------------+ +--------+ +----------------+ |PW Demultiplexer|<PW Segment>|PW Demux|<PW Segment>|PW Demultiplexer| +----------------+ +--------+ +----------------+ | PSN Tunnel, |<PSN Tunnel>| PSN |<PSN Tunnel>| PSN Tunnel, | | PSN & Physical | |Physical| | PSN & Physical | | Layers | | Layers | | Layers | +-------+--------+ +--------+ +----------------+ | .......... | .......... | | / \ | / \ | +==========/ PSN \===/ PSN \==========+ \ domain 1 / \ domain 2 / \__________/ \__________/ `````````` `````````` draft-bocci-bryant-ms-pw-architecture-00.txt

  8. Other Issues • Control Plane: • Can be static or dynamic • Gaps in current version of the draft: • Maintenance reference model • Security issues draft-bocci-bryant-ms-pw-architecture-00.txt

  9. Conclusions • Architecture is fundamental to the solution • Would like to achieve consensus as early as possible • Please provide comments and text to improve the draft! draft-bocci-bryant-ms-pw-architecture-00.txt

More Related