PCE in Native IP Network (Dynamic Network Resource Scheduling) https://datatracker.ietf.org/doc/draft-wang-teas-pce-native-ip/ https://datatracker.ietf.org/doc/draft-wang-pce-extension-native-ip/ Aijun Wang (Speaker) (China Telecom) Quintin Zhao(Huawei) Boris Khasanov(Huawei) Kevin Mi(Tencent) Raghavendra Mallya(Juniper) IETF 97@Seoul, Nov. 14-18 2016

Traffic Engineering Current Status TE(IP Network) MPLS Distributed (MPLS-TE) Central Control (PCE/PCECC/SR) Native IPv6 Distributed (DiffServ) Central Control (SR/DNRS) Native IPv4 Central Control (DNRS) Distributed (DiffServ) Covered by current drafts

The key idea of  PCE in Native IP is based on Dual/Multi-BGP session strategy and PCE-based central control architecture R1 R2 R4 R3 R5 R6 R7 Prefix11 Prefix12 Prefix13 Prefix14 … … Prefix1N PCE Prefix21 Prefix22 Prefix23 Prefix24 Prefix2N Dual/Multi BGP Peers between R1/R7 with different loopback addresses BGP Peer 1 advertised prefixes BGP Peer 2 advertised prefixes BGP Peer N advertised prefixes Explicit Route to Peer 1 Explicit Route to Peer 2 Explicit Route to Peer N

Case 1: QoS Requirement Changed (Prefix14/Prefix24) PCE R3 Prefix21 Prefix22 Prefix23 Prefix24 … … Prefix1N Prefix11 Prefix12 Prefix13 Prefix14 … … Prefix1N R5 R6 R1 R7 R2 R4 Dual/Multi BGP Peers between R1/R7 with different loopback addresses BGP Peer 1 advertised prefixes BGP Peer 2 advertised prefixes … … BGP Peer N advertised prefixes Explicit Route to Peer 1 Explicit Route to Peer 2 Explicit Route to Peer N

Case 2: Traffic for assured Prefixes changed (Prefix14/Prefix24) PCE R3 Prefix21 Prefix22 Prefix23 Prefix24 … … Prefix1N Prefix11 Prefix12 Prefix13 Prefix14 … … Prefix1N R5 R6 R1 R7 R2 R4 Dual/Multi BGP Peers between R1/R7 with different loopback addresses BGP Peer 1 advertised prefixes BGP Peer 2 advertised prefixes … … BGP Peer N advertised prefixes Explicit Route to Peer 1 Explicit Route to Peer 2 Explicit Route to Peer N

PCEP Extension New PCEP Objects Key Parameters Usage Peer Address List (PAL) List of Peer Addresses PCC uses this information to build BGP connection with the appointed peer Peer Prefix Association (PPA) Relation between Different Prefixes and their associated peer PCC advertises different prefixes via different BGP peer. Explicit Peer Route (EPR) Explicit Routes to Peer Address PCC builds the explicit routes to the peer address

Solution Comparison Solution Key Steps Challenge Drawback BGP FlowSpec BGP Policy on every on-path router State Table is same on every router Extensibility OpenFlow Specific Rule on every on-path router Dual/Multi BGP (NETCONF) BGP Policy on Edge router. Limited explicit routes on intermediate router. Deployed Via NETCONF Same as BGP VPN Solution Multiple YANG Supported Needed/Agility/ Dual/Multi BGP (PCEP) Deployed Via PCEP PCEP Extension

Deployment Consideration Scalability Same as the BGP L3VPN solution. High Availability PCE should and can assure it. Incremental deployment Congested router pair can be updated first Deployment within Pure IGP network Similar procedure/route tag/route policy

Further Action Adopt as one WG draft? Solution for Pure IGP network? QoS consideration Comments? wangaj@ctbri.com.cn quintin.zhao@huawei.com khasanov.boris@huawei.com kevinmi@tencent.com rmallya@juniper.net IETF97@Seoul