<html 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="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@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:Aptos;
panose-1:2 11 0 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:12.0pt;
font-family:"Aptos",sans-serif;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
font-size:12.0pt;
font-family:"Aptos",sans-serif;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Aptos",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:738331978;
mso-list-type:hybrid;
mso-list-template-ids:1700970934 67698705 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style>
</head>
<body lang="EN-US" link="#467886" vlink="#96607D" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">Dear Ignacio, SLS WG chairs, and CESG,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">The issue of us running out of AOS SCID namespace, particularly in the crowded X-Band, was forecast for a few years now. We bought some time by “putting a bandage” on the problem and allocating SCIDs in frequency
bins, but even that has now been over-run and <b><i>the SANA is actually having to turn away SCID requests because the namespace is all used up. See attached email.</i></b><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">I know you are aware of this.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">I know that there are several different options that are in discussion, some much more feasible than others.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">I wish to urge you to bring this matter to closure during this meeting. This has already affected our users and that is not good for our reputation as a forward looking organization.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">I do have some comments about the options. Some of the proposed options involve augmenting the SANA registries by adding entirely new fields, such as using the coding, modulation, and other low level S/C
comm characteristics. I wish to argue strongly against this approach, for the following reasons:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1"><span style="font-size:11.0pt">This would require major re-engineering of all of the SCID & Spacecraft registries, which is a major impact on the SANA and a source of delay.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1"><span style="font-size:11.0pt">More importantly, we do not have this information at hand, it is not part of the usual SCID submissions, so gathering it will be time consuming and difficult
(based on our prior experiences with requests for other added information). This will be a large source of delay.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1"><span style="font-size:11.0pt">Even more importantly, these parameters are typically not fixed and singular for any given spacecraft. Many spacecraft design in and use more than one
modulation and coding, some have large tables of different combinations for different apertures. As a consequence, this approach will just not work as a discriminator.<o:p></o:p></span></li></ol>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">We know that there will be “knock-on” impacts from the proposal to use the spare bits in the AOS header. It will require changes in the radios and in the ground systems. But it will actually give us an approach
that will be relatively easy to implement in the SANA and in our procedures. More importantly, it will give us an approach that will work to discriminate clearly, at the link layer protocol, among different spacecraft.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">With any of these options it does appear that operational coordination will still be required, especially at the crowded polar regions, but none of these solutions will have any impact on that.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">We all know that the longer term solution for this is to get missions to adopt USLP. And we must keep pushing in that direction for any number of different reasons. But we must solve this issue now, and
as quickly as possible.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Best regards, Peter<o:p></o:p></span></p>
<div>
<div style="border:none;border-bottom:double windowtext 2.25pt;padding:0in 0in 1.0pt 0in">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#212121"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Peter Shames</span><span style="font-size:11.0pt;color:#212121"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Consultative Committee for Space Data Systems (CCSDS)</span><span style="font-size:11.0pt;color:#212121"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Systems Engineering Area Director</span><span style="font-size:11.0pt;color:#212121"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Jet Propulsion Laboratory / Interplanetary Network Directorate</span><span style="font-size:11.0pt;color:#212121"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">4800 Oak Grove Drive</span><span style="font-size:11.0pt;color:#212121"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">MS 301-490</span><span style="font-size:11.0pt;color:#212121"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Pasadena, CA 91109</span><span style="font-size:11.0pt;color:#212121"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> </span><span style="font-size:11.0pt;color:#212121"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><a href="mailto:peter.m.shames@jpl.nasa.gov" title="mailto:peter.m.shames@jpl.nasa.gov"><span style="color:#0563C1">peter.m.shames@jpl.nasa.gov</span></a></span><span style="font-size:11.0pt;color:#212121"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">C: 818-687-7901</span><span style="font-size:11.0pt;color:#212121"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><a href="https://urldefense.us/v3/__https:/cwe.ccsds.org/sea/default.aspx__;!!PvBDto6Hs4WbVuu7!fgncIVD-iu0I_1xWlmq78lUqf1aK_WZzB2gUhx7cfOlLefMQluIGVhXTKIrzYkYoUsYraXcV$" title="https://urldefense.us/v3/__https:/cwe.ccsds.org/sea/default.aspx__;!!PvBDto6Hs4WbVuu7!fgncIVD-iu0I_1xWlmq78lUqf1aK_WZzB2gUhx7cfOlLefMQluIGVhXTKIrzYkYoUsYraXcV$"><span style="color:#0563C1">https://cwe.ccsds.org/sea/default.aspx</span></a></span><span style="font-size:11.0pt;color:#212121"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#212121"> <o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div id="mail-editor-reference-message-container">
<div>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="color:black">From:
</span></b><span style="color:black">Space Assigned Number Authority <info@sanaregistry.org><br>
<b>Date: </b>Thursday, October 24, 2024 at 5:57</span><span style="font-family:"Arial",sans-serif;color:black"> </span><span style="color:black">AM<br>
<b>To: </b>Shames, Peter M (US 9740) <peter.m.shames@jpl.nasa.gov><br>
<b>Cc: </b>info@sanaregistry.org <info@sanaregistry.org>, Lux, Jim (US 3370) <james.p.lux@jpl.nasa.gov>, Shannon Rodriguez <shannon.rodriguez-1@nasa.gov><br>
<b>Subject: </b>[EXTERNAL] SCID V2 X-Band depletion<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:11.0pt">Dear Peter and all,<br>
In the past few weeks we got many SCID requests, among which most <br>
required X-Band V2.<br>
Due to the SCID depletion, we are not able to allocate most of the new <br>
requests. Do you think a solution will be found during the upcoming CCSDS?<br>
<br>
-- <br>
Best regards,<br>
Julien Bernard<br>
Space Assigned Numbers Authority<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</body>
</html>