<span style=" font-size:10pt;font-family:sans-serif">Actually I meant:</span>
<br><span style=" font-size:10pt;font-family:sans-serif"><b>This could
be a way to still be friendly to requester but avoiding a "interpretable"
task to </b></span><span style=" font-size:10pt;color:red;font-family:sans-serif"><b>SANA</b></span><span style=" font-size:10pt;font-family:sans-serif"><b>.</b></span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Sorry</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Gippo</span>
<br>
<br>
<br>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">From:
</span><span style=" font-size:9pt;font-family:sans-serif">Gian
Paolo Calzolari/esoc/ESA</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">To:
</span><span style=" font-size:9pt;font-family:sans-serif">"Shames,
Peter M\(US 312B\)" <peter.m.shames@jpl.nasa.gov></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Cc:
</span><span style=" font-size:9pt;font-family:sans-serif">"CCSDS
Engineering Steering Group - CESG Exec" <cesg@mailman.ccsds.org>,
"Marc Blanchet" <marc.blanchet@viagenie.ca>, "SANA
Steering Group (SSG)" <ssg@mailman.ccsds.org></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Date:
</span><span style=" font-size:9pt;font-family:sans-serif">15-06-21
11:03</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Subject:
</span><span style=" font-size:9pt;font-family:sans-serif">Re:
[CESG] Requesting SSG "consensus": QSCID Question</span>
<br>
<hr noshade>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Peter,</span>
<br><span style=" font-size:10pt;font-family: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:10pt;font-family:sans-serif">I mean that -
since the SCID values are all public at </span><a href=https://sanaregistry.org/r/spacecraftid/><span style=" font-size:10pt;color:blue;font-family:sans-serif">https://sanaregistry.org/r/spacecraftid/</span></a><span style=" font-size:10pt;font-family: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:10pt;font-family: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:10pt;font-family: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:10pt;font-family: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:10pt;font-family:sans-serif">My cent,,,</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Gippo</span>
<br>
<br>
<br><span style=" font-size:10pt;font-family: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:10pt;font-family:sans-serif">This is just to
say that the requester would have been able to know that his request </span><span style=" font-size:11pt;font-family:Calibri"> “pick
your own number” was a mission impossible.</span>
<br><span style=" font-size:11pt;font-family:Calibri">In case those values
were free, he could have stated this in his analysis justifying the ticked
“pick your own number” option.</span>
<br>
<br>
<br>
<br>
<br>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">From:
</span><span style=" font-size:9pt;font-family:sans-serif">"Shames,
Peter M\(US 312B\) via CESG" <cesg@mailman.ccsds.org></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">To:
</span><span style=" font-size:9pt;font-family:sans-serif">"SANA
Steering Group (SSG)" <ssg@mailman.ccsds.org></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Cc:
</span><span style=" font-size:9pt;font-family:sans-serif">"Marc
Blanchet" <marc.blanchet@viagenie.ca>, "CCSDS Engineering
Steering Group - CESG Exec" <cesg@mailman.ccsds.org></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Date:
</span><span style=" font-size:9pt;font-family:sans-serif">15-06-21
01:52</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Subject:
</span><span style=" font-size:9pt;font-family:sans-serif">[CESG]
Requesting SSG "consensus": QSCID Question</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Sent
by: </span><span style=" font-size:9pt;font-family:sans-serif">"CESG"
<cesg-bounces@mailman.ccsds.org></span>
<br>
<hr noshade>
<br>
<br>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Hi
Marc,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">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.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">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?</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">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.”</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">In
accordance with CCSDS Consensus processes "Can anyone not live with
this choice? “</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Thanks,
Peter</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Calibri"><b>From:
</b>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></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Hello,
</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> 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. </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Marc.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"><br>
</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Début
du message transféré :</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt"><b>De:
</b>"'Blalock, John R. (GSFC-459.0)[PERATON, INC]' via Engineering"
<</span><a href=mailto:eng@viagenie.ca><span style=" font-size:11pt;color:blue"><u>eng@viagenie.ca</u></span></a><span style=" font-size:11pt">></span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt"><b>Objet:
QSCID Question</b></span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt"><b>Date:
</b>14 juin 2021 à 10:29:04 HAE</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt"><b>À:
</b>SANA <</span><a href=mailto:info@sanaregistry.org><span style=" font-size:11pt;color:blue"><u>info@sanaregistry.org</u></span></a><span style=" font-size:11pt">></span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt"><b>Cc:
</b>"Zaki, Bashaer E (GSFC-450.0)[Internet Consulting Services, LLC]"
<</span><a href=mailto:bashaer.e.zaki@nasa.gov><span style=" font-size:11pt;color:blue"><u>bashaer.e.zaki@nasa.gov</u></span></a><span style=" font-size:11pt">></span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt"><b>Répondre
à: </b>"Blalock, John R. (GSFC-459.0)[PERATON, INC]" <</span><a href=mailto:john.r.blalock@nasa.gov><span style=" font-size:11pt;color:blue"><u>john.r.blalock@nasa.gov</u></span></a><span style=" font-size:11pt">></span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Hello,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">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)</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<ul>
<li><span style=" font-size:11pt;font-family:Calibri">116 </span>
<li><span style=" font-size:11pt;font-family:Calibri">229</span>
<li><span style=" font-size:11pt;font-family:Calibri">068</span></ul><span style=" font-size:11pt;font-family:Calibri"> </span>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Regards,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">John
Blalock Jr.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span><tt><span style=" font-size:10pt">_______________________________________________<br>
CESG mailing list<br>
CESG@mailman.ccsds.org<br>
</span></tt><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg"><tt><span style=" font-size:10pt">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg</span></tt></a><tt><span style=" font-size:10pt"><br>
</span></tt></p>
<p style="margin-top:0px;margin-Bottom:0px"></p>
<p style="margin-top:0px;margin-Bottom:0px"></p>
<p style="margin-top:0px;margin-Bottom:0px"></p>
<PRE>This message is intended only for the recipient(s) named above. It may contain proprietary information and/or
protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received
this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect
personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo@esa.int).
</PRE>