MPLS IN THE AGGREGATION 2.0

Size: px

Start display at page:

Download "MPLS IN THE AGGREGATION 2.0"

Claud Quinn
6 years ago
Views:

1 MPLS IN THE AGGREGATION 2.0 Bruno De Troch Tech Lead Access and Aggregation Solutions EMEA NNTF - September 2012

2 AGENDA Market Drivers to modify the Aggregation Design Architectural Choices for Access and Aggregation Seamless MPLS Concepts Seamless MPLS Implementation Details Location and flexibility of Service Nodes 2 Copyright 2012 Juniper Networks, Inc.

3 MARKET DRIVERS

MARKET DYNAMICS UNPRECEDENTED TRAFFIC GROWTH Worldwide internet

100,000 80,000 60,000 # of Connections Source: Juniper, Cisco,

net 20,000 Forecast Model +27% 2008-2020 CAGR Cloud computing,

Mobile BB access 2008-2020 WWW is born Need to accelerate

service delivery costs Digital decade Service delivery platforms

efficient OSS/BSS integration Outsourcing application

streaming and download Targeted online ad revenue CDN Managed

4 MARKET DYNAMICS UNPRECEDENTED TRAFFIC GROWTH Worldwide internet traffic, PB/month 180, , , , ,000 80,000 60,000 # of Connections Source: Juniper, Cisco, MINTS 4 Copyright 2012 Juniper Networks, Inc. 20,000 Forecast Model +27% CAGR Cloud computing, PaaS, SaaS Mobile advertising 17x Network outsourcing Growth Mobile BB access WWW is born Need to accelerate service velocity and add value for subscribers while reducing service delivery costs Digital decade Service delivery platforms w/ common set of capabilities enabling deployment flexiblity and efficient OSS/BSS integration Outsourcing application development Service mix evolving: Home networking Video streaming and download Targeted online ad revenue CDN Managed telepresence MACHINE TO MACHINE? +32% Video +20% Non-video 40,

6 METRO ARCHITECTURAL CHOICES

7 SERVICE PROVIDER METRO CHOICES OSS/BSS IMS Web Services AAA + Policy and Resource Control Residential?-2 IP Service Edge Wireless?-1 Internet Business Access Aggregation / /Metro Core Data Center 7 Copyright 2012 Juniper Networks, Inc.

8 ?-1 WHAT TECHNOLOGY TO USE IN AGGREGATION? Some Requirements Multi-Service: Multi-Play, Legacy, Mobile, Optimized for Multicast: IPTV, Business, Gaming, Flexibility: Add nodes, services, capacity, High Performance: Under varying conditions, Resilience: Redundancy, Convergence, Scalable: Throughput, Nodes, MACs, IPs, VCs, Manageable: OAM Protocols and Tools Standardized and open interfaces + Optimized for cost (Capex + Opex) 8 Copyright 2012 Juniper Networks, Inc.

9 WHY MPLS? Flexibility Services (L2 and L3, Virtualization ) Topology (Any, Traffic Engineering ) Consistent Framework Scalability Standardization Rich OAM Toolkit 9 Copyright 2012 Juniper Networks, Inc.

10 SERVICES CONVERGENCE Offers a converged and combinable services framework Ethernet Services IP Services Legacy Services Multicast Legacy Ethernet IP [BGP, LDP] TDM FR/ATM L2VPN E-LINE E-LAN VPLS IP IPVPN [LDP, RSVP] MPLS Any L1/L2 10 Copyright 2012 Juniper Networks, Inc.

11 ?-2 WHERE SHOULD THE IP SERVICES EDGE BE? Location of the IP Edge depends on a number of critical elements Service requirements Number of central offices Existing network infrastructure Security costs / risks Operational expense structure Bandwidth costs General trend is a movement of the IP Edge closer towards the enduser In all cases, a centralized policy control is required 11 Copyright 2012 Juniper Networks, Inc.

FLEXIBILITY IN SERVICE EDGE LOCATION Multiple Business, Residential and Mobile apps across Ethernet aggregation Flexibility of Service Edge location required as services evolve Distribute or

