[Css-csts] RE: Impacts on MD-CSTS (was RE: please help)
Ray, Timothy J. (GSFC-5830)
timothy.j.ray at nasa.gov
Mon Dec 12 17:56:16 EST 2011
That sounds good. Thanks John!
Tim
-----Original Message-----
From: John Pietras [mailto:john.pietras at gst.com]
Sent: Friday, December 09, 2011 4:22 PM
To: Ray, Timothy J. (GSFC-5830)
Cc: css-csts at mailman.ccsds.org
Subject: Impacts on MD-CSTS (was RE: please help)
Tim,
I've made a pass through the draft Monitored Data CSTS to see what changes would result from the latest round of updates to the CSTS Framework. In summary, since the MD service is constructed of procedures that are all adopted from the Framework, once those updated procedures are implemented in the prototype there should be no additional changes required at the service level. Remember that it's not just the Information Query, Cyclic Report, and Notification procedures that have been updated (in the Framework) since the spring, but also Association Control (AC), the interactions between the AC procedure and the other procedures, and the service state machine.
Here's a section-by-section overview of the changes that will have to be made to the MD-CSTS specification before it is ready to be released for Red Book review:
Section 1 The only changes that I can see is that since the notions of functional resource identifier, functional resource instance, and functional resource type are being adopted as part of the Framework, their definitions would move from "Terms Defined in this Specification" to "Terms Defined in the CSTS FW". Also, references will need to be updated.
Section 2 A fair amount of work would have to go here to realign the terminology. It will need to reflect whatever decisions we make about the issue that I raised in my email yesterday regarding what is actually published by the service provider and what is subscribed to by the service user, how that relates to how the monitored parameters and notifiable events are defined and assigned OIDs, and how list names are also formed and used.
Section 3 This section is normative, but since all of the procedures are adopted from the Framework and not derived, there is no change to the specification of the procedures. The State Machine subsection needs to refer to the "state machine for a CSTS with a stateful prime procedure" instead of "state machine for a CSTS with a started prime procedure".
Section 4 This section includes the specification of what constitutes the names that are to be published by the service provider and subscribed to by the user. In particular, it needs to distinguish between the published names (which are pairs of object identifiers) and the individual object identifiers.
Annex A This annex specifies the service Object Identifiers, and is not affected by the recent changes.
Best regards,
John
-----Original Message-----
From: css-csts-bounces at mailman.ccsds.org [mailto:css-csts-bounces at mailman.ccsds.org] On Behalf Of Ray, Timothy J. (GSFC-5830)
Sent: Tuesday, December 06, 2011 10:37 AM
To: css-csts at mailman.ccsds.org
Subject: 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]
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] 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] 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
More information about the Css-csts
mailing list