Hi there I have reviewed this draft - here are my comments.
Best regards Jon Section 3.2 Figure 2, I think the "sync done" PCRpt should have SYNC=0, not SYNC=1. Section 5.2 If a PCC has to force full LSP DB synchronization due to reasons including but not limited: (1) local policy configured at the PCC; (2) no sufficient LSP state caches for incremental update, the PCC can set the D flag to 0. Perhaps I have misunderstood, but I think case (2) above doesn't work. The PCC does not know that it has "no sufficient LSP state caches" until it receives the OPEN from the PCE and sees what DBv the PCE has sent. By then, the PCC has already sent its OPEN so it is too late to set D=0. To cover case (2) the draft needs a mechanism for the PCC to change its mind and tell the PCE that it is going to send a full snapshot, not a replay of the missing database updates. The simplest thing is probably for the PCC to bring the session down and then bring it back up again with D=0. Section 4 talks about the PCE having to mark its LSP database as stale, and then remove any stale LSPs at the end of the synchronization process. I assume that this does not apply in section 5. To avoid confusion, I think section 5 should state that the PCE does not mark its LSP database as stale if both it and the PCC have set D=1. In figure 7, I may have misunderstood section 4, but I don't think this is how the T bit is specified. I don't think T=1 forces the PCC to wait for a PCUpd before sending the initial snapshot as you have shown. I don't think this substantially changes anything about section 5, so I suggest removing the discussion of the T bit from section 5.
_______________________________________________ Pce mailing list [email protected] https://www.ietf.org/mailman/listinfo/pce
