<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=ks_c_5601-1987">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Gulim;
panose-1:2 11 6 0 0 1 1 1 1 1;}
@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:"\@Gulim";
panose-1:2 11 6 0 0 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Gulim",serif;
mso-fareast-language:KO;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Gulim",serif;
mso-fareast-language:KO;}
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:12.0pt;
font-family:"Gulim",serif;
mso-fareast-language:KO;}
span.EmailStyle18
{mso-style-type:personal;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:85.05pt 1.0in 1.0in 1.0in;}
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-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Thank you for this list!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Having an idea of proposed standard services is an excellent way to start the discussion of how would we identify/enumerate services.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">_Ed<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Edward J. Birrane, III, Ph.D. (he/him/his)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Chief Engineer, Space Constellation Networking<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Supervisor, Embedded Applications Group
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Space Exploration Sector<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Johns Hopkins Applied Physics Laboratory<br>
(W) 443-778-7423 / (C) 443-690-8272</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<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;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">
</span><span lang="KO" style="font-size:11.0pt">±ΈΓΆΘΈ</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <chkoo@kari.re.kr>
<br>
<b>Sent:</b> Wednesday, May 24, 2023 7:40 PM<br>
<b>To:</b> Birrane, Edward J. <Edward.Birrane@jhuapl.edu><br>
<b>Cc:</b> sis-dtn@mailman.ccsds.org<br>
<b>Subject:</b> [EXT] Re: [Sis-dtn] IPN URI Scheme Service Numbers<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div id="APLWarningText">
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" align="left">
<tbody>
<tr>
<td width="100%" style="width:100.0%;background:#E0E0E0;padding:0in 0in 0in 0in">
<p class="MsoNormal" style="mso-element:frame;mso-element-frame-hspace:1.3pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<b><span style="color:red">APL external email warning: </span></b><span style="color:black">Verify sender
<a href="mailto:chkoo@kari.re.kr">chkoo@kari.re.kr</a> before clicking links or attachments</span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p><span style="font-family:"Times New Roman",serif"> </span><o:p></o:p></p>
</div>
</div>
<p><span style="font-size:10.0pt">Hi, Ed.<br>
<br>
Here is my list for potential DTN services that I think would come someday.<br>
<br>
- BP ping<br>
- BP chat<br>
- CFDP<br>
- Video streaming<br>
- BP traceroute<br>
- BP HTTP<br>
- Network management protocol<br>
<br>
Best,<br>
Cheol<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Tue, 23 May 2023 02:29:11 +0000<br>
From: "Birrane, Edward J." <<a href="mailto:Edward.Birrane@jhuapl.edu">Edward.Birrane@jhuapl.edu</a>><br>
To: Felix Flentge <<a href="mailto:Felix.Flentge@esa.int">Felix.Flentge@esa.int</a>>, "<a href="mailto:sis-dtn@mailman.ccsds.org">sis-dtn@mailman.ccsds.org</a>"<br>
</span><span style="font-size:10.0pt;font-family:"Times New Roman",serif"> </span><span style="font-size:10.0pt"> <<a href="mailto:sis-dtn@mailman.ccsds.org">sis-dtn@mailman.ccsds.org</a>><br>
Subject: Re: [Sis-dtn] IPN URI Scheme Service Numbers<br>
Message-ID: <<a href="mailto:8fbf017ec65a4ebc8f51e51b32955830@jhuapl.edu">8fbf017ec65a4ebc8f51e51b32955830@jhuapl.edu</a>><br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
I would encourage any observations on the need for standard service numbers (and that they are not port numbers) to be also made to the DTNWG mailing list. It would help inform the discussion that is occurring there.<br>
<br>
-Ed<br>
<br>
Edward J. Birrane, III, Ph.D. (he/him/his) Chief Engineer, Space Constellation Networking Supervisor, Embedded Applications Group Space Exploration Sector Johns Hopkins Applied Physics Laboratory<br>
(W) 443-778-7423 / (C) 443-690-8272<br>
<br>
<br>
> -----Original Message-----<br>
> From: Felix Flentge <<a href="mailto:Felix.Flentge@esa.int">Felix.Flentge@esa.int</a>><br>
> Sent: Monday, May 22, 2023 11:50 AM<br>
> To: Birrane, Edward J. <<a href="mailto:Edward.Birrane@jhuapl.edu">Edward.Birrane@jhuapl.edu</a>>; sis-<br>
> <a href="mailto:dtn@mailman.ccsds.org">dtn@mailman.ccsds.org</a><br>
> Subject: [EXT] RE: IPN URI Scheme Service Numbers<br>
><br>
> APL external email warning: Verify sender <a href="mailto:Felix.Flentge@esa.int">
Felix.Flentge@esa.int</a> before<br>
> clicking links or attachments<br>
><br>
> Hi,<br>
><br>
> Seems to be a very sensible proposal to me. For the more immediate future,<br>
> I assume that there will be only limited need for interoperable use of service<br>
> numbers (ie, an application of one agency communicating to an application<br>
> of another agency) and I would expect missions to pick the low service<br>
> numbers for their (private) M&C and payload needs anyway. What we might<br>
> want to agree on are service numbers used for network management and<br>
> diagnostic needs (e.g., bpecho).<br>
><br>
> Regards,<br>
> Felix<br>
><br>
> -----Original Message-----<br>
> From: SIS-DTN <<a href="mailto:sis-dtn-bounces@mailman.ccsds.org">sis-dtn-bounces@mailman.ccsds.org</a>> On Behalf Of Birrane,<br>
> Edward J. via SIS-DTN<br>
> Sent: Monday, May 22, 2023 2:38 PM<br>
> To: <a href="mailto:sis-dtn@mailman.ccsds.org">sis-dtn@mailman.ccsds.org</a><br>
> Subject: [Sis-dtn] IPN URI Scheme Service Numbers<br>
><br>
> WG,<br>
><br>
></span><span style="font-size:10.0pt;font-family:"Times New Roman",serif"> </span><span style="font-size:10.0pt"> Last week at the SIS-DTN weekly meeting we had a good discussion on<br>
> allocation strategies for IPN service numbers.<br>
><br>
></span><span style="font-size:10.0pt;font-family:"Times New Roman",serif"> </span><span style="font-size:10.0pt"> IIRC, there were three major areas of discussion related to these numbers:<br>
> encoding size, allocation policy, and registry ownership.<br>
><br>
></span><span style="font-size:10.0pt;font-family:"Times New Roman",serif"> </span><span style="font-size:10.0pt"> The encoding size discussion noted that the CBOR encoding of service<br>
> numbers creates a very small allocation of 1-byte encodings (0-23), a small<br>
> allocation of 2-byte encodings (24-155), a moderate size allocation of 3-byte<br>
> encodings (256-65,535), and then 4+ byte encodings that give us the<br>
> remainder of the 64bit service number space.<br>
><br>
></span><span style="font-size:10.0pt;font-family:"Times New Roman",serif"> </span><span style="font-size:10.0pt"> The allocation policy discussion noted that there was a good case for<br>
> "private use" service numbers for mission-specific use cases (commanding,<br>
> telemetry) that do not otherwise map to a standardized protocol. These<br>
> mission specific service numbers should not be standardized (they are<br>
> mission specific) and there should be some allowance for them in the small<br>
> encoding space since they will be used by missions often (perhaps most<br>
> often).<br>
><br>
></span><span style="font-size:10.0pt;font-family:"Times New Roman",serif"> </span><span style="font-size:10.0pt"> The registry ownership discussion noted that IANA is creating (updating<br>
> really..) a registry for service numbers and should there be a SANA allocation<br>
> in that registry.<br>
><br>
></span><span style="font-size:10.0pt;font-family:"Times New Roman",serif"> </span><span style="font-size:10.0pt"> At the end of the discussion the following proposal was put forward:<br>
><br>
> 1 byte service numbers (1-23) will be private use .<br>
> 2 byte service numbers (24-255) will be expert review with a 64-id chunk<br>
> allocated to SANA.<br>
> 3 byte service numbers (256-65k) will be cut 1/3 private use, 1/3 IANA<br>
> managed and 1/3 IANA managed but given to SANA.<br>
> 4 byte will have a chunk of experimental.<br>
> 4+bytes is unassigned.<br>
><br>
></span><span style="font-size:10.0pt;font-family:"Times New Roman",serif"> </span><span style="font-size:10.0pt"> This continues to be an area of active discussion in the IETF mailing list.<br>
> Some IETF participants are proposing that all service numbers be private-use<br>
> and there be no standard service numbers since service discovery is better<br>
> done today independent of port numbers. I disagree with this position -<br>
> service numbers are not port numbers - but that case needs to be made, for<br>
> those interested in following the discussion on the IETF mailing list.<br>
><br>
> -Ed<br>
><br>
> ---<br>
> Edward J. Birrane, III, Ph.D. (he/him/his) Chief Engineer, Space Constellation<br>
> Networking Supervisor, Embedded Applications Group Space Exploration<br>
> Sector Johns Hopkins Applied Physics Laboratory<br>
> (W) 443-778-7423 / (F) 443-228-3839<br>
><br>
><br>
><br>
> _______________________________________________<br>
> SIS-DTN mailing list<br>
> <a href="mailto:SIS-DTN@mailman.ccsds.org">SIS-DTN@mailman.ccsds.org</a><br>
> <a href="https://protect2.fireeye.com/v1/url?k=57fc07a6-08676dae-57f97628-ac1f6bdccbcc-48ad6278b81cd32f&q=1&e=b4259b40-80ac-4b4b-a14a-92c3072ae173&u=https%3A%2F%2Fmailman.ccsds.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fsis-dtn">
https://protect2.fireeye.com/v1/url?k=57fc07a6-08676dae-57f97628-ac1f6bdccbcc-48ad6278b81cd32f&q=1&e=b4259b40-80ac-4b4b-a14a-92c3072ae173&u=https%3A%2F%2Fmailman.ccsds.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fsis-dtn</a><br>
> This message is intended only for the recipient(s) named above. It may<br>
> contain proprietary information and/or protected content. Any<br>
> unauthorised disclosure, use, retention or dissemination is prohibited. If you<br>
> have received this e-mail in error, please notify the sender immediately. ESA<br>
> applies appropriate organisational measures to protect personal data, in case<br>
> of data privacy queries, please contact the ESA Data Protection Officer<br>
> (<a href="mailto:dpo@esa.int">dpo@esa.int</a>).<br>
<br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
SIS-DTN mailing list<br>
<a href="mailto:SIS-DTN@mailman.ccsds.org">SIS-DTN@mailman.ccsds.org</a><br>
<a href="https://protect2.fireeye.com/v1/url?k=c23fcc3f-9da4a637-c23abdb1-ac1f6bdccbcc-506e8a5c82861025&q=1&e=b4259b40-80ac-4b4b-a14a-92c3072ae173&u=https%3A%2F%2Fmailman.ccsds.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fsis-dtn">https://protect2.fireeye.com/v1/url?k=c23fcc3f-9da4a637-c23abdb1-ac1f6bdccbcc-506e8a5c82861025&q=1&e=b4259b40-80ac-4b4b-a14a-92c3072ae173&u=https%3A%2F%2Fmailman.ccsds.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fsis-dtn</a><br>
<br>
<br>
------------------------------<br>
<br>
End of SIS-DTN Digest, Vol 143, Issue 37<br>
****************************************</span><o:p></o:p></p>
</div>
</div>
</body>
</html>