<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";
panose-1:2 11 6 0 7 2 5 8 2 4;}
@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:0in;
font-size:10.0pt;
font-family:"Aptos",sans-serif;}
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:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal-reply;
color:black;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:623077540;
mso-list-template-ids:1670692286;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1
{mso-list-id:860778667;
mso-list-template-ids:1462150010;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
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:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level2
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
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:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level2
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#467886" vlink="#96607D" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:black">Peter, Tomaso:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">I think we’re in agreement in the architectural sense that BP forms the e2e backbone linking IP domains when there is a physical/performance difference that limits the extent of the IP domain. One suggestion occurs
to me – Enhance the protocol stack diagrams to distinguish between differing environments for which the various protocols are intended to operate.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black">Link layer examples: 3GPP operates within a defined environment that makes it suitable for surface-surface communications. So does WiFi but its environmental limits are different, e.g., range.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black">Network layer: IP operates in connected & mesh environments with low latency while BP operates in intermittently connected & long latency environments.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black">If we depict those differences as ‘background’ (or ‘underlying’) with boundaries between regions with different characteristics, then the choice of which protocols to use & where is driven by the scenario/use case.
The difference between low latency & high, for example, could be different backgrounds for parts of the diagram and the boundary between them shows why a border gateway is needed to switch protocol stacks.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black">I think we’re all aware of that distinction but it might make it easier to communicate it to others.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black">Jim<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</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>Sent:</b> Tuesday, March 5, 2024 12:27 PM<br>
<b>To:</b> Tomaso.deCola@dlr.de; Klaus-Juergen.Schulz@esa.int; Asmar, Sami W (JPL-9100)[JPL Employee] <sami.w.asmar@jpl.nasa.gov>; murata.masaya@jaxa.jp; Schier, James (HQ-CG000) <james.schier-1@nasa.gov><br>
<b>Cc:</b> AMassaquoi@asrcfederal.com; Peura, Angela D. (HQ-CG000)[Agile Decision Sciences] <angela.d.peura@nasa.gov>; cesg@mailman.ccsds.org<br>
<b>Subject:</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 style="font-size:11.0pt;font-family:"Calibri",sans-serif">Hi Tomaso,<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 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 style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span 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 style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span 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://www.franklincovey.com/the-7-habits/habit-2/">
https://www.franklincovey.com/the-7-habits/habit-2/</a><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 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 style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span 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 style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Thanks, 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 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 0in 0in 0in">
<p class="MsoNormal"><b><span lang="DE" style="font-size:12.0pt;font-family:"Calibri",sans-serif;color:black">From:
</span></b><span lang="DE" 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 lang="DE" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span lang="DE" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Hi Peter,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="DE" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span 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 style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Regards,<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 style="font-size:11.0pt;font-family:"Calibri",sans-serif">Tomaso<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span lang="DE" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Von:</span></b><span lang="DE" 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"><span lang="DE"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Hi Tomaso,<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 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 style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span 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 style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span 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 style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Best regards, 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 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 0in 0in 0in">
<p class="MsoNormal"><b><span lang="DE" style="font-size:12.0pt;font-family:"Calibri",sans-serif;color:black">From:
</span></b><span lang="DE" 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 lang="DE" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span lang="DE" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Hi Peter,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="DE" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span 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 style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span 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 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 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 style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Tomaso<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"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span lang="DE" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Von:</span></b><span lang="DE" 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"><span lang="DE"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Tomaso,<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 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 style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span 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 style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span 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 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 style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span 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 style="font-size:12.0pt;font-family:"Calibri",sans-serif">“</span><span 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 style="font-size:12.0pt;font-family:"Calibri",sans-serif">”.</span><span style="font-size:14.0pt;font-family:"Calibri",sans-serif"> </span><span 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 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 0in 0in 0in">
<p class="MsoNormal"><b><span lang="DE" style="font-size:12.0pt;font-family:"Calibri",sans-serif;color:black">From:
</span></b><span lang="DE" 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 lang="DE" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span lang="DE" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Dear All,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="DE" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span 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 style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Best Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><br>
Tomaso<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span lang="DE" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Von:</span></b><span lang="DE" 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 lang="DE" 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"><span lang="DE"><o:p> </o:p></span></p>
<p class="MsoNormal"><span 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 style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Teach me to rush.<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 style="font-size:11.0pt;font-family:"Calibri",sans-serif">Sorry, 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 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 0in 0in 0in">
<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">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 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 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">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 style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Best regards, 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 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 0in 0in 0in">
<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 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span 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 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 style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span 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 style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">I agree we should add the other keywords.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span 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 0in 0in 0in">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="font-size:12.0pt;color:black;mso-fareast-language:JA">From:
</span></b><span 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 style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black;mso-fareast-language:JA"> </span><span 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 style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA">Hi Sami.</span><span style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA"> </span><span style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA">Because the following theme just touches lunar
<span lang="JA">“</span>communications<span lang="JA">”</span>, I was wondering about lunar
<span lang="JA">“</span>navigation<span lang="JA">”</span>. It might be better to add keywords
<span lang="JA">“</span>navigation<span lang="JA">”</span> or <span lang="JA">“</span>PNT<span lang="JA">”</span> in the theme so that people from navigation community would be also participating without a problem.
</span><span style="mso-fareast-language:JA"><o:p></o:p></span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="mso-list:l3 level1 lfo3"><b><span style="font-size:12.0pt;mso-fareast-language:JA">Theme: </span></b><span 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 style="mso-fareast-language:JA"><o:p></o:p></span></li></ul>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA"> </span><span style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA">Best regards,</span><span style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA"> </span><span style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA">Masaya</span><span style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA"> </span><span style="mso-fareast-language:JA"><o:p></o:p></span></p>
<div>
<div id="divtagdefaultwrapper">
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Calibri",sans-serif;color:black;mso-fareast-language:JA">----------------------------------------------------------</span><span style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Calibri",sans-serif;color:black;mso-fareast-language:JA">Masaya Murata</span><span style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Calibri",sans-serif;color:black;mso-fareast-language:JA">Japan Aerospace eXploration Agency</span><span style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Calibri",sans-serif;color:black;mso-fareast-language:JA">Phone: 050-3362-3985</span><span style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span 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 style="mso-fareast-language:JA"><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Calibri",sans-serif;color:black;mso-fareast-language:JA">----------------------------------------------------------</span><span 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 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:JA">From:</span></b><span 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 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 style="mso-fareast-language:JA"><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span style="mso-fareast-language:JA"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;mso-fareast-language:JA"> </span><span style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;mso-fareast-language:JA">I think is should within scope. Navigation tools and techniques must be interoperable.</span><span style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;mso-fareast-language:JA"> </span><span style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;mso-fareast-language:JA">Thanks</span><span style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;mso-fareast-language:JA"> </span><span style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;mso-fareast-language:JA"> </span><span 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 0in 0in 0in">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="font-size:12.0pt;color:black;mso-fareast-language:JA">From:
</span></b><span 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 style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black;mso-fareast-language:JA"> </span><span 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 style="mso-fareast-language:JA"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA">Hi Sami,</span><span style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA"> </span><span style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span 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 style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA">Regarding the theme, lunar
<span lang="JA">“</span>navigation<span lang="JA">”</span> or <span lang="JA">“</span>PNT<span lang="JA">”</span> is not within the scope of this forum?</span><span style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA"> </span><span style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA">Best regards,</span><span style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA"> </span><span style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA">Masaya</span><span style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Yu Gothic",sans-serif;mso-fareast-language:JA"> </span><span style="mso-fareast-language:JA"><o:p></o:p></span></p>
<div>
<div id="divtagdefaultwrapper">
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Calibri",sans-serif;color:black;mso-fareast-language:JA">----------------------------------------------------------</span><span style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Calibri",sans-serif;color:black;mso-fareast-language:JA">Masaya Murata</span><span style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Calibri",sans-serif;color:black;mso-fareast-language:JA">Japan Aerospace eXploration Agency</span><span style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Calibri",sans-serif;color:black;mso-fareast-language:JA">Phone: 050-3362-3985</span><span style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span 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 style="mso-fareast-language:JA"><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Calibri",sans-serif;color:black;mso-fareast-language:JA">----------------------------------------------------------</span><span 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 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:JA">From:</span></b><span 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 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 style="mso-fareast-language:JA"><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;mso-fareast-language:JA"> </span><span style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;mso-fareast-language:JA"> </span><span style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;mso-fareast-language:JA">Hi Jim and Masaya,</span><span style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;mso-fareast-language:JA"> </span><span style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span 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 style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;mso-fareast-language:JA"> </span><span style="mso-fareast-language:JA"><o:p></o:p></span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="mso-list:l2 level1 lfo6"><b><span style="font-size:12.0pt;mso-fareast-language:JA">Workshop title:</span></b><span style="font-size:12.0pt;mso-fareast-language:JA"> “Lunar Interoperability Forum”</span><span style="mso-fareast-language:JA"><o:p></o:p></span></li><li class="MsoNormal" style="mso-list:l2 level1 lfo6"><b><span style="font-size:12.0pt;mso-fareast-language:JA">Date:</span></b><span style="font-size:12.0pt;mso-fareast-language:JA"> 7 May 24 in Washington, DC</span><span style="mso-fareast-language:JA"><o:p></o:p></span></li><li class="MsoNormal" style="mso-list:l2 level1 lfo6"><b><span style="font-size:12.0pt;mso-fareast-language:JA">Place: </span></b><span style="font-size:12.0pt;mso-fareast-language:JA">US Dept of Commerce (NOTE: may need to work access issues)</span><span style="mso-fareast-language:JA"><o:p></o:p></span></li><li class="MsoNormal" style="mso-list:l2 level1 lfo6"><b><span style="font-size:12.0pt;mso-fareast-language:JA">Sponsors:
</span></b><span style="font-size:12.0pt;mso-fareast-language:JA">CCSDS & IOAG</span><span style="mso-fareast-language:JA"><o:p></o:p></span></li><li class="MsoNormal" style="mso-list:l2 level1 lfo6"><b><span style="font-size:12.0pt;mso-fareast-language:JA">Chair:
</span></b><span style="font-size:12.0pt;mso-fareast-language:JA">Sami Asmar</span><span style="mso-fareast-language:JA"><o:p></o:p></span></li><li class="MsoNormal" style="mso-list:l2 level1 lfo6"><b><span style="font-size:12.0pt;mso-fareast-language:JA">Theme: </span></b><span 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 style="mso-fareast-language:JA"><o:p></o:p></span></li><li class="MsoNormal" style="mso-list:l2 level1 lfo6"><b><span style="font-size:12.0pt;mso-fareast-language:JA">CCSDS objective</span></b><span 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 style="mso-fareast-language:JA"><o:p></o:p></span></li></ul>
<p class="MsoNormal"><span style="font-size:12.0pt;mso-fareast-language:JA"> </span><span style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span 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 style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;mso-fareast-language:JA"> </span><span style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;mso-fareast-language:JA">Jim will also be one of our speakers, of course.</span><span style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;mso-fareast-language:JA"> </span><span style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;mso-fareast-language:JA">Sami</span><span style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;mso-fareast-language:JA"> </span><span style="mso-fareast-language:JA"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;mso-fareast-language:JA"> </span><span 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>