<font size=2 color=#004080 face="Calibri">Dear Erik and All,</font>
<p><font size=2 color=#004080 face="Calibri">Indeed we are aware of the
registry management policy that is being developed by Peter. In this
context, I’d like to mention that in a brainstorming held yesterday
with Wolfgang and Holger, we came up with a proposals about the use of
some OIDs in CSTS and the relevant registration approach. More specifically,
we were addressing the issue of the components building up the SI Identifier
. This topic will be comprehensively described by Wolfgang shortly, but
basically the idea is to make use of OIDs for all components, namely the
spacecraft identifier, the facility identifier and the ( meanwhile agreed)
functional resource associated to each given SLE or CSTS instance of service.</font>
<p><font size=2 color=#004080 face="Calibri">Also, welcoming a suggestion
from John, we thought that such elements will travel on the wire in their
“OID shape” , i.e. any mapping to a string , or a name, or whatever else,
will be done by the local applications, in the best suited way for the
operators. (Notice, that this applies to CSTS’s SIIs. Concerning
SLE’s SII, they will remain as are).</font>
<p><font size=2 color=#004080 face="Calibri">That approach implies, if
agreed , that the CSTS Specification Framework book can be updated with
such notion of SII - and the book can thus continue its path towards completion/publication.
However, the CSTS WG will rely on the coordination within the CSS
area for proper definition of the OIDs (other than the ones for FRs) and,
I assume, CSS will coordinate with SEA (or experts group, or…) for
proper registration approach. </font>
<p><font size=2 color=#004080 face="Calibri">In my view coordination on
this topic within CSS is required possibly already in the upcoming
teleconferences, and notably at Fall Meeting.</font>
<p><font size=2 color=#004080 face="Calibri">Also, I would like to address
John’s question about registration of ASN.1 modules. Actually, the
CSTS WG did request the registration of the OIDs of the ASN.1 modules from
CSTS SFW, and these are now visible, although in preliminary form , in
the SANA registry under APROVED REGISTRIES/CCSDS Object identifiers. There
it is possible to see (again, in preliminary form) the tree structure of
the OIDs, and notably the branching between SLE OIDs and CSTS OIDs. This
said, the registries need to be updated, to bring them in line with the
latest version of CSTS SFW, and the title shall be revised to something
more specific then “CCSDS Object identifiers”. </font>
<p><font size=2 color=#004080 face="Calibri">So, I would conclude that
also MD CSTS (and any other CSTS) shall register its ASN.1 OIDs in
the same way.</font>
<p><font size=2 color=#004080 face="Calibri">We can discuss this point
at next CSTS WG Telecon, scheduled by 24 June ( an invitation will
be sent shortly).</font>
<p><font size=2 color=#004080 face="Calibri">Kind regards,<br>
Margherita</font>
<p><font size=2 color=#004080 face="Calibri">-------------------------------------------------------------<br>
Margherita di Giulio<br>
Ground Station Back-end Section (HSO-GIB)<br>
European Space Agency ESA/ESOC<br>
Robert-Bosch-Str. 5<br>
D-64293 Darmstadt - Germany<br>
Tel: +49-6151-902779<br>
e-mail: Margherita.di.Giulio@esa.int<br>
</font><font size=2 face="sans-serif"><br>
</font>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">"Barkley, Erik
J (3970)" <erik.j.barkley@jpl.nasa.gov></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">John Pietras <john.pietras@gst.com>,
"CCSDS_CSTSWG (css-csts@mailman.ccsds.org)"
<css-csts@mailman.ccsds.org>, </font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">10/06/2015 01:42</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">[Css-csts] RE:
Updated MD-CSTS on CWE</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Sent by:
</font><font size=1 face="sans-serif">css-csts-bounces@mailman.ccsds.org</font>
<br>
<hr noshade>
<br>
<br>
<br><font size=2 color=#004080 face="Calibri">John, Margherita,</font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri">A note about the registries.
As you may be aware, the System Engineering Area is currently developing
what can be considered as a much more comprehensive registry management
policy. Especially so, in comparison to today's "laissez-faire"
registry policy that CCSDS has in place. Accordingly, the registry management
policy which was developed for the entire Cross Support Services Area will
likely need revision. I will take a look and provide some suggested
updates and/or at a minimum some insight as to what may need to be changed.
I hope to do so by next week at the latest.</font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri">Best regards,</font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri">-Erik</font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 face="Calibri"><b>From:</b> css-csts-bounces@mailman.ccsds.org
[</font><a href="mailto:css-csts-bounces@mailman.ccsds.org"><font size=2 face="Calibri">mailto:css-csts-bounces@mailman.ccsds.org</font></a><font size=2 face="Calibri">]
<b>On Behalf Of </b>John Pietras<b><br>
Sent:</b> Tuesday, June 02, 2015 1:07 PM<b><br>
To:</b> CCSDS_CSTSWG (css-csts@mailman.ccsds.org)<b><br>
Subject:</b> [Css-csts] Updated MD-CSTS on CWE</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">CSTSWG colleagues ---</font>
<br><font size=2 face="Calibri">I have just uploaded the latest version
of the MD-CSTS draft Recommended Standard to the CWE> </font><a href=http://cwe.ccsds.org/css><font size=2 color=blue face="Calibri"><u>Cross
Support Services Area (CSS)</u></font></a><font size=2 face="Calibri"> >
</font><a href="http://cwe.ccsds.org/css/docs/Forms/AllItems.aspx?View=%7B8045374D-F8E0-4356-83CA-993252A38FE8%7D"><font size=2 color=blue face="Calibri"><u>Documents</u></font></a><font size=2 face="Calibri">
> </font><a href="http://cwe.ccsds.org/css/docs/Forms/AllItems.aspx?RootFolder=%2Fcss%2Fdocs%2FCSS%2DCSTS&View=%7B8045374D-F8E0-4356-83CA-993252A38FE8%7D"><font size=2 color=blue face="Calibri"><u>CSS-CSTS</u></font></a><font size=2 face="Calibri">
> </font><a href="http://cwe.ccsds.org/css/docs/Forms/AllItems.aspx?RootFolder=%2Fcss%2Fdocs%2FCSS%2DCSTS%2FCWE%20Private&View=%7B8045374D-F8E0-4356-83CA-993252A38FE8%7D"><font size=2 color=blue face="Calibri"><u>CWE
Private</u></font></a><font size=2 face="Calibri"> > 2 - MD CSTS RED-1
Review material folder at URL</font>
<br><a href="http://cwe.ccsds.org/css/docs/CSS-CSTS/CWE%20Private/2%20-%20MD%20CSTS%20RED-1%20Review%20material/MD-CSTS-922x1r1_3-150602.doc"><font size=2 color=blue face="Calibri"><u>http://cwe.ccsds.org/css/docs/CSS-CSTS/CWE%20Private/2%20-%20MD%20CSTS%20RED-1%20Review%20material/MD-CSTS-922x1r1_3-150602.doc</u></font></a>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">This update:</font>
<br><font size=2 face="Calibri">- Includes
updates resulting from comments from Wolfgang Hell and Tim Ray on the previous
version;</font>
<br><font size=2 face="Calibri">- Aligns
with all changes to the CSTS SFW since the Spring meeting;</font>
<br><font size=2 face="Calibri">- Aligns
the Functional Resource references in section 2 and annex F with the set
of FRs as currently defined; and</font>
<br><font size=2 face="Calibri">- Fixes
various typographical errors. </font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">Assuming that there are no more technical
change in the CSTS SFW to the procedures used by the MD-CSTS, the only
incomplete aspect of the MD-CSTS is with respect to SANA Functional Resource
registry. This registry has not been created yet, so it cannot be referred
to by URL.</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">Note that previous versions of the MD-CSTS
also stated that the MD-CSTS-specific ASN.1 modules would be registered
with SANA, but I don’t know if that is necessary – the Recommended Standard
itself is registered with SANA, and the ASN.1 modules being contained normatively
may be sufficient. The specification of the CSTS SFW ASN.1 modules make
no reference to being registered with SANA. If they are going to
be registered, then the MD-CSTS (and all other CSTSes) should register
their SN.1 modules in a similar manner. But in the meantime, I have removed
any mention in the MD-CSTS regarding registration of the ASN.1 modules.</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">Best regards,</font>
<br><font size=2 face="Calibri">John</font>
<br><font size=2 face="Calibri"> </font><tt><font size=2>_______________________________________________<br>
Css-csts mailing list<br>
Css-csts@mailman.ccsds.org<br>
</font></tt><a href="http://mailman.ccsds.org/cgi-bin/mailman/listinfo/css-csts"><tt><font size=2>http://mailman.ccsds.org/cgi-bin/mailman/listinfo/css-csts</font></tt></a><tt><font size=2><br>
</font></tt>
<br><PRE>This message and any attachments are intended for the use of the addressee or addressees only.
The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its
content is not permitted.
If you received this message in error, please notify the sender and delete it from your system.
Emails can be altered and their integrity cannot be guaranteed by the sender.
Please consider the environment before printing this email.
</PRE>