Dear Authors, Here are a few comments -
1. In section 5.2: "Path Computation State Report (PCRpt): a PCEP message sent by a PCE to a PCC to report the status of one or more LSPs." I think there is mistake, PCRpt is sent from PCC to PCE based on the rest of the draft. 2. In section 5:3: It's important to add correlation between PCE Capability Discovery by IGP and via OPEN. Do you suggest to use both methods interchangeably? 3. Multiple Timers needs to be described to handle Statefull sync making sure PCC finishes the synchronization and send PCRpt with SyncDone=1 within a timeframe. You can also consider adding state synchronization as a part of Statefull Session Up. I.e. PCEP Statefull session is declared up only when PCC sends PCRpt with SyncDone=1. 4. In Section 5.5.4 you touch on Redundant Statefull PCE, we should explore backup PCE in more details. Another mechanism can be Primary and Backup Statefull PCE have a direction session and relationship to handle primary failure in a much faster and secure mechanism. 5. Wrt to delegation, PCE updates LSP parameters and send PcUpd to PCC, if PCC apply Make-Before-Break policy where new applying new parameters has failed, it's important for PCC to send PCRpt stating that LSP is up but without updating the new parameters as suggested by PCE in PCUpd. 6. Wrt to section 6.1, ERO is used to carry the path as specified by PCE, RRO is also used if LSP is setup along the path. I am not sure why you need both ERO and RRO, can you give a use case? Similarly am not sure what is the purpose of IRO in PCUpd? Sorry for nit-picking I guess! :D Also few things that should be considered - 1) Synchronization Vector: If PCC request some LSP to be computed together I think this relationship should continue in Statefull PCE so PCRpt and PCUpd should continue to support that 2) Statefull PCE becoming Bottleneck: This needs to clearly specified, mechanism like Overload PCE notification should be enhanced to handle Statefull PCE, we can explore option of PCE-PCE communication (intradomain scope) to handle Primary Statefull PCE failure/overload conditions. The clear benefit would be only 2 entity (Primary PCE and Backup PCE) will be involved, otherwise all PCC in the system must send PCRpt with Delegate=1 for all LSP. Hope we have a fruitful discussion in Taipei. Regards, Dhruv *************************************************************************************** Dhruv Dhody, Senior Technical Leader, Huawei Technologies, Bangalore, India, Ph. +91-9845062422<tel:%2B91-9845062422> This e-mail and attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient's) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!
_______________________________________________ Pce mailing list [email protected] https://www.ietf.org/mailman/listinfo/pce
