Transcript IPv6 Site Renumbering Gap Analysis

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
1
Traffic Engineering Current Status
Distributed
(MPLS-TE)
MPLS
Central Control
(PCE/PCECC/SR)
Distributed
(DiffServ)
TE(IP Network)
Native IPv6
Central Control
(SR/DNRS)
Central Control
(DNRS)
Native IPv4
Distributed
(DiffServ)
Covered by current drafts
2
The key idea of PCE in Native IP is based on
Dual/Multi-BGP session strategy and
PCE-based central control architecture
PCE
R3
Prefix11
Prefix12
Prefix13
Prefix14
……
……
Prefix1N
R5
R6
R1
R7
R2
R4
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
Explicit Route to Peer 1
Explicit Route to Peer 2
……
BGP Peer N
advertised prefixes
Explicit Route to Peer N
3
Case 1: QoS Requirement Changed
(Prefix14/Prefix24)
PCE
R3
Prefix11
Prefix12
Prefix13
Prefix14
……
……
Prefix1N
R5
R6
R1
R7
R2
Prefix21
Prefix22
Prefix23
Prefix24
……
……
Prefix1N
R4
Dual/Multi BGP Peers between R1/R7
with different loopback addresses
BGP Peer 1
advertised prefixes
BGP Peer 2
advertised prefixes
Explicit Route to Peer 1
Explicit Route to Peer 2
……
BGP Peer N
advertised prefixes
Explicit Route to Peer N
4
Case 2: Traffic for assured Prefixes changed
(Prefix14/Prefix24)
PCE
R3
Prefix11
Prefix12
Prefix13
Prefix14
……
……
Prefix1N
R5
R6
R1
R7
R2
Prefix21
Prefix22
Prefix23
Prefix24
……
……
Prefix1N
R4
Dual/Multi BGP Peers between R1/R7
with different loopback addresses
BGP Peer 1
advertised prefixes
BGP Peer 2
advertised prefixes
Explicit Route to Peer 1
Explicit Route to Peer 2
……
BGP Peer N
advertised prefixes
Explicit Route to Peer N
5
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
6
Solution Comparison
Solution
BGP
FlowSpec
Key Steps
Challenge
BGP Policy on every on-path State Table is
router
same on every
router
Drawback
Extensibility
OpenFlow
Specific Rule on every onpath router
State Table is
same on every
router
Extensibility
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)
BGP Policy on Edge router.
Limited explicit routes on
intermediate router.
Deployed Via PCEP
Same as BGP
VPN Solution
PCEP Extension
7
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
8
Further Action
•
•
•
•
Adopt as one WG draft?
Solution for Pure IGP network?
QoS consideration
Comments?
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
IETF97@Seoul
9