1 / 7

PCE WG, IETF 83rd , Paris , France draft-gonzalezdedios-pce-reservation-state-01

PCEP Extensions for Temporary Reservation of Computed Path Resources and Support for Limited Context State in PCE. PCE WG, IETF 83rd , Paris , France draft-gonzalezdedios-pce-reservation-state-01 Oscar Gonzalez de Dios ( ogondio@tid.es ) Ramon Casellas ( ramon.casellas@cttc.es)

loisn
Télécharger la présentation

PCE WG, IETF 83rd , Paris , France draft-gonzalezdedios-pce-reservation-state-01

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. PCEP Extensions for Temporary Reservation of Computed Path Resources and Support for Limited Context State in PCE PCE WG, IETF 83rd, Paris, France draft-gonzalezdedios-pce-reservation-state-01 Oscar Gonzalez de Dios (ogondio@tid.es) Ramon Casellas (ramon.casellas@cttc.es) Cyril Margaria(cyril.margaria@nsn.com) Young Lee (leeyoung@huawei.com) Fatai Zhang (zhangfatai@huawei.com)

  2. Changes from 00 • Welcome Cyril, Fatai and Young to the draft and thanks for their comments and suggestions • Aim of the draft: allow the PCC to indicate to the PCE to block the resources computed in a path request of a TE LSP for subsequent requests for a certain time • Helps to reduce the number of crankbacks. • Aim of the changes: • After 00 was presented, comments where received regarding cases where, after receiving an update of information to the TED, it was not possible to hold the reservation. • This versions aims at clarifying the scope of the temporary reservation of resources • Clarifying the terminology • Refine the document

  3. Changes from 00 • Changes in the introduction • Reservation/booking mechanisms can be applied by policy • However… the PCE cannot infer the intention of the PCC with the computed TE-LSP path. • Identified two main cases applying reservations: • 1) Resource is uniquely identified in the topology update -> Reservation can hold after the update (no uncertainty) E.G. receiving a OSPF-TE TE LSA with a bitmap encoded wavelength availability. • 2) Resource is NOT uniquely identified in the topology update. In this case, to maintain coherence, the topology update previals. • Minor changes through all the sections of the draft.

  4. Changes from 00 • Added the 2 possible cases when topology updates arrive to the PCE in the protocol procedures section. • Use case Multiple LSP restoration -> Multiple LSP restoration in a WSON network • Use case has been extended.

  5. Open Points • Need to send PCC_ID. • Remove the need to send it? • Re-use RESERVATION object for the response • Scope the reservation per PCEP session? • If PCEP session stops, reservations do not apply longer.

  6. Next Steps • Do we want this functionality on the PCE? • Refine it based on the feedback from the meeting or mailing list: • Use of absolute timestamps vs relative timestamps in reservations • Recommended value for reservation time • Multi-domain reservations • Synchronization of reservations with multiple PCEs • More use cases?

  7. Acknowledgements • Meral Sherazipour: feedback in mailing list and private mail • Filippo Cuigini: mail feedback, work on path state based PCE update • PCE WG Chairs, feedback in meetings • Adrian Farrel, feedback in meetings • STRONGEST Project to support the work

More Related