<font size=2 face="sans-serif">NO from RFM WG.</font>
<br>
<br><font size=2 face="sans-serif">Enrico</font>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">Gian.Paolo.Calzolari@esa.int</font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">"SLS - Space Link
Services Area" <sls@mailman.ccsds.org></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">18/07/2016 10:49</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">[SLS] Are
your documents using the term GSCID?</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Sent by:
</font><font size=1 face="sans-serif">"SLS"
<sls-bounces@mailman.ccsds.org></font>
<br>
<hr noshade>
<br>
<br>
<br><font size=2 face="sans-serif">Dear All,</font><font size=3> </font><font size=2 face="sans-serif"><br>
there is an ongoing update for CCSDS 320.0-B-6
CCSDS Global Spacecraft Identification Field Code Assignment Control
Procedures. Blue Book. Issue 6. October 2013.</font><font size=3> </font><font size=2 face="sans-serif"><br>
That document defines the acronym GSCID corresponding to the term "Global
Spacecraft Identifier" being the concatenation of
the 2-bit Version Number (VN) and the SCID.
</font><font size=3> </font><font size=2 face="sans-serif"><br>
To be able to allocate more values, the update of CCSDS 320.0-B-6 would
link the assigned value to the Frequency Band actually used by the spacecraft.</font><font size=3>
</font><font size=2 face="sans-serif"><br>
A possible consequence is that the use of the tern GSCID will be discouraged/deprecated
for future use.</font><font size=3> <br>
</font><font size=2 face="sans-serif"><br>
Note that some SLP documents (*) define that "The concatenation of
a TFVN and a SCID is known as a Master Channel Identifier (MCID),"</font><font size=3>
</font><font size=2 face="sans-serif"><br>
With TFVN (transfer Frame Version Number) being actually the same of the
VN mentioned in CCSDS 320.0-B-6 <br>
(*) CCSDS 132.0-B-2, , CCSDS 232.0-B-3, CCSDS 732.0-B-3. Moreover
MCID is mentioned in CCSDS 133.0-B-1</font><font size=3> <br>
</font><font size=2 face="sans-serif"><br>
Just to evaluate the possible impact that updating CCSDS 320.0-B-6 could
have on SLS documents, could you ALL please check and report if any document
of your Working Group is using the term GSCID or the term MCID?</font><font size=3>
<br>
</font><font size=2 face="sans-serif"><br>
Thank you and best regards</font><font size=3> <br>
</font><font size=2 face="sans-serif"><br>
Gian Paolo</font><font size=3> <br>
</font><font size=2 face="sans-serif"><br>
PS The only effect I can dream about right now, is adding a note in those
document to inform that the MCID is called GSCID in CCSDS 320.0-B-6......</font>
<br><tt><font size=3>This message and any attachments are intended for
the use of the addressee or addressees only.<br>
The unauthorised disclosure, use, dissemination or copying (either in whole
or in part) of its<br>
content is not permitted.<br>
If you received this message in error, please notify the sender and delete
it from your system.<br>
Emails can be altered and their integrity cannot be guaranteed by the sender.<br>
<br>
Please consider the environment before printing this email.<br>
</font></tt><tt><font size=2>_______________________________________________<br>
SLS mailing list<br>
SLS@mailman.ccsds.org<br>
</font></tt><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sls"><tt><font size=2>https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sls</font></tt></a><tt><font size=2><br>
</font></tt>
<br>
<br><PRE>This message and any attachments are intended for the use of the addressee or addressees only.
The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its
content is not permitted.
If you received this message in error, please notify the sender and delete it from your system.
Emails can be altered and their integrity cannot be guaranteed by the sender.
Please consider the environment before printing this email.
</PRE>