<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=us-ascii">
<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;}
@font-face
{font-family:"Helvetica Neue";}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
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:#954F72;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.p1, li.p1, div.p1
{mso-style-name:p1;
margin-top:12.0pt;
margin-right:0cm;
margin-bottom:3.75pt;
margin-left:0cm;
font-size:9.0pt;
font-family:"Helvetica Neue";}
p.p2, li.p2, div.p2
{mso-style-name:p2;
margin:0cm;
margin-bottom:.0001pt;
font-size:9.0pt;
font-family:"Helvetica Neue";}
p.p3, li.p3, div.p3
{mso-style-name:p3;
margin:0cm;
margin-bottom:.0001pt;
font-size:9.0pt;
font-family:"Helvetica Neue";}
p.p4, li.p4, div.p4
{mso-style-name:p4;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:14.85pt;
margin-bottom:.0001pt;
font-size:9.0pt;
font-family:"Helvetica Neue";}
p.p5, li.p5, div.p5
{mso-style-name:p5;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:26.1pt;
margin-bottom:.0001pt;
font-size:9.0pt;
font-family:"Helvetica Neue";}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.EmailStyle25
{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:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
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-GB" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">As to the “homework” “what to do next”, we should also address at some point the remarks made by Peter Shames also in relation to the considerations drawn in IOAG about the overall security framework
in CCSDS and missing elements in DTN (i.e. those going beyond BPSEC). Specifically he pointed in a presentation shared in June to: “Key management and identity mechanisms need to be defined,
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Secure network management framework for multi-agency interoperability needs to be defined”.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Tomaso<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> SIS-DTN <sis-dtn-bounces@mailman.ccsds.org>
<b>On Behalf Of </b>Dr. Keith L Scott via SIS-DTN<br>
<b>Sent:</b> Donnerstag, 28. Juli 2022 17:56<br>
<b>To:</b> sis-dtn@mailman.ccsds.org<br>
<b>Subject:</b> [Sis-dtn] Telecon 20220728<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="p1"><b><span lang="EN-US">SIS-DTN</span></b><span lang="EN-US"><o:p></o:p></span></p>
<p class="p2"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="p1"><b><span lang="EN-US">IETF DTN WG Meeting</span></b><span lang="EN-US"><o:p></o:p></span></p>
<p class="p3"><span lang="EN-US">CCSDS:<o:p></o:p></span></p>
<p class="p4"><span lang="EN-US">• Talked about our ‘requirements’ for auditing / accounting / reliability<o:p></o:p></span></p>
<p class="p4"><span lang="EN-US">• Plan forward: do work, ensure that IETF DTN WG is cognizant of it; coordinate as makes sense<o:p></o:p></span></p>
<p class="p2"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="p3"><span lang="EN-US">Naming:<o:p></o:p></span></p>
<p class="p4"><span lang="EN-US">• I wasn’t able to make the second half of the DTN WG meeting where naming was discussed<o:p></o:p></span></p>
<p class="p4"><span lang="EN-US">• Apparently Airbus has some needs that aren’t well-met by ‘just’ an IPN Node #, looking for something more<o:p></o:p></span></p>
<p class="p4"><span lang="EN-US">• Scott proposed using ‘just’ IPN node numbers as the identification mechanism and developing ‘DNS-like’ and ‘whois-like’ services:<o:p></o:p></span></p>
<p class="p5"><span lang="EN-US">• DNS-like: transforms mnemonics into IPN node numbers<o:p></o:p></span></p>
<p class="p5"><span lang="EN-US">• whois-like: translates IPN node numbers into points-of-contact<o:p></o:p></span></p>
<p class="p5"><span lang="EN-US">• Need to secure both of these services (obviously)<o:p></o:p></span></p>
<p class="p2"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="p1"><b><span lang="EN-US">LTP Orange:</span></b><span lang="EN-US"><o:p></o:p></span></p>
<p class="p3"><span lang="EN-US">Need use cases / metrics for when orange is a win.<o:p></o:p></span></p>
<p class="p4"><span lang="EN-US">• E.g. with a latency of xxx and an LTP segment loss rate of yyy, using the metrics: (total memory*time used by receiver, total memory*time used by transmitter) ...<o:p></o:p></span></p>
<p class="p2"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="p3"><span lang="EN-US">If we can’t find a use case that is compelling, we shouldn’t include Orange (keep the protocol as simple as possible).<o:p></o:p></span></p>
<p class="p2"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="p1"><b><span lang="EN-US">Jonathan’s bit ordering question</span></b><span lang="EN-US"><o:p></o:p></span></p>
<p class="p3"><span lang="EN-US">In RFC9171, things like the Bundle Processing Control Flags refer to the ‘least significant bit’.<span class="apple-converted-space">
</span>Note that the BPCF is a bit field represented by a CBOR unsigned integer.<span class="apple-converted-space">
</span>In the integer representation of the CBOR unsigned int, ‘least significant bit’ is unambiguous (It’s the bit that determines whether the integer is odd or even).<o:p></o:p></span></p>
<p class="p2"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="p3"><span lang="EN-US">We don’t really care how the link layer might mangle things for transmission, so long as what is received is interpretable as (the same) CBOR unsigned integer, so the LSB makes sense.<o:p></o:p></span></p>
<p class="p1"><b><span lang="EN-US">Homework</span></b><span lang="EN-US"><o:p></o:p></span></p>
<p class="p4"><span lang="EN-US">• LTP Orange Question<o:p></o:p></span></p>
<p class="p4"><span lang="EN-US">• What to do next?<span class="apple-converted-space">
</span>BPsec Green, NM (Blue, Green), LTP<o:p></o:p></span></p>
<p class="p2"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="p1"><b><span lang="EN-US">Simon’s question about ADMs</span></b><span lang="EN-US"><o:p></o:p></span></p>
<p class="p3"><span lang="EN-US">We pushed a lot of things out of the BPv7 profile for expediency.<span class="apple-converted-space">
</span>Many of those SHOULD be addressable via network management.<span class="apple-converted-space">
</span>We should work a set of ADMs (e.g. BPv7, ION, LTPv2, ...) in concert with the ‘base’ NM protocol work as a sanity-check to ensure that the NM protocol will in fact support what we need.<span class="apple-converted-space">
</span>Use these to address the issues we pushed out of the base CCSDS BPv7 profile.<o:p></o:p></span></p>
<p class="p2"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="p3"><span lang="EN-US">There’s an (old) draft BP ADM here: <a href="https://datatracker.ietf.org/doc/draft-birrane-dtn-adm-bp/">
https://datatracker.ietf.org/doc/draft-birrane-dtn-adm-bp/</a> (thanks Sarah, for pointing this out).<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
</body>
</html>