[Nsi-wg] Issue 48 in ogf-nsi-project: Addition of a Failed state into the state machine.

[ogf-nsi-project at googlecode.com]

Comment #2 on issue 48 by thost... at gmail.com: Addition of a Failed state  
into the state machine.
http://code.google.com/p/ogf-nsi-project/issues/detail?id=48

This topic somewhat binds into how we update connections states and the  
responsibility of provider or requester for getting updates propagated.

Knowing why a connection failed / was terminated early could be very  
convenient for an user/operator. A failed state however doesn't buy us a  
lot as it just tell us it was failed, but not why, which is the immediate  
follow-up question. An information field is much more useful IMO.

 From a connection point-of-view there is no difference between terminated  
and failed (the connection is down, and there isn't really a lot to do  
about it), so a failed state doesn't really buy us a lot, where as an  
information field does.