<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:mv="http://macVmlSchemaUri" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Title" content="">
<meta name="Keywords" content="">
<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:Arial;
        panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
        {font-family:"Courier New";
        panose-1:2 7 3 9 2 2 5 2 4 4;}
@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:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
        {font-family:sans-serif;
        panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
pre
        {mso-style-priority:99;
        mso-style-link:"HTML Preformatted Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:10.0pt;
        font-family:"Courier New";}
span.HTMLPreformattedChar
        {mso-style-name:"HTML Preformatted Char";
        mso-style-priority:99;
        mso-style-link:"HTML Preformatted";
        font-family:Courier;}
span.EmailStyle19
        {mso-style-type:personal-reply;
        font-family:Calibri;
        color:windowtext;}
span.msoIns
        {mso-style-type:export-only;
        mso-style-name:"";
        text-decoration:underline;
        color:teal;}
.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;}
--></style>
</head>
<body bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Seems good to me.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">                                --keith<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-family:Calibri;color:black">From: </span>
</b><span style="font-family:Calibri;color:black">"cesg-bounces@mailman.ccsds.org" <cesg-bounces@mailman.ccsds.org> on behalf of Gian Calzolari <Gian.Paolo.Calzolari@esa.int><br>
<b>Date: </b>Tuesday, July 19, 2016 at 3:31 AM<br>
<b>To: </b>Peter Shames <peter.m.shames@jpl.nasa.gov><br>
<b>Cc: </b>Tom Gannett <thomas.gannett@tgannett.net>, CCSDS Exec <cesg@mailman.ccsds.org><br>
<b>Subject: </b>Re: [CESG] Why renaming GSCID inf revised CCSDS SCID Code Assignment Control Procedures?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"sans-serif","serif"">Fine with me.</span>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif"">What about other CESGers?</span>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif"">Regards</span> <br>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif"">Gian Paolo</span>
<br>
<br>
<br>
<br>
<span style="font-size:7.5pt;font-family:"sans-serif","serif";color:#5F5F5F">From:        </span><span style="font-size:7.5pt;font-family:"sans-serif","serif"">"Shames, Peter M (312B)" <peter.m.shames@jpl.nasa.gov></span>
<br>
<span style="font-size:7.5pt;font-family:"sans-serif","serif";color:#5F5F5F">To:        </span><span style="font-size:7.5pt;font-family:"sans-serif","serif"">"Thomas Gannett" <thomas.gannett@tgannett.net>, "Gian.Paolo.Calzolari@esa.int" <Gian.Paolo.Calzolari@esa.int></span>
<br>
<span style="font-size:7.5pt;font-family:"sans-serif","serif";color:#5F5F5F">Cc:        </span><span style="font-size:7.5pt;font-family:"sans-serif","serif"">"'CCSDS CESG --'" <cesg@mailman.ccsds.org></span>
<br>
<span style="font-size:7.5pt;font-family:"sans-serif","serif";color:#5F5F5F">Date:        </span><span style="font-size:7.5pt;font-family:"sans-serif","serif"">18/07/2016 18:12</span>
<br>
<span style="font-size:7.5pt;font-family:"sans-serif","serif";color:#5F5F5F">Subject:        </span><span style="font-size:7.5pt;font-family:"sans-serif","serif"">Re: [CESG] Why renaming GSCID inf revised CCSDS SCID Code Assignment Control Procedures?</span>
<o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" noshade="" style="color:#AAAAAA" align="center">
</div>
<p class="MsoNormal"><br>
<br>
<br>
<span style="font-size:10.0pt;font-family:Calibri">Guys,</span> <br>
<span style="font-size:10.0pt;font-family:Calibri"> </span> <br>
<span style="font-size:10.0pt;font-family:Calibri">I think we’ve gotten into the right neighborhood now.    And I like Tom’s suggestion for use of Q-SCID.  I’ll mark up the draft to reflect this agreement and re-submit.  </span>
<br>
<span style="font-size:10.0pt;font-family:Calibri"> </span> <br>
<span style="font-size:10.0pt;font-family:Calibri">And we will, as requested, go thru the full CESG / CMC / Agency review cycle.</span>
<br>
<span style="font-size:10.0pt;font-family:Calibri"> </span> <br>
<span style="font-size:10.0pt;font-family:Calibri">Agreed?</span> <br>
<span style="font-size:10.0pt;font-family:Calibri"> </span> <br>
<span style="font-size:10.0pt;font-family:Calibri">Peter</span> <br>
<span style="font-size:10.0pt;font-family:Calibri"> </span> <br>
<span style="font-size:10.0pt;font-family:Calibri"> </span> <br>
<b><span style="font-family:Calibri">From: </span></b><span style="font-family:Calibri">Tom Gannett <thomas.gannett@tgannett.net><b><br>
Date: </b>Monday, July 18, 2016 at 6:09 AM<b><br>
To: </b>Gian Paolo Calzolari <Gian.Paolo.Calzolari@esa.int>, Peter Shames <peter.m.shames@jpl.nasa.gov><b><br>
Cc: </b>CCSDS Engineering Steering Group - CESG Exec <cesg@mailman.ccsds.org><b><br>
Subject: </b>RE: [CESG] Why renaming GSCID inf revised CCSDS SCID Code Assignment Control Procedures?</span>
<br>
  <br>
