Presentation is loading. Please wait.

Presentation is loading. Please wait.

71 th IETF – Philadelphia, USA March 2008 PCECP Requirements and Protocol Extensions in Support of Global Concurrent Optimization Young Lee (Huawei) J-L.

Similar presentations


Presentation on theme: "71 th IETF – Philadelphia, USA March 2008 PCECP Requirements and Protocol Extensions in Support of Global Concurrent Optimization Young Lee (Huawei) J-L."— Presentation transcript:

1 71 th IETF – Philadelphia, USA March 2008 PCECP Requirements and Protocol Extensions in Support of Global Concurrent Optimization Young Lee (Huawei) J-L Le Roux (France Telecom) Daniel King (Aria Networks) Eiji Oki (NTT)

2 71 th IETF – Philadelphia, USA March 2008 What is GCO? Global Concurrent Optimization (GCO) is a concurrent path computation application where a set of TE paths are computed concurrently in order to efficiently utilize network resources.

3 71 th IETF – Philadelphia, USA March 2008 Document History Presented as an individual draft in 67 th San Diego in Nov Revised 5 times (04 version) during Adopted as PCE WG item in June 2007 (right after 69 th and Issued the WG draft draft-ietf-pce-global-concurrent-optimization-00.txt Have revised 2 times since then: currently 02 version. draft-ietf-pce-global-concurrent-optimization-02.txt

4 71 th IETF – Philadelphia, USA March 2008 Changes since the last version Fabien provided many useful comments: Section 5 - add a new text: "Note also that when the XRO is global to a SVEC, and F bit is set, it should be allowed to specify multiple RRO objects in the PCReq message. Section Instead of creating a new bit (C bit) in the SVEC object to indicate explicitly the GCO application, implicit method was used in v.2. The following text was added: "This can be indicated implicitly by placing the GCO related objects (GOF, GC or XRO) after the SVEC object. That is, if any of these objects follows the SVEC object in the PCReq message, all of the requested path computations specified in the SVEC object are subject to GOF, GC or XRO. Section The Order TLV format was changed to be consistent with PCEP draft. Section Clarify that the delete order is not applicable to new LSP. Section GLOBAL CONSTRAINT Object-Class value is changed to 22 to be consistent with PCEP and OF drafts.

5 71 th IETF – Philadelphia, USA March 2008 Current Standing I-D is stable. A few Implementations underway. Waiting for chairs review Ready for WG LC?


Download ppt "71 th IETF – Philadelphia, USA March 2008 PCECP Requirements and Protocol Extensions in Support of Global Concurrent Optimization Young Lee (Huawei) J-L."

Similar presentations


Ads by Google