[Css-csts] Status of MD-CSTS

Mon Jun 22 18:28:22 UTC 2015

Peter,
I failed to repeat all of the "background information" regarding annexes F (MD-CSTS) and  L (CSTS SFW). Both annexes are informative only - they both point to the SANA registry as the repository of the full, true, normative set of parameters.

The reason for the existence of annex L in the CSTS SFW is (a) to describe the contents of the SANA parameter registry entries and (b) to provide examples (in this case, 2) of those parameters.

The reason for Annex F in MD-CSTS is a little  bit different. There is an extensive Operational Scenario  in section 2 of the MD-CSTS that walks through how an instance of MS-CSTS is configured, bound, and operated. Since there are a number of variations of the way a single instance of MD-CSTS can be used, the scenario uses  a number of different parameters of different functional resources (just to make the scenario fun!). To keep the operation scenario from totally sinking in the details, the parameters and events used in the scenario use OID names (e.g., {few401SpaceLinkCarrierXmit}) instead of the OIDs themselves, and aren't defined in the scenario itself. Annex F provides that lower level of detail for anyone who wants to see how the whole thing works top-to-bottom, without having to go "outside the book" to the SANA registry to get the lowest level of those details. A secondary benefit of putting Annex F in the MD-CSTS is that the Operational Scenario can remain stable with respect to the example set of FRs and parameters in Annex F, and not have to be changed (or become incorrect) if (for whatever reason) the normative set of FRS and parameters might change in the future. The Operational Scenario and Annex F remain synchronized to describe the content, if not necessarily the actual FR types and parameters.

We have written annexes F and L to be consistent with the SANA registry as we conceive of it today, and with luck they will remain consistent, at least with respect to the FRs and parameters that we chose to use in those annexes. But we can't know that that will always be the case, s both Annex F and Annex L have the appropriate disclaimers that these are examples, and that one must always go to the SANA registry to get the real deal.

So - bottom line - I believe that we are already doing essentially what you have suggested. The question that I was attempting to raise in my email below was how much the _representation_ of the SANA registry info in MD-CSTS Annex F needed to look like that of CSTS SFW Annex L, in light of my concern that the Annex L style of representation is would bloat the MD-CSTS book a bit more.

Best always,
John

From: Shames, Peter M (312B) [mailto:peter.m.shames at jpl.nasa.gov]
Sent: Monday, June 22, 2015 1:53 PM
To: John Pietras
Subject: Re: [Css-csts] Status of MD-CSTS

Hi John,

Would it make sense to have the structure of the parameters space defined in the BB, but to have all of these parameters, in all their gory detai, documented in an exetnsible registry?

As you probably know we are working on a common set of organization, person, OID, and other registries.  Erik has seen this, I do not know that you have.  FYI I will forward the current set to you in a moment.  I've been staying out of the working sessions, but wanted you to be aware of what we are thinking and where we are headed.

Always open to feedback.

Thanks, Peter

From: <css-csts-bounces at mailman.ccsds.org<mailto:css-csts-bounces at mailman.ccsds.org>> on behalf of John Pietras <john.pietras at gst.com<mailto:john.pietras at gst.com>>
Date: Monday, June 22, 2015 at 10:45 AM
To: CSTS-WG <css-csts at mailman.ccsds.org<mailto:css-csts at mailman.ccsds.org>>
Subject: [Css-csts] Status of MD-CSTS

CSTSWG colleagues ---
One of the topics for this coming Tuesday's telecon is that status of the MD-CSTS book. I'd like to remind all of you that the latest version fo the MD-CSTS was posted to the CWE> 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> > 2 - MD CSTS RED-1 Review material folder at URL
http://cwe.ccsds.org/css/docs/CSS-CSTS/CWE%20Private/2%20-%20MD%20CSTS%20RED-1%20Review%20material/MD-CSTS-922x1r1_3-150602.doc
on 2 June. As I noted when I posted the draft, this update:
*         Includes updates resulting from comments from Wolfgang Hell and Tim Ray on the previous version;
*         Aligns with all changes to the CSTS SFW since the Spring meeting;
*         Aligns the Functional Resource references in section 2 and annex F with the set of FRs as currently defined; and
*         Fixes various typographical errors.