<span style="font-size:10.0pt;font-family:Calibri;color:#004080">I’m not sure where “global” came from, except I think it was a catchy term in the early days of personal computing. The book actually defines a
<i>qualified</i> SCID, so why not “QSCID” for SCID qualified by version number and frequency band?
</span><br>
<span style="font-size:10.0pt;font-family:Calibri;color:#004080"> </span> <br>
<span style="color:#004080"> </span> <br>
<span style="color:#004080">Thomas Gannett</span> <br>
<span style="color:#004080">thomas.gannett@tgannett.net</span> <br>
<span style="color:#004080">+1 443 472 0805</span> <br>
<span style="font-size:10.0pt;font-family:Calibri;color:#004080"> </span> <br>
<b><span style="font-size:10.0pt;font-family:Tahoma">From:</span></b><span style="font-size:10.0pt;font-family:Tahoma"> Gian.Paolo.Calzolari@esa.int [</span><a href="mailto:Gian.Paolo.Calzolari@esa.int"><span style="font-size:10.0pt;font-family:Tahoma">mailto:Gian.Paolo.Calzolari@esa.int</span></a><span style="font-size:10.0pt;font-family:Tahoma">]
<b><br>
Sent:</b> Monday, July 18, 2016 4:47 AM<b><br>
To:</b> Shames, Peter M (312B)<b><br>
Cc:</b> CCSDS CESG --; Tom Gannett<b><br>
Subject:</b> Re: [CESG] Why renaming GSCID inf revised CCSDS SCID Code Assignment Control Procedures?</span>
<br>
  <br>
<span style="font-size:10.0pt;font-family:Arial">Peter,</span> <span style="font-size:10.0pt;font-family:Arial">
<br>
       my cent.</span> <span style="font-size:10.0pt;font-family:Arial"><br>
1) Priority is on 320.0-B/M ==> let's focus there</span> <span style="font-size:10.0pt;font-family:Arial">
<br>
2) Define </span><span style="font-size:10.0pt;font-family:Calibri"> “Extended GSCID” or E-GSCID
</span><span style="font-size:10.0pt;font-family:Arial">(or any better name)</span>
<span style="font-size:10.0pt;font-family:Arial"><br>
3) Remark with NOTES that <br>
       a- GSCID is the term used before (kept for backward compatibility) and it defines a value that does go into the field(s) of the Transfer Frames (while
</span><span style="font-size:10.0pt;font-family:Calibri"> E-GSCID</span><span style="font-size:10.0pt;font-family:Arial"> does not).
<br>
       b- other documents refer to that value as MCID</span> <span style="font-size:10.0pt;font-family:Arial">
<br>
       c- (optionally) future use of the acronym GSCID is discouraged/deprecated.</span>
