<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:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:NotesEsa;
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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-ligatures:standardcontextual;}
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;
mso-ligatures:standardcontextual;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@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:1410997781;
mso-list-template-ids:2084579592;}
@list l1
{mso-list-id:1643804579;
mso-list-template-ids:-609186956;}
@list l2
{mso-list-id:1649170033;
mso-list-type:hybrid;
mso-list-template-ids:-243244300 134807567 134807577 134807579 134807567 134807577 134807579 134807567 134807577 134807579;}
@list l2:level1
{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">Hi Daniel (et al),<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I agree that the Org & Proc doc is a little confusing on this matter (and others, I might add). The reason is that the Org & Proc is organized along the lines of “responsibilities”, for each of the categories; CMC, CESG, AD, WG chair.
But what we have been trying to do is to discuss a “procedure”, which in this case cross cuts: WG, AD, CESG, and CMC. So yes, we are trying to find all the “procedure threads” and pull them out of a “responsibility” document. I would note that there are
some “procedure” parts in the Org and Proc too, such as CESG Meetings, Sec 5.2.3 or On-line Voting, Sec 5.3, but not in this case.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">My own re-statement of what I believe is accurate is this:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoNormal" style="color:black;mso-list:l0 level1 lfo4"><span style="mso-ligatures:none">AD asks WG and CMC for candidates (Sec. 2.3.3.4)</span><span style="font-size:10.0pt;mso-ligatures:none"><o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l0 level1 lfo4"><span style="mso-ligatures:none">CMC is given a month to respond (Sec 2.3.3.4, which sometimes results in a one month séance during which there is dead silence)</span><span style="font-size:10.0pt;mso-ligatures:none"><o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l0 level1 lfo4"><span style="mso-ligatures:none">AD selects from the available candidates (Sec 2.3.3.4) and asks the CESG to approve / concur (Sec. 2.3.2.3.n)</span><span style="font-size:10.0pt;mso-ligatures:none"><o:p></o:p></span></li></ol>
<p class="MsoNormal"><span style="mso-ligatures:none"><o:p> </o:p></span></p>
<p class="MsoNormal">As you note, it is often the case that the AD will ask the WG if they have an obvious candidate, but there is no mention of “agree upon”. In practice that’s a good thing to do, but it is not stated. The WG, after all, is our experts in
that field of technical subject matter. If there is more than one candidate (a very lucky and unusual situation in my experience) then the AD has to make a choice. There is no stated process nor guidance for doing this, so you are free to use any process
you wish. I tend to favor an extremely murky crystal ball, but other options are available. That’s a joke, of course. If there are choices and there is a question of who might make the best candidate I tend to go ask trusted experts who know the field better
than I do.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I will make a different, but somewhat related, point, since we are having this discussion. There is nothing in the CCSDS Org and Proc doc about trying to maintain anything like appropriate balance among agencies. In this context it is
always of interest that Klaus-Juergen, and the CESG chairs who preceded him, have always reported at the Plenary meetings on Agency participation statistics. This is a demonstration that the various Agencies are actually invested in, and support, what we
do. But the focus in the Org & Proc is on picking the best candidates for any position (at all levels). And that is someone who has (quoting from the WG Chair, Sec 2.3.3.4):<o:p></o:p></p>
<p style="margin-left:.5in"><span style="font-size:12.0pt;font-family:"TimesNewRomanPSMT",serif;color:#0070C0">“Candidates for selection as WG chairs must be recognized as a leading technical expert in the field covered by that WG. Candidates may come from
any organization (including industry) and do not have to be employees of space agencies. “</span><span style="color:#0070C0"><o:p></o:p></span></p>
<p class="MsoNormal">The point I am trying to make here, even though it is not written anywhere, is that sometimes we may make candidate choices to try and maintain some acceptable level of organizational balance as well. This is just sensible because it is
a way of helping to ensure that all of the significant contributing member agencies actively demonstrate that they are invested in the CCSDS organization and our products by supporting key leadership positions.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks, 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;mso-ligatures:none">From:
</span></b><span lang="EN-GB" style="font-size:12.0pt;color:black;mso-ligatures:none">Daniel Fischer <Daniel.Fischer@esa.int><br>
<b>Date: </b>Wednesday, October 11, 2023 at 9:02 AM<br>
<b>To: </b>Ignacio Sanchez-Aguillar <Ignacio.Aguilar.Sanchez@esa.int>, Peter Shames <peter.m.shames@jpl.nasa.gov>, CCSDS Secretariat <secretariat@mailman.ccsds.org><br>
<b>Cc: </b>CESG <cesg@mailman.ccsds.org><br>
<b>Subject: </b>[EXTERNAL] RE: CCSDS Resolution SEA-R-2023-10-001, appointment of Marcus Wallum as the SEA Security WG Deputy Chair<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="mso-ligatures:none"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-GB">Hi all,<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">Just to remark that for the MOIMS SM&C deputy chair appointment, I did follow what is written in 2.3.3.4 (I made a typo in my mail this morning by referring to 2.3.2.3…should have been 2.3.3.4), at least the way I understand
it. In simple terms, the procedure according to my interpretation is (for an existing WG):<o:p></o:p></span></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l2 level1 lfo3"><span lang="EN-GB">WG and AD to agree on candidate<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l2 level1 lfo3"><span lang="EN-GB">AD to send a mail to CMC with the proposed candidate asking for additional nominations (30 days time)<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l2 level1 lfo3"><span lang="EN-GB">If no additional nominations are received, after 30 days, AD to proceed with requesting a CESG poll. If there are additional candidates actually 2.3.3.4 is very
unclear on how to proceed (I did not have the case yet).<o:p></o:p></span></li></ol>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">Is my understanding correct?<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">Cheers<br>
Daniel<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><b><u><span lang="EN-GB" style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:gray"> </span></u></b><span lang="EN-GB" style="font-size:8.5pt;font-family:"Arial",sans-serif;color:black"><br>
</span><b><span lang="EN-GB" style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:gray">ESA – European Space Agency</span></b><span lang="EN-GB" style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:gray"><br>
Daniel Fischer </span><span lang="EN-GB" style="font-size:7.5pt;font-family:"Arial",sans-serif;color:gray">I</span><span lang="EN-GB" style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:gray"> Head of Ground Segment System and Cybersecurity Engineering<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:gray">Ground Segment Engineering and Innovation Department</span><span lang="EN-GB" style="font-size:8.5pt;font-family:"Arial",sans-serif;color:black"><br>
</span><span lang="EN-GB" style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:gray">Directorate of Operations</span><span lang="EN-GB" style="font-size:8.5pt;font-family:"Arial",sans-serif;color:black"><br>
</span><span lang="EN-GB" style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:gray">ESOC </span><span lang="EN-GB" style="font-size:7.5pt;font-family:"Arial",sans-serif;color:gray">I</span><span lang="EN-GB" style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:gray"> Robert-Bosch-Str.
5, 64293 Darmstadt, Germany<br>
Tel: +49 6151 902718</span><span lang="EN-GB" style="font-size:8.5pt;font-family:"Arial",sans-serif;color:black"><br>
</span><span lang="EN-GB" style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:gray"><a href="mailto:Daniel.Fischer@esa.int">Daniel.Fischer@esa.int</a> </span><span lang="EN-GB" style="font-size:7.5pt;font-family:"Arial",sans-serif;color:gray">I</span><span lang="EN-GB" style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:gray">
<a href="https://urldefense.us/v3/__http:/www.esa.int/__;!!PvBDto6Hs4WbVuu7!KvF9p2altA9mSyOGUxWFg27gi2fu8aGHLhtwyIiK_N3JLYQKvDRvqSdRGW2QtvTb7NDIFyy28SsFgTpgW5NCzdz1Z6iF-EBdlw$"><span style="color:blue">www.esa.int</span></a></span><span lang="EN-GB" style="mso-ligatures:none"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="mso-ligatures:none">From:</span></b><span style="mso-ligatures:none"> CESG <cesg-bounces@mailman.ccsds.org>
<b>On Behalf Of </b>Ignacio Aguilar Sanchez via CESG<br>
<b>Sent:</b> Wednesday, October 11, 2023 3:17 PM<br>
<b>To:</b> Shames, Peter M (US 312B) <peter.m.shames@jpl.nasa.gov>; CCSDS Secretariat <secretariat@mailman.ccsds.org><br>
<b>Cc:</b> CESG <cesg@mailman.ccsds.org><br>
<b>Subject:</b> Re: [CESG] CCSDS Resolution SEA-R-2023-10-001, appointment of Marcus Wallum as the SEA Security WG Deputy Chair<br>
<b>Importance:</b> High<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">Dear Peter, Daniel and CESG 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">I would like to raise a point concerning the appointments for WG Chairs and Co-chairs as per CCSDS Org & Proc, A02.1-Y-4c2.<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">Based on recent CMC and CESG correspondence (Optical WG Chair, SEA Sec Deputy Chair, MOIMS SM&C WG Deputy Chair) there seem to be at least two ways in which a WG Chair and Co-chair can be nominated.<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">In SLS we follow the (lengthy) process dictated by Sec. 2.3.3.4. It involves CMC. Such process is identified as a Cor. 2 in the document, which I interpret as a most recent modification.<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">In SEA and MOIMS reference is made to a specific CESG responsibility identified by Section 2.3.2.3, n) “Approving WG Chairs and Deputy Chairs”.
<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">It shall be mentioned that such responsibility is the first sentence found in Sec. 2.3.3.4<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">As far as I understand, the absence of alternative candidates to those proposed by an Area Director can only be formally established by applying the procedure in Sec. 2.3.3.4.<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">In the case of the Optical WG Chair, following the mailing to CMC I have received a request a few days later from one of our main space agencies asking for the remaining time they had to propose a candidate. I referred
to Sec. 2.3.3.4 and the 30 calendar days established for an existing WG.<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">I believe we should discuss this point as soon as possible and hopefully agree on what the applied procedure shall be.<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">Kind regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none">Ignacio</span><span lang="EN-GB" style="mso-ligatures:none"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:8.5pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none"><br>
<br>
</span><b><span lang="EN-GB" style="font-size:10.0pt;font-family:NotesEsa;color:#4F4F4F;mso-ligatures:none">Ignacio Aguilar Sánchez</span></b><span lang="EN-GB" style="font-size:8.5pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none"><br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:NotesEsa;color:#4F4F4F;mso-ligatures:none">Communication Systems Engineer</span><span lang="EN-GB" style="font-size:8.5pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none"><br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:NotesEsa;color:#4F4F4F;mso-ligatures:none">Electrical Engineering Department</span><span lang="EN-GB" style="font-size:8.5pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none"><br>
<br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:NotesEsa;color:#4F4F4F;mso-ligatures:none">European Space Research and Technology Centre<br>
Keplerlaan 1, PO Box 299, 2200 AG Noordwijk, The Netherlands<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt;font-family:NotesEsa;color:#4F4F4F;mso-ligatures:none">Mob.+31641360257</span><span lang="EN-GB" style="font-size:8.5pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none"><br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:NotesEsa;color:#4F4F4F;mso-ligatures:none">Fax +31715655418</span><span lang="EN-GB" style="font-size:8.5pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none"><br>
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:NotesEsa;color:#4F4F4F;mso-ligatures:none">Email:
<a href="mailto:ignacio.aguilar.sanchez@esa.int"><span style="color:blue">ignacio.aguilar.sanchez@esa.int</span></a><br>
</span><span lang="EN-GB" style="font-size:8.5pt;font-family:"Arial",sans-serif;color:black;mso-ligatures:none"><a href="https://urldefense.us/v3/__http:/www.esa.int/__;!!PvBDto6Hs4WbVuu7!KvF9p2altA9mSyOGUxWFg27gi2fu8aGHLhtwyIiK_N3JLYQKvDRvqSdRGW2QtvTb7NDIFyy28SsFgTpgW5NCzdz1Z6iF-EBdlw$" target="_blank"><span style="font-size:10.0pt;font-family:NotesEsa;color:blue">www.esa.int</span></a></span><span lang="EN-GB" style="mso-ligatures:none"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="mso-ligatures:none">From:</span></b><span style="mso-ligatures:none"> CESG <<a href="mailto:cesg-bounces@mailman.ccsds.org">cesg-bounces@mailman.ccsds.org</a>>
<b>On Behalf Of </b>Shames, Peter M (US 312B) via CESG<br>
<b>Sent:</b> Tuesday, October 10, 2023 9:02 PM<br>
<b>To:</b> CCSDS Secretariat <<a href="mailto:secretariat@mailman.ccsds.org">secretariat@mailman.ccsds.org</a>><br>
<b>Cc:</b> Marcus Wallum <<a href="mailto:Marcus.Wallum@esa.int">Marcus.Wallum@esa.int</a>>; Howie Weiss <<a href="mailto:Howard.Weiss@parsons.com">Howard.Weiss@parsons.com</a>>; CESG <<a href="mailto:cesg@mailman.ccsds.org">cesg@mailman.ccsds.org</a>><br>
<b>Subject:</b> [CESG] CCSDS Resolution SEA-R-2023-10-001, appointment of Marcus Wallum as the SEA Security WG Deputy Chair<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-ligatures:none">Dear CCSDS Secretariat,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-ligatures:none"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-ligatures:none">Resolution: Appointment of Marcus Wallum as the SEA Security WG Deputy Chair<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-ligatures:none"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-ligatures:none">The Systems Engineering Area,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-ligatures:none"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-ligatures:none">CONSIDERING that the position of SEA Security WG Deputy Chair is open,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-ligatures:none">And that ESA has nominated Marcus Wallum, who has been an active member of the WG, to fill that position,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-ligatures:none">And that Marcus has the necessary experience in the WG and excellent credentials.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-ligatures:none">And RECOGNIZING that responsibility for recommending a WG Deputy Chair is an AD responsibility, <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-ligatures:none">And that approving the WG Deputy Chair is a CESG responsibility (CCSDS Org & Proc, A02.1-Y-4c2, Sec 2.3.2.3 CESG Responsibilities, Clause n)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-ligatures:none"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-ligatures:none">RESOLVES to request CESG to approve the appointment of Marcus Wallum as the SEA Security WG Deputy Chair, and<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-ligatures:none"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-ligatures:none">REQUESTS that a CESG poll be conducted to accomplish this.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black;mso-ligatures:none"> <o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-ligatures:none">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 (<a href="mailto:dpo@esa.int">dpo@esa.int</a>).
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-ligatures:none">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>