<font size=2 face="sans-serif">Greg,</font>
<br><font size=2 face="sans-serif"> clearly
I do agree that the 31 December deadline is simply impossible and we should
work this out in 2015 to finalize it before Spring 2015 Meetings in Pasadena.</font>
<br><font size=2 face="sans-serif">I think there are other two options
to be explored.</font>
<br><font size=2 face="sans-serif">1) checking with Agencies usage of "TEST
SCID". I know some agencies liked to have for a spacecraft also a
different ID to be used while testing on ground. As those SCID's are never
flying, they might be reused too. Clearly this would need asking back either
to CMC Delegates or (better?) to the SCID Representatives listed here </font><a href=http://sanaregistry.org/r/agency_representatives/agency_representatives.html><font size=2 face="sans-serif">http://sanaregistry.org/r/agency_representatives/agency_representatives.html</font></a><font size=2 face="sans-serif">
</font>
<br><font size=2 face="sans-serif">2) Determining an "escape ID"
[e.g. SCID = 0 Hex or another value] that could be interpreted as
a value to be detailed somewhere else e.g. in the secondary header or in
some spare field, Clearly this should be an extreme resource....</font>
<br>
<br><font size=2 face="sans-serif">BTW, the list is at </font><a href=http://sanaregistry.org/r/spacecraftid/spacecraftid.html><font size=2 face="sans-serif">http://sanaregistry.org/r/spacecraftid/spacecraftid.html</font></a><font size=2 face="sans-serif">
</font>
<br>
<br><font size=2 face="sans-serif">Regards</font>
<br>
<br><font size=2 face="sans-serif">Gian Paolo</font>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">"Kazz, Greg J
(312B)" <greg.j.kazz@jpl.nasa.gov></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">"sls-slp@mailman.ccsds.org"
<sls-slp@mailman.ccsds.org>, </font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">19/12/2014 23:00</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">[Sls-slp] Action
Item from CMC to SLP WG</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Sent by:
</font><font size=1 face="sans-serif">sls-slp-bounces@mailman.ccsds.org</font>
<br>
<hr noshade>
<br>
<br>
<br><font size=4 face="Calibri">Dear SLP members,</font>
<br>
<br><font size=4 face="Calibri">I have received the following action item
from the CCSDS today:</font>
<br>
<br><font size=1 face="sans-serif">Date: 24/11/2014
20:23</font><font size=3 face="Calibri"> </font><font size=1 face="sans-serif"><br>
Subject: SLP-WG Action Item from London</font><font size=3 face="Calibri">
</font><font size=3><br>
</font>
<hr noshade><font size=2 face="Calibri"><br>
</font><font size=3 face="Calibri"> </font><font size=2 face="Calibri"><br>
Below is the action item assigned to the SLP WG. Let me know if you want
to send to Greg or if you want me to send to Greg directly.</font><font size=3 face="Calibri">
</font><font size=2 face="Calibri"><br>
</font><font size=3> </font>
<table width=697 style="border-collapse:collapse;">
<tr valign=top height=8>
<td width=189 style="border-style:solid;border-color:#000000;border-width:2px 3px 2px 2px;padding:1px 1px;"><font size=2 face="Times New Roman">CMC-A-2014-11-19</font>
<td width=497 style="border-style:solid;border-color:#000000;border-width:2px 2px 2px 3px;padding:1px 1px;"><font size=2 face="Times New Roman">The
SLP WG is requested to do an analysis and create procedures (if applicable)
for assigning SCIDs to multiple spacecraft (this is needed for V1 and V2
but most critical for V2). Provide recommendations to the Secretariat for
forwarding to the CMC and SANA Steering Group.</font><font size=4 face="Calibri">
</font><font size=2 face="Times New Roman"><br>
</font><font size=4 face="Calibri"> </font><font size=2 face="Times New Roman"><br>
Action: SLP WG</font><font size=4 face="Calibri"> </font><font size=2 face="Times New Roman"><br>
Due Date: 31 December 2014</font><font size=4 face="Calibri"> </font><font size=2 face="Times New Roman"><br>
Status: Open</font></table>
<p><font size=3 face="Calibri">Obviously, we cannot nor do we need to meet
the 31 Dec 2014 deadline. It is negotiable with the CMC.</font>
<p><font size=3 face="Calibri">However, I want to bring this A.I. to your
attention and explain it’s motivation.</font>
<p><font size=3 face="Calibri">The main reason for this A.I. was a warning
provided by SANA to the CMC after the London meeting that Version 2 SCIDs
(AOS) may very well be exhausted within 6 months time. The number of "available
“ V2 SCIDs is approx. 13%. The number of V1 SCIDs “available” meaning
capable of being assigned is approx 27%. So the motivation is clear. </font>
<p>
<p><font size=3 face="Calibri">What needs to be done? CMC wants a recommendation
from us on the way forward. Apparently the wording in the A.I. referring
to "assigning SCIDs to multiple spacecraft " had two origins:</font>
<br><font size=2 face="sans-serif">1. </font><font size=3 face="Calibri">Requests
that are submitted for the same SCID for both type V1 and V2 SCIDs.</font>
<br><font size=2 face="sans-serif">2. </font><font size=3 face="Calibri">Requests
that are submitted to assign SCIDs for more than one spacecraft (as in
a constellation)</font>
<p><font size=2 face="Calibri"> </font>
<p><font size=2 face="Calibri">So SLP WG needs to consider solutions to
the problem of CCSDS running out of assignable SCIDs. Some immediate thoughts
come to mind in how to increase the SCID assignment pool:</font>
<ul>
<li><font size=3 face="Calibri">Short term: Have each agency poll it</font><font size=2 face="Calibri">’</font><font size=3 face="Calibri">s
missions to return SCID assignments no longer in use.</font>
<li><font size=3 face="Calibri">Longer term: Adopt USLP which increases
the size of the SCID to at least 13 bits and does away with multiple SCID
assignments due to use (Telemetry, Telecommand, Proximity).</font></ul><font size=3>I
look forward to continuing this dialog with you after the holiday.</font>
<br><font size=3>Happy holidays to all !</font>
<br>
<br><font size=3>Greg </font>
<br><font size=3>Chairman CCSDS SLS-SLP WG</font><tt><font size=2>_______________________________________________<br>
Sls-slp mailing list<br>
Sls-slp@mailman.ccsds.org<br>
</font></tt><a href="http://mailman.ccsds.org/mailman/listinfo/sls-slp"><tt><font size=2>http://mailman.ccsds.org/mailman/listinfo/sls-slp</font></tt></a><tt><font size=2><br>
</font></tt>
<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>