<span style="font-size:10.0pt;font-family:Arial"><br>
4) Replace VN with TFVN and add a NOTE to explain this painless replacement due to the fact that TFVN is used by SDLP's and SLE documents and that "Version Number" could be ambiguous as there are actually TFVN and PVN.</span>
<br>
<span style="font-size:10.0pt;font-family:Arial"><br>
That's all. <br>
For the rest let's see the version Tom will produce at CESG Poll.</span> <br>
<span style="font-size:10.0pt;font-family:Arial"><br>
Gian Paolo</span> <br>
<br>
<br>
<span style="font-size:7.5pt;font-family:Arial;color:#5F5F5F"><br>
From:        </span><span style="font-size:7.5pt;font-family:Arial">"Shames, Peter M (312B)" <</span><a href="mailto:peter.m.shames@jpl.nasa.gov"><span style="font-size:7.5pt;font-family:Arial">peter.m.shames@jpl.nasa.gov</span></a><span style="font-size:7.5pt;font-family:Arial">></span>
<span style="font-size:7.5pt;font-family:Arial;color:#5F5F5F"><br>
To:        </span><span style="font-size:7.5pt;font-family:Arial">"</span><a href="mailto:Gian.Paolo.Calzolari@esa.int"><span style="font-size:7.5pt;font-family:Arial">Gian.Paolo.Calzolari@esa.int</span></a><span style="font-size:7.5pt;font-family:Arial">"
 <</span><a href="mailto:Gian.Paolo.Calzolari@esa.int"><span style="font-size:7.5pt;font-family:Arial">Gian.Paolo.Calzolari@esa.int</span></a><span style="font-size:7.5pt;font-family:Arial">>, "CCSDS CESG --" <</span><a href="mailto:cesg@mailman.ccsds.org"><span style="font-size:7.5pt;font-family:Arial">cesg@mailman.ccsds.org</span></a><span style="font-size:7.5pt;font-family:Arial">></span>
<span style="font-size:7.5pt;font-family:Arial;color:#5F5F5F"><br>
Cc:        </span><span style="font-size:7.5pt;font-family:Arial">"Tom Gannett" <</span><a href="mailto:thomas.gannett@tgannett.net"><span style="font-size:7.5pt;font-family:Arial">thomas.gannett@tgannett.net</span></a><span style="font-size:7.5pt;font-family:Arial">></span>
<span style="font-size:7.5pt;font-family:Arial;color:#5F5F5F"><br>
Date:        </span><span style="font-size:7.5pt;font-family:Arial">14/07/2016 18:01</span>
<span style="font-size:7.5pt;font-family:Arial;color:#5F5F5F"><br>
Subject:        </span><span style="font-size:7.5pt;font-family:Arial">Re: [CESG] Why renaming GSCID inf revised CCSDS SCID Code Assignment Control Procedures?</span>
<o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" noshade="" style="color:#AAAAAA" align="center">
</div>
<p class="MsoNormal"><br>
<br>
<br>
<span style="font-size:10.0pt;font-family:Calibri"><br>
Hi Gippo,</span> <span style="font-size:10.0pt;font-family:Calibri"><br>
</span> <span style="font-size:10.0pt;font-family:Calibri"><br>
That’s fine, but what do you propose we do with the existing inconsistency?   We have used two different terms to mean the exact same thing.  In one case (actually 4 cases) we call these two fields “MCID”, in the other case we call the exact same two fields
 “SCID”.  In your opinion should we drop the term GSCID and use MCID everywhere, or should we bring all of the protocols into line and adopt GSCID everywhere?</span>
<span style="font-size:10.0pt;font-family:Calibri"><br>
</span> <span style="font-size:10.0pt;font-family:Calibri"><br>
Or, probably the worst case, should we document this mistake we have made so that it is clear that we have two terms for the same thing?</span>
<span style="font-size:10.0pt;font-family:Calibri"><br>
</span> <span style="font-size:10.0pt;font-family:Calibri"><br>
I’m asking you, in particular, because all of those protocol docs are in your area.  I’m also guessing that you will be resistant to changing any of them, in which case the choice is likely to be “Keep MCID.”  We can do that, but then we will need to put something
 in the “GSCID doc”, which should really in that case be called the “MCID doc”, that these are actually one and the same.</span>
