<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" 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=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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:Tahoma;
panose-1:2 11 6 4 3 5 4 4 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:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle20
{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]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#376092;mso-style-textfill-fill-color:#376092;mso-style-textfill-fill-alpha:100.0%">Good point, Peter. I’ll back off on my suggestion that we need a common term across all 3 documents, and just leave it as being that
the </span><span style="color:#376092;mso-style-textfill-fill-color:#376092;mso-style-textfill-fill-alpha:100.0%;letter-spacing:-.3pt">Service Request/Service Package book has to somehow address the assignment of the facility identifier for purposes of identification
of CSTS service instances. Erik is putting together an “Inter-Recommendation Tracking” spreadsheet that could be used to record the “lien” on the Service Request/Service Package book.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#376092;mso-style-textfill-fill-color:#376092;mso-style-textfill-fill-alpha:100.0%;letter-spacing:-.3pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#376092;mso-style-textfill-fill-color:#376092;mso-style-textfill-fill-alpha:100.0%;letter-spacing:-.3pt">Regarding SANA registration – I agree. Colin is already looking into standard, registered station IDs for the Simple
Schedule book; a generalization to various types of facilities is a reasonable extrapolation.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#376092;mso-style-textfill-fill-color:#376092;mso-style-textfill-fill-alpha:100.0%;letter-spacing:-.3pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#376092;mso-style-textfill-fill-color:#376092;mso-style-textfill-fill-alpha:100.0%;letter-spacing:-.3pt">John</span><span style="color:#376092;mso-style-textfill-fill-color:#376092;mso-style-textfill-fill-alpha:100.0%"><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 #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""> Shames, Peter M (312B) [mailto:peter.m.shames@jpl.nasa.gov]
<br>
<b>Sent:</b> Wednesday, October 29, 2014 3:03 PM<br>
<b>To:</b> John Pietras; CCSDS_CSTSWG (css-csts@mailman.ccsds.org); CCSDS SMWG ML (smwg@mailman.ccsds.org)<br>
<b>Subject:</b> Re: [Css-csts] Facility Identifier (or StationRef?)<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">Strikes me that there may be other sorts of facilities thatn "stations", such as network control centers, mission control centers, and the like. Maybe there needs to be some sort of taxonomy and
also a SANA registry of these items. I think we also need to associate those facilities with the organization that owns and operates them. I think that Nav WG has a similar issue and that some sort of common, global, registry(s) need to be defined.<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">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">John Pietras <<a href="mailto:john.pietras@gst.com">john.pietras@gst.com</a>><br>
<b>Date: </b>Wednesday, October 29, 2014 11:08 AM<br>
<b>To: </b>CSTS-WG <<a href="mailto:css-csts@mailman.ccsds.org">css-csts@mailman.ccsds.org</a>>, SMWG <<a href="mailto:smwg@mailman.ccsds.org">smwg@mailman.ccsds.org</a>><br>
<b>Subject: </b>[Css-csts] Facility Identifier (or StationRef?)<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">CSTSWG and CSSMWG colleagues ---<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">The CSTS SFW defines (in section 3.4.2.2.7.2) the service-instance-identifier as comprising 4 components, one of which is “<span style="letter-spacing:-.3pt">the facility identifier as defined by the service package
</span></span><span style="color:black;letter-spacing:-.3pt;mso-fareast-language:FR">specified</span><span style="color:black;letter-spacing:-.3pt"> in references
</span><span style="color:black;mso-fareast-language:JA">[</span><span style="color:black">2]<span style="letter-spacing:-.3pt"> and
</span>[1]<span style="letter-spacing:-.3pt">”, where reference 1 is the SC<i>CS SM Service Request and Service Package Data Formats</i> Recommended Standard that the CSSMWG is currently developing.
</span><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black;letter-spacing:-.3pt"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black;letter-spacing:-.3pt">As far as I know, we in the CSSMWG have not progressed the content of the book to specifically identify a “facility identifier”. However, the
<i>Simple Schedule Format</i> book that is working its way through CESG and CMC approval for Red-1 release
<i>does</i> define a s<b>tationRef</b> parameter (defined as “</span><span style="color:black">The ground station or relay satellite to which the scheduled activity applies”)
<span style="letter-spacing:-.3pt"> that appears to contain the same type of identification intended by the CSTS SFW’s facility identifier. So in SM we have adopted the concept of associating the delivery of services with a specific facility or station. We
in the CSSMWG need to make sure that this identification is also present in the Service Package format (schema) defined in the SC<i>CS SM Service Request and Service Package Data Formats</i> Blue Book.
</span><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black;letter-spacing:-.3pt"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black;letter-spacing:-.3pt">Assuming that will happen, I recommend that we adopt a common term across all three books (CSTS SFW, Simple Schedule, and Service Request/Service Package). As noted above, CSTS SFW uses ‘facility
identifier” and the Simple Schedule book uses “stationRef”. I personally don’t have any preference for one or the other, just a belief that a single name should be used for simplicity and clarity.
</span><span style="color:black"><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">John<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
</div>
</blockquote>
<div>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-size:13.5pt;color:black;background:white">
<hr size="2" width="100%" align="center">
</span></div>
<p class="MsoNormal"><span style="font-size:13.5pt;color:black;background:white"><br>
<a href="https://filter.gst.com/canit/b.php?i=01N97bAr1&m=b1854bc8115e&c=s" target="canit_note">Spam</a><br>
<a href="https://filter.gst.com/canit/b.php?i=01N97bAr1&m=b1854bc8115e&c=n" target="canit_note">Not spam</a><br>
<a href="https://filter.gst.com/canit/b.php?i=01N97bAr1&m=b1854bc8115e&c=f" target="canit_note">Forget previous vote</a></span><span style="font-size:10.5pt;color:black"><o:p></o:p></span></p>
</div>
</div>
</body>
</html>