[Css-csts] Another RID - repeated dataSequenceCounter

John Pietras john.pietras at gst.com
Wed Nov 3 10:44:06 EST 2010


Yves, 

I stumbled across this while responding to your EXECUTE-DIRECTIVE
message.

 

Page: 4-49, D-27

Short title: repeated dataSequenceCounter

 

1) In 4.9.4.3.3.4 (b), change

"otherwise, the data-sequence-last-OK parameter shall specify the
sequence

number of the data unit that most recently was successfully processed."

 

to

 

"otherwise, the data-sequence-last-OK parameter shall specify the
sequence

number of the most recent data unit that was successfully processed and
the time at which it was processed".

 

 

2)  In the DataProcessingNotifyInvocExt type definition, change:

 

dataSequenceLastOk CHOICE

{ noSuccessfulProcessing [0] NULL

, dataSequenceCounter [1] SEQUENCE

{ dataSequenceCounter DataSequenceCounter

, dataProductionTime Time

}

}

 

to

 

dataSequenceLastOk CHOICE

{ noSuccessfulProcessing [0] NULL

, dataSequenceCounterAndTime [1] SEQUENCE

{ dataSequenceCounter DataSequenceCounter

, dataProductionTime Time

}

}

 

Analysis

 

1) The ASN.1 includes a timestamp, which is not mentioned in the text.
Also, reworded to sentence for clarity 

("the data unit that most recently was successfully processed" to "the
most recent data unit that was successfully processed")

 

2) The name of the sequence (dataSequenceCounter) should not be the same
as the first element of

that sequence.

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ccsds.org/pipermail/css-csts/attachments/20101103/d2c8d58c/attachment.html


More information about the Css-csts mailing list