<span style="font-size:10.0pt;font-family:Calibri"><br>
</span> <span style="font-size:10.0pt;font-family:Calibri"><br>
And I think, as I said, that we can call this field, concatenated with the frequency bin, the “Extended GSCID” or E-GSCID (or E-MCID).</span>
<span style="font-size:10.0pt;font-family:Calibri"><br>
</span> <span style="font-size:10.0pt;font-family:Calibri"><br>
I’d like to get your opinion about this specific issue so I can include it in the revised 320x0 that I submit for review.</span>
<span style="font-size:10.0pt;font-family:Calibri"><br>
</span> <span style="font-size:10.0pt;font-family:Calibri"><br>
Thanks, Peter</span> <span style="font-size:10.0pt;font-family:Calibri"><br>
</span> <span style="font-size:10.0pt;font-family:Calibri"><br>
</span> <b><span style="font-family:Calibri"><br>
From: </span></b><span style="font-family:Calibri">CESG <</span><a href="mailto:cesg-bounces@mailman.ccsds.org"><span style="font-family:Calibri">cesg-bounces@mailman.ccsds.org</span></a><span style="font-family:Calibri">> on behalf of Gian Paolo Calzolari
 <</span><a href="mailto:Gian.Paolo.Calzolari@esa.int"><span style="font-family:Calibri">Gian.Paolo.Calzolari@esa.int</span></a><span style="font-family:Calibri">><b><br>
Date: </b>Thursday, July 14, 2016 at 2:01 AM<b><br>
To: </b>CCSDS Engineering Steering Group - CESG Exec <</span><a href="mailto:cesg@mailman.ccsds.org"><span style="font-family:Calibri">cesg@mailman.ccsds.org</span></a><span style="font-family:Calibri">><b><br>
Cc: </b>Tom Gannett <</span><a href="mailto:thomas.gannett@tgannett.net"><span style="font-family:Calibri">thomas.gannett@tgannett.net</span></a><span style="font-family:Calibri">><b><br>
Subject: </b>Re: [CESG] Why renaming GSCID inf revised CCSDS SCID Code Assignment Control Procedures?</span>
<br>
 <span style="font-size:10.0pt;font-family:Arial"><br>
IMHO reusing terms giving them a different meaning is wrong by nature and prone to introduce backward compatibility issues.</span>
<br>
<br>
<span style="font-size:7.5pt;font-family:Arial;color:#5F5F5F"><br>
<br>
From:        </span><span style="font-size:7.5pt;font-family:Arial">"Shames, Peter M (312B)" <</span><a href="mailto:peter.m.shames@jpl.nasa.gov"><span style="font-size:7.5pt;font-family:Arial">peter.m.shames@jpl.nasa.gov</span></a><span style="font-size:7.5pt;font-family:Arial">></span>
<span style="font-size:7.5pt;font-family:Arial;color:#5F5F5F"><br>
To:        </span><span style="font-size:7.5pt;font-family:Arial">"</span><a href="mailto:Gian.Paolo.Calzolari@esa.int"><span style="font-size:7.5pt;font-family:Arial">Gian.Paolo.Calzolari@esa.int</span></a><span style="font-size:7.5pt;font-family:Arial">"
 <</span><a href="mailto:Gian.Paolo.Calzolari@esa.int"><span style="font-size:7.5pt;font-family:Arial">Gian.Paolo.Calzolari@esa.int</span></a><span style="font-size:7.5pt;font-family:Arial">></span>
<span style="font-size:7.5pt;font-family:Arial;color:#5F5F5F"><br>
Cc:        </span><span style="font-size:7.5pt;font-family:Arial">"CCSDS CESG --" <</span><a href="mailto:cesg@mailman.ccsds.org"><span style="font-size:7.5pt;font-family:Arial">cesg@mailman.ccsds.org</span></a><span style="font-size:7.5pt;font-family:Arial">>,
 "Tom Gannett" <</span><a href="mailto:thomas.gannett@tgannett.net"><span style="font-size:7.5pt;font-family:Arial">thomas.gannett@tgannett.net</span></a><span style="font-size:7.5pt;font-family:Arial">></span>
