[Css-csts] Framework ASN.1

[John Pietras]

Tim and Yves,

I hope that it is not necessary to generate service-specific ASN.1 using
the Framework. That would negate one of the benefits of the CSTS
(toolkit) approach.

 

Best regards,

John

 

________________________________

From: css-csts-bounces at mailman.ccsds.org
[mailto:css-csts-bounces at mailman.ccsds.org] On Behalf Of Ray, Timothy J.
(GSFC-5830)
Sent: Thursday, June 04, 2009 6:27 PM
To: Yves.Doat at esa.int
Cc: css-csts at mailman.ccsds.org
Subject: [Css-csts] Framework ASN.1

 

Hi Yves,

 

When implementing the Forward CLTU Service, all incoming messages were
decoded into a single top-level C structure (the OSS tool called it
'CltuVersion1Pdu').  

 

In trying to work with the Framework ASN.1, I can't find an analogous
single top-level structure (there are multiple top-level structures -
e.g. AssociationPdu, InformationQueryPdu, ThrowEventPdu,
DataProcessingPdu, etc).     I suspect that the answer is "each service
must define additional ASN.1 (that will provide this top-level
structure)".  If so, we will have to define service-level ASN.1 for our
inter-operability testing (as far as I know, this hasn't been done yet).


 

Best regards,

Tim

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