<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=Windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@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">OK, I’ve uploaded all the PIDs to the “CESG Review 1 20221000” folder. There are the RID-formatted ones from SLS and the document markup from Peter (in the .docx document). In the document I inserted Peter’s comments as comments and replied
to most of them. I think there are a couple large topics listed below (though I invite folks to correct that assessment). As a way to address some of these I added some text to the end of section 2 talking about ongoing / future work; many of Peter’s comments
dealt with things like “how do I know the source EID of this bundle isn’t spoofed”? I think the way we’ve thought of to address that is BPsec, so there’s a little bit of text there about BPsec and network management. Have a look, comment at will.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Larger topics for discussion:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">1) What information needs to be in a node / EID registry? e.g. should it contain information about the convergence layers a node supports or other (detailed) configuration information? What if those convergence layers / the configuration
information vary with time?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Options for information here include:<o:p></o:p></p>
<p class="MsoNormal">Node Number<o:p></o:p></p>
<p class="MsoNormal">POC<o:p></o:p></p>
<p class="MsoNormal">Mission<o:p></o:p></p>
<p class="MsoNormal">Bundle Protocol versions supported<o:p></o:p></p>
<p class="MsoNormal">Physical asset to which this node is tied / on which the node is hosted<o:p></o:p></p>
<p class="MsoNormal">Maximum supported bundle size<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">EID naming schemes supported<o:p></o:p></p>
<p class="MsoNormal">List of extension block types supported<o:p></o:p></p>
<p class="MsoNormal">Does the node support BPsec?<o:p></o:p></p>
<p class="MsoNormal">Does the node implement standardized network management?<o:p></o:p></p>
<p class="MsoNormal">If implements standardized network management, which ADMs?<o:p></o:p></p>
<p class="MsoNormal">Lit of Convergence Layer Adaptors supported<o:p></o:p></p>
<p class="MsoNormal">The number of kilobytes of storage allocated to bundle retention at this node and not currently occupied by bundles.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">---- <I think the following are 'too much' for the 'node number' registry -- Maybe we define some sort of separate 'ops' registry for highly-dynamic information?> ------<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">CL addresses / names (e.g. DNS name to resolve to an IP address)<o:p></o:p></p>
<p class="MsoNormal">Schedule for when communications are supported (contact plan)<o:p></o:p></p>
<p class="MsoNormal">Security key information (to support identity)<o:p></o:p></p>
<p class="MsoNormal">Services supported by this node (e.g. bping, cfdp, ...)<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">2b) For the moment, until we (SIS-DTN and SEA-SEC) work out something better, the key management solution (both for configuring keys / key management and exchanging keymat so as to identify peers) is going to be 'manual'.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">3) It might be worth adding a subsection to the end of section 2 that discusses ongoing / future work. Such a subsection could talk about BPsec and a bit about how we envision its use to support authentication / identity, and network management
including the types of information we expect to be managed by some of the basic ADMs.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">How MUCH do we need to discuss security (and potential security policies) there? We have a BPsec Red Book and a Green Book in the current charter.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> --keith<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>