<html 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=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:12.0pt;
font-family:"Calibri",sans-serif;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
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:3.75pt;
margin-left:0in;
font-size:9.0pt;
font-family:"Helvetica Neue";}
p.p6, li.p6, div.p6
{mso-style-name:p6;
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;}
span.EmailStyle28
{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;}
/* List Definitions */
@list l0
{mso-list-id:91366412;
mso-list-type:hybrid;
mso-list-template-ids:-1482911038 134807569 134807577 134807579 134807567 134807577 134807579 134807567 134807577 134807579;}
@list l0:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1
{mso-list-id:772281374;
mso-list-template-ids:-159754406;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">OK, so we don’t have to worry about an APID for SPP, great.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">For CLs, we can certainly include a TCP CL; I’d suggest the one that is standardized in the IETF as part of the BPv7 suite. It should be pretty easy from a standardization / implementation standpoint.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> --keith<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><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-bottom:12.0pt"><b><span style="color:black">From:
</span></b><span style="color:black">Tomaso.deCola@dlr.de <Tomaso.deCola@dlr.de><br>
<b>Date: </b>Thursday, July 1, 2021 at 4:17 PM<br>
<b>To: </b>Dr. Keith L Scott <kscott@mitre.org>, sis-dtn@mailman.ccsds.org <sis-dtn@mailman.ccsds.org><br>
<b>Subject: </b>[EXT] RE: SIS-DTN Telecon Notes 20210630<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt">Hi Keith, all,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Just two considerations:</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo3"><span style="font-size:11.0pt">SPP APID: as mentioned on the chat, the SANA registry for the APID is now counting only one approved APID. In the past there were two more for CFDP and
LTP over SPP, but it was agreed in the latest specification of SPP (you can check Annex 2 for SANA considerations) that APID definitions should be mission specific and therefore no specific protocol mapping would be defined in the specification. This is a
point we also discussed with Scott last Autumn once the spec was out, just to have some thoughts on how it could work for us. But as said at that point, any mission will be free to select its own APID(s) apparently.</span><o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo3"><span style="font-size:11.0pt">Concerning CLs for BP, in the past we were also envisaging the case of BP over TCP for the terrestrial links, in case bundles could be forwarded from
the ground station to the users by using classical TCP/IP infrastructure. Should this be considered too here, or will we in any case refer to the TCPCL spec from IETF?</span><o:p></o:p></li></ol>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">My 0.02 cents,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Tomaso</span><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt">From:</span></b><span style="font-size:11.0pt"> SIS-DTN <sis-dtn-bounces@mailman.ccsds.org>
<b>On Behalf Of </b>Dr. Keith L Scott<br>
<b>Sent:</b> Mittwoch, 30. Juni 2021 18:07<br>
<b>To:</b> sis-dtn@mailman.ccsds.org<br>
<b>Subject:</b> [Sis-dtn] SIS-DTN Telecon Notes 20210630</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="p1"><b>SIS-DTN Telecon</b><o:p></o:p></p>
<p class="p2"> <o:p></o:p></p>
<p class="p3">BPsec -- Ed asked SEA-SEC for a quick review of format from the old SBSP book<o:p></o:p></p>
<p class="p2"> <o:p></o:p></p>
<p class="p3">LTP Orange<o:p></o:p></p>
<p class="p4">• Discussion<o:p></o:p></p>
<p class="p4">• Implementation<o:p></o:p></p>
<p class="p4">• Use cases?<o:p></o:p></p>
<p class="p2"> <o:p></o:p></p>
<p class="p1"><b>BPv7</b><o:p></o:p></p>
<p class="p5"><b>Felix Flentge</b><o:p></o:p></p>
<p class="p3">DTPC<o:p></o:p></p>
<p class="p4">• How to separate the various parts out of that<o:p></o:p></p>
<p class="p4">• Custody signaling in BPv7<o:p></o:p></p>
<p class="p6">• Stuff not covered in BIBE-CT -- want to use CT for multi-hop custody.<o:p></o:p></p>
<p class="p6">• Bundle might take a long time to get to their destination.<o:p></o:p></p>
<p class="p6">• independent custody signaling (based on ACS)<o:p></o:p></p>
<p class="p6">• Interested in a custody transfer mechanism where you don’t need to know/identify the next custodian<o:p></o:p></p>
<p class="p6">• Looking at very high data rate downlink scenarios / less predictable<o:p></o:p></p>
<p class="p2"> <o:p></o:p></p>
<p class="p3">Beau Blanding -- will be doing the writing, helped by Josh and Lee Pitts.<o:p></o:p></p>
<p class="p2"> <o:p></o:p></p>
<p class="p3">Maybe keep w/ BIBE-CT for now in CCSDS and augment with some other extension-block-supported mechanism later in CCSDS and/or IETF.<o:p></o:p></p>
<p class="p2"> <o:p></o:p></p>
<p class="p3">Convergence Layers for v7:<o:p></o:p></p>
<p class="p4">• LTP<o:p></o:p></p>
<p class="p4">• Encapsulation Packets<o:p></o:p></p>
<p class="p4">• Felix: Space packets<o:p></o:p></p>
<p class="p1"><b>Simon Singh</b><o:p></o:p></p>
<p class="p3">Flow management<o:p></o:p></p>
<p class="p4">• Resource allocation / management in intermediate nodes<o:p></o:p></p>
<p class="p4">• Anybody else interested in flow management?<o:p></o:p></p>
<p class="p2"> <o:p></o:p></p>
<p class="p3">Extension blocks (previous hop, bundle age)<o:p></o:p></p>
<p class="p4">• Any node should be able to process these blocks<o:p></o:p></p>
<p class="p4">• Block processing flags<o:p></o:p></p>
<p class="p2"> <o:p></o:p></p>
<p class="p1"><b>Actions:</b><o:p></o:p></p>
<p class="p4">• Look at the Orange thread<o:p></o:p></p>
<p class="p4">• NASA need for custody transfer?<span class="apple-converted-space">
</span>PACE / Gateway<o:p></o:p></p>
<p class="p4">• Felix: write down thoughts on extension-block based custody transfer support<o:p></o:p></p>
<p class="p4">• Keith: figure out about APID assignment for BP over space packets<o:p></o:p></p>
<p class="p4">• Keith: definitive lists of capabilities for LTP and BP updates<o:p></o:p></p>
<p class="p4">• Understand the ‘traffic pared’ bundle expiration reason code<o:p></o:p></p>
<p class="p6">• What’s the purpose / use case?<o:p></o:p></p>
<p class="p6">• How does a node know that it’s neighbor isn’t just going to delete things?<o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:16.0pt"> </span><o:p></o:p></p>
</div>
</body>
</html>