<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: 14px; font-family: Calibri, sans-serif;">
<div>Dear Jean-Marc,</div>
<div><br>
</div>
<div>I agree completely that this is not a settled issue by any means, and I am glad that you and Osvaldo are engaged more actively in the discussion. As I noted, this has been discussed for some time, but this is the first effort to try and come to terms
with it and to actually identify a workable solution. I believe that open dialogue is essential, since this ultimately affects all agencies (and other organizations) who use CCSDS standards.</div>
<div><br>
</div>
<div>Once we identify an agreed path forward we must then, as quickly as we can, get all of the involved elements (registries, documents, procedures), revised so that everyone knows what to expect. In the meantime I think we are in a transitional state where
we really must retain as much of the limited “SCID namespace” as we can in order to not find ourselves at an abruopt halt when we run out of available numbers.</div>
<div><br>
</div>
<div>Other comments are in-line, below.</div>
<div><br>
</div>
<div>Very best regards, Peter</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>Jean-Marc Soula <<a href="mailto:Jean-Marc.Soula@cnes.fr">Jean-Marc.Soula@cnes.fr</a>><br>
<span style="font-weight:bold">Date: </span>Wednesday, July 29, 2015 at 10:49 AM<br>
<span style="font-weight:bold">To: </span>Peter Shames <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>>, "<a href="mailto:osvaldo.peinado@dlr.de">osvaldo.peinado@dlr.de</a>" <<a href="mailto:osvaldo.peinado@dlr.de">osvaldo.peinado@dlr.de</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>RE: AW: [SANA #5270] AW: SCID assignments<br>
</div>
<div><br>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div 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="http://www.w3.org/TR/REC-html40">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@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:"Book Antiqua";
panose-1:2 4 6 2 5 3 5 3 3 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
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;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Texte de bulles Car";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.TextedebullesCar
{mso-style-name:"Texte de bulles Car";
mso-style-priority:99;
mso-style-link:"Texte de bulles";
font-family:"Tahoma","sans-serif";}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Bonjour à tous,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">I share the Oswaldo’s concern on which explanations or which solutions may be offered by CCSDS to the projects requesting multiple SCId and being
rejected for those assets pertaining to the simulator / tester … category.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">I understand the rules have changed (and I do not object the arguments for that) but the procedures were not yet revised (the abstracted blue text
below clearly shows that simulators / testers were valid assets to obtain a SCId) … nor alternate solutions are offered (which we should discuss further now).<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
</div>
</div>
</div>
</blockquote>
</span>
<div><br>
</div>
<div>You are correct in that the current, published, SCID document does not discriminate against simulators nor testers. And yet we have this problem that we must resolve in some way that does not halt the ability of new spacecraft to be flown, by as many
different users as can be accommodated. In the immediate term the only way that I can see to handle this is to only give out new (or re-cycled) SCIDs to the real spacecraft. Your support for a set of registries sorted by frequency, and inclusion of a "Frequency
= none” category may be a rapid way forward.</div>
<div><br>
</div>
<div>I think we can, through discussion, arrive at an agreed recommendation to agencies re how to deal with the similator / tester issue. I hope that this is the start of an active discussion where we try and arrive at that agreement, because so far the discussion
jhas ben of the nature “We have a problem ….. What do we do?"</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div 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="http://www.w3.org/TR/REC-html40">
<div lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">In CNES we also have several projects for which simulators have been assigned a SCId, different from the one assigned to the SC.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Some more may come soon with similar requirements…<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
</div>
</div>
</div>
</blockquote>
</span>
<div><br>
</div>
<div>I hope that is sufficient motivation to have you and your staff, among others from different agencies, get engaged in the discussion.</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div 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="http://www.w3.org/TR/REC-html40">
<div lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">CCSDS should offer a workaround way to answer these requests and not just reject the request because of the lack of Ids.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
</div>
</div>
</div>
</blockquote>
</span>
<div>I agree we need a work-around. And I think we need to find one quickly and document it.</div>
<div><br>
</div>
<div>Meanwhile, if we do not modulate requests for multiple SCIDs what is to stop anyone from requesting several SCIDs for one spacecraft and using up what little resource we have left?</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div 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="http://www.w3.org/TR/REC-html40">
<div lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Out of your list of activities below, Peter, I see Number 3 as quite promising in terms of solving our SCId capacity issue, but I am not 100% sure
if Number 4 could be another solution or not.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">In more details:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Number 3: if SANA may allocate the same SCId to several missions, based on the frequency discrimination, the issue of the testers / simulators may
be solved as they fall in the category “no radiation” (meaning “no frequency”). Frequencies are already part of the SCId request form and the information is already available for a majority of missions (I hope).<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
</div>
</div>
</div>
</blockquote>
</span>
<div>You are correct, but we seem to have a bit of an issue. While the transmitting frequencies (TM & TC) are on the form (<a href="http://sanaregistry.org/cgi/spacecraftid">http://sanaregistry.org/cgi/spacecraftid</a>) they do not appear in the available
database in SANA (<a href="http://sanaregistry.org/r/spacecraftid/spacecraftid.html">http://sanaregistry.org/r/spacecraftid/spacecraftid.html</a>). We will have to check with the SANA operator to see if this information is, in fact, in the database but is
just hidden in what is displayed. We will also have to accommodate spacecraft that use more than one frequency, as in S / X or X / Ka. I do not know that the database in its current form accommpodates that.</div>
<div><br>
</div>
<div>As you suggest, perhaps we can, for a while, adopt that “no frequency” approach and still manage the simulator / tester assignments within SANA. I think that is an interesting approach to discuss.</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div 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="http://www.w3.org/TR/REC-html40">
<div lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Number 4: I saw a lot of emails on registries but could not spend enough time with them to be sure of the meaning of “Object Id (OId)” and how it
may be used in practice to differentiate the assets of a same satellite project and the assets of multiple projects between them. It could be, assuming some verifications, that the OID is another way to allow SANA to allocate several times the same SCId to
several missions, based on the OID discrimination this time. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
</div>
</div>
</div>
</blockquote>
</span>
<div><br>
</div>
<div>The concept of the OID is an ISO construct that the Cross Support Services area first started to use. It is a tree structured name space where “CCSDS” (ISO OID = 1.3.112.4) forms the base of the tree and we then get to determine which classes of objects
we will assign unique numbers to. A proposal for how to manage that namespace is in the draft Registry Policy document and there is an information model for it as well. Both are attached here. What has been proposed is that there is a branch of the OID
tree for spacecraft, and that every spacecraft, simulator, or tester would have a unique SCID assigned. That Spacecraft OID, as proposed, is just a number, of the form 1.3.112.4.7.nnn. This OID is assigned when any registeration request is made and it remains
associated with that spacecraft forever. In that way it can be used to unambiguously tag the spacecraft data and allows the SCIDs to just be used on the transmitted spacelink.</div>
<div><br>
</div>
<div>The rest of the Spacecraft information will be stored in the Spacecraft database, as it is now, along with the SCID (during the valid period) and the OID (which is permanent). The model of the spacecraft database is also attached for reference. Most
of these fields are in the current database, but any shown in red are newly added. It does occur to me now that we will probably need to add both transmitting and receiving frequencies, and to add the ability to have a spacecraft with multiple frequency bands.
</div>
<div><br>
</div>
<div>So if we adopt some such approach I agree that we can re-allocate the same SCID, using the Version Number (protocol type) and Frequency(s). On the ground we can use just the OID as a unique identifier since it is permanent. But unless there is a way
to adopt the OID on the spacelink I do not think that gives us any discrimination in radiated space communication.</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div 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="http://www.w3.org/TR/REC-html40">
<div lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Those two options should be explored quickly, and I believe this is the idea in the messages below, to confirm that the activity Number 2 may be cancelled
and there is enough room then to continue the allocation to simulators / testers.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Does it make sense ?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
</div>
</div>
</div>
</blockquote>
</span>
<div><br>
</div>
<div>Based on this discussion, and if others agree with the use of frequency band (including = none) , then I think that we could continue to use the SANA to regsiter simulators and testers, as long as we can use that distinction as well. For that matter,
since these simulators and testers will each belong to some single organization that “owns” that asset you could even imagine a “Frequency = None” namespace on a per agency / organization basis. There is no fear then of collisions in communications and the
OID can be used for unambiguous identification of datasets. It is a little more complicated than what we now do, but it is quite “future proof” and avoids any risk of ambiguity.</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div 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="http://www.w3.org/TR/REC-html40">
<div lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">In any case, one criteria to decide is how long it may take to put a solution in place.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">If too long, then we have a risk of overflow on the SCIds in the meantime ; if doable in a reasonable time span, it would be a pity to have rejected
some requests for SCIds and have a solution for them a few months later…</span></p>
</div>
</div>
</div>
</blockquote>
</span>
<div><br>
</div>
<div>I agree, but contingent on getting rapid agreement on having a “Frequency = none” SCID registry immediately set up, either on a global basis or on an agency / organization basis. Does that sound agreeable to you (and others)? </div>
<div><br>
</div>
<div>I think, for practicality, that we also need to reach agreement on a set of SCID registries separated by frequency band (including None) so that we can immediately re-gain some SCID breathing room/ </div>
<div><br>
</div>
<div>Does that sound workable as well? </div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div 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="http://www.w3.org/TR/REC-html40">
<div lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">So my recommendation would be to work on activities 3 or 4, with the objective not to apply number 2.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Of course activities number 1 and 5 should continue, with less pressure on number1 if a solution is found … and no pressure on number 5 which anyway
is a long term and maybe not a global solution.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">For further discussions I believe…<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
</div>
</div>
</div>
</blockquote>
</span>
<div><br>
</div>
<div>Yes. Indeed.</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div 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="http://www.w3.org/TR/REC-html40">
<div lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Best regards<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><i><span style="font-size: 10pt; font-family: 'Book Antiqua', serif; color: rgb(31, 73, 125);">Jean-Marc Soula</span></i><span style="color:#1F497D"><br>
</span><i><span style="font-size: 10pt; font-family: 'Book Antiqua', serif; color: rgb(31, 73, 125);">CNES - DCT/OP/C-STA</span></i><span style="color:#1F497D"><br>
</span><i><span style="font-size: 10pt; font-family: 'Book Antiqua', serif; color: rgb(31, 73, 125);">Advisor, GN Operations</span></i><span style="color:#1F497D"><br>
</span><i><span style="font-size: 10pt; font-family: 'Book Antiqua', serif; color: rgb(31, 73, 125);">18 Avenue Edouard Belin</span></i><span style="color:#1F497D"><br>
</span><i><span style="font-size: 10pt; font-family: 'Book Antiqua', serif; color: rgb(31, 73, 125);">31401 Toulouse Cedex 9 - France</span></i><span style="color:#1F497D"><br>
</span><i><span style="font-size: 10pt; font-family: 'Book Antiqua', serif; color: rgb(31, 73, 125);">Tel.: +33 (0)5 61 2 74647</span></i><span style="color:#1F497D"><br>
</span><i><span style="font-size: 10pt; font-family: 'Book Antiqua', serif; color: rgb(31, 73, 125);">Fax.: +33 (0)5 61 2 73135</span></i><span style="color:#1F497D"><br>
</span><i><span style="font-size: 10pt; font-family: 'Book Antiqua', serif; color: rgb(31, 73, 125);">Email:
<a href="mailto:Jean-Marc.Soula@cnes.fr">Jean-Marc.Soula@cnes.fr</a></span></i></p>
</div>
</div>
</div>
</blockquote>
</span>
<div><br>
</div>
<div>Best regards, Peter</div>
<div><br>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div 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="http://www.w3.org/TR/REC-html40">
<div lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D"></span><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"><o:p></o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="FR" style="font-size: 10pt; font-family: Tahoma, sans-serif;">De :</span></b><span lang="FR" style="font-size: 10pt; font-family: Tahoma, sans-serif;">
<a href="mailto:ssg-bounces@mailman.ccsds.org">ssg-bounces@mailman.ccsds.org</a> [<a href="mailto:ssg-bounces@mailman.ccsds.org">mailto:ssg-bounces@mailman.ccsds.org</a>]
<b>De la part de</b> Shames, Peter M (312B)<br>
<b>Envoyé :</b> mercredi 29 juillet 2015 18:18<br>
<b>À :</b> <a href="mailto:osvaldo.peinado@dlr.de">osvaldo.peinado@dlr.de</a><br>
<b>Cc :</b> CCSDS Engineering Steering Group - CESG Exec; SANA Steering Group (SSG)<br>
<b>Objet :</b> [SSG] Re: AW: [SANA #5270] AW: SCID assignments<br>
<b>Importance :</b> Haute<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">Dear Osvaldo,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">As I think you are aware, the CCSDS is in danger of running out of available spacecraft ID (SCID) numbers. You could say that we are now being hurt by our
own success because there are so many spacecraft using CCSDS data link and related standards that we no longer can assign a SCID for the spacecraft, the simulator, and other possible “flight-less birds”.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">In the current SCID document, CCSDS 320.0-B-6C1, we have this statement (<b><u>emphasis added</u></b>):<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<blockquote style="margin-left:30.0pt;margin-right:0cm">
<div>
<p class="MsoNormal"><b><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: blue;">Section 2.1 Purpose of the CCSDS SCID</span></b><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
</blockquote>
<div>
<blockquote style="margin-left:30.0pt;margin-right:0cm">
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: blue;">Because the SCID field is only eight or ten bits long, the SCID is not intended to provide unique identification for all times. </span><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: blue;"> It is inevitable that the SCIDs will have to be reused;
<b><u>however, at any one time, the number of vehicles under simulation, </u></b></span><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><b><u><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: blue;">test, or active operational control is not anticipated to exceed the available numbering domains</span></u></b><u><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: blue;">.</span></u><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
</blockquote>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">Clearly this is no longer the case and the SSG, SLS and CESG have been discussing this for at least the last three meetings. There are several loosely coordinated
activities which are now in process that relate to this:<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<blockquote style="margin-left:30.0pt;margin-right:0cm">
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">1) We have requested the Agency Representatives to relinquish all assigned SCIDs for spacecraft that are no longer operational. This has been somewhat successful,
but we need to do it again.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">2) We are in the process of revising the SCID assignment procedures to no longer allow assignment of multiple SCID for a spacecraft (simulators, testers, etc)<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">3) We are considering the use of frequency separation as well as the current Version Number (VN) separation that is now in use. This could relatively easily
increase the number assignment space.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">4) Under the new registry approach that is now in discussion we will be assigning unique, permanent, object identifiers (OID) to all spacecraft, similators,
flightless birds, etc. These will persist through time.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">5) We are working on a new protocol, USLP, with a larger SCID number space.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">We have not yet discussed in any depth what recommendation we can make to organizations who wish to have a separate, unique, SCID that they can use internally
to distinguish the spacecraft from any other simulators or test gigs. Clearly this is a concern, but it is may be treated as an internal issue that can be managed locally. It does not have the same potential for cross agency impact because any such signals
will not be broadcast.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">If you (or anyone else on this thread) has any other ideas or wishes to contribute to the discussion please do so. I think that this is an important enough
issue for us to work quickly (as quickly as CCSDS can move) to come up with a resolution.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">Best regards, Peter<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">On 7/29/15, 7:43 AM, "<a href="mailto:osvaldo.peinado@dlr.de">osvaldo.peinado@dlr.de</a>" <<a href="mailto:osvaldo.peinado@dlr.de">osvaldo.peinado@dlr.de</a>>
wrote:<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<blockquote style="border:none;border-left:solid #B5C4DF 4.5pt;padding:0cm 0cm 0cm 4.0pt;margin-left:3.75pt;margin-right:0cm" id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE">
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">Dear Audric,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">I know about the problem of SCIDs becoming rare.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">You can process the satellite one, and discard the SIM one, BUT ....I need to have for the project anyways and official answer from SANA.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">It should be possible to inform the users about the situation and in case of rejecting a request indicate a reference to a document and to propose a solution,
like "use the same ID as the Spacecraft or something that you like, because your system is a closed one", as example , can you do that?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">I have another question:<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">I need to submit a request for another Satellite and it looks like the link to do the request from the SANA page simply disappear, it is only an E-mail.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">It is that correct?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">Thanks and best Regards<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">O. Peinado<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">-----Ursprüngliche Nachricht-----<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">Von: SANA [<a href="mailto:info@sanaregistry.org">mailto:info@sanaregistry.org</a>]
<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">Gesendet: Mittwoch, 29. Juli 2015 16:07<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">An: Peinado, Osvaldo Luis<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">Betreff: Re: [SANA #5270] AW: SCID assignments<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">Dear Mr. Peinado,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">We were waiting for the SSG answer before getting back to you and see if<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">you had any constraint on the two SCIDs being assigned at the same time<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">or not.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">If you tell us that we can go and process the non-sim request, we will<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">happily do that.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">Thank you.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">--
<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">Best regards,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">Audric Schiltknecht<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">Space Assigned Numbers Authority<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">Le 2015-07-29 09:47,
<a href="mailto:osvaldo.peinado@dlr.de">osvaldo.peinado@dlr.de</a> a écrit :<o:p></o:p></span></p>
</div>
<blockquote style="border:none;border-left:solid #B5C4DF 4.5pt;padding:0cm 0cm 0cm 4.0pt;margin-left:3.75pt;margin-right:0cm" id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE">
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">Dear Audrich<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">Thank you for your answer.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">I´m aware about the discussion about the SIM SCID and that till now is nothing written down to deal with it, but what happened with the SCID for the satellite?
<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">I sent two separate request.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">I do not see it also in the list of registry updates, why?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">Best Regards<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">Osvaldo<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">-----------------------------------<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">Dr. Osvaldo Peinado<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">Ground Operations Manager<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">German Space Operations Center (GSOC)<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">Tel: +49 8153 28 3010<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">Fax: +49 8153 28 1456<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">Mobile: +491729410099<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">German Aerospace Center (DLR)<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">Oberpfaffenhofen<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">82234 Wessling<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">Germany<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">-----Ursprüngliche Nachricht-----<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">Von: Space Assigned Numbers Authority [<a href="mailto:info@sanaregistry.org">mailto:info@sanaregistry.org</a>]
<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">Gesendet: Dienstag, 28. Juli 2015 22:35<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">An: Peinado, Osvaldo Luis<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">Cc: Space Assigned Numbers Authority<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">Betreff: SCID assignments<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">Dear Mr. Peinado,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">SANA are currently discussing some issues regarding your recent SCID<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">requests with the SSG (Sana Steering Group).<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">When all is sorted out, we will inform you of the result.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">Thank you for your understanding.<o:p></o:p></span></p>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
</span>
</body>
</html>