<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><br>
</p>
<p>The DTN flight node developers already have a detailed list of
fault condition triggers and are working with network management
folks to see what might be standardized. We capture selected
state, time, and source EID of the problem bundle(s) and send an
event message. Included is a compression and/or filtering
mechanism for faults that can occur repeatedly so we don't flood.<br>
</p>
<p>These event messages can be acted on by local network management
and are stored to be sent to network management when a link is
available. <br>
</p>
<p>Note this is a common pattern used by embedded flight systems.<br>
</p>
Kind Regards,<br>
<br>
Jonathan<br>
<br>
Jonathan Wilmot<br>
Vantage Systems, Inc<br>
NASA/GSFC 580<br>
<br>
<br>
<div class="moz-cite-prefix">On 5/25/2023 12:56 AM, Vint Cerf via
SIS-DTN wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAHxHggdvoLJZ1TZRDg6_EkazuTLD4tdoE+PVr5NvEocL-MtRHw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">keep in mind that some of the real-time functions
we found useful in the Internet may be less useful in the DTN
because of uncertain and long delays for response - the
resolution of a transient problem may get data too late to be
useful. We might need to think through triggers in the bundle
relay nodes that capture state when a problem arises and sends
to a network management site.
<div><br>
</div>
<div>v</div>
<div><br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, May 25, 2023 at
2:40 AM 구철회 via SIS-DTN <<a
href="mailto:sis-dtn@mailman.ccsds.org"
moz-do-not-send="true" class="moz-txt-link-freetext">sis-dtn@mailman.ccsds.org</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div class="msg-8136323644547880357">
<div lang="KO">
<div class="m_-8540667493610344858WordSection1">
<p><span style="font-size:10pt" lang="EN-US">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"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">Edward.Birrane@jhuapl.edu</a>><br>
To: Felix Flentge <<a
href="mailto:Felix.Flentge@esa.int"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">Felix.Flentge@esa.int</a>>,
"<a href="mailto:sis-dtn@mailman.ccsds.org"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">sis-dtn@mailman.ccsds.org</a>"<br>
<<a
href="mailto:sis-dtn@mailman.ccsds.org"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">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"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">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) <a href="tel:(443)%20778-7423"
value="+14437787423" target="_blank"
moz-do-not-send="true">443-778-7423</a> / (C) <a
href="tel:(443)%20690-8272" value="+14436908272"
target="_blank" moz-do-not-send="true">443-690-8272</a><br>
<br>
<br>
> -----Original Message-----<br>
> From: Felix Flentge <<a
href="mailto:Felix.Flentge@esa.int"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">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"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">Edward.Birrane@jhuapl.edu</a>>;
sis-<br>
> <a href="mailto:dtn@mailman.ccsds.org"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">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"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">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"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">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"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">sis-dtn@mailman.ccsds.org</a><br>
> Subject: [Sis-dtn] IPN URI Scheme Service
Numbers<br>
><br>
> WG,<br>
><br>
> Last week at the SIS-DTN weekly meeting we
had a good discussion on<br>
> allocation strategies for IPN service numbers.<br>
><br>
> IIRC, there were three major areas of
discussion related to these numbers:<br>
> encoding size, allocation policy, and registry
ownership.<br>
><br>
> 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>
> 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>
> 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>
> 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>
> 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) <a href="tel:(443)%20778-7423"
value="+14437787423" target="_blank"
moz-do-not-send="true">443-778-7423</a> / (F) <a
href="tel:(443)%20228-3839" value="+14432283839"
target="_blank" moz-do-not-send="true">443-228-3839</a><br>
><br>
><br>
><br>
> _______________________________________________<br>
> SIS-DTN mailing list<br>
> <a href="mailto:SIS-DTN@mailman.ccsds.org"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">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"
target="_blank" moz-do-not-send="true">
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" target="_blank"
moz-do-not-send="true"
class="moz-txt-link-freetext">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"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">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"
target="_blank" moz-do-not-send="true">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><span
lang="EN-US"></span></p>
</div>
</div>
_______________________________________________<br>
SIS-DTN mailing list<br>
<a href="mailto:SIS-DTN@mailman.ccsds.org" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">SIS-DTN@mailman.ccsds.org</a><br>
<a
href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sis-dtn"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sis-dtn</a><br>
</div>
</blockquote>
</div>
<br clear="all">
<div><br>
</div>
<span class="gmail_signature_prefix">-- </span><br>
<div dir="ltr" class="gmail_signature">
<div dir="ltr">
<div>Please send any postal/overnight deliveries to:</div>
<div>
<div>Vint Cerf</div>
<div>Google, LLC</div>
<div>1900 Reston Metro Plaza, 16th Floor</div>
<div>Reston, VA 20190</div>
<div>+1 (571) 213 1346<br>
</div>
<div><br style="color:rgb(34,34,34)">
</div>
</div>
<div><br>
</div>
<div>until further notice</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
</div>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
SIS-DTN mailing list
<a class="moz-txt-link-abbreviated" href="mailto:SIS-DTN@mailman.ccsds.org">SIS-DTN@mailman.ccsds.org</a>
<a class="moz-txt-link-freetext" href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sis-dtn">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sis-dtn</a>
</pre>
</blockquote>
</body>
</html>