Query in OIF-UNI-1.0 Implementation Aggrement

[brajaram@npd.hcltech.com]

Hi,
    I have the following doubt.

    If there is cleanup timeout (Path celanup or Resv celanup) in
UNI_C(client side) or in UNI_N(network side), whether we can consider
that as "Network Failue" and start Graceful deletion in respective side
itself by considering direction. Because, if I consider cleanup timeout
as "Network Failue", then I should not send PathErr or ResvErr to the
ingress or egress end.

    For example, if there is Resv cleanup timeout expired in source
UNI_C, then instead of sending ResvTear (as in normal RSVP) message, I
can send ResvErr to source UNI_N(network side). Thinking from the
implementation prespectivem, since I consider cleanup timeout situation
as "Network Failue"(not fault handling situation), I will have to inform
the respective application (in this case, source UNI_C application) with
PathErr(direction is important) message using corresponding Path State
details.

    My observation is that hello synchronization will handle this
situation as fault handling scenario. Anyway, please clarify that what
action can be taken, when state cleanup timeout expires. Whether
"graceful deletion" or ?...

Thanks,
Rajaraman. B