<font size=2 face="sans-serif">Dear Peter,</font>
<br><font size=2 face="sans-serif"> 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>
<br>
<br><font size=2 face="sans-serif">Thanks to Enrico and best regards to
everybody</font>
<br>
<br><font size=2 face="sans-serif">Gian Paolo</font>
<br>
<br><font size=2 face="sans-serif">--------------------------------------------------------------------------------------------------------------</font>
<br>
<br><font size=2 face="sans-serif">1) Ka-band missing frequency range in
Table 2</font>
<br>
<table width=616 style="border-collapse:collapse;">
<tr valign=top height=8>
<td width=176 style="border-style:none solid none none;border-color:#000000;border-width:0px 1px 0px 0px;padding:0px 7px;"><font size=3 face="Times">Ka-Band
SRS or EES <b>27-40 GHz</b></font>
<td width=143 style="border-style:none solid none solid;border-color:#000000;border-width:0px 1px 0px 1px;padding:0px 7px;"><font size=3 color=blue face="Times New Roman">25.5
- 27 GHz</font>
<td width=35 style="border-style:none solid none solid;border-color:#000000;border-width:0px 1px 0px 1px;padding:0px 7px;"><font size=3 face="Times New Roman">Ka-NE</font>
<td width=149 style="border-style:none solid none solid;border-color:#000000;border-width:0px 1px 0px 1px;padding:0px 7px;"><font size=3 face="Times New Roman">31.8
– 32.3 GHz</font>
<td width=35 style="border-style:none none none solid;border-color:#000000;border-width:0px 0px 0px 1px;padding:0px 7px;"><font size=3 face="Times New Roman">Ka-DS</font></table>
<br>
<br><font size=2 face="sans-serif">I suggest adding an additional line
as:</font>
<br>
<br>
<table width=616 style="border-collapse:collapse;">
<tr valign=top height=8>
<td width=176 style="border-style:none solid none none;border-color:#000000;border-width:0px 1px 0px 0px;padding:0px 7px;"><font size=3 face="Times">Ka-Band
SRS </font>
<br><font size=3 face="Times"><b>27-40 GHz</b></font>
<td width=143 style="border-style:none solid none solid;border-color:#000000;border-width:0px 1px 0px 1px;padding:0px 7px;"><font size=3 color=blue face="Times New Roman">37.0-38.0
GHz</font>
<td width=35 style="border-style:none solid none solid;border-color:#000000;border-width:0px 1px 0px 1px;padding:0px 7px;"><font size=3 face="Times New Roman">Ka</font>
<td width=149 style="border-style:none solid none solid;border-color:#000000;border-width:0px 1px 0px 1px;padding:0px 7px;"><font size=3 color=blue face="Times New Roman">37.0-38.0
GHz</font>
<td width=35 style="border-style:none none none solid;border-color:#000000;border-width:0px 0px 0px 1px;padding:0px 7px;"><font size=3 face="Times New Roman">Ka</font></table>
<br>
<br><font size=2 face="sans-serif">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>
<br>
<br><font size=2 face="sans-serif">2) Statement below table 2</font>
<br>
<br><font size=2 face="sans-serif">Replace allocated by assigned and allocation
by assignment (they have different meanings in ITU).</font>
<br>
<br><font size=2 face="sans-serif">From:</font>
<br>
<br><font size=3 face="Times New Roman">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>
<br>
<br><font size=2 face="sans-serif">To:</font>
<br>
<br><font size=3 face="Times New Roman">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>
<br>
<br><font size=2 face="sans-serif">3) SCID request form (non normative)</font>
<br>
<br><font size=2 face="sans-serif">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>
<div><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>
<br>
<br><font size=2 face="sans-serif">Alternatively, the example shall be
deleted.</font>
<br>
<br><font size=2 face="sans-serif">4) Editorials</font>
<br>
<br><font size=2 face="sans-serif">In Table 2, EES shall be replaced by
EESS (occurs twice). </font>
<br>
<br><font size=2 face="sans-serif">ITC shall be changed to ITU in Annex
A. </font>
<br>
<br><font size=2 face="sans-serif">In ITU, the T stands for Telecommunication
(singular). In the magenta book all occurrences are in plural. </font>
<br>
<br><font size=2 face="sans-serif">WRC in Annex A is spelled out as Radiocommunications
(plural) whereas it is singular.</font>
<br>
<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">11/07/2016 22:42</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">[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=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 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 GSCIDs, 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">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-07-001 Request publication
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 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">The SSG Members concur that this draft
is ready for publication.</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 now 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 approval of this document, and that</font>
<br><font size=4 face="Calibri">Once the CESG poll succeeds that the CMC
be polled to approve the document for direct publication, as it was in
its original form.</font>
<br><font size=4 face="Calibri"> </font>
<br><font size=4 face="Calibri"> </font>
<br><font size=4 face="Calibri"> [attachment "320x0b6c1_mods_7-12July16.docx"
deleted by Gian Paolo Calzolari/esoc/ESA] </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>
<br></div><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>