<span style="font-size:7.5pt;font-family:Arial;color:#5F5F5F"><br>
Date:        </span><span style="font-size:7.5pt;font-family:Arial">13/07/2016 17:22</span>
<span style="font-size:7.5pt;font-family:Arial;color:#5F5F5F"><br>
Subject:        </span><span style="font-size:7.5pt;font-family:Arial">Re: [CESG] Why renaming GSCID inf revised CCSDS SCID Code Assignment Control Procedures?</span>
<o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" noshade="" style="color:#AAAAAA" align="center">
</div>
<p class="MsoNormal"><br>
<br>
<br>
<span style="font-size:10.0pt;font-family:Calibri"><br>
<br>
Dear Gippo,</span> <br>
<span style="font-size:10.0pt;font-family:Calibri"><br>
In this case we seem to have a term, GSCID, defined in 320x0 that is used only in that document and nowhere else.  And we have the fields that compose that term, the VN and SCID, defined in every other relevant document as the MCID.  The only exception to this,
 I have been informed, is the new USLP which proposes to use the term GSCID instead of MCID.</span>
<br>
<span style="font-size:10.0pt;font-family:Calibri"><br>
In order to get this cleared up efficiently I propose that we use the term MCID in the 320x0 document, thus fixing that obvious error, and that we also bring the USLP in-line, before it sees the light of day.</span>
<br>
<span style="font-size:10.0pt;font-family:Calibri"><br>
At that point we can use the term GSCID as I proposed, without any risk of confusing anyone, since no other document uses that term.</span>
<br>
<span style="font-size:10.0pt;font-family:Calibri"><br>
Or, if you wish, we can create a new term, Extended SCID (ESCID) and define it to mean the concatenation of the Frequency Band with the MCID (or GSCID, if you wish to persist that into the future).  </span>
<br>
<span style="font-size:10.0pt;font-family:Calibri"><br>
Or perhaps you want to change all of the other protocol docs to use the term GSCID instead of MCID so that they are all consistent?</span>
<br>
<span style="font-size:10.0pt;font-family:Calibri"><br>
Which of these are acceptable, to you and the other CESG members?</span> <br>
<span style="font-size:10.0pt;font-family:Calibri"><br>
Regards, Peter</span> <br>
<br>
<b><span style="font-family:Calibri"><br>
From: </span></b><span style="font-family:Calibri">Gian Paolo Calzolari <</span><a href="mailto:Gian.Paolo.Calzolari@esa.int"><span style="font-family:Calibri">Gian.Paolo.Calzolari@esa.int</span></a><span style="font-family:Calibri">><b><br>
Date: </b>Wednesday, July 13, 2016 at 5:30 AM<b><br>
To: </b>Peter Shames <</span><a href="mailto:peter.m.shames@jpl.nasa.gov"><span style="font-family:Calibri">peter.m.shames@jpl.nasa.gov</span></a><span style="font-family:Calibri">><b><br>
Cc: </b>CCSDS Engineering Steering Group - CESG Exec <</span><a href="mailto:cesg@mailman.ccsds.org"><span style="font-family:Calibri">cesg@mailman.ccsds.org</span></a><span style="font-family:Calibri">>, Tom Gannett <</span><a href="mailto:thomas.gannett@tgannett.net"><span style="font-family:Calibri">thomas.gannett@tgannett.net</span></a><span style="font-family:Calibri">><b><br>
Subject: </b>Re: [CESG] Why renaming GSCID inf revised CCSDS SCID Code Assignment Control Procedures?</span>
<br>
<span style="font-size:10.0pt;font-family:Arial"><br>
Dear Peter,</span> <span style="font-size:10.0pt;font-family:Arial"><br>
     I never said that the current situation is perfect.</span> <span style="font-size:10.0pt;font-family:Arial">
