[SLS] Are your documents using the term GSCID?

[Gian.Paolo.Calzolari at esa.int]

Dear All,
        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.
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. 
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.
A possible consequence is that the use of the tern GSCID will be 
discouraged/deprecated for future use.

Note that some SLP documents (*) define that "The concatenation of a TFVN 
and a SCID is known as a Master Channel Identifier (MCID),"
With TFVN (transfer Frame Version Number) being actually the same of the 
VN mentioned in CCSDS 320.0-B-6 
(*) 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

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?

Thank you and best regards

Gian Paolo

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......
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.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/sls/attachments/20160718/f36e51da/attachment.html>