<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 15 (filtered medium)">
<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:"Segoe UI";
panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:250093463;
mso-list-type:hybrid;
mso-list-template-ids:-1790803248 67698705 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1
{mso-list-id:1391541237;
mso-list-type:hybrid;
mso-list-template-ids:-1978351440 67698705 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l2
{mso-list-id:2086951180;
mso-list-type:hybrid;
mso-list-template-ids:-1968643276 67698705 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l2:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l2:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l2:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span class="EmailStyle19">Dear Colleagues,<o:p></o:p></span></p>
<p class="MsoNormal"><span class="EmailStyle19"><o:p> </o:p></span></p>
<p class="MsoNormal"><span class="EmailStyle19">Thanks for a great discussion this morning (or afternoon). I just uploaded my file to the CESG meeting folder (<a href="https://cwe.ccsds.org/cesg/docs/Forms/AllItems.aspx?RootFolder=%2Fcesg%2Fdocs%2FCWE%20Private%2FMeetings%2F2022%20CESG%20Systems%20Management%20and%20Configuration%2020%20Jan&FolderCTID=0x0120008F128D83E4774A40906DD60662AC3B27&View=%7B448728FC%2D9186%2D4BCF%2D80F0%2D192B39C01942%7D">https://cwe.ccsds.org/cesg/docs/Forms/AllItems.aspx?RootFolder=%2Fcesg%2Fdocs%2FCWE%20Private%2FMeetings%2F2022%20CESG%20Systems%20Management%20and%20Configuration%2020%20Jan&FolderCTID=0x0120008F128D83E4774A40906DD60662AC3B27&View=%7B448728FC%2D9186%2D4BCF%2D80F0%2D192B39C01942%7D</a>).
<o:p></o:p></span></p>
<p class="MsoNormal"><span class="EmailStyle19"><o:p> </o:p></span></p>
<p class="MsoNormal"><span class="EmailStyle19">My own notes from this discussion, in abbreviated form, identify these topics:<o:p></o:p></span></p>
<p class="MsoNormal"><span class="EmailStyle19"><o:p> </o:p></span></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level1 lfo1">Pg 2: EDS includes data objects too.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level1 lfo1">Pg 4: ESA uses the kinds of information that is in an ICS as part of cross support agreements, but it does not use ICS directly.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level1 lfo1">Pg 5: The FRM describes functions in the abstract and not elements. Most of these functions are defined in protocol docs, but not all of them.
<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level1 lfo1">Pg 5: The FRM has explicitly defined a dictionary of terms that are part of the modeling environment, but these have not been formalized in a published document.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level1 lfo1">Pg 6: EDS does not (yet) formalize the definition of deployments (Port 1 of Component A is connected to Port 3 of Component B), but a list of all EDS used in a system, along with a
description of their connectivity, is being used to create a formalized description of a deployment.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level1 lfo1">Pg 8: A Management Information Base (MIB), as now defined in CCSDS documents, is abstract and without data types or ranges. But implementations need to define the parameters in a
MIB more formally, and this must include data types, ranges, and any constraints imposed by the implementation. The FRM does define data types and ranges, but not constraints. NOTE: CCSDS could do this better, but it may cross the line between specifications
and implementations.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level1 lfo1">Pg 12: An EDS could be used to describe the components, interfaces, and behavior of real ground system components. The FRM already defines the functions that these components implement,
but that FRM description is divorced from the components themselves.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level1 lfo1">Pg 14: The Dictionary of Terms defined and documented for the EDS, and the Dictionary of Terms that are an explicit part of the FRM modeling environment should be combined into one
shared Dictionary of Terms that both sets of standards share. (See later note, this could occur within the FRM Tool adaptation test that was agreed to).<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level1 lfo1">Pg 14: For many of the protocol functions defined by the FRM there will need to be a related set of “inverse functions” , with “reversed polarity”. In order to describe the spacecraft
end of the link the ground station function that does “TC PLOP, Sync and Channel
<b>Encoding</b>” needs to have an inverse “TC PLOP, Sync and Channel <b>Decoding</b>” function. This is true of all such functions, except those, like DTN, that are inherently symmetric in the first place.<o:p></o:p></li></ol>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Holger demoed his quick exploration that used the FRM toolset to document the DTN protocol. It appeared that this was a relatively quick and painless exercise (Holger did not wince) and it clarified just what the existing tool could do.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l2 level1 lfo2">The FRM tool can output the generated models in XML, JSON, ASN.1 and other formats.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l2 level1 lfo2">The FRM tool appears to be limited to using bytes (octets) and words, but not (in a simple form) bit fields.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l2 level1 lfo2">The FRM tool, as it has been used, provides a convenient way to document field and parameter names, and to assign them with ISO OIDs.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l2 level1 lfo2">The FRM, at present, defines and names functions and their parameter sets, but not PDUs and other data structures<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l2 level1 lfo2">Keith Scott asked if it were possible to put protocol PDUs (and MIBs) into the FRM tool.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l2 level1 lfo2">Holger suggested that it might be possible, but it appeared to be a little awkward. Holger suggested that TSN.1, instead of ASN.1, was the more natural mapping for the kinds of bit-wise
fields that are needed for PDU mapping.<o:p></o:p></li></ol>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Test Project:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo3">Holger agreed to extend the FRM tool, and the current DTN model, to define all of the needed abstract names and data types (Recommend that this reference the EDS DoT as a source).
This extended model would also include all of the PDUs, parameters, and the MIB data items, with full type structures (guessed at initially).<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo3">Keith Scott suggested initially modeling the DTN Primary Bundle Block, or Payload Block, because they are relatively simple structures.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo3">There was a discussion of whether the FRM tool should be extended to also output EDS’s or whether the EDS tool chain should be modified to accept FRM tool outputs. This was left for
a later discussion.<o:p></o:p></li></ol>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We agreed to meet again on 17 March to review progress and discuss next steps.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Klaus Juergen raised the topic of the management of DTN nodes and the suggestion that we should next explore the use of MOIMS SM&C services in this context. Peter pointed out that there is already an extensive, documented, and well formulated,
set of DTN asynchronous management protocols that have been developed in the IETF and SIS DTN WG. These address the issues of managing distributed DTN nodes using a simple asynchronous protocol and an interoperable set of directives and data models. Peter
has been working with Keith Scott, Ed Birrane, and Howie Weiss (among others) on a separate presentation that addresses this, but there was not time to present it. This existing, interoperable and focused, set of standards and models should be the starting
point for CCSDS DTN management and control.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">There may be errors or omissions in these notes. Feel free to comment or edit as you see fit.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Regards, Peter<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span lang="EN-GB" style="font-size:12.0pt;color:black">From:
</span></b><span lang="EN-GB" style="font-size:12.0pt;color:black">Maria Beickler <Maria.Beickler@ext.esa.int><br>
<b>Date: </b>Thursday, January 20, 2022 at 4:34 AM<br>
<b>To: </b>CCSDS Engineering Steering Group - CESG Exec <cesg@mailman.ccsds.org>, Sami Asmar <sami.w.asmar@jpl.nasa.gov>, Holger Dreihahn <Holger.Dreihahn@esa.int>, Keith Scott <kscott@mitre.org>, Mehran Sarkarati <Mehran.Sarkarati@esa.int><br>
<b>Cc: </b>Colin Haddow <Colin.Haddow@esa.int>, Peter Shames <peter.m.shames@jpl.nasa.gov>, Erik Barkley <erik.j.barkley@jpl.nasa.gov>, "Grubbs, Rodney P. (MSFC-HP27)" <rodney.grubbs@nasa.gov>, Mario Merri <Mario.Merri@esa.int>, Klaus-Juergen Schulz <Klaus-Juergen.Schulz@esa.int>,
Joachim Fuchs <Joachim.Fuchs@esa.int><br>
<b>Subject: </b>[EXTERNAL] CESG: Systems Management and Configuration<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-GB">Dear Colleagues,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">This is to inform that I have created a directory under CESG -> CWE private -> meetings -> 2022 CESG Systems Management and Configuration 20 Jan<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">May I ask you to copy your presentation into this folder.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">Thank you very much.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">Maria<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">On behalf of Klaus-Juergen Schulz<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:12.0pt;font-family:"Segoe UI",sans-serif;color:#00204F;mso-fareast-language:EN-GB">Maria Beickler</span><span lang="EN-GB" style="font-size:8.5pt;font-family:"Arial",sans-serif;color:black;mso-fareast-language:EN-GB"><br>
</span><span lang="EN-GB" style="font-size:12.0pt;font-family:"Segoe UI",sans-serif;color:#00204F;mso-fareast-language:EN-GB">Ground Station Engineering Division</span><span lang="EN-GB" style="font-size:8.5pt;font-family:"Arial",sans-serif;color:black;mso-fareast-language:EN-GB"><br>
</span><span lang="EN-GB" style="font-size:12.0pt;font-family:"Segoe UI",sans-serif;color:#00204F;mso-fareast-language:EN-GB">Telespazio Germany GmbH</span><span lang="EN-GB" style="font-size:8.5pt;font-family:"Arial",sans-serif;color:black;mso-fareast-language:EN-GB"><br>
<br>
</span><span lang="EN-GB" style="font-size:12.0pt;font-family:"Segoe UI",sans-serif;color:#172B4D;mso-fareast-language:EN-GB">Frame Contract for Administrative and Management Services at ESOC</span><span lang="EN-GB" style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black;mso-fareast-language:EN-GB"> </span><span lang="EN-GB" style="font-size:8.5pt;font-family:"Arial",sans-serif;color:black;mso-fareast-language:EN-GB"><br>
<br>
</span><b><span lang="EN-GB" style="font-size:12.0pt;font-family:"Segoe UI",sans-serif;color:#172B4D;mso-fareast-language:EN-GB">ESA/ESOC</span></b><span lang="EN-GB" style="font-size:12.0pt;font-family:"Segoe UI",sans-serif;color:#172B4D;mso-fareast-language:EN-GB"><br>
Robert-Bosch-Str. 5<br>
64293 Darmstadt, Germany<br>
Tel: +49-6151-90-2481</span><span lang="EN-GB" style="mso-fareast-language:EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">This message is intended only for the recipient(s) named above. It may contain proprietary information and/or protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have
received this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo@esa.int).
<o:p></o:p></span></p>
</div>
</body>
</html>