<br>
However i do find inappropriate having a term that means alfa till today and it will mean beta as of tomorrow.</span>
<span style="font-size:10.0pt;font-family:Arial"><br>
Regards</span> <span style="font-size:10.0pt;font-family:Arial"><br>
Gian Paolo</span> <br>
<span style="font-size:7.5pt;font-family:Arial;color:#5F5F5F"><br>
<br>
<br>
From:        </span><span style="font-size:7.5pt;font-family:Arial">"Shames, Peter M (312B)" <</span><a href="mailto:peter.m.shames@jpl.nasa.gov"><span style="font-size:7.5pt;font-family:Arial">peter.m.shames@jpl.nasa.gov</span></a><span style="font-size:7.5pt;font-family:Arial">></span>
<span style="font-size:7.5pt;font-family:Arial;color:#5F5F5F"><br>
To:        </span><span style="font-size:7.5pt;font-family:Arial">"</span><a href="mailto:Gian.Paolo.Calzolari@esa.int"><span style="font-size:7.5pt;font-family:Arial">Gian.Paolo.Calzolari@esa.int</span></a><span style="font-size:7.5pt;font-family:Arial">"
 <</span><a href="mailto:Gian.Paolo.Calzolari@esa.int"><span style="font-size:7.5pt;font-family:Arial">Gian.Paolo.Calzolari@esa.int</span></a><span style="font-size:7.5pt;font-family:Arial">>, "CCSDS CESG --" <</span><a href="mailto:cesg@mailman.ccsds.org"><span style="font-size:7.5pt;font-family:Arial">cesg@mailman.ccsds.org</span></a><span style="font-size:7.5pt;font-family:Arial">></span>
<span style="font-size:7.5pt;font-family:Arial;color:#5F5F5F"><br>
Cc:        </span><span style="font-size:7.5pt;font-family:Arial">"Tom Gannett" <</span><a href="mailto:thomas.gannett@tgannett.net"><span style="font-size:7.5pt;font-family:Arial">thomas.gannett@tgannett.net</span></a><span style="font-size:7.5pt;font-family:Arial">></span>
<span style="font-size:7.5pt;font-family:Arial;color:#5F5F5F"><br>
Date:        </span><span style="font-size:7.5pt;font-family:Arial">12/07/2016 18:58</span>
<span style="font-size:7.5pt;font-family:Arial;color:#5F5F5F"><br>
Subject:        </span><span style="font-size:7.5pt;font-family:Arial">Re: [CESG] Why renaming GSCID inf revised CCSDS SCID Code Assignment Control Procedures?</span>
<o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" noshade="" style="color:#AAAAAA" align="center">
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
<br>
<br>
<span style="font-size:10.0pt;font-family:Calibri"><br>
<br>
<br>
Dear Gippo,</span> <span style="font-size:10.0pt;font-family:Calibri"><br>
<br>
I appreciate your attention to detail and looking at this early on, but I have to differ re some conclusions.   I note the following:</span>
<span style="font-family:Calibri"><br>
<br>
-          </span><span style="font-size:10.0pt;font-family:Calibri">The term GSCID was defined
</span><span style="font-family:Calibri">as “</span>GSCID = VN <b>. </b>SCID”<span style="font-size:10.0pt;font-family:Calibri"> where the “</span><b>.</b><span style="font-size:10.0pt;font-family:Calibri">” means concatenation.</span>
<span style="font-family:Calibri"><br>
-          </span><span style="font-size:10.0pt;font-family:Calibri">The terms SCID and GSCID are used more or less interchangeably in the CCSDS 320x0b document, but they mean different things.  This is a flaw in the current document that I have tried to remedy.</span>
<span style="font-family:Calibri"><br>
-          </span><span style="font-size:10.0pt;font-family:Calibri">The term SCID is defined specifically in the various protocol documents, 320x0 just references it.</span>
<span style="font-family:Calibri"><br>
-          </span><span style="font-size:10.0pt;font-family:Calibri">The term GSCID
<b><i>does not</i></b> appear in any of our protocol documents, TC, TM, or AOS.  They tend to call the combination of the VN (actually the TFVN) and the SCID an MCID, not a GSCID.</span>
<span style="font-family:Calibri"><br>
-          </span><span style="font-size:10.0pt;font-family:Calibri">If you search the CCSDS files you will find that the only reference to GSCID is in this 320x0 document, and not in any others.</span>
<span style="font-size:10.0pt;font-family:Calibri"><br>
All of that said, I think that there is really no impediment in the way of extending the definition of GSCID to include the frequency band, because globally, in fact, the frequency band has from the beginning been a part of the actual physical and logical link
 layer signal.  We just did not acknowledge this until now.</span> <span style="font-size:10.0pt;font-family:Calibri">
