1 / 6

draft-zhang-pce-hierarchy-extensions-01.txt

Extensions to Path Computation Element Communication Protocol (PCEP) for Hierarchical Path Computation Elements (PCE ). draft-zhang-pce-hierarchy-extensions-01.txt. Fatai Zhang (Huawei ) Quentin Zhao (Huawei) Óscar González de Dios ( Telefonica ) R amón Casellas (CTTC)

lea
Download Presentation

draft-zhang-pce-hierarchy-extensions-01.txt

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Extensions to Path Computation Element Communication Protocol (PCEP) for Hierarchical Path Computation Elements (PCE) draft-zhang-pce-hierarchy-extensions-01.txt Fatai Zhang (Huawei) Quentin Zhao (Huawei) Óscar González de Dios (Telefonica) RamónCasellas (CTTC) Daniel King (Old Dog Consulting)

  2. Updates from -00 version • Minor changes • Added ditor’s notes with the open points and suggestions • Added section on Building of parent topology

  3. OPEN issues • Parent PCE TED management • Framework document relies on basic domain connectivity, precluding TE aggregation mechanisms. • Options: should be a decision of the network operator to decide the level of information exchange allowed. • It will depend on the actual scenario (e.g. multi-area WSON vs Inter-AS/carriers) • Do we decouple Hierarchical TED management? • Alternative approaches: • (Dhruv) suggest to keep the Parent-PCE’s topology graph free of BNs (Boundary Nodes) and inter-AS TE link; it being composed only of neighbor domain adjacency.

  4. OPEN issues • Domain representation • Alignmente with e.g. draft-dhruv on domain sequence • Avoid new encodings for domains which could re-use Route sub-objects • OF codes • New requirements arise regarding OF codes • Consideration of actual OF codes (e.g. minimize domain crossing) and policies affecting them (e.g. do not allow domain re-enter). • specify the OF codes to apply at both levels? • at the parent level and also the child's (i.e. intra-domain level)

  5. OPEN issues • Reachability • Current framework and pcep drafts rely on polling to locate endpoints. (caching is not preculed) • Solutions based on notifications/announcements of endpoint (prefixes) can be considered. • Exclusions • exclusions need to take into account domains.

  6. Next Steps • Discuss the open points (meeting, mailing list) • Update the draft according to the chosen direction

More Related