16 FLEXIBILITY IN SERVICE EDGE LOCATION Multiple Business, Residential and Mobile apps across Ethernet aggregation Flexibility of Service Edge location required as services evolve Distribute or centralise Business Residential Data, VoIP Residential Video L3 VPN L2 P2P VPN L2 PMPVPN Layer 2 Backhaul & Aggregation Transport Infrastructure (MPLS LSPs) Signalling and Auto-discovery (BGP) Transport Infrastructure (MPLS LSPs) 16 Copyright 2012 Juniper Networks, Inc.

17 SEAMLESS MPLS

18 CONVERGENCE IN NETWORKING User s (Services) View Single Bill and Customer Care for multiple services Same services everywhere (Home, Hot Spots, Cellular) All services on all Terminals and Screens Seamless cross-domain mobility Operator s (Network) View Independence of Services from Network with seamless end-to-end implementation Converged Core Converged Edge Converged Access/Aggregation Converged Control Plane (AAA, IMS, Web services) Converged Data Centers 18 Copyright 2012 Juniper Networks, Inc.

19 GOAL: THE SERVICE CENTRIC NETWORK Converge networks Shared access/aggregation, edge and core infrastructure across all services Deliver appropriate and deterministic network SLAs (regardless of scale) Converge services Shared service delivery points across wireline and wireless services (FMC) Integrated profile and services (e.g. AAA) Enabler for service mobility and portability of user experience Reduce operational costs Simplify provisioning, management and troubleshooting Minimized number of service provisioning points Flexible topological placement of service delivery points Improve service velocity Reduce time to service, lower cost of new service intro, improve effectiveness of service delivery Decouple service and network architectures Enable new services and service delivery changes without altering network architecture Flexible service insertion points supporting time to market, scaling and evolution 19 Copyright 2012 Juniper Networks, Inc.

IMPLEMENTATION: SEAMLESS MPLS AS FOUNDATION FOR ONE CONVERGED NETWORK Decoupled network and service architectures Complete virtualization of network services Flexible topological placement of

20 IMPLEMENTATION: SEAMLESS MPLS AS FOUNDATION FOR ONE CONVERGED NETWORK Decoupled network and service architectures Complete virtualization of network services Flexible topological placement of services enabler for per service de-centralization Minimized number of provisioning points, simplified end-to-end operation Network Scale and End-to-End service restoration 100,000s of devices in ONE packet network Seamless service recovery from any failure event (Sub-50ms) Clients Access Aggregation Edge Core Data Center Seamless MPLS Networking at scale without boundaries 20 Copyright 2012 Juniper Networks, Inc.

21 SEAMLESS MPLS CONNECTIVITY BLUEPRINT Regions A single network divided into regions: multiple Metro regions (leafs) interconnected by WAN backbone (core) Regions can be of different types: (i) IGP area, (ii) IGP instance, (iii) BGP AS All spanned by a single MPLS network, with any to any MPLS connectivity blueprints (AN to SN, SN to SN, AN to AN, etc) Devices and their roles Access Nodes terminate local loop from subscribers (e.g. DSLAM, MSAN, CSR/HSR, enodeb) Transport Nodes packet transport within the region (e.g. Metro LSR, Core LSR) Border Nodes enable inter-region packet transport (e.g. ABR, ASBR) Service Nodes service delivery points, with flexible topological placement (e.g. IPVPN PE, S-GW, P-GW, CDN, CGN) Service Helpers service enablement or control plane scale points (e.g. Radius, BGP RR, MME, PCRF) End Nodes represent customer network, located outside of service provider network (e.g. UE) Decoupled architectures Services architecture defines where & how the services are delivered, incl. interaction between SNs and SHs Network architecture provides underlying connectivity for services Seamless MPLS Network EN AN SH SH SN SN TN TN BN TN TN BN TN TN AN EN Metro-1 Region WAN Backbone Region Metro-2 Region 21 Copyright 2012 Juniper Networks, Inc.

SEAMLESS MPLS SIMPLIFIED SERVICE DELIVERY Traditional CPE AN Access/ Aggregation PE PE Core PE AN - Access Nodes terminate local loop from subscribers TN - Transport Nodes packet transport within the

22 SEAMLESS MPLS SIMPLIFIED SERVICE DELIVERY Traditional CPE AN Access/ Aggregation PE PE Core PE AN - Access Nodes terminate local loop from subscribers TN - Transport Nodes packet transport within the region BN - Border Nodes enable inter-region packet transport SN - Service Nodes service delivery points EN - End Nodes represent customer network PE Access/ Aggregation AN CPE MPLS 1 MPLS 2 MPLS 3 Seamless EN AN Access/ Aggregation BN SN Core BN SN Access/ Aggregation AN EN One Converged Seamless MPLS Network Services Simplified Service Instantiation (single provisioning point per connection) 22 Copyright 2012 Juniper Networks, Inc.