<br>
But if you are worried about some confusion for others we could introduce a new term for the FB
</span><b>. </b><span style="font-size:10.0pt;font-family:Calibri">VN </span><b>.
</b><span style="font-size:10.0pt;font-family:Calibri">SCID combination.  I’m reluctant to call it a “Super” SCID, that sounds like a kid’s toy.   ;-}  And in truth, I think that this is more of a Global SCID than the current definition, and which the protocol
 docs call an MCID.  In effect we have given the same thing two different names, surely that is not a good approach?  Maybe we should align this book with all of the existing protocol docs and call the VN
</span><b>. </b><span style="font-size:10.0pt;font-family:Calibri">SCID combo an MCID and the FB
</span><b>. </b><span style="font-size:10.0pt;font-family:Calibri">VN </span><b>.
</b><span style="font-size:10.0pt;font-family:Calibri">SCID combo the GSCID?</span>
<span style="font-size:10.0pt;font-family:Calibri"><br>
I am open to other suggestions.</span> <span style="font-size:10.0pt;font-family:Calibri">
<br>
Regards, Peter</span> <br>
<b><span style="font-family:Calibri"><br>
<br>
From: </span></b><span style="font-family:Calibri">CESG <</span><a href="mailto:cesg-bounces@mailman.ccsds.org"><span style="font-family:Calibri">cesg-bounces@mailman.ccsds.org</span></a><span style="font-family:Calibri">> on behalf of Gian Paolo Calzolari
 <</span><a href="mailto:Gian.Paolo.Calzolari@esa.int"><span style="font-family:Calibri">Gian.Paolo.Calzolari@esa.int</span></a><span style="font-family:Calibri">><b><br>
Date: </b>Tuesday, July 12, 2016 at 6:18 AM<b><br>
To: </b>CCSDS Engineering Steering Group - CESG Exec <</span><a href="mailto:cesg@mailman.ccsds.org"><span style="font-family:Calibri">cesg@mailman.ccsds.org</span></a><span style="font-family:Calibri">><b><br>
Cc: </b>Tom Gannett <</span><a href="mailto:thomas.gannett@tgannett.net"><span style="font-family:Calibri">thomas.gannett@tgannett.net</span></a><span style="font-family:Calibri">><b><br>
Subject: </b>[CESG] Why renaming GSCID inf revised CCSDS SCID Code Assignment Control Procedures?</span>
<span style="font-size:10.0pt;font-family:Arial"><br>
<br>
Dear CESGers,</span> <span style="font-size:10.0pt;font-family:Arial"><br>
    in order to gain time and not to delay eventual Poll and start of Agency Review, I would like to anticipate that as SLS AD I wonder about the need of renaming GSCID in revised CCSDS SCID Code Assignment Control Procedures.</span>
<span style="font-size:10.0pt;font-family:Arial"><br>
<br>
In fact the revised book includes a new definition of GSCID (see snapshot) that is conflicting with the definition in the Blue Book in force (see second snapshot) as the new one also refers to Frequency Band.</span>
<span style="font-size:10.0pt;font-family:Arial"><br>
<br>
First of all I think that it is not appropriate modifying a term used for so many years (and for sure spread in "billions" of documents from many agencies) also considering that the the prefix "Global" is widely used for e.g. the Global VCID and Global MAP
 ID (for sure in SLE and SLS books) without considering the Frequency Band.</span>
<span style="font-size:10.0pt;font-family:Arial"><br>
Therefore there would be a discrepancy of meaning about the term Global between the GSCID and the GVCID</span>
<span style="font-size:10.0pt;font-family:Arial"><br>
<br>
Last, but not list the book title "CCSDS Global Spacecraft Identification Field" points to a field i.e. a portion of data that is normally contained in transfer frames. In other words while the actual GSCID matches completely the contents of some bits of a
 Frame Header, the proposed future GSCID will not.</span> <span style="font-size:10.0pt;font-family:Arial">
