<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style type="text/css" style="display:none"><!--P{margin-top:0;margin-bottom:0;} @font-face
        {font-family:Calibri}
@font-face
        {font-family:Tahoma}
@font-face
        {font-family:Consolas}
@font-face
        {font-family:Verdana}
@font-face
        {font-family:Georgia}
@font-face
        {font-family:"Helvetica Neue"}
@font-face
        {font-family:"Franklin Gothic Book"}
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri","sans-serif"}
a:link, span.MsoHyperlink
        {color:#0563C1;
        text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
        {color:purple;
        text-decoration:underline}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri","sans-serif"}
span.PlainTextChar
        {font-family:Consolas}
span.EmailStyle19
        {font-family:"Calibri","sans-serif";
        color:windowtext}
span.EmailStyle21
        {font-family:"Calibri","sans-serif";
        color:#1F497D}
.MsoChpDefault
        {font-size:10.0pt}
@page WordSection1
        {margin:1.0in 1.0in 1.0in 1.0in}
div.WordSection1
        {}--></style>
</head>
<body dir="ltr" style="font-size:12pt;color:#000000;background-color:#FFFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p>Tom</p>
<p><br>
</p>
<p>I understand the permissions issue with ISO.  However, my angle is wouldn't it be nice to just have one universal glossary as a reference in all books?  New books could reference the SANA glossary and then would only have to define terms that are not found
 in the universal glossary.  This would be remedied after the book is published and the terms are pulled into the universal glossary.
</p>
<p><br>
</p>
<p>But, since the SANA glossary doesn't exist as a document, and if all of the ISO issues disappeared, how would it be referenced in a document?  As a URL?
</p>
<p><br>
</p>
<p>regards</p>
<p><br>
</p>
<p>howie<br>
</p>
<p><br>
</p>
<div id="Signature">
<div name="divtagdefaultwrapper" style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:; margin:0">
<div style="font-size:13px">
<div style="font-size:13px">
<div style="font-size:13px">
<div style="font-size:13px">
<div style="font-size:13px">
<div style="font-size:13px">
<div style="font-size:13px">
<div style="font-size:13px">
<div style="font-size:13px">
<div style="font-size:13px">
<div style="font-size:13px">
<div style="font-family:Tahoma; font-size:13px"><font style="font-family:Verdana" size="2"><span style="font-weight:bold"><br>
</span></font></div>
<hr style="font-family:Tahoma; width:100%; height:2px">
<font style=""><span style="font-weight:bold"></span></font><span style="font-weight:bold"><font face="Verdana, Geneva, sans-serif"><font style="" size="2">HOWARD WEISS</font>,
<font style="" size="1">CISSP</font></font></span><br>
<br>
<font style="font-family:Tahoma" size="1"><font size="2"></font><font size="2" face="Verdana, Geneva, sans-serif">7110 Samuel Morse Drive<br>
Columbia, MD 21046<br>
443-430-8089 (office) / 443-494-9087 (cell) <br>
howard.weiss@parsons.com<br>
www.parsons.com</font><br>
</font></div>
<div style="font-family:Tahoma; font-size:13px"><br>
</div>
<div style="font-family:Tahoma; font-size:13px"><font size="1"><span style="color:rgb(51,153,102)">Please consider the environment before printing this message</span></font><br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<div style="color: rgb(33, 33, 33);">
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font style="font-size:11pt" face="Calibri, sans-serif" color="#000000"><b>From:</b> Thomas Gannett <thomas.gannett@tgannett.net><br>
<b>Sent:</b> Monday, February 3, 2020 3:31 PM<br>
<b>To:</b> 'Shames, Peter M (US 312B)'; Weiss, Howard; 'Barkley, Erik J (US 3970)'; 'Jonathan Wilmot'<br>
<b>Cc:</b> 'Space Assigned Numbers Authority'; 'CCSDS Engineering Steering Group - CESG Exec'; Blackwood, Michael D. (HQ-CG000)[Arctic Slope Technical Services, Inc.]<br>
<b>Subject:</b> RE: [Secretariat] [EXTERNAL] Re: CESG Approval of Revised Information Security Glossary</font>
<div> </div>
</div>
<div>
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Howie:</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D">The way we currently view things is that terms in the glossary are derived, along with their normative force, if any, from published CCSDS documents. So you could reference the SANA glossary, because the SANA
 glossary references the normative source document, but it would seem to me to be more precise simply to reference the document.</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D">The peculiar wrinkle in this case is that, so far, we don’t actually have permission from ISO to go far beyond fair use in borrowing terms wholesale from copyrighted ISO documents.</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D">I personally would like to see such permission in writing before releasing the document on the CCSDS site.  The situation could actually arise in which we are unable to release the document publicly—or we release
 it and are then asked to take it down.  If that were to happen, the terms would nevertheless have found their way into the SANA glossary, making it the only viable reference (provided ISO doesn’t know about it).</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D">I’m not trying to give everyone heartburn so much as to remind Michael he’s supposed to see about getting ISO permission.</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D">Tom</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<div>
<div style="border:none; border-bottom:solid windowtext 1.0pt; padding:0in 0in 1.0pt 0in">
<p class="MsoNormal" style="border:none; padding:0in"><span style="font-size:12.0pt; font-family:"Times New Roman","serif"; color:#1F497D"> </span></p>
</div>
<p class="MsoNormal"><span style="font-size:12.0pt; font-family:"Times New Roman","serif"; color:#1F497D">Logothete, L.L.C.</span></p>
<p class="MsoNormal"><span style="font-size:12.0pt; font-family:"Times New Roman","serif"; color:#1F497D">thomas.gannett@tgannett.net</span></p>
<p class="MsoNormal"><span style="font-size:12.0pt; font-family:"Times New Roman","serif"; color:#1F497D">+1 443 472 0805</span></p>
</div>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<div>
<div style="border:none; border-top:solid #B5C4DF 1.0pt; padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif""> Secretariat [mailto:secretariat-bounces@mailman.ccsds.org]
<b>On Behalf Of </b>Shames, Peter M (US 312B) via Secretariat<br>
<b>Sent:</b> Monday, February 03, 2020 2:46 PM<br>
<b>To:</b> Weiss, Howard; Barkley, Erik J (US 3970); Jonathan Wilmot<br>
<b>Cc:</b> CCSDS Secretariat; Space Assigned Numbers Authority; CCSDS Engineering Steering Group - CESG Exec<br>
<b>Subject:</b> Re: [Secretariat] [EXTERNAL] Re: CESG Approval of Revised Information Security Glossary</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<p class="MsoNormal">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.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">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.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Thanks, Peter</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> </p>
<div style="border:none; border-top:solid #B5C4DF 1.0pt; padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-left:.5in"><b><span style="font-size:12.0pt; color:black">From:
</span></b><span style="font-size:12.0pt; color:black">Howie Weiss <Howard.Weiss@parsons.com><br>
<b>Date: </b>Monday, February 3, 2020 at 11:28 AM<br>
<b>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><br>
<b>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><br>
<b>Subject: </b>[EXTERNAL] Re: CESG Approval of Revised Information Security Glossary</span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> </p>
</div>
<p style="margin-left:.5in">Peter</p>
<p style="margin-left:.5in"> </p>
<p style="margin-left:.5in">Question - in its current state, can a CCSDS document use the SANA glossary as a normative reference?  </p>
<p style="margin-left:.5in"> </p>
<p style="margin-left:.5in">howie</p>
<p style="margin-left:.5in"> </p>
<div id="Signature">
<div name="divtagdefaultwrapper">
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif""> </span></p>
</div>
<div style="margin-left:.5in">
<div class="MsoNormal" style="text-align:center" align="center"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"">
<hr width="100%" size="1" align="center">
</span></div>
</div>
<p class="MsoNormal" style="margin-left:.5in"><b><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"">HOWARD WEISS,
</span></b><b><span style="font-size:7.5pt; font-family:"Tahoma","sans-serif"">CISSP</span></b><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif""><br>
<br>
</span><span style="font-size:10.0pt; font-family:"Verdana","sans-serif"">7110 Samuel Morse Drive<br>
Columbia, MD 21046<br>
443-430-8089 (office) / 443-494-9087 (cell) <br>
howard.weiss@parsons.com<br>
www.parsons.com</span><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif""></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:7.5pt; font-family:"Tahoma","sans-serif""><img id="_x0000_i1028" alt="https://dadcowa.parsons.com/owa/service.svc/s/GetFileAttachment?id=AAMkADU3OTA4MzlmLTkxMGItNDY0Zi04OGNmLTMwOTZjYzM5YTM3MgBGAAAAAADnseb%2BLc5MQ6BtWqvkjs6CBwCqn5Imv8rRRJfroHJUWEZZAAAAAAEMAACqn5Imv8rRRJfroHJUWEZZAAMft6UoAAABEgAQANLe86Fi15NBgUxLIz1DQdM%3D&X-OWA-CANARY=lraV37OvLkKgdF6tZiDqj3WftAG-qNcIZs4vecQS_9P1fFASGrlDPWLji8cJIJ41HaJNwmPY_A8." width="250" height="55" src="https://webportal.parsons.com/owa/service.svc/s/,DanaInfo=dadcowa.parsons.com,SSL+GetFileAttachment?id=AAMkADU3OTA4MzlmLTkxMGItNDY0Zi04OGNmLTMwOTZjYzM5YTM3MgBGAAAAAADnseb%2BLc5MQ6BtWqvkjs6CBwCqn5Imv8rRRJfroHJUWEZZAAAAAAEMAACqn5Imv8rRRJfroHJUWEZZAAMft6UoAAABEgAQANLe86Fi15NBgUxLIz1DQdM%3D&X-OWA-CANARY=lraV37OvLkKgdF6tZiDqj3WftAG-qNcIZs4vecQS_9P1fFASGrlDPWLji8cJIJ41HaJNwmPY_A8."><br>
<span style="color:#339966">Please consider the environment before printing this message</span></span><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif""></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<div>
<div style="margin-left:.5in">
<div class="MsoNormal" style="text-align:center" align="center"><span style="color:#212121">
<hr width="100%" size="1" align="center">
</span></div>
</div>
<div id="divRplyFwdMsg">
<p class="MsoNormal" style="margin-left:.5in"><b><span style="color:black">From:</span></b><span style="color:black"> Shames, Peter M (US 312B) <peter.m.shames@jpl.nasa.gov><br>
<b>Sent:</b> Monday, February 3, 2020 1:15 PM<br>
<b>To:</b> Barkley, Erik J (US 3970); Weiss, Howard; Jonathan Wilmot<br>
<b>Cc:</b> CCSDS Engineering Steering Group - CESG Exec; Space Assigned Numbers Authority; CCSDS Secretariat<br>
<b>Subject:</b> [EXTERNAL] Re: CESG Approval of Revised Information Security Glossary</span><span style="color:#212121">
</span></p>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#212121"> </span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#212121">Guys,</span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#212121"> </span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#212121">Once this document is approved those terms will be entered into / updated in the SANA Terminology registry.</span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#212121"> </span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#212121">That is the process and has been for years.</span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#212121"> </span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#212121">Thanks, Peter</span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#212121"> </span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#212121"> </span></p>
<div style="border:none; border-top:solid #B5C4DF 1.0pt; padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-left:1.0in"><b><span style="font-size:12.0pt; color:black">From:
</span></b><span style="font-size:12.0pt; color:black">Erik Barkley <erik.j.barkley@jpl.nasa.gov><br>
<b>Date: </b>Monday, February 3, 2020 at 10:07 AM<br>
<b>To: </b>Howie Weiss <Howard.Weiss@parsons.com>, "Wilmot, Jonathan J. (GSFC-5820)" <Jonathan.J.Wilmot@NASA.gov><br>
<b>Cc: </b>Peter Shames <peter.m.shames@jpl.nasa.gov><br>
<b>Subject: </b>RE: CESG Approval of Revised Information Security Glossary</span><span style="color:#212121"></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:1.0in"><span style="color:#212121"> </span></p>
</div>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:14.0pt; font-family:"Georgia","serif"; color:#1F497D">Howie,</span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:14.0pt; font-family:"Georgia","serif"; color:#1F497D"> </span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:14.0pt; font-family:"Georgia","serif"; color:#1F497D">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><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:14.0pt; font-family:"Georgia","serif"; color:#1F497D"> </span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:14.0pt; font-family:"Georgia","serif"; color:#1F497D">Best regards,</span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:14.0pt; font-family:"Georgia","serif"; color:#1F497D">-Erik
</span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:14.0pt; font-family:"Georgia","serif"; color:#1F497D"> </span><span style="color:#212121"></span></p>
<div>
<div style="border:none; border-top:solid #E1E1E1 1.0pt; padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-left:1.0in"><b><span style="color:#212121">From:</span></b><span style="color:#212121"> Weiss, Howard <Howard.Weiss@parsons.com>
<br>
<b>Sent:</b> Friday, January 31, 2020 10:25<br>
<b>To:</b> Jonathan Wilmot <Jonathan.J.Wilmot@NASA.gov>; Barkley, Erik J (US 3970) <erik.j.barkley@jpl.nasa.gov><br>
<b>Subject:</b> [EXTERNAL] FW: CESG Approval of Revised Information Security Glossary</span></p>
</div>
</div>
<p class="MsoNormal" style="margin-left:1.0in"><span style="color:#212121"> </span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="color:#212121">Erik and Jonathan</span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="color:#212121"> </span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="color:#212121">I just saw your comments regarding the Information Security Glossary and I couldn’t agree with you more. 
</span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="color:#212121"> </span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="color:#212121">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 class="MsoNormal" style="margin-left:1.0in"><span style="color:#212121"> </span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="color:#212121">Regards</span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="color:#212121"> </span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="color:#212121">howie</span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="color:#212121"> </span></p>
<div>
<p class="MsoNormal" style="margin-left:1.0in"><span style="color:#212121">----------</span></p>
<p class="MsoNormal" style="margin-left:1.0in"><b><span style="font-family:"Franklin Gothic Book","sans-serif"; color:#212121"> </span></b><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><b><span style="font-size:10.0pt; font-family:"Franklin Gothic Book","sans-serif"; color:#212121">HOWARD WEISS</span></b><b><span style="font-size:9.0pt; font-family:"Franklin Gothic Book","sans-serif"; color:#212121">,
</span></b><b><span style="font-size:8.0pt; font-family:"Franklin Gothic Book","sans-serif"; color:#212121">CISSP</span></b><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><b><span style="font-size:9.0pt; font-family:"Franklin Gothic Book","sans-serif"; color:#212121"> </span></b><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><b><span style="font-size:10.0pt; font-family:"Franklin Gothic Book","sans-serif"; color:#212121">PARSONS, Inc.</span></b><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:10.0pt; font-family:"Franklin Gothic Book","sans-serif"; color:#212121">7110 Samuel Morse Dr, Suite 200</span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:10.0pt; font-family:"Franklin Gothic Book","sans-serif"; color:#212121">Columbia, MD 21046</span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:10.0pt; font-family:"Franklin Gothic Book","sans-serif"; color:#212121"><a href="mailto:howard.weiss@parsons.com">howard.weiss@parsons.com</a></span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:10.0pt; font-family:"Franklin Gothic Book","sans-serif"; color:#212121">443-430-8089 (office) / 443-494-9087 (mobile)</span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="color:#212121"> </span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:10.5pt; font-family:"Helvetica Neue"; color:#333333"><img id="_x0000_i1026" width="250" height="55" border="0" src="cid:image001.png@01D5DAA3.F48A33C0"></span><span style="color:#212121"></span></p>
</div>
<p class="MsoNormal" style="margin-left:1.0in"><span style="color:#212121"> </span></p>
<div>
<div style="border:none; border-top:solid #E1E1E1 1.0pt; padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-left:1.0in"><b><span style="color:#212121">From:</span></b><span style="color:#212121"> SEA-SEC <<a href="mailto:sea-sec-bounces@mailman.ccsds.org">sea-sec-bounces@mailman.ccsds.org</a>>
<b>On Behalf Of </b>Weiss, Howard<br>
<b>Sent:</b> Friday, January 31, 2020 1:19 PM<br>
<b>To:</b> 'sea-sec@mailman.ccsds.org' <<a href="mailto:sea-sec@mailman.ccsds.org">sea-sec@mailman.ccsds.org</a>><br>
<b>Subject:</b> [EXTERNAL] [Sea-sec] CESG Approval of Revised Information Security Glossary</span></p>
</div>
</div>
<p class="MsoNormal" style="margin-left:1.0in"><span style="color:#212121"> </span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="color:#212121">FYI - The CESG has approved the revised Information Security Glossary:</span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="color:#212121"> </span></p>
<p class="MsoPlainText" style="margin-left:1.0in"><span style="color:#212121">* * * * * * * * * * * * * * * * * * * * * * * *
</span></p>
<p class="MsoPlainText" style="margin-left:1.0in"><span style="color:#212121">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 class="MsoPlainText" style="margin-left:1.0in"><span style="color:#212121"> </span></p>
<p class="MsoPlainText" style="margin-left:1.0in"><span style="color:#212121">               Abstain:  0 (0%)
</span></p>
<p class="MsoPlainText" style="margin-left:1.0in; text-indent:.5in"><span style="color:#212121">Approve Unconditionally:  6 (100%) (Barkley, Merri, Shames, Burleigh, Moury, Wilmot)
</span></p>
<p class="MsoPlainText" style="margin-left:1.0in; text-indent:.5in"><span style="color:#212121">Approve with Conditions:  0 (0%)
</span></p>
<p class="MsoPlainText" style="margin-left:1.0in; text-indent:.5in"><span style="color:#212121">Disapprove with Comment:  0 (0%)</span></p>
<p class="MsoPlainText" style="margin-left:1.0in; text-indent:.5in"><span style="color:#212121"> </span></p>
<p class="MsoPlainText" style="margin-left:1.0in"><span style="color:#212121">CONDITIONS/COMMENTS:</span></p>
<p class="MsoPlainText" style="margin-left:1.0in"><span style="color:#212121"> </span></p>
<p class="MsoPlainText" style="margin-left:1.0in"><span style="color:#212121">     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 class="MsoPlainText" style="margin-left:1.0in"><span style="color:#212121"> </span></p>
<p class="MsoPlainText" style="margin-left:1.0in"><span style="color:#212121">     Jonathan Wilmot (Approve</span></p>
<p class="MsoPlainText" style="margin-left:1.0in"><span style="color:#212121">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 class="MsoPlainText" style="margin-left:1.0in"><span style="color:#212121"> </span></p>
<p class="MsoPlainText" style="margin-left:1.0in"><span style="color:#212121"> </span></p>
<p class="MsoPlainText" style="margin-left:1.0in"><span style="color:#212121">Total Respondents:  6</span></p>
<p class="MsoPlainText" style="margin-left:1.0in"><span style="color:#212121"> </span></p>
<p class="MsoPlainText" style="margin-left:1.0in"><span style="color:#212121">All Areas responded to this question.</span></p>
<p class="MsoPlainText" style="margin-left:1.0in"><span style="color:#212121"> </span></p>
<p class="MsoPlainText" style="margin-left:1.0in"><span style="color:#212121">SECRETARIAT INTERPRETATION OF RESULTS:  Approved Unconditionally</span></p>
<p class="MsoPlainText" style="margin-left:1.0in"><span style="color:#212121">PROPOSED SECRETARIAT ACTION:            Generate CMC poll</span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="color:#212121"> </span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="color:#212121"> </span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="color:#212121">----------</span></p>
<p class="MsoNormal" style="margin-left:1.0in"><b><span style="font-family:"Franklin Gothic Book","sans-serif"; color:#212121"> </span></b><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><b><span style="font-size:10.0pt; font-family:"Franklin Gothic Book","sans-serif"; color:#212121">HOWARD WEISS</span></b><b><span style="font-size:9.0pt; font-family:"Franklin Gothic Book","sans-serif"; color:#212121">,
</span></b><b><span style="font-size:8.0pt; font-family:"Franklin Gothic Book","sans-serif"; color:#212121">CISSP</span></b><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><b><span style="font-size:9.0pt; font-family:"Franklin Gothic Book","sans-serif"; color:#212121"> </span></b><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><b><span style="font-size:10.0pt; font-family:"Franklin Gothic Book","sans-serif"; color:#212121">PARSONS, Inc.</span></b><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:10.0pt; font-family:"Franklin Gothic Book","sans-serif"; color:#212121">7110 Samuel Morse Dr, Suite 200</span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:10.0pt; font-family:"Franklin Gothic Book","sans-serif"; color:#212121">Columbia, MD 21046</span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:10.0pt; font-family:"Franklin Gothic Book","sans-serif"; color:#212121"><a href="mailto:howard.weiss@parsons.com">howard.weiss@parsons.com</a></span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:10.0pt; font-family:"Franklin Gothic Book","sans-serif"; color:#212121">443-430-8089 (office) / 443-494-9087 (mobile)</span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="color:#212121"> </span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:10.5pt; font-family:"Helvetica Neue"; color:#333333"><img id="Picture_x0020_1" alt="cid:image001.png@01D5DA79.6E6023B0" width="250" height="55" border="0" src="cid:image001.png@01D5DAA3.F48A33C0"></span><span style="color:#212121"></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="color:#212121"> </span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="color:#212121"> </span></p>
<div>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:10.0pt; font-family:"Franklin Gothic Book","sans-serif"; color:#212121">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="color:#212121"></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>