<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 12px; font-family: Courier, sans-serif;">
<div><br>
</div>
<div>All:</div>
<div><br>
</div>
<div>Peter Shames is trying to set up a telecon to discuss registries for assigning spacecraft identifiers in CCSDS.</div>
<div><br>
</div>
<div>Personally I think we are agnostic about the content/structure of the identifiers, but I thought I should ask you all...</div>
<div><br>
</div>
<div>David</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>"Shames, Peter M (312B)" <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>><br>
<span style="font-weight:bold">Date: </span>Tuesday, September 15, 2015 at 10:47 AM<br>
<span style="font-weight:bold">To: </span>Nestor Peccia <<a href="mailto:Nestor.Peccia@esa.int">Nestor.Peccia@esa.int</a>>, "Tai, Wallace S (9000)" <<a href="mailto:wallace.s.tai@jpl.nasa.gov">wallace.s.tai@jpl.nasa.gov</a>>, Gian Paolo Calzolari <<a href="mailto:Gian.Paolo.Calzolari@esa.int">Gian.Paolo.Calzolari@esa.int</a>>,
Gilles Moury <<a href="mailto:Gilles.Moury@cnes.fr">Gilles.Moury@cnes.fr</a>>, "<a href="mailto:Enrico.Vassallo@esa.int">Enrico.Vassallo@esa.int</a>" <<a href="mailto:Enrico.Vassallo@esa.int">Enrico.Vassallo@esa.int</a>>, "<a href="mailto:Massimo.Bertinelli@esa.int">Massimo.Bertinelli@esa.int</a>"
<<a href="mailto:Massimo.Bertinelli@esa.int">Massimo.Bertinelli@esa.int</a>>, "Kazz, Greg J (312B)" <<a href="mailto:greg.j.kazz@jpl.nasa.gov">greg.j.kazz@jpl.nasa.gov</a>>, "Lee, Dennis K (332G)" <<a href="mailto:dennis.k.lee@jpl.nasa.gov">dennis.k.lee@jpl.nasa.gov</a>>,
"Barkley, Erik J (3970)" <<a href="mailto:erik.j.barkley@jpl.nasa.gov">erik.j.barkley@jpl.nasa.gov</a>>, Marc Blanchet <<a href="mailto:marc.blanchet@viagenie.ca">marc.blanchet@viagenie.ca</a>>, David Berry <<a href="mailto:David.S.Berry@jpl.nasa.gov">David.S.Berry@jpl.nasa.gov</a>>,
Tom Gannett <<a href="mailto:thomas.gannett@tgannett.net">thomas.gannett@tgannett.net</a>><br>
<span style="font-weight:bold">Cc: </span>CCSDS Engineering Steering Group - CESG Exec <<a href="mailto:cesg@mailman.ccsds.org">cesg@mailman.ccsds.org</a>>, "SANA Steering Group (SSG)" <<a href="mailto:ssg@mailman.ccsds.org">ssg@mailman.ccsds.org</a>><br>
<span style="font-weight:bold">Subject: </span>Request for a SIG to discuss SCID "band" assignments<br>
</div>
<div><br>
</div>
<div>
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-family: Calibri, sans-serif;">
<div style="color: rgb(0, 0, 0); font-size: 14px;">Dear All,</div>
<div style="color: rgb(0, 0, 0); font-size: 14px;"><br>
</div>
<div style="color: rgb(0, 0, 0); font-size: 14px;">During our discussions in the SANA Steering Group (SSG) it has become clear that we really must do the work to arrive at a better policy for allocating Spacecraft Idenifiers (SCID). We are all aware that we
have been close to “exhausting” that number space for a while. Instead of just discussing it some more we wish to form a focused CCSDS Special Interest group for SCID Registry Assignments (SIG-SRA) to address this and to make a recommendation for CESG and
CMC approval. We believe that this SIG must contain people from key SLS WGs, from the CSS, possibly from the Nav WG, and from SEA. I am sending this specifically to those AD and WG chairs. If others from the CESG feel that they should have an active role
please signal your interest now.</div>
<div style="color: rgb(0, 0, 0); font-size: 14px;"><br>
</div>
<div style="color: rgb(0, 0, 0); font-size: 14px;">I think we can do this quickly, or as quickly as CCSDS can ever do anything, because there are only a limited number of viable approaches (short of defining a new protocol with a bigger number range). And
I think we should do it quickly because based on SANA Operator analysis and SSG discussions we clearly have a problem with at least one of the registries now.</div>
<div style="color: rgb(0, 0, 0); font-size: 14px;"><br>
</div>
<div style="color: rgb(0, 0, 0); font-size: 14px;">Can we schedule a telecon in early October to discuss this? I would like to try and get this moving well ahead of the working meetings. In this way if there are topics that do need further discussion in the
WGs that can happen then.</div>
<div style="color: rgb(0, 0, 0); font-size: 14px;"><br>
</div>
<div style="color: rgb(0, 0, 0); font-size: 14px;">The topics I think we need to address are these:</div>
<ol>
<li><font face="Calibri,sans-serif"><font>Revision of CCSDS policies</font></font></li><li><font>Use of “bands” to segregate S/C alocations</font></li><li><font>Relationship to spectrum assignments</font></li><li><font>Orbital / spatial segregation</font></li><li><font>and handling of S/C simulators</font></li></ol>
<div style="color: rgb(0, 0, 0); font-size: 14px;"><font face="Calibri" style="font-family: Calibri;">For topic 2 we have a proposal on the table to create “Band Bins” that might look like this:</font><span style="font-family: Calibri;"> </span></div>
<div style="color: rgb(0, 0, 0); font-size: 14px;"><br style="font-family: Calibri;">
<font face="Calibri" style="font-family: Calibri;"><span class="Apple-tab-span" style="white-space:pre"></span>· Everything below S-Band (HF, VHF, UHF, L) </font><span style="font-family: Calibri;"></span><font color="red" face="Calibri" style="font-family: Calibri;"><b>0-2
GHz</b></font><span style="font-family: Calibri;"> </span><br style="font-family: Calibri;">
<font face="Calibri" style="font-family: Calibri;"><span class="Apple-tab-span" style="white-space:pre"></span>· S-Band & C-Band </font><font color="red" face="Calibri" style="font-family: Calibri;"><b>2-8 GHz</b></font><span style="font-family: Calibri;"> </span><br style="font-family: Calibri;">
<font face="Calibri" style="font-family: Calibri;"><span class="Apple-tab-span" style="white-space:pre"></span>· X-Band </font><font color="red" face="Calibri" style="font-family: Calibri;"><b>8-12 GHz</b></font><span style="font-family: Calibri;"> </span><br style="font-family: Calibri;">
<font face="Calibri" style="font-family: Calibri;"><span class="Apple-tab-span" style="white-space:pre"></span>· K-Band (Ku, K, Ka)</font><font color="red" face="Calibri" style="font-family: Calibri;"><b>12-40 GHz</b></font><span style="font-family: Calibri;"> </span><br style="font-family: Calibri;">
<font face="Calibri" style="font-family: Calibri;"><span class="Apple-tab-span" style="white-space:pre"></span>· None or unstated</font><span style="font-family: Calibri;"></span>
<p style="font-family: Calibri;">For topic 3 we need to hear back from our RF & M experts and to learn if there is anything that we need to do in regards the spectrum and frequency groups. Are they considering anything to deal with these issues? Do they see
some other approach or some other issues?</p>
<p style="font-family: Calibri;">For topic 4 we may wish to consider what is effectively spatial or orbital and trajectory segregation. This clearly works for “proximity" links of various types, such as around Mars or the Moon, but it also provides suitable
isolation when “short-haul” links like 802.xx are used as well. But because all of these celestial objects are always in motion, and spatial domains will overlap at least some of the time, we might want to consider deep space bands separately from near
Earth (exploration) bands. This could lead to an even greater number of “Band Bins”. </p>
<p style="font-family: Calibri;">I do not know that we need additional “territorial distinctions”, at least for the next 20 years or so, unless we consider what might be called the “CubeSat explosion”. Perhaps someone from the RF&M or mission planning communities
could comment usefully on this?</p>
<p style="font-family: Calibri;">For topic 5 I think that we can just use the Band Bin = “none” approach from topic 2. Or we could even create a per agency registry of “not radiated” SCID numbers that SANA or the agencies themselves manage. I think that this
is really a pretty easy problem to solve, it is just a matter of the most effective way to do it. Given a “per agency” approach the only situation where there would be an issue would be for collaborative missions where the simulators from different agencies
are communicating.</p>
<p style="font-family: Calibri;">If anyone has other alternatives, considerations, or issues please bring them up using email. Unless there are strong objections to this whole approach I will propose a Doodle Poll to see if we can find a time in October to
have a telecon.</p>
<p style="font-family: Calibri;">Thanks, Peter</p>
<p style="font-family: Calibri;"><br>
</p>
<p style="font-family: Calibri;"><br>
</p>
<p style="font-family: Calibri;"><br>
</p>
<p style="font-family: Calibri;"><br>
</p>
<p style="font-family: Calibri;"><br>
</p>
<p style="font-family: Calibri;"><br>
</p>
</div>
</div>
</div>
</span>
</body>
</html>