<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)">
<!--[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:Helvetica;
panose-1:0 0 0 0 0 0 0 0 0 0;}
@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:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:TimesNewRomanPS;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:TimesNewRomanPSMT;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:-webkit-standard;
panose-1:2 11 6 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
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:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle21
{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:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1129058114;
mso-list-type:hybrid;
mso-list-template-ids:-1862101856 -96319762 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@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:Symbol;
mso-fareast-font-family:Calibri;
mso-bidi-font-family:"Times New Roman";}
@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;}
@list l1
{mso-list-id:1360014130;
mso-list-type:hybrid;
mso-list-template-ids:-387709084 1444282540 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l1:level1
{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 l1: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 l1: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 l1: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 l1: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 l1: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 l1: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 l1: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 l1: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="en-IT" link="#0563C1" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US">Dear Peter,<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 need to react to your note. I will focus on facts:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<ul style="margin-top:0cm" type="disc">
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l1 level1 lfo3"><span lang="EN-US">SM&C and Security WGs interacted in 2018 and 2019. Joint meetings were held in both years. Last joint meeting was in Spring 2019. Security WGs MoM of both Technical
Meetings are attached to this email.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l1 level1 lfo3"><span lang="EN-US">Security WG had on request of SM&C WG performed a through and detailed analysis of SM&C set of standards. A dedicated
<b><u><span style="color:red">prototype</span></u></b><span style="color:red"> </span>
had been implemented to further deepen the implementation aspects<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l1 level1 lfo3"><span lang="EN-US">Very detailed recommendations and changes to SM&C books were provided by Security WG to SM&C WG mid 2019. These were at the level of changes of text/sentences in
the SM&C Books.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l1 level1 lfo3"><span lang="EN-US">Dedicated follow up technical session were hold between the technical lead of SM&C WG and the experts of Security WG.
<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l1 level1 lfo3"><span lang="EN-US">I refer to the MoM of the Security WG, which are attached to this email:<o:p></o:p></span></li><ul style="margin-top:0cm" type="circle">
<li class="MsoListParagraph" style="color:black;margin-left:0cm;mso-list:l1 level2 lfo3">
<span lang="EN-US" style="font-size:12.0pt;font-family:"Arial",sans-serif">“</span><i><span style="font-family:"Arial",sans-serif;color:black">The Security WG presented suggested updates to call affected SM&C books in the form of a redlined version. The affected
books are fortuitously in the process of being revised or in draft. SM&C was very receptive to the proposals and will include them in the document updates</span></i><span style="font-size:12.0pt;font-family:"Arial",sans-serif">.</span><span lang="EN-US" style="font-size:12.0pt;font-family:"Arial",sans-serif">”
</span><span style="font-family:"-webkit-standard",serif"><o:p></o:p></span></li></ul>
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l1 level1 lfo3"><span lang="EN-US">I have reached out to the Deputy Chair of the Security WG and quote his response:<o:p></o:p></span></li><ul style="margin-top:0cm" type="circle">
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l1 level2 lfo3"><span lang="EN-US" style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">“</span><span style="font-family:"Arial",sans-serif;color:black">Update of the SM&C books: This
was done subsequently with Sam and presented as well at the next CCSDS meeting. The Security WG considers this business closed to their satisfaction</span><span style="font-family:"Arial",sans-serif;color:#4472C4">.</span><span lang="EN-US" style="font-family:"Arial",sans-serif;color:#4472C4">”</span><o:p></o:p></li></ul>
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l1 level1 lfo3"><span lang="EN-US">The reference Model was sent to review
<b><u><span style="color:red">one year after</span></u></b> the close interactions between SM&C WG and the Security WG. In CCSDS terms and considering the speed of our processes this is like a “minute ago” if not a second ago. In our meeting yesterday, you
repeatedly claimed interactions were years ago and you had asked members of security WG and they considered things have changed dramatically since. This is a very wrong statement.</span><o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l1 level1 lfo3"><span lang="EN-US">The reference Model Book was updated and sent to review
<b><u><span style="color:red">under NASA leadership</span></u></b> of the WG. Dan Smith was the lead and coordinated this books update and I trust he has certainly ensured correct and adequate implementation of proposed changes.</span><o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l1 level1 lfo3"><span lang="EN-US">The SM&C WG is currently undertaking a major effort of updating all its books under the Umbrella Term MO 2.0. The resources for this undertaking are massive and
we are facing sever challenges of prioritizing our efforts </span><o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l1 level1 lfo3"><span lang="EN-US">It is for our WG difficult to understand that when we have a dedicated WG in CCSDS for Security, how can it be that the Area director of that WG holds a very different
position than the WG itself. </span><o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l1 level1 lfo3"><span lang="EN-US">From our perspective we have followed what is exactly expected in CCSDS among the expert WGs. We have reached out and consulted the Security WG. From the minutes
and confirmed by the Deputy Chair and the members of the WG (even in your attached emails) the two WGs worked
<b><u><span style="color:red">perfectly well together and there was no disagreement</span></u></b>. All recommendations were accepted and Security WG considered the issue as closed. It is extremely frustrating to see that having gone through this process, we
are facing broad, generic and unsubstantiated claims, raised by the Area director of the same WG (even wrt years you talked yesterday about 5 years ago, now you say about 3 year ago instead of saying less than a year between the interaction and update of
the book and sending of the book to review). I find this very deceptive and passing a very wrong picture.</span><o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l1 level1 lfo3"><span lang="EN-US">The Reference Model is frankly not on the top of our priorities right now with the update of the MAL, Bindings, M&C Book, Mission Data Product Distribution Service
and others on our plate. </span><o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l1 level1 lfo3"><span lang="EN-US">Of course, there may be mistakes and it may be that one or the other recommendation of the Security WG is not implemented to your full satisfaction. We can review
the comments raised by Security WG and track them back in the updated book and demonstrate due diligence. The problem is, all of this is
<b><u><span style="color:red">extremely effort and time consuming</span></u></b> and we would like to report back to CMC and CESG on the sever impact of this on the schedule of our WG for the MO 2.0 updates.</span><o:p></o:p></li></ul>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-US">I consider all of the above simple facts, which have been checked with those in leading role before I took over the chairmanship of the SM&C WG.<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">Now I leave the world of facts and enter the domain of perception:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">We observe that in any review of any of book that has an MO element, be it from the SM&C WG and MP&S WGs we always face severe “problems”, resistance and delays coming always only from one and the same direction, which
is you in your role as the AD. <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">This is true for the charter of the MP&S WG, the approval of the Blue Book of the MP&S, the approval of the MAL, the binding books, the SM&C books, …<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">You keep on coming back on the same issues again and again , even when we see that your concerns are overruled by CESG and CMC. You raise the same comments nonetheless in any opportunity.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">This is apparent when we see the same type of comments raised on the “unchanged” part of a book that was already approved and published, when it goes through the 5 years review.<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">We value your expertise and do not question your authority, nor your opinion. But as you yourself say, we are in CCSDS a consensus organization. To me this means that when you have a reservation wrt to MO in general and
have raised this reservations over the years again and again, nonetheless the CCSDS organization (in form of CESG and CMC) have decided otherwise, it is the fair play that you do not look for any opportunity to slow down the process of our WG and refrain from
bringing up the same point again in the next book review.<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 put a disclaimer on the top of these points and repeat again that this is mine and WG’s perception and not facts. This is how we perceive your repetitive comments on any book that has something with MO.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">I apologies if this is a wrong perception, nonetheless from your side it would be important that you acknowledge how your interaction with our WG is perceived by the majority of the WG (I am not referring only to this
case).<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">I have not conducted a vote on this in the WG and am passing the message of direct interactions with many of the members of our WG.<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">Now, back to the process, I believe since both you and me are referring to the Security WG and at least for my side I am not comfortable to talk on their behalf, I will request a clarification to the Chair and Deputy
Chair of the Security WG.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">I will also double check if any of the recommendations of the Security WG was not implemented.
<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">For now, we in the SM&C WG need however to discuss in our WG, if we can afford spending resources on detailed analysis of your comments and detailed demonstration of the history and “proving” that we have done everything
ok.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">We have currently more important issues with the update of our books on hand.<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 would like to formally report to the CESG and CMC that the consequence of this perceived “pattern” is concretely resources and expenditure on the participating agencies of our WG and ask for guidance of how to handle
the entertaining of this process in view of sever lack of resources and higher priority tasks.
<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">One last point is, our WG has very tight schedule and we have regular bi-weekly and monthly splinters and WG meetings to close the MO 2.0 updates.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">I would like to ask you, in case you wish to discuss with SM&C WG something, please inform me in advance and I will see how best to organize dedicated meeting, if and when the resources and availability of the WG allows.<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"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Kind Regards<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Mehran<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"><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 style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">"Shames, Peter M (US 312B)" <peter.m.shames@jpl.nasa.gov><br>
<b>Date: </b>Wednesday, 30 June 2021 at 22:30<br>
<b>To: </b>Mehran Sarkarati <Mehran.Sarkarati@esa.int>, "moims-sc@mailman.ccsds.org" <moims-sc@mailman.ccsds.org><br>
<b>Cc: </b>CCSDS Engineering Steering Group - CESG Exec <cesg@mailman.ccsds.org>, SEA-Sec <sea-sec@mailman.ccsds.org><br>
<b>Subject: </b>Issues with SM&C MO Ref Model, CCSDS 520.1-P-1.1, as identified in CESG poll CESG-P-2021-04-002<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><span style="font-size:16.0pt">Dear Mehran and the SM&C WG,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:16.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:16.0pt">Yesterday, on 29 Jun 21, you held an SM&C WG meeting where one of the topics on the agenda was the CESG Poll results on SM&C MO Ref Model, CCSDS 520.1-P-1.1, as identified in CESG poll CESG-P-2021-04-002.
Since I had voted to disapprove this document, for a set of clearly stated reasons, I did you the courtesy of coming to the meeting so that I could answer any questions and clarify any concerns you might have. From my point of view the outcome of that meeting
was quite unsatisfactory, and I wish you all to understand why. I would not normally take the time to do this, but in this situation a clear and unambiguous response seems warranted.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:16.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:16.0pt">I’m going to start by providing a little background about where I am coming from since there appears to be a lack of understanding of the role that I, and all other CESG members, play in CCSDS processes.
I am the CCSDS Systems Engineering Area Director (SEA AD). As such I am responsible for the SEA and the Security WG which is within that Area. As one of the six CCSDS Area Directors (AD) I am also a member of the CCSDS Engineering Steering Group (CESG),
which has responsibility for reviewing and approving every single document that the CCSDS produces. </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:16.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:16.0pt">It seems that I must remind you that the CCSDS Organization and Processes document, CCSDS A02.1-Y-4, guides and controls all of our work. I have taken the liberty of extracting, and underlining, the key sections
that you appear to have forgotten or are unaware of:</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:36.0pt">
<b><span style="font-size:16.0pt;font-family:TimesNewRomanPS;color:#2F5597">2.3.2.2 CESG Operating Principles
</span></b><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:36.0pt">
<span style="font-size:16.0pt;font-family:TimesNewRomanPSMT;color:#2F5597">d) </span><i><span style="font-size:16.0pt;font-family:TimesNewRomanPS;color:#2F5597">Consistency</span></i><span style="font-size:16.0pt;font-family:TimesNewRomanPSMT;color:#2F5597">.
An important job of the CESG is to watch over the output of all of the WGs to help prevent CCSDS specifications that are at odds with each other. This is why ADs and DADs are required to review the drafts coming out of Areas other than their own as part of
the consensus process leading up to their adoption into the program of work. <u>
The quality of the CCSDS Recommended Standards comes both from the review that they get in the WGs and the review that the WG products get from the CESG.
</u></span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:36.0pt">
<span style="font-size:16.0pt;font-family:TimesNewRomanPSMT;color:#2F5597">e) </span><i><span style="font-size:16.0pt;font-family:TimesNewRomanPS;color:#2F5597">Anticipation</span></i><span style="font-size:16.0pt;font-family:TimesNewRomanPSMT;color:#2F5597">.
<u>The CESG must be able to look ahead and anticipate new standards that stakeholders will most likely require</u>, and begin prospective planning for their development so that there is sufficient time to complete them once a hard requirement emerges. This
implies working with technology and experimental communities to vector research resources into the standardization process.
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:16.0pt">And</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:36.0pt">
<b><span style="font-size:16.0pt;font-family:TimesNewRomanPS;color:#2F5597">2.3.2.3 CESG Responsibilities
</span></b><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:36.0pt">
<span style="font-size:16.0pt;font-family:TimesNewRomanPSMT;color:#2F5597">The CESG is specifically responsible for the following:
</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:36.0pt">
<span style="font-size:16.0pt;font-family:TimesNewRomanPSMT;color:#2F5597">a) <u>maintaining and upholding the overall technical quality and consistency of the evolving set of CCSDS Recommended Standards and Practices</u>;
</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:36.0pt">
<span style="font-size:16.0pt;font-family:TimesNewRomanPSMT;color:#2F5597">b) providing the CCSDS-wide forum where the work programs of the Areas may be coordinated and synchronized in the
<u>context of an overall architecture for space- mission cross support</u> and the needs of individual customers;
</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:36.0pt">
<span style="font-size:16.0pt;font-family:TimesNewRomanPSMT;color:#2F5597">i) <u>periodically reviewing the technical work of each Area to ensure that it is progressing toward common goals</u>, that the process of consensus is being observed and that the needs
of CCSDS stakeholders (2.2) are being satisfied in a timely manner (the ADs shall be responsible for reporting on all work items within their Area);
</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:36.0pt">
<span style="font-size:16.0pt;font-family:TimesNewRomanPSMT;color:#2F5597">j) <u>identifying “red flag” items where technical work in a proposed CCSDS document is not of the required quality or nature</u>, where technical work is not progressing satisfactorily,
where resources are inadequate, or where significant issues exist, and raising these to the attention of the CMC for corrective action;
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:16.0pt">I am providing this as a reference because you seemed to be of the impression that having a discussion between the SM&C WG and the Sec WG three years ago was sufficient “to disposition” the security and other
issues that I identified in my PID. It is not. And, as we shall see, the earlier interactions with the SecWG did not, in any event, “disposition” the issues that were raised three years ago (Fall 2018). Based on my review it is clear that these issues remain
and they are viewed by me, and the SecWG, as being even more serious now than they were then.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:16.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:16.0pt">An abbreviated form of the key issues that I raised in the CESG PID were these:</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:16.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:16.0pt;font-family:"Times New Roman",serif;color:black">There are two major issues that must be contended with, and neither of them are adequately addressed: 1) The SM&C MAL is undergoing
a major revision, one of which is to remove the COM, but that is not addressed; 2) a solid security approach, for single systems, but most especially for multi-mission systems, is essential, but the mechanisms in this document remain vague, weak, and poorly
articulated.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:16.0pt;font-family:"Times New Roman",serif"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:16.0pt;font-family:"Times New Roman",serif;color:black">Since one of the stated desires is to use this framework for major, multi-mission, and multi-agency, deployments we also looked at
it from that point of view. The following comment, quoted from one [SecWG] reviewer, should provide further insights:</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:16.0pt;font-family:"Times New Roman",serif;color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:72.0pt"><span style="font-size:16.0pt;font-family:"Times New Roman",serif;color:black">"I have read all the MO books and followed the SM&C WG for ten years now (although its meetings always conflict with my own WGs). When
I have a hard time figuring out how security fits into MO services, a non-CCSDS reader can expect even more difficulty.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:72.0pt"><span style="font-size:16.0pt;font-family:"Times New Roman",serif;color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:72.0pt"><span style="font-size:16.0pt;font-family:"Times New Roman",serif;color:black">JSC gave up active participation in SM&C WG due to a perceived lack of ROI for our missions. Compared to the mature operational capabilities
already implemented for ISS in custom software, MO services were viewed as redundant. The single most important features deemed lacking, which would have recommended MO above a custom implementation, were precisely those security capabilities necessary to
support multiple complex missions across multiple agencies/contractors each with their own access restriction requirements. But work on MO security services has been deferred indefinitely by the SM&C WG (and reading the MO 2.0 list of topics, appears to be
absent yet again).”</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:16.0pt;font-family:"Times New Roman",serif"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:16.0pt;font-family:"Times New Roman",serif;color:black">Another point to be made, in the context of CCSDS "reference model" Magenta Books is that MB are intended to be normative content. This
permits them to not be "directly implementable", but it also requires that they "provide normative, controlling, guidance rather than purely descriptive material." While the word "normative" is used a lot, and there is liberal use made of UML diagrams, which
give the appearance of concrete recommendations, on closer examination all of the figures are abstractions and there are really no concrete examples to reference and tie these abstractions to reality. At almost every turn these very real concrete concerns
are just dismissed as "implementation" or "deployment" details. This makes the document vague and does not provide concrete examples to substantiate that the stated claims can be achieved. This is especially true of the security sections, but it is also
true throughout, particularly where multi-mission deployments are considered.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:16.0pt">I am going to just focus on the security issues for now, but the others also remain unresolved. During the telecon you asserted that the SM&C WG
had met with the SecWG three years ago and that all of the security concerns that they had raised at that time had been resolved. I told you that even though I do have a strong background in distributed systems architectures and secure systems I had consulted
with members of the SecWG just prior to submitting my PID. They confirmed my concerns and completely supported my analysis.
</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:16.0pt">Because of your statements just after the SM&C meeting on Tuesday, 29 June, I again contacted the SecWG to determine what their knowledge was of the
situation. These are the replies I got:</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:16.0pt"> </span><o:p></o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" style="margin-left:36.0pt"><b><span style="font-size:18.0pt;color:black">From:
</span></b><span style="font-size:18.0pt;color:black">"Biggerstaff, Craig (JSC-CD42)[SGT, INC]" <craig.biggerstaff@nasa.gov><br>
<b>Date: </b>Tuesday, June 29, 2021 at 10:17 AM<br>
<b>To: </b>Howie Weiss <Howard.Weiss@parsons.com>, Peter Shames <peter.m.shames@jpl.nasa.gov>, "Sheehe, Charles J. (GRC-LCN0)" <charles.j.sheehe@nasa.gov><br>
<b>Cc: </b>"Radulescu, Costin (US 9300)" <cradule@jpl.nasa.gov><br>
<b>Subject: </b>RE: [EXTERNAL] RE: Issues with SM&C MO Ref Model treatment of security topics</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:16.0pt"> </span><o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:16.0pt;color:#1F497D">Security analysis produced by ESA, posted in the SM&C WG meeting materials from
<b>Fall 2018</b>:</span><o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:72.0pt;text-indent:-18.0pt;mso-list:l0 level1 lfo2">
<![if !supportLists]><span style="font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:16.0pt;color:#1F497D"><a href="https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.us%2Fv3%2F__https%3A%2Fcwe.ccsds.org%2Fmoims%2Fdocs%2FMOIMS-SMandC%2FMeeting*20Materials%2F2018%2FFall%2FMOS_Security_CCSDS_161018.pptx%3Fd%3Dw6be12e1a154d41a7b3fe4a126d59adde__%3BJQ!!PvBDto6Hs4WbVuu7!ZASh8ARy3w73YAeFEYVr5ReOkHVZ9zONUObvTqad9T6Cd0q3CPf5BB6B9ADG18oVUXI%24&data=04%7C01%7CMehran.Sarkarati%40esa.int%7C65ef09ea3a8e45a7087908d93bf0f54c%7C9a5cacd02bef4dd7ac5c7ebe1f54f495%7C0%7C0%7C637606728358516854%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=hvA8DnzSMYKxQ9KzfDlLX%2B%2B7VgzECMRUy7qOc%2BTcFKY%3D&reserved=0">https://cwe.ccsds.org/moims/docs/MOIMS-SMandC/Meeting%20Materials/2018/Fall/MOS_Security_CCSDS_161018.pptx?d=w6be12e1a154d41a7b3fe4a126d59adde</a></span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:16.0pt;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:16.0pt;color:#1F497D">More security analysis produced by ESA, posted in the SM&C WG meeting materials from
<b>Fall 2019</b>:</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:16.0pt;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:72.0pt;text-indent:-18.0pt;mso-list:l0 level1 lfo2">
<![if !supportLists]><span style="font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:16.0pt;color:#1F497D"><a href="https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.us%2Fv3%2F__https%3A%2Fcwe.ccsds.org%2Fmoims%2Fdocs%2FMOIMS-SMandC%2FMeeting*20Materials%2F2019%2FFall*202019%2FSecurity_Authentication*20and*20Access*20Control*20for*20MO*20Services_final.pdf__%3BJSUlJSUlJSU!!PvBDto6Hs4WbVuu7!ZASh8ARy3w73YAeFEYVr5ReOkHVZ9zONUObvTqad9T6Cd0q3CPf5BB6B9ADGFD2KSgo%24&data=04%7C01%7CMehran.Sarkarati%40esa.int%7C65ef09ea3a8e45a7087908d93bf0f54c%7C9a5cacd02bef4dd7ac5c7ebe1f54f495%7C0%7C0%7C637606728358526842%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=W5A1WS%2BSNxwTrmf4cQNHGTyLDJRepvqRC6wb8ClsZyQ%3D&reserved=0">https://cwe.ccsds.org/moims/docs/MOIMS-SMandC/Meeting%20Materials/2019/Fall%202019/Security_Authentication%20and%20Access%20Control%20for%20MO%20Services_final.pdf</a></span><o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:72.0pt;text-indent:-18.0pt;mso-list:l0 level1 lfo2">
<![if !supportLists]><span style="font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:16.0pt;color:#1F497D"><a href="https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.us%2Fv3%2F__https%3A%2Fcwe.ccsds.org%2Fmoims%2Fdocs%2FMOIMS-SMandC%2FMeeting*20Materials%2F2019%2FFall*202019%2FSecurity_Proposed*20modification*20of*20standards_final.pdf__%3BJSUlJSU!!PvBDto6Hs4WbVuu7!ZASh8ARy3w73YAeFEYVr5ReOkHVZ9zONUObvTqad9T6Cd0q3CPf5BB6B9ADG0IOL8Yo%24&data=04%7C01%7CMehran.Sarkarati%40esa.int%7C65ef09ea3a8e45a7087908d93bf0f54c%7C9a5cacd02bef4dd7ac5c7ebe1f54f495%7C0%7C0%7C637606728358536837%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=X%2BTvoi71PTv12H6jxBrLu2eVENvDkq3PMs%2B70wd66GE%3D&reserved=0">https://cwe.ccsds.org/moims/docs/MOIMS-SMandC/Meeting%20Materials/2019/Fall%202019/Security_Proposed%20modification%20of%20standards_final.pdf</a></span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:16.0pt;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:16.0pt;color:#1F497D">You will find many of the same issues in these documents that Howie and I identified in reply to your email. I could not find any SM&C WG meeting minutes that mentioned
that a security discussion occurred, much less listed any actions.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:16.0pt;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:16.0pt;color:#1F497D">Craig</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:16.0pt;color:#1F497D"> </span><o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" style="margin-left:36.0pt"><b><span style="font-size:16.0pt">From:</span></b><span style="font-size:16.0pt"> Weiss, Howard <Howard.Weiss@parsons.com>
<br>
<b>Sent:</b> Tuesday, June 29, 2021 10:53 AM<br>
<b>To:</b> Shames, Peter M (JPL-312B)[JPL Employee] <peter.m.shames@jpl.nasa.gov>; Sheehe, Charles J. (GRC-LCN0) <charles.j.sheehe@nasa.gov>; Biggerstaff, Craig (JSC-CD42)[SGT, INC] <craig.biggerstaff@nasa.gov><br>
<b>Cc:</b> Radulescu, Costin (JPL-9300)[JPL Employee] <cradule@jpl.nasa.gov><br>
<b>Subject:</b> Re: [EXTERNAL] RE: Issues with SM&C MO Ref Model treatment of security topics</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:16.0pt"> </span><o:p></o:p></p>
<p style="margin-left:36.0pt"><span style="font-size:18.0pt;color:black">Peter</span><o:p></o:p></p>
<p style="margin-left:36.0pt"><span style="font-size:18.0pt">…</span><o:p></o:p></p>
<p style="margin-left:36.0pt"> <o:p></o:p></p>
<p style="margin-left:36.0pt"><span style="font-size:18.0pt;color:black">From my recollections, we last met with them at the NASA/Ames meeting a couple of years ago. Daniel Fischer typically acted as the liaison between Security and SM&C, mostly because he
worked for Mario and Mario had been the head of SM&C. From a technical perspective, we mostly worked with Sam. I believe we gave them a very detailed list of issues at the Ames meeting but I'd have to dig around to see if I have it. Daniel, as the primary
interface, might have more than I have. I remember that the list of issues was lengthy and detailed. </span><o:p></o:p></p>
<p style="margin-left:36.0pt"><span style="font-size:18.0pt;color:black"> </span><o:p></o:p></p>
<p style="margin-left:36.0pt"><span style="font-size:18.0pt;color:black">howie</span><o:p></o:p></p>
<p style="margin-left:36.0pt"><span style="font-size:18.0pt;color:black"> </span><o:p></o:p></p>
<div id="Signature">
<div name="divtagdefaultwrapper">
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:12.0pt;font-family:"Tahoma",sans-serif;color:black"> </span><o:p></o:p></p>
</div>
<div style="margin-left:36.0pt">
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-size:12.0pt;color:black">
<hr size="0" width="100%" align="center">
</span></div>
</div>
<p class="MsoNormal" style="margin-left:36.0pt"><b><span style="font-size:12.0pt;font-family:"Verdana",sans-serif;color:black">HOWARD WEISS,
</span></b><b><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:black">CISSP</span></b><span style="font-size:12.0pt;color:black">
<br>
</span><span style="font-size:12.0pt;font-family:"Verdana",sans-serif;color:black">7110 Samuel Morse Drive<br>
Columbia, MD 21046<br>
443-430-8089 (office) / 443-494-9087 (cell) <br>
<a href="mailto:howard.weiss@parsons.com">howard.weiss@parsons.com</a><br>
<a href="https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.us%2Fv3%2F__https%3A%2Fgcc02.safelinks.protection.outlook.com%2F%3Furl%3Dhttp*3A*2F*2Fwww.parsons.com*2F%26data%3D04*7C01*7Ccraig.biggerstaff*40nasa.gov*7C90ede06a3a6140fe2b2708d93b192a7a*7C7005d45845be48ae8140d43da96dd17b*7C0*7C0*7C637605801541132868*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C1000%26sdata%3D0lRDT1*2BjXW5dxdT2nUeYZRc7XFumhb28F0NwPGrS*2B3U*3D%26reserved%3D0__%3BJSUlJSUlJSUlJSUlJSUlJSUlJQ!!PvBDto6Hs4WbVuu7!ZASh8ARy3w73YAeFEYVr5ReOkHVZ9zONUObvTqad9T6Cd0q3CPf5BB6B9ADGTZx92g8%24&data=04%7C01%7CMehran.Sarkarati%40esa.int%7C65ef09ea3a8e45a7087908d93bf0f54c%7C9a5cacd02bef4dd7ac5c7ebe1f54f495%7C0%7C0%7C637606728358536837%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=wucZ6FEQ5sqp3v8w8LDSzjBP4nZHBucFwz5SXX237GI%3D&reserved=0">www.parsons.com</a></span><o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#339966">Please consider the environment before printing this message</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:12.0pt;font-family:"Tahoma",sans-serif;color:black"> </span><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<div>
<div style="margin-left:36.0pt">
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-size:18.0pt;color:black">
<hr size="0" width="100%" align="center">
</span></div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:16.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:16.0pt">I downloaded the presentation and the paper that Daniel Fischer and his colleagues from ESA had provided back in Fall 2018 and again in Fall 2019.
In their analyses they identified, and carefully documented, the very same issues that I had raised. And they described the basis of their concerns in even greater depth, pointing out that the documented SM&C security mechanisms are susceptible to even fairly
primitive “man in the middle” attacks, let alone more sophisticated approaches. At that time, three years ago, they also proposed specific fixes and extensions that could have been adopted to fix these problems. It appears that these issues were swept aside
then, much as you chose to do yesterday. It also seems clear, given what was in the document and SM&C plans presented in the last CESG and CMC meetings, that in the intervening three years nothing has been done, and according to you, there are no plans to
fix this now.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:16.0pt">I must conclude that the statements you made yesterday about “We met with the SecWG 3 years ago and they agreed that we did everything we needed to.”
were inaccurate and rather misleading. In point of fact these same issues remain, the limitations of not having adequate security for multi-mission systems remans, and the potential consequences of not having adequate security have increased. I must also
point out that the way that these issues were handled, previously, and in yesterday’s meeting, are in violation of CCSDS principles for consensus operation. There is no part of the documented CCSDS process that says “ignore issues and brush them aside”.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:16.0pt">I do not believe that we can allow these issues to be ignored any longer, and that the CESG, as the appointed guardians of CCSDS architecture, processes,
document content, and quality, must insist that these issues are remedied before this document can be published.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:16.0pt">Regards, Peter Shames</span><o:p></o:p></p>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><span style="font-size:14.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:14.0pt;font-family:Helvetica">________________________________________________________<br>
<br>
Peter Shames<br>
CCSDS Systems Engineering Area Director<br>
<br>
Jet Propulsion Laboratory, MS 301-490<br>
California Institute of Technology<br>
Pasadena, CA 91109 USA <br>
<br>
Telephone: +1 818 354-5740, Fax: +1 818 393-6871<br>
<br>
Internet: <a href="https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2FPeter.M.Shames%40jpl.nasa.gov%2F&data=04%7C01%7CMehran.Sarkarati%40esa.int%7C65ef09ea3a8e45a7087908d93bf0f54c%7C9a5cacd02bef4dd7ac5c7ebe1f54f495%7C0%7C0%7C637606728358546829%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=XhMLoBA9%2FYnmIXP0G%2F5L%2F%2FkvphQIte25dhzVBOVhpyM%3D&reserved=0"><span style="color:blue">Peter.M.Shames@jpl.nasa.gov</span></a><br>
________________________________________________________<br>
<br>
We must recognize the strong and undeniable influence that our language exerts on our ways of thinking and, in fact, delimits the abstract space in which we can formulate - give form to - our thoughts.<br>
<br>
Niklaus Wirth</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:16.0pt"> </span><o:p></o:p></p>
</div>
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).
</body>
</html>