[Css-csts] MD-CSTS W-0.8 on CWE

John Pietras john.pietras at gst.com
Wed Sep 2 17:12:18 EDT 2009


Francois,

Thank you for your detailed review of both documents. Please find my responses below. In general, I think the responses are pretty straightforward, but we can discuss them further if necessary.

 

Best regards,

John

 

________________________________

From: Lassere Francois [mailto:francois.lassere at cnes.fr] 
Sent: Thursday, August 27, 2009 8:50 AM
To: John Pietras; css-csts at mailman.ccsds.org
Subject: RE : [Css-csts] MD-CSTS W-0.8 on CWE

 

Dear John,

 

Please find here below a few comments or questions on your 2 following documents : "version 0.8 of the MD-CSTS White Book" and  "Baseline Functional Resources for the CCSDS Monitored Data Cross Support Transfer Service" :  

 

 

version 0.8 of the MD-CSTS White Book :

 

1- Section 2.5.2 Service Provision, end of Page 2-7 : "In performing the Notification procedure of the MD-CSTS,..."  We should find "Information Query" instead of "Notification" .

 

>> It has been corrected.

 

2- Section 2.6 Operational scenario, middle of page 2-10 : "The MD-CSTS provider invokes the TRANSFER-DATA operation to report the values of the two-second-interval monitored parameters : Each invocation[C1] of the TRANSFER-DATA operation for this instance of the Cyclic Report procedure transfer the following data :"

Reading this last sentence, I can understand that we need a TRANSFER DATA operation for each transfer of data.  What do you think of :  "One invocation of  the TRANSFER-DATA operation for this instance of the Cyclic Report procedure transfers periodically the following data :"

 

>> I understand and agree with your desire to convey the idea that the reporting is done periodically. However, where you have suggested inserting "periodically" implies that one single invocation of the operation results in multiple transfers of data. I have changed the sentence and the one before it to read: "Every two seconds, the MD-CSTS provider invokes the TRANSFER-DATA operation to report the values of the two-second-interval monitored parameters: Each periodic invocation of the TRANSFER-DATA operation for this instance of the Cyclic Report procedure transfers the following data:"  Is that satisfactory?

 

3- Same thing 5 lines below for the ten-second-interval monitored parameters.

 

>> I have made the same type of change as above ("Every ten seconds, ...).

 

4- Section 5.2.2 (relative distinguished name of a parameter) : the definition and syntax for a relative distinguished name of a parameter has already been given in 4.6.2

 

>> Section 5.2.2 has been simplified as follows: "Each monitored parameter value shall be identifiable by its relative distinguished name, the composition and syntax of which are defined in 4.6.2."

 

5- Section 5.3.2 (relative distinguished name of a notifiable event) : the definition and syntax for a relative distinguished name of a notifiable event has already been given in 4.7.2

 

>> Section 5.3.2 has been simplified as follows: "Each event shall be identifiable by its relative distinguished name, the composition and syntax of which are defined in 4.7.2."

 

 

Baseline Functional Resources for the CCSDS Monitored Data Cross Support Transfer Service :

 

1- introduction : "The CCSDS[C1]  will define a standard set of functional resources and monitored parameters... " Do you mean CCSDS or MD-CSTS ?

Same thing 10 lines below : "This baseline set can serve as a starting point for the development of the CCSDS[C2]  common monitored parameters catalog,..." 

 

>> I meant CCSDS, although I could have been more specific and said "CSTSWG". This is in concert with our agreement to not specify any actual monitored parameters in the MD-CSTS because compiling such a standard list could take a considerable amount of time and we did not want to delay publication of the MD-CSTS. 

 

Best regards.

 

François

 

 

	-----Message d'origine-----
	De : css-csts-bounces at mailman.ccsds.org [mailto:css-csts-bounces at mailman.ccsds.org] De la part de John Pietras
	Envoyé : lundi 10 août 2009 17:37
	À : css-csts at mailman.ccsds.org
	Objet : [Css-csts] MD-CSTS W-0.8 on CWE

	CSTSWG colleagues ---

	 

	I have uploaded to the CWE version 0.8 of the MD-CSTS White Book at URL http://cwe.ccsds.org/css/docs/CSS-CSTS/CWE%20Private/Future%20Services%20using%20Toolkit/MonitoredDataCSTS/MonitoredDataCSTS_W-0.8.doc

	 

	or http://tinyurl.com/MD-CSTS-W-0-8

	 

	The new version reflects the review comments received on V0.7 at the Colorado Springs meeting. Specific changes include:

	-   Removal of functional group specifics from section 2, replaced with functional resource terminology.

	-   Deletion of functional resource annexes A-E

	-   Changed "distinguished name" to "relative distinguished name"

	-   Modified the Operational Scenario to deal with functional resources.

	-   Modified the service composition table to reflect the version identification decisions.

	-   Combined the lists of cyclically-reported and queriable monitored parameters in section 4.

	-   Reference and external (TBD) standard for monitored parameters and event notifications, instead of the Annexes that previously held this information.

	 

	PLEASE NOTE that while this version reflects the notion of functional resources and their use in the naming of monitored parameters and notifiable events, this version DOES NOT incorporate the shorthand method for subscribing to those parameters in the START and GET operations. As described in my email of 7/24, using the shorthand method (in which only the parameter type is used in the subscription, but the full collection of instances of that type are reported) is not possible to perform without extending the associated procedures of the CSTS Framework. I had proposed the shorthand notation as a way of addressing potential issues in providing services to highly flexible missions with large numbers of possible monitored parameters, only a subset of which might be active for a given Service Package. However, since this shorthand method is still under analysis and discussion, I decided that it would be a good idea to post a version of the MD-CSTS specification that uses purely adopted procedures so that we will have that as a new baseline to work from. 

	 

	Best regards,

	John 

	 

	John Pietras

	GST, Inc. 

	7855 Walker Drive, Suite 200

	Greenbelt, MD 20770

	240-542-1155

	 

________________________________

 [C1]

 [C2]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ccsds.org/pipermail/css-csts/attachments/20090902/299131c2/attachment-0001.html


More information about the Css-csts mailing list