<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.ms-sitemapdirectional
{mso-style-name:ms-sitemapdirectional;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Consolas","serif";}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Dear Margherita,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I think that getting the registry established, even though it’s final content is not “perfect”, is an excellent idea.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Regarding the ‘controllable’ field, I suggest that we use the term “configurable” for the field (attribute). “Controllable” has the connotation of real-time
control, i.e., being able to be changed during the execution of the service package. All configurable attributes have to be declared by CCSDS (they are what have to be managed in order for the functional resource to operate properly). All configurable parameters
are also candidates for being controllable, but each Agency/Complex/Provider CSSS will have to decide which subset of those configurable parameters (if any) it actually allows to be changed during service package execution (or as part of an Event Sequence).
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">As far as the future Service Control CSTS is concerned, all configurable parameters will be potentially changeable, but if an Agency/Complex/Provider CSSS does
not support real-time control of a given parameter an EXECUTE-DIRECTIVE invocation to change the value of that parameter would fail with an ‘invalid Functional Resource parameter’ diagnostic.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">John<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Margherita.di.Giulio@esa.int [mailto:Margherita.di.Giulio@esa.int]
<br>
<b>Sent:</b> Wednesday, July 08, 2015 6:20 AM<br>
<b>To:</b> John Pietras<br>
<b>Cc:</b> CCSDS_CSTSWG (css-csts@mailman.ccsds.org)<br>
<b>Subject:</b> Re: [Css-csts] updated MD-CSTS on CWE<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif"">Dear John,<br>
many thanks for this update. <br>
Concerning the URL of the SANA Registry of Functional Resources, I was thinking of contacting the SANA engineer, in order to "move" our beta version to the final destination in the Registry. In fact, although the FR table needs to be reworked to a certain
extent, I think the prototyped version meets our expectation about the shape of the registered items.<br>
In this way, at least the URL can be definitively established - and possibly before the MD CSTS gets finally to the top of the editor's queue ( and so, we may have this last-minute change done by the editor).<br>
As to the work required to complete the content of the registration, I will address that with Wolfgang and Holger. Basically, I think we need to add one field to the parameter's entry, to state if the parameter is controllable, and , most demanding, we need
to bring the FRs, parameters and events in line with the last version of the FR/parameter model.<br>
<br>
With this version of MD CSTS I think the implementers of the Prototype (CNES and ESA) can start looking into the changes with respect to the old version of the the prototype. Then, the actual implementation can start only when the Framework API will be completed
(hopefully by end of September).<br>
<br>
Kind regards,<br>
Margherita<br>
<br>
<br>
-------------------------------------------------------------<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: <a href="mailto:Margherita.di.Giulio@esa.int">Margherita.di.Giulio@esa.int</a><br>
<br>
<span style="color:#990099"><a href="mailto:-----css-csts-bounces@mailman.ccsds.org">-----css-csts-bounces@mailman.ccsds.org</a> wrote: -----</span><o:p></o:p></span></p>
<div>
<div style="border:none;border-left:solid black 1.5pt;padding:0in 0in 0in 4.0pt">
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif"">To: "CCSDS_CSTSWG (<a href="mailto:css-csts@mailman.ccsds.org">css-csts@mailman.ccsds.org</a>)" <<a href="mailto:css-csts@mailman.ccsds.org">css-csts@mailman.ccsds.org</a>><br>
From: John Pietras <br>
Sent by: <a href="mailto:css-csts-bounces@mailman.ccsds.org">css-csts-bounces@mailman.ccsds.org</a><br>
Date: 07/07/2015 03:17PM<br>
Subject: [Css-csts] updated MD-CSTS on CWE<o:p></o:p></span></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">CSTSWG colleagues ---<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">I have uploaded an updated version (R-1.4) of the MD-CSTS to the CWE>
<a href="http://cwe.ccsds.org/css">Cross Support Services Area (CSS)</a> > <a href="http://cwe.ccsds.org/css/docs/Forms/AllItems.aspx?View=%7B8045374D-F8E0-4356-83CA-993252A38FE8%7D">
Documents</a> > <a href="http://cwe.ccsds.org/css/docs/Forms/AllItems.aspx?RootFolder=%2Fcss%2Fdocs%2FCSS%2DCSTS&View=%7B8045374D-F8E0-4356-83CA-993252A38FE8%7D">
CSS-CSTS</a> > <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">
CWE Private</a> > <span class="ms-sitemapdirectional">2 - MD CSTS RED-1 Review material folder at URL</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><a href="http://cwe.ccsds.org/css/docs/CSS-CSTS/CWE%20Private/2%20-%20MD%20CSTS%20RED-1%20Review%20material/MD-CSTS-922x1r1_4.zip.zip">http://cwe.ccsds.org/css/docs/CSS-CSTS/CWE%20Private/2%20-%20MD%20CSTS%20RED-1%20Review%20material/MD-CSTS-922x1r1_4.zip.zip</a><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">The updates reflect the outcome of the discussion of the MD-CSTS during the CSTSWG WebEx on 24 June 2015. Specifically:<o:p></o:p></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif"">1.</span><span style="font-size:7.0pt">
</span><span style="font-size:10.0pt;font-family:"Verdana","sans-serif"">A reference ([3]) to the “SANA Functional Resources registry: TBD” has been added to the References section (1.10), and references to that SANA registry throughout the book now point to
reference [3]. <o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif"">2.</span><span style="font-size:7.0pt">
</span><span style="font-size:10.0pt;font-family:"Verdana","sans-serif"">Wording has been added to Annex F, Example Functional Resource Type Object Identifier Registry, explaining that the parameter attributes in annex F are the subset of the SANA registry
parameter attributes that are most useful in understanding the Operational Scenario in 2.5.
<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">With these updates the book is as complete and correct as possible until the time that the SANA FR registry is established, at which time the “TBD” of reference [3] can be replaced
by the actual URL of the SANA FR registry.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Note that the file that has been uploaded to the CWE is a zip file that contains both the draft Recommended Standard itself and a plain text version of the two MD-CSTS-specific
ASN.1 modules. These ASN.1 modules have not changed since the previous version, but I have included them for completeness.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Best regards,<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">John<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New"">_______________________________________________<br>
Css-csts mailing list<br>
<a href="mailto:Css-csts@mailman.ccsds.org">Css-csts@mailman.ccsds.org</a><br>
<a href="http://mailman.ccsds.org/cgi-bin/mailman/listinfo/css-csts">http://mailman.ccsds.org/cgi-bin/mailman/listinfo/css-csts</a></span><span style="font-size:10.0pt;font-family:"Verdana","sans-serif""><o:p></o:p></span></p>
</div>
</div>
</div>
<pre>This message and any attachments are intended for the use of the addressee or addressees only.<o:p></o:p></pre>
<pre>The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its<o:p></o:p></pre>
<pre>content is not permitted.<o:p></o:p></pre>
<pre>If you received this message in error, please notify the sender and delete it from your system.<o:p></o:p></pre>
<pre>Emails can be altered and their integrity cannot be guaranteed by the sender.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Please consider the environment before printing this email.<o:p></o:p></pre>
<div>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-size:13.5pt;color:black;background:white">
<hr size="2" width="100%" align="center">
</span></div>
<p class="MsoNormal"><span style="font-size:13.5pt;color:black;background:white"><br>
<a href="https://filter.gst.com/canit/b.php?i=01ONKuKAX&m=df31bf618270&c=s" target="canit_note">Spam</a><br>
<a href="https://filter.gst.com/canit/b.php?i=01ONKuKAX&m=df31bf618270&c=n" target="canit_note">Not spam</a><br>
<a href="https://filter.gst.com/canit/b.php?i=01ONKuKAX&m=df31bf618270&c=f" target="canit_note">Forget previous vote</a></span><o:p></o:p></p>
</div>
</div>
</body>
</html>