<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:"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:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Aptos;
panose-1:2 11 0 4 2 2 2 2 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Lucida Sans Unicode";
panose-1:2 11 6 2 3 5 4 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
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;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.zdencodedid
{mso-style-name:zdencodedid;}
span.EmailStyle23
{mso-style-type:personal-reply;
font-family:"Aptos",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:94522883;
mso-list-type:hybrid;
mso-list-template-ids:450535830 67698711 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-number-format:alpha-lower;
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:1792240996;
mso-list-type:hybrid;
mso-list-template-ids:-1624838894 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:1845827152;
mso-list-type:hybrid;
mso-list-template-ids:-63791158 67698705 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l2:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l2:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l2:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2: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" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">Folks,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">I think that this is one of those grey areas (no, I am not advocating another new CCSDS Book Color) where we need to agree on a de facto policy. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">Here is my thinking:<o:p></o:p></span></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level1 lfo1"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">We have a set of formal policies for different book colors, as defined in the Bible and the Pubs manual. Note that I’m
not using the formal doc numbers, but you all know what I mean from the context. This is, clearly, casual usage.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level1 lfo1"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">The Pubs manual says that only Blue and Magenta Books, and other published documents, may be used in the formal reference
list in a CCSDS document (sec 3.4.1.8.a). It does not provide a definitive list of such documents, it only, in Fig B-1, provides
<u>examples</u> of what may be used, including: CCSDS document, ISO Standard, Articles in professional journals, papers in proceedings documents, Internet standards & RFCs, and “random technical documents or websites”.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level1 lfo1"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">I could argue that a WG White Paper, of a certain maturity, could qualify as a “random technical document” and that a
reference to where it might be found, in the CWE, could qualify as a “random web site”.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level1 lfo1"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">I’m not arguing that this class of docs should be treated as formal, Normative, documents.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level1 lfo1"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">Any such White Papers, White Books, Internet Drafts (ID), and other not yet ready to approve and publish documents are
DRAFTs, and ought, IMHO, be treated as such.<o:p></o:p></span></li></ol>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">So then the question is, what can we do with these, and why would we even want to mention them since they are too immature to publish?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">My assertion is this:<o:p></o:p></span></p>
<ol style="margin-top:0in" start="1" type="a">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo2"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">CCSDS publishes a variety of standards and recommended practices. These have well established guidelines as to what they
must contain and the properties that they are to embody. We all (WG, AD, CESG, CTE) have the role(s) of trying to ensure that the published docs are faithful to our established practices and that these documents have been properly vetted.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo2"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">But then, many of our “ISO layer by ISO layer” documents really need to be understood in the context of the “protocol
stack” within which they live. So we often include, within the normative documentation for a single protocol layer N, a non-normative section on required and provided services, exposed at the N+1 and N-1 Service Access Point (SAP) interfaces, and these document
what is expected of the upper and lower protocols in the stack.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo2"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">Often we have a specific upper or lower layer protocol in mind when we write these standards, and this is a practice that
is as old as “ISO BRM” time. That’s where these “layer N” and “SAP” terms were defined.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo2"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">Sometimes the upper layer (or even lower layer) protocol is not yet defined, and we just publish an abstract “SAP”. This
is ok. In fact, it is even recommended so that the designer of the next layer in the stack knows what is expected to be provided (by the lower layer) or offered (to the upper layer).<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo2"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">In the case of some protocol layers we may also identify that other ”on-the-side” capabilities are required, such as authentication,
encryption, or management. These may be optional, implemented “by management”, or “by out of band means”, or “by a separate, as yet TBD, protocol that interfaces on the side”. Security and management are often like this. We “put the hooks in”, sometimes
leave them as optional, and often hang things on these hooks afterwards.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo2"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">Some of these protocols, like Erik’s “</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">CCSDS
902.4-R-1, Cross Support Service Management—Service Package Data Formats (Red Book, Issue 1, September 2022)</span><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">” have mature Red Book drafts, but are still in the process of “becoming”. Some
are still in a White Book / conceptual stage.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo2"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">We can ignore them entirely, or we can acknowledge that they exist, or that they are being defined, or that they are a
gleam in someone’s eye. We need to do this carefully so as not to confuse the readers.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo2"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">Particularly in new areas of “growth” in CCSDS we have a number of these instances. We have them in SIS DTN (routing,
network management, security/identity), we have them in CSS SM (SMURF and friends, FRM), and we have them in MOIMS and SOIS (the Application and Support Layer (ASL) document is a Green Book because so much of what we wanted to document was based on a mix of
Blue, Magenta, and Green material.<o:p></o:p></span></li></ol>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">Enough discourse, I think you get the idea. My recommendation, for what it is worth, is that we adopt this approach:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><u><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">Normative References:</span></u><span style="font-size:11.0pt;font-family:"Aptos",sans-serif"> Follow the CCSDS Guidelines for BB, MB, and other forms, as Tom has requested
and as we have all been doing.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><u><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">Non-normative References:</span></u><span style="font-size:11.0pt;font-family:"Aptos",sans-serif"> Where required or of significant value to the readers, a CCSDS WG may include
such non-normative references as are useful to fill in gaps, or to sketch out where a related set of standards are going. We have published examples of this.<o:p></o:p></span></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l2 level1 lfo3"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">Put these into the Non-normative References section of the document (adhere to the Pubs Doc 3.4.1.8.b)<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l2 level1 lfo3"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">If they are published documents mark them as required in Annex B.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l2 level1 lfo3"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">If they are not yet published, but are valuable for understanding and are sufficiently mature and can be found on-line,
include them in the Non-Normative References section and mark them as [Future], in both the text where they appear and in the Non-Normative Annex.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l2 level1 lfo3"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">If such [Future] references are included, an introductory paragraph must be included in the text documenting that these
somewhat speculative draft standards have been included and describing the cautions that a reader should exercise.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l2 level1 lfo3"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">An example of such text may be found in the SCCS-ARD, 901.1-M-1, Sec 1.3.2 Limit of Applicability. Similar text appears
in the ASL GB, CCSDS 371.0-G-1, Sec 1.3 Rationale.<o:p></o:p></span></li></ol>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">The rationale for such an approach, particularly for complex sets of standards, is that it allows us to “paint a picture” for the readers where some of the pieces are fully colored
in and others are still blank, but where the intended contents are at least sketched out. This helps them to understand what we are doing, and where we are going, but it is clearly not something that they can fully rely upon.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">But this is, in my opinion, a far better approach than to just wave our hands, or leave blank spaces, or, even worse, to neglect to say anything and just leave a hole that someone
may stumble into because we did not bother to say “watch out, construction zone ahead”.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">Or maybe, just maybe, we need to amend the Pubs manual to make this clear.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">Thanks, Peter<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif"><o:p> </o:p></span></p>
<div id="mail-editor-reference-message-container">
<div>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="font-family:"Aptos",sans-serif;color:black">From:
</span></b><span style="font-family:"Aptos",sans-serif;color:black">Barkley, Erik J (US 3970) <erik.j.barkley@jpl.nasa.gov><br>
<b>Date: </b>Monday, October 7, 2024 at 9:40</span><span style="font-family:"Arial",sans-serif;color:black"> </span><span style="font-family:"Aptos",sans-serif;color:black">AM<br>
<b>To: </b>Thomas Gannett <thomas.gannett@tgannett.net>, LStafford@asrcfederal.com <LStafford@asrcfederal.com><br>
<b>Cc: </b>'Smith, Danford S. (GSFC-590.0)[EMERITUS]' <danford.s.smith@nasa.gov>, Shames, Peter M (US 312B) <peter.m.shames@jpl.nasa.gov><br>
<b>Subject: </b>RE: [EXTERNAL] RE: CCSDS 902.6-B<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Tom,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Okay, I will take the issue up with the WG. I can appreciate the "just the facts" approach for calling out normative references. But, the SMURF (902.9), defined partly by
UML class diagrams, does include an abstract class for event sequence. So I would like to discuss excising the book reference with the SMURF book captain and the WG.
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">-Erik</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><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><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Thomas Gannett <thomas.gannett@tgannett.net>
<br>
<b>Sent:</b> Monday, October 7, 2024 09:19<br>
<b>To:</b> Barkley, Erik J (US 3970) <erik.j.barkley@jpl.nasa.gov>; LStafford@asrcfederal.com<br>
<b>Cc:</b> 'Smith, Danford S. (GSFC-590.0)[EMERITUS]' <danford.s.smith@nasa.gov>; Shames, Peter M (US 312B) <peter.m.shames@jpl.nasa.gov><br>
<b>Subject:</b> RE: [EXTERNAL] RE: CCSDS 902.6-B</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Erik:</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Since those books are Magenta and by definition not directly implementable, the bar is substantially lower; and Peter has in recent years at least labeled such
“forthcoming” twinkles in some working group’s eyes as ‘[future]’ (or some such).</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">The alternative approach is to list only existing, available books in normative references lists, but I have only reason and logic to support that argument.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Tom</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<div>
<div style="border:none;border-bottom:solid windowtext 1.0pt;padding:0in 0in 1.0pt 0in">
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
</div>
<p class="MsoNormal"><span style="color:#1F497D">Logothete, L.L.C.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"><a href="mailto:thomas.gannett@tgannett.net">thomas.gannett@tgannett.net</a></span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">+1 443 472 0805</span><o:p></o:p></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif"> Barkley, Erik J (US 3970) [<a href="mailto:erik.j.barkley@jpl.nasa.gov">mailto:erik.j.barkley@jpl.nasa.gov</a>]
<br>
<b>Sent:</b> Monday, October 07, 2024 12:10 PM<br>
<b>To:</b> Thomas Gannett; <a href="mailto:LStafford@asrcfederal.com">LStafford@asrcfederal.com</a><br>
<b>Cc:</b> 'Smith, Danford S. (GSFC-590.0)[EMERITUS]'; Shames, Peter M (US 312B)<br>
<b>Subject:</b> RE: [EXTERNAL] RE: CCSDS 902.6-B</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Tom,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Seems like that precedent was set many moons ago with the initial publication of the CS ARD and ADD whereby several planned recommendations where allowed to be stated as “forthcoming”
in the list of references. Can you suggest an alternate approach? </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">-Erik</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><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><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Thomas Gannett <<a href="mailto:thomas.gannett@tgannett.net">thomas.gannett@tgannett.net</a>>
<br>
<b>Sent:</b> Monday, October 7, 2024 09:00<br>
<b>To:</b> Barkley, Erik J (US 3970) <<a href="mailto:erik.j.barkley@jpl.nasa.gov">erik.j.barkley@jpl.nasa.gov</a>>;
<a href="mailto:LStafford@asrcfederal.com">LStafford@asrcfederal.com</a><br>
<b>Cc:</b> 'Smith, Danford S. (GSFC-590.0)[EMERITUS]' <<a href="mailto:danford.s.smith@nasa.gov">danford.s.smith@nasa.gov</a>>; Shames, Peter M (US 312B) <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>><br>
<b>Subject:</b> RE: [EXTERNAL] RE: CCSDS 902.6-B</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Eric:</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Nevertheless, the document is listed in the normative references of CCSDS 902.4-R-1, Cross Support Service Management—Service Package Data Formats (Red Book,
Issue 1, September 2022), and anyone who might want to base an implementation on that Red Book would require access to all the normative references—thus my longstanding and continually repeated objection to the inclusion of unavailable (and/or imaginary as
the case may be) documents in normative references lists.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Tom</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<div>
<div style="border:none;border-bottom:solid windowtext 1.0pt;padding:0in 0in 1.0pt 0in">
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
</div>
<p class="MsoNormal"><span style="color:#1F497D">Logothete, L.L.C.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"><a href="mailto:thomas.gannett@tgannett.net">thomas.gannett@tgannett.net</a></span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">+1 443 472 0805</span><o:p></o:p></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif"> Barkley, Erik J (US 3970) [<a href="mailto:erik.j.barkley@jpl.nasa.gov">mailto:erik.j.barkley@jpl.nasa.gov</a>]
<br>
<b>Sent:</b> Monday, October 07, 2024 11:52 AM<br>
<b>To:</b> Thomas Gannett; <a href="mailto:LStafford@asrcfederal.com">LStafford@asrcfederal.com</a><br>
<b>Cc:</b> Smith, Danford S. (GSFC-590.0)[EMERITUS]; Shames, Peter M (US 312B)<br>
<b>Subject:</b> RE: [EXTERNAL] RE: CCSDS 902.6-B</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Hi Laura, Tom,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">This (I think) all stems from the MOSA CDE effort (I am copying Dan Smith for cognizance).
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">902.6 (Event Sequence) is a legitimately planned project in the CSS Area. There is a rough draft book that exist, but resources are continually less than forthcoming to
enable the project to formally get underway. I recall having noted that there is no official project yet re 902.6 for the MOSA CDE folks.
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">I suspect the best response is just to say it is a planned standard but does not currently exist.
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">-Erik</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><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><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Thomas Gannett <<a href="mailto:thomas.gannett@tgannett.net">thomas.gannett@tgannett.net</a>>
<br>
<b>Sent:</b> Monday, October 7, 2024 05:31<br>
<b>To:</b> <a href="mailto:LStafford@asrcfederal.com">LStafford@asrcfederal.com</a>; Barkley, Erik J (US 3970) <<a href="mailto:erik.j.barkley@jpl.nasa.gov">erik.j.barkley@jpl.nasa.gov</a>><br>
<b>Subject:</b> [EXTERNAL] RE: CCSDS 902.6-B</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Laura:</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">That is one of the many imaginary CSS books that the CSSM WG insists on including in normative reference lists, despite my many remonstrances over the years.
You should direct all such inquiries to Eric.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Tom</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<div>
<div style="border:none;border-bottom:solid windowtext 1.0pt;padding:0in 0in 1.0pt 0in">
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
</div>
<p class="MsoNormal"><span style="color:#1F497D">Logothete, L.L.C.</span><o:p></o:p></p>
<p class="MsoNormal"><a href="mailto:thomas.gannett@tgannett.net">thomas.gannett@tgannett.net</a><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">+1 443 472 0805</span><o:p></o:p></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif"> Laura Stafford (Support) [</span><a href="mailto:secretariat@mailman.ccsds.org"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">mailto:secretariat@mailman.ccsds.org</span></a><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">]
<br>
<b>Sent:</b> Monday, October 07, 2024 12:01 AM<br>
<b>Cc:</b> Thomas Gannett<br>
<b>Subject:</b> CCSDS 902.6-B</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<div>
<div>
<p class="MsoNormal" style="line-height:13.5pt"><span style="font-size:9.0pt;font-family:"Verdana",sans-serif;color:#2F2F8C">##- Please type your reply above this line -##</span><o:p></o:p></p>
</div>
<p style="line-height:13.5pt"><span style="font-size:9.0pt;font-family:"Verdana",sans-serif;color:#444444">You are registered as a CC on this request (13235). Reply to this email to add a comment to the request.</span><o:p></o:p></p>
<div style="margin-top:18.75pt">
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="100%" style="width:100.0%;border-collapse:collapse">
<tbody>
<tr>
<td width="100%" style="width:100.0%;border:none;border-top:dotted #C5C5C5 1.0pt;padding:11.25pt 0in 11.25pt 0in">
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="100%" style="width:100.0%;border-collapse:collapse">
<tbody>
<tr>
<td width="100%" valign="top" style="width:100.0%;padding:0in 0in 0in 0in">
<p style="margin:0in;line-height:13.5pt"><strong><span style="font-size:11.5pt;font-family:"Lucida Sans Unicode",sans-serif;color:#1B1D1E">Laura Stafford</span></strong><span style="font-size:11.5pt;font-family:"Lucida Sans Unicode",sans-serif;color:#1B1D1E">
(ASRC Federal) </span><o:p></o:p></p>
<p style="margin-bottom:11.25pt;line-height:18.75pt"><span style="font-size:10.0pt;font-family:"Lucida Sans Unicode",sans-serif;color:#BBBBBB">Oct 7, 2024, 12:00</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#BBBBBB"> </span><span style="font-size:10.0pt;font-family:"Lucida Sans Unicode",sans-serif;color:#BBBBBB">AM
EDT </span><o:p></o:p></p>
<div style="margin-top:11.25pt;margin-bottom:11.25pt">
<p class="MsoNormal" style="line-height:16.5pt"><span style="color:#2B2E2F">Tom,<br>
I looked in the CCSDS Project system and in the CCSDS Publications area, and could not find a book number or name per the request. Do you happen to know which book this could be?<br>
Thanks,</span><o:p></o:p></p>
<div>
<p style="margin-bottom:11.25pt;line-height:16.5pt"><span style="font-size:10.0pt;color:#2B2E2F">Laura Stafford<br>
CCSDS IT Tech Support<br>
mailto:</span><span style="font-size:10.0pt"><a href="mailto:lstafford@asrcfederal.com">lstafford@asrcfederal.com</a><span style="color:#2B2E2F"><br>
o: 937-985-4445<br>
7000 Muirkirk Meadows Drive, Beltsville, MD 20705<br>
asrcfederal.com | Purpose Driven. Enduring Commitment.</span></span><o:p></o:p></p>
</div>
</div>
</td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal" style="line-height:13.5pt"><span style="font-size:9.0pt;font-family:"Verdana",sans-serif;color:#444444"> </span><o:p></o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="100%" style="width:100.0%;border-collapse:collapse">
<tbody>
<tr>
<td width="100%" style="width:100.0%;border:none;border-top:dotted #C5C5C5 1.0pt;padding:11.25pt 0in 11.25pt 0in">
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="100%" style="width:100.0%;border-collapse:collapse">
<tbody>
<tr>
<td width="100%" valign="top" style="width:100.0%;padding:0in 0in 0in 0in">
<p style="margin:0in;line-height:13.5pt"><strong><span style="font-size:11.5pt;font-family:"Lucida Sans Unicode",sans-serif;color:#1B1D1E">Temansot</span></strong><span style="font-size:11.5pt;font-family:"Lucida Sans Unicode",sans-serif;color:#1B1D1E">
</span><o:p></o:p></p>
<p style="margin-bottom:11.25pt;line-height:18.75pt"><span style="font-size:10.0pt;font-family:"Lucida Sans Unicode",sans-serif;color:#BBBBBB">Oct 4, 2024, 2:53</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#BBBBBB"> </span><span style="font-size:10.0pt;font-family:"Lucida Sans Unicode",sans-serif;color:#BBBBBB">PM
EDT </span><o:p></o:p></p>
<div style="margin-top:11.25pt;margin-bottom:11.25pt">
<p style="margin-bottom:11.25pt;line-height:16.5pt"><span style="font-size:10.0pt;color:#2B2E2F">Good afternoon,</span><o:p></o:p></p>
<p style="margin-bottom:11.25pt;line-height:16.5pt"><span style="font-size:10.0pt;color:#2B2E2F">I am one of the librarians at the National Reconnaissance Office and I'm<br>
trying to locate a copy of CCSDS 902.6-B Space Link Event Sequence Data<br>
Format. I've searched your website but haven't been able to locate this<br>
document. Can you help me get a copy of this document or tell me where I<br>
might find it?</span><o:p></o:p></p>
<p style="margin-bottom:11.25pt;line-height:16.5pt"><span style="font-size:10.0pt;color:#2B2E2F">Any assistance you could provide would be most appreciated.
</span><o:p></o:p></p>
<p style="margin-bottom:11.25pt;line-height:16.5pt"><span style="font-size:10.0pt;color:#2B2E2F">Tracy Temanson<br>
National Reconnaissance Office - Library<br>
14675 Lee Road<br>
Chantilly, VA 20151<br>
(703) 808-3839<br>
DSN: 898-3839<br>
Email: </span><span style="font-size:10.0pt"><a href="mailto:tracy.temanson@nro.mil">tracy.temanson@nro.mil</a></span><o:p></o:p></p>
</div>
<p style="margin-bottom:11.25pt;line-height:16.5pt"><span style="font-size:10.5pt;font-family:"Lucida Sans Unicode",sans-serif;color:#333333">Attachment(s)<br>
</span><span style="font-size:10.0pt"><a href="https://urldefense.us/v3/__https:/scanss.zendesk.com/attachments/token/Is9b32M677MKrkAOznrorqX2F/?name=smime.p7s__;!!PvBDto6Hs4WbVuu7!JkgxIcToznBNfJEfOXgy3V6kV_ym3nduUPmvzpUd-9fsRNfXwK9cGtIgW1aQAtfVH5oUsrjUJZTFKQ_371eex2uHV1m6efdtroUX2g$"><span style="font-size:10.5pt;font-family:"Lucida Sans Unicode",sans-serif">smime.p7s</span></a></span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
</div>
</div>
<div style="border:none;border-top:solid #EEEEEE 1.0pt;padding:8.0pt 0in 0in 0in;margin-top:7.5pt;margin-bottom:10.5pt">
<p class="MsoNormal" style="line-height:13.5pt"><span style="font-size:9.0pt;font-family:"Verdana",sans-serif;color:#2F2F8C">ASRC Federal | Purpose Driven. Enduring Commitment.
</span><o:p></o:p></p>
</div>
<p class="MsoNormal"><span class="zdencodedid"><span style="color:white">[NVWRK9-ML5V5]</span></span>
<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</body>
</html>