<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=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;}
@font-face
{font-family:Aptos;
panose-1:2 11 0 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Aptos",sans-serif;
mso-ligatures:standardcontextual;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#467886;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
font-size:11.0pt;
font-family:"Aptos",sans-serif;
mso-ligatures:standardcontextual;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Aptos",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1576740472;
mso-list-type:hybrid;
mso-list-template-ids:-423092512 67567633 67567641 67567643 67567631 67567641 67567643 67567631 67567641 67567643;}
@list l0:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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="#467886" vlink="#96607D" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Hi Felix –<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I am very happy to see these charts – I have been asking the DTN Program to agree on some standard scenarios for a number of years and it just hasn’t gotten done – so these scenarios will be a great baseline!
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I am getting data on the projected links from the Mars program office. On the trunk lines there will be different uplink and downlink rates, and the rates are dependent on A. distance to Mars, and B. elevation of the DSN antennas in the
case of RF links. Also links P-* use adaptive data rate control, and are on UHF at present – there are S-band radios in development for proximity links at the moon, but I’m not 100% sure if S-band is planned for rovers/landers at Mars etc.. Will find out!.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Finally, they are also planning crosslinks between orbiters. I will provide more data on that when I find out.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">A comment about 3GPP/WIFI on the surface of the moon – we did a lot of testing of DTN over TCP/IP (with IP neighbor discovery and Nak-Oriented Multicast) for DARPA a few years back, tested the system in the field at a USMC base with mobile
ground units for weeks, and proved that DTN works great in terrestrial WIfi network scenarios, as long as your Wifi is up – and when it’s not or it’s intermittent, DTN store and forward fixed that, so in all test scenarios (multicast, unicast with different
ground relay configurations as one would find in combat situations, etc.) DTN always saved the day. DTN end-to-end on lunar surface ops will fix intermittent IP links if they use DTN as it was designed, which is end-to-end. If they decide to drop bundles into
a non-DTN lunar surface network and go with the so-called “islands-of-IP” concept, well I hope they like what they end up with.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">(GRC never wanted to do DTN in their spacesuits (for this reason and that reason, going back to the Constellation days even), but I’m sure they’ll figure out something to help with astronaut to earth comm reliability eventually.. In any
case, DTN (BBN’s implementation by the way) over 802.11 networks with and without multicast and IPND was tested rigorously for the 5 years of the DARPA DTN program, so I agree that the surface DTN/IP cases won’t impact any near-term CCSDS standards work.)<o:p></o:p></p>
<p class="MsoNormal"><o:p></o:p></p>
<p class="MsoNormal">Thanks<o:p></o:p></p>
<p class="MsoNormal">Leigh<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></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"><b><span lang="EN-GB" style="font-size:12.0pt;font-family:"Calibri",sans-serif;color:black;mso-ligatures:none">From:
</span></b><span lang="EN-GB" style="font-size:12.0pt;font-family:"Calibri",sans-serif;color:black;mso-ligatures:none">SIS-DTN <sis-dtn-bounces@mailman.ccsds.org> on behalf of Felix Flentge via SIS-DTN <sis-dtn@mailman.ccsds.org><br>
<b>Reply-To: </b>Felix Flentge <Felix.Flentge@esa.int><br>
<b>Date: </b>Wednesday, June 12, 2024 at 7:14 AM<br>
<b>To: </b>"Booth, Stephanie L. (GRC-LCN0)" <stephanie.l.booth@nasa.gov>, "Tomaso.deCola@dlr.de" <Tomaso.deCola@dlr.de><br>
<b>Cc: </b>"sis-dtn@mailman.ccsds.org" <sis-dtn@mailman.ccsds.org><br>
<b>Subject: </b>Re: [Sis-dtn] [EXTERNAL] [BULK] Re: DTN Reference Scenarios<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:12.0pt;mso-ligatures:none"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-GB">Thanks Stephanie,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">we have considered adding IP networks (surface or spacecraft + visiting vehicles) into the reference scenario but decided to not include those for the time being. They were considered less relevant for the scenario as
we wanted to focus on BP. Additional BP nodes which are reachable via IP CLA are a bit less interesting as they are already present in the terrestrial networks and are always connected (more or less).<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">However, the question of mixed IP / BP network is extremely relevant for Lunar scenarios (although currently not too much in the focus of CCSDS). I am wondering whether we could take the presented Lunar Reference Scenario
as a base scenario and define an extension for your purpose (adding some IP networks). If something within the base (BP) lunar scenario is not adequate for this I believe it could be added. Would that work for you?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">(And I would hope that someone with more knowledge about the expected IP networks would volunteer to make a proposal for that extension.)<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">I think this may be a general approach: we try to define some base scenarios which can then be extended for certain questions (e.g., I could imagine that somebody could add different traffic generation patterns for QoS
work, or use different error rates for other link types, ...). <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="mso-ligatures:none">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-ligatures:none">Felix<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-left:.5in"><b><span style="font-family:"Calibri",sans-serif;mso-ligatures:none">From:</span></b><span style="font-family:"Calibri",sans-serif;mso-ligatures:none"> Booth, Stephanie L. (GRC-LCN0) <stephanie.l.booth@nasa.gov>
<br>
<b>Sent:</b> Tuesday, June 11, 2024 6:09 PM<br>
<b>To:</b> Felix Flentge <Felix.Flentge@esa.int>; Tomaso.deCola@dlr.de<br>
<b>Cc:</b> sis-dtn@mailman.ccsds.org<br>
<b>Subject:</b> RE: [EXTERNAL] [BULK] Re: [Sis-dtn] DTN Reference Scenarios<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" style="margin-left:.5in"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Calibri",sans-serif">I am going to chime in on Felix’s second comment below on behalf of Rachel Dudukovich and mine’s conversation about the ppt.
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Calibri",sans-serif">It would be good to include more 3GPP/WiFi nodes but in addition, build up a scenario with different sub-networks that are both DTN and non-DTN. That’s one of the things
DTN is supposed to help handle. By doing this there would be a lot of things to work out for the ground DTN gateways and such. For example, there would be different classes of nodes (gateway, edge nodes, etc). If you can create a picture encompassing it all
that would be great! Especially for network management and routing since we need to clearly show where the various decision-making elements take place.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Calibri",sans-serif">Stephanie Booth<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-left:.5in"><b><span style="font-family:"Calibri",sans-serif;mso-ligatures:none">From:</span></b><span style="font-family:"Calibri",sans-serif;mso-ligatures:none"> SIS-DTN <<a href="mailto:sis-dtn-bounces@mailman.ccsds.org">sis-dtn-bounces@mailman.ccsds.org</a>>
<b>On Behalf Of </b>Felix Flentge via SIS-DTN<br>
<b>Sent:</b> Friday, June 7, 2024 4:13 AM<br>
<b>To:</b> <a href="mailto:Tomaso.deCola@dlr.de">Tomaso.deCola@dlr.de</a><br>
<b>Cc:</b> <a href="mailto:sis-dtn@mailman.ccsds.org">sis-dtn@mailman.ccsds.org</a><br>
<b>Subject:</b> [EXTERNAL] [BULK] Re: [Sis-dtn] DTN Reference Scenarios<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
<table class="MsoNormalTable" border="1" cellspacing="0" cellpadding="0" align="left" width="100%" style="width:100.0%;border:solid black 1.5pt">
<tbody>
<tr>
<td width="100%" style="width:100.0%;border:none;background:#FFEB9C;padding:3.75pt 3.75pt 3.75pt 3.75pt">
<p class="MsoNormal" style="mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<b><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black;mso-ligatures:none">CAUTION:</span></b><span style="font-family:"Calibri",sans-serif;color:black;mso-ligatures:none">
</span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black;mso-ligatures:none">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.</span><span style="font-family:"Calibri",sans-serif;color:black;mso-ligatures:none">
</span><span style="font-family:"Calibri",sans-serif;mso-ligatures:none"><o:p></o:p></span></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
<span lang="EN-GB" style="font-family:"Calibri",sans-serif;mso-ligatures:none"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span lang="EN-GB">Hi Tomaso,<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span lang="EN-GB">Please see my replies below.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span lang="EN-GB"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span lang="EN-GB" style="mso-ligatures:none">Regards,<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span lang="EN-GB" style="mso-ligatures:none">Felix<o:p></o:p></span></p>
</div>
<p class="MsoNormal" style="margin-left:.5in"><span lang="EN-GB"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-left:1.0in"><b><span style="font-family:"Calibri",sans-serif;mso-ligatures:none">From:</span></b><span style="font-family:"Calibri",sans-serif;mso-ligatures:none">
<a href="mailto:Tomaso.deCola@dlr.de">Tomaso.deCola@dlr.de</a> <<a href="mailto:Tomaso.deCola@dlr.de">Tomaso.deCola@dlr.de</a>>
<br>
<b>Sent:</b> Friday, June 7, 2024 9:44 AM<br>
<b>To:</b> Felix Flentge <<a href="mailto:Felix.Flentge@esa.int">Felix.Flentge@esa.int</a>><br>
<b>Cc:</b> <a href="mailto:sis-dtn@mailman.ccsds.org">sis-dtn@mailman.ccsds.org</a>;
<a href="mailto:Edward.Birrane@jhuapl.edu">Edward.Birrane@jhuapl.edu</a><br>
<b>Subject:</b> AW: DTN Reference Scenarios<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" style="margin-left:1.0in"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span lang="DE" style="font-family:"Calibri",sans-serif">Hi Felix,<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span lang="DE" style="font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-family:"Calibri",sans-serif">thank you for sharing the slides presented yesterday.
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-family:"Calibri",sans-serif">Just three comments:<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="margin-left:1.5in;text-indent:-.25in;mso-list:l0 level1 lfo2">
<![if !supportLists]><span style="font-family:"Calibri",sans-serif"><span style="mso-list:Ignore">1)<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-family:"Calibri",sans-serif">I see no mention of optical communications, while the lunar WG within IOAG was pointing to them too. Any reason for excluding them now from the picture?<br>
<br>
FF: At least Moonlight does not include optical trunk link (, yet) and the scenario seems complex enough for the time being.
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
<p class="MsoListParagraph" style="margin-left:1.5in;text-indent:-.25in;mso-list:l0 level1 lfo2">
<![if !supportLists]><span style="font-family:"Calibri",sans-serif"><span style="mso-list:Ignore">2)<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-family:"Calibri",sans-serif">The SOIS-WIR WG has been working on green and blue books about the communication solutions for in-situ planetary network, possibly resulting in the coexistence of 3GPP/WiFi solutions
with DTN-based ones. Is this also captured in the pictures you have put in your slides?<br>
<br>
FF: No, we have considered adding more nodes on surfaces but I think it does not considerably change the scenario (again, seems already complex enough). It would certainly be exciting to consider surface IP networks as well but I would keep this for later.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
<p class="MsoListParagraph" style="margin-left:1.5in;text-indent:-.25in;mso-list:l0 level1 lfo2">
<![if !supportLists]><span style="font-family:"Calibri",sans-serif"><span style="mso-list:Ignore">3)<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-family:"Calibri",sans-serif">As to where push information about all (and possibly other) DTN reference scenarios, let’s not forget that we have the CCSDS 734.0-G-1 “Rationale, Scenarios, and Requirements for
DTN in Space” which is since long (the document was published already in 2010) in our ToDo list for the 5-year review. Probably the material you provided in the slides could be further elaborated and expanded for a new version of that green book. In any case
it is probably now time to think how and when to start the 5-year review of that book (I know all our resources are on the blue and orange books, but that green book is really old and must be refreshed)<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:1.5in">FF: Yes, I could imagine the scenarios ending up in the green book but I would like to finish the first version asap. Maybe we can have them yellow (‘yellow is the new green’) first just to have something to reference
to.<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.25in"><span style="font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-family:"Calibri",sans-serif">Just another point somehow correlated to scenarios: during the monthly telco between SIS and IETF DTN WG, it emerged that IETF would like to come up with a concept/white
paper about the challenges of space internetworking. Moreover, a first step would be to review and update RFC4838 which now contains some outdated content that should be revised. I add here Ed who can say a few words more on this point.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:.5in;text-indent:.5in">FF: Indeed, I think that these scenarios are also relevant in this context as they may help to add some more realism to the general discussions. However, we should stress that the intention is more
short-term and still very agency-centric so this should not limit work on scalable solutions for large networks.<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-family:"Calibri",sans-serif">Regards,<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-family:"Calibri",sans-serif">Tomaso<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-left:1.0in"><b><span lang="DE" style="font-family:"Calibri",sans-serif;mso-ligatures:none;mso-fareast-language:DE">Von:</span></b><span lang="DE" style="font-family:"Calibri",sans-serif;mso-ligatures:none;mso-fareast-language:DE">
SIS-DTN <<a href="mailto:sis-dtn-bounces@mailman.ccsds.org">sis-dtn-bounces@mailman.ccsds.org</a>>
<b>Im Auftrag von </b>Felix Flentge via SIS-DTN<br>
<b>Gesendet:</b> Donnerstag, 6. Juni 2024 17:57<br>
<b>An:</b> Dr. Keith L Scott via SIS-DTN <<a href="mailto:sis-dtn@mailman.ccsds.org">sis-dtn@mailman.ccsds.org</a>><br>
<b>Betreff:</b> [Sis-dtn] DTN Reference Scenarios<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" style="margin-left:1.0in"><span lang="DE"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span lang="EN-GB">Dear All,<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span lang="EN-GB">I have uploaded today’s presentation on DTN Reference Scenarios to CWE:<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span lang="EN-GB"><a href="https://urldefense.us/v3/__https:/cwe.ccsds.org/sis/docs/SIS-DTN/Other*20Documents/DTN*20Reference*20Scenario/CCSDS*20DTN*20Scenarios.pptx?d=wf3b24c8d83344cf998bc7846fe279269__;JSUlJSU!!PvBDto6Hs4WbVuu7!IWzuZP6K6VNS-GM3zYF4f_Vq2KPbGbcKpV9frpbG5S59NWyqvdGIcvIQ8LwdyR34QgLsAU-zavlduSE05LGyTzp0XuU$">https://cwe.ccsds.org/sis/docs/SIS-DTN/Other%20Documents/DTN%20Reference%20Scenario/CCSDS%20DTN%20Scenarios.pptx?d=wf3b24c8d83344cf998bc7846fe279269</a><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span lang="EN-GB">Please let us know if you have any feedback (in particular, on the overall topologies – we need to fix them now for the next steps).<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span lang="EN-GB" style="mso-ligatures:none">Regards,<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span lang="EN-GB" style="mso-ligatures:none">Felix<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span lang="EN-GB" style="font-family:"Calibri",sans-serif;mso-ligatures:none;mso-fareast-language:DE">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 (<a href="mailto:dpo@esa.int">dpo@esa.int</a>).
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span lang="EN-GB" style="font-family:"Calibri",sans-serif;mso-ligatures:none">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 (<a href="mailto:dpo@esa.int">dpo@esa.int</a>).
<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:12.0pt;mso-ligatures:none">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). <o:p></o:p></span></p>
</div>
</body>
</html>