On 10/5/17 8:56, [email protected] wrote:
Hi,
I think the main point is what does the session reset bring here ? IMO nothing
in that case, your session will constantly bounce until the someone reduce the
number of states sent by a particular PCC which will create even more load on
the PCE. This is an event that cannot be corrected by the session reset.
I don't have a strong opinion after all, but before closing the session
you get the proper PCNtf. There is no need to constantly bounce. To your
question, IMHO closing the session accomplishes precisely
(deterministically) that either you reach end of sync or not; not
allowing to get a "half-sync" state.
Logging the Notification is a better approach that would allow the operator to
be informed and trigger a fix.
You log it anyway. The session is not "abruptly" closed.
At the end, I am fine with either choice. Even if I consider not being
able to complete sync an issue, I also consider setting a policy that
prevents a pcc to sync another (unrelated) issue.
Regards
Ramon
_______________________________________________
Pce mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/pce
