<span style=" font-size:11pt;font-family:Calibri">Dear Tom and All,</span>
<br><span style=" font-size:11pt;font-family:Calibri">I will put
one item in the Agenda of the CESG Telecon - and also of future
CCSDS sessions - to recap the discussion about the SANA Glossary,
and its relation with the Glossaries of the CCSDS books.</span>
<br><span style=" font-size:11pt;font-family:Calibri">Namely: </span>
<br><span style=" font-size:11pt;font-family:Calibri">-
current situation of the SANA Glossary, where terms are derived
from normative as well as informative sources</span>
<br><span style=" font-size:11pt;font-family:Calibri">-
Evolution of the SANA Glossary , having either of the following
targets in mind: </span>
<br><span style=" font-size:11pt;font-family:Calibri"> o
to clearly identify/distinguish between normative
vs. informative terms (depending if e.g. they come from blue or from green
books), or </span>
<br><span style=" font-size:11pt;font-family:Calibri">o
to only leave normative terms in, thus aiming at fully normative
role of the Glossary </span>
<br><span style=" font-size:11pt;font-family:Calibri">o
other proposals, next steps and roadmap </span>
<br><span style=" font-size:11pt;font-family:Calibri">-
Terms and definitions replicated from copyrighted ISO publications
(issue is mainly with the Security Glossary) for which CCSDS does
not (yet) have ISO permission </span>
<br>
<br><span style=" font-size:11pt;font-family:Calibri">Kind regards,<br>
Margherita</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">--------------------------------------------------------------<br>
</span><span style=" font-size:8pt;color:#00a1e0;font-family:Verdana"><b>Margherita
di Giulio</b></span>
<br><span style=" font-size:8pt;color:#5f5f5f;font-family:Verdana">Ground
Station Systems Division</span>
<br><span style=" font-size:8pt;color:#5f5f5f;font-family:Verdana">Backend
Software Section (OPS-GSB)</span>
<br>
<br>
<br><span style=" font-size:8pt;color:#5f5f5f;font-family:Verdana"><b>European
Space Agency ESA/ESOC</b><br>
Robert-Bosch-Str. 5<br>
D-64293 Darmstadt - Germany<br>
Tel: +49-6151-902779<br>
e-mail: Margherita.di.Giulio@esa.int</span><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif"><br>
<br>
</span>
<br>
<br>
<br>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">From:
</span><span style=" font-size:9pt;font-family:sans-serif">"Thomas
Gannett" <thomas.gannett@tgannett.net></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">To:
</span><span style=" font-size:9pt;font-family:sans-serif"><Gian.Paolo.Calzolari@esa.int>,
"'Shames, Peter M\(US 312B\)'" <peter.m.shames@jpl.nasa.gov></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Cc:
</span><span style=" font-size:9pt;font-family:sans-serif">"'CCSDS
Engineering Steering Group - CESG Exec'" <cesg@mailman.ccsds.org>,
"'Space Assigned Numbers Authority'" <info@sanaregistry.org>,
"'CESG'" <cesg-bounces@mailman.ccsds.org>, "'Weiss,
Howard'" <Howard.Weiss@parsons.com></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Date:
</span><span style=" font-size:9pt;font-family:sans-serif">04/02/2020
18:55</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Subject:
</span><span style=" font-size:9pt;font-family:sans-serif">Re:
[CESG] [Secretariat] [EXTERNAL] Re: CESG Approval of Revised Information
Security Glossary</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Sent
by: </span><span style=" font-size:9pt;font-family:sans-serif">"CESG"
<cesg-bounces@mailman.ccsds.org></span>
<br>
<hr noshade>
<br>
<br>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">I
think perhaps the term “normative” needs to be defined in the SANA Glossary:
Even though the SANA Glossary contains terms derived from normative as
well as informative sources, the purpose of having the glossary is to normalize
the terms within the CCSDS. The Glossary is in fact intended to be “normative”
for the CCSDS regardless of the source of the terms: we do adjure all document
developers that they should consult it, preferentially use terms defined
in it, not arbitrarily redefine terms that already exist in it, etc.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">Unfortunately,
the SANA Glossary is also in a draft state, so discussions of its normative
force are academic at the present time.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#004080;font-family:Times New Roman"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#004080;font-family:Times New Roman">Logothete,
L.L.C.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#004080;font-family:Times New Roman">thomas.gannett@tgannett.net</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#004080;font-family:Times New Roman">+1
443 472 0805</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Tahoma"><b>From:</b>
Secretariat [</span><a href="mailto:secretariat-bounces@mailman.ccsds.org"><span style=" font-size:10pt;font-family:Tahoma">mailto:secretariat-bounces@mailman.ccsds.org</span></a><span style=" font-size:10pt;font-family:Tahoma">]
<b>On Behalf Of </b>Gian.Paolo.Calzolari@esa.int<b><br>
Sent:</b> Tuesday, February 04, 2020 5:56 AM<b><br>
To:</b> Shames, Peter M(US 312B)<b><br>
Cc:</b> Weiss, Howard; CCSDS Engineering Steering Group - CESG Exec; Space
Assigned Numbers Authority; CESG<b><br>
Subject:</b> Re: [Secretariat] [CESG] [EXTERNAL] Re: CESG Approval of Revised
Information Security Glossary</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Times New Roman"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Arial">There
is an additional case: terms defined in an informative annex of a Blue
Book. :o)</span><span style=" font-size:12pt;font-family:Times New Roman">
<br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
Regards</span><span style=" font-size:12pt;font-family:Times New Roman">
<br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
Gian Paolo</span><span style=" font-size:12pt;font-family:Times New Roman">
<br>
<br>
<br>
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
From: </span><span style=" font-size:9pt;font-family:Arial">"Shames,
Peter M\(US 312B\) via CESG" <cesg@mailman.ccsds.org></span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
To: </span><span style=" font-size:9pt;font-family:Arial">"Weiss,
Howard" <Howard.Weiss@parsons.com>, "Barkley, Erik J (US
3970)" <erik.j.barkley@jpl.nasa.gov>, "Jonathan Wilmot"
<Jonathan.J.Wilmot@NASA.gov></span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
Cc: </span><span style=" font-size:9pt;font-family:Arial">"Space
Assigned Numbers Authority" <info@sanaregistry.org>, "CCSDS
Engineering Steering Group - CESG Exec" <cesg@mailman.ccsds.org></span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
Date: </span><span style=" font-size:9pt;font-family:Arial">03-02-20
20:45</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
Subject: </span><span style=" font-size:9pt;font-family:Arial">Re:
[CESG] [EXTERNAL] Re: CESG Approval of Revised Information Security Glossary</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
Sent by: </span><span style=" font-size:9pt;font-family:Arial">"CESG"
<cesg-bounces@mailman.ccsds.org></span><span style=" font-size:12pt;font-family:Times New Roman">
</span></p>
<div align=center>
<hr noshade></div>
<p style="margin-top:0px;margin-Bottom:240px"><span style=" font-size:12pt;font-family:Times New Roman"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">I
would say that's a "qualified yes". The normative documents
in CCSDS are Blue and Magenta, and so the documents are authoritative.
The Glossary only contains terms that are published in CCSDS documents
and it includes the references to those source documents.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">The
"qualified" part is that there are terms in the Glossary that
were were pulled in from Green Books. As such these are not normative.
So as long as you stick with terms from normative documents I think
you are on safe ground.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Thanks,
Peter</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Calibri"><b>From:
</b>Howie Weiss <Howard.Weiss@parsons.com><b><br>
Date: </b>Monday, February 3, 2020 at 11:28 AM<b><br>
To: </b>Peter Shames <peter.m.shames@jpl.nasa.gov>, Erik Barkley
<erik.j.barkley@jpl.nasa.gov>, "Wilmot, Jonathan J. (GSFC-5820)"
<Jonathan.J.Wilmot@NASA.gov><b><br>
Cc: </b>CCSDS Engineering Steering Group - CESG Exec <cesg@mailman.ccsds.org>,
Space Assigned Numbers Authority <info@sanaregistry.org>, CCSDS Secretariat
<secretariat@mailman.ccsds.org><b><br>
Subject: </b>[EXTERNAL] Re: CESG Approval of Revised Information Security
Glossary</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Times New Roman"><br>
Peter <br>
<br>
Question - in its current state, can a CCSDS document use the SANA glossary
as a normative reference? <br>
<br>
howie <br>
</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Tahoma"> </span></p>
<div align=center>
<hr></div>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Tahoma"><b>HOWARD
WEISS, </b></span><span style=" font-size:8pt;font-family:Tahoma"><b>CISSP</b></span><span style=" font-size:10pt;font-family:Verdana"><br>
<br>
7110 Samuel Morse Drive<br>
Columbia, MD 21046<br>
443-430-8089 (office) / 443-494-9087 (cell) <br>
howard.weiss@parsons.com</span><span style=" font-size:12pt;color:blue;font-family:Times New Roman"><u><br>
</u></span><a href=www.parsons.com><span style=" font-size:10pt;color:blue;font-family:Verdana"><u>www.parsons.com</u></span></a></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:8pt;color:#3f8080;font-family:Tahoma"><br>
Please consider the environment before printing this message</span></p>
<div align=center>
<hr></div>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"><b>From:</b>
Shames, Peter M (US 312B) <peter.m.shames@jpl.nasa.gov><b><br>
Sent:</b> Monday, February 3, 2020 1:15 PM<b><br>
To:</b> Barkley, Erik J (US 3970); Weiss, Howard; Jonathan Wilmot<b><br>
Cc:</b> CCSDS Engineering Steering Group - CESG Exec; Space Assigned Numbers
Authority; CCSDS Secretariat<b><br>
Subject:</b> [EXTERNAL] Re: CESG Approval of Revised Information Security
Glossary</span><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri">
</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri">Guys,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri">Once
this document is approved those terms will be entered into / updated in
the SANA Terminology registry.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri">That
is the process and has been for years.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri">Thanks,
Peter</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Calibri"><b>From:
</b>Erik Barkley <erik.j.barkley@jpl.nasa.gov><b><br>
Date: </b>Monday, February 3, 2020 at 10:07 AM<b><br>
To: </b>Howie Weiss <Howard.Weiss@parsons.com>, "Wilmot, Jonathan
J. (GSFC-5820)" <Jonathan.J.Wilmot@NASA.gov><b><br>
Cc: </b>Peter Shames <peter.m.shames@jpl.nasa.gov><b><br>
Subject: </b>RE: CESG Approval of Revised Information Security Glossary</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:14pt;color:#004080;font-family:Georgia">Howie,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:14pt;color:#004080;font-family:Georgia"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:14pt;color:#004080;font-family:Georgia">Glad
to hear you agree with getting the terms into SANA. With regard to getting
“it” into SANA (existing glossary and/or security terms glossary – “it”
was not quite clear to me but I assume security terms) I think that is
something best initiated under the cognizance of the SE Area. I’ll
be happy to “second” any motion if need be, but I think the origin for
any such request has to be with the SE Area. I am copying Peter on this
email.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:14pt;color:#004080;font-family:Georgia"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:14pt;color:#004080;font-family:Georgia">Best
regards,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:14pt;color:#004080;font-family:Georgia">-Erik
</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:14pt;color:#004080;font-family:Georgia"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri"><b>From:</b>
Weiss, Howard <Howard.Weiss@parsons.com> <b><br>
Sent:</b> Friday, January 31, 2020 10:25<b><br>
To:</b> Jonathan Wilmot <Jonathan.J.Wilmot@NASA.gov>; Barkley, Erik
J (US 3970) <erik.j.barkley@jpl.nasa.gov><b><br>
Subject:</b> [EXTERNAL] FW: CESG Approval of Revised Information Security
Glossary</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri">Erik
and Jonathan</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri">I
just saw your comments regarding the Information Security Glossary and
I couldn’t agree with you more. </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri">It
has always been our plan that the glossary move into SANA. Others
have voiced the same opinion. However, there has been no movement.
I’ve heard that the existing glossary found on the SANA web site
required the first attention since its not been reviewed or revised. Maybe
you guys can initiate some movement to get it into SANA?</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri">Regards</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri">howie</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri">----------</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Franklin Gothic Book"><b> </b></span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;color:#2f2f2f;font-family:Franklin Gothic Book"><b>HOWARD
WEISS</b></span><span style=" font-size:9pt;color:#2f2f2f;font-family:Franklin Gothic Book"><b>,
</b></span><span style=" font-size:8pt;color:#2f2f2f;font-family:Franklin Gothic Book"><b>CISSP</b></span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:9pt;color:#2f2f2f;font-family:Franklin Gothic Book"><b> </b></span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;color:#2f2f2f;font-family:Franklin Gothic Book"><b>PARSONS,
Inc.</b></span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;color:#2f2f2f;font-family:Franklin Gothic Book">7110
Samuel Morse Dr, Suite 200</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;color:#2f2f2f;font-family:Franklin Gothic Book">Columbia,
MD 21046</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><a href=mailto:howard.weiss@parsons.com><span style=" font-size:10pt;color:#0082bf;font-family:Franklin Gothic Book"><u>howard.weiss@parsons.com</u></span></a></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;color:#2f2f2f;font-family:Franklin Gothic Book">443-430-8089
(office) / 443-494-9087 (mobile)</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><img src=cid:_4_1A2D19EC1A2D178000586917C1258505 style="border:0px solid;"></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri"><b>From:</b>
SEA-SEC <</span><a href="mailto:sea-sec-bounces@mailman.ccsds.org"><span style=" font-size:11pt;color:#0082bf;font-family:Calibri"><u>sea-sec-bounces@mailman.ccsds.org</u></span></a><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri">>
<b>On Behalf Of </b>Weiss, Howard<b><br>
Sent:</b> Friday, January 31, 2020 1:19 PM<b><br>
To:</b> 'sea-sec@mailman.ccsds.org' <</span><a href="mailto:sea-sec@mailman.ccsds.org"><span style=" font-size:11pt;color:#0082bf;font-family:Calibri"><u>sea-sec@mailman.ccsds.org</u></span></a><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri">><b><br>
Subject:</b> [EXTERNAL] [Sea-sec] CESG Approval of Revised Information
Security Glossary</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri">FYI
- The CESG has approved the revised Information Security Glossary:</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri">*
* * * * * * * * * * * * * * * * * * * * * * * </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri">CESG
E-Poll Identifier: CESG-P-2019-12-004 Approval to publish CCSDS 350.8-M-2,
Information Security Glossary of Terms (Magenta Book, Issue 2) Results
of CESG poll beginning 31 December 2019 and ending 29 January 2020:</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri">
Abstain: 0 (0%) </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri">Approve
Unconditionally: 6 (100%) (Barkley, Merri, Shames, Burleigh, Moury,
Wilmot) </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri">Approve
with Conditions: 0 (0%) </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri">Disapprove
with Comment: 0 (0%)</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri">CONDITIONS/COMMENTS:</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri">
Erik Barkley (Approve Unconditionally): A comment/question
(not a condition): Seems like it would make sense to have this in
SANA rather than a book -- has that been considered? In terms of normative
application the MB could still be normative in identifying SANA registry
and the update/governance policy.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri">
Jonathan Wilmot (Approve</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri">Unconditionally):
I agree with Eric that glossaries would be better in SANA as they
are living documents that will change over time. Example: where would
terms from BPsec be placed?</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri">Total
Respondents: 6</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri">All
Areas responded to this question.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri">SECRETARIAT
INTERPRETATION OF RESULTS: Approved Unconditionally</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri">PROPOSED
SECRETARIAT ACTION: Generate CMC
poll</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri">----------</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Franklin Gothic Book"><b> </b></span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;color:#2f2f2f;font-family:Franklin Gothic Book"><b>HOWARD
WEISS</b></span><span style=" font-size:9pt;color:#2f2f2f;font-family:Franklin Gothic Book"><b>,
</b></span><span style=" font-size:8pt;color:#2f2f2f;font-family:Franklin Gothic Book"><b>CISSP</b></span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:9pt;color:#2f2f2f;font-family:Franklin Gothic Book"><b> </b></span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;color:#2f2f2f;font-family:Franklin Gothic Book"><b>PARSONS,
Inc.</b></span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;color:#2f2f2f;font-family:Franklin Gothic Book">7110
Samuel Morse Dr, Suite 200</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;color:#2f2f2f;font-family:Franklin Gothic Book">Columbia,
MD 21046</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><a href=mailto:howard.weiss@parsons.com><span style=" font-size:10pt;color:#0082bf;font-family:Franklin Gothic Book"><u>howard.weiss@parsons.com</u></span></a></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;color:#2f2f2f;font-family:Franklin Gothic Book">443-430-8089
(office) / 443-494-9087 (mobile)</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><img src=cid:_4_1B74DFBC1B74DD5000586917C1258505 alt=cid:image001.png@01D5DA79.6E6023B0 style="border:0px solid;"></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#2f2f2f;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;color:#2f2f2f;font-family:Franklin Gothic Book">NOTICE:
This email message and all attachments transmitted with it may contain
privileged and confidential information, and information that is protected
by, and proprietary to, Parsons Corporation, and is intended solely for
the use of the addressee for the specific purpose set forth in this communication.
If the reader of this message is not the intended recipient, you are hereby
notified that any reading, dissemination, distribution, copying, or other
use of this message or its attachments is strictly prohibited, and you
should delete this message and all copies and backups thereof. The recipient
may not further distribute or use any of the information contained herein
without the express written authorization of the sender. If you have received
this message in error, or if you have any questions regarding the use of
the proprietary information contained therein, please contact the sender
of this message immediately, and the sender will provide you with further
instructions.</span><span style=" font-size:10pt;font-family:Courier New">_______________________________________________<br>
CESG mailing list<br>
CESG@mailman.ccsds.org</span><span style=" font-size:12pt;color:blue;font-family:Times New Roman"><u><br>
</u></span><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg"><span style=" font-size:10pt;color:blue;font-family:Courier New"><u>https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg</u></span></a></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">This
message is intended only for the recipient(s) named above. It may contain
proprietary information and/or</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">protected
content. Any unauthorised disclosure, use, retention or dissemination is
prohibited. If you have received</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">this
e-mail in error, please notify the sender immediately. ESA applies appropriate
organisational measures to protect</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">personal
data, in case of data privacy queries, please contact the ESA Data Protection
Officer (dpo@esa.int).</span><tt><span style=" font-size:10pt">_______________________________________________<br>
CESG mailing list<br>
CESG@mailman.ccsds.org<br>
</span></tt><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg"><tt><span style=" font-size:10pt">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg</span></tt></a><tt><span style=" font-size:10pt"><br>
</span></tt></p>
<p style="margin-top:0px;margin-Bottom:0px"></p>
<p style="margin-top:0px;margin-Bottom:0px"></p>
<PRE>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).
</PRE>