<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>Hi Erik,</div>
<div><br>
</div>
<div>I think we are on the same page here, or at least are edging closer. In the proposed mods to the existing registries I showed how we could, in fact, add attributes like "service provider" to an organization entry and I proposed an OID structure that
defines that role. I think we need to have both your SM WG guys, and the SANA guys, vet that and either agree to use it or propose an alternative. My belief is that we need that review and analysis.</div>
<div><br>
</div>
<div>Most of the questions in your added notes seem to be of the "when will it be ready?" form. Since the key registries (orgs, people, spacecraft) already exist I think the answer is "as soon as you guys sign off on it and as soon as the SANA team cranks
the numbers into the right fields. Some (but not all) of those key numbers are OIDs. We have an OID registry. I think we can extend this pretty quickly if/when we can get your crew and the SANA guys to sign off on (or fix) what has been proposed. </div>
<div><br>
</div>
<div>I think we do need to go through a more formal CCSDS doc update and review process, but in the meanwhile we can create some provisional registries that have all of these features. It's sort of up to Marc and co to say whether this can work, if it is viable
based on available resources, and when it might be mocked up. I think for this purpose that even if we just had provisional registries for now we would be in good shape for rolling this out for external review. </div>
<div><br>
</div>
<div>We can make this a long drawn out process or just get on with it. I'd prefer, with some amount of deliberation, to just get on with it. IMHO almost anything that we do after some thought will be better than what we have now.</div>
<div><br>
</div>
<div>As for the RF Asset registry, after thinking about it some more I suggest that we just ask the RF Asset people to add an OID (that we provide) to their registry. We should also ask for access, and I think they should allow it, but that is up to them.
I asked Marc and his team about this yesterday, but have not yet heard back from him. But again, after some thought, I think you CSS (SM & CSTS) guys may well need your own registry where you define the service aspects, as opposed to the physical aspects
(diameter, etc) of these antennas, the ground station sites, and other service sites that do not have GS but still offer services (of different kinds). I proposed a Site and Ground Station registry that I believe covers all of these topics. I'd like to get
your guys to take a look at this and see if it fits your needs. As I understand it a lot of what you are building in the SLE and CSTS OID tree has to do with classification and type. I think that the instances of elements that get tagged with those types
belong in the Site & GS registry, or at least that is how I envision it.</div>
<div><br>
</div>
<div>Is this right or did you guys have something else in mind?</div>
<div><br>
</div>
<div>Regards, Peter</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Erik Barkley <<a href="mailto:Erik.J.Barkley@jpl.nasa.gov">Erik.J.Barkley@jpl.nasa.gov</a>><br>
<span style="font-weight:bold">Date: </span>Tuesday, June 23, 2015 at 5:38 PM<br>
<span style="font-weight:bold">To: </span>Peter Shames <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>>, SMWG <<a href="mailto:smwg@mailman.ccsds.org">smwg@mailman.ccsds.org</a>><br>
<span style="font-weight:bold">Cc: </span>Marc Blanchet <<a href="mailto:marc.blanchet@viagenie.ca">marc.blanchet@viagenie.ca</a>><br>
<span style="font-weight:bold">Subject: </span>RE: Input from SE Area requested: Proposed updates to SoS SANA Registry section<br>
</div>
<div><br>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div xmlns:v="urn:schemas-microsoft-com:vml" 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">
<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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.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;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.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><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Peter,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Thanks for the timely input. Some comments in return are in the attached.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">-Erik<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Shames, Peter M (312B) <br>
<b>Sent:</b> Monday, June 22, 2015 2:48 PM<br>
<b>To:</b> Barkley, Erik J (3970); CCSDS Service Mgmt WG<br>
<b>Cc:</b> Marc Blanchet (<a href="mailto:marc.blanchet@viagenie.ca">marc.blanchet@viagenie.ca</a>)<br>
<b>Subject:</b> Re: Input from SE Area requested: Proposed updates to SoS SANA Registry section<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">Hi Erik, et al,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">Attached please find your text with some mark-ups. See also the attached diagrams showing the proposed structures for organization, person, OID, spacecraft, and Site & Ground Station registries.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">The biggest question for me in looking over your stuff is whether you want to persist in using names (even formal & registered ones) for sites, assets, and spacecraft, or whether you are willing
to shift to using OIDs as unambiguous references? If we do as proposed (and following your lead) adopt OIDs for every major org, person, site, service element, and antenna, then I wonder if you really want to continue using names? I get that names are human
readable, but they are nowhere near as convenient, and unambigous, as an OID. Is it NASA / JPL or just JPL, or maybe JPL – CIT? <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">Or maybe you want both, names for convenience and OIDs to remove any possible ambiguity?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">I am attaching the Site / GS and OID models here. I'll send the whole wad of DRAFT models, with explanation, in a separate note. These are evolving and are not yet fixed. If you guys have changes
or comments (like "THAT won't work") please let me know. I'm also atached a "SCID registry relationships" model that tries to say how these various registries are connected. It's not really correct (yet), but it should give you and idea of what I had in
mind. There would be, of course, a similar "Site and GS relationships" model, maybe I'll sketch that next.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">Thanks, Peter<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<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">Erik Barkley <<a href="mailto:Erik.J.Barkley@jpl.nasa.gov">Erik.J.Barkley@jpl.nasa.gov</a>><br>
<b>Date: </b>Monday, June 22, 2015 at 11:44 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>Cc: </b>SMWG <<a href="mailto:smwg@mailman.ccsds.org">smwg@mailman.ccsds.org</a>>, Marc Blanchet <<a href="mailto:marc.blanchet@viagenie.ca">marc.blanchet@viagenie.ca</a>><br>
<b>Subject: </b>Input from SE Area requested: Proposed updates to SoS SANA Registry section<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<blockquote style="border:none;border-left:solid #B5C4DF 4.5pt;padding:0in 0in 0in 4.0pt;margin-left:3.75pt;margin-right:0in" id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE">
<div>
<div>
<p class="MsoNormal"><span style="color:black">Peter,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Attached please find the SANA registries considerations section extracted from the current scheduling of services blue book candidate with the proposed modifications that I believe are consistent with the newly
emerging SANA registry policy. Colin and I had a teleconference this morning and I believe the changes indicated in the attached represent our consensus as to how to proceed with the registry updates. Track changes has been turned on so you can see what the
differences are. Please note that there are eight editorial notes listed in bracketed italic font which indicate various implications as a result of having updated the verbiage to match the emerging policy. Your comments with regard to those notes that have
an effect on registry definitions or merit consideration from overall registry management will be much appreciated at your earliest convenience.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">-Erik<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
</span>
</body>
</html>