WorkAround handling Operational states notification

Based on UTD observations,:
When a fiber failure happens,
1. VendorA ROADM a) OTS interface and b) DEG port operational status will become outOfService. VendorA ROADM sends an AlarmNotification to T-PCE, but no a ChangeNotification. T-PCE will not start the restoration.
2. VendorB ROADM sends a ChangeNotification to T-PCE. But its a) OTS interface and b) DEG port operational status remains inService. So, T-PCE will not start the restoration also.
This means that we need to find a work around to handle SC22 demo.
1) Check implementation (netconf/openROADM stream
2) Define the way we handle the workaround

tianliang : Please could you provide the extract of the state-change notification sent by VendorB equipment, to provide a workaround in the shortest time.