JUNIPER S SEAMLESS MPLS ARCHITECTURE CONNECTIVITY AND SERVICES BLUEPRINT EN AN Seamless MPLS Network SH SH SN SN TN TN BN TN TN BN TN TN AN EN EN C AN Metro-1 Region WAN Backbone Region Basic

23 JUNIPER S SEAMLESS MPLS ARCHITECTURE CONNECTIVITY AND SERVICES BLUEPRINT EN AN Seamless MPLS Network SH SH SN SN TN TN BN TN TN BN TN TN AN EN EN C AN Metro-1 Region WAN Backbone Region Basic Pt-to-Pt Connectivity Services Pseudowire Metro-2 Region C AN EN EN C AN Centralized Business edge Pseudowire S SN L3 or L2 VPN Services Any2Any S SN Centralized Business edge Pseudowire C AN EN EN EN C AN C AN Pseudowire Pseudowire S SN S SN De-centralized residential edge De-centralized residential edge Content / hosted app. Services Any2Any Internet Access Services Any2Any SN SN Internet Network service provisioning and operation points: C S Connectivity provisioned by NMS or AAA L3/L3+ Services provisioned by NMS or AAA 23 Copyright 2012 Juniper Networks, Inc.

24 SEAMLESS MPLS IMPLEMENTATION DETAILS

25 JUNIPER "SEAMLESS" MPLS SERVICE AND NETWORK ARCHITECTURE Requirements addressed across the three main architectural dimensions (1) Scale enables 100,000s of devices in ONE PSN network Large network scale via MPLS LSP hierarchy and robust network protocol stack (IGP, BGP) No service dependency whatsoever all packet services supported Low-cost/low-end access devices accommodated natively without adding complexity (MPLS labels on demand) (2) E2E service restoration enables sub-50ms recovery from any event Service restoration made independent of scale, services and failure types Achieved with full coverage of local-repair mechanisms for sub-50ms restoration Deterministic for any failure domain size / radius (3) Pseudowire Headend Termination (PHT) virtualizing service access Flexible topological service placement enabled via MPLS PHT Virtualization of service access with tight integration of Ethernet, IP and MPLS Minimized number of provisioning points, simplifying service delivery and IT systems 25 Copyright 2012 Juniper Networks, Inc.

26 SEAMLESS MPLS SCALE (1) Design Split the network into regions: access, metro/aggregation, edge, core Single IGP with areas per metro/edge and core regions Hierarchical LSPs to enable e2e LSP signaling across all regions IGP + LDP/RSVP for intra-domain transport LSP signaling BGP Labeled Unicast for cross-domain hierarchical LSP signaling LDP Downstream-on-Demand for LSP signaling to/from access devices Static routing on access devices Properties Large scale achieved with hierarchical design BGP labeled unicast enables any-to-any connectivity between >100k devices no service dependencies (e.g. no need for PW stitching for base VPWS service) A simple MPLS stack on access devices (static routes, LDP DoD) 26 Copyright 2012 Juniper Networks, Inc.

27 SEAMLESS MPLS SCALE (2) EN "Seamless" MPLS Roles LDP DoD LDP Downstream on Demand, RFC5036 LDP DU LDP Downstream Unsolicited, RFC5036 BGP LU BGP Label Unicast, RFC3107 NHS BGP next-hop-self AN TN TN BN TN TN BN TN TN AN EN CPE AGN1 AGN2 ABR RR3107 LSR LSR ABR RR3107 AGN2 AGN1 CPE MPLS data plane Network Control Plane Static-Route + LDP-DoD ISIS-L1 + LDP-DU ISIS-L2 + LDP-DU ISIS-L1 + LDP-DU BGP-LU no NHS ABR RR NHS BGP-LU Pseudowire ABR NHS no NHS RR BGP-LU Static-Route + LDP-DoD Service Control Plane Data Plane push push PW-L LDP-L swap push PW-L BGP-L LDP-L swap PW-L BGP-L LDP-L swap (*) IP/MPLS control plane protocol stack and MPLS dataplane per Deployment Scenario #1 in draft-mpls-seamless-mpls 27 Copyright 2012 Juniper Networks, Inc. PW-L BGP-L LDP-L swap Targeted LDP PW-L BGP-L LDP-L pop Data flow PW-L BGP-L LDP-L swap push PW-L BGP-L LDP-L pop PW-L BGP-L LDP-L pop PW-L BGP-L pop PW-L

