[Css-csts] RE: please help

Thu Dec 15 10:28:39 EST 2011

Margherita,

I actually don't think that updating the MD-CSTS book itself is a prerequisite to updating the Prototype software. As I said in my earlier note, since the MD service fully adopts the three procedures from the Framework, once Yves has those completed, the coding can begin. As long as the Prototype can deal with parameter/event names (and list names) that are composed of pairs of object identifiers (OIDs) (the first of which might optionally be NULL) then the code should be viable. 

However, in my earlier assessment of what has to be done to make the MD book ready for Red-1 review, I forgot that the specification must now address how the object identifiers are to be created and registered with SANA, and that the current baseline set of monitored parameters (along with their type definitions and OIDs) is to be included in an informative Annex to the book. For this the WG will need to define a naming tree structure for the OIDs. I am not aware of this having been discussed within the WG. Such a naming tree structure will have to include:

a)      OIDs for monitored/queried parameters and notifiable events. Off the top of my head, I think that this would be organized by functional resource type; e.g., there would be nodes for forward carrier, forward subcarrier, etc., and under those nodes would be the monitored parameter and notifiable event OIDs. The structure would have to make provisions for extension for new CCSDS-standard functional resource types and (I think) Agency-specific extensions. Regarding Agency-specific extensions, we need to think about whether we allow for just extension at the top of the tree (i.e., every Agency would have to replicate the functional resource types within its subtree) or extension within each standard functional resource type. (I tend to favor the latter approach, because it keeps the Agency extensions as "standard" as possible).

b)      OIDs for functional resource *instances*. I think that the FR instances are unique to an Agency, Complex, or even a Service Agreement. My off-the-top-of-my-head suggestion is to put an 'instances' node under each FR type node in the standard naming tree, and under that node have Agency subnodes. The Agencies would then be delegated responsibility for managing those subnodes (e.g., defining Agency-wide RF instance identifiers, allocating their definition to Complexes that belong to the Agency, or some combination). Whether or not the actual FR instance OIDs are expected to be registered with  SAN is a topic for discussion.

c)       OIDs for list names. Again, I think that the actual list names should be left to the Agencies or their Complexes. The CCSDS-standard naming tree could establish a top-level node for list names (or should there be top-level nodes for each type of list name: cyclically-reported parameters, queried parameters, and notifiable events?)

Regarding the monitored/queried parameters, Wolfgang already has his candidate list of parameters in Monitored Data Dictionary 01.doc*. I have a number of questions about this document, but we can certainly use it as the baseline for the naming tree to be used for the Prototyping effort [* I have a copy of this document, but I can't figure out how I got it. I couldn't find it on the CSTS CWE, and I couldn't find an email with it as an attachment. I have posted a copy in the

Cross Support Services Area (CSS) <http://cwe.ccsds.org/css>  > Documents <http://cwe.ccsds.org/css/docs/Forms/AllItems.aspx?View=%7B8045374D%2DF8E0%2D4356%2D83CA%2D993252A38FE8%7D&>  > CSS-CSTS <http://cwe.ccsds.org/css/docs/Forms/AllItems.aspx?RootFolder=%2Fcss%2Fdocs%2FCSS%2DCSTS&View=%7B8045374D%2DF8E0%2D4356%2D83CA%2D993252A38FE8%7D&>  > CWE Private <http://cwe.ccsds.org/css/docs/Forms/AllItems.aspx?RootFolder=%2Fcss%2Fdocs%2FCSS%2DCSTS%2FCWE%20Private&View=%7B8045374D%2DF8E0%2D4356%2D83CA%2D993252A38FE8%7D&>  > Future Services using Toolkit <http://cwe.ccsds.org/css/docs/Forms/AllItems.aspx?RootFolder=%2Fcss%2Fdocs%2FCSS%2DCSTS%2FCWE%20Private%2FFuture%20Services%20using%20Toolkit&View=%7B8045374D%2DF8E0%2D4356%2D83CA%2D993252A38FE8%7D&>  > MonitoredDataCSTS

folder at URL

http://cwe.ccsds.org/css/docs/CSS-CSTS/CWE%20Private/Future%20Services%20using%20Toolkit/MonitoredDataCSTS/Monitored%20Data%20Dictionary%2001.doc

] 

