<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8">
<style>
div.plaintext { white-space: normal; }
body { font-family: sans-serif; }
div.plaintext h1 { font-size: 1.4em; }
div.plaintext h2 { font-size: 1.2em; }
div.plaintext h3 { font-size: 1.1em; }
blockquote.embedded,div.plaintext blockquote { margin: 0 0 5px; padding-left: 5px; border-left: 2px solid #777777; color: #777777; }
blockquote.embedded blockquote.embedded,div.plaintext blockquote blockquote { border-left-color: #999999; color: #999999; }
blockquote.embedded blockquote.embedded blockquote.embedded,div.plaintext blockquote blockquote blockquote { border-left-color: #BBBBBB; color: #BBBBBB; }
div.plaintext a { color: #3983C4 }
blockquote.embedded,div.plaintext blockquote a { color: #777777; }
blockquote.embedded blockquote.embedded,div.plaintext blockquote blockquote a { color: #999999; }
blockquote.embedded blockquote.embedded blockquote.embedded,div.plaintext blockquote blockquote blockquote a { color: #BBBBBB; }
div.plaintext math[display="inline"] > mrow { padding:5px; }
div.plaintext div.footnotes li p { margin: 0.2em 0; }
</style>
</head>
<body>
<div class="plaintext"><p dir="auto">FYI,<br>
The IETF DTN working group current charter has an item about a generic standard registry for service numbers, similar to the IP ports/services registry, where a service ID is identified for a specific service. I started the initial work while dtnrg (<a href="https://www.ietf.org/archive/id/draft-blanchet-dtnrg-bp-application-framework-01.txt">https://www.ietf.org/archive/id/draft-blanchet-dtnrg-bp-application-framework-01.txt</a>). Obviously not the « what this deployed node has currently running which services », but more if I send a bundle to this specific service ID, then the sender is expecting that the receiver application stack will do appropriately. same as port 80 is expected to be http, 443 https.</p>
<p dir="auto">Marc.</p>
<p dir="auto">On 28 Aug 2018, at 8:39, Scott, Keith L. wrote:</p>
</div>
<blockquote class="embedded"><style scoped></style>
<div lang=EN-US link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt'>Greetings,<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'>Peter Shames noted that while there are registries for SANA CBHE Node and Service numbers that will allow us to deconflict node EIDs and have a uniform interpretation of the service numbers, there is nothing that says WHICH services are running at WHICH node, OR anything that associates BP Nodes (in our case identified by CBHE Node IDs) and the services they’re running with ‘Sites’ (using the Service and Site Aperture Registry definition) such as ground stations, spacecraft, etc. This kind of information, while not technically required to make BP work, is part of the administration/operation of the network, and would be expected to change infrequently (and so at least feasible to maintain in a registry).<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'>The desire is for the DTN WG to identify changes / augmentations to the SANA registries to provide the information above. The attached Registry Management Policy deck includes an overview of the Service Site & Aperture structure on slides 21—23.<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'>I propose the following strawman for discussion:<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt'>Change the <span style='color:#4472C4'>Network Services</span> under <span style='color:#00B050'>Site Service Info</span> on slide 22 to be a ‘<span style='color:#C55A11;mso-style-textfill-fill-color:#C55A11;mso-style-textfill-fill-alpha:100.0%'>mayInclude (0..*)</span> – i.e. allow for possibly multiple network services. This would allow sites that have multiple BP routers, which I’ll admit might be unusual but certainly possible.<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt'>Define a <span style='color:#4472C4'>BP_Network_Service </span>element (registry) that is a logical subclass of the <span style='color:#4472C4'>Network_Services</span> listed on slide 22 as:<o:p></o:p></span></p><p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-size:11.0pt;font-family:Symbol'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><b><span style='font-size:11.0pt'>CBHE Node #,</span></b><span style='font-size:11.0pt'> 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-left:1.0in;text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-size:11.0pt;font-family:Symbol'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><b><span style='font-size:11.0pt'>POC</span></b><span style='font-size:11.0pt'>: 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-left:1.0in;text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-size:11.0pt;font-family:Symbol'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><b><span style='font-size:11.0pt'>List of CBHE Service #s</span></b><span style='font-size:11.0pt'>: 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-left:1.0in;text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-size:11.0pt;font-family:Symbol'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><b><span style='font-size:11.0pt'>List of convergence layers and their information</span></b><span style='font-size:11.0pt'>: 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-left:1.5in;text-indent:-.25in;mso-list:l0 level2 lfo1'><![if !supportLists]><span style='font-size:11.0pt;font-family:"Courier New"'><span style='mso-list:Ignore'>o<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-size:11.0pt;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:11.0pt'><o:p></o:p></span></p><p class=MsoListParagraph style='margin-left:1.5in;text-indent:-.25in;mso-list:l0 level2 lfo1'><![if !supportLists]><span style='font-size:11.0pt;font-family:"Courier New"'><span style='mso-list:Ignore'>o<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-size:11.0pt;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:11.0pt'><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'>Somebody should probably also define an <span style='color:#4472C4'>IP_Network_Service</span> element. That may fall to us as well but could pretty much mirror the BP one (but without CL info).<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'>Thoughts on this?<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'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'> v/r,<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><p class=MsoNormal style='line-height:14.0pt;text-autospace:none'><u><span style='font-size:10.0pt;color:black'><o:p><span style='text-decoration:none'> </span></o:p></span></u></p><p class=MsoNormal style='line-height:14.0pt;text-autospace:none'><b><span style='font-size:10.0pt;color:#7F7F7F'>Dr. Keith Scott Office: +1.703.983.6547</span></b><span style='font-size:10.0pt;color:#7F7F7F'><o:p></o:p></span></p><p class=MsoNormal style='line-height:14.0pt;text-autospace:none'><b><span style='font-size:10.0pt;color:#7F7F7F'>Chief Engineer, Communications Network Engineering & Analysis Fax: +1.703.983.7142</span></b><span style='font-size:10.0pt;color:#7F7F7F'><o:p></o:p></span></p><p class=MsoNormal style='line-height:14.0pt;text-autospace:none'><b><span style='font-size:10.0pt;color:#7F7F7F'>Advanced Data Transport Capability Area Lead Email: <a href="mailto:kscott@mitre.org"><span style='color:#7F7F7F'>kscott@mitre.org</span></a></span></b><span style='font-size:10.0pt;color:#7F7F7F'><o:p></o:p></span></p><p class=MsoNormal style='line-height:14.0pt;text-autospace:none'><b><span style='font-size:10.0pt;color:#474747'> </span></b><span style='font-size:10.0pt;color:black'><o:p></o:p></span></p><p class=MsoNormal style='line-height:14.0pt;text-autospace:none'><span style='font-size:10.0pt;color:black'><a href="http://www.mitre.org/"><b><span style='color:blue'>The MITRE Corporation</span></b></a><o:p></o:p></span></p><p class=MsoNormal style='line-height:14.0pt;text-autospace:none'><b><span style='font-size:10.0pt;color:#7F7F7F'>M/S J500</span></b><span style='font-size:10.0pt;color:#7F7F7F'><o:p></o:p></span></p><p class=MsoNormal style='line-height:14.0pt;text-autospace:none'><b><span style='font-size:10.0pt;color:#7F7F7F'>7515 Colshire Drive</span></b><span style='font-size:10.0pt;color:#7F7F7F'><o:p></o:p></span></p><p class=MsoNormal style='line-height:14.0pt;text-autospace:none'><b><span style='font-size:10.0pt;color:#7F7F7F'>McLean, VA 22102</span></b><span style='font-size:10.0pt;color:#7F7F7F'><o:p></o:p></span></p><p class=MsoNormal style='line-height:14.0pt;text-autospace:none'><b><span style='font-size:10.0pt;color:#7F7F7F'> </span></b><span style='font-size:10.0pt;color:#7F7F7F'><o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.0pt;color:#7F7F7F'>MITRE self-signs its own certificates. Information about the MITRE PKI Certificate Chain is available from <a href="https://www.mitre.org/tech/mii/pki/"><span style='color:#7F7F7F'>https://www.mitre.org/tech/mii/pki/</span></a></span></b><span style='font-size:10.0pt;color:#7F7F7F'><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'><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'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p></div></div></blockquote>
<div class="plaintext"><blockquote>
</blockquote><blockquote><p dir="auto">_______________________________________________<br>
SSG mailing list<br>
SSG@mailman.ccsds.org<br>
<a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/ssg">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/ssg</a></p>
</blockquote></div>
</body>
</html>