[Css-csts] Re: Incorrect Cyclic Report TRANSFER-DATA extension

[Yves.Doat at esa.int]

Dear John,

Thank you for your comment.
I reviewed and updated the Cyclic Report procedure taking into consideration
that the qualified parameters are carried by refinement of the TRANSFER-DATA
'data' parameter. However I changed your comments which (I think) still mixed
refinement and extension.

I attach the resulting Cyclic Report procedure and here is a summary of the
changes:
   Table 4-25. The TRANSFER-DATA operation is not extended but refined.
   Section 4.7.4.2 has been rephrased identifying the refinement and not
   anymore the extension.
   I updated the CyclicReportStartDiagnosticExt ASN.1 (section D.3.9)
   changing unknownName to unknownName
   I rephrase the CyclicReportTransferDataExt ASN.1 to
   CyclicReportTransferDataRef identifying the refinement.

Best regards
Yves
(See attached file: Cyclic Report Procedure - TRANSFER-DATA updated.pdf)


                                                                                                                                   
  From:       "John Pietras" <john.pietras at gst.com>                                                                                
                                                                                                                                   
  To:         <Yves.Doat at esa.int>                                                                                                  
                                                                                                                                   
  Cc:         <css-csts at mailman.ccsds.org>                                                                                         
                                                                                                                                   
  Date:       26/01/2012 17:18                                                                                                     
                                                                                                                                   
  Subject:    Incorrect Cyclic Report TRANSFER-DATA extension                                                                      
                                                                                                                                   





Yves,
In the definition of the Cyclic Report procedure, section 4.7.4.2 incorrectly
states “This procedure extends the TRANSFER-DATA operation defined in 4.6.3.3
through the addition of one parameter to the invocation.” This is incorrect –
the procedure does *not* add a new parameter to the invocation, it casts the
‘data’ parameter to be a sequence of qualified-parameters. The remainder of
section 4.7.4.2 also specifies that a new parameter is being added to the
invocation.

The corresponding ASN.1 in D3.9 does identify that it is the ‘data’ parameter
that is being extended (not the set of invocation parameters), but it
interleaves the specification of the extension parameters (i.e., adding
parameters to the invocation) and the extension (recasting) of the ‘data’
parameter. Specifically, it has the comment about the extensionParameter of
the TransferDataInvocation being set to notUsed between the specification of
the data parameter extension syntax and the specification of the OID for the
data parameter extension syntax. Also, the OID for the parameter extension
syntax is currently crTransferDataInvocDataExt although the syntax
specification itself is named CyclicReportTransferDataExt.

Attached are 2 PDFs that contain my recommendations for fixing the problem in
sections 4.7.4.2 and D3.9. The first PDF shows the markup, the second is a
“clean” version. If you wish, I can also provide to you a copy of the
December draft of the CSTS SF with these proposed changes made in it.

The changes are summarized as follows:
      -          In 4.7.4.2.1 (General), the extension is correctly
      identified as an extension of the ‘data’ parameter.
      -          Section 4.7.2.2 is reworked to define the syntax of the data
      parameter (not the invocation extension parameters).The extension
      syntax is given a slightly different name (“
      CyclicReportTransferDataInvocDataExt” instead of “
      CyclicReportTransferDataExt”) to identify that it is the ‘data’
      parameter that is being extended and no the set of invocation
      parameters. This is also consistent with the naming of the OID for the
      parameter extension syntax in D3.9.
      -          In D3.9, I’ve split the TRANSFER-DATA ASN.1 into two
      “paragraphs” (one for the extension (new) parameters of the invocation
      and one for the “extension” of the ‘data’ parameter) in line with our
      convention of providing a separate section for each possible extension
      point of an operation.

Best regards,
John [attachment "201112 921x1r2[CR_data_parameter]-markup.pdf" deleted by
Yves Doat/esoc/ESA] [attachment "201112 921x1r2[CR_data_parameter]-clean.pdf"
deleted by Yves Doat/esoc/ESA]

This message and any attachments are intended for the use of the addressee or addressees only. The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its content is not permitted. If you received this message in error, please notify the sender and delete it from your system. Emails can be altered and their integrity cannot be guaranteed by the sender.

Please consider the environment before printing this email.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: Cyclic Report Procedure - TRANSFER-DATA
	updated.pdf
Type: application/pdf
Size: 284644 bytes
Desc: not available
Url : http://mailman.ccsds.org/pipermail/css-csts/attachments/20120220/50ef525d/CyclicReportProcedure-TRANSFER-DATAupdated-0001.pdf