<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="Title" content="">
<meta name="Keywords" content="">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Courier New";
panose-1:2 7 3 9 2 2 5 2 4 4;}
@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:sans-serif;
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
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:"Times New Roman";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Courier;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:Calibri;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.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:1544487773;
mso-list-type:hybrid;
mso-list-template-ids:1263333958 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{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:1921406111;
mso-list-type:hybrid;
mso-list-template-ids:1194748474 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
{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 bgcolor="white" lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Dear Mattia, et al,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">I was about to send these documents off for CESG review, and was about to say "I've read and approve of them.", when I stumbled over the fact that I had not read the recent version of the
Pink Book nor the new Quasar Catalog procedure. And so I did.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">It may be that you will not thank me for this, but I needed to do it and I think the docs will be better for it. My suggested edits are marked in the attached files. Many of them relate
to alignment with the new Registry Management Policy, but some are quite a bit broader than that. I've tried to concentrate on the major technical and structural issues, not just editorial ones. And I have inserted comments, where
<b><span style="background:yellow;mso-highlight:yellow">bold highlights</span></b> mean it's something that I would really like you to attend to.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Here is a summary of the most important items in my view:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><u><span style="font-size:11.0pt;font-family:Calibri">Pink book on DDOR operations<o:p></o:p></span></u></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-size:11.0pt;font-family:Calibri"><span style="mso-list:Ignore">1.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:Calibri">There is the intent to adopt CSS SM specs in the future, but these are not yet ready. That said, in order to get this book aligned with where those specs are already going I
think that you should be using the same sorts of terminology and identifiers that they are. Failing to do this will mean that your book will potentially be out of sync with theirs for another 5 years. I do not think that is acceptable.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-size:11.0pt;font-family:Calibri"><span style="mso-list:Ignore">2.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:Calibri">One implication of this is to request that you bring the book into line with the Registry Management Policy (RMP) that was created to define registries for all of the organizations,
contact persons, services, sites, spacecraft, etc that occur in CCSDS standards. I want to encourage you to adopt these now since otherwise you just have a set of somewhat arbitrary locally defined names for things that are otherwise already listed in standard
registries. There are notes to this effect in the marked up document.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-size:11.0pt;font-family:Calibri"><span style="mso-list:Ignore">3.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:Calibri">A consequence of this is the recommendation that you change the D-DOR support request parameters to align with these standardized names and identifiers. I note that for many
of these items that you decided to create "short names", of 4 characters in length, for missions, S/C, Quasar, Station, etc. All of the standard registries use longer name fields. If you really want to stick to these short names maybe you should request
to add them to these standard registries as a new SANA registry update.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-size:11.0pt;font-family:Calibri"><span style="mso-list:Ignore">4.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:Calibri">The rules for 6.2 DELTA-DOR SUPPORT REQUEST MESSAGE EXCHANGE SPECIFICATIONS are really weakly specified. They are described, in effect, by examples in sec 6.2.2, sec 6.2.3,
and Annex C. Please see the comments on pg 6-5 in particular.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-size:11.0pt;font-family:Calibri"><span style="mso-list:Ignore">5.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:Calibri">It may be that you want to continue using the existing spec, it does, after, work. But I really wonder if you could hand this spec to anyone else who is not "part of the D-DOR
Club" and have them successfully implement a request tool or a request parser that would work the first time they try it without a lot of hand holding from the "club".<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-size:11.0pt;font-family:Calibri"><span style="mso-list:Ignore">6.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:Calibri">Perhaps you want to consider a Version 1 spec and a version 2 spec? Or to just fix this one, and your tools, to be compliant with an improved version? Now might be a good time
to deal with this because otherwise it is likely to be another 5 years.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><u><span style="font-size:11.0pt;font-family:Calibri">Magenta Book on DDOR quasar catalogue<o:p></o:p></span></u></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo2"><![if !supportLists]><span style="font-size:11.0pt;font-family:Calibri"><span style="mso-list:Ignore">1.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:Calibri">This is a brand new document, so the version management (as in item 6 above) is not an issue, but I do recognize that you have established practices. That said …<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo2"><![if !supportLists]><span style="font-size:11.0pt;font-family:Calibri"><span style="mso-list:Ignore">2.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:Calibri">There are two major questions that come up for me immediately: how are you going to handle the Ka band catalog and how are you going to handle observation and validation of baselines
that do not just include the three DSN stations?<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo2"><![if !supportLists]><span style="font-size:11.0pt;font-family:Calibri"><span style="mso-list:Ignore">3.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:Calibri">The current catalog registers X-band sources. I know that you guys are working on a catalog of Ka-band sources. Is this going to be a separate catalog or just an extension of
this catalog? How does any of this affect the catalog structure, update process, naming, etc?
<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo2"><![if !supportLists]><span style="font-size:11.0pt;font-family:Calibri"><span style="mso-list:Ignore">4.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:Calibri">Do you expect the Ka-Band catalog creation, observations, and update processes to follow what is documented here or is it really different?<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo2"><![if !supportLists]><span style="font-size:11.0pt;font-family:Calibri"><span style="mso-list:Ignore">5.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:Calibri">The current catalog and descriptions seem to require the use of the three DSN stations to establish flux densities for one or more baselines. I understand that this has been
the practice to date, but is it expected to always be the case? What if there are a series of JAXA – ESA north / south baseline observations? Can these other baselines get registered? How?<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo2"><![if !supportLists]><span style="font-size:11.0pt;font-family:Calibri"><span style="mso-list:Ignore">6.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:Calibri">All of the same SANA registry issues identified for the Pink Book in items 2 & 3 above apply here as well. Now is the time to start using the standard registries and to make
sure that you are either using them as they are or asking that they be augmented to meet your needs. The use of submitter (and org) identifiers, station identifiers and location info, etc are examples.
<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo2"><![if !supportLists]><span style="font-size:11.0pt;font-family:Calibri"><span style="mso-list:Ignore">7.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:Calibri">You have been, in effect, assigning unique identifiers to the Quasars in the catalog. By the simple request for creation of a Quasar OID prefix you would turn these into a globally
unique ID that is registered at ISO level. This is also completely extensible and, by treating at as a qualifier on the whole registry does not require modifying the registry (although there may be other reasons for adding this explicitly to the database.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo2"><![if !supportLists]><span style="font-size:11.0pt;font-family:Calibri"><span style="mso-list:Ignore">8.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:Calibri">I do not know if your Ka-band Quasar registry will be just new entries in this registry, or new columns in the registry for Ka-band, or a whole new registry. I also do not know
if it is possible that existing X-band sources will also appear in the Ka-band part. The use of an ISO OID tied to the actual astronomical source is a fine way to disambiguate this. The source gets the OID and this can then tie different entries in different
catalogs together (if that is how you choose to handle this X- / Ka- issue).<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo2"><![if !supportLists]><span style="font-size:11.0pt;font-family:Calibri"><span style="mso-list:Ignore">9.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:Calibri">Your procedure essentially states that the D-DOR WG will always exist. It may not. I recommend that you think about how you would handle updates to the Quasar catalog if the
D-DOR WG is no longer operational. Assuming that these catalogs become valuable community assets maybe some sort of D-DOR or Quasar catalog expert group would be appropriate?<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo2"><![if !supportLists]><span style="font-size:11.0pt;font-family:Calibri"><span style="mso-list:Ignore">10.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:Calibri">You talk about catalog contents and catalog submission, but do not even mention any sort of format specs for this. I think that you could, and should either specify some ASCII
format, or use the SANA expert XML format, or work with SANA to define a JSON format. You could even allow all three, but not having any spec seems dangerous.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo2"><![if !supportLists]><span style="font-size:11.0pt;font-family:Calibri"><span style="mso-list:Ignore">11.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:Calibri">Speaking of ISO OIDs and other SANA registries, you really need to make a "SANA Considerations" section of this document, as required in the SANA policy and the RMP. You have
some of the required parts already, they just need to be better organized.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Please let me know if you need to discuss any of this. We can setup a telecom if need be. Since this is an SEA document, and the SEA is responsible for the SANA, the RMP, and related
matters I think it is essential that these documents be brought into alignment. And, as I mentioned in an earlier note, we already had a request from the CSS area to ensure that this was done.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Thanks, Peter<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><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" style="margin-left:.5in"><b><span style="font-family:Calibri;color:black">From:
</span></b><span style="font-family:Calibri;color:black">Mattia Mercolino <Mattia.Mercolino@esa.int><br>
<b>Date: </b>Tuesday, October 25, 2016 at 2:20 AM<br>
<b>To: </b>Peter Shames <peter.m.shames@jpl.nasa.gov><br>
<b>Cc: </b>Tom Gannett <tomg@aiaa.org>, James Border <james.s.border@jpl.nasa.gov>, Hiroshi Takeuchi <takeuchi@isas.jaxa.jp><br>
<b>Subject: </b>CCSDS - DDOR Operation Pink Book and Quasar catalogue Magenta book - Ready for publication<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
<span style="font-size:10.0pt;font-family:"sans-serif","serif"">Dear Peter,</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif"">As promised during the Plenary last week, we have completed the review and RID disposition of both the books we had to discuss during this Fall meeting, namely:</span>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif"">- The proposed Pink book on DDOR operations</span>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif"">- The proposed Magenta Book on DDOR quasar catalogue update</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif"">Given the mostly editorial kind of the received RIDs we think we are in a position to resolve to go for publication of both books</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif"">I attach here both documents with track changes and in their clean version, for your review and further processing by the Secretariat.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif"">Kind Regards,</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif"">- Pink Book (DDOR operations)</span>
<br>
<br>
<br>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif"">- Magenta Book (DDOR quasar catalogue)</span>
<o:p></o:p></p>
<pre style="margin-left:.5in">this message and any attachments are intended for the use of the addressee or addressees only.<o:p></o:p></pre>
<pre style="margin-left:.5in">The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its<o:p></o:p></pre>
<pre style="margin-left:.5in">content is not permitted.<o:p></o:p></pre>
<pre style="margin-left:.5in">If you received this message in error, please notify the sender and delete it from your system.<o:p></o:p></pre>
<pre style="margin-left:.5in">Emails can be altered and their integrity cannot be guaranteed by the sender.<o:p></o:p></pre>
<pre style="margin-left:.5in"><o:p> </o:p></pre>
<pre style="margin-left:.5in">Please consider the environment before printing this email.<o:p></o:p></pre>
</div>
</body>
</html>