<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Aptos;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle20
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1458333964;
mso-list-type:hybrid;
mso-list-template-ids:1862331454 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
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="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">CESG Colleagues,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I tend to support the approach, ideas that are in the “Role of CCSDS with respect to PNT at the Moon” document. I think that taking on a PNT effort in CCSDS cannot just be one single working group. And I think it should be the system engineering
area in conjunction with the CESG that figures out how to prioritize and look at the standards that need to be produced. It may be that this is really not so much given we already have, presumably, a good start with the signal format from ICG. Having said
that, it may be that it is easiest for a more public audience to grasp "expansion" of a working group in CCSDS to consider PNT more thoroughly for the moon. I will note that the proposed group here is technically not the "Timing WG” as noted in the presentation,
but really rather the “Time Management WG". Given that this is in the system engineering area, then this is probably going in the right direction.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">With regard to the document, it may well be that some sort of magenta book codifying what is good practices ultimately makes sense, but I don't think you want to lead with that in the presentation. I worry that this will come across as
too much “PhD-ing” (theory) versus getting towards practical solutions. At the same time, I think we could may be add something in the presentation to make it clear that one of the advantages of CCSDS would be the ability to marshal and orchestrate and/or
tune as necessary supporting standards that might be needed to get to a proper international PNT solution for the moon. So a suggestion for slide 4 could be to add a bullet point like:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">Ability to address supporting standards to facilitate complete PNT systems needs<o:p></o:p></li></ul>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">(nodes that support PNT delivery will of course need to be managed, implying trajectory determination, collision assessment, telecommand, telemetry, etc., for these nodes, all of which CCSDS addresses via its suite of standards)<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Slide 3 of the presentation – the Navigation WG and “Timing WG” (really “Time Management WG”) boxes are present throughout the entire set of animations. Perhaps this is intentional to highlight two of the key groups that would likely be
involved with PNT? But I find it detracts quite a bit from trying to present an overview of the CCSDS technical areas.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best regards,<o:p></o:p></p>
<p class="MsoNormal">-Erik<o:p></o:p></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>From:</b> CESG <cesg-bounces@mailman.ccsds.org> <b>On Behalf Of
</b>Lux, Jim (US 3370) via CESG<br>
<b>Sent:</b> Monday, February 10, 2025 10:13<br>
<b>To:</b> CESG <cesg@mailman.ccsds.org><br>
<b>Subject:</b> [EXTERNAL] [CESG] Following on Daniel's slides<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Daniel’s slides and my ideas sort of crossed in the mail.<o:p></o:p></p>
<p class="MsoNormal">In the attached, Peter Shames and I came up with some thoughts (not intended for direct distribution, more as thoughts to feed into what we might want to do). I was thinking that maybe CCSDS could define a PNT architecture (within the
framework we already have) – defining PNT unique aspects: satellites, pseudolites, ground stations, users, control segment – everyone has their own preferences for the actual implementation, but CCSDS could at least define a common way to describe their implementation.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Jim Lux<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>