<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=us-ascii">
<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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Aptos",sans-serif;
mso-ligatures:standardcontextual;
mso-fareast-language:EN-US;}
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:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
font-size:11.0pt;
font-family:"Aptos",sans-serif;
mso-ligatures:standardcontextual;
mso-fareast-language:EN-US;}
span.EmailStyle22
{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:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
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:-18.0pt;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@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:-18.0pt;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@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:-18.0pt;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@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:0cm;}
ul
{margin-bottom:0cm;}
--></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-GB" link="#467886" vlink="#96607D" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Hi Tomaso,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I have been thinking yellow as the scenarios might support interoperability testing (and because I would have though that it is quick).<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Anyway, I think what is more important is to finalise the scenarios and find a way to make them publicly available.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="mso-ligatures:none;mso-fareast-language:EN-GB">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-ligatures:none;mso-fareast-language:EN-GB">Felix<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" style="margin-left:36.0pt"><b><span lang="EN-US" style="font-family:"Calibri",sans-serif;mso-ligatures:none;mso-fareast-language:EN-GB">From:</span></b><span lang="EN-US" style="font-family:"Calibri",sans-serif;mso-ligatures:none;mso-fareast-language:EN-GB">
Tomaso.deCola@dlr.de <Tomaso.deCola@dlr.de> <br>
<b>Sent:</b> Friday, June 7, 2024 11:21 AM<br>
<b>To:</b> Felix Flentge <Felix.Flentge@esa.int><br>
<b>Cc:</b> sis-dtn@mailman.ccsds.org; Edward.Birrane@jhuapl.edu<br>
<b>Subject:</b> AW: DTN Reference Scenarios<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" style="margin-left:36.0pt"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="DE" style="font-family:"Calibri",sans-serif">Hi Felix,<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="DE" style="font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" style="font-family:"Calibri",sans-serif">thank your for the answers.
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" style="font-family:"Calibri",sans-serif">Concerning “the yellow is the new green”, I’m honestly not much convinced of that also because we already have a green book dealing with those subjects,
so coming up with a new and different book won’t help much, as we’ll have in any case to update the green book (soon or later). Moreover, according to the CCSDS organization and procedures book:<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><i><span lang="EN-US" style="font-family:"Calibri",sans-serif">“Yellow Books may be reports or meeting records, but they are also used for documenting CCSDS internal processes, procedures, and controlling guidelines
and for documenting interoperability test plans and reports. Yellow Books shall be used to document the test plans and test reports produced in support of CCSDS Blue Book interoperability testing. Yellow Books may also be used to document CCSDS internal processes,
procedures, and controlling guidelines. This document is itself a CCSDS Yellow Book, and it is a controlling document describing CCSDS procedures. Any CCSDS Yellow Book that is normative upon CCSDS itself requires CESG and CMC approval polling.”<o:p></o:p></span></i></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" style="font-family:"Calibri",sans-serif">In this light ,IMHO I don’t see yellow book as the place for scenarios discussion/analysis, but I’m in any case open. We can further discuss on this
point once the iteration on DTN scenarios can be considered closed or at least consolidated.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" style="font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" style="font-family:"Calibri",sans-serif">Best,<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" style="font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" style="font-family:"Calibri",sans-serif">Tomaso<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" style="margin-left:36.0pt"><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">
Felix Flentge <<a href="mailto:Felix.Flentge@esa.int">Felix.Flentge@esa.int</a>>
<br>
<b>Gesendet:</b> Freitag, 7. Juni 2024 10:13<br>
<b>An:</b> de Cola, Tomaso <<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>;
<a href="mailto:Edward.Birrane@jhuapl.edu">Edward.Birrane@jhuapl.edu</a><br>
<b>Betreff:</b> RE: DTN Reference Scenarios<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="DE"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt">Hi Tomaso,<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt">Please see my replies below.<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"><o:p> </o:p></p>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="mso-ligatures:none;mso-fareast-language:EN-GB">Regards,<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="mso-ligatures:none;mso-fareast-language:EN-GB">Felix<o:p></o:p></span></p>
</div>
<p class="MsoNormal" style="margin-left:36.0pt"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" style="margin-left:72.0pt"><b><span lang="EN-US" style="font-family:"Calibri",sans-serif;mso-ligatures:none;mso-fareast-language:EN-GB">From:</span></b><span lang="EN-US" style="font-family:"Calibri",sans-serif;mso-ligatures:none;mso-fareast-language:EN-GB">
<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:72.0pt"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:72.0pt"><span lang="DE" style="font-family:"Calibri",sans-serif">Hi Felix,<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:72.0pt"><span lang="DE" style="font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:72.0pt"><span lang="EN-US" 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:72.0pt"><span lang="EN-US" style="font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:72.0pt"><span lang="EN-US" style="font-family:"Calibri",sans-serif">Just three comments:<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:72.0pt"><span lang="EN-US" style="font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="margin-left:108.0pt;text-indent:-18.0pt;mso-list:l0 level1 lfo2">
<![if !supportLists]><span lang="EN-US" 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 lang="EN-US" 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:36.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="margin-left:108.0pt;text-indent:-18.0pt;mso-list:l0 level1 lfo2">
<![if !supportLists]><span lang="EN-US" 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 lang="EN-US" 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:36.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="margin-left:108.0pt;text-indent:-18.0pt;mso-list:l0 level1 lfo2">
<![if !supportLists]><span lang="EN-US" 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 lang="EN-US" 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:36.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:108.0pt"><span lang="EN-US">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></span></p>
<p class="MsoNormal" style="margin-left:90.0pt"><span lang="EN-US" style="font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:72.0pt"><span lang="EN-US" 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:36.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt;text-indent:36.0pt"><span lang="EN-US">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></span></p>
<p class="MsoNormal" style="margin-left:72.0pt"><span lang="EN-US" style="font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:72.0pt"><span lang="EN-US" style="font-family:"Calibri",sans-serif">Regards,<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:72.0pt"><span lang="EN-US" style="font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:72.0pt"><span lang="EN-US" style="font-family:"Calibri",sans-serif">Tomaso<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:72.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" style="margin-left:72.0pt"><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:72.0pt"><span lang="DE"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:72.0pt">Dear All,<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:72.0pt"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:72.0pt">I have uploaded today’s presentation on DTN Reference Scenarios to CWE:<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:72.0pt"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:72.0pt"><a href="https://cwe.ccsds.org/sis/docs/SIS-DTN/Other%20Documents/DTN%20Reference%20Scenario/CCSDS%20DTN%20Scenarios.pptx?d=wf3b24c8d83344cf998bc7846fe279269">https://cwe.ccsds.org/sis/docs/SIS-DTN/Other%20Documents/DTN%20Reference%20Scenario/CCSDS%20DTN%20Scenarios.pptx?d=wf3b24c8d83344cf998bc7846fe279269</a><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:72.0pt"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:72.0pt">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></p>
<p class="MsoNormal" style="margin-left:72.0pt"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:72.0pt"><span style="mso-ligatures:none;mso-fareast-language:EN-GB">Regards,<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:72.0pt"><span style="mso-ligatures:none;mso-fareast-language:EN-GB">Felix<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:72.0pt"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:72.0pt"><span 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:36.0pt"><span 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>
</div>
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).
</body>
</html>