<br>
<br>
As a conclusion I would retain the current definition of  GSCID while adding a new definition for the  concatenation of the frequency band (FB), 2-bit Version Number (VN) and the SCID.</span>
<span style="font-size:10.0pt;font-family:Arial"><br>
This could be called Universal SCID, Super SCID, Supreme SCID, Frequenced SCID or whatever you prefer.    [Please consider some humour in some proposed definitions.]</span>
<span style="font-size:10.0pt;font-family:Arial"><br>
<br>
Regards</span> <span style="font-size:10.0pt;font-family:Arial"><br>
<br>
Gian Paolo</span> <span style="font-size:10.0pt;font-family:Arial"><br>
<br>
PS Of course I did not perform a complete review of the document.......</span> <br>
<br>
<img border="0" width="771" height="134" id="_x0000_i1029" src="cid:image001.gif@01D1E1A6.9CA0F530"><br>
<img border="0" width="790" height="168" id="_x0000_i1030" src="cid:image002.gif@01D1E1A6.9CA0F530"><span style="font-size:10.0pt;font-family:"Courier New""><br>
This message and any attachments are intended for the use of the addressee or addressees only.</span>
<span style="font-size:10.0pt;font-family:"Courier New""><br>
The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its</span>
<span style="font-size:10.0pt;font-family:"Courier New""><br>
content is not permitted.</span> <span style="font-size:10.0pt;font-family:"Courier New"">
<br>
If you received this message in error, please notify the sender and delete it from your system.</span>
<span style="font-size:10.0pt;font-family:"Courier New""><br>
Emails can be altered and their integrity cannot be guaranteed by the sender.</span>
<span style="font-size:10.0pt;font-family:"Courier New""><br>
<br>
Please consider the environment before printing this email.</span> <span style="font-size:10.0pt;font-family:"Courier New"">
<br>
This message and any attachments are intended for the use of the addressee or addressees only.</span>
<span style="font-size:10.0pt;font-family:"Courier New""><br>
The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its</span>
<span style="font-size:10.0pt;font-family:"Courier New""><br>
content is not permitted.</span> <span style="font-size:10.0pt;font-family:"Courier New"">
<br>
If you received this message in error, please notify the sender and delete it from your system.</span>
<span style="font-size:10.0pt;font-family:"Courier New""><br>
Emails can be altered and their integrity cannot be guaranteed by the sender.</span>
<br>
<span style="font-size:10.0pt;font-family:"Courier New""><br>
Please consider the environment before printing this email.</span> <span style="font-size:10.0pt;font-family:"Courier New"">
<br>
This message and any attachments are intended for the use of the addressee or addressees only.</span>
<span style="font-size:10.0pt;font-family:"Courier New""><br>
The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its</span>
<span style="font-size:10.0pt;font-family:"Courier New""><br>
content is not permitted.</span> <span style="font-size:10.0pt;font-family:"Courier New"">
<br>
If you received this message in error, please notify the sender and delete it from your system.</span>
<span style="font-size:10.0pt;font-family:"Courier New""><br>
Emails can be altered and their integrity cannot be guaranteed by the sender.</span>
<span style="font-size:10.0pt;font-family:"Courier New""><br>
</span> <span style="font-size:10.0pt;font-family:"Courier New""><br>
Please consider the environment before printing this email.</span> <br>
<span style="font-size:10.0pt;font-family:"Courier New"">This message and any attachments are intended for the use of the addressee or addressees only.</span>
<br>
<span style="font-size:10.0pt;font-family:"Courier New"">The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its</span>
<br>
<span style="font-size:10.0pt;font-family:"Courier New"">content is not permitted.</span>
<br>
<span style="font-size:10.0pt;font-family:"Courier New"">If you received this message in error, please notify the sender and delete it from your system.</span>
<br>
<span style="font-size:10.0pt;font-family:"Courier New"">Emails can be altered and their integrity cannot be guaranteed by the sender.</span>
<br>
<span style="font-size:10.0pt;font-family:"Courier New""> </span> <br>
<span style="font-size:10.0pt;font-family:"Courier New"">Please consider the environment before printing this email.</span>
<o:p></o:p></p>
<pre>This message and any attachments are intended for the use of the addressee or addressees only.<o:p></o:p></pre>
<pre>The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its<o:p></o:p></pre>
<pre>content is not permitted.<o:p></o:p></pre>
<pre>If you received this message in error, please notify the sender and delete it from your system.<o:p></o:p></pre>
<pre>Emails can be altered and their integrity cannot be guaranteed by the sender.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Please consider the environment before printing this email.<o:p></o:p></pre>
</div>
</div>
</div>
</body>
</html>