[Css-csts] Data-Processing Procedure - Comments

[Yves.Doat at esa.int]

Dear Tim,
Please find below several comments to the Data-Processing procedure.

==================================================================
COMMENT 1:
The format should be revised to be in line with the rest of the document,
e.g.: tables borders, tables in portrait (not in landscape),  table 3-1,
section 2.4.1 does not follow the agreed structure (Feedback), ...

==================================================================
COMMENT 2:
Section 1.2.2 specifies that for each data unit immediate feed-back is
provided (acknowledge). In fact the Process-Data is a two ways operation and
we should not mention 'acknowledge' but 'return'.
However I note that the procedure has two new notifications (section 3.3.2)
'data expired'  and 'data processing successfully completed'. We would
consider this operation as a 3 ways operations, we would have an
acknowledgement and we could cover those two notifications as part of the
return. Can we consider that the PROCESS-DATA operation could always be
three-ways?

==================================================================
COMMENT 3:
Section 2.3 states that if the provider accepts a Data-Unit, it is buffered.
I am missing in the description when is the data-unit removed from the
buffer?
Do we really want the procedure specifies the data buffer behaviour? Is that
not implementation specific? Can we avoid talking of a data buffer?

==================================================================
COMMENT 4:
Section 2.4.3.2 specifies that the provider shall always notify the user on a
negative completion of the processing. Does that mean that the
process-completion-report parameter of the PROCESS-DATA operation shall
always be set to true? What would be the behaviour. I think the behaviour
associated to the process-completion-report parameter is to be clarified.

==================================================================
COMMENT 5:
I am working on the ASN.1 definition and that triggers the following comment.
I have a problem with the NOTIFY extension and I will try to explain the
problem hereafter.

The types of notifications agreed are the following:
   production status configured;
   production status interrupted;
   production status halted;
   production status operational
   notification extension

In your notification extension you request whatever notification to carry
similar detailed information, i.e. data-sequence-last-processed,
data-processing-status,data-processing-start-time, data-sequence-last-OK,
data-production-time). So far so good. I can map the required information as
follows:
   Change the common type NotificationTypes to allow carrying external data
   whatever notification is used;
   Define a structure that covers your need: no problem I have done it (I do
   not attach it here otherwise the mail would be too messy)

Now comes the problem. In addition to the above list the NOTIFY shall also
carry the production status.
As a consequence, the provider could send a NOTIFY with a NotificationType
"productionConfigured" that would contain your proposed structure containing
the production-status information.

I propose to remove the 'production-status' parameter from the NOTIFY
extension to avoid redundancy.

==================================================================
COMMENT 6:
The procedure requires the following two new notification types: 'data
expired', 'data processing successfully completed'.
 I have the feeling that:
   'data expired' is redundant with the value 'data expired' of the
   'data-process-status'
   'data processing successfully completed' is redundant with the value ‘data
   successfully processed’

I wonder whether the 'data-process-status' should not be in fact a
notification type.

Let's assume we convert this parameter into a notification type, we would
have in addition to the standard notification types:
   data successfully processed
   data expired
   data processing interrupted
   data processing started
   data processing not started
Consequence: In case the production status would change to interrupted while
a PROCESS-DATA is not completed, the user would get two notifications:
'production status interrupted' and 'data processing not started'. The next
question would be to know whether we need all this progress information when
processing the data.

Best regards

Yves
__________________________________________________
Head Ground Infrastructure Baseband Section (OPS-GIB)
ESA/ESOC Robert-Bosch Strasse 5
D-64293 Darmstadt, Germany
Tel.: +49 (6151) 90.2288               Fax:+49 (6151) 90.3046
Internet: http://www.esa.int/
__________________________________________________