[Css-csts] practical concerns - TransferBuffer

[Ray, Timothy J. (GSFC-5830)]

Dear Working Group,

When a CSTS User receives an incoming TransferBufferInvocation, it has to dig pretty deep to determine the ProcedureInstanceId.  If it is ever important to make the User's processing of incoming data efficient (i.e. so that data can be transferred at a high data rate), it may be worthwhile to ease the processing required.  For example, we might consider adding a ProcedureInstanceId (or StandardInvocationHeader) at the top-level of the TransferBufferInvocation structure.

Related topic:  If it is ever important to reduce the overhead (bandwidth) associated with CSTS, it might be worthwhile to reduce the number of Standard-Invocation-Header appearances in a TransferBufferInvocation.   For example, currently, if a single TransferBufferInvocation contains 100 TransferDataInvocations, there will be 100 copies of the StandardInvocationHeader (and thus 100 copies of the Credentials, and 100 copies of the ProcedureInstanceId).

Thoughts towards a possible solution:
When invocations are nested inside another invocation, the StandardInvocationHeader is only required in the outermost invocation.
The StandardInvocationHeader is optional in the TransferDataInvocation and NotificationInvocation.

Best regards,
Tim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ccsds.org/pipermail/css-csts/attachments/20090812/492e559f/attachment-0001.html