28 LDP DOWNSTREAM-ON-DEMAND (1) IP/MPLS routers implement LDP Downstream Unsolicited (LDP DU) label distribution Advertising MPLS labels for all routes in their RIB This is very insufficient for Access Nodes Mostly stub nodes, can rely on static routing and need reachability to a small subset of total routes (labels) AN requirement addressed with LDP DoD LDP DoD enables on-request label distribution ensuring that only required labels are requested, provided and installed LDP DoD is described in RFC5036 But not widely available in IP/MPLS routers apart from MPLS over ATM/FR This is being fixed now 28 Copyright 2012 Juniper Networks, Inc.

LDP DOWNSTREAM-ON-DEMAND (2) 1 AN: provisioned static routes 2 AGN1: provisioned static routes 3 AGN1: statics redistributed into IGP (optional) and LDP-DU 4 AGN1: statics redistributed into BGP-LU 5

29 LDP DOWNSTREAM-ON-DEMAND (2) 1 AN: provisioned static routes 2 AGN1: provisioned static routes 3 AGN1: statics redistributed into IGP (optional) and LDP-DU 4 AGN1: statics redistributed into BGP-LU 5 AN: LDP DoD lbl mapping requests for FECs associated with /32 static routes and configured services using /32 routes matching default route(*) 6 AGN1: LDP DoD lbl mapping requests for static route /32 FECs DSLAM OLT DSLAM OLT Static routes: 0/0 default /32 destination Static route: /32 AN loopback LDP DoD LDP DoD Label Distribution Protocol, Downstream on Demand distribution, RFC5036 LDP DU Label Distribution Protocol, Downstream Unsolicited distribution, RFC5036 BGP LU Border Gateway Protocol, Label Unicast extensions, RFC Copyright 2012 Juniper Networks, Inc AGN1b AGN1b 3 4 AGN2a AGN2b IP/MPLS Network IGP (ISIS,OSPF) LDP DU (*) Requires LDP support for longest match prefix in RIB (in addition to the exact match) as per RFC ibgp LU IGP LDP DU ABRa ABRb IP/MPLS Backbone

30 BGP LABELED UNICAST (RFC3107) BGP-LU enables distribution of /32 router loopback MPLS FECs Used between Seamless MPLS regions for any2any MPLS reachability Enables large scale MPLS network with hierarchical LSPs Not all MPLS FECs have to be installed in the data plane Separation of BGP-LU control plane and LFIB Only required MPLS FECs are placed in LFIB E.g. on RR BGP-LU FECs with next-hop-self E.g. FECs requested by LDP-DoD by upstream Enables scalability with minimum impact on data plane resources use what you need approach 30 Copyright 2012 Juniper Networks, Inc.

31 SEAMLESS MPLS E2E SERVICE RESTORATION (1) Design IP-FRR(LFA)/TE-FRR for local-repair of transit MPLS link and node failures LSP tail-end protection for egress PE node failures (IP, L3VPN, L2VPN, BGP-LU, RR-NHS) Optimized global-repair as fall-back if local-repair not feasible (e.g. no LFA cover) Note: LFA cover can be extended with RSVP-TE BGP PE-CE link local-repair protection for BGP edge link failures (IP, L3VPN, L2VPN, BGP3107) Properties Local-repair for all PE access links, PE and P nodes Local-repair for all PE/P transit links, topology independent (albeit certain topologies may introduce increased complexity e.g. RSVP-TE if no LFA coverage) E2E restoration in O(50ms) achievable, regardless of network and service scale 31 Copyright 2012 Juniper Networks, Inc.

32 SEAMLESS MPLS E2E SERVICE RESTORATION (2) Local-repair Based on the pre-computed local backup forwarding state - provides sub-50msec restoration Global-repair Requires signaling to take place after failure detection - can provide sub-1sec or longer restoration times link break, local-repair start local repair stop global repair start Local-repair complements Global-repair Local-repair keeps traffic flowing while Global-repair gets things right Variation of Make before break global repair stop 20-50ms ms 32 Copyright 2012 Juniper Networks, Inc.

