<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:±¼¸²;
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:"\@±¼¸²";
panose-1:2 11 6 0 0 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:±¼¸²;}
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.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:±¼¸²;}
span.EmailStyle19
{mso-style-type:personal-compose;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:3.0cm 72.0pt 72.0pt 72.0pt;}
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="KO" link="blue" vlink="purple">
<div class="WordSection1">
<p><span lang="EN-US" style="font-size:10.0pt">Hi Colleagues,<br>
<br>
What do you think about using this interface for the BP application? First, we need to implement some new options in the socket creation of BP at the kernel level. For example:<br>
<br>
sockfd = socket(AF_INET, SOCK_DTNCL_ORDER, 0); as noted we have options for it SOCK_STREAM, SOCK_DGRAM, SOCK_RAW for the terrestrial network<br>
<br>
Note: several options are possible<br>
1) SOCK_DTNCL_ORDER delivers packet data in order, so undetermined delay must be anticipated due to retransmission.<br>
2) SOCK_DTNCL_OOO (out-of-order), delivering packet data out-of-order.<br>
3) SOCK_DTN_DGRAM acts like LTP-Green.<br>
<br>
Then, a BP application can interface freely with its lower data link layer, as is commonly done with TCP/IP.<br>
<br>
These sockets for DTN automatically switch among currently available link layers, such as the terrestrial network, CCSDS Encap, LTP, and so on, so the BP application does not need to consider its downstream communication status.<br>
<br>
<br>
Cheol<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Mon, 11 Mar 2024 09:06:25 -0700<br>
From: <sburleig.sb@gmail.com><br>
To: "'Deaton, Joshua E. \(MSFC-HP27\)[MOSSI2]'"<br>
<joshua.e.deaton@nasa.gov>, "'Mayer, Jeremy P. \(JSC-OT/ESA\)[EUROPEAN<br>
SPACE AGENCY]'" <jeremy.mayer@dlr.de>, <Felix.Flentge@esa.int>,<br>
<vint@google.com><br>
Cc: <sis-dtn@mailman.ccsds.org><br>
Subject: Re: [Sis-dtn] [EXTERNAL] [BULK] Re: BP Sockets [was RE: IP<br>
networking within DTN-based protocol architectures]<br>
Message-ID: <024a01da73ce$11f8dbb0$35ea9310$@gmail.com><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
It?s not an implementation of BP. It?s an API that all implementations of BP could support and that large numbers of applications ? applications that already communication over sockets ? could use in order to migrate to BP at low cost.<br>
<br>
<br>
<br>
You?re right, though, that it has nothing to do with the question of creating a group to handle IP over BP, which I doubt is a good idea. (ION has included an implementation of this capability for several years, but nobody seems to be enthusiastic about using
it.) I think offering an easy way for existing IP applications to utilize BP (rather than tunneling applications? current IP traffic over BP) is a better idea.<br>
<br>
<br>
<br>
Scott<br>
<br>
<br>
<br>
From: Deaton, Joshua E. (MSFC-HP27)[MOSSI2] <joshua.e.deaton@nasa.gov><br>
Sent: Monday, March 11, 2024 8:54 AM<br>
To: sburleig.sb@gmail.com; Mayer, Jeremy P. (JSC-OT/ESA)[EUROPEAN SPACE AGENCY] <jeremy.mayer@dlr.de>; Felix.Flentge@esa.int; vint@google.com<br>
Cc: sis-dtn@mailman.ccsds.org<br>
Subject: RE: [EXTERNAL] [BULK] Re: [Sis-dtn] BP Sockets [was RE: IP networking within DTN-based protocol architectures]<br>
<br>
<br>
<br>
While this does look interesting and would definitely have merit in existing I?m not sure what standardization would be needed. This really just looks like another implementation at this point. Also, I?m not sure how this relates to the original question of
creating a group for how to handle IP over BP. In that regard I do think a new group would be good as we?ve stated several times that we think it is outside the scope of the SIS-DTN group. I do think there needs to be discussion on what exactly we mean by
IP over BP, whether we are going to simply encapsulate an IP packet vs removing the payload from the IP packet a.k.a terminating the transport layer at the bundle creation point.<br>
<br>
<br>
<br>
Sincerely,<br>
<br>
Joshua Deaton<br>
<br>
<br>
<br>
From: sburleig.sb@gmail.com <<a href="mailto:sburleig.sb@gmail.com">mailto:sburleig.sb@gmail.com</a>> <sburleig.sb@gmail.com <<a href="mailto:sburleig.sb@gmail.com">mailto:sburleig.sb@gmail.com</a>> ><br>
Sent: Monday, March 11, 2024 10:34 AM<br>
To: Deaton, Joshua E. (MSFC-HP27)[MOSSI2] <joshua.e.deaton@nasa.gov <<a href="mailto:joshua.e.deaton@nasa.gov">mailto:joshua.e.deaton@nasa.gov</a>> >; Mayer, Jeremy P. (JSC-OT/ESA)[EUROPEAN SPACE AGENCY] <jeremy.mayer@dlr.de <<a href="mailto:jeremy.mayer@dlr.de">mailto:jeremy.mayer@dlr.de</a>>
>; Felix.Flentge@esa.int <<a href="mailto:Felix.Flentge@esa.int">mailto:Felix.Flentge@esa.int</a>> ; vint@google.com <<a href="mailto:vint@google.com">mailto:vint@google.com</a>><br>
Cc: sis-dtn@mailman.ccsds.org <<a href="mailto:sis-dtn@mailman.ccsds.org">mailto:sis-dtn@mailman.ccsds.org</a>><br>
Subject: RE: [EXTERNAL] [BULK] Re: [Sis-dtn] BP Sockets [was RE: IP networking within DTN-based protocol architectures]<br>
<br>
<br>
<br>
<br>
CAUTION: This email originated from outside of NASA. Please take care when clicking links or opening attachments. Use the "Report Message" button to report suspicious messages to the NASA SOC.<br>
<br>
<br>
<br>
The way I conceive it is something like this:<br>
<br>
<br>
<br>
int bpFd;<br>
<br>
const void *serializedAdu;<br>
<br>
size_t aduLen;<br>
<br>
int flags;<br>
<br>
const struct sockaddr *destEid;<br>
<br>
socklen_t eidLen;<br>
<br>
<br>
<br>
bpFd = socket(AF_BP, SOCK_RAW, 0);<br>
<br>
<br>
<br>
/* Maybe some sockopt() calls. */<br>
<br>
<br>
<br>
/* Set destEid, eidLen, maybe flags. */<br>
<br>
<br>
<br>
if (sendto(bpFd, serializedAdu, aduLen, flags, destEid, eidLen) < 0)<br>
<br>
{<br>
<br>
perror(?Failed to send application data.?);<br>
<br>
}<br>
<br>
<br>
<br>
The implementation and configuration of BP in the sockets code would determine the means by which the data would be transferred. That implementation could be any BP implementation, configured in the same general way that we configure BPAs now, so it would
have a convergence layer interface that might invoke TCP or UDP or (directly) IP or LTP or CCSDS encapsulation packets protocol. No need to displace anything, no need even to forego the use of TCP (under BP) for bundle transmission.<br>
<br>
<br>
<br>
Scott<br>
<br>
<br>
<br>
From: Deaton, Joshua E. (MSFC-HP27)[MOSSI2] <joshua.e.deaton@nasa.gov <<a href="mailto:joshua.e.deaton@nasa.gov">mailto:joshua.e.deaton@nasa.gov</a>> ><br>
Sent: Monday, March 11, 2024 7:40 AM<br>
To: sburleig.sb@gmail.com <<a href="mailto:sburleig.sb@gmail.com">mailto:sburleig.sb@gmail.com</a>> ; Mayer, Jeremy P. (JSC-OT/ESA)[EUROPEAN SPACE AGENCY] <jeremy.mayer@dlr.de <<a href="mailto:jeremy.mayer@dlr.de">mailto:jeremy.mayer@dlr.de</a>> >; Felix.Flentge@esa.int
<<a href="mailto:Felix.Flentge@esa.int">mailto:Felix.Flentge@esa.int</a>> ; vint@google.com <<a href="mailto:vint@google.com">mailto:vint@google.com</a>><br>
Cc: sis-dtn@mailman.ccsds.org <<a href="mailto:sis-dtn@mailman.ccsds.org">mailto:sis-dtn@mailman.ccsds.org</a>><br>
Subject: RE: [EXTERNAL] [BULK] Re: [Sis-dtn] BP Sockets [was RE: IP networking within DTN-based protocol architectures]<br>
<br>
<br>
<br>
Just to make sure I am following correctly; the current suggestion is to create a POSIX (BSD) Socket Specification for BP where we are putting BP directly on top of IP without TCP/UDP or are we trying to fully displace IP all the way down and so BP replaces
IP at layer 3.<br>
<br>
<br>
<br>
Sincerely,<br>
<br>
Joshua Deaton<br>
<br>
<br>
<br>
From: SIS-DTN <sis-dtn-bounces@mailman.ccsds.org <<a href="mailto:sis-dtn-bounces@mailman.ccsds.org">mailto:sis-dtn-bounces@mailman.ccsds.org</a>> > On Behalf Of sburleig.sb--- via SIS-DTN<br>
Sent: Monday, March 11, 2024 9:22 AM<br>
To: Mayer, Jeremy P. (JSC-OT/ESA)[EUROPEAN SPACE AGENCY] <jeremy.mayer@dlr.de <<a href="mailto:jeremy.mayer@dlr.de">mailto:jeremy.mayer@dlr.de</a>> >; Felix.Flentge@esa.int <<a href="mailto:Felix.Flentge@esa.int">mailto:Felix.Flentge@esa.int</a>> ; vint@google.com
<<a href="mailto:vint@google.com">mailto:vint@google.com</a>><br>
Cc: sis-dtn@mailman.ccsds.org <<a href="mailto:sis-dtn@mailman.ccsds.org">mailto:sis-dtn@mailman.ccsds.org</a>><br>
Subject: [EXTERNAL] [BULK] Re: [Sis-dtn] BP Sockets [was RE: IP networking within DTN-based protocol architectures]<br>
<br>
<br>
<br>
<br>
CAUTION: This email originated from outside of NASA. Please take care when clicking links or opening attachments. Use the "Report Message" button to report suspicious messages to the NASA SOC.<br>
<br>
<br>
<br>
Right, the service interface in the CCSDS BP specification -- like all service specifications -- is abstract; it defines the properties of a BP API for the purpose of explaining the required behavior of a Bundle Protocol Agent. Any number of existing and future
BP implementations with very different APIs can be wholly conformant to that specification. But a BP sockets specification would enable any application that currently communicates over POSIX (BSD) sockets to use BP instead of UDP without extensive code changes;
the syntax is already in place. That?s the compelling advantage of the idea.<br>
<br>
<br>
<br>
Scott<br>
<br>
<br>
<br>
From: Jeremy.Mayer@dlr.de <<a href="mailto:Jeremy.Mayer@dlr.de">mailto:Jeremy.Mayer@dlr.de</a>> <Jeremy.Mayer@dlr.de <<a href="mailto:Jeremy.Mayer@dlr.de">mailto:Jeremy.Mayer@dlr.de</a>> ><br>
Sent: Monday, March 11, 2024 3:48 AM<br>
To: Felix.Flentge@esa.int <<a href="mailto:Felix.Flentge@esa.int">mailto:Felix.Flentge@esa.int</a>> ; sburleig.sb@gmail.com <<a href="mailto:sburleig.sb@gmail.com">mailto:sburleig.sb@gmail.com</a>> ; vint@google.com <<a href="mailto:vint@google.com">mailto:vint@google.com</a>><br>
Cc: sis-dtn@mailman.ccsds.org <<a href="mailto:sis-dtn@mailman.ccsds.org">mailto:sis-dtn@mailman.ccsds.org</a>><br>
Subject: RE: BP Sockets [was RE: [Sis-dtn] IP networking within DTN-based protocol architectures]<br>
<br>
<br>
<br>
Hi,<br>
<br>
In the abstract, I?d say so, but (let?s be honest) many developers tend to ignore the abstract notion of the service interface and prefer to have a tangible set of API operations.<br>
<br>
<br>
<br>
Thanks,<br>
<br>
Jeremy<br>
<br>
<br>
<br>
From: Felix Flentge <Felix.Flentge@esa.int <<a href="mailto:Felix.Flentge@esa.int">mailto:Felix.Flentge@esa.int</a>> ><br>
Sent: Montag, 11. M?rz 2024 11:46<br>
To: sburleig.sb@gmail.com <<a href="mailto:sburleig.sb@gmail.com">mailto:sburleig.sb@gmail.com</a>> ; Mayer, Jeremy <Jeremy.Mayer@dlr.de <<a href="mailto:Jeremy.Mayer@dlr.de">mailto:Jeremy.Mayer@dlr.de</a>> >; vint@google.com <<a href="mailto:vint@google.com">mailto:vint@google.com</a>><br>
Cc: sis-dtn@mailman.ccsds.org <<a href="mailto:sis-dtn@mailman.ccsds.org">mailto:sis-dtn@mailman.ccsds.org</a>><br>
Subject: BP Sockets [was RE: [Sis-dtn] IP networking within DTN-based protocol architectures]<br>
<br>
<br>
<br>
Hi,<br>
<br>
<br>
<br>
I like the idea but isn?t this already covered (partially) by the CCSSDS BP service interface, eg:<br>
<br>
<br>
<br>
* Bind ? register EID in passive state<br>
<br>
* Listen ? register EID in active state<br>
<br>
* Connect ? sets a default destination for future send.request<br>
<br>
* Send ? send.request<br>
<br>
* Recv ? poll.request<br>
<br>
<br>
<br>
Regards,<br>
<br>
Felix<br>
<br>
<br>
<br>
From: SIS-DTN <sis-dtn-bounces@mailman.ccsds.org <<a href="mailto:sis-dtn-bounces@mailman.ccsds.org">mailto:sis-dtn-bounces@mailman.ccsds.org</a>> > On Behalf Of sburleig.sb--- via SIS-DTN<br>
Sent: Saturday, March 9, 2024 6:56 PM<br>
To: Jeremy.Mayer@dlr.de <<a href="mailto:Jeremy.Mayer@dlr.de">mailto:Jeremy.Mayer@dlr.de</a>> ; vint@google.com <<a href="mailto:vint@google.com">mailto:vint@google.com</a>><br>
Cc: sis-dtn@mailman.ccsds.org <<a href="mailto:sis-dtn@mailman.ccsds.org">mailto:sis-dtn@mailman.ccsds.org</a>><br>
Subject: Re: [Sis-dtn] IP networking within DTN-based protocol architectures<br>
<br>
<br>
<br>
Thanks for that analysis, Jeremy. We?ve been talking about at least since STINT several years ago, and I really think it?s an idea whose time has come.<br>
<br>
<br>
<br>
Scott<br>
<br>
<br>
<br>
From: Jeremy.Mayer@dlr.de <<a href="mailto:Jeremy.Mayer@dlr.de">mailto:Jeremy.Mayer@dlr.de</a>> <Jeremy.Mayer@dlr.de <<a href="mailto:Jeremy.Mayer@dlr.de">mailto:Jeremy.Mayer@dlr.de</a>> ><br>
Sent: Saturday, March 9, 2024 8:01 AM<br>
To: vint@google.com <<a href="mailto:vint@google.com">mailto:vint@google.com</a>> ; sburleig.sb@gmail.com <<a href="mailto:sburleig.sb@gmail.com">mailto:sburleig.sb@gmail.com</a>><br>
Cc: Tomaso.deCola@dlr.de <<a href="mailto:Tomaso.deCola@dlr.de">mailto:Tomaso.deCola@dlr.de</a>> ; sis-dtn@mailman.ccsds.org <<a href="mailto:sis-dtn@mailman.ccsds.org">mailto:sis-dtn@mailman.ccsds.org</a>><br>
Subject: RE: [Sis-dtn] IP networking within DTN-based protocol architectures<br>
<br>
<br>
<br>
Hi,<br>
<br>
That?s a fair point. Generally, I?d say that BP-POSIX could work with the following:<br>
<br>
* Bind ? works: sets source EID.<br>
<br>
* Listen ? works; sets source EID and opens reception.<br>
<br>
* Connect ? UDP style, sets default destination address.<br>
<br>
* Send ? only valid for connected bundlesocks.<br>
<br>
* Sendto/sendmsg ? works.<br>
<br>
* Recv ? works.<br>
<br>
* Recvfrom/recvmsg ? works, probably should support ?wildcard? EIDs, at least for services.<br>
<br>
* Getaddrinfo and friends ? not required<br>
<br>
* Select ? Works, highly implementation dependent.<br>
<br>
<br>
<br>
BSD sockets really do work for everything!<br>
<br>
<br>
<br>
Thanks,<br>
<br>
Jeremy<br>
<br>
<br>
<br>
<br>
<br>
From: Vint Cerf <vint@google.com <<a href="mailto:vint@google.com">mailto:vint@google.com</a>> ><br>
Sent: Samstag, 9. M?rz 2024 16:51<br>
To: Scott Burleigh <sburleig.sb@gmail.com <<a href="mailto:sburleig.sb@gmail.com">mailto:sburleig.sb@gmail.com</a>> ><br>
Cc: Mayer, Jeremy <Jeremy.Mayer@dlr.de <<a href="mailto:Jeremy.Mayer@dlr.de">mailto:Jeremy.Mayer@dlr.de</a>> >; de Cola, Tomaso <Tomaso.deCola@dlr.de <<a href="mailto:Tomaso.deCola@dlr.de">mailto:Tomaso.deCola@dlr.de</a>> >; Dr. Keith L Scott via SIS-DTN <sis-dtn@mailman.ccsds.org
<<a href="mailto:sis-dtn@mailman.ccsds.org">mailto:sis-dtn@mailman.ccsds.org</a>> ><br>
Subject: Re: [Sis-dtn] IP networking within DTN-based protocol architectures<br>
<br>
<br>
<br>
Yes generally speaking<br>
<br>
<br>
<br>
On Sat, Mar 9, 2024, 10:43 <sburleig.sb@gmail.com <<a href="mailto:sburleig.sb@gmail.com">mailto:sburleig.sb@gmail.com</a>> > wrote:<br>
<br>
I think we get closer to BSD/POSIX if we use UDP as a model. The attenuated UDP notion of connect() would work for BP, I think.<br>
<br>
<br>
<br>
Scott<br>
<br>
<br>
<br>
From: SIS-DTN <sis-dtn-bounces@mailman.ccsds.org <<a href="mailto:sis-dtn-bounces@mailman.ccsds.org">mailto:sis-dtn-bounces@mailman.ccsds.org</a>> > On Behalf Of Jeremy Mayer via SIS-DTN<br>
Sent: Saturday, March 9, 2024 12:35 AM<br>
To: vint@google.com <<a href="mailto:vint@google.com">mailto:vint@google.com</a>> ; Tomaso.deCola@dlr.de <<a href="mailto:Tomaso.deCola@dlr.de">mailto:Tomaso.deCola@dlr.de</a>><br>
Cc: sis-dtn@mailman.ccsds.org <<a href="mailto:sis-dtn@mailman.ccsds.org">mailto:sis-dtn@mailman.ccsds.org</a>><br>
Subject: Re: [Sis-dtn] IP networking within DTN-based protocol architectures<br>
<br>
<br>
<br>
Hi,<br>
<br>
I?m tempted to agree. I?ve seen limited utility in IP->BP encap, as (other than some unidirectional UDP-based applications), the assumptions made in IP networks (especially TCP) do not scale well to DTN environments. The two largest issues I see are:<br>
<br>
A. The assumption that relatively low-latency and bidirectional communication is available.<br>
<br>
B. The layering of stream and message-based semantics.<br>
<br>
<br>
<br>
Almost every TCP-ish application which I?ve seen run over BP winds up with exceptionally low performance, unless some sort of PEP is integrated, which adds complexity, failure points, and fragility.<br>
<br>
<br>
<br>
+1 for the notion of a standard API though, with the additional caveat that we should standardize nomenclature across implementations. We could likely reuse about 80% of the BSD/POSIX interface for BP, with the notable exception of connect.<br>
<br>
<br>
<br>
Thanks,<br>
<br>
Jeremy<br>
<br>
<br>
<br>
From: SIS-DTN <sis-dtn-bounces@mailman.ccsds.org <<a href="mailto:sis-dtn-bounces@mailman.ccsds.org">mailto:sis-dtn-bounces@mailman.ccsds.org</a>> > On Behalf Of Vint Cerf via SIS-DTN<br>
Sent: Freitag, 8. M?rz 2024 12:31<br>
To: de Cola, Tomaso <Tomaso.deCola@dlr.de <<a href="mailto:Tomaso.deCola@dlr.de">mailto:Tomaso.deCola@dlr.de</a>> ><br>
Cc: sis-dtn@mailman.ccsds.org <<a href="mailto:sis-dtn@mailman.ccsds.org">mailto:sis-dtn@mailman.ccsds.org</a>><br>
Subject: Re: [Sis-dtn] IP networking within DTN-based protocol architectures<br>
<br>
<br>
<br>
The more I think about this, the less I like trying to manage off-Earth IP networks remotely. I think I would much rather see native applications running over BP. In any case we need to develop standard APIs for BP, such as the Sockets interface for Linux/Unix/Posix.<br>
<br>
<br>
<br>
We do need to figure out how IP-based and BP-based applications interwork. What do Domain Names mean in the BP context for example.<br>
<br>
<br>
<br>
v<br>
<br>
<br>
<br>
<br>
<br>
On Fri, Mar 8, 2024 at 4:24?AM Tomaso de Cola via SIS-DTN <sis-dtn@mailman.ccsds.org <<a href="mailto:sis-dtn@mailman.ccsds.org">mailto:sis-dtn@mailman.ccsds.org</a>> > wrote:<br>
<br>
Dear All,<br>
<br>
<br>
<br>
as mentioned yesterday during our DTN weekly, during the past Fall meeting a presentation was given by University of Nanjing with the support of Chinese agency about IP-networking within DTN-based protocol stacks, especially for planetary network segments (i.e.
what is often referred to as IP-islands).<br>
<br>
The link to that presentation is as follows:<br>
<br>
<br>
<br>
https://protect2.fireeye.com/v1/url?k=92a850c8-cd333ac0-92ad2146-ac1f6bdccbcc-94c996e347a14f37&q=1&e=2732b66a-980f-4357-8ddd-69084e386830&u=https%3A%2F%2Fcwe.ccsds.org%2Fsis%2Fdocs%2FSIS-DTN%2FMeeting%2520Materials%2F2023%2FFall%25202023%2520SIS-DTN%2FPossible%2520BOF%2520Discussion.pptx%3Fd%3Dw44d31f0b3be649e4bf24ec4ae50479a1<br>
<br>
<br>
<br>
The proposal made there was for a BOF (i.e. towards a WG formation), which I see however too premature. On the contrary, I?d be more in favour for a SIG (Special Interest Group), happening outside the DTN WG.<br>
<br>
<br>
<br>
As discussed yesterday, key points to clarify/agree are:<br>
<br>
<br>
<br>
1. Is the proposal sound and meaningful to be addressed?<br>
<br>
2. Is appropriate for the SIS area or should be better addressed at architectural level in SEA (maybe it can be even a cross-area initiative)?<br>
<br>
3. In the case of SIS, is there significant support to start this? In other words, which agencies have interest in contributing to this activity?<br>
<br>
<br>
<br>
Thank you for sharing comments/objections/suggestions.<br>
<br>
<br>
<br>
Have a nice weekend,<br>
<br>
<br>
<br>
Tomaso<br>
<br>
<br>
<br>
????????????????????????<br>
<br>
Deutsches Zentrum f?r Luft- und Raumfahrt (DLR)<br>
German Aerospace Center<br>
Institute of Communications and Navigation | Satellite Networks | Oberpfaffenhofen | 82234 Wessling | Germany<br>
<br>
Tomaso de Cola, Ph.D. | Integrated Satellite Systems (INS) Team Leader<br>
Telefon +49 8153 28-2156 <tel:+49%208153%20282156> | Telefax +49 8153 28-2844 <tel:+49%208153%20282844> | <<a href="mailto:sandro.scalise@dlr.de">mailto:sandro.scalise@dlr.de</a>> tomaso.decola@dlr.de<br>
<<a href="https://protect2.fireeye.com/v1/url?k=bcd1784b-e34a1243-bcd409c5-ac1f6bdccbcc-f7e03b1d0820c4d9&q=1&e=2732b66a-980f-4357-8ddd-69084e386830&u=http%3A%2F%2Fwww.dlr.de%2Fkn%2Finstitut%2Fabteilungen%2Fsan">https://protect2.fireeye.com/v1/url?k=bcd1784b-e34a1243-bcd409c5-ac1f6bdccbcc-f7e03b1d0820c4d9&q=1&e=2732b66a-980f-4357-8ddd-69084e386830&u=http%3A%2F%2Fwww.dlr.de%2Fkn%2Finstitut%2Fabteilungen%2Fsan</a>>
<a href="https://protect2.fireeye.com/v1/url?k=8920b7bd-d6bbddb5-8925c633-ac1f6bdccbcc-e7bfe930d82e1158&q=1&e=2732b66a-980f-4357-8ddd-69084e386830&u=http%3A%2F%2Fwww.dlr.de%2Fkn%2Finstitut%2Fabteilungen%2Fsan">
https://protect2.fireeye.com/v1/url?k=8920b7bd-d6bbddb5-8925c633-ac1f6bdccbcc-e7bfe930d82e1158&q=1&e=2732b66a-980f-4357-8ddd-69084e386830&u=http%3A%2F%2Fwww.dlr.de%2Fkn%2Finstitut%2Fabteilungen%2Fsan</a><br>
<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
SIS-DTN mailing list<br>
SIS-DTN@mailman.ccsds.org <<a href="mailto:SIS-DTN@mailman.ccsds.org">mailto:SIS-DTN@mailman.ccsds.org</a>><br>
<a href="https://protect2.fireeye.com/v1/url?k=ad4dc160-f2d6ab68-ad48b0ee-ac1f6bdccbcc-b71b67d7eba20916&q=1&e=2732b66a-980f-4357-8ddd-69084e386830&u=https%3A%2F%2Fmailman.ccsds.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fsis-dtn">https://protect2.fireeye.com/v1/url?k=ad4dc160-f2d6ab68-ad48b0ee-ac1f6bdccbcc-b71b67d7eba20916&q=1&e=2732b66a-980f-4357-8ddd-69084e386830&u=https%3A%2F%2Fmailman.ccsds.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fsis-dtn</a><br>
<br>
<br>
<br>
<br>
<br>
<br>
--<br>
<br>
Please send any postal/overnight deliveries to:<br>
<br>
Vint Cerf<br>
<br>
Google, LLC<br>
<br>
1900 Reston Metro Plaza, 16th Floor<br>
<br>
Reston, VA 20190<br>
<br>
+1 (571) 213 1346<br>
<br>
<br>
<br>
<br>
<br>
until further notice<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
This message is intended only for the recipient(s) named above. It may contain proprietary information and/or protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received this e-mail in error, please notify
the sender immediately. ESA applies appropriate organisational measures to protect personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo@esa.int <<a href="mailto:dpo@esa.int">mailto:dpo@esa.int</a>> ).<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://protect2.fireeye.com/v1/url?k=74d1a530-2b4acf38-74d4d4be-ac1f6bdccbcc-04a8a296a14f1710&q=1&e=2732b66a-980f-4357-8ddd-69084e386830&u=http%3A%2F%2Fmailman.ccsds.org%2Fpipermail%2Fsis-dtn%2Fattachments%2F20240311%2Fca5e5e22%2Fattachment.htm">https://protect2.fireeye.com/v1/url?k=74d1a530-2b4acf38-74d4d4be-ac1f6bdccbcc-04a8a296a14f1710&q=1&e=2732b66a-980f-4357-8ddd-69084e386830&u=http%3A%2F%2Fmailman.ccsds.org%2Fpipermail%2Fsis-dtn%2Fattachments%2F20240311%2Fca5e5e22%2Fattachment.htm</a>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
SIS-DTN mailing list<br>
SIS-DTN@mailman.ccsds.org<br>
<a href="https://protect2.fireeye.com/v1/url?k=33488b0e-6cd3e106-334dfa80-ac1f6bdccbcc-49c3466d6f17aee2&q=1&e=2732b66a-980f-4357-8ddd-69084e386830&u=https%3A%2F%2Fmailman.ccsds.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fsis-dtn">https://protect2.fireeye.com/v1/url?k=33488b0e-6cd3e106-334dfa80-ac1f6bdccbcc-49c3466d6f17aee2&q=1&e=2732b66a-980f-4357-8ddd-69084e386830&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 153, Issue 22<br>
****************************************</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
</body>
</html>