Best regards,

John

From: css-csts-bounces at mailman.ccsds.org [mailto:css-csts-bounces at mailman.ccsds.org] On Behalf Of Margherita.di.Giulio at esa.int
Sent: Thursday, December 15, 2011 6:00 AM
To: Ray, Timothy J. (GSFC-5830)
Cc: Lassere Francois; css-csts-bounces at mailman.ccsds.org; css-csts at mailman.ccsds.org
Subject: RE: [Css-csts] RE: please help

Dear Tim and All, 
let me try to recap the sequence of steps and the relevant schedule: 

1) the updated CSTS Spec. Framework, containing the Return Services ONLY shall be ready by end February. Yves is confident that he will mange to include all the latest changes ( dual-object-identifier etc) and complete the Book by that time. This will be submitted to the Secretariat for  being published as Red-2. 

2) at this time, the enhancement to  the CSTS prototype can start (the framework prototype with the dummy services). We will continue the work as before, i.e. ESA enhancing the Provider side and NASA the User side. I assume (I hope) that most of the work can be carried our during the March/April time frame, such that at the Spring Meeting in Darmstadt some interoperability tests can be run . I know that the schedule is tight, but we should make all efforts  in order to start the engineering work as soon as the CSTS Framework is available. For Tim: is this feasible on your side? 

3) in parallel the MD Service Book shall be updated. John has highlighted the chapters that will be affected. For John: would you be available for updating the book in the a.m time frame (I mean, as soon as  the CSTS SF Book is deemed to be complete and is sent to Secretariat)? How long do you estimate that this task will take? 

4)   when the MD Service Book is finalised, the enhancement to the MD Service Prototype can start. 

Obviously, the two books  (Framework and MD Service) will further evolve, due the the upcoming Review of the Red-2 version. However, I think that we shall not wait until the Review is complete, as this  will take quite some time. 
Actually, I am convinced that the "enhancement" of Prototypes will provide some important feedback during the review process. 
Further changes  will/may be required to the prototype after the Review is completed. But this we will tackle when the time comes. 

Kind regards,
Margherita 

-------------------------------------------------------------
Margherita di Giulio
Ground Station Back-end Section (HSO-GIB)
European Space Agency ESA/ESOC
Robert-Bosch-Str. 5
D-64293 Darmstadt - Germany
Tel: +49-6151-902779
e-mail: Margherita.di.Giulio at esa.int

From: 

"Ray, Timothy J. (GSFC-5830)" <timothy.j.ray at nasa.gov> 

To: 

Lassere Francois <Francois.Lassere at cnes.fr>, "css-csts at mailman.ccsds.org" <css-csts at mailman.ccsds.org> 

Date: 

13/12/2011 16:44 

Subject: 

RE: [Css-csts] RE: please help 

Sent by: 

css-csts-bounces at mailman.ccsds.org

________________________________

Ok.  Thank you for the update Francois!

Tim

-----Original Message-----
From: Lassere Francois [mailto:Francois.Lassere at cnes.fr <mailto:Francois.Lassere at cnes.fr> ] 
Sent: Tuesday, December 13, 2011 3:15 AM
To: Ray, Timothy J. (GSFC-5830); css-csts at mailman.ccsds.org
Subject: RE: [Css-csts] RE: please help

Hi Tim,

I have asked for some budget but I dont know, at the moment, if we will have this budget in time to be able to update the prototype for the spring meetings.
Best regards.

François

-----Message d'origine-----
De : css-csts-bounces at mailman.ccsds.org [mailto:css-csts-bounces at mailman.ccsds.org <mailto:css-csts-bounces at mailman.ccsds.org> ] De la part de Ray, Timothy J. (GSFC-5830)
Envoyé : mardi 6 décembre 2011 16:37
À : css-csts at mailman.ccsds.org
Objet : RE: [Css-csts] RE: please help

Thanks to everyone for the timely responses!

