<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi David,<br>
<br>
The "Description and Reference" column has been renamed to "<span>Description</span>"
in the relevant registries on the beta website.<br>
<br>
It will be pushed on the production website in the next
deployment.<br>
</p>
<p><br>
</p>
<pre class="moz-signature" cols="72">--
Best regards,
Julien Bernard
Space Assigned Numbers Authority</pre>
<p><span></span></p>
<div class="moz-cite-prefix">On 2019-10-06 23 h 21, 'Berry, David S
(US 3920)' via Engineering wrote:<br>
</div>
<blockquote type="cite"
cite="mid:3FC652C0-6914-40D9-B2C6-FD80B4098A68@jpl.nasa.gov">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<div class="WordSection1">
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span>Dear SANA Operator:</span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span>I am sending this email to start upon
the 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></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span>In this email I will request action
on item #3b below (highlighted).</span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span>For the following registries, please
change the name of the "Description and Reference" column to
simply "Description". At a later time I will follow up with
material for the existing "References" column.</span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span>All registries are members of the
higher hierarchical level registry
<a
href="https://sanaregistry.org/r/navigation_standard_normative_annexes"
moz-do-not-send="true">https://sanaregistry.org/r/navigation_standard_normative_annexes</a>
. The affected sub-registries are:</span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span><a
href="https://sanaregistry.org/r/orbital_elements"
moz-do-not-send="true">https://sanaregistry.org/r/orbital_elements</a>
</span></p>
<p class="MsoNormal"><span><a
href="https://sanaregistry.org/r/attitude_and_spacecraft_conventions"
moz-do-not-send="true">https://sanaregistry.org/r/attitude_and_spacecraft_conventions</a>
</span></p>
<p class="MsoNormal"><span><a
href="https://sanaregistry.org/r/orbital_covariance_matrix_types"
moz-do-not-send="true">https://sanaregistry.org/r/orbital_covariance_matrix_types</a>
</span></p>
<p class="MsoNormal"><span><a
href="https://sanaregistry.org/r/time_systems"
moz-do-not-send="true">https://sanaregistry.org/r/time_systems</a>
</span></p>
<p class="MsoNormal"><span><a
href="https://sanaregistry.org/r/celestial_body_reference_frames"
moz-do-not-send="true">https://sanaregistry.org/r/celestial_body_reference_frames</a>
</span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span>The other sub-registries either have
no "Description" column, or are already named simply
"Description".</span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span>Regards,</span></p>
<p class="MsoNormal"><span>David</span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span> </span></p>
<div>
<p class="MsoNormal"><b><span>From: </span></b><span>"Shames,
Peter M (US 312B)" <a class="moz-txt-link-rfc2396E" href="mailto:peter.m.shames@jpl.nasa.gov"><peter.m.shames@jpl.nasa.gov></a><br>
<b>Date: </b>Thursday, September 12, 2019 at 3:27 PM<br>
<b>To: </b>"Berry, David S (US 3920)"
<a class="moz-txt-link-rfc2396E" href="mailto:david.s.berry@jpl.nasa.gov"><david.s.berry@jpl.nasa.gov></a>, "SANA Steering Group
(SSG)" <a class="moz-txt-link-rfc2396E" href="mailto:ssg@mailman.ccsds.org"><ssg@mailman.ccsds.org></a>, Space Assigned
Numbers Authority <a class="moz-txt-link-rfc2396E" href="mailto:info@sanaregistry.org"><info@sanaregistry.org></a><br>
<b>Cc: </b><a class="moz-txt-link-rfc2396E" href="mailto:thomas.gannett@tgannett.net">"thomas.gannett@tgannett.net"</a>
<a class="moz-txt-link-rfc2396E" href="mailto:thomas.gannett@tgannett.net"><thomas.gannett@tgannett.net></a>, <a class="moz-txt-link-rfc2396E" href="mailto:Mario.Merri@esa.int">"Mario.Merri@esa.int"</a>
<a class="moz-txt-link-rfc2396E" href="mailto:Mario.Merri@esa.int"><Mario.Merri@esa.int></a><br>
<b>Subject: </b>Re: URGENT: The CCSDS Re-Entry Data
Message Standard</span></p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<p class="MsoNormal">Dear David, SANA Steering Group, and SANA
Operator</p>
<p class="MsoNormal"> </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:</p>
<p class="MsoNormal"> </p>
<ol type="1" start="1">
<li class="MsoListParagraph">Assign the following registries
and their contents "Approved" status. The Nav WG has vetted
this and I see no reason not to approve them:
<ol type="a" start="1">
<li class="MsoListParagraph">Orbit Centers: This WG level
registry is a candidate registry.</li>
<li class="MsoListParagraph">Time Systems: This WG level
registry is a candidate registry.</li>
<li class="MsoListParagraph">Celestial Body Reference
Frames: This WG level registry is a candidate registry.</li>
<li class="MsoListParagraph">Orbit Relative Reference
Frames: This WG level registry was re-created as a
candidate registry.</li>
</ol>
</li>
<li class="MsoListParagraph">After this is done the related
document, the Re-Entry Data Message (RDM) Draft CCSDS
Standard, can proceed through the approval for publication
process.</li>
<li class="MsoListParagraph">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:
<ol type="a" start="1">
<li class="MsoListParagraph">Fix the reference fields in
all of these registries, where appropriate, by moving
text from the "Description and Reference" field to the
"Reference Field"</li>
<li class="MsoListParagraph"><span>Change the name of the
"Description and Reference" column to just
"Description"</span></li>
<li class="MsoListParagraph">Adopt the existing
Organization Role
<span>"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)</li>
<li class="MsoListParagraph">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</li>
</ol>
</li>
</ol>
<p class="MsoNormal"> </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.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Thanks, Peter</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal"><b><span>From:
</span></b><span>David Berry
<a class="moz-txt-link-rfc2396E" href="mailto:david.s.berry@jpl.nasa.gov"><david.s.berry@jpl.nasa.gov></a><br>
<b>Date: </b>Saturday, August 31, 2019 at 9:16 AM<br>
<b>To: </b>Space Assigned Numbers Authority
<a class="moz-txt-link-rfc2396E" href="mailto:info@sanaregistry.org"><info@sanaregistry.org></a><br>
<b>Cc: </b>Tom Gannett
<a class="moz-txt-link-rfc2396E" href="mailto:thomas.gannett@tgannett.net"><thomas.gannett@tgannett.net></a>, Mario Merri
<a class="moz-txt-link-rfc2396E" href="mailto:Mario.Merri@esa.int"><Mario.Merri@esa.int></a>, Peter Shames
<a class="moz-txt-link-rfc2396E" href="mailto:peter.m.shames@jpl.nasa.gov"><peter.m.shames@jpl.nasa.gov></a><br>
<b>Subject: </b>URGENT: The CCSDS Re-Entry Data Message
Standard</span></p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">Dear SANA:</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">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.
</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">The RDM requires that the values for
several keywords be drawn from SANA registries, as follows:</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">1. Organizations registry: This
enterprise level registry is an approved registry; no action
is necessary.</p>
</div>
<div>
<p class="MsoNormal">2. Conjunction Data Message CATALOG_NAME
registry: This Working Group (WG) level registry is an
approved registry; no action is necessary.</p>
</div>
<div>
<p class="MsoNormal">3. Orbit Centers: This WG level registry
is a candidate registry.</p>
</div>
<div>
<p class="MsoNormal">4. Time Systems: This WG level registry
is a candidate registry.</p>
</div>
<div>
<p class="MsoNormal">5. Celestial Body Reference Frames: This
WG level registry is a candidate registry.</p>
</div>
<div>
<p class="MsoNormal">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"
moz-do-not-send="true">info@sanaregistry.org</a>.</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">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".</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">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)).</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">Best Regards, and Thank You so much for
the excellent SANA support to date,</p>
</div>
<div>
<p class="MsoNormal">David Berry</p>
</div>
<div>
<p class="MsoNormal">Chair, CCSDS Navigation Working Group</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
</div>
</blockquote>
<pre class="moz-signature" cols="72">
</pre>
</body>
</html>