<html 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:Courier;
panose-1:2 0 5 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:"Times New Roman \(Body CS\)";
panose-1:2 2 6 3 5 4 5 2 3 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
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.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:Courier;
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:Courier;
color:windowtext;}
.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:404381646;
mso-list-template-ids:1046649836;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1
{mso-list-id:1916092053;
mso-list-type:hybrid;
mso-list-template-ids:-544196548 67698705 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style>
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier">Dear SANA Operator:</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier">I am sending this email to continue work upon Nav WG SANA Registry clean-up actions requested by Peter Shames. I will break this task up into manageable chunks in order to facilitate actions
for me, actions for you, and Peter's auditing function.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier">In this email I will request action on a variant of item #3c below (highlighted).</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier">For the following registry, please add the organization role of "Flight Dynamics Data Provider" (OID
</span><span style="font-size:12.0pt;font-family:Courier">1.3.112.4.5.1.4.3)</span><span style="font-size:12.0pt;font-family:Courier"> to the following entries in the "Organizations" registry:
</span><span style="font-size:12.0pt;font-family:Courier"><o:p></o:p></span></p>
<p><span style="font-size:12.0pt;font-family:Courier">Centre Nation d'Etudes Spatiales OID =
</span><span style="font-size:12.0pt;font-family:Courier">1.3.112.4.1.8<o:p></o:p></span></p>
<p><span style="font-size:12.0pt;font-family:Courier">Deutsche Zentrum für Luft- und Raumfahrt OID = 1.3.112.4.1.11<o:p></o:p></span></p>
<p><span style="font-size:12.0pt;font-family:Courier">European Space Operations Center OID = 1.3.112.4.1.12.3<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier">German Space Operations Center OID = 1.3.112.4.1.11.1<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier">Japan Aerospace Exploration Agency OID = 1.3.112.4.1.14<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier">JPL/Deep Space Network (DSN) OID = 1.3.112.4.1.106<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier">National Aeronautics and Space Administration OID = 1.3.112.4.1.19<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier">NASA Goddard Space Flight Center OID = 1.3.112.4.1.19.1<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier">NASA Jet Propulsion Laboratory OID = 1.3.112.4.1.19.2<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier">NASA Johnson Space Center OID = 1.3.112.4.1.19.4<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier">United Kingdom Space Agency OID = 1.3.112.4.1.17<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier">Space Data Center OID = 1.3.112.4.1.126<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier">There are no doubt more organizations for which this attribute may apply, but these agencies are those that participate in the standards development process as members of the CCSDS Navigation
WG so there is a documented presumption that flight dynamics data is provided. </span>
<o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier">Regards,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier">David</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier"> </span><o:p></o:p></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;color:black">From: </span></b><span style="font-size:12.0pt;color:black">"Shames, Peter M (US 312B)" <peter.m.shames@jpl.nasa.gov><br>
<b>Date: </b>Thursday, September 12, 2019 at 3:27 PM<br>
<b>To: </b>"Berry, David S (US 3920)" <david.s.berry@jpl.nasa.gov>, "SANA Steering Group (SSG)" <ssg@mailman.ccsds.org>, Space Assigned Numbers Authority <info@sanaregistry.org><br>
<b>Cc: </b>"thomas.gannett@tgannett.net" <thomas.gannett@tgannett.net>, "Mario.Merri@esa.int" <Mario.Merri@esa.int><br>
<b>Subject: </b>Re: URGENT: The CCSDS Re-Entry Data Message Standard</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<p class="MsoNormal">Dear David, SANA Steering Group, and SANA Operator<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">I have reviewed this set of concerns with David Berry and reviewed the status of the several registries that are involved in this standard. I am convinced that the Nav WG has done due diligence in creating, vetting, and validating these
several registries. I had voiced some concerns to David about the way that certain of the registry entries are formatted and he has agreed to resolve these in an expeditious fashion. Based on this agreement I have agreed to conditionally approve these registries.
I am sending this note to affirm that and to ask that the following actions be carried out:<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level1 lfo3">Assign the following registries and their contents "Approved" status. The Nav WG has vetted this and I see no reason not to approve them:
<o:p></o:p>
<ol style="margin-top:0in" start="1" type="a">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level2 lfo3">Orbit Centers: This WG level registry is a candidate registry.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level2 lfo3">Time Systems: This WG level registry is a candidate registry.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level2 lfo3">Celestial Body Reference Frames: This WG level registry is a candidate registry.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level2 lfo3">Orbit Relative Reference Frames: This WG level registry was re-created as a candidate registry.<o:p></o:p></li></ol>
</li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level1 lfo3">After this is done the related document, the Re-Entry Data Message (RDM) Draft CCSDS Standard, can proceed through the approval for publication process.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level1 lfo3">David has agreed to do the following clean-up actions on these registries, to be carried out as quickly as possible, but not prior to starting the approval process:
<o:p></o:p>
<ol style="margin-top:0in" start="1" type="a">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level2 lfo3">Fix the reference fields in all of these registries, where appropriate, by moving text from the "Description and Reference" field to the "Reference Field"<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level2 lfo3">Change the name of the "Description and Reference" column to just "Description"<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level2 lfo3"><span style="background:yellow;mso-highlight:yellow">Adopt the existing Organization Role
<span style="color:#0070C0">"Flight Dynamics Data Providers", OID = 1.3.112.4.5.1.4.3</span> , for the Nav organizations that provide this RDM service (and document it)
<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level2 lfo3">Work with at least the members of the Nav WG to get their agencies who do provide these kinds of data to identify as service providers<o:p></o:p></li></ol>
</li></ol>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">If anyone has issues with this please let me know ASAP. Otherwise please move ahead with all due speed to get these registries sorted out so that this doc may get into the Approve for Publication queue.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Thanks, Peter<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-left:.5in"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">David Berry <david.s.berry@jpl.nasa.gov><br>
<b>Date: </b>Saturday, August 31, 2019 at 9:16 AM<br>
<b>To: </b>Space Assigned Numbers Authority <info@sanaregistry.org><br>
<b>Cc: </b>Tom Gannett <thomas.gannett@tgannett.net>, Mario Merri <Mario.Merri@esa.int>, Peter Shames <peter.m.shames@jpl.nasa.gov><br>
<b>Subject: </b>URGENT: The CCSDS Re-Entry Data Message Standard</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Dear SANA:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Yesterday 30-Aug-2019 I received a call from Tom Gannett, CCSDS Lead Editor, regarding the Re-Entry Data Message Draft CCSDS Standard (hereafter, "RDM"). The RDM is at the point of being submitted to the CESG and
CMC for the polls required for approval to publish, however, Tom pointed out an issue that I need to address. Specifically, he stated that he could not prepare the required RDM polls of CESG and CMC at this time.
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">The RDM requires that the values for several keywords be drawn from SANA registries, as follows:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">1. Organizations registry: This enterprise level registry is an approved registry; no action is necessary.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">2. Conjunction Data Message CATALOG_NAME registry: This Working Group (WG) level registry is an approved registry; no action is necessary.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">3. Orbit Centers: This WG level registry is a candidate registry.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">4. Time Systems: This WG level registry is a candidate registry.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">5. Celestial Body Reference Frames: This WG level registry is a candidate registry.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">6. Orbit Relative Reference Frames: This WG level registry was created in the SANA "beta", but has since been overlaid. The material necessary to create the registry has been provided to
<a href="mailto:info@sanaregistry.org">info@sanaregistry.org</a>.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">To date I have assumed that once a Blue Book is approved by the CESG and CMC that any relevant candidate registries would be promoted to "Approved', but according to Tom these polls cannot proceed without the various
registries being approved. The relevant SANA-related Yellow Books (313.0-Y-2, 313.1-Y-1, 313.2-Y-1) do not mention CESG/CMC polling in any significant fashion, but there is a statement in 313.0-Y-2, section 3.10, that "The SANA operator shall publish the approved
registry prior to the final publication of the document that creates it." Given that my prior assumption has apparently been in error, it appears that the RDM cannot be approved for publication without the registries #3, #4, #5, #6 listed above being "approved".<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Accordingly, I would like to request that the registries listed as #3, #4, #5 above be "approved" as soon as possible, and that the registry listed as #6 above be created as soon as possible for review by the Navigation
Working Group and then approved as soon as possible. According to my understanding, this will then allow Tom Gannett to create the requisite CESG and CMC "approval to publish" polls. Our WG has been hoping for publication of the RDM prior to the Fall 2019
CCSDS Meetings, and I believe this may still be possible, though the timing will likely be tight. The WG will certainly do everything in its power to respond immediately to any information or actions required by the SANA Operator in furtherance of this request
(reference 313.2-Y-1 section 2.3(i)).<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Best Regards, and Thank You so much for the excellent SANA support to date,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">David Berry<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Chair, CCSDS Navigation Working Group<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
</div>
</div>
</body>
</html>