I agree with John and Yves that our prototypes should match the updated specifications of the Framework and Monitored Data service (that we may be able to produce within the next few weeks).

ESA/CNES: Do you agree in principle?  If so, will you be able to update your prototype in time to support an inter-operability test at the Spring meetings in Darmstadt?

Best regards,
Tim

-----Original Message-----
From: Yves.Doat at esa.int [mailto:Yves.Doat at esa.int <mailto:Yves.Doat at esa.int> ]
Sent: Tuesday, December 06, 2011 8:49 AM
To: John Pietras
Cc: css-csts at mailman.ccsds.org; css-csts-bounces at mailman.ccsds.org; Lassere Francois; Ray, Timothy J. (GSFC-5830)
Subject: RE: [Css-csts] RE: please help

Dear John,

Please note that I consider that the NOTIFY operation needs as well to be updated (I wait feed-back from the WG).

Best regards
Yves

 From:       "John Pietras" <john.pietras at gst.com>

 To:         "Lassere Francois" <Francois.Lassere at cnes.fr>, "Ray, Timothy J. (GSFC-5830)" <timothy.j.ray at nasa.gov>

 Cc:         css-csts at mailman.ccsds.org

 Date:       06/12/2011 14:46

 Subject:    RE: [Css-csts] RE: please help

 Sent by:    css-csts-bounces at mailman.ccsds.org

Tim and Francois,
In order to be meaningful, the prototypes should be updated to use the dual-object-identifier form of naming that we agreed to in Boulder. Yves has an draft of the Framework that contains the updated versions  the Cyclic Report and Information Query procedures, GET operation, and associated ASN.1 modules. He's asked me to review the updated version of the Notification procedure, and I'm hoping do that in the next 2 days. With those changes in place, he should be able to generate a draft version of the FW and generate the ASN.1 text modules that have the updates pertinent to the MD-CSTS.

I will review the MD-CSTS spec to see what, if any, impacts there are from these latest changes. I will try to do that this week.

Best regards,
John

From: css-csts-bounces at mailman.ccsds.org [ mailto:css-csts-bounces at mailman.ccsds.org <mailto:css-csts-bounces at mailman.ccsds.org> ] On Behalf Of Lassere Francois
Sent: Tuesday, December 06, 2011 8:05 AM
To: 'Ray, Timothy J. (GSFC-5830)'
Cc: css-csts at mailman.ccsds.org
Subject: [Css-csts] RE: please help

Hi Tim,

The upgrades we have made recently (fall 2011) were made with the current version of specifications of the framework (something like 0.22). Is it really what you want ?
Best regards.

François

De : css-csts-bounces at mailman.ccsds.org [ mailto:css-csts-bounces at mailman.ccsds.org <mailto:css-csts-bounces at mailman.ccsds.org> ] De la part de Ray, Timothy J.
(GSFC-5830)
Envoyé : mardi 6 décembre 2011 00:25
À : css-csts at mailman.ccsds.org
Objet : [Css-csts] please help

Hi,

I have a short window of time to work on upgrading the NASA software prototype of the Monitored Data Service - in about a month the window may close and not re-open until after the Spring meetings.

To ensure that inter-operability testing goes smoothly, we have to make sure
that all of the prototypes use the same specifications!   With that in mind,
I am requesting that someone (Francois?) please send me the proper version of the specifications for the Framework and Monitored Data Service.

Plus (please, please, please, please) an ASCII TEXT version of all the ASN.1 definitions (Cyril?).

Best regards,
Tim_______________________________________________
Css-csts mailing list
Css-csts at mailman.ccsds.org
http://mailman.ccsds.org/cgi-bin/mailman/listinfo/css-csts <http://mailman.ccsds.org/cgi-bin/mailman/listinfo/css-csts> 

_______________________________________________
Css-csts mailing list
Css-csts at mailman.ccsds.org
http://mailman.ccsds.org/cgi-bin/mailman/listinfo/css-csts <http://mailman.ccsds.org/cgi-bin/mailman/listinfo/css-csts> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ccsds.org/pipermail/css-csts/attachments/20111215/c74ecf4d/attachment-0001.htm