SEAMLESS MPLS E2E SERVICE RESTORATION (3) Ingress: CE-PE link, PE node failure ECMP, LFA Transit: PE-P, P-P link, P node failure LFA based

node failure (new)(*) LSP tailend protection with context label lookup on the backup PE Failure repaired locally by adjacent P router using

and service scale This provides network layer failure transparency to service layers, becoming a major enabler for network consolidation (*)

33 SEAMLESS MPLS E2E SERVICE RESTORATION (3) Ingress: CE-PE link, PE node failure ECMP, LFA Transit: PE-P, P-P link, P node failure LFA based on IGP/LDP; if no 100% LFA coverage, delta with RSVP-TE RSVP-TE FRR Egress: PE-CE link failure BGP PE-CE link local protection Egress: PE node failure (new)(*) LSP tailend protection with context label lookup on the backup PE Failure repaired locally by adjacent P router using LFA (or TE-FRR) Packet based networks finally can provide E2E service protection similar to SDH 1:1 protection, regardless of network size and service scale This provides network layer failure transparency to service layers, becoming a major enabler for network consolidation (*) High Availability for 2547 VPN Service, Y.Rekhter, MPLS&Ethernet World Congress, Paris Copyright 2012 Juniper Networks, Inc.

SEAMLESS MPLS E2E SERVICE RESTORATION (4) Route Flow Traffic Flow Primary path Backup path CE3 PE11 P1 P2 PE21-PLR X CE1 PE12 Choices for handling egress PE-CE link failure Use vrf-table-label to

34 SEAMLESS MPLS E2E SERVICE RESTORATION (4) Route Flow Traffic Flow Primary path Backup path CE3 PE11 P1 P2 PE21-PLR X CE1 PE12 Choices for handling egress PE-CE link failure Use vrf-table-label to force IP lookup on egress PE Use PE-CE link protection for any label allocation mode PE22 PE-CE link protection (local-repair) Core facing nexthop(s) installed in FIB as alternate (backup) for CE facing routes Upon local PE-CE failure FIB in-place modification of CE routes to use alternate nexthop(s) Support for both BGP uni-path and multi-path P3 P4 CE2 34 Copyright 2012 Juniper Networks, Inc.

SEAMLESS MPLS E2E SERVICE RESTORATION (5) Route Flow Traffic Flow Primary path Backup path CE3 PE11 P1 P2-PLR PE21 X CE1 CE2 PE12 P3 P4 PE22 Requires protecting service (or LSP) endpoint (PE21) PLR

35 SEAMLESS MPLS E2E SERVICE RESTORATION (5) Route Flow Traffic Flow Primary path Backup path CE3 PE11 P1 P2-PLR PE21 X CE1 CE2 PE12 P3 P4 PE22 Requires protecting service (or LSP) endpoint (PE21) PLR (P2) does not hold any service state Protecting failed node requires PLR to divert the outer (transport) LSP to another (backup) node (PE22) Backup edge node needs to be able to interpret labels allocated by primary edge node 35 Copyright 2012 Juniper Networks, Inc.

36 SEAMLESS MPLS E2E SERVICE RESTORATION (6) Route Flow Traffic Flow Primary path Backup path CE3 PE11 P1 P2-PLR PE21-primary X CE1 LSP tailend protection PE12 Backup PE22 maintains a mirror image of primary PE21 service label table a context specific label space identified by virtual loopback configured on both primary and backup Primary owns the loopback, advertising it in Next_Hop attribute (virtual loopback is never used for control plane peerings) In case of primary failure, PLR (P2) diverts traffic destined to the virtual loopback to backup using IPFRR LFA or TE- FRR procedures Backup PE22 looks up received packets in the label table specific to primary PE21 (identified by virtual loopback), and forwards to the right destination 36 Copyright 2012 Juniper Networks, Inc. P3 P4 PE22-backup CE2

