<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:x="urn:schemas-microsoft-com:office:excel" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size: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="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Dear CMC members, et al,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">During today’s CMC meeting I presented the first two pages of the attached presentation, which is what was presented to the IOAG a couple weeks ago. These two pages were created as a collaboration between ESA and NASA to briefly describe
what we could agree upon about the motivation and technical challenges in the context of multi-agency DTN deployments. This stated, in a very abbreviated form, the key motivations and technical challenges for DTN interoperability.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The bottom line is that while the DTN protocols that are published have some key security features for authentication and encryption, a complete framework for secure DTN interoperability and management has yet to be standardized. The consequence
is that all arrangements for secure identity, key management, and network management must be handled as local matters, or shared privately between partners. This approach can be made to work, but it is not likely to result in a broadly interoperable framework.
This is a rather complicated set of technical topics, but also one that CCSDS must tackle, preferably with the support and concurrence of agency and mission security experts. As Jonathan pointed out this security and identity framework could have much broader
applicability for other spacecraft on-board services such as software authentication and instrument identification.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We all acknowledge, I believe, that this is a somewhat “delicate” topic because it must touch upon agency and mission security approaches. At the same time, I wish to point out that we do have similar kinds of interoperable security mechanisms
that are used terrestrially, by all agencies, to secure identities, provide access control, and perform routing and network management. What we are proposing here is to do the work, now, to determine which, if any, of these widely used and understood terrestrial
security approaches can be adopted or adapted for use in space. This should not (really, must not) involve exposing any details of deeper agency security approaches.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I have included in this package the rest of the slides that I prepared, but at Klaus-Juergen’s request did not present. These are the work that I, and other CCSDS security, DTN, and system architecture experts did to more fully explore
the motivations, issues, and approaches that might be adopted within CCSDS to provide standardized solutions to these challenges. You may choose to only look at the first two pages, which are the joint ESA/NASA materials, or to read the entire package. These
materials are all aligned with concepts that have been identified in the existing IOAG Lunar and Mars comm architecture documents, but which CCSDS has yet to standardize.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The rest of the package goes into each of these subjects in more depth. The entire package has been reviewed by NASA/JPL Export Control and is cleared for open, public, release. You are free to share these with any of your CCSDS participants
or with your own agency or mission security staff. I would personally request that you do that and see what the analysis of your experts reveals. This is not yet a “technical solution”, more like a deeper exploration of the challenges and the solution space.
Blame me for any errors or mis-statements.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Finally, as I requested at the end of the discussion, would you each try to find a way within your own agency constraints to identify a security expert who could meet with both our existing CCSDS Security and DTN WG experts, and each other,
to start to discuss a possible set of acceptable solutions. That would represent a huge step forward toward real space internetworking interoperability. Even if the initial steps were just to identify a sort of “recommended practice cookbook” for the initial
SSI Stage 1 deployments that would be a move toward creating and preserving interoperability in this growing segment of space operations.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best regards, Peter<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">CESG <cesg-bounces@mailman.ccsds.org> on behalf of CESG <cesg@mailman.ccsds.org><br>
<b>Reply-To: </b>Michael Blackwood <MBlackwood@asrcfederal.com><br>
<b>Date: </b>Wednesday, June 15, 2022 at 5:38 AM<br>
<b>To: </b>CMC <CMC@mailman.ccsds.org><br>
<b>Cc: </b>CESG <cesg@mailman.ccsds.org><br>
<b>Subject: </b>[EXTERNAL] [CESG] Agenda Item - CESG Topics<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">Dear CMC and CESG Members,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">With the addition of an agenda item to discuss any CESG topics of interest to the CMC today, I have collected some topics, issues and concerns reported by the CESG yesterday. We may discuss some or all today and you can use this list for
future reference.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best regards,<o:p></o:p></p>
<p class="MsoNormal"><b><span style="color:#595959"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><b><span style="color:#595959">Michael Blackwood</span></b><span style="color:#ED5A24"><br>
</span><i><span style="font-size:9.0pt;color:#595959">CCSDS Secretariat</span></i><o:p></o:p></p>
<p class="MsoNormal" style="line-height:12.0pt;text-autospace:none"><span style="font-size:9.0pt"><a href="mailto:mblackwood@asrcfederal.com">mblackwood@asrcfederal.com</a><o:p></o:p></span></p>
<p class="MsoNormal" style="line-height:12.0pt;text-autospace:none"><span style="font-size:9.0pt;color:#E5A941">o:</span><span style="font-size:9.0pt;color:#595959"> (301) 837-3901<o:p></o:p></span></p>
<p class="MsoNormal" style="line-height:12.0pt;text-autospace:none"><span style="font-size:9.0pt;color:#595959">7000 Muirkirk Meadows Drive, Beltsville, MD 20705<o:p></o:p></span></p>
<p class="MsoNormal"><a href="https://urldefense.us/v3/__https:/www.asrcfederal.com/__;!!PvBDto6Hs4WbVuu7!YWKIKwO0h9yY1UoB3xZXMPnktVl_kTQXbYjDD0posIixDnhwa7thwrzsIQdDFD5DqPhZlGvR$" target="_blank"><span style="font-size:9.0pt">asrcfederal.com</span></a><b><span style="font-size:9.0pt;color:#4E869E">
</span></b><span style="font-size:9.0pt;color:#E5A941">|</span><b><span style="font-size:9.0pt;color:#4E869E">
</span></b><span style="font-size:9.0pt;color:#4E869E">Purpose Driven. Enduring Commitment.</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="0" width="100%" align="center">
</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.<br>
<br>
</span><o:p></o:p></p>
</div>
</body>
</html>