<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:"MS Gothic";
panose-1:2 11 6 9 7 2 5 8 2 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:"Yu Gothic";
panose-1:2 11 4 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"\@MS Gothic";
panose-1:2 11 6 9 7 2 5 8 2 4;}
@font-face
{font-family:"MS PGothic";
panose-1:2 11 6 0 7 2 5 8 2 4;}
@font-face
{font-family:"\@MS PGothic";}
@font-face
{font-family:"\@Yu Gothic";
panose-1:2 11 4 0 0 0 0 0 0 0;}
@font-face
{font-family:Aptos;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:Aptos;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#467886;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#96607D;
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:11.0pt;
font-family:"Calibri",sans-serif;}
span.E-MailFormatvorlage18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.E-MailFormatvorlage20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@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:572860566;
mso-list-template-ids:-2015741300;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1
{mso-list-id:690184539;
mso-list-template-ids:955003572;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2
{mso-list-id:977031560;
mso-list-template-ids:348833562;}
@list l2:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level2
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3
{mso-list-id:1023869734;
mso-list-template-ids:-757273232;}
@list l3:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level2
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
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="DE" link="#467886" vlink="#96607D">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">Hi Peter,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">concerning these 43 solutions, I‘ve to check. My impression in any case is that the S&F is not addressed in all 43 solutions, but in
just few of them. Moreover I got to know yesterday from one of the companies pushing for this concept in their satellites that so far they considered an ad-hoc solution and proprietary solution for S&F, which as such won’t be landing onto 3GPP standardization.
They are in any case open to consider BP-solutions for that. <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">I’m also not a super-expert of 3GPP but in general I agree with you that their main focus is mostly at L1/L2 of the protocol stack for
what concerns the radio access network (RAN) and then is mostly about control/management plane for the core network and integration with the RAN. What’s happening on the higher layers of the protocol stack will be pretty much IP-based so that in principle
putting on top a DTN-based protocol stack (e.g., BP over TCP or BP over UDP) should be doable, which is actually what already proposed in the SOIS book we were discussing these last days.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">As to the IP islands, as you may know in IETF there are some discussions more towards the use of IP for deep-space possibly even replacing
DTN, which looks quite debatable. But at the moment it’s just an internet-draft and in the last months there was not much activity around it. Maybe something more will happen at the next IETF meeting starting in 10 days. Some ideas about IP-islands within
a DTN-based network architecture is actually something that was proposed by the Chinese space agency during the last Fall meeting with a dedicated presentation in the SIS-DTN WG, with the possible idea to go further with a SIG, eventually leading to a BOF
and a WG if things get mature enough. But at that time it was not clear whether other agencies could support this initiative, otherwise an activity run by just an agency would not make much sense. I’ve to discuss further with the DTN WG how we could move further
with that (if we want to move at all…), although eventually the SIG will formally be in the SIS area but external to the DTN WG. But still many of the people of the SIS-DTN should likely be involved there. Obviously if you can share any ideas/suggestions on
this, these will be as usual very welcome!<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">Best Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">Tomaso<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language: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"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Von:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Shames, Peter M (US 312B) <peter.m.shames@jpl.nasa.gov>
<br>
<b>Gesendet:</b> Mittwoch, 6. März 2024 22:11<br>
<b>An:</b> de Cola, Tomaso <Tomaso.deCola@dlr.de>; Klaus-Juergen.Schulz@esa.int; Asmar, Sami W (US 9100) <sami.w.asmar@jpl.nasa.gov>; murata.masaya@jaxa.jp; james.schier-1@nasa.gov; Jonathan.J.Wilmot@NASA.gov<br>
<b>Cc:</b> AMassaquoi@asrcfederal.com; angela.d.peura@nasa.gov; cesg@mailman.ccsds.org<br>
<b>Betreff:</b> Re: [EXTERNAL] RE: Moving forward with Lunar Interoperability Forum<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Hi Tomaso,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">As I said before, I am really glad to hear that you are so actively engaged in this 3GPP effort. I do not think that anyone else is similarly engaged, except,
perhaps, from Jonathan Wilmot’s SOIS crew. That SOIS document you mentioned in the 883.0-B book that is now in CESG review.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">I had heard, separately, that there were many different S&F solutions proposed, was not aware that it was as many as 43. I was about to say that I could not imagine
that there were 43 truly different solutions, but where money and company “positioning” is involved the objectives must be something like “market share”, “differentiation” and “user lock-in” and not interoperability.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">I am of the opinion, perhaps totally wrong, that the focus on 3GPP is really on what we would call the “link layer” and the management and control of end user
devices. If they change some of the details in that stack from one version to another that should not matter at the network layer and above. I believe that these devices run TCP/IP as a network “stack” on top of the link layers. As I understand it, this
network stack has two uses, one is support of user services, the other supports the management, access control, authentication, etc. Is this correct in your view?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">If it is right, then I believe what we will need to do is to put a DTN “stack” on top of the link layer as well, to support end node user services and support
end-to-end DTN traffic over the rest of the long haul backbone. The other piece I think we will need to add, in the “islands of IP mode” is to define and build a protocol translating gateway that will allow the “IP Island” to operate as it does, but to take
some subset of protocols, RFC822 email and RFC959 FTP come to mind, to interface over a DTN transport. I do not think anyone has defined that at this point, but it has surfaced in discussion in certain circles. Is this something you are aware of / have opinions
about?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Best regards, Peter<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:12.0pt;font-family:"Calibri",sans-serif;color:black">From:
</span></b><span style="font-size:12.0pt;font-family:"Calibri",sans-serif;color:black">"<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>Date: </b>Wednesday, March 6, 2024 at 12:18 AM<br>
<b>To: </b>Peter Shames <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>>, Klaus-Juergen Schulz <<a href="mailto:Klaus-Juergen.Schulz@esa.int">Klaus-Juergen.Schulz@esa.int</a>>, Sami Asmar <<a href="mailto:sami.w.asmar@jpl.nasa.gov">sami.w.asmar@jpl.nasa.gov</a>>,
"<a href="mailto:murata.masaya@jaxa.jp">murata.masaya@jaxa.jp</a>" <<a href="mailto:murata.masaya@jaxa.jp">murata.masaya@jaxa.jp</a>>, Jim Schier <<a href="mailto:james.schier-1@nasa.gov">james.schier-1@nasa.gov</a>>, "Wilmot, Jonathan J. (GSFC-5820)" <<a href="mailto:Jonathan.J.Wilmot@NASA.gov">Jonathan.J.Wilmot@NASA.gov</a>><br>
<b>Cc: </b>Amber Massaquoi <<a href="mailto:AMassaquoi@asrcfederal.com">AMassaquoi@asrcfederal.com</a>>, "<a href="mailto:angela.d.peura@nasa.gov">angela.d.peura@nasa.gov</a>" <<a href="mailto:angela.d.peura@nasa.gov">angela.d.peura@nasa.gov</a>>, CESG <<a href="mailto:cesg@mailman.ccsds.org">cesg@mailman.ccsds.org</a>><br>
<b>Subject: </b>AW: [EXTERNAL] RE: Moving forward with Lunar Interoperability Forum<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Well let me say that the focus of 3GPP with the ongoing releases and the past ones was mostly towards 5G specification and deployment for terrestrial infrastructures,
i.e. on Earth. If they mentioned Moon in any documents, I’d say it was just for the sake of exemplification. Jonathan can know more on this, since if I’m not wrong there is still a book from SOIS about these aspects under update.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">By chance I was already yesterday in a meeting with the NTN community about the forthcoming SI/WI in 3GPP and we shortly discussed also the point of the S&F function.
Apparently so far 3GPP has not considered yet DTN and other 43 solutions (!) have been proposed instead, not sure though whether they are all about S&F. In any case, quite a few stakeholders raised interest towards the possible use of DTN, but it is clarified
whether its use can meet the requirements of the use cases so far formulated, and more importantly if the power budget considered for NGSO satellite so far can accommodate a full DTN protocol stack (I know putting “just” a gNB in space is quite challenging).
I’ll iterate further with the people there and then let’s see what happens. As you correctly spotted in a previous email, the 3GPP procedures with respect to WI/SI adoption etc. is way different from CCSDS, already in terms of number of participating entities,
which are commercial entities whereby individual market interests have sometime higher priority.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">The picture you took in my opinion is too 4G-oriented, in the sense that the takes into account still components and interfaces that are not any longer in the
5GSA mode, such as the S-GW, the PGW, and the Sx interfaces (5G architecture is now more service-oriented and Sx interfaces are replaced by Nx). But as said, I tend to think that some update of this book will happen in the near future if the plan is to accommodate
a 5G architecture on Moon. I agree in any case that convergence between these standards is needed to have a fully interoperable system from user side (probably more 3GPP-driven) and then from a transportation standpoint (probably more CCSDS-driven).<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Best,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Tomaso<o:p></o:p></span></p>
<p class="MsoNormal"><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"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Von:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Shames, Peter M (US 312B) <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>>
<br>
<b>Gesendet:</b> Dienstag, 5. März 2024 18:27<br>
<b>An:</b> de Cola, Tomaso <<a href="mailto:Tomaso.deCola@dlr.de">Tomaso.deCola@dlr.de</a>>;
<a href="mailto:Klaus-Juergen.Schulz@esa.int">Klaus-Juergen.Schulz@esa.int</a>; Asmar, Sami W (US 9100) <<a href="mailto:sami.w.asmar@jpl.nasa.gov">sami.w.asmar@jpl.nasa.gov</a>>;
<a href="mailto:murata.masaya@jaxa.jp">murata.masaya@jaxa.jp</a>; <a href="mailto:james.schier-1@nasa.gov">
james.schier-1@nasa.gov</a><br>
<b>Cc:</b> <a href="mailto:AMassaquoi@asrcfederal.com">AMassaquoi@asrcfederal.com</a>;
<a href="mailto:angela.d.peura@nasa.gov">angela.d.peura@nasa.gov</a>; <a href="mailto:cesg@mailman.ccsds.org">
cesg@mailman.ccsds.org</a><br>
<b>Betreff:</b> Re: [EXTERNAL] RE: Moving forward with Lunar Interoperability Forum<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Hi Tomaso,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">That sounds like a good plan, and it should benefit SIS for the use of BP (& BPSec). I think it would be even more beneficial if we could get the 3GPP community
to understand the potential uses of 3GPP technology off-planet, on the surface of the Moon, as the SOIS 3GPP effort intends. This takes some further thought because a lot of the intrinsically required 3GPP authentication and access control requires its own
(local) IP-based infrastructure. <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Furthermore, what I think we really need is a well formed, clearly documented, end-to-end, comm architecture that features DTN at the network layer, CCSDS and
other links like 3GPP or WiFi at the link layer, and the ability to join together remote “islands of IP” using DTN as the network “backbone”. This is beyond just getting the 3GPP consortium to adopt DTN for their purposes, but it is, I believe, what we will
need end-to-end for LunaNet and other similar Lunar deployments. <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">If we all agree that this is where we need to wind up let’s make sure that we start in the right direction to get there. Like Steven Covey, and other wise leaders,
say “Begin with the end in mind”. <a href="https://urldefense.us/v3/__https:/www.franklincovey.com/the-7-habits/habit-2/__;!!PvBDto6Hs4WbVuu7!MFFPGWas4LNsyM6O30djGXl6okP2hwB-5YGdZPRtJ7bt9XhHHdnIvnv7UZH3W_XHU3bXEM5HpXnnMdTxY2YAUXavCCv1SWGa$">
https://www.franklincovey.com/the-7-habits/habit-2/</a><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">The appended diagram, taken from the SOIS 883.0-B-1 3GPP and WiFi document, is, I believe, one of the best examples we have of an end-to-end architecture that
shows DTN E2E and includes 3GPP (or WiFi) tail circuits. It is missing a specific “islands of IP” component, largely because that was not what they were trying to accomplish.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Can we agree that this larger vision is important and try to work to achieve it. Can we also agree that this kind of architecture is “in the ballpark” of what
will be needed?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Thanks, Peter<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:12.0pt;font-family:"Calibri",sans-serif;color:black">From:
</span></b><span style="font-size:12.0pt;font-family:"Calibri",sans-serif;color:black">"<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>Date: </b>Tuesday, March 5, 2024 at 1:28 AM<br>
<b>To: </b>Peter Shames <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>>, Klaus-Juergen Schulz <<a href="mailto:Klaus-Juergen.Schulz@esa.int">Klaus-Juergen.Schulz@esa.int</a>>, Sami Asmar <<a href="mailto:sami.w.asmar@jpl.nasa.gov">sami.w.asmar@jpl.nasa.gov</a>>,
"<a href="mailto:murata.masaya@jaxa.jp">murata.masaya@jaxa.jp</a>" <<a href="mailto:murata.masaya@jaxa.jp">murata.masaya@jaxa.jp</a>>, Jim Schier <<a href="mailto:james.schier-1@nasa.gov">james.schier-1@nasa.gov</a>><br>
<b>Cc: </b>Amber Massaquoi <<a href="mailto:AMassaquoi@asrcfederal.com">AMassaquoi@asrcfederal.com</a>>, "<a href="mailto:angela.d.peura@nasa.gov">angela.d.peura@nasa.gov</a>" <<a href="mailto:angela.d.peura@nasa.gov">angela.d.peura@nasa.gov</a>>, CESG <<a href="mailto:cesg@mailman.ccsds.org">cesg@mailman.ccsds.org</a>><br>
<b>Subject: </b>AW: [EXTERNAL] RE: Moving forward with Lunar Interoperability Forum<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Hi Peter,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">yes I’ve some contacts there that I’ll try to exploit to better understand what is the plan and possibly create some joint plan between CCSDS and 3GPP to make
sure that in the case BP is planned to be used this is done in the proper way.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Tomaso<o:p></o:p></span></p>
<p class="MsoNormal"><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"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Von:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Shames, Peter M (US 312B) <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>>
<br>
<b>Gesendet:</b> Montag, 4. März 2024 18:22<br>
<b>An:</b> de Cola, Tomaso <<a href="mailto:Tomaso.deCola@dlr.de">Tomaso.deCola@dlr.de</a>>;
<a href="mailto:Klaus-Juergen.Schulz@esa.int">Klaus-Juergen.Schulz@esa.int</a>; Asmar, Sami W (US 9100) <<a href="mailto:sami.w.asmar@jpl.nasa.gov">sami.w.asmar@jpl.nasa.gov</a>>;
<a href="mailto:murata.masaya@jaxa.jp">murata.masaya@jaxa.jp</a>; <a href="mailto:james.schier-1@nasa.gov">
james.schier-1@nasa.gov</a><br>
<b>Cc:</b> <a href="mailto:AMassaquoi@asrcfederal.com">AMassaquoi@asrcfederal.com</a>;
<a href="mailto:angela.d.peura@nasa.gov">angela.d.peura@nasa.gov</a>; <a href="mailto:cesg@mailman.ccsds.org">
cesg@mailman.ccsds.org</a><br>
<b>Betreff:</b> Re: [EXTERNAL] RE: Moving forward with Lunar Interoperability Forum<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Hi Tomaso,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Thanks for the informative reply. Getting to see your slides the end of this week would be fine. For me it’s more a matter of curiosity and wanting to stay informed.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">The fact that you have been tracking these 3GPP is really good to hear. It appears that you have been involved in this for some time and that is excellent from
my point of view. So we have, one way or another, both SOIS and SIS engaged in this, from two somewhat different points of view. Perhaps we should consider having a sort of side discussion among interested CCSDS parties and any support staff who are involved.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">I like your suggestion of trying to have a “technical discussion with the people involved in the standardization of this S&F service”. Do you have contact with
any of them? Would you want to have a discussion that involved the SOIS guys too? And I still think it might be useful to form a liaison with them, but maybe this discussion you propose is the best way to assess that and facilitate it.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Best regards, Peter<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:12.0pt;font-family:"Calibri",sans-serif;color:black">From:
</span></b><span style="font-size:12.0pt;font-family:"Calibri",sans-serif;color:black">"<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>Date: </b>Monday, March 4, 2024 at 2:47 AM<br>
<b>To: </b>Peter Shames <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>>, Klaus-Juergen Schulz <<a href="mailto:Klaus-Juergen.Schulz@esa.int">Klaus-Juergen.Schulz@esa.int</a>>, Sami Asmar <<a href="mailto:sami.w.asmar@jpl.nasa.gov">sami.w.asmar@jpl.nasa.gov</a>>,
"<a href="mailto:murata.masaya@jaxa.jp">murata.masaya@jaxa.jp</a>" <<a href="mailto:murata.masaya@jaxa.jp">murata.masaya@jaxa.jp</a>>, Jim Schier <<a href="mailto:james.schier-1@nasa.gov">james.schier-1@nasa.gov</a>><br>
<b>Cc: </b>Amber Massaquoi <<a href="mailto:AMassaquoi@asrcfederal.com">AMassaquoi@asrcfederal.com</a>>, "<a href="mailto:angela.d.peura@nasa.gov">angela.d.peura@nasa.gov</a>" <<a href="mailto:angela.d.peura@nasa.gov">angela.d.peura@nasa.gov</a>>, CESG <<a href="mailto:cesg@mailman.ccsds.org">cesg@mailman.ccsds.org</a>><br>
<b>Subject: </b>AW: [EXTERNAL] RE: Moving forward with Lunar Interoperability Forum<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Hi Peter,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">if I manage I could share the slides by Friday this week, it will be in any case a introduction to CCSDS and SIS area as this webinar is part of the IPNSIG “academy”
series, as such no deep dive into CCSDS will be provided. Also because in 1h time I cannot provide too many details.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">As to the 3GPP activities, I’m well aware of what’s happening there around the so-called “non-terrestrial networks” (NTN) standardization activity.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">To the best of my knowledge, the S&F service was requested only the NB-IoT scenario so that each data received from the satellite could be stored onboard until
the satellite reaches the area where the destination is located and then dump the data accordingly. This scenario is under the assumption that no ISL were in place (as reference architecture in Rel. 18 of 3GPP). Then with the new release, ISL should be addressed
as well, but I don’t know if this is considered only for broadband service or also for the IoT part. I’m somehow following the standardization there so that at some point once the specification work will start I hope this will clearer whether or not this is
the case. The critical point, as you correctly spotted, is what 3GPP means by delay/disruption tolerant networking. To the best of my knowledge, there is not yet a clear idea in this respect, although they are not necessarily pointing to the DTN we know from
IETF/CCSDS, i.e. BP over convergence layer adapters. It can well be an ad-hoc service, where the packets processed by an onboard gNB (i.e. after PDCP protocol layer operations) are stored “somehow” in a dedicated UPF (user-plane function) module, which could
be in principle responsible also for switching/routing and other networking functionalities (if desirable). Obviously from this standpoint, one could think why not to directly use BP on top of PDCP (or if we want to keep an IP-based interface something like
BP over UDP over IP over PDCP) and in turn over the space link from a satellite to a ground station this could BP over EPP/SPP over USLP over DVB (some manufacturers are also fine over TM C&S). For sure it would be desirable to join forces between CCSDS and
3GPP in this respect to avoid re-inventing the wheel. Moreover, in the context of SOIS there are already a few books (e.g., CCSDS 883.0-B-1) addressing the integration of BP and 3GPP technologies.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">This said, I don’t know if the best would be to directly pursue a liaision between CCSDS and 3GPP or to have a technical discussion with the people involved in
the standardization of this S&F service as to better understand if 1) they want really to specify a S&F service and if so 2) convincing them about the fact that there exist already quite consolidated technology coming from us, i.e. DTN.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Tomaso<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><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"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Von:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Shames, Peter M (US 312B) <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>>
<br>
<b>Gesendet:</b> Freitag, 1. März 2024 20:33<br>
<b>An:</b> de Cola, Tomaso <<a href="mailto:Tomaso.deCola@dlr.de">Tomaso.deCola@dlr.de</a>>;
<a href="mailto:Klaus-Juergen.Schulz@esa.int">Klaus-Juergen.Schulz@esa.int</a>; Asmar, Sami W (US 9100) <<a href="mailto:sami.w.asmar@jpl.nasa.gov">sami.w.asmar@jpl.nasa.gov</a>>;
<a href="mailto:murata.masaya@jaxa.jp">murata.masaya@jaxa.jp</a>; <a href="mailto:james.schier-1@nasa.gov">
james.schier-1@nasa.gov</a><br>
<b>Cc:</b> <a href="mailto:AMassaquoi@asrcfederal.com">AMassaquoi@asrcfederal.com</a>;
<a href="mailto:angela.d.peura@nasa.gov">angela.d.peura@nasa.gov</a>; <a href="mailto:cesg@mailman.ccsds.org">
cesg@mailman.ccsds.org</a><br>
<b>Betreff:</b> Re: [EXTERNAL] RE: Moving forward with Lunar Interoperability Forum<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Tomaso,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">I think this is great. The more that we can all speak and deliver essentially the same message, in our own voices of course, the better off we will be.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Would you be willing to share your materials prior to delivering them?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Along these same lines of “Lunar Interoperability”, but on what should only be a slight tangent, I learned today that the 3rd Generation Partnership Project (3GPP)
has just published a document titled “</span><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif">3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on satellite access Phase 3</span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">”.
The public document is attached here. You may be saying “so what, what does this have to do with CCSDS and Lunar Interoperabilty?”.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">This document purports to describe a 5G architecture that corresponds to a set of 5G requirements that include “store & forward” and use over non-geo-stationary
satellite links (NGSO). And the example that is provided on pg 44, fig A-1, states
</span><span lang="EN-US" style="font-size:12.0pt;font-family:"Calibri",sans-serif">“</span><span lang="EN-US" style="font-size:12.0pt">The concept of “S&F” service is widely used in the fields of delay-tolerant networking and disruption-tolerant networking.</span><span lang="EN-US" style="font-size:12.0pt;font-family:"Calibri",sans-serif">”.</span><span lang="EN-US" style="font-size:14.0pt;font-family:"Calibri",sans-serif">
</span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">You might think that the use of those specific phrases means that they are adopting DTN, but, in fact, they do not mention DTN at all. In fact, what I understand is that
the 3GPP members, who are highly competitive instead of collaborative, supplied some 20 separate proposals all of which were different company owned approaches and none of which were DTN.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif">So yes, 3GPP is a little off-topic for Lunar interoperability, but I think it is highly germane. I think we, CCSDS, should seek a liaison relationship with the
3GPP and offer them up our DTN solution over their 5G circuits. This liaison relationship may or may not work, but I think it is worth a shot. The SOIS already has a working relationship with at least one of the 3GPP companies. NASA has, I know, some separate
3GPP effort going on. And somehow ETSI is also involved. What CCSDS (and the agencies involved in Lunar exploration), have to offer is a possible path to use of 3GPP architecture, and DTN, on the Moon. This is what the CCSDS 3GPP and WiFi document envisions.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif">What do you think? Is this something we should aggressively pursue, and now?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Regards, Peter<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:12.0pt;font-family:"Calibri",sans-serif;color:black">From:
</span></b><span style="font-size:12.0pt;font-family:"Calibri",sans-serif;color:black">"<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>Date: </b>Friday, March 1, 2024 at 12:43 AM<br>
<b>To: </b>Peter Shames <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>>, Klaus-Juergen Schulz <<a href="mailto:Klaus-Juergen.Schulz@esa.int">Klaus-Juergen.Schulz@esa.int</a>>, Sami Asmar <<a href="mailto:sami.w.asmar@jpl.nasa.gov">sami.w.asmar@jpl.nasa.gov</a>>,
"<a href="mailto:murata.masaya@jaxa.jp">murata.masaya@jaxa.jp</a>" <<a href="mailto:murata.masaya@jaxa.jp">murata.masaya@jaxa.jp</a>>, Jim Schier <<a href="mailto:james.schier-1@nasa.gov">james.schier-1@nasa.gov</a>><br>
<b>Cc: </b>Amber Massaquoi <<a href="mailto:AMassaquoi@asrcfederal.com">AMassaquoi@asrcfederal.com</a>>, "<a href="mailto:angela.d.peura@nasa.gov">angela.d.peura@nasa.gov</a>" <<a href="mailto:angela.d.peura@nasa.gov">angela.d.peura@nasa.gov</a>>, CESG <<a href="mailto:cesg@mailman.ccsds.org">cesg@mailman.ccsds.org</a>><br>
<b>Subject: </b>AW: [EXTERNAL] RE: Moving forward with Lunar Interoperability Forum<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Dear All,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">on March 14th I’m going to give an introduction to CCSDS SIS area activities at IPNSIG (<a href="https://urldefense.us/v3/__https:/www.ipnsig.org/__;!!PvBDto6Hs4WbVuu7!J-nIV4zd7yV9BYvLrs1ctVLv0FarmDfeulHFlG1e1_Su8I_aKAjFyn6kLF33gya0cMSkiyTtoY9F27BRU92mRidORa0z-n-2$">https://www.ipnsig.org/</a>).
I was thinking to share some information about this initiative at the end of the talk, although the date of the talk is relatively close to the deadline we set to collect the contributions. If you have any objections about my proposal, please let me know.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Best Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><br>
Tomaso<o:p></o:p></span></p>
<p class="MsoNormal"><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"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Von:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> CESG <<a href="mailto:cesg-bounces@mailman.ccsds.org">cesg-bounces@mailman.ccsds.org</a>>
<b>Im Auftrag von </b>Shames, Peter M (US 312B) via CESG<br>
<b>Gesendet:</b> Donnerstag, 29. Februar 2024 22:37<br>
<b>An:</b> Klaus-Juergen Schulz <<a href="mailto:Klaus-Juergen.Schulz@esa.int">Klaus-Juergen.Schulz@esa.int</a>>; Asmar, Sami W (US 9100) <<a href="mailto:sami.w.asmar@jpl.nasa.gov">sami.w.asmar@jpl.nasa.gov</a>>;
</span><span style="font-size:11.0pt;font-family:"MS Gothic"">村田 眞哉</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <<a href="mailto:murata.masaya@jaxa.jp">murata.masaya@jaxa.jp</a>>; Schier, James (HQ-CG000) <<a href="mailto:james.schier-1@nasa.gov">james.schier-1@nasa.gov</a>><br>
<b>Cc:</b> Massaquoi Amber <<a href="mailto:AMassaquoi@asrcfederal.com">AMassaquoi@asrcfederal.com</a>>; Peura, Angela D. (HQ-CG000)[Agile Decision Sciences] <<a href="mailto:angela.d.peura@nasa.gov">angela.d.peura@nasa.gov</a>>; CESG <<a href="mailto:cesg@mailman.ccsds.org">cesg@mailman.ccsds.org</a>><br>
<b>Betreff:</b> Re: [CESG] [EXTERNAL] RE: Moving forward with Lunar Interoperability Forum<br>
<b>Priorität:</b> Hoch<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Please use announcement v1a (attached). Angela pointed out (thank you) that I had written “pointing” instead of “positioning” as the “P” in PNT.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Teach me to rush.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Sorry, Peter<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:12.0pt;font-family:"Calibri",sans-serif;color:black">From:
</span></b><span lang="EN-US" style="font-size:12.0pt;font-family:"Calibri",sans-serif;color:black">Peter Shames <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>><br>
<b>Date: </b>Thursday, February 29, 2024 at 1:14 PM<br>
<b>To: </b>Klaus-Juergen Schulz <<a href="mailto:Klaus-Juergen.Schulz@esa.int">Klaus-Juergen.Schulz@esa.int</a>>, Sami Asmar <<a href="mailto:sami.w.asmar@jpl.nasa.gov">sami.w.asmar@jpl.nasa.gov</a>>,
</span><span style="font-size:12.0pt;font-family:"MS Gothic";color:black">村田 眞哉</span><span lang="EN-US" style="font-size:12.0pt;font-family:"Calibri",sans-serif;color:black"> <<a href="mailto:murata.masaya@jaxa.jp">murata.masaya@jaxa.jp</a>>, Jim Schier <<a href="mailto:james.schier-1@nasa.gov">james.schier-1@nasa.gov</a>><br>
<b>Cc: </b>"Peura, Angela D. (HQ-CG000)[Agile Decision Sciences]" <<a href="mailto:angela.d.peura@nasa.gov">angela.d.peura@nasa.gov</a>>, Amber Massaquoi <<a href="mailto:AMassaquoi@asrcfederal.com">AMassaquoi@asrcfederal.com</a>>, CESG <<a href="mailto:cesg@mailman.ccsds.org">cesg@mailman.ccsds.org</a>><br>
<b>Subject: </b>Re: [EXTERNAL] RE: Moving forward with Lunar Interoperability Forum<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Attached are the two revised files for the Lunar Interoperability Forum that include PNT as well as comm, and otherwise clean up wording.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Best regards, Peter<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-GB" style="font-size:12.0pt;font-family:"Calibri",sans-serif;color:black">From:
</span></b><span lang="EN-GB" style="font-size:12.0pt;font-family:"Calibri",sans-serif;color:black">Klaus-Juergen Schulz <<a href="mailto:Klaus-Juergen.Schulz@esa.int">Klaus-Juergen.Schulz@esa.int</a>><br>
<b>Date: </b>Thursday, February 29, 2024 at 1:54 AM<br>
<b>To: </b>Sami Asmar <<a href="mailto:sami.w.asmar@jpl.nasa.gov">sami.w.asmar@jpl.nasa.gov</a>>,
</span><span style="font-size:12.0pt;font-family:"MS Gothic";color:black">村田 眞哉</span><span lang="EN-GB" style="font-size:12.0pt;font-family:"Calibri",sans-serif;color:black"> <<a href="mailto:murata.masaya@jaxa.jp">murata.masaya@jaxa.jp</a>>, Jim Schier <<a href="mailto:james.schier-1@nasa.gov">james.schier-1@nasa.gov</a>>,
Peter Shames <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>><br>
<b>Cc: </b>"Peura, Angela D. (HQ-CG000)[Agile Decision Sciences]" <<a href="mailto:angela.d.peura@nasa.gov">angela.d.peura@nasa.gov</a>>, Amber Massaquoi <<a href="mailto:AMassaquoi@asrcfederal.com">AMassaquoi@asrcfederal.com</a>><br>
<b>Subject: </b>[EXTERNAL] RE: Moving forward with Lunar Interoperability Forum<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Dear Sami,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Yes, please add “Position, Navigation, Timing (PNT)” spelled out in the announcement. It was an oversight on the CESG side on Tuesday.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Best Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Klaus-Juergen<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;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 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Asmar, Sami W (US 9100) <<a href="mailto:sami.w.asmar@jpl.nasa.gov">sami.w.asmar@jpl.nasa.gov</a>>
<br>
<b>Sent:</b> Thursday, February 29, 2024 1:05 AM<br>
<b>To:</b> </span><span style="font-size:11.0pt;font-family:"MS Gothic"">村田 眞哉</span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <<a href="mailto:murata.masaya@jaxa.jp">murata.masaya@jaxa.jp</a>>; Schier, James (HQ-CG000) <<a href="mailto:james.schier-1@nasa.gov">james.schier-1@nasa.gov</a>>;
Shames, Peter M (US 312B) <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>><br>
<b>Cc:</b> Peura, Angela D. (HQ-CG000)[Agile Decision Sciences] <<a href="mailto:angela.d.peura@nasa.gov">angela.d.peura@nasa.gov</a>>; Massaquoi Amber <<a href="mailto:AMassaquoi@asrcfederal.com">AMassaquoi@asrcfederal.com</a>>; Klaus-Juergen Schulz <<a href="mailto:Klaus-Juergen.Schulz@esa.int">Klaus-Juergen.Schulz@esa.int</a>><br>
<b>Subject:</b> Re: Moving forward with Lunar Interoperability Forum<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt">Peter/Klaus-Juergen: Did the CESG intend for this to be limited to Communications?
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt">I agree we should add the other keywords.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt"><o:p> </o:p></span></p>
<div id="mail-editor-reference-message-container">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span lang="EN-US" style="font-size:12.0pt;color:black;mso-fareast-language:JA">From:
</span></b><span lang="EN-US" style="font-size:12.0pt;color:black;mso-fareast-language:JA"><a href="mailto:murata.masaya@jaxa.jp">murata.masaya@jaxa.jp</a> <<a href="mailto:murata.masaya@jaxa.jp">murata.masaya@jaxa.jp</a>><br>
<b>Date: </b>Wednesday, February 28, 2024 at 4:03</span><span lang="EN-US" style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black;mso-fareast-language:JA"> </span><span lang="EN-US" style="font-size:12.0pt;color:black;mso-fareast-language:JA">PM<br>
<b>To: </b>Asmar, Sami W (US 9100) <<a href="mailto:sami.w.asmar@jpl.nasa.gov">sami.w.asmar@jpl.nasa.gov</a>>, Schier, James (HQ-CG000) <<a href="mailto:james.schier-1@nasa.gov">james.schier-1@nasa.gov</a>>, Shames, Peter M (US 312B) <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>><br>
<b>Cc: </b>Peura, Angela D. (HQ-CG000)[Agile Decision Sciences] <<a href="mailto:angela.d.peura@nasa.gov">angela.d.peura@nasa.gov</a>>, Massaquoi Amber <<a href="mailto:AMassaquoi@asrcfederal.com">AMassaquoi@asrcfederal.com</a>><br>
<b>Subject: </b>[EXTERNAL] RE: Moving forward with Lunar Interoperability Forum<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA">Hi Sami.</span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA"> </span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA">Because the following theme just touches lunar
</span><span lang="JA" style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA">“</span><span lang="EN-US" style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA">communications</span><span lang="JA" style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA">”</span><span lang="EN-US" style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA">,
I was wondering about lunar </span><span lang="JA" style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA">“</span><span lang="EN-US" style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA">navigation</span><span lang="JA" style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA">”</span><span lang="EN-US" style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA">.
It might be better to add keywords </span><span lang="JA" style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA">“</span><span lang="EN-US" style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA">navigation</span><span lang="JA" style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA">”</span><span lang="EN-US" style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA">
or </span><span lang="JA" style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA">“</span><span lang="EN-US" style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA">PNT</span><span lang="JA" style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA">”</span><span lang="EN-US" style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA">
in the theme so that people from navigation community would be also participating without a problem.
</span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></p>
<ul style="margin-top:0cm" type="disc">
<li class="MsoNormal" style="mso-list:l3 level1 lfo3"><b><span lang="EN-US" style="font-size:12.0pt;mso-fareast-language:JA">Theme: </span></b><span lang="EN-US" style="font-size:12.0pt;mso-fareast-language:JA">Bringing together members of the Lunar communications
“community” to discuss drivers, opportunities, and means to foster development and deployment of interoperable (and secure) communications systems</span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></li></ul>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA"> </span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA">Best regards,</span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA"> </span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA">Masaya</span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA"> </span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></p>
<div>
<div id="divtagdefaultwrapper">
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt;font-family:"Calibri",sans-serif;color:black;mso-fareast-language:JA">----------------------------------------------------------</span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt;font-family:"Calibri",sans-serif;color:black;mso-fareast-language:JA">Masaya Murata</span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt;font-family:"Calibri",sans-serif;color:black;mso-fareast-language:JA">Japan Aerospace eXploration Agency</span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt;font-family:"Calibri",sans-serif;color:black;mso-fareast-language:JA">Phone: 050-3362-3985</span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt;font-family:"Calibri",sans-serif;color:black;mso-fareast-language:JA">Email: <a href="mailto:murata.masaya@jaxa.jp">murata.masaya@jaxa.jp</a></span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt;font-family:"Calibri",sans-serif;color:black;mso-fareast-language:JA">----------------------------------------------------------</span><span lang="EN-US" style="mso-fareast-language:JA"><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"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:JA">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:JA"> Asmar, Sami W
(US 9100) <<a href="mailto:sami.w.asmar@jpl.nasa.gov">sami.w.asmar@jpl.nasa.gov</a>>
<br>
<b>Sent:</b> Thursday, February 29, 2024 9:00 AM<br>
<b>To:</b> </span><span lang="JA" style="font-size:11.0pt;font-family:"MS PGothic",sans-serif;mso-fareast-language:JA">村田 眞哉</span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:JA"> <<a href="mailto:murata.masaya@jaxa.jp">murata.masaya@jaxa.jp</a>>;
Schier, James (HQ-CG000) <<a href="mailto:james.schier-1@nasa.gov">james.schier-1@nasa.gov</a>>; Shames, Peter M (US 312B) <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>><br>
<b>Cc:</b> Peura, Angela D. (HQ-CG000)[Agile Decision Sciences] <<a href="mailto:angela.d.peura@nasa.gov">angela.d.peura@nasa.gov</a>>; Massaquoi Amber <<a href="mailto:AMassaquoi@asrcfederal.com">AMassaquoi@asrcfederal.com</a>><br>
<b>Subject:</b> Re: Moving forward with Lunar Interoperability Forum</span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:JA"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt;mso-fareast-language:JA"> </span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt;mso-fareast-language:JA">I think is should within scope. Navigation tools and techniques must be interoperable.</span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt;mso-fareast-language:JA"> </span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt;mso-fareast-language:JA">Thanks</span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt;mso-fareast-language:JA"> </span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt;mso-fareast-language:JA"> </span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></p>
<div id="mail-editor-reference-message-container">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span lang="EN-US" style="font-size:12.0pt;color:black;mso-fareast-language:JA">From:
</span></b><span lang="EN-US" style="font-size:12.0pt;color:black;mso-fareast-language:JA"><a href="mailto:murata.masaya@jaxa.jp">murata.masaya@jaxa.jp</a> <<a href="mailto:murata.masaya@jaxa.jp">murata.masaya@jaxa.jp</a>><br>
<b>Date: </b>Wednesday, February 28, 2024 at 3:57</span><span lang="EN-US" style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black;mso-fareast-language:JA"> </span><span lang="EN-US" style="font-size:12.0pt;color:black;mso-fareast-language:JA">PM<br>
<b>To: </b>Asmar, Sami W (US 9100) <<a href="mailto:sami.w.asmar@jpl.nasa.gov">sami.w.asmar@jpl.nasa.gov</a>>, Schier, James (HQ-CG000) <<a href="mailto:james.schier-1@nasa.gov">james.schier-1@nasa.gov</a>>, Shames, Peter M (US 312B) <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>><br>
<b>Cc: </b>Peura, Angela D. (HQ-CG000)[Agile Decision Sciences] <<a href="mailto:angela.d.peura@nasa.gov">angela.d.peura@nasa.gov</a>>, Massaquoi Amber <<a href="mailto:AMassaquoi@asrcfederal.com">AMassaquoi@asrcfederal.com</a>><br>
<b>Subject: </b>[EXTERNAL] RE: Moving forward with Lunar Interoperability Forum</span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA">Hi Sami,</span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA"> </span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA">Thank you very much for the wonderful news.</span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA">Regarding the theme, lunar
</span><span lang="JA" style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA">“</span><span lang="EN-US" style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA">navigation</span><span lang="JA" style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA">”</span><span lang="EN-US" style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA">
or </span><span lang="JA" style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA">“</span><span lang="EN-US" style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA">PNT</span><span lang="JA" style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA">”
</span><span lang="EN-US" style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA">is not within the scope of this forum?</span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA"> </span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA">Best regards,</span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA"> </span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA">Masaya</span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA"> </span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></p>
<div>
<div id="divtagdefaultwrapper">
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt;font-family:"Calibri",sans-serif;color:black;mso-fareast-language:JA">----------------------------------------------------------</span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt;font-family:"Calibri",sans-serif;color:black;mso-fareast-language:JA">Masaya Murata</span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt;font-family:"Calibri",sans-serif;color:black;mso-fareast-language:JA">Japan Aerospace eXploration Agency</span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt;font-family:"Calibri",sans-serif;color:black;mso-fareast-language:JA">Phone: 050-3362-3985</span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt;font-family:"Calibri",sans-serif;color:black;mso-fareast-language:JA">Email: <a href="mailto:murata.masaya@jaxa.jp">murata.masaya@jaxa.jp</a></span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt;font-family:"Calibri",sans-serif;color:black;mso-fareast-language:JA">----------------------------------------------------------</span><span lang="EN-US" style="mso-fareast-language:JA"><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"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:JA">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:JA"> Asmar, Sami W
(US 9100) <<a href="mailto:sami.w.asmar@jpl.nasa.gov">sami.w.asmar@jpl.nasa.gov</a>>
<br>
<b>Sent:</b> Thursday, February 29, 2024 8:28 AM<br>
<b>To:</b> Schier, James (HQ-CG000) <<a href="mailto:james.schier-1@nasa.gov">james.schier-1@nasa.gov</a>>;
</span><span lang="JA" style="font-size:11.0pt;font-family:"MS PGothic",sans-serif;mso-fareast-language:JA">村田 眞哉</span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:JA"> <<a href="mailto:murata.masaya@jaxa.jp">murata.masaya@jaxa.jp</a>>;
Shames, Peter M (US 312B) <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>><br>
<b>Cc:</b> Peura, Angela D. (HQ-CG000)[Agile Decision Sciences] <<a href="mailto:angela.d.peura@nasa.gov">angela.d.peura@nasa.gov</a>>; Massaquoi Amber <<a href="mailto:AMassaquoi@asrcfederal.com">AMassaquoi@asrcfederal.com</a>><br>
<b>Subject:</b> Moving forward with Lunar Interoperability Forum</span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;mso-fareast-language:JA"> </span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt;mso-fareast-language:JA"> </span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt;mso-fareast-language:JA">Hi Jim and Masaya,</span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt;mso-fareast-language:JA"> </span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt;mso-fareast-language:JA">I wanted to let you know that the Forum will take place. We are changing it a little bit to separate from the procurement/tender process by NASA and ESA and make more
a community forum for exchange of relevant information.</span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt;mso-fareast-language:JA"> </span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></p>
<ul style="margin-top:0cm" type="disc">
<li class="MsoNormal" style="mso-list:l2 level1 lfo6"><b><span lang="EN-US" style="font-size:12.0pt;mso-fareast-language:JA">Workshop title:</span></b><span lang="EN-US" style="font-size:12.0pt;mso-fareast-language:JA"> “Lunar Interoperability Forum”</span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></li><li class="MsoNormal" style="mso-list:l2 level1 lfo6"><b><span lang="EN-US" style="font-size:12.0pt;mso-fareast-language:JA">Date:</span></b><span lang="EN-US" style="font-size:12.0pt;mso-fareast-language:JA"> 7 May 24 in Washington, DC</span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></li><li class="MsoNormal" style="mso-list:l2 level1 lfo6"><b><span lang="EN-US" style="font-size:12.0pt;mso-fareast-language:JA">Place: </span></b><span lang="EN-US" style="font-size:12.0pt;mso-fareast-language:JA">US Dept of Commerce (NOTE: may need to work access
issues)</span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></li><li class="MsoNormal" style="mso-list:l2 level1 lfo6"><b><span lang="EN-US" style="font-size:12.0pt;mso-fareast-language:JA">Sponsors:
</span></b><span lang="EN-US" style="font-size:12.0pt;mso-fareast-language:JA">CCSDS & IOAG</span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></li><li class="MsoNormal" style="mso-list:l2 level1 lfo6"><b><span lang="EN-US" style="font-size:12.0pt;mso-fareast-language:JA">Chair:
</span></b><span lang="EN-US" style="font-size:12.0pt;mso-fareast-language:JA">Sami Asmar</span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></li><li class="MsoNormal" style="mso-list:l2 level1 lfo6"><b><span lang="EN-US" style="font-size:12.0pt;mso-fareast-language:JA">Theme: </span></b><span lang="EN-US" style="font-size:12.0pt;mso-fareast-language:JA">Bringing together members of the Lunar communications
“community” to discuss drivers, opportunities, and means to foster development and deployment of interoperable (and secure) communications systems</span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></li><li class="MsoNormal" style="mso-list:l2 level1 lfo6"><b><span lang="EN-US" style="font-size:12.0pt;mso-fareast-language:JA">CCSDS objective</span></b><span lang="EN-US" style="font-size:12.0pt;mso-fareast-language:JA">: Encourage community members to participate
in CCSDS Standards activities, there are no other data standards orgs aside from the IETF DTN</span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></li></ul>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt;mso-fareast-language:JA"> </span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt;mso-fareast-language:JA">I know JAXA will have a presentation for us. We are now preparing the agenda and getting ready to send the announcement but wanted you to know first.</span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt;mso-fareast-language:JA"> </span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt;mso-fareast-language:JA">Jim will also be one of our speakers, of course.</span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt;mso-fareast-language:JA"> </span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt;mso-fareast-language:JA">Sami</span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt;mso-fareast-language:JA"> </span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12.0pt;mso-fareast-language:JA"> </span><span lang="EN-US" style="mso-fareast-language:JA"><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri",sans-serif">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>
</body>
</html>