<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:"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:Georgia;
panose-1:2 4 5 2 5 4 5 2 3 3;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
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";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
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;}
--></style>
</head>
<body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span class="EmailStyle22"><span style="font-size:11.0pt">Hi Eric,<o:p></o:p></span></span></p>
<p class="MsoNormal"><span class="EmailStyle22"><span style="font-size:11.0pt"><o:p> </o:p></span></span></p>
<p class="MsoNormal"><span class="EmailStyle22"><span style="font-size:11.0pt">I rather agree with your points. In fact, the oid-info people suggested that they pull all the data and host it on their system and I politely suggest that that was not a good idea.
They took some offence and pointed out that it was public data and they could browse it if they wanted to. And then they backed off and just provided that "child link". I think that is just how we want to leave it.<o:p></o:p></span></span></p>
<p class="MsoNormal"><span class="EmailStyle22"><span style="font-size:11.0pt"><o:p> </o:p></span></span></p>
<p class="MsoNormal"><span class="EmailStyle22"><span style="font-size:11.0pt">And yes, the "OID as a sort of GUID" is exactly why we gave everything in these registries an OID. That was part of the original RMP redesign back in 2016. And in the CCSDS 320.0-M-7
update we allowed anyone to register a S/C and get an OID assigned, even if they did not want a SCID assigned. That allows OIDs for all sorts of "space stuff", like Cubesats.<o:p></o:p></span></span></p>
<p class="MsoNormal"><span class="EmailStyle22"><span style="font-size:11.0pt"><o:p> </o:p></span></span></p>
<p class="MsoNormal"><span class="EmailStyle22"><span style="font-size:11.0pt">The other label clean up stuff is a good idea. I suggest that you guys (CSS and SM WG in particular, I guess) create a list of suggested changes and submit them.<o:p></o:p></span></span></p>
<p class="MsoNormal"><span class="EmailStyle22"><span style="font-size:11.0pt"><o:p> </o:p></span></span></p>
<p class="MsoNormal"><span class="EmailStyle22"><span style="font-size:11.0pt">Thanks, Peter<o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><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="color:black">From: </span>
</b><span style="color:black">Erik Barkley <erik.j.barkley@jpl.nasa.gov><br>
<b>Date: </b>Monday, September 21, 2020 at 3:10 PM<br>
<b>To: </b>Peter Shames <peter.m.shames@jpl.nasa.gov>, Space Assigned Numbers Authority <info@sanaregistry.org>, "SANA Steering Group (SSG)" <ssg@mailman.ccsds.org><br>
<b>Cc: </b>CCSDS Engineering Steering Group - CESG Exec <cesg@mailman.ccsds.org><br>
<b>Subject: </b>RE: [EXTERNAL] Re: OID repository: Updated<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">Peter,</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">For what it is worth, the “see child OIDs” link on the oid-info.com when putting in the top-level CCSDS OID is really all that is required.
I don’t think even the top-level decomposition would be the best idea for oid-info.com to track
<u>unless</u> you have some sort of auto-synch mechanism set up from SANA to oid-info.com. And of course that mechanism would have to be agreed to between various parties and tested. I think it’s better off to keep all CCSDS child OIDs as CCSDS affair only
and not get into publishing potentially conflicting/erroneous information.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">Assigning an OID to a spacecraft to function as something like a GUID (Globally Unique Identifier) seems like a good idea to me and already
appears to be in SANA. </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">A note re SANA – putting in a “random” OID to look at its search capability, I tried 1.3.112.4.7.21 and got SOHO. No problem there – but the
information in the record includes a rather odd field name in this: “Expected Launch Date” – I think it’s safe to say that given that SOHO has been flying since it’s launch in December 1995 that it’s launch date is no longer expected. Unless SANA is tracking
what expectations where when the OID was created, assuming launch had yet to occur? Which probably does not have that much value? Perhaps this could just be called “Launch Date” ? This brings me to a general question as to if there is a registry that registers
the metadata and provides the semantics for the various field names/parameters? In this case it might be good to know that this is the date entered at time of record creation and that it’s update depends solely on the record creator updating it (assuming that
is the case). I am not necessarily expecting any “fix” for these kind of lower-level details, but to the extent we might have more automated processes in the future it might be good to start thinking about making the semantics available for reference.
</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">Best regards,</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">-Erik</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"> </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" style="margin-left:.5in"><b><span style="font-size:11.0pt">From:</span></b><span style="font-size:11.0pt"> CESG <cesg-bounces@mailman.ccsds.org>
<b>On Behalf Of </b>Shames, Peter M (US 312B) via CESG<br>
<b>Sent:</b> Tuesday, September 15, 2020 09:56<br>
<b>To:</b> Space Assigned Numbers Authority <info@sanaregistry.org>; SANA Steering Group (SSG) <ssg@mailman.ccsds.org><br>
<b>Cc:</b> CCSDS Engineering Steering Group - CESG Exec <cesg@mailman.ccsds.org><br>
<b>Subject:</b> [CESG] FW: [EXTERNAL] Re: OID repository: Updated</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt">Dear SANA, et al,</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt">A recent question came up relating to the use of the ISO Object Identifiers (OID) that we have built into the SANA revisions. The question was related to the use of SCIDs as a unique
identifier for spacecraft. Since SCIDs are not unique (and never were) my suggestion was that the ISO OIDs that we assigned to spacecraft when they request SCIDs should be used. These are truly globally unique identifiers and persist once assigned. They
can also be assigned by the SANA even if a SCID is not requested. How wide this use will be remains to be seen, but that is a separate topic.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt">When I went looking for an Internet link to the OIDs that we have defined I realized that while CCSDS has an OID assigned [1.3.112.4], and that could be looked up in an on-line OID
registry (<a href="https://urldefense.us/v3/__http:/oid-info.com__;!!PvBDto6Hs4WbVuu7!dxa-i89FLFktcIY_jqqRCVbIujn1KQA0x1vZQ8q5qlq2-h41n5SOsUL_urhey_m060thiL_O7Q$">http://oid-info.com</a>), there was no connection from this CCSDS OID entry to the SANA registries
where these detailed CCSDS OIDs were documented. This was a gap and expecting users to navigate from this OID registry, to the CCSDS website, to the SANA, seemed to be too much to expect.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt">Yesterday I reached out to this OID registry and asked if they could remedy this. They have done that, and in spades. They not only updated the CCSDS registry entry, and added a
link to the SANA registries, but they also included references to the SANA Yellow Books that document the registries. I have attached a snapshot of the current entry in their oid-info.com registry and also one of the SANA page that their link now takes the
user to.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt">As you can see from their reply, we have control over this information and could, if we wished, send them the whole set of OIDs. We could do this, or we could just send them the top
level decomposition, and use that as a driver of users to our site, which is the authoritative source. I see no benefit is sending them the whole OID set, but do see a potential benefit in sending them the first level decomp, which is the names of the sets:
organizations, contacts, spacecraft, SLE, CSS, S/C, Service Site & Aperture, etc. See CCSDS OID screenshot.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt">Wanted you all to be aware of this and to have an opportunity to review, comment, and request changes if any appear to be needed.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt">And BTW, there are also some Wikipedia web pages for OID that I intend to update as well. Might as well get some added visibility for this. It is public and it is, or could be, of
value to others.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt">Cheers, Peter</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt"> </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" style="margin-left:1.0in"><b><span style="color:black">From:
</span></b><span style="color:black">"<a href="mailto:olivier.dubuisson@orange.com">olivier.dubuisson@orange.com</a>" <<a href="mailto:olivier.dubuisson@orange.com">olivier.dubuisson@orange.com</a>><br>
<b>Organization: </b>Orange<br>
<b>Date: </b>Tuesday, September 15, 2020 at 1:36 AM<br>
<b>To: </b>Peter Shames <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>><br>
<b>Subject: </b>[EXTERNAL] Re: OID repository: Question from a user</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:1.0in">
Hi,<br>
<br>
I've updated the description of your OID at <a href="https://urldefense.us/v3/__http:/oid-info.com/get/1.3.112.4__;!!PvBDto6Hs4WbVuu7!a9ORvqdJWwag-cdrWvdRHi4QIUshrQVCXBivv_myv3nY9x6gxxmZ48zT0szYylQTlSAF6Qfk$">
http://oid-info.com/get/1.3.112.4</a><br>
You can <a href="https://urldefense.us/v3/__http:/www.oid-info.com/cgi-bin/manage?oid=1.3.112.4&a=modify__;!!PvBDto6Hs4WbVuu7!a9ORvqdJWwag-cdrWvdRHi4QIUshrQVCXBivv_myv3nY9x6gxxmZ48zT0szYylQTlatOpQTN$">
Modify this OID</a> at any time.<br>
<br>
We don't have a resolution system per se which could be interconnected with other resolution systems. But you can submit a large set of OIDs in an XML file as explained at
<a href="https://urldefense.us/v3/__http:/www.oid-info.com/submit.htm__;!!PvBDto6Hs4WbVuu7!a9ORvqdJWwag-cdrWvdRHi4QIUshrQVCXBivv_myv3nY9x6gxxmZ48zT0szYylQTlSAEbDrX$">
http://www.oid-info.com/submit.htm</a><br>
but we'll implement a tool that will automatically add your OIDs to our OID repository with a hyperlink to their description in the SANA registry. (If you have any issue with this, please reply quickly :-) )<br>
<br>
Thanks,<br>
OID repository admin<o:p></o:p></p>
<div>
<p class="MsoNormal" style="margin-left:1.0in">On 14/09/2020 23:55, Shames, Peter M (US 312B) wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:11.0pt">Dear OID Admin,</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:11.0pt">I represent an organization, CCSDS, ISO OID [1.3.112.4]. We, have an on-line registry called the Space Assigned Numbers Authority (SANA),
<a href="https://urldefense.us/v3/__https:/sanaragistry.org__;!!PvBDto6Hs4WbVuu7!a9ORvqdJWwag-cdrWvdRHi4QIUshrQVCXBivv_myv3nY9x6gxxmZ48zT0szYylQTla2BgFLI$">
https://sanaragistry.org</a>, that will accept all CCSDS full OIDs and resolve them to their proper, lower level, entries.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:11.0pt">How can we connect our registry, which has the ability to do fully qualified OID resolution, to this tool? Can we at least put a URL link to the SANA in the CCSDS "Description"
field that shows up on your pages? Or is there some other a way to reference this on-line registry?</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:11.0pt">Thanks, Peter Shames</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:1.0in">
<span style="font-size:11.0pt;font-family:Helvetica">________________________________________________________<br>
<br>
Peter Shames<br>
CCSDS Systems Engineering Area Director<br>
<br>
Jet Propulsion Laboratory, MS 301-490<br>
California Institute of Technology<br>
Pasadena, CA 91109 USA <br>
<br>
Telephone: +1 818 354-5740, Fax: +1 818 393-6871<br>
<br>
Internet: <a href="Peter.M.Shames@jpl.nasa.gov">Peter.M.Shames@jpl.nasa.gov</a><br>
________________________________________________________</span><o:p></o:p></p>
</blockquote>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<pre style="margin-left:1.0in">_________________________________________________________________________________________________________________________<o:p></o:p></pre>
<pre style="margin-left:1.0in"> <o:p></o:p></pre>
<pre style="margin-left:1.0in">Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc<o:p></o:p></pre>
<pre style="margin-left:1.0in">pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler<o:p></o:p></pre>
<pre style="margin-left:1.0in">a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,<o:p></o:p></pre>
<pre style="margin-left:1.0in">Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.<o:p></o:p></pre>
<pre style="margin-left:1.0in"> <o:p></o:p></pre>
<pre style="margin-left:1.0in">This message and its attachments may contain confidential or privileged information that may be protected by law;<o:p></o:p></pre>
<pre style="margin-left:1.0in">they should not be distributed, used or copied without authorisation.<o:p></o:p></pre>
<pre style="margin-left:1.0in">If you have received this email in error, please notify the sender and delete this message and its attachments.<o:p></o:p></pre>
<pre style="margin-left:1.0in">As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.<o:p></o:p></pre>
<pre style="margin-left:1.0in">Thank you.<o:p></o:p></pre>
</div>
</body>
</html>