<font size=2 face="sans-serif">Dear Peter,</font>
<br><font size=2 face="sans-serif"> it
looks as the comments provided in the attached mail on July 12 have been
overlooked.</font>
<br><font size=2 face="sans-serif">Ciao</font>
<br>
<br><font size=2 face="sans-serif">Gian Paolo</font>
<br>
<br>
<br><font size=1 color=#800080 face="sans-serif">----- Forwarded by Gian
Paolo Calzolari/esoc/ESA -----</font>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">Gian.Paolo.Calzolari@esa.int</font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">"CCSDS CESG --"
<cesg@mailman.ccsds.org></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Cc:
</font><font size=1 face="sans-serif">"Tom Gannett"
<thomas.gannett@tgannett.net>, Enrico.Vassallo@esa.int, "SANA
Steering Group\(SSG\)" <ssg@mailman.ccsds.org></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">12/07/2016 11:43</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">Re: [CESG] SEA
Resolution SEA-R-2016-07-001: Request publication of revised CCSDS SCID
Code Assignment Control Procedures</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Sent by:
</font><font size=1 face="sans-serif">"CESG"
<cesg-bounces@mailman.ccsds.org></font>
<br>
<hr noshade>
<br>
<br>
<br><font size=2 face="sans-serif">Dear Peter,</font><font size=3> </font><font size=2 face="sans-serif"><br>
I passed the document to Enrico that had a
quick look at it with the result given by the attached comments to be considered
at the appropriate point in time with respect to Poll Preatation, Agency
Review or other.</font><font size=3> <br>
</font><font size=2 face="sans-serif"><br>
Thanks to Enrico and best regards to everybody</font><font size=3> <br>
</font><font size=2 face="sans-serif"><br>
Gian Paolo</font><font size=3> <br>
</font><font size=2 face="sans-serif"><br>
--------------------------------------------------------------------------------------------------------------</font><font size=3>
<br>
</font><font size=2 face="sans-serif"><br>
1) Ka-band missing frequency range in Table 2</font><font size=3> </font>
<table width=616 style="border-collapse:collapse;">
<tr valign=top height=8>
<td width=193 style="border-style:none solid none none;border-color:#000000;border-width:0px 1px 0px 0px;padding:1px 1px;"><font size=3>Ka-Band
SRS or EES <b>27-40 GHz</b> </font>
<td width=156 style="border-style:none solid none solid;border-color:#000000;border-width:0px 1px 0px 1px;padding:1px 1px;"><font size=3 color=blue face="Times New Roman">25.5
- 27 GHz</font><font size=3> </font>
<td width=37 style="border-style:none solid none solid;border-color:#000000;border-width:0px 1px 0px 1px;padding:1px 1px;"><font size=3 face="Times New Roman">Ka-NE</font><font size=3>
</font>
<td width=163 style="border-style:none solid none solid;border-color:#000000;border-width:0px 1px 0px 1px;padding:1px 1px;"><font size=3 face="Times New Roman">31.8
– 32.3 GHz</font><font size=3> </font>
<td width=51 style="border-style:none none none solid;border-color:#000000;border-width:0px 0px 0px 1px;padding:1px 1px;"><font size=3 face="Times New Roman">Ka-DS</font></table>
<br><font size=3><br>
</font><font size=2 face="sans-serif"><br>
I suggest adding an additional line as:</font><font size=3> <br>
</font>
<table width=616 style="border-collapse:collapse;">
<tr valign=top height=8>
<td width=198 style="border-style:none solid none none;border-color:#000000;border-width:0px 1px 0px 0px;padding:1px 1px;"><font size=3>Ka-Band
SRS <b><br>
27-40 GHz</b> </font>
<td width=159 style="border-style:none solid none solid;border-color:#000000;border-width:0px 1px 0px 1px;padding:1px 1px;"><font size=3 color=blue face="Times New Roman">37.0-38.0
GHz</font><font size=3> </font>
<td width=38 style="border-style:none solid none solid;border-color:#000000;border-width:0px 1px 0px 1px;padding:1px 1px;"><font size=3 face="Times New Roman">Ka</font><font size=3>
</font>
<td width=166 style="border-style:none solid none solid;border-color:#000000;border-width:0px 1px 0px 1px;padding:1px 1px;"><font size=3 color=blue face="Times New Roman">37.0-38.0
GHz</font><font size=3> </font>
<td width=38 style="border-style:none none none solid;border-color:#000000;border-width:0px 0px 0px 1px;padding:1px 1px;"><font size=3 face="Times New Roman">Ka</font></table>
<br><font size=3><br>
</font><font size=2 face="sans-serif"><br>
This allocation can be used for both NE and DS missions so I suggest calling
it simply Ka. Please note that I do not know what the color code in table
2 means (some frequencies in blue...)</font><font size=3> <br>
</font><font size=2 face="sans-serif"><br>
2) Statement below table 2</font><font size=3> <br>
</font><font size=2 face="sans-serif"><br>
Replace allocated by assigned and allocation by assignment (they
have different meanings in ITU).</font><font size=3> <br>
</font><font size=2 face="sans-serif"><br>
From:</font><font size=3> <br>
</font><font size=3 face="Times New Roman"><br>
The SCID assignment procedures require that each registered spacecraft
specify the one (or more) frequency bands that they have been allocated
by their agency spectrum manager. It is expected that every spacecraft,
early in its development process, will acquire a frequency allocation for
uplink and downlink. The assignment of one or more GSCIDs will be
done relative to the number of frequency bands that a spacecraft uses,
but every attempt will be made to assign the same SCID in all bands if
that is possible.</font><font size=3> <br>
</font><font size=2 face="sans-serif"><br>
To:</font><font size=3> <br>
</font><font size=3 face="Times New Roman"><br>
The SCID assignment procedures require that each registered spacecraft
specify the one (or more) frequency bands that they have been assigned
by their agency spectrum manager. It is expected that every spacecraft,
early in its development process, will acquire a frequency assignment for
uplink and downlink. The assignment of one or more GSCIDs will be
done relative to the number of frequency bands that a spacecraft uses,
but every attempt will be made to assign the same SCID in all bands if
that is possible.</font><font size=3> <br>
</font><font size=2 face="sans-serif"><br>
3) SCID request form (non normative)</font><font size=3> <br>
</font><font size=2 face="sans-serif"><br>
The given print out in old Annex A provided as example shows that the exact
frequencies have to be entered differently from the rest of the document
specifying only the frequency bins. It is believed that many agencies would
not like to have the exact frequencies in a SANA on-line database. Therefore,
the form even if called example should be adjusted to align with the text:</font><font size=3>
</font>
<br><font size=3 face="Times New Roman">NOTE - The form requests only the
frequency bands, it does not require the exact operating frequencies. As
long as the same VN and FB is used for uplink and downlink only one GSCID
need be assigned. </font><font size=3> <br>
</font><font size=2 face="sans-serif"><br>
Alternatively, the example shall be deleted.</font><font size=3> <br>
</font><font size=2 face="sans-serif"><br>
4) Editorials</font><font size=3> <br>
</font><font size=2 face="sans-serif"><br>
In Table 2, EES shall be replaced by EESS (occurs twice). </font><font size=3><br>
</font><font size=2 face="sans-serif"><br>
ITC shall be changed to ITU in Annex A. </font><font size=3><br>
</font><font size=2 face="sans-serif"><br>
In ITU, the T stands for Telecommunication (singular). In the magenta book
all occurrences are in plural. </font><font size=3><br>
</font><font size=2 face="sans-serif"><br>
WRC in Annex A is spelled out as Radiocommunications (plural) whereas it
is singular.</font><font size=3> <br>
<br>
<br>
</font>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">"Shames, Peter
M (312B)" <peter.m.shames@jpl.nasa.gov></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">"CCSDS Secretariat"
<secretariat@mailman.ccsds.org>, "Tom Gannett" <thomas.gannett@tgannett.net></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Cc:
</font><font size=1 face="sans-serif">"SANA Steering
Group\(SSG\)" <ssg@mailman.ccsds.org>, "CCSDS Engineering
Steering Group - CESG Exec" <cesg@mailman.ccsds.org></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">23/09/2016 23:46</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">[CESG] SEA Resolution
SEA-R-2016-09-001: Request Agency Review for publication of revised CCSDS
SCID Code Assignment Control Procedures</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Sent by:
</font><font size=1 face="sans-serif">"CESG"
<cesg-bounces@mailman.ccsds.org></font>
<br>
<hr noshade>
<br>
<br><font size=4 face="Calibri">[attachment "320x0b6c1_mods_7-23Sep16.docx"
deleted by Gian Paolo Calzolari/esoc/ESA] </font>
<br>
<br><font size=4 face="Calibri">Dear CCSDS Secretariat,</font>
<br><font size=4 face="Calibri"> </font>
<br><font size=4 face="Calibri">Please find attached the SEA resolution
concerning the request for Agency Review for publication of the revised
CCSDS SCID Code Assignment Control Procedures Magenta Book. The major
changes are the inclusion of frequency band bins for allocation of Qualified
SCID (Q-SCID), references to the new registries defined in the RMP, and
re-classifying the document as a Magenta Book based upon its type.</font>
<br><font size=4 face="Calibri"> </font>
<br><font size=4 face="Calibri">This fixes all of the conditions raised
in the earlier CESG vote and the CMC feedback that we also received.
There are no remaining conditions that I am aware of aside from the one
requesting that this document be given an Agency review because it is a
major change to a key document and has an effect on the Agency procedures
for requesting and relinquishing SCIDs. In accordance with
one CMC condition it does not require the specification of uplink and downlink
<b><i>frequencies</i></b>, but it does require correct specification of
the uplink and downlink <b><i>frequency bands</i></b>, aligned to the actual
frequency ranges and not just to some colloquial use of, for example, "K-band"
when the actual frequency in use falls into the X-band range. </font>
<br><font size=3 face="Calibri"> </font>
<br><font size=4 face="Calibri">Thanks, Peter</font>
<br><font size=4 face="Calibri"> </font>
<br><font size=4 face="Calibri">==========================================================================</font>
<br><font size=4 face="Calibri"> </font>
<br><font size=4 face="Calibri"><b>SEA-R-2016-09-001 Request Agency
Review of revised CCSDS SCID Code Assignment Control Procedures</b></font>
<br><font size=4 face="Calibri">--------------------------------------------------------------------------------</font>
<br><font size=4 face="Calibri"> </font>
<br><font size=4 face="Calibri">The <b>System Engineering Area,</b></font>
<br><font size=4 face="Calibri"> </font>
<br><font size=4 face="Calibri"><b>CONSIDERING</b> that:</font>
<br><font size=4 face="Calibri"> </font>
<br><font size=4 face="Calibri">The SEA SANA Steering Group (SSG) has produced
a revision of the existing Blue Book called the CCSDS GLOBAL SPACECRAFT
IDENTIFIER FIELD:</font>
<br><font size=4 face="Calibri">CODE ASSIGNMENT CONTROL PROCEDURES (CCSDS
320.0-B-6), and that</font>
<br><font size=4 face="Calibri">The source document, CCSDS 320.0-B-1, was
originally directly published as a CMC Blue Book document, and that</font>
<br><font size=4 face="Calibri">The specific major changes to the document
have already been reviewed and agreed to by the CESG and CMC, and that</font>
<br><font size=4 face="Calibri">All of the requested updates have been
made to satisfy the identified conditions.</font>
<br><font size=4 face="Calibri"> </font>
<br><font size=4 face="Calibri">And <b>RECOGNIZING</b> that: </font>
<br><font size=4 face="Calibri"> </font>
<br><font size=4 face="Calibri">A CCSDS Area Director is responsible for
requesting CESG concurrence prior to publication, and that</font>
<br><font size=4 face="Calibri">The CCSDS Organization and Processes (A02.1-Y-4
cor 2) in Section 6.2.2.2 requests that the AD forward the draft documents
to the CESG, and</font>
<br><font size=4 face="Calibri">notify the Chief Technical Editor.</font>
<br><font size=4 face="Calibri"> </font>
<br><font size=4 face="Calibri">And <b>RECOGNIZING</b> that:</font>
<br><font size=4 face="Calibri"> </font>
<br><font size=4 face="Calibri">The CCSDS Organization and Processes (A02.1-Y-4
cor 2) in Section 6.1.4.3 defines this type of book (a process or procedure
description) as a Magenta Book, and that</font>
<br><font size=4 face="Calibri">Sec 6.2.7 requires periodic review and
re-confirmation of Normative Track documents.</font>
<br><font size=4 face="Calibri"> </font>
<br><font size=4 face="Calibri"><b>RESOLVES</b> to request:</font>
<br><font size=4 face="Calibri"> </font>
<br><font size=4 face="Calibri">That the Chief Technical Editor ready the
document for review, and that</font>
<br><font size=4 face="Calibri">The document be re-classified as a Magenta
Book, to properly characterize it based on its contents, and that</font>
<br><font size=4 face="Calibri">The Secretariat create the necessary CESG
poll to request the CESG review and approve release of this document for
Agency Review, and that</font>
<br><font size=4 face="Calibri">Once the CESG poll succeeds that the CMC
be polled to approve the document for Agency Review.</font>
<br><font size=4 face="Calibri"> </font>
<br><font size=4 face="Calibri"> </font>
<br><font size=4 face="Calibri"> </font><tt><font size=2>_______________________________________________<br>
CESG mailing list<br>
CESG@mailman.ccsds.org<br>
</font></tt><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg"><tt><font size=2>https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg</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>