[Css-csts] 'invalid procedure instance identifier' should lead to peer abort

John Pietras john.pietras at gst.com
Fri Feb 4 11:42:06 EST 2011


CSTSWG colleagues ---

The Standard Operation Header has the diagnostic 'invalid procedure
instance identifier', which is defined as

'invalid procedure instance identifier' - the submitted procedure
instance identifier is invalid as a result of

-        procedure type is not specified by the service,

-        the combination of procedure type and instance is not in line
with the configuration of the provider;

 

However, because it is an SOH diagnostic, this can only be returned for
confirmed operations: e.g., a TRANSFER-SERVICE invocation referencing a
procedure type that is not used by the service, or containing a
procedure instance number for a procedure instance that hasn't been
activated, would presumably proceed without correction. An error of this
type seems to be at least as serious as the other conditions that result
in a peer abort, so even for a confirmed operation it would seem
inadvisable to simply reject to invocation and continue on. This
diagnostic should be moved from the SOH to the PEER-ABORT operation, so
that when the condition is present it results in a peer abort regardless
of whether the operation is confirmed or not. 

 

Best regards,

John

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ccsds.org/pipermail/css-csts/attachments/20110204/d892d7b2/attachment.htm


More information about the Css-csts mailing list