<html 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: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:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
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.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.EmailStyle22
{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;}
--></style>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<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" style="margin-left:.5in"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">Peter Shames <peter.m.shames@jpl.nasa.gov><br>
<b>Date: </b>Tuesday, September 3, 2019 at 4:16 PM<br>
<b>To: </b>"Margherita.di.Giulio@esa.int" <Margherita.di.Giulio@esa.int>, CCSDS Engineering Steering Group - CESG Exec <cesg@mailman.ccsds.org><br>
<b>Subject: </b>Re: [EXTERNAL] [CESG] CESG Mid-term Telecon on 5th September - Introduction<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<p class="MsoNormal" style="margin-left:.5in">Hi Margherita,<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">I suggest that we add an AI on Mario and Jonathan to discuss the status of negotiations on the SOIS / MOIMS interface. This has been holding up the Yellow Book.<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">The other topic that has surfaced recently is how the WG are handling the creation of new registries, and the timing associated with this. This has caused problems with a recent SPP update poll and more recently
with a Nav WG poll. We have a pretty clear policy and process, it is just not being followed. To quote from some of the email traffic about the SPP issue:<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="color:black">"… during the CESG poll both Erik and I, separately, identified issues with the SANA Considerations section in the updated SPP document, CCSDS 133.0-P-1.1. The SANA section, as written,
is not an adequate description of the intended registry. Furthermore, it appears that no one ever contacted the SANA Operator to review this registry nor to develop a suitable prototype. Our CCSDS procedures, in the Org & Proc doc, A02x1y4, call for following
the SANA Procedures in CCSDS 313.0-Y-2. And that document, and the Registry Management Policy, both point to the CCSDS Working Group Procedures for SANA Registry Specification, CCSDS 313.2-Y-1 as the guide to what a WG must do to create or modify a registry.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="color:black">What is blindingly clear is that these procedures were not followed and we now have a situation where a document that should be easily cleared for review and publication is not ready,
the registry it calls for is not fully specified, and there is no draft/candidate registry, nor has the SANA Operator even been contacted. This all violates CCSDS procedures."</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">There may be an issue in that there are three separate docs that must be looked at in order to understand both the policies and the procedures. But it is also the case that we can just point all WG Chairs at the
rather modest sized "<span style="color:black">CCSDS Working Group Procedures for SANA Registry Specification, CCSDS 313.2-Y-1" as the guide to what a WG must do.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">Thanks, Peter<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-left:1.0in"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">CESG <cesg-bounces@mailman.ccsds.org> on behalf of "Margherita.di.Giulio@esa.int" <Margherita.di.Giulio@esa.int><br>
<b>Date: </b>Tuesday, September 3, 2019 at 9:00 AM<br>
<b>To: </b>CCSDS Engineering Steering Group - CESG Exec <cesg@mailman.ccsds.org><br>
<b>Subject: </b>[EXTERNAL] [CESG] CESG Mid-term Telecon on 5th September - Introduction</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:1.0in"> <o:p></o:p></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:1.0in">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Dear All,</span> <br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">in view of the CESG Mid-term Telcon on 5th September, I provide herewith some introduction about the topics that will be addressed.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The following Agenda has been proposed ( in the invite)</span>
<br>
<br>
<span style="font-family:"Arial",sans-serif">CESG Mid-term Telecon - AGENDA</span>
<br>
<br>
<span style="font-family:"Arial",sans-serif;color:blue">1) Introduction, report from CMC meeting about CESG-related topics</span>
<br>
<span style="font-family:"Arial",sans-serif;color:blue">2) A.I. on J.Wilmot: Notion of MIB, data formats (template) , commonality and possible relationship to other Areas (TBC).</span>
<br>
<span style="font-family:"Arial",sans-serif;color:blue">3) Status of other A.I.s from the CESG Meeting</span>
<br>
<span style="font-family:"Arial",sans-serif;color:blue">4) Info about the Fall Meeting in Darmstadt</span>
<br>
<span style="font-family:"Arial",sans-serif;color:blue">5) AOB</span> <br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Please let me know if you would like to add any AOB.
</span><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Concerning AGENDA Item 1), the CESG have received the list of CMC Resolutions and Actions from Michael Balckwood on 17 June (also attached to this e-mail, for your convenience).
</span><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Some Actions and resolutions are relevant to CESG.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Please have a look. </span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The following will be addressed during the Telecon:
</span><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">a) <b>Resolution CMC-R-2019-06-04</b> (involvement of CCSDS on Lunar Gateway) I will report about the steps taken by CMC and by IOAG
</span><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">This action was generated following CESG request to "open a special channel between CCSDS and Gateway to discuss priorities on standards production and adoption by the Gateway". ( see MoM, AI/S19-5
MM)</span> <br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">b)<b> A.I</b>.<b> CMC-A-2019-06-01</b></span><b><span style="font-size:10.0pt"> (</span></b><span style="font-size:10.0pt">
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Agency Representatives to verify the frequency bands used by missions that have been assigned SCIDs ) this is partially accomplished.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">I will report from the CMC Telecon.
</span><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Peter, please contribute to this topic.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">c) <b>A.I</b>.</span><b><span style="font-size:10.0pt">
</span></b><span style="font-size:10.0pt;font-family:"Arial",sans-serif"> </span>
<span style="font-size:10.0pt">•</span><b><span style="font-size:10.0pt;font-family:"Arial",sans-serif">CMC-A-2019-06-05
</span></b><span style="font-size:10.0pt;font-family:"Arial",sans-serif">The CMC asks that Peter Shames report to the CMC the process for reassigning SCID frequency bins.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">and <b>A.I</b>.</span><b><span style="font-size:10.0pt"> •</span></b><b><span style="font-size:10.0pt;font-family:"Arial",sans-serif">CMC-A-2019-06-06</span></b><span style="font-size:10.0pt;font-family:"Arial",sans-serif">
The CMC asks Peter Shames to report to the CMC when the SCID frequency bins in SANA have been updated.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Peter, please let us know about the status.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">d) <b>A.I</b>.<b> CMC-A-2019-06-07</b> about adoption by Gateway of USLP and other standards --> I will report ( Wallace to contribute)</span>
<br>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Concerning AGENDA Item 2), from the CESG meeting in Mountain View, Jonathan is supposed to provide a presentation about the MIB for EDS and about potential commonality and relationship with the
information models from other Ares ( F.R model in CSS and network management in SIS).</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"> I assume he will provide such presentation during the Telecon (I have sent a reminder on 22 July)</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Concerning AGENDA Item 3), Status of other action items from the CESG meeting. These are the A.I.s related to "Deployment Scenarios for MO Services and Electronic Data Sheets" .<b> AI/S19-6 PS,
AI/S19-7 PS/MM/JW and AIS19-8 MM/JW</b></span> <br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Mario, Peter, Jonathan at the Telecon please report on the progress.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Kind regards,<br>
Margherita</span> <br>
<br>
<br>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">--------------------------------------------------------------<br>
</span><b><span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:#00A1E0">Margherita di Giulio</span></b>
<br>
<span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:#5F5F5F">Ground Station Systems Division</span>
<br>
<span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:#5F5F5F">Backend Software Section (OPS-GSB)</span>
<br>
<br>
<br>
<b><span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:#5F5F5F">European Space Agency ESA/ESOC</span></b><span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:#5F5F5F"><br>
Robert-Bosch-Str. 5<br>
D-64293 Darmstadt - Germany<br>
Tel: +49-6151-902779<br>
e-mail: Margherita.di.Giulio@esa.int</span><o:p></o:p></p>
<pre style="margin-left:1.0in">This message is intended only for the recipient(s) named above. It may contain proprietary information and/or<o:p></o:p></pre>
<pre style="margin-left:1.0in">protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received<o:p></o:p></pre>
<pre style="margin-left:1.0in">this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect<o:p></o:p></pre>
<pre style="margin-left:1.0in">personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo@esa.int).<o:p></o:p></pre>
</div>
</body>
</html>