[Css-csts] RE: NULL requested GVCID value for ROCF?

[John Pietras]

Martin,
Thank you. Yes, I now see the description in Table 3-11. I failed to notice that before sending my comment.

Best regards,
John

From: Martin Götzelmann [mailto:martin.goetzelmann at telespazio-vega.de]
Sent: Tuesday, March 05, 2013 12:01 PM
To: John Pietras; Wolfgang.Hell at esa.int
Cc: CCSDS_CSTSWG (css-csts at mailman.ccsds.org)
Subject: RE: NULL requested GVCID value for ROCF?

John,
I think I remember this one because we had a problem when defining the API. The problem is the parameter can be retrieved in the state ready i.e. before START operation has been invoked and therefore the requested GVCID is undefined.
Regards, Martin

From: css-csts-bounces at mailman.ccsds.org<mailto:css-csts-bounces at mailman.ccsds.org> [mailto:css-csts-bounces at mailman.ccsds.org] On Behalf Of John Pietras
Sent: 04 March 2013 22:47
To: Wolfgang.Hell at esa.int<mailto:Wolfgang.Hell at esa.int>
Cc: CCSDS_CSTSWG (css-csts at mailman.ccsds.org<mailto:css-csts at mailman.ccsds.org>)
Subject: [Css-csts] NULL requested GVCID value for ROCF?

Wolfgang,
The ASN.1 RocfGetParameter type specifies the value component of the parReqGvcId choice as being of type RequestedGvcId. In turn, RequestedGvcId is defined as
RequestedGvcId ::= CHOICE
{ gvcid [0] GvcId
, undefined [1] NULL
}

However, the requestedGvcId parameter of the RocfStartInvocation parameter is cast simply as type GvcId.  I think the RequestedGvcId  type definition is an error - it isn't necessary and the value component of parReqGvcId should be cast as GvcId .

(This is just speculation on my part, but it may have resulted from a confusion with the RequestedTcVcid type, which is used to specify the TC VC that is being monitored and which *can* have a null value (if the OCFs don't contain CLCWs).)

Best regards,
John

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