Status: Accepted Owner: jmacauley Labels: Type-Defect Priority-Medium FoundInVersion-2.0 FixedInVersion-2.0 New issue 92 by jmacauley: The Maastricht updates - Introduction of Notification retrieval http://code.google.com/p/ogf-nsi-project/issues/detail?id=92 Description of Issue: During design of NSI CS version 2 the majority of error states were removed from the state machine and a new set of notifications were added to inform the uRA of issues with a reservation that did not directly effect the new state machine. Removing the majority of error states help simplify the state machine, and reduce the spontaneous state machine transitions previously triggered by error conditions. As a result of this new strategy, there is no way for a uRA to determine if an error notification was generated against a reservation if that uRA is not listening to notifications on that reservation. This situation may occur if the RA is using a polling mechanism, or is recovering from a communications problem with the peer provider NSA. As you can imagine, this is a serious issue that needs to be addressed before NSI CS version 2 can be declared ready for prime time. To help remedy this issue, it was agreed that a new mechanism should be added to the existing NSI CS version 2 protocol that will allow an RA to query a reservation and determine if there have been any error notifications raised against that reservation. Specifically, we need to allow for the handling of ErrorEventType, ReserveTimeoutRequestType, and messageDeliveryTimeout notifications as these will require corrective action from the uRA. The dataPlaneStateChange notification need not be handed as this state is modeled in the dataPlaneStatus element already available in the reservation query. Discussion of Issue: See attached discussion of issue. Resolution of Issue: A slightly modified solution 2b was agreed upon for implementation. Attachments: NSI-CS-NotificationQueries-v1.pdf 975 KB -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings