<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=utf-8">
<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;
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.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.EmailStyle20
{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>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">Comments <span style="color:#0070C0">in line<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#0070C0"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#0070C0">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#0070C0">Leigh<o:p></o:p></span></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" style="margin-left:.5in"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">SIS-DTN <sis-dtn-bounces@mailman.ccsds.org> on behalf of "Scott, Keith L." <kscott@mitre.org><br>
<b>Date: </b>Tuesday, August 28, 2018 at 5:42 AM<br>
<b>To: </b>"sis-dtn@mailman.ccsds.org" <sis-dtn@mailman.ccsds.org><br>
<b>Cc: </b>"Shames, Peter M (312B)" <Peter.M.Shames@jpl.nasa.gov>, "Burleigh, Scott C (312B)" <Scott.C.Burleigh@jpl.nasa.gov>, SANA Group <ssg@mailman.ccsds.org><br>
<b>Subject: </b>[Sis-dtn] Proposed registry (and registry changes) to address BP operations in CCSDS.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:1.5in;margin-bottom:.0001pt;text-indent:-.25in;font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span class="apple-converted-space"><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black"> </span></span><b><span style="color:black">CBHE Node #,</span></b><span class="apple-converted-space"><span style="color:black"> </span></span><span style="color:black">the
CBHE Node Number of the BP Node, hyperlinked to the node number allocation range in the CBHE Node Number Registry<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin:0in;margin-bottom:.0001pt"><o:p> </o:p></p>
<p class="MsoListParagraph" style="margin:0in;margin-bottom:.0001pt"><span style="color:#0070C0">Depending on my spacecraft, its architecture, and the presence or absence of DTN-enabled instruments etc., I might have many CHBE node #s, and trying to put them
all in a registry tied to a given spacecraft will be cumbersome, and somewhat akin to trying to register NAT’d IP addresses in someone’s LAN.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin:0in;margin-bottom:.0001pt"><o:p> </o:p></p>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:1.5in;margin-bottom:.0001pt;text-indent:-.25in;font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="color:black">·</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black"> <span class="apple-converted-space"> </span></span><b><span style="color:black">POC</span></b><span style="color:black">: a link to the appropriate
SANA registry entry for who to talk to about connecting with this node (e.g. routing through it) [Could be a person or an organization?]<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin:0in;margin-bottom:.0001pt"><o:p> </o:p></p>
<p class="MsoListParagraph" style="margin:0in;margin-bottom:.0001pt"><span style="color:#0070C0">Sorry, you get to connect with my spacecraft by asking the mission ops team, not some higher organization. And I’m not publishing anything in public except that
which is needed to deconflict potential telemetry link layer issues, like spacecraft ID.
</span><o:p></o:p></p>
<p class="MsoListParagraph" style="margin:0in;margin-bottom:.0001pt"><o:p> </o:p></p>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:1.5in;margin-bottom:.0001pt;text-indent:-.25in;font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="color:black">·</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black"> <span class="apple-converted-space"> </span></span><b><span style="color:black">List of CBHE Service #s</span></b><span style="color:black">:
A list of CBHE service numbers that can be expected to be running on the node (e.g. CFDP) – hyperlinked to their corresponding entries in the CBHE Service # registry.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin:0in;margin-bottom:.0001pt"><o:p> </o:p></p>
<p class="MsoListParagraph" style="margin:0in;margin-bottom:.0001pt"><span style="color:#0070C0">Conventions that are akin to the lower range of internet well-known ports are probably a good idea.. at least I see no harm in doing that.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin:0in;margin-bottom:.0001pt"><o:p> </o:p></p>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:1.5in;margin-bottom:.0001pt;text-indent:-.25in;font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="color:black">·</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black"> <span class="apple-converted-space"> </span></span><b><span style="color:black">List of convergence layers and their information</span></b><span style="color:black">:
so for example, if the node is running a TCPCL on IP address 10.1.2.3:1234, a UDP CL on port address 10.1.2.6:5678, and an LTP/Encap CL on virtual channel 3, those would be listed.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin:0in;margin-bottom:.0001pt"><o:p> </o:p></p>
<p class="MsoListParagraph" style="margin:0in;margin-bottom:.0001pt"><span style="color:#0070C0">No, I would push back on this. When I register an IP address, I don’t tell you what services I have running, what ports I happen to be using or anything else –
you may assume that if I am running a web server you might try to hit me on port 80 and so forth, but I don’t have to register that anywhere. CCSDS could specify
<i>what</i> information a mission would need to make available to other missions (in the vein of “if you want to talk to me using DTN, I have CFDP running as this EID, my comm links support X, Y or Z link layer, and if you want to talk to mission ops computers,
use STCP on this network and port”) – but trying to put that information into some sort of international registry is doomed to failure. (For instance, we have to change your example TCPCL info quite often in practice, as terrestrial IP network security dictates
– we have established firewall port and protocol conventions between centers and organizations that are SBU information, and I’m not going to put my project at risk by letting all my DTN BP contact information / EIDs and services be part of some public registry.
For non-NASA folks, SBU is a NASA security classification meaning “Sensitive But Unclassified” and us used to protect agency information that shouldn’t be released to the public, sent over unencrypted channels, etc. The Department of Defense and Department
of Energy use actual classifications like Confidential, Secret, Top Secret – but since NASA isn’t part of the DoD or DoE, they just have SBU which I always take as sort of a military “Confidential” or even “Secret” classification.)<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin:0in;margin-bottom:.0001pt"><span style="color:#0070C0"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="margin:0in;margin-bottom:.0001pt"><span style="color:#0070C0">In any case, I don’t believe we should go overboard in trying to put everything anyone does with DTN in space into some public CCSDS registry – let’s just put in
things that are absolutely necessary to deconflict links.. Remember that BP isn’t a link layer protocol, and RF links don’t need any DTN EID information to establish contact with a spacecraft.</span><o:p></o:p></p>
<p class="MsoListParagraph" style="margin:0in;margin-bottom:.0001pt"><o:p> </o:p></p>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:2.0in;margin-bottom:.0001pt;text-indent:-.25in;font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="font-family:"Courier New";color:black">o</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black"> <span class="apple-converted-space"> </span></span><span style="color:red">Maybe listing the VC isn’t appropriate here?
That’s more a function of the mission configuration (e.g. each mission could use a different VC even if all share the same aperture and site, I think)</span><span style="font-size:12.0pt;color:black"><o:p></o:p></span></p>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:2.0in;margin-bottom:.0001pt;text-indent:-.25in;font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="font-family:"Courier New";color:black">o</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:black"> <span class="apple-converted-space"> </span></span><span style="color:red">I’d vote for the CL info being a free text
field with a convention for entries like TCP:1234:4556 rather than trying to generate a whole sub-structure for CL entries – thoughts?</span><span style="font-size:12.0pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in;font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="color:black"> </span><span style="font-size:12.0pt;color:black"><o:p></o:p></span></p>
</div>
</body>
</html>