[Css-csts] Re-Delivery of the SFW Package

[Wolfgang Hell]

Dear members of the CSTS WG,

I have just uploaded the SFW package updated in accordance with the 
outcome of last week's meeting. The missing parameter that controls the 
latency limit in case the BDD procedure is operated in real-time mode 
has been added to the configuration parameters of that procedure. This 
parameter is also specified to me modifiable while the service instance 
using this procedure is bound. The addition of this parameter triggered 
a number of changes in the ASN.1, also of one type that is used by all 
procedures permitting dynamic updating of configuration parameters. 
Fortunately enough, the change is such that it is backwards compatible, 
i.e. an implementation based on the previous ASN.1 specification is 
interoperable with an implementation based on the ASN.1 of the SFW 
re-delivery as long as the BDD procedure is not used. Because of the 
changes in the ASN.1, the re-delivery contains also a new ASN.1 text 
file. This contains the two OIDs that were missing in the previous 
version and all changes that were neede to accommodate the missing BDD 
configuration parameter. In addition, the formatting is now more human 
reader friendly.

The addition of the missing parameter required also a change of the OID 
tree. For this reason, the re-delivery also contains the OID 
spreadsheet. Figure K-4 in the SFW has been changed accordingly.

As agreed with Margherita I have also changed the tables in annex L to 
cure the ambiguity that Yves observed while working on the scenarios. 
When we generate the Functional Resources XML, we will have to take this 
into account. For the production-status issue that Yves also addresses 
in his scenarios document, I did not introduce any change in the SFW for 
now. We shall consider this point carefully and make sure that one can 
use the MD service also to query the production status of SLE services 
and they do not match with the CSTS production convention.

I did not touch the list of Observer Agencies. As far as I can tell, 
BITTT is actually covered by the fourth entry in that list. In any case, 
the secretariat will certainly make sure that the lists will be 
up-to-date in the official Red-2 Book.

The re-delivery of the SFW contains further purely editorial updates. To 
help a rapid review of the more substantive changes, I have accepted all 
purely editorial fixes and therefore they are not highlighted as changes 
in the re-delivery. If you feel that you need to see each and every 
change, please use the 'compare' tool of Word.

As stated in the minutes of last week's meeting (and as promised to Tom 
Gannet), I shall provide the revised delivery to the secretariat no 
later than Monday, April 14. Therefore, if you detect any problem with 
the updates please let me know asap.

You find the zip-archive on the CWE at
Cross Support Services Area (CSS) <http://cwe.ccsds.org/css>> Documents 
<http://cwe.ccsds.org/css/docs/Forms/AllItems.aspx?View=%7B8045374D-F8E0-4356-83CA-993252A38FE8%7D>> 
CSS-CSTS 
<http://cwe.ccsds.org/css/docs/Forms/AllItems.aspx?RootFolder=%2Fcss%2Fdocs%2FCSS%2DCSTS&View=%7B8045374D-F8E0-4356-83CA-993252A38FE8%7D>> 
CWE Private 
<http://cwe.ccsds.org/css/docs/Forms/AllItems.aspx?RootFolder=%2Fcss%2Fdocs%2FCSS%2DCSTS%2FCWE%20Private&View=%7B8045374D-F8E0-4356-83CA-993252A38FE8%7D>> 
CSTS Framework and Concept
and the file name is 921x1r2[Draft_20140408].zip

Best regards,
Wolfgang
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ccsds.org/pipermail/css-csts/attachments/20140410/3f22b76d/attachment.html