The 2 June 205 version of the MD-CSTS is still consistent with all normative aspects of the most-recent version of the CSTS SFW, which Wolfgang uploaded earlier today. There is only one normative item that needs to be completed before the MD-CSTS can be published as a Blue Book  (assuming that everything else about the book is acceptable):  the MD-CSTS references the SANA Functional Resource registry. Since this registry has not been created yet, there is not yet a URL for the registry that can be inserted into the MD-CSTS.

There is a second possible issue that I would like to discuss at Wednesday's webex session: the representation of the managed parameters for the example set of Functional Resources presented in annex F of the MD-CSTS. Briefly summarized, the MD-CSTS lists all parameters of for a Functional Resource type in a single table, where each parameter is represented by a row that contains the parameter name, description, type, range of values and engineering units, and OID of the parameter.
The comparable section of the CSTS SFW is annex L, which presents the FR parameters by giving each parameter its own table, which contains the title, semantic definition, name in the form of an object identifier, syntax specification, value range, engineering unit(s), a flag indicating if the definition has been deprecated, the authorizing entity, and the creation date.
I would like to discuss whether the parameter presentation in annex F of the MD-CSTS should adopt that of the CSTS SFW annex L. In general, I believe that it should be brought into alignment, since CSTS SFW annex L covers all of the information  addressed by the SANA registry.
However, I am concerned that changing the representation in this way will cause the size of annex F to balloon. Annex F is currently 13 page long, which is almost 10% of the 122-page length of the whole MD-CSTS. Annex F address 19 parameters and events (compared to 2 parameters addressed by CSTS SFW Annex L), and I estimate that going to the one-table-per-parameter approach used in Annex L would lengthen Annex F to 17 or 18 pages total.
I look forward to discussing this on Wednesday.
Best regards,
John

-----Original Appointment-----
From: Margherita di Giulio/esoc/ESA [mailto:Margherita.di.Giulio at esa.int]
Sent: Thursday, June 11, 2015 11:16 AM
To: Margherita di Giulio/esoc/ESA; css-csts at mailman.ccsds.org<mailto:css-csts at mailman.ccsds.org>
Subject: [Css-csts] Invitation: CSTS WG - Teleconference/ WebEx (24 Jun 16:00 CEDT)
When: Wednesday, June 24, 2015 4:00 PM-5:30 PM W. Europe.
Where:

Agenda:
1) Progress on CSTS SFW, further changes conceived after the Spring Mtg
2) About newly introduced OIDs
3) Approach and policies for SANA registration
4) Status of MD CSTS
5) Coordination on prototyping activities
6) Status of other CSTS products
7) AOB
Margherita Di Giulio invites you to an online meeting using WebEx.

Meeting Number: 840 359 549
Meeting Password: csts1234

-------------------------------------------------------
To join this meeting (Now from mobile devices!)
-------------------------------------------------------
1. Go to https://esa-meeting.webex.com/esa-meeting/j.php?MTID=m23fa471b0f240f50ca736bc7f8c3f5cd
2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: csts1234
4. Click "Join".
5. Follow the instructions that appear on your screen.

-------------------------------------------------------
Audio conference information
-------------------------------------------------------
Call-in toll number (UK): +44-203-478-5289
Global call-in numbers: https://esa-meeting.webex.com/esa-meeting/globalcallin.php?serviceType=MC&ED=377834297&tollFree=0

Access code:840 359 549

http://www.webex.com

IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and any documents and other materials exchanged or viewed during the session to be recorded. By joining this session, you automatically consent to such recordings. If you do not consent to the recording, discuss your concerns with the meeting host prior to the start of the recording or do not join the session. Please note that any such recordings may be subject to discovery in the event of litigation. << File: pic20268.gif >>  << File: ATT00001.htm >>  << File: c171554.ics >>  << File: ATT00002.txt >>

________________________________

Spam<https://filter.gst.com/canit/b.php?i=01OHtRVlK&m=551bd923486f&c=s>
Not spam<https://filter.gst.com/canit/b.php?i=01OHtRVlK&m=551bd923486f&c=n>
Forget previous vote<https://filter.gst.com/canit/b.php?i=01OHtRVlK&m=551bd923486f&c=f>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/css-csts/attachments/20150622/186fbea8/attachment.html>