[Css-csts] RE: DPP Prototype ASN.1 definitions

[Zoller, David A. (MSFC-EO50)[HOSC SERVICES CONTRACT]]

Dear CSTS WG Members,
Last night, I had additional thoughts on the TransferBuffer so I would like to add another set of bullets to the list:


·         TransferBuffer is only mentioned in the Behavior section (4.7.4) of Buffered Data Processing

o   Is the usage of the TransferBuffer allowed with Sequence-Controlled Data Processing?



·         TransferBuffer is defined as a "SEQUENCE OF ProcessDataInvocation"

o   Has a definition of "SEQUENCE OF CstsFrameworkPdu" already been considered and rejected?

§  Is that even possible in ASN.1?

§  PDU type checking would be done by the Performer to ensure that they are all ProcessDataInvocations in this case

Best regards,
DZ


David Zoller
COLSA Corporation
MSFC/HOSC - C107
*Office: (256) 544-1820
*EMail: david.a.zoller at nasa.gov<mailto:david.a.zoller at nasa.gov>

From: Zoller, David A. (MSFC-EO50)[HOSC SERVICES CONTRACT]
Sent: Thursday, January 16, 2014 2:27 PM
To: css-csts at mailman.ccsds.org
Subject: DPP Prototype ASN.1 definitions

Dear CSTS WG Members,
I have been updating the DPP Provider prototype with the latest ASN.1 definitions that I could find which I pulled from the document: 921x1r2[Draft_201310]_-_All_Services.docx. Please find below some comments on the ASN.1 definitions.


·         The ASN.1 uses Performer/Invoker while the document uses Provider/User

o   Is there a preferred terminology?

o   I am okay with using both as is ;-)



·         BIND and UNBIND invocations use a parameter name of invocationHeader while all of the other messages use standardInvocationHeader

o   I think it would be better if they were all consistent



·         StandardInvocationHeader.procedureInstanceId.procedureType usage

o   I wish to instantiate the appropriate performer type based on the invoker's specified ProcedureType

§  bufferedDataProcessing and sequenceControlledDataProcessing types are defined

§  It would be useful to be able to specify bufferedDataProcessingComplete and bufferedDataProcessingTimely types

o   Or will there be individual START formats for each of the types that I should key on?

o   Should these be part of the Framework baseline ASN.1 or would these be extensions for the prototype?



·         There were a few errors and warnings while processing the ASN.1

o   These have probably been corrected since the draft in October but let me know if anyone needs details



·         TransferBuffer with ProcessDataInvocations is not incorporated into the CstsFrameworkPdu structure yet

o   I am making use of the TransferBufferInvocation with TransferDataNotifications until the other is available

I recognize that this is a work in progress and I probably do not have the latest and greatest version. I am willing to help validate the DPP end of things as best I can if so desired.

Best regards,
David

David Zoller
COLSA Corporation
MSFC/HOSC - C107
*Office: (256) 544-1820
*EMail: david.a.zoller at nasa.gov<mailto:david.a.zoller at nasa.gov>

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