1 / 7

Why Carriers Like Pseudowires…

Why Carriers Like Pseudowires…. A type of “ virtual circuit ” : on top of all Layer-2, below Layer-3 (IP) A point-to-point connection that carries packets, cells or bit streams Uses MPLS control plane to provision data flows Works over legacy as well as low-cost Metro Ethernet

britain
Download Presentation

Why Carriers Like Pseudowires…

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. Why Carriers Like Pseudowires… • A type of “virtual circuit”: on top of all Layer-2, below Layer-3 (IP) • A point-to-point connection that carries packets, cells or bit streams • Uses MPLS control plane to provision data flows • Works over legacy as well as low-cost MetroEthernet • Future-proofedagainst ‘next big thing’ in access • Suitable for Service Convergence • Utilizes current access assets User Applications Payload (IP, L2 data, voice) PseudoWires Layer-2 (Ethernet, ATM…) Physical (Optical, Wireless) Payload (IP, L2 data, voice) PseudoWires Layer-2 (Ethernet, ATM…) Physical (Optical, Wireless) Convergence Layer-2 Service Layer-1 Transport

  2. User 1 User 2 CPE CPE Making a Service out of Pseudowires • Flexibility • Multiplex traffic from all access infrastructure • QoS guarantees at fine granularity • Sustain per-flow QoS after aggregation • Support delay-sensitive traffic • Edge-to-edge OAM • Support MPLS-Ethernet/ATM OAM Mapping • RapidProtection & Restoration • Recovery from failures in msec’s • Support Multiple Control-Planes • MPLS, Ethernet, ATM… • Easy to Manage • Compatible with backbone’s MPLS control-plane • Cost Effective • Remove unnecessary IP functions • Equipment Requirements • Process at Pseudowire-level (e.g. switching) • No need to carry Layer-2 traffic with Layer-3 gear IP Routing Pseudowires Data Aggregation Switch Layer-2 Flows

  3. Tunnel Label 100 Tunnel Label 100 Data Data Data Data Data Data Access Access Core PW Label 1000 PW Label 2000 Draft-Martini: Originally Designed as Generic Encapsulation for Routers User 1 Pseudowire for User 1 User 2 Pseudowire for User 2 MPLS Tunnel IP Routing (Needed to setup MPLS Tunnels) MPLS Tunnels Pseudowires

  4. Tunnel Label 300 Tunnel Label 200 Tunnel Label 100 Tunnel Label 100 Tunnel Label 300 Tunnel Label 200 Data Data Data Data Data Data Data Data Data Data Access Access Edge Edge Core PW Label 1000 PW Label 2000 PW Label 2000 PW Label 1000 PW Label 2000 PW Label 1000 Draft-Martini:In Practice, Requires IP Routing and Routers Everywhere User 1 Pseudowire for User 1 User 2 Pseudowire for User 2 MPLS Tunnel MPLS Tunnel MPLS Tunnel IP Routing IP Routing IP Routing MPLS Tunnels MPLS Tunnels MPLS Tunnels Pseudwires Pseudowires Pseudowires

  5. Tunnel Label 100 Tunnel Label 100 Data Data Data Data Data Data Data Data Data Data Access Access Edge Edge Core PW Label 2000 PW Label 2000 PW Label 1000 PW Label 2000 PW Label 1000 PW Label 1000 Dry-Martini:Provide Data Multiplexing, Simplify Network Access User 1 Pseudowire for User 1 User 2 Pseudowire for User 2 MPLS Tunnel IP Routing MPLS Tunnels Pseudowires Pseudowires Pseudowires

  6. proxy How does Dry-Martini Work? (Option 3) Setup PW’s via out-of-band Net-1 CPE/MSPP/PON Edge Switch Any Access Infrastructure Net-2 Access Network Connection • Insert a label per flow • Label: MPLS or VLAN • Look uplabel • & forward (Option 1) Peer-to-peer Target LDP (Option 2) Lightweight PW UNI

  7. Impact of Dry-Martini • IP Router is overkillfor data access • Support of draft-martini needs IP routing (to setup MPLS tunnels) • With dry-martini, no need for full IP/MPLS stack on access devices • Access devices can be cheap and simple • Just insert labels to data flows • Control plane can be as simple (or fancy) as you want • Access device can aggregate data flows with minor add-on for packet forwarding • Introduce cost reduction for access devices: • EPON, GPON • CPE • MSPP • Edge switch needs not to be a “God Box” • Aggregate user flows toward IP routers for VPN services… • Support PWE3 and some basic MPLS features • But needs to be very good at QoS, OAM and per-port cost

More Related