<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: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)">
<!--[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:Wingdings;
panose-1:5 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: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:11.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;
font-size:10.0pt;
font-family:"Courier New";}
tt
{mso-style-priority:99;
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;}
/* List Definitions */
@list l0
{mso-list-id:1778402742;
mso-list-template-ids:457238648;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span class="EmailStyle22">Hi Gippo,<o:p></o:p></span></p>
<p class="MsoNormal"><span class="EmailStyle22"><o:p> </o:p></span></p>
<p class="MsoNormal"><span class="EmailStyle22">I do understand what you are proposing, but the situation has gotten a lot more complicated than I think you may be aware. Some agencies, from the beginning, chose to have their SCID assignments hidden, so
what is really an allocated number appears empty. Other agencies are choosing to do that now, or to not even register their SCIDs even though they are using CCSDS protocols.<o:p></o:p></span></p>
<p class="MsoNormal"><span class="EmailStyle22"><o:p> </o:p></span></p>
<p class="MsoNormal"><span class="EmailStyle22">As a result of this, instead of being able to use a straightforward algorithm to search for and assign SCIDs the SANA staff have to waste their time going on “Easter Egg Hunts”. This is really inefficient and
I fail to understand why it is even of value.<o:p></o:p></span></p>
<p class="MsoNormal"><span class="EmailStyle22"><o:p> </o:p></span></p>
<p class="MsoNormal"><span class="EmailStyle22">Perhaps I am not understanding something, but what is the value in picking a specific SCID? Do agencies really have hardware and software that is “wired” to one SCID number that cannot be changed?<o:p></o:p></span></p>
<p class="MsoNormal"><span class="EmailStyle22"><o:p> </o:p></span></p>
<p class="MsoNormal"><span class="EmailStyle22">Thanks, Peter<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">Gian Paolo Calzolari <Gian.Paolo.Calzolari@esa.int><br>
<b>Date: </b>Tuesday, June 15, 2021 at 2:03 AM<br>
<b>To: </b>Peter Shames <peter.m.shames@jpl.nasa.gov><br>
<b>Cc: </b>CCSDS Engineering Steering Group - CESG Exec <cesg@mailman.ccsds.org>, Marc Blanchet <marc.blanchet@viagenie.ca>, "SANA Steering Group (SSG)" <ssg@mailman.ccsds.org><br>
<b>Subject: </b>[EXTERNAL] Re: [CESG] Requesting SSG "consensus": QSCID Question<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.0pt;font-family:"Arial",sans-serif">Peter,</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"> I concur with Marc analysis and with your considerations but I wonder whether a softer approach could be used.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">I mean that - since the SCID values are all public at
</span><a href="https://urldefense.us/v3/__https:/sanaregistry.org/r/spacecraftid/__;!!PvBDto6Hs4WbVuu7!a8DH8ZwEglT8_6NMWb8wINgI3d3v6aPLrXo8dkcP7ZbUOP8GJY9LxVuIesuMuP60fjxZosO0$"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">https://sanaregistry.org/r/spacecraftid/</span></a><span style="font-size:10.0pt;font-family:"Arial",sans-serif">
- an Agency has all the means to check if a value is free or assigned. (Some remarks below)</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Therefore, one chance could be leaving the “pick your own number” option but requiring that the research for availability be performed and included in the request by the requester,</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">This could be a way to still be friendly to requester but avoiding a "interpretable" task to NASA.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Last, but not least I think CMC shall be polled on this question as the task is mainly on Agency Delegates or persons acting on behalf of their Agency Delegate.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">My cent,,,</span> <br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Gippo</span> <br>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">PS with respect to the specific request I first looked for decimal 68 = Hex 44 and I find it assigned to NILESAT-2 for both TM and TC. Then I also saw that 116 = Hex 74 is assigned to MSL98-Flight
and 229 = E5 Hex is assigned to STELLATsim.</span> <br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">This is just to say that the requester would have been able to know that his request
</span> “pick your own number” was a mission impossible. <br>
In case those values were free, he could have stated this in his analysis justifying the ticked “pick your own number” option.
<br>
<br>
<br>
<br>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">From: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"Shames, Peter M\(US 312B\) via CESG" <cesg@mailman.ccsds.org></span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">To: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"SANA Steering Group (SSG)" <ssg@mailman.ccsds.org></span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Cc: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"Marc Blanchet" <marc.blanchet@viagenie.ca>, "CCSDS Engineering Steering Group - CESG Exec" <cesg@mailman.ccsds.org></span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Date: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">15-06-21 01:52</span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Subject: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">[CESG] Requesting SSG "consensus": QSCID Question</span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Sent by: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"CESG" <cesg-bounces@mailman.ccsds.org></span>
<o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="0" width="100%" noshade="" style="color:#A0A0A0" align="center">
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<p style="margin:0in">Hi Marc,<o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in">I completely sympathize with your situation. I would agree that these kinds of requests are really pretty unreasonable since the QSCID ought to be a simple ID in a table in any reasonably designed software system.<o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in">I am also concerned, when they say “TLM and TC” that they are thinking “old school SCID” and not necessarily realizing that there are separate QSCIDs for different protocols. Do they really mean TLM, i.e. TM protocol, and not AOS?<o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in">Unless someone on the SSG strongly objects I am going to suggest that we remove the “pick your own number” option from the SANA SCID website and tell them “You get one of the available numbers, as assigned by our algorithm.”<o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in">In accordance with CCSDS Consensus processes "Can anyone not live with this choice? “<o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in">Thanks, Peter<o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in"><b><span style="font-size:12.0pt">From: </span></b><span style="font-size:12.0pt">SSG <ssg-bounces@mailman.ccsds.org> on behalf of Marc Blanchet <marc.blanchet@viagenie.ca><b><br>
Date: </b>Monday, June 14, 2021 at 2:07 PM<b><br>
To: </b>"SANA Steering Group (SSG)" <ssg@mailman.ccsds.org><b><br>
Subject: </b>[EXTERNAL] [SSG] Fwd: QSCID Question</span><o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in">Hello, <o:p></o:p></p>
<p style="margin:0in"> We have work hard to fulfill those in the past., but with all the multiple overlaps over multiple bands, these kind of requests for «specific assignments » are becoming complicated to fulfill, are time consuming and potentially error
prone. We would like at some point that we have the right to just say: « sorry, we can’t fulfill specific assignments ». We would like to have guidance from the SSG about these.
<o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in">Marc.<o:p></o:p></p>
<p style="margin:0in"><o:p> </o:p></p>
<p style="margin:0in">Début du message transféré :<o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in"><b>De: </b>"'Blalock, John R. (GSFC-459.0)[PERATON, INC]' via Engineering" <<a href="mailto:eng@viagenie.ca">eng@viagenie.ca</a>><o:p></o:p></p>
<p style="margin:0in"><b>Objet: QSCID Question</b><o:p></o:p></p>
<p style="margin:0in"><b>Date: </b>14 juin 2021 à 10:29:04 HAE<o:p></o:p></p>
<p style="margin:0in"><b>À: </b>SANA <<a href="mailto:info@sanaregistry.org">info@sanaregistry.org</a>><o:p></o:p></p>
<p style="margin:0in"><b>Cc: </b>"Zaki, Bashaer E (GSFC-450.0)[Internet Consulting Services, LLC]" <<a href="mailto:bashaer.e.zaki@nasa.gov">bashaer.e.zaki@nasa.gov</a>><o:p></o:p></p>
<p style="margin:0in"><b>Répondre à: </b>"Blalock, John R. (GSFC-459.0)[PERATON, INC]" <<a href="mailto:john.r.blalock@nasa.gov">john.r.blalock@nasa.gov</a>><o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in">Hello,<o:p></o:p></p>
<p style="margin:0in">One of our missions would like to know if some V1 QSCIDs are available for TLM and TC in the X-band to match their other SCIDs. Are any of the QSCIDs below available for us to request? (all in decimal)<o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<ul type="disc">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
116 <o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
229 <o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
068<o:p></o:p></li></ul>
<p class="MsoNormal"> <o:p></o:p></p>
<p style="margin:0in">Regards,<o:p></o:p></p>
<p style="margin:0in">John Blalock Jr.<o:p></o:p></p>
<p style="margin:0in"> <tt><span style="font-size:10.0pt">_______________________________________________</span></tt><span style="font-size:10.0pt;font-family:"Courier New""><br>
<tt>CESG mailing list</tt><br>
<tt>CESG@mailman.ccsds.org</tt><br>
</span><a href="https://urldefense.us/v3/__https:/mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg__;!!PvBDto6Hs4WbVuu7!a8DH8ZwEglT8_6NMWb8wINgI3d3v6aPLrXo8dkcP7ZbUOP8GJY9LxVuIesuMuP60fp0AQwpU$"><tt><span style="font-size:10.0pt">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg</span></tt></a><o:p></o:p></p>
<pre>This message is intended only for the recipient(s) named above. It may contain proprietary information and/or<o:p></o:p></pre>
<pre>protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received<o:p></o:p></pre>
<pre>this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect<o:p></o:p></pre>
<pre>personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo@esa.int).<o:p></o:p></pre>
</div>
</body>
</html>