%% You should probably cite rfc8735 instead of this I-D. @techreport{ietf-teas-native-ip-scenarios-12, number = {draft-ietf-teas-native-ip-scenarios-12}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-teas-native-ip-scenarios/12/}, author = {Aijun Wang and Xiaohong Huang and Caixia Qou and Zhenqiang Li and Penghui Mi}, title = {{Scenarios and Simulation Results of PCE in a Native IP Network}}, pagetotal = 16, year = 2019, month = oct, day = 29, abstract = {Requirements for providing the End-to-End (E2E) performance assurance are emerging within the service provider networks. While there are various technology solutions, there is no single solution that can fulfill these requirements for a native IP network. In particular, there is a need for a universal E2E solution that can cover both intra- and inter-domain scenarios. One feasible E2E traffic-engineering solution is the addition of central control in a native IP network. This document describes various complex scenarios and simulation results when applying the Path Computation Element (PCE) in a native IP network. This solution, referred to as Centralized Control Dynamic Routing (CCDR), integrates the advantage of using distributed protocols and the power of a centralized control technology, providing traffic engineering for native IP networks in a manner that applies equally to intra- and inter-domain scenarios.}, }