%% You should probably cite rfc8735 instead of this I-D.
@techreport{ietf-teas-native-ip-scenarios-10,
    number =    {draft-ietf-teas-native-ip-scenarios-10},
    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/10/},
    author =    {Aijun Wang and Xiaohong Huang and Caixia Qou and Zhenqiang Li and Penghui Mi},
    title =     {{Scenarios and Simulation Results of PCE in Native IP Network}},
    pagetotal = 17,
    year =      ** No value found for 'doc.pub_date.year' **,
    month =     ** No value found for 'doc.pub_date' **,
    day =       ** No value found for 'doc.pub_date.day' **,
    abstract =  {Requirements for providing the End to End(E2E) performance assurance are emerging within the service provider network. While there are various technology solutions, there is no one solution which can fulfill these requirements for a native IP network. One universal (E2E) solution which can cover both intra-domain and inter-domain scenarios is needed. 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.},
}