<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 14 (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:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 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:Georgia;
panose-1:2 4 5 2 5 4 5 2 3 3;}
@font-face
{font-family:"Helvetica Neue";}
@font-face
{font-family:"Franklin Gothic Book";
panose-1:2 11 5 3 2 1 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:Consolas;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle24
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></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=purple><div class=WordSection1><p class=MsoNormal><span style='color:#1F497D'>Michael:<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>We have discussed this a couple of times in the past on telecons, prior to Agency review. The issue is that the Security Glossary replicates a vast number of terms and definitions from copyrighted ISO books, and we do not have ISO permission to do that.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>I suspect that if ISO understands clearly that we intend to republish copyrighted ISO material and make it available for free on the CCSDS site, they might object. I also suspect, however, that if we approach it from the ISO-standardization perspective, that is, that the Security Glossary will be submitted via SC13 to become an ISO standard (not mentioning that the same book will be available for free from CCSDS), there is a possibility that ISO would simply grant permission.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Without explicit permission, I have serious qualms about releasing the document.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>In answer to one of your questions, “</span><span style='color:#1F497D'>Will additional terms be reproduced in future documents?”:<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>With respect to the Security WG, the purpose of the Glossary is to obviate having to replicate the terms in future documents; however, other WGs may want to publish similar glossaries of terms from other disciplines in the future, for much the same purpose.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>The current version of the Security Glossary is attached.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Tom<o:p></o:p></span></p><div><div style='mso-element:para-border-div;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'><o:p> </o:p></span></p></div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif";color:#1F497D'>Logothete, L.L.C.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif";color:#1F497D'>thomas.gannett@tgannett.net<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif";color:#1F497D'>+1 443 472 0805<o:p></o:p></span></p></div><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></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"'> Blackwood, Michael D. [mailto:MBlackwood@asrcfederal.com] <br><b>Sent:</b> Tuesday, February 04, 2020 10:18 AM<br><b>To:</b> Thomas Gannett; 'Shames, Peter M (US 312B)'; 'Weiss, Howard'; 'Barkley, Erik J (US 3970)'; Wilmot, Jonathan<br><b>Cc:</b> Blackwood, Michael D. (HQ-CG000)[Arctic Slope Technical Services, Inc.]; 'Space Assigned Numbers Authority'; 'CCSDS Engineering Steering Group - CESG Exec'<br><b>Subject:</b> RE: [Secretariat] [CESG] [EXTERNAL] Re: CESG Approval of Revised Information Security Glossary<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='color:#1F497D'>Hi Tom and All,<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>I’m not sure I fully understand the issue relating to using ISO terms nor am I familiar with the Security Glossary. Here are a few questions I would expect ISO to ask.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Is the intention to align terms in CCSDS documents with ISO terms and define them identically or is there another rationale for this reuse?<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>How many terms will be reproduced at this time?<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>From which ISO standards do these terms come?<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Will additional terms be reproduced in future documents?<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>How does CCSDS plan to attribute the origin of the terms in question?<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>The glossary itself answers most of these questions, so having a copy I can share with the ISO would be very helpful. Generally ISO allows extracts of standards in other publications with citation and cognizance of the user’s license for the ISO publication. CCSDS does not have a license for any ISO standards which may be a wrinkle.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Best regards,<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Michael Blackwood<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>CCSDS Secretariat<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>W: 301-837-3901 | <a href="mailto:michael.blackwood@asrcfederal.com">michael.blackwood@asrcfederal.com</a><o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>7515 Mission Drive, Seabrook, MD 20706<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>ASRC Federal | <i>Customer-Focused. Operationally Excellent.<o:p></o:p></i></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><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>From:</b> Secretariat [mailto:secretariat-bounces@mailman.ccsds.org] <b>On Behalf Of </b>Thomas Gannett<br><b>Sent:</b> Monday, February 3, 2020 3:32 PM<br><b>To:</b> 'Shames, Peter M (US 312B)' <peter.m.shames@jpl.nasa.gov>; 'Weiss, Howard' <Howard.Weiss@parsons.com>; 'Barkley, Erik J (US 3970)' <erik.j.barkley@jpl.nasa.gov>; Wilmot, Jonathan <jonathan.j.wilmot@nasa.gov><br><b>Cc:</b> Blackwood, Michael D. (HQ-CG000)[Arctic Slope Technical Services, Inc.] <michael.d.blackwood@nasa.gov>; 'Space Assigned Numbers Authority' <info@sanaregistry.org>; 'CCSDS Engineering Steering Group - CESG Exec' <cesg@mailman.ccsds.org><br><b>Subject:</b> Re: [Secretariat] [CESG] [EXTERNAL] Re: CESG Approval of Revised Information Security Glossary<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif";color:red'>[External Email]</span><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'> <o:p></o:p></span></p><div class=MsoNormal align=center style='text-align:center'><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><hr size=3 width="100%" align=center></span></div><p class=MsoNormal><span style='color:#1F497D'>Howie:<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></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.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></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.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></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).<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></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.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Tom<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-bottom:solid windowtext 1.0pt;padding:0in 0in 1.0pt 0in'><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif";color:#1F497D'><o:p> </o:p></span></p></div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif";color:#1F497D'>Logothete, L.L.C.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif";color:#1F497D'>thomas.gannett@tgannett.net<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif";color:#1F497D'>+1 443 472 0805<o:p></o:p></span></p></div><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></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<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></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.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></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.<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 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<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><p style='margin-left:.5in'>Peter<o:p></o:p></p><p style='margin-left:.5in'><o:p> </o:p></p><p style='margin-left:.5in'>Question - in its current state, can a CCSDS document use the SANA glossary as a normative reference? <o:p></o:p></p><p style='margin-left:.5in'><o:p> </o:p></p><p style='margin-left:.5in'>howie<o:p></o:p></p><p style='margin-left:.5in'><o:p> </o:p></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"'><o:p> </o:p></span></p></div><div style='margin-left:.5in'><div class=MsoNormal align=center style='text-align:center'><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><hr size=1 width="100%" 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"'><o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:7.5pt;font-family:"Tahoma","sans-serif";border:solid windowtext 1.0pt;padding:0in'><img border=0 width=250 height=55 id="Picture_x0020_3" src="cid:image002.jpg@01D5DB57.F0D9A210" alt="Image removed by sender. https://dadcowa.parsons.com/owa/service.svc/s/GetFileAttachment?id=AAMkADU3OTA4MzlmLTkxMGItNDY0Zi04OGNmLTMwOTZjYzM5YTM3MgBGAAAAAADnseb%2BLc5MQ6BtWqvkjs6CBwCqn5Imv8rRRJfroHJUWEZZAAAAAAEMAACqn5Imv8rRRJfroHJUWEZZAAMft6UoAAABEgAQANLe86Fi15NBgUxLIz1DQdM%3D&X-OWA-CANARY=lraV37OvLkKgdF6tZiDqj3WftAG-qNcIZs4vecQS_9P1fFASGrlDPWLji8cJIJ41HaJNwmPY_A8."></span><span style='font-size:7.5pt;font-family:"Tahoma","sans-serif"'><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"'><o:p></o:p></span></p></div></div></div></div></div></div></div></div></div></div></div></div></div><div><div style='margin-left:.5in'><div class=MsoNormal align=center style='text-align:center'><span style='color:#212121'><hr size=1 width="100%" 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'> <o:p></o:p></span></p><div><p class=MsoNormal style='margin-left:.5in'><span style='color:#212121'> <o:p></o:p></span></p></div></div><div><div><p class=MsoNormal style='margin-left:.5in'><span style='color:#212121'>Guys,<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='color:#212121'> <o:p></o:p></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.<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='color:#212121'> <o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='color:#212121'>That is the process and has been for years.<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='color:#212121'> <o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='color:#212121'>Thanks, Peter<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='color:#212121'> <o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='color:#212121'> <o:p></o:p></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'><o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:1.0in'><span style='color:#212121'> <o:p></o:p></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'><o:p></o:p></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'><o:p></o:p></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'><o:p></o:p></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'><o:p></o:p></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'><o:p></o:p></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'><o:p></o:p></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'><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 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<o:p></o:p></span></p></div></div><p class=MsoNormal style='margin-left:1.0in'><span style='color:#212121'> <o:p></o:p></span></p><p class=MsoNormal style='margin-left:1.0in'><span style='color:#212121'>Erik and Jonathan<o:p></o:p></span></p><p class=MsoNormal style='margin-left:1.0in'><span style='color:#212121'> <o:p></o:p></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. <o:p></o:p></span></p><p class=MsoNormal style='margin-left:1.0in'><span style='color:#212121'> <o:p></o:p></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?<o:p></o:p></span></p><p class=MsoNormal style='margin-left:1.0in'><span style='color:#212121'> <o:p></o:p></span></p><p class=MsoNormal style='margin-left:1.0in'><span style='color:#212121'>Regards<o:p></o:p></span></p><p class=MsoNormal style='margin-left:1.0in'><span style='color:#212121'> <o:p></o:p></span></p><p class=MsoNormal style='margin-left:1.0in'><span style='color:#212121'>howie<o:p></o:p></span></p><p class=MsoNormal style='margin-left:1.0in'><span style='color:#212121'> <o:p></o:p></span></p><div><p class=MsoNormal style='margin-left:1.0in'><span style='color:#212121'>----------<o:p></o:p></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'><o:p></o:p></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'><o:p></o:p></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'><o:p></o:p></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'><o:p></o:p></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'><o:p></o:p></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'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:1.0in'><a href="mailto:howard.weiss@parsons.com"><span style='font-size:10.0pt;font-family:"Franklin Gothic Book","sans-serif"'>howard.weiss@parsons.com</span></a><span style='color:#212121'><o:p></o:p></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'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:1.0in'><span style='color:#212121'> <o:p></o:p></span></p><p class=MsoNormal style='margin-left:1.0in'><span style='font-size:10.5pt;font-family:"Helvetica Neue";color:#333333'><img border=0 width=250 height=55 id="Picture_x0020_2" src="cid:image003.png@01D5DB57.F0D9A210" alt="cid:image003.png@01D5DB3C.0127BD80"></span><span style='color:#212121'><o:p></o:p></span></p></div><p class=MsoNormal style='margin-left:1.0in'><span style='color:#212121'> <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 style='margin-left:1.0in'><b><span style='color:#212121'>From:</span></b><span style='color:#212121'> SEA-SEC <</span><a href="mailto:sea-sec-bounces@mailman.ccsds.org">sea-sec-bounces@mailman.ccsds.org</a><span style='color:#212121'>> <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' <</span><a href="mailto:sea-sec@mailman.ccsds.org">sea-sec@mailman.ccsds.org</a><span style='color:#212121'>><br><b>Subject:</b> [EXTERNAL] [Sea-sec] CESG Approval of Revised Information Security Glossary<o:p></o:p></span></p></div></div><p class=MsoNormal style='margin-left:1.0in'><span style='color:#212121'> <o:p></o:p></span></p><p class=MsoNormal style='margin-left:1.0in'><span style='color:#212121'>FYI - The CESG has approved the revised Information Security Glossary:<o:p></o:p></span></p><p class=MsoNormal style='margin-left:1.0in'><span style='color:#212121'> <o:p></o:p></span></p><p class=MsoPlainText style='margin-left:1.0in'><span style='color:#212121'>* * * * * * * * * * * * * * * * * * * * * * * * <o:p></o:p></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:<o:p></o:p></span></p><p class=MsoPlainText style='margin-left:1.0in'><span style='color:#212121'> <o:p></o:p></span></p><p class=MsoPlainText style='margin-left:1.0in'><span style='color:#212121'> Abstain: 0 (0%) <o:p></o:p></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) <o:p></o:p></span></p><p class=MsoPlainText style='margin-left:1.0in;text-indent:.5in'><span style='color:#212121'>Approve with Conditions: 0 (0%) <o:p></o:p></span></p><p class=MsoPlainText style='margin-left:1.0in;text-indent:.5in'><span style='color:#212121'>Disapprove with Comment: 0 (0%)<o:p></o:p></span></p><p class=MsoPlainText style='margin-left:1.0in;text-indent:.5in'><span style='color:#212121'> <o:p></o:p></span></p><p class=MsoPlainText style='margin-left:1.0in'><span style='color:#212121'>CONDITIONS/COMMENTS:<o:p></o:p></span></p><p class=MsoPlainText style='margin-left:1.0in'><span style='color:#212121'> <o:p></o:p></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.<o:p></o:p></span></p><p class=MsoPlainText style='margin-left:1.0in'><span style='color:#212121'> <o:p></o:p></span></p><p class=MsoPlainText style='margin-left:1.0in'><span style='color:#212121'> Jonathan Wilmot (Approve<o:p></o:p></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?<o:p></o:p></span></p><p class=MsoPlainText style='margin-left:1.0in'><span style='color:#212121'> <o:p></o:p></span></p><p class=MsoPlainText style='margin-left:1.0in'><span style='color:#212121'> <o:p></o:p></span></p><p class=MsoPlainText style='margin-left:1.0in'><span style='color:#212121'>Total Respondents: 6<o:p></o:p></span></p><p class=MsoPlainText style='margin-left:1.0in'><span style='color:#212121'> <o:p></o:p></span></p><p class=MsoPlainText style='margin-left:1.0in'><span style='color:#212121'>All Areas responded to this question.<o:p></o:p></span></p><p class=MsoPlainText style='margin-left:1.0in'><span style='color:#212121'> <o:p></o:p></span></p><p class=MsoPlainText style='margin-left:1.0in'><span style='color:#212121'>SECRETARIAT INTERPRETATION OF RESULTS: Approved Unconditionally<o:p></o:p></span></p><p class=MsoPlainText style='margin-left:1.0in'><span style='color:#212121'>PROPOSED SECRETARIAT ACTION: Generate CMC poll<o:p></o:p></span></p><p class=MsoNormal style='margin-left:1.0in'><span style='color:#212121'> <o:p></o:p></span></p><p class=MsoNormal style='margin-left:1.0in'><span style='color:#212121'> <o:p></o:p></span></p><p class=MsoNormal style='margin-left:1.0in'><span style='color:#212121'>----------<o:p></o:p></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'><o:p></o:p></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'><o:p></o:p></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'><o:p></o:p></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'><o:p></o:p></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'><o:p></o:p></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'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:1.0in'><a href="mailto:howard.weiss@parsons.com"><span style='font-size:10.0pt;font-family:"Franklin Gothic Book","sans-serif"'>howard.weiss@parsons.com</span></a><span style='color:#212121'><o:p></o:p></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'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:1.0in'><span style='color:#212121'> <o:p></o:p></span></p><p class=MsoNormal style='margin-left:1.0in'><span style='font-size:10.5pt;font-family:"Helvetica Neue";color:#333333'><img border=0 width=250 height=55 id="Picture_x0020_1" src="cid:image003.png@01D5DB57.F0D9A210" alt="cid:image001.png@01D5DA79.6E6023B0"></span><span style='color:#212121'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:1.0in'><span style='color:#212121'> <o:p></o:p></span></p><p class=MsoNormal style='margin-left:1.0in'><span style='color:#212121'> <o:p></o:p></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'><o:p></o:p></span></p></div></div></div></div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p> </o:p></span></p><div class=MsoNormal align=center style='text-align:center'><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><hr size=2 width="100%" align=center></span></div><p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif";color:gray'><br>The preceding message (including attachments) is covered by the Electronic Communication Privacy Act, 18 U.S.C. sections 2510-2512, is intended only for the person or entity to which it is addressed, and may contain information that is confidential, protected by attorney-client or other privilege, or otherwise protected from disclosure by law. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error and destroy the original message and all copies.</span><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p></div></body></html>