<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body>
<div dir="ltr" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
Thank you David.</div>
<div dir="ltr" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
Regards</div>
<div dir="ltr" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
Mehran</div>
<div id="ms-outlook-mobile-body-separator-line" dir="ltr"><br>
</div>
<div id="ms-outlook-mobile-signature" dir="ltr"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Berry, David S (US 3920) <david.s.berry@jpl.nasa.gov><br>
<b>Sent:</b> Monday, July 21, 2025 12:20:35 AM<br>
<b>To:</b> Mehran Sarkarati <Mehran.Sarkarati@esa.int><br>
<b>Cc:</b> moims-nav-exec@mailman.ccsds.org <moims-nav-exec@mailman.ccsds.org><br>
<b>Subject:</b> CCSDS Nav WG "Simple Report"</font>
<div> </div>
</div>
<style>
<!--
@font-face
{font-family:"Cambria Math"}
@font-face
{font-family:Calibri}
@font-face
{font-family:Aptos}
@font-face
{}
p.x_MsoNormal, li.x_MsoNormal, div.x_MsoNormal
{margin:0in;
font-size:12.0pt;
font-family:"Aptos",sans-serif}
span.x_EmailStyle17
{font-family:"Calibri",sans-serif;
color:windowtext;
font-weight:normal;
font-style:normal}
.x_MsoChpDefault
{}
@page WordSection1
{margin:1.0in 1.0in 1.0in 1.0in}
div.x_WordSection1
{}
-->
</style>
<div lang="EN-US" link="#467886" vlink="#96607D" style="word-wrap:break-word">
<div class="x_WordSection1">
<p class="x_MsoNormal"><span style="font-family:"Calibri",sans-serif; color:black">Mehran:</span></p>
<p class="x_MsoNormal"><span style="font-family:"Calibri",sans-serif; color:black"> </span></p>
<p class="x_MsoNormal"><span style="font-family:"Calibri",sans-serif; color:black">Here is the "simple report" on Nav WG projects in progress as of our 16-Jul-2025 telecon. Overall progress is modest for various reasons (e.g., short time since Spring Meetings,
etc.). There were also several projects that were not discussed in detail at the telecon as we focused primarily on those projects closest to milestone achievements.</span></p>
<p class="x_MsoNormal"><span style="font-family:"Calibri",sans-serif; color:black"> </span></p>
<p class="x_MsoNormal"><span style="font-family:"Calibri",sans-serif; color:black">Regards,</span></p>
<p class="x_MsoNormal"><span style="font-family:"Calibri",sans-serif; color:black">David</span></p>
<p class="x_MsoNormal"><span style="font-family:"Calibri",sans-serif; color:black"> </span></p>
<p class="x_MsoNormal"><span style="font-family:"Calibri",sans-serif; color:black">500.0 Navigation Data - Definitions and Conventions Green Book (V.4): Exploration of a concept related to transitioning Nav Green Book material from a static Green Book to SANA
registries is in progress (much of this material could migrate into the CCSDS Glossary Registries). We reviewed a mock-up of the concept with the SANA Team during the 2025 Spring Meetings and the reception was favorable. We continue to make progress on the
concept, but it was not directly discussed during the most recent telecon.</span></p>
<p class="x_MsoNormal"><span style="font-family:"Calibri",sans-serif; color:black"> </span></p>
<p class="x_MsoNormal"><span style="font-family:"Calibri",sans-serif; color:black">503.0 Tracking Data Message (TDM V.3): </span><span style="font-family:"Calibri",sans-serif">Work on a draft 2.0.3 is in progress and seems to be nearing completion; we anticipate
an updated version imminently. At the Lead Editor’s discretion, we are considering scheduling a “proofreading review” of 2.0.3. We usually do this once the technical changes have settled down, prior to submitting to the Editors for Agency Review polling.</span><span style="font-family:"Times New Roman",serif; color:black"></span></p>
<p class="x_MsoNormal"><span style="font-family:"Calibri",sans-serif; color:black"> </span></p>
<p class="x_MsoNormal"><span style="font-family:"Calibri",sans-serif; color:black">505.0 Navigation Data Messages XML Specification (NDM/XML V.4): Prototype testing is complete, test report is in progress. We will soon present a request for “Approval to Publish”
polling. Not directly discussed during the most recent telecon.</span></p>
<p class="x_MsoNormal"><span style="font-family:"Calibri",sans-serif; color:black"> </span></p>
<p class="x_MsoNormal"><span style="font-family:"Calibri",sans-serif; color:black">507.0 Navigation Events Message (NEM V.1): Further details of the implementation of the XML apparatus for the NEM was presented during Spring Meetings. Progress is significant.
We anticipate a White Book shortly after the Spring Meetings. Not directly discussed during the most recent telecon.</span></p>
<p class="x_MsoNormal"><span style="font-family:"Calibri",sans-serif; color:black"> </span></p>
<p class="x_MsoNormal"><span style="font-family:"Calibri",sans-serif; color:black">507.1 Launch Data Message: Significant steps towards this standard were taken prior to the Spring Meetings, where a skeleton of the technical material was laid out. Not directly
discussed during the most recent telecon.</span></p>
<p class="x_MsoNormal"><span style="font-family:"Calibri",sans-serif; color:black"> </span></p>
<p class="x_MsoNormal"><span style="font-family:"Calibri",sans-serif; color:black">508.0 Conjunction Data Message (CDM V.2): The CDM was one of the key topics in the telecon; it consumed a fair amount of the available time. RIDs have been applied to the Agency
Review Pink Book, and we are preparing for testing. The controversial topics that arose with respect to the TraCSS implementation (as discussed at Spring Meetings) have been resolved. A Test Plan has been produced that includes tests of both existing and new
material. Most members/agencies of the WG have portions to test. XML schema development (required for one of the tests) is nearly complete. Testing should commence in the relatively near future.</span></p>
<p class="x_MsoNormal"><span style="font-family:"Calibri",sans-serif; color:black"> </span></p>
<p class="x_MsoNormal"><span style="font-family:"Calibri",sans-serif; color:black">508.1 Re-Entry Data Message (RDM V.1): This standard was recently re-confirmed. Not directly discussed during the most recent telecon.</span></p>
<p class="x_MsoNormal"><span style="font-family:"Calibri",sans-serif; color:black"> </span></p>
<p class="x_MsoNormal"><span style="font-family:"Calibri",sans-serif; color:black">508.2 Fragmentation Data Message: Significant steps towards this standard were taken prior to the Spring Meetings, where a skeleton of the technical material was laid out. Not
directly discussed during the most recent telecon.</span></p>
<p class="x_MsoNormal"><span style="font-family:"Calibri",sans-serif; color:black"> </span></p>
<p class="x_MsoNormal"><span style="font-family:"Calibri",sans-serif; color:black">5xx.0 ("xx" TBD): Navigation Composite Message: A White Book 1.0 is anticipated prior to the Spring 2025 Meetings.
</span></p>
<p class="x_MsoNormal"><span style="font-family:"Calibri",sans-serif; color:black"> </span></p>
<p class="x_MsoNormal"><span style="font-family:"Calibri",sans-serif; color:black"> </span></p>
<p class="x_MsoNormal"><span style="font-family:"Calibri",sans-serif; color:black">Recently published/reconfirmed standards/other documents with no action necessary: 500.2 Navigation Data Messages Overview Green Book (V.3), 502.0 Orbit Data Message (V.3), 504.0
Attitude Data Messages (V.2), 509.0 Pointing Request Message (V.1).</span></p>
<p class="x_MsoNormal"><span style="font-family:"Calibri",sans-serif; color:black"> </span></p>
<p class="x_MsoNormal"><span style="font-family:"Calibri",sans-serif"> </span></p>
</div>
</div>
This message is intended only for the recipient(s) named above. It may contain proprietary information and/or protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received this e-mail in error, please notify
the sender immediately. ESA applies appropriate organisational measures to protect personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo@esa.int).
</body>
</html>