<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">Le 15 juin 2021 à 07:56, Shames, Peter M (US 312B) <<a href="mailto:peter.m.shames@jpl.nasa.gov" class="">peter.m.shames@jpl.nasa.gov</a>> a écrit :</div><br class="Apple-interchange-newline"><div class=""><meta charset="UTF-8" class=""><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class="EmailStyle22" style="font-family: Calibri, sans-serif; color: windowtext;">Hi Gippo,<o:p class=""></o:p></span></div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class="EmailStyle22" style="font-family: Calibri, sans-serif; color: windowtext;"><o:p class=""> </o:p></span></div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class="EmailStyle22" style="font-family: Calibri, sans-serif; color: windowtext;">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.</span></div></div></div></blockquote><div><br class=""></div><div><br class=""></div><div>Moreover, one has to look carefully at frequency bands. </div><div><br class=""></div><blockquote type="cite" class=""><div class=""><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class="EmailStyle22" style="font-family: Calibri, sans-serif; color: windowtext;"><o:p class=""></o:p></span></div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class="EmailStyle22" style="font-family: Calibri, sans-serif; color: windowtext;"><o:p class=""> </o:p></span></div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class="EmailStyle22" style="font-family: Calibri, sans-serif; color: windowtext;">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.</span></div></div></div></blockquote><div><br class=""></div><div><br class=""></div><div>yeap. Given the scarce space available, most specific requests like these have to be declined. We have spent a lot of efforts to automate our process to minimize as much as possible any errors in allocations. This manual « I want my SCID » route just bypass this process and therefore is more error prone on our side. </div><div><br class=""></div><br class=""><blockquote type="cite" class=""><div class=""><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class="EmailStyle22" style="font-family: Calibri, sans-serif; color: windowtext;"><o:p class=""></o:p></span></div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class="EmailStyle22" style="font-family: Calibri, sans-serif; color: windowtext;"><o:p class=""> </o:p></span></div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class="EmailStyle22" style="font-family: Calibri, sans-serif; color: windowtext;">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?</span></div></div></div></blockquote><div><br class=""></div><div>yes, it would be very useful to understand the need for specific IDs. It can’t be « this is a nice number ». Again given the scarce space available, the reason has to be pretty important.</div><div><br class=""></div><div>Marc.</div><div><br class=""></div><br class=""><blockquote type="cite" class=""><div class=""><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class="EmailStyle22" style="font-family: Calibri, sans-serif; color: windowtext;"><o:p class=""></o:p></span></div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class="EmailStyle22" style="font-family: Calibri, sans-serif; color: windowtext;"><o:p class=""> </o:p></span></div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class="EmailStyle22" style="font-family: Calibri, sans-serif; color: windowtext;">Thanks, Peter<o:p class=""></o:p></span></div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="border-style: solid none none; border-top-width: 1pt; border-top-color: rgb(181, 196, 223); padding: 3pt 0in 0in;" class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><b class=""><span style="font-size: 12pt;" class="">From:<span class="Apple-converted-space"> </span></span></b><span style="font-size: 12pt;" class="">Gian Paolo Calzolari <<a href="mailto:Gian.Paolo.Calzolari@esa.int" style="color: blue; text-decoration: underline;" class="">Gian.Paolo.Calzolari@esa.int</a>><br class=""><b class="">Date:<span class="Apple-converted-space"> </span></b>Tuesday, June 15, 2021 at 2:03 AM<br class=""><b class="">To:<span class="Apple-converted-space"> </span></b>Peter Shames <<a href="mailto:peter.m.shames@jpl.nasa.gov" style="color: blue; text-decoration: underline;" class="">peter.m.shames@jpl.nasa.gov</a>><br class=""><b class="">Cc:<span class="Apple-converted-space"> </span></b>CCSDS Engineering Steering Group - CESG Exec <<a href="mailto:cesg@mailman.ccsds.org" style="color: blue; text-decoration: underline;" class="">cesg@mailman.ccsds.org</a>>, Marc Blanchet <<a href="mailto:marc.blanchet@viagenie.ca" style="color: blue; text-decoration: underline;" class="">marc.blanchet@viagenie.ca</a>>, "SANA Steering Group (SSG)" <<a href="mailto:ssg@mailman.ccsds.org" style="color: blue; text-decoration: underline;" class="">ssg@mailman.ccsds.org</a>><br class=""><b class="">Subject:<span class="Apple-converted-space"> </span></b>[EXTERNAL] Re: [CESG] Requesting SSG "consensus": QSCID Question<o:p class=""></o:p></span></div></div><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div></div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 10pt; font-family: Arial, sans-serif;" class="">Peter,</span><span class="Apple-converted-space"> </span><br class=""><span style="font-size: 10pt; font-family: Arial, sans-serif;" class=""> I concur with Marc analysis and with your considerations but I wonder whether a softer approach could be used.</span><span class="Apple-converted-space"> </span><br class=""><span style="font-size: 10pt; font-family: Arial, sans-serif;" class="">I mean that - since the SCID values are all public at<span class="Apple-converted-space"> </span></span><a href="https://urldefense.us/v3/__https:/sanaregistry.org/r/spacecraftid/__;!!PvBDto6Hs4WbVuu7!a8DH8ZwEglT8_6NMWb8wINgI3d3v6aPLrXo8dkcP7ZbUOP8GJY9LxVuIesuMuP60fjxZosO0$" style="color: blue; text-decoration: underline;" class=""><span style="font-size: 10pt; font-family: Arial, sans-serif;" class="">https://sanaregistry.org/r/spacecraftid/</span></a><span style="font-size: 10pt; font-family: Arial, sans-serif;" class=""><span class="Apple-converted-space"> </span>- an Agency has all the means to check if a value is free or assigned. (Some remarks below)</span><span class="Apple-converted-space"> </span><br class=""><span style="font-size: 10pt; font-family: Arial, sans-serif;" class="">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><span class="Apple-converted-space"> </span><br class=""><br class=""><span style="font-size: 10pt; font-family: Arial, sans-serif;" class="">This could be a way to still be friendly to requester but avoiding a "interpretable" task to NASA.</span><span class="Apple-converted-space"> </span><br class=""><br class=""><span style="font-size: 10pt; font-family: Arial, sans-serif;" class="">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><span class="Apple-converted-space"> </span><br class=""><br class=""><span style="font-size: 10pt; font-family: Arial, sans-serif;" class="">My cent,,,</span><span class="Apple-converted-space"> </span><br class=""><br class=""><span style="font-size: 10pt; font-family: Arial, sans-serif;" class="">Gippo</span><span class="Apple-converted-space"> </span><br class=""><br class=""><br class=""><span style="font-size: 10pt; font-family: Arial, sans-serif;" class="">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><span class="Apple-converted-space"> </span><br class=""><span style="font-size: 10pt; font-family: Arial, sans-serif;" class="">This is just to say that the requester would have been able to know that his request<span class="Apple-converted-space"> </span></span> “pick your own number” was a mission impossible.<span class="Apple-converted-space"> </span><br class="">In case those values were free, he could have stated this in his analysis justifying the ticked “pick your own number” option.<span class="Apple-converted-space"> </span><br class=""><br class=""><br class=""><br class=""><br class=""><span style="font-size: 9pt; font-family: Arial, sans-serif; color: rgb(95, 95, 95);" class="">From: </span><span style="font-size: 9pt; font-family: Arial, sans-serif;" class="">"Shames, Peter M\(US 312B\) via CESG" <<a href="mailto:cesg@mailman.ccsds.org" style="color: blue; text-decoration: underline;" class="">cesg@mailman.ccsds.org</a>></span><span class="Apple-converted-space"> </span><br class=""><span style="font-size: 9pt; font-family: Arial, sans-serif; color: rgb(95, 95, 95);" class="">To: </span><span style="font-size: 9pt; font-family: Arial, sans-serif;" class="">"SANA Steering Group (SSG)" <<a href="mailto:ssg@mailman.ccsds.org" style="color: blue; text-decoration: underline;" class="">ssg@mailman.ccsds.org</a>></span><span class="Apple-converted-space"> </span><br class=""><span style="font-size: 9pt; font-family: Arial, sans-serif; color: rgb(95, 95, 95);" class="">Cc: </span><span style="font-size: 9pt; font-family: Arial, sans-serif;" class="">"Marc Blanchet" <<a href="mailto:marc.blanchet@viagenie.ca" style="color: blue; text-decoration: underline;" class="">marc.blanchet@viagenie.ca</a>>, "CCSDS Engineering Steering Group - CESG Exec" <<a href="mailto:cesg@mailman.ccsds.org" style="color: blue; text-decoration: underline;" class="">cesg@mailman.ccsds.org</a>></span><span class="Apple-converted-space"> </span><br class=""><span style="font-size: 9pt; font-family: Arial, sans-serif; color: rgb(95, 95, 95);" class="">Date: </span><span style="font-size: 9pt; font-family: Arial, sans-serif;" class="">15-06-21 01:52</span><span class="Apple-converted-space"> </span><br class=""><span style="font-size: 9pt; font-family: Arial, sans-serif; color: rgb(95, 95, 95);" class="">Subject: </span><span style="font-size: 9pt; font-family: Arial, sans-serif;" class="">[CESG] Requesting SSG "consensus": QSCID Question</span><span class="Apple-converted-space"> </span><br class=""><span style="font-size: 9pt; font-family: Arial, sans-serif; color: rgb(95, 95, 95);" class="">Sent by: </span><span style="font-size: 9pt; font-family: Arial, sans-serif;" class="">"CESG" <<a href="mailto:cesg-bounces@mailman.ccsds.org" style="color: blue; text-decoration: underline;" class="">cesg-bounces@mailman.ccsds.org</a>></span><o:p class=""></o:p></div><div class="MsoNormal" align="center" style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif; text-align: center;"><hr size="0" width="100%" noshade="" align="center" style="color: rgb(160, 160, 160);" class=""></div><p class="MsoNormal" style="margin: 0in 0in 12pt; font-size: 11pt; font-family: Calibri, sans-serif;"><o:p class=""> </o:p></p><div style="margin: 0in;" class="">Hi Marc,<o:p class=""></o:p></div><div style="margin: 0in;" class=""> <o:p class=""></o:p></div><div style="margin: 0in;" class="">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 class=""></o:p></div><div style="margin: 0in;" class=""> <o:p class=""></o:p></div><div style="margin: 0in;" class="">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 class=""></o:p></div><div style="margin: 0in;" class=""> <o:p class=""></o:p></div><div style="margin: 0in;" class="">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 class=""></o:p></div><div style="margin: 0in;" class=""> <o:p class=""></o:p></div><div style="margin: 0in;" class="">In accordance with CCSDS Consensus processes "Can anyone not live with this choice? “<o:p class=""></o:p></div><div style="margin: 0in;" class=""> <o:p class=""></o:p></div><div style="margin: 0in;" class="">Thanks, Peter<o:p class=""></o:p></div><div style="margin: 0in;" class=""> <o:p class=""></o:p></div><div style="margin: 0in;" class=""> <o:p class=""></o:p></div><div style="margin: 0in;" class=""> <o:p class=""></o:p></div><div style="margin: 0in;" class=""> <o:p class=""></o:p></div><div style="margin: 0in;" class=""><b class=""><span style="font-size: 12pt;" class="">From:<span class="Apple-converted-space"> </span></span></b><span style="font-size: 12pt;" class="">SSG <<a href="mailto:ssg-bounces@mailman.ccsds.org" style="color: blue; text-decoration: underline;" class="">ssg-bounces@mailman.ccsds.org</a>> on behalf of Marc Blanchet <<a href="mailto:marc.blanchet@viagenie.ca" style="color: blue; text-decoration: underline;" class="">marc.blanchet@viagenie.ca</a>><b class=""><br class="">Date:<span class="Apple-converted-space"> </span></b>Monday, June 14, 2021 at 2:07 PM<b class=""><br class="">To:<span class="Apple-converted-space"> </span></b>"SANA Steering Group (SSG)" <<a href="mailto:ssg@mailman.ccsds.org" style="color: blue; text-decoration: underline;" class="">ssg@mailman.ccsds.org</a>><b class=""><br class="">Subject:<span class="Apple-converted-space"> </span></b>[EXTERNAL] [SSG] Fwd: QSCID Question</span><o:p class=""></o:p></div><div style="margin: 0in;" class=""> <o:p class=""></o:p></div><div style="margin: 0in;" class="">Hello,<span class="Apple-converted-space"> </span><o:p class=""></o:p></div><div style="margin: 0in;" class=""> 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 class=""></o:p></div><div style="margin: 0in;" class=""> <o:p class=""></o:p></div><div style="margin: 0in;" class="">Marc.<o:p class=""></o:p></div><div style="margin: 0in;" class=""><o:p class=""> </o:p></div><div style="margin: 0in;" class="">Début du message transféré :<o:p class=""></o:p></div><div style="margin: 0in;" class=""> <o:p class=""></o:p></div><div style="margin: 0in;" class=""><b class="">De:<span class="Apple-converted-space"> </span></b>"'Blalock, John R. (GSFC-459.0)[PERATON, INC]' via Engineering" <<a href="mailto:eng@viagenie.ca" style="color: blue; text-decoration: underline;" class="">eng@viagenie.ca</a>><o:p class=""></o:p></div><div style="margin: 0in;" class=""><b class="">Objet: QSCID Question</b><o:p class=""></o:p></div><div style="margin: 0in;" class=""><b class="">Date:<span class="Apple-converted-space"> </span></b>14 juin 2021 à 10:29:04 HAE<o:p class=""></o:p></div><div style="margin: 0in;" class=""><b class="">À:<span class="Apple-converted-space"> </span></b>SANA <<a href="mailto:info@sanaregistry.org" style="color: blue; text-decoration: underline;" class="">info@sanaregistry.org</a>><o:p class=""></o:p></div><div style="margin: 0in;" class=""><b class="">Cc:<span class="Apple-converted-space"> </span></b>"Zaki, Bashaer E (GSFC-450.0)[Internet Consulting Services, LLC]" <<a href="mailto:bashaer.e.zaki@nasa.gov" style="color: blue; text-decoration: underline;" class="">bashaer.e.zaki@nasa.gov</a>><o:p class=""></o:p></div><div style="margin: 0in;" class=""><b class="">Répondre à:<span class="Apple-converted-space"> </span></b>"Blalock, John R. (GSFC-459.0)[PERATON, INC]" <<a href="mailto:john.r.blalock@nasa.gov" style="color: blue; text-decoration: underline;" class="">john.r.blalock@nasa.gov</a>><o:p class=""></o:p></div><div style="margin: 0in;" class=""> <o:p class=""></o:p></div><div style="margin: 0in;" class="">Hello,<o:p class=""></o:p></div><div style="margin: 0in;" class="">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 class=""></o:p></div><div style="margin: 0in;" class=""> <o:p class=""></o:p></div><ul type="disc" style="margin-bottom: 0in;" class=""><li class="MsoNormal" style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;">116<span class="Apple-converted-space"> </span><o:p class=""></o:p></li><li class="MsoNormal" style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;">229<span class="Apple-converted-space"> </span><o:p class=""></o:p></li><li class="MsoNormal" style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;">068<o:p class=""></o:p></li></ul><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <span class="Apple-converted-space"> </span><o:p class=""></o:p></div><div style="margin: 0in;" class="">Regards,<o:p class=""></o:p></div><div style="margin: 0in;" class="">John Blalock Jr.<o:p class=""></o:p></div><div style="margin: 0in;" class=""> <tt style="font-family: "Courier New";" class=""><span style="font-size: 10pt;" class="">_______________________________________________</span></tt><span style="font-size: 10pt; font-family: "Courier New";" class=""><br class=""><tt style="font-family: "Courier New";" class="">CESG mailing list</tt><br class=""><tt style="font-family: "Courier New";" class=""><a href="mailto:CESG@mailman.ccsds.org" style="color: blue; text-decoration: underline;" class="">CESG@mailman.ccsds.org</a></tt><br class=""></span><a href="https://urldefense.us/v3/__https:/mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg__;!!PvBDto6Hs4WbVuu7!a8DH8ZwEglT8_6NMWb8wINgI3d3v6aPLrXo8dkcP7ZbUOP8GJY9LxVuIesuMuP60fp0AQwpU$" style="color: blue; text-decoration: underline;" class=""><tt style="font-family: "Courier New";" class=""><span style="font-size: 10pt;" class="">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg</span></tt></a><o:p class=""></o:p></div><pre style="margin: 0in; font-size: 10pt; font-family: "Courier New";" class="">This message is intended only for the recipient(s) named above. It may contain proprietary information and/or<o:p class=""></o:p></pre><pre style="margin: 0in; font-size: 10pt; font-family: "Courier New";" class="">protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received<o:p class=""></o:p></pre><pre style="margin: 0in; font-size: 10pt; font-family: "Courier New";" class="">this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect<o:p class=""></o:p></pre><pre style="margin: 0in; font-size: 10pt; font-family: "Courier New";" class="">personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (<a href="mailto:dpo@esa.int" style="color: blue; text-decoration: underline;" class="">dpo@esa.int</a>).</pre></div></div></blockquote></div><br class=""></body></html>