<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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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:"Arial Narrow";
panose-1:2 11 6 6 2 2 2 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-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;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:204148591;
mso-list-type:hybrid;
mso-list-template-ids:827196114 244855594 67895299 67895301 67895297 67895299 67895301 67895297 67895299 67895301;}
@list l0:level1
{mso-level-start-at:0;
mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-font-family:Calibri;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></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="FR" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:EN-US">Bonjour<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US">I believe the next teleconference will be useful to clarify the actions on the SANA registries.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US">My understanding is that the AR’s do not have rights to update all registries but just the enterprise registries which fall under their responsibilities (ref. slide 9 of
Peter’s presentation at mid-term).<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US">For me, the resolutions formulated by the CESG show what needs to be done: 1) check the newly imported data. 2) And for that AR’s must be nominated.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US">The reason why this was not triggered by the CMC is just that the CMC wants to understand beforehand:<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l0 level1 lfo1"><![if !supportLists]><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US"><span style="mso-list:Ignore">-<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US">If the newly created registries are justified and what is the amount of additional work for the SANA operator, with the new registries<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l0 level1 lfo1"><![if !supportLists]><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US"><span style="mso-list:Ignore">-<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US">What is the process to approve the registries and why the CMC is not in the decision loop<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l0 level1 lfo1"><![if !supportLists]><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US"><span style="mso-list:Ignore">-<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US">Which data needs be reviewed by the ARs and the associated amount of work<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US">In my opinion, the first question addresses the most recent registries among the 45 (I have no doubt on the dozens of pre-existing registries) ; the second question concerns
the 45 + 16 registries.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US">My main concern is the third question, first because it is not clear which registries and data are under the AR’s and second because the process / procedure to update is
not clear either (on line, email interface to the SANA operator,…). In summary, what are the imported data and how to update it (contrary to the SCId registry, there is no friendly user interface to manage the other registries). On the latter, a demo during
the next webex would help.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US">Last, I am hopeful that the SCId data base doesn’t need be reviewed by the AR’s as this has been under the SANA operator since the web interface was created and the transfer
to the new OIDs context must have been fully mastered and under control. <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US">This is just an opinion, no need to answer, and I agree with Osvaldo:
</span><span lang="EN-US" style="color:#1F497D">Let’s see what happens in the next round in September… if a date may be found.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US">Best regards<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:5.0pt;margin-right:0cm;margin-bottom:5.0pt;margin-left:0cm;text-autospace:none">
<b><i><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial Narrow",sans-serif;color:#1F497D">Jean-Marc Soula
<br>
</span></i></b><i><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial Narrow",sans-serif;color:#1F497D">CNES
</span></i><i><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial Narrow",sans-serif;color:#002060">–
</span></i><i><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial Narrow",sans-serif;color:#1F497D">DNO/SA/DA<br>
Deputy Head of Stations networks and Alert systems Department<br>
18 Avenue Edouard Belin <br>
31401 Toulouse Cedex 9 - France <br>
Tel.: +33 (0)5 61 2 74647 <br>
Fax.: +33 (0)5 61 2 </span></i><i><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial Narrow",sans-serif;color:#002060">73993</span></i><i><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial Narrow",sans-serif;color:#1F497D"><br>
Email: <a href="mailto:jean-marc.soula@cnes.fr">jean-marc.soula@cnes.fr</a> </span>
</i><i><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial Narrow",sans-serif;color:#002060"><br>
<a href="http://www.cnes.fr">www.cnes.fr</a><o:p></o:p></span></i></p>
</div>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b>De :</b> CMC-EXEC <cmc-exec-bounces@mailman.ccsds.org> <b>
De la part de</b> osvaldo.peinado@dlr.de<br>
<b>Envoyé :</b> mardi 28 août 2018 15:35<br>
<b>À :</b> Wallace.S.Tai@jpl.nasa.gov; CMC-exec@mailman.ccsds.org<br>
<b>Objet :</b> Re: [CMC Alert] SANA discussion<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Thank you Wallace<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">I think the AR need to do an update, not only review, for the 45 approved SANA Registries (all, not only the names imported from CWE)
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">I do not agree to do a review, send E-mails with the mistakes to the SANA operator and then review again if everything is ok.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Non AR have the time to do the work twice or more times (for example my own name is wrong and still not fixed).<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Let see what happens in the next round in September<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Best Regards<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Osvaldo<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma",sans-serif">Von:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma",sans-serif"> Tai, Wallace S (9000) [<a href="mailto:Wallace.S.Tai@jpl.nasa.gov">mailto:Wallace.S.Tai@jpl.nasa.gov</a>]
<br>
<b>Gesendet:</b> Montag, 27. August 2</span><span lang="DE" style="font-size:10.0pt;font-family:"Tahoma",sans-serif">018 19:36<br>
<b>An:</b> Peinado, Osvaldo Luis; <a href="mailto:CMC-exec@mailman.ccsds.org">CMC-exec@mailman.ccsds.org</a><br>
<b>Betreff:</b> Re: [CMC Alert] SANA discussion<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="DE"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">All,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">I hesitated to join the fray about SANA during the various long discussions taking place recently since, from the CESG perspective, Margherita already stated the SANA use cases clearly. I understand there are still issues
to be resolved by the CMC.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black">After reading Osvaldo’s assessment, I agree with him that the SANA functions are working well. I further agree that there are a few deficiencies in the current SANA data base.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black">However, we have to recognize that there is "clean-up" work on the Spacecraft registry contents that can only be done by each Agency's AR. This in fact was the subject of the following SEA resolution:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-US" style="color:black">SEA-R-2018-04-05 Require that each Agency Representative (AR) shall be asked to review the newly imported Mission / Spacecraft from the CCSDS Website and identify overlapping, aliased,
missing, and/or retired entries.</span></b><span lang="EN-US" style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black">And that resolution requires that each Agency HoD assign an AR (or take on that role themselves), which was another SEA resolution:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-US" style="color:black">SEA-R-2018-04-04 Request that each CCSDS Agency and Observer ensure that they have at least one authorized Agency Representative (AR) for managing Agency information in the SANA, and
that this information is updated.</span></b><span lang="EN-US" style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black">Both of these resolutions are part of the set of seven (7) that the CMC has seen fit to put on hold.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Wallace<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:12.0pt;color:black">From:
</span></b><span lang="EN-US" style="font-size:12.0pt;color:black">CMC-EXEC <<a href="mailto:cmc-exec-bounces@mailman.ccsds.org">cmc-exec-bounces@mailman.ccsds.org</a>> on behalf of "<a href="mailto:osvaldo.peinado@dlr.de">osvaldo.peinado@dlr.de</a>" <<a href="mailto:osvaldo.peinado@dlr.de">osvaldo.peinado@dlr.de</a>><br>
<b>Date: </b>Friday, August 24, 2018 at 2:47 AM<br>
<b>To: </b>"<a href="mailto:CMC-exec@mailman.ccsds.org">CMC-exec@mailman.ccsds.org</a>" <<a href="mailto:CMC-exec@mailman.ccsds.org">CMC-exec@mailman.ccsds.org</a>><br>
<b>Subject: </b>[CMC Alert] SANA discussion<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US">Dear all<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">After the very long discussion about SANA, I was checking some of the points that we talk about<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">There are 45 approved registries and in my opinion that are the ones that need to be checked (agency representative), not only the names from CWE<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">And there are 16 candidates, may be for the next CMC to be discussed?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Some of them like the Spacecraft, looks to me more important than other already approved. And the funny thing here is that the content it is approved!<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Kind of confusing situation here.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">On the approved ones, for example Apertures, the antennas are provisional, this register was originated by IOAG but in most of them there is no country mentioned and a lot for information is missing (for example in the
KSAT Antennas that are listed).<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Similar situation is in the aperture links, the register is approved, but all the content is still provisional.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Same is transport services.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">DTN looks good.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">CCSDS Abbreviations are all provisional, although the references to the corresponding books are correct.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">CFDP is status unmanaged, what that means?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Than we have the glossary that only makes a reference to Terms and Abbreviations.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">By the terms is the same situation as Abbreviations, do we need to check all of them to make them approved?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">I can follow on, for each of the 45 approved Registries (without approved content) till we arrive to the Contacts<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Here we have the long discussion, and here in my opinion should be simply imported from CWE, not to have the information in both places<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">I think we will need to have a long telecom again for clarify all these points and what is meaningful to have in SANA; not to justify SANA; but review and decided about the content<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Have a nice weekend<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Osvaldo<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">__________________________________________________________________________________________<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Dr. Osvaldo Peinado<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Ground Operations Manager<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">German Space Operation Center (GSOC)<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">DLR (German Aeropspace Agency)<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Phone: +49 8153 283010<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Mobile: +49 172 9410099<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Muenchenerstr. 20<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">82234 Wessling<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Germany<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
</div>
</body>
</html>