[Nsi-wg] Issue 110 in ogf-nsi-project: errorEvent does not provide originatingConnectionId or originatingNSA

[ogf-nsi-project at googlecode.com]

Status: Accepted
Owner: jmacauley
Labels: Type-Defect Priority-Medium FoundInVersion-2.0 FixedInVersion-2.0

New issue 110 by jmacauley: errorEvent does not provide  
originatingConnectionId or originatingNSA
http://code.google.com/p/ogf-nsi-project/issues/detail?id=110

The errorEvent message is an autonomous message issued from a PA to an RA  
when an existing reservation encounters an autonomous error condition that  
may impact the reservation.  The three errors currently modelled are:
•	The reservation is administratively terminated on an uPA before the  
reservation's scheduled end-time.
•	An activation or deactivation of data plane resources associated with the  
reservation has failed.
•	An error has occurred within the data plane that has impacted resources  
associated with the reservation.

The current errorEvent structure does not identify the originating uPA of  
the error, nor the impacted connectionId.  Without this information,  
trouble shooting of the issue will be impossible.  It is recommended that  
the errorEvent be extended as follows:

     <xsd:complexType name="ErrorEventType">
         <xsd:annotation>
             <xsd:documentation xml:lang="en">
                 Type definition for an autonomous message issued from a
                 Provider NSA to a Requester NSA when an existing reservation
                 encounters an autonomous error condition such as being
                 administratively terminated before the reservation's  
scheduled
                 end-time.

                 Elements:

                 connectionId - The Provider NSA assigned connectionId that  
this
                 notification is against.

                 notificationId - A notification identifier that is unique  
in the
                 context of a connectionId.  This is a linearly increasing
                 identifier that can be used for ordering notifications in  
the
                 context of the connectionId.

                 timeStamp - Time the event was generated on the originating  
NSA.

                 event - The type of event that generated this notification.

                 originatingConnectionId - The connectionId that triggered  
the
                 error event.

                 originatingNSA - The NSA originating the error event.

                 additionalInfo - Type/value pairs that can provide  
additional
                 error context as needed.

                 serviceException - Specific error condition - the reason  
for the
                 generation of the error event.
             </xsd:documentation>
         </xsd:annotation>
         <xsd:complexContent>
             <xsd:extension  base="tns:NotificationBaseType">
                 <xsd:sequence>
                     <xsd:element name="event"                    
type="tns:EventEnumType" />
                     <xsd:element name="originatingConnectionId"  
type="ftypes:ConnectionIdType" />
                     <xsd:element name="originatingNSA"           
type="ftypes:NsaIdType" />
                     <xsd:element name="additionalInfo"           
type="ftypes:TypeValuePairListType" minOccurs="0" />
                     <xsd:element name="serviceException"         
type="ftypes:ServiceExceptionType" minOccurs="0" />
                 </xsd:sequence>
             </xsd:extension>
         </xsd:complexContent>
     </xsd:complexType>



-- 
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