37 PSEUDOWIRE HEADEND TERMINATION (1) Design Use MPLS transport pseudowires (PW) to virtualize access for L2 and L3 services Service Node (SN e.g. PE, BNG) to support a PW Headend access interface with all required data plane and control plane functions (HQoS, security, OAM, PE-CE routing) Combined SN and TN - enable co-existence of IP/MPLS Service and Transport functions on the same physical node and the same physical links Properties L1/L2 access interface on SN replaced with PW Headend virtual interface Access side SN reachability govern by IP/MPLS decoupled from L1/L2 interfaces Reduced number of access provisioning points vs. present mode of operation SN support for all L2 and L3 services with appropriate scale E2E service restoration with local-repair for SN failures incl. access PW, node, transit links 37 Copyright 2012 Juniper Networks, Inc.

38 PSEUDOWIRE HEADEND TERMINATION (2) Flexible topological L2/L3 edge location Virtualized pseudowire access interface enables L3 edge insertion anywhere within the MPLS cloud Services can be placed optimally based on network, services and operation economics no impact on the network architecture Simplify network operations End-to-end MPLS across Aggregation and Core domains No Ethernet L2 interconnect with associated complexity (provision, assure, protect) No complex L2/L3 redundancy schemes (ie no MC-LAG) Simplified provisioning Unify L3 edge Standardize on pseudowire access with Ethernet and IP encapsulations only Support legacy access (ATM, FR, SONET/SDH) thru IP i/working function distributed into access/aggr Results in a uniform L3 Edge for all access 38 Copyright 2012 Juniper Networks, Inc.

39 LOCATION AND FLEXIBILITY OF SERVICE NODES

40 TRANSPORT VERSUS SERVICES EN AN Seamless MPLS Network SH SH SN SN TN TN BN TN TN BN TN TN AN EN Metro-1 Region WAN Backbone Region Metro-2 Region Transport Nodes Packet transport within the region (e.g. Metro LSR, Core LSR) Service Nodes Service delivery points, with flexible topological placement (e.g. IPVPN PE, S-GW, P-GW, CDN, CGN) What are the differences? Cost, Flexibility, HW, SW, Can a node evolve from TN to SN and back over its lifetime? Yes, No, Cost, 40 Copyright 2012 Juniper Networks, Inc.

SERVICE NODE SERVICES EXAMPLES (*) Broadband Broadband Subscriber Management Video Services 10Gbps Multicast Distribution for Video Distribution Video Quality Monitoring Large Scale Routing Large

41 SERVICE NODE SERVICES EXAMPLES (*) Broadband Broadband Subscriber Management Video Services 10Gbps Multicast Distribution for Video Distribution Video Quality Monitoring Large Scale Routing Large Scale Layer 3 Aggregation and Distribution Layer 3 Peering for Transit & Content Service Providers Converged L2/L3 Data Center Aggregation & Core Data Center Data Center Interconnect Load Balancing Business Services VPLS Provider Edge and Aggregation Layer 3 Virtual Private Networks Provider Edge Layer 2 Services Mobile Backhaul using Layer 2 VPN Layer 2 Circuits and Business VPLS Connectivity Mobile Services P-GW Security Services Deep Packet Inspection Address Translation CGNAT (*) Taken from current MX customer deployments 41 Copyright 2012 Juniper Networks, Inc.

42 ADDING SERVICES IN THE BEST LOCATION Requires: Optional Services component on nodes Typically license based With or without specialized extension (services blade) Tight integration with the framework Best Location varies and depends on: Network topology and geography (rings, distances, ) Service Characteristics (subscriber awareness, ) Timing and Success of the Service (trial, launch, ) Cost Required Scale Regulatory requirements 42 Copyright 2012 Juniper Networks, Inc.

47 SUMMARY

48 SEAMLESS MPLS DELIVERS A single converged packet network for delivery of all services Wireline, wireless, residential, business, wholesale, mobile Scalable Services Delivery over A single MPLS network spanning core, edge, aggregation and access Deterministic availability SLAs regardless of scale SONET/SDH like restoration times (O(50ms)) end to end Unmatched Service flexibility and simplified operations Minimized number of service provisioning points Service flexibility and easy mobility by decoupling service architecture from underlying network topology Increased service velocity and adaptability 48 Copyright 2012 Juniper Networks, Inc.

Egress Protection (draft-shen-mpls-egress-protection-framework) Presented by Krzysztof G. Szarkowicz NANOG71 October 4, 2017

Egress Protection (draft-shen-mpls-egress-protection-framework) Presented by Krzysztof G. Szarkowicz NANOG71 October 4, 2017 Current status draft-shen-mpls-egress-protection-framework-05 Co-authored by