<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;}
@font-face
{font-family:"Helvetica Neue";
panose-1:2 0 5 3 0 0 0 2 0 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.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
p.p1, li.p1, div.p1
{mso-style-name:p1;
margin-top:12.0pt;
margin-right:0in;
margin-bottom:3.75pt;
margin-left:0in;
font-size:9.0pt;
font-family:"Helvetica Neue";}
p.p2, li.p2, div.p2
{mso-style-name:p2;
margin:0in;
font-size:9.0pt;
font-family:"Helvetica Neue";}
p.p3, li.p3, div.p3
{mso-style-name:p3;
margin:0in;
font-size:9.0pt;
font-family:"Helvetica Neue";}
p.p4, li.p4, div.p4
{mso-style-name:p4;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:14.85pt;
font-size:9.0pt;
font-family:"Helvetica Neue";}
p.p5, li.p5, div.p5
{mso-style-name:p5;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:26.1pt;
font-size:9.0pt;
font-family:"Helvetica Neue";}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
.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>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="p1"><b>SIS-DTN</b><o:p></o:p></p>
<p class="p2"><o:p> </o:p></p>
<p class="p1"><b>IETF DTN WG Meeting</b><o:p></o:p></p>
<p class="p3">CCSDS:<o:p></o:p></p>
<p class="p4">• Talked about our ‘requirements’ for auditing / accounting / reliability<o:p></o:p></p>
<p class="p4">• Plan forward: do work, ensure that IETF DTN WG is cognizant of it; coordinate as makes sense<o:p></o:p></p>
<p class="p2"><o:p> </o:p></p>
<p class="p3">Naming:<o:p></o:p></p>
<p class="p4">• I wasn’t able to make the second half of the DTN WG meeting where naming was discussed<o:p></o:p></p>
<p class="p4">• Apparently Airbus has some needs that aren’t well-met by ‘just’ an IPN Node #, looking for something more<o:p></o:p></p>
<p class="p4">• Scott proposed using ‘just’ IPN node numbers as the identification mechanism and developing ‘DNS-like’ and ‘whois-like’ services:<o:p></o:p></p>
<p class="p5">• DNS-like: transforms mnemonics into IPN node numbers<o:p></o:p></p>
<p class="p5">• whois-like: translates IPN node numbers into points-of-contact<o:p></o:p></p>
<p class="p5">• Need to secure both of these services (obviously)<o:p></o:p></p>
<p class="p2"><o:p> </o:p></p>
<p class="p1"><b>LTP Orange:</b><o:p></o:p></p>
<p class="p3">Need use cases / metrics for when orange is a win.<o:p></o:p></p>
<p class="p4">• 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></p>
<p class="p2"><o:p> </o:p></p>
<p class="p3">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></p>
<p class="p2"><o:p> </o:p></p>
<p class="p1"><b>Jonathan’s bit ordering question</b><o:p></o:p></p>
<p class="p3">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></p>
<p class="p2"><o:p> </o:p></p>
<p class="p3">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></p>
<p class="p1"><b>Homework</b><o:p></o:p></p>
<p class="p4">• LTP Orange Question<o:p></o:p></p>
<p class="p4">• What to do next?<span class="apple-converted-space"> </span>BPsec Green, NM (Blue, Green), LTP<o:p></o:p></p>
<p class="p2"><o:p> </o:p></p>
<p class="p1"><b>Simon’s question about ADMs</b><o:p></o:p></p>
<p class="p3">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></p>
<p class="p2"><o:p> </o:p></p>
<p class="p3">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></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>