<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:Helvetica;
panose-1:0 0 0 0 0 0 0 0 0 0;}
@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:12.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
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:12.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-reply;
font-family:Courier;
color:windowtext;}
p.p1, li.p1, div.p1
{mso-style-name:p1;
margin:0in;
margin-bottom:.0001pt;
font-size:22.5pt;
font-family:Helvetica;}
.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:36659727;
mso-list-type:hybrid;
mso-list-template-ids:-2081109580 67698705 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1
{mso-list-id:243537967;
mso-list-type:hybrid;
mso-list-template-ids:1184793510 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;}
@list l2
{mso-list-id:445545411;
mso-list-template-ids:1640001652;}
@list l3
{mso-list-id:1352956808;
mso-list-template-ids:-382849178;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-family:Courier">Peter:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:Courier"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:Courier">The "Navigation Data - Definitions and Conventions" is well understood to be non-normative. It doesn't "define" any time systems, just provides descriptions of time systems that have been defined by other
authoritative entities. This document is cited by virtually all Navigation WG standards as an INFORMATIVE reference.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:Courier"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:Courier">The Navigation WG itself does not (or has not) dealt with issues of time correlation and/or time synchronization as a CCSDS entity. It may be the case that this function resides in flight dynamics in some
of the CCSDS Agencies, but I don't know. Of course we do depend upon timetag accuracy, as do many other space mission functions, but to my knowledge the timetag functions are handled by either tracking networks or spacecraft flight teams or both.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:Courier"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:Courier">The most current information related to Time Systems provided by the Navigation WG (and targeted for use as values for keywords in Navigation WG standards) is now ON the SANA at
<a href="https://sanaregistry.org/r/time_systems?sort=name">https://sanaregistry.org/r/time_systems?sort=name</a> . At present this is a "candidate" registry, though we hope to have it "approved" in the not too distant future. If the names and descriptions
are technically incorrect, we would of course like to correct that, but the material has been reviewed by knowledgeable WG members and I believe it to be substantially correct. The only time related TERMS we are defining are the NAMES of the time systems,
and a description of the time system. Based on my understanding of the CCSDS SANA Registry Management Policy, I believe that the SANA is meant to be a normative source of "assignments" in instantiations of CCSDS Standards. So for example, there are many "time
related terms" in the CCSDS Terms Registry, but very few of them are in the Nav WG Time Systems registry. The term in the CCSDS Terms Registry would in general NOT be acceptable in an instantiation of one of the Nav WG standards.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:Courier"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:Courier">Regarding your heartburn with respect to the Nav WG intent for the CCSDS "Navigation Data - Definitions and Conventions", Green Book, we have indeed been discussing major revisions to the document, with
the POSSIBLE future step of eliminating it. The first step has been to ensure that the terms in that document's glossary are present and correct in the SANA
<a href="https://sanaregistry.org/r/terms">https://sanaregistry.org/r/terms</a> registry, after which time we plan to remove the glossary from the document and refer to the SANA registry (this avoids duplication, inconsistency, etc.). The terms to which I refer
are not "invented on the fly", but rather are terms used in common spacecraft flight dynamics activities. Also, please note that the CCSDS "Navigation Data - Definitions and Conventions" was first published in September 2004, and the "realized SANA" and the
Magenta Book paradigm came along substantially later; if the Green Book needs to be changed, that can be discussed, but the existence and contents of this Green Book have not been an issue through 3 editions. And again, our
<a href="https://sanaregistry.org/r/time_systems?sort=name">https://sanaregistry.org/r/time_systems?sort=name</a> registry doesn't define TERMS, it specifies a set of VALUES that are acceptable for various keywords in instantiations of our standards that relate
to the time system used.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:Courier"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:Courier">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:Courier">David<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:Courier"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:Courier"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:Courier"><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="color:black">From: </span></b><span style="color:black">"Shames, Peter M (312B)" <Peter.M.Shames@jpl.nasa.gov><br>
<b>Date: </b>Tuesday, February 19, 2019 at 10:13 AM<br>
<b>To: </b>"Berry, David S (3920)" <David.S.Berry@jpl.nasa.gov>, "Wilmot, Jonathan J. (GSFC-5820)" <jonathan.j.wilmot@nasa.gov><br>
<b>Cc: </b>Ramon Krosley <r.krosley@andropogon.org>, "Gramling, Cheryl J. (GSFC-5950)" <cheryl.j.gramling@nasa.gov>, Jon Hamkins via SEA-TIME <sea-time@mailman.ccsds.org><br>
<b>Subject: </b>A request for coordination from the SEA Time BoF<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt">Dear David and Jonathan,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">During today's SEA Time BoF telecon we were working through the set of definitions that we need for time, clock, correlation, synchronization, etc, all in the aim of providing time management services. In
the process of defining these terms we have been reviewing the existing definitions in the SANA as well as definitions from authoritative normative external sources such as the BIPM and NIST.
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">We have, in the course of exploring what has been defined in the SANA, stumbled across definitions that came from various MOIMS Navigation WG (Navigation Data—Definitions and Conventions. Green Book. Issue
3. May 2010, CCSDS 500.0-G-3) and SOIS App WGs (Spacecraft Onboard Interface Services—Time Access Service. Silver Book. Issue 1. January 2011, CCSDS 872.0-M-1-S), as well as those in the SEA Time Code document, (Time Code Formats. Blue Book. Issue 4. November
2010, CCSDS 301.0-B-4). Here is where things start to get interesting and why I am reaching out to you.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">As best I can tell these three documents are the primary sources of definitions for terms related to time. They are what comes up in the CCSDS Terms registry. But here's the issue:</span><o:p></o:p></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo3"><span style="font-size:11.0pt">The Time Code format document does not itself specify normative definitions. All of the terms it uses come from other sources like BIPM and NIST. So
far so good.</span><o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo3"><span style="font-size:11.0pt">The SOIS Time Access service is now a Silver Book, but we understand (from Ray Krosley) that it is under consideration to be brought back to life, possibly
in some new form. I would guess that it would be well served by the Time Code Format definitions, plus any new ones for time correlation and synchronization that the SEA Time WG standardizes. TBD.</span><o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo3"><span style="font-size:11.0pt">The Nav Definitions and Conventions is a Green Book, which, in normal CCSDS parlance means that it is by definition non-normative. That said, this document
contains a broad range of terms related to navigation, including some related to time, clocks, etc. We all know that navigation references time as well as position reference frames. And we know that this is used as a reference by other Nav WG docs.</span><o:p></o:p></li></ol>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">We need to make sure that these different uses of the set of terms related to time, correlation, synchronization are aligned, and to the extent possible, identical. David, I heard from Cheryl Gramling today
that the Nav WG has been reviewing what is in the SANA and proposes to make changes. The fact that you are doing that is excellent and aligned with CCSDS policies, but I need to ask that we find a way to coordinate with the Time BoF. I know that the BoF
is not yet a formal entity, it will be shortly (I hope). The regular crew of 8-11 people have an excellent background in time and time keeping, so I want to suggest that when terms relating to time are adopted that this group be asked to concur, if not to
take the lead. </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">To that end would you please send your new list of terms to me for distribution to the Time BoF? I want to make sure that we concur, or if not, to provide you with feedback about any issues we see.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">On a related topic, Cheryl said that you have in mind defining or updating terms in the SANA and then eliminating the existing Green Book. She may have mis-stated your intention, but I have to say that with
my SEA AD CESG "hat" on that gives me major heartburn for a few reasons:</span><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 lfo6"><span style="font-size:11.0pt">The CCSDS process and publication procedures (CCSDS A02.1-Y-4) say that formal terms are to be included in a normative section of a normative document,
whether that is a Blue Book or a Magenta Book (both are normative) and that common terms shall be adopted (Sec A11).</span><o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level1 lfo6"><span style="font-size:11.0pt">The CCSDS process document says that "Magenta Books may … define means for applying or using standards or for documenting reference architectures and
other formal specifications, or … document reference models or reference architectures to assist in the design, use, description, or selection of one or more standards." Since you intend this document to be used across other Nav WG documents I assert that
it must be a Magenta Book, and not a Green Book. This is in line with a recent CESG discussion on a similar SLE Reference Architecture Blue Book that is now to be re-issued as a Magenta Book for consistency with CCSDS guidelines.</span><o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level1 lfo6"><span style="font-size:11.0pt">The Registry Management Policy (CCSDS 313.1-Y-1) in Sec 3.4.4 says that Glossary items must be derived from published documents and that terminology
from authoritative sources is to be preferred. There is no part of any CCSDS procedures that permits SANA Glossary terms to be invented on the fly without being sourced in a published document.</span><o:p></o:p></li></ol>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Bottom line, let's figure out how to arrive at a set of terms that meets the needs of these three WG, and thereby the needs of other WG that need to reference, but not uniquely define, these terms. Ok?</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Thanks, Peter</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
</div>
</body>
</html>