<font size=2 face="sans-serif">....... but agency review and publication
in the same sentence looked conflicting :o)</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">"Gian.Paolo.Calzolari@esa.int"
<Gian.Paolo.Calzolari@esa.int></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Cc:
</font><font size=1 face="sans-serif">"CCSDS Engineering
Steering Group - CESG Exec" <cesg@mailman.ccsds.org>, "CESG"
<cesg-bounces@mailman.ccsds.org>, "CCSDS Secretariat" <secretariat@mailman.ccsds.org>,
"SANA Steering Group(SSG)" <ssg@mailman.ccsds.org>, "Tom
Gannett" <thomas.gannett@tgannett.net></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">27/09/2016 22:30</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-09-001: Request Agency Review for publication of
revised CCSDS SCID Code Assignment Control Procedures</font>
<br>
<hr noshade>
<br>
<br>
<br><font size=2 face="Calibri">Hi Gippo,</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">Yes. That is why I titled it:</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=3 face="Calibri"><b>Request Agency Review of revised CCSDS
SCID Code Assignment Control Procedures</b></font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">And described it as "</font><font size=4 face="Calibri">
request the CESG review and approve release of this document for Agency
Review"</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">Thanks, Peter</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri"> </font>
<br><font size=3 face="Calibri"><b>From: </b>Gian Paolo Calzolari <Gian.Paolo.Calzolari@esa.int><b><br>
Date: </b>Tuesday, September 27, 2016 at 1:23 PM<b><br>
To: </b>Peter Shames <peter.m.shames@jpl.nasa.gov><b><br>
Cc: </b>CCSDS Engineering Steering Group - CESG Exec <cesg@mailman.ccsds.org>,
CESG <cesg-bounces@mailman.ccsds.org>, CCSDS Secretariat <secretariat@mailman.ccsds.org>,
"SANA Steering Group (SSG)" <ssg@mailman.ccsds.org>, Tom
Gannett <thomas.gannett@tgannett.net><b><br>
Subject: </b>Re: [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=3 face="Times New Roman"> </font>
<br><font size=2 face="sans-serif">Peter,</font><font size=3 face="Times New Roman">
</font><font size=2 face="sans-serif"><br>
if I understand well your request is for starting
Agency Review and not for actual publication of the new version.</font><font size=3 face="Times New Roman">
</font><font size=2 face="sans-serif"><br>
Am I correct?</font><font size=3 face="Times New Roman"> <br>
</font><font size=2 face="sans-serif"><br>
Thanks</font><font size=3 face="Times New Roman"> <br>
</font><font size=2 face="sans-serif"><br>
Gippo</font><font size=3 face="Times New Roman"> <br>
<br>
<br>
</font><font size=1 color=#5f5f5f face="sans-serif"><br>
From: </font><font size=1 face="sans-serif">"Shames,
Peter M (312B)" <peter.m.shames@jpl.nasa.gov></font><font size=3 face="Times New Roman">
</font><font size=1 color=#5f5f5f face="sans-serif"><br>
To: </font><font size=1 face="sans-serif">"CCSDS
Secretariat" <secretariat@mailman.ccsds.org>, "Tom Gannett"
<thomas.gannett@tgannett.net></font><font size=3 face="Times New Roman">
</font><font size=1 color=#5f5f5f face="sans-serif"><br>
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><font size=3 face="Times New Roman">
</font><font size=1 color=#5f5f5f face="sans-serif"><br>
Date: </font><font size=1 face="sans-serif">23/09/2016
23:46</font><font size=3 face="Times New Roman"> </font><font size=1 color=#5f5f5f face="sans-serif"><br>
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><font size=3 face="Times New Roman">
</font><font size=1 color=#5f5f5f face="sans-serif"><br>
Sent by: </font><font size=1 face="sans-serif">"CESG"
<cesg-bounces@mailman.ccsds.org></font><font size=3 face="Times New Roman">
</font>
<div align=center>
<hr noshade></div>
<br><font size=3 face="Times New Roman"><br>
<br>
</font><font size=4 face="Calibri"><br>
Dear CCSDS Secretariat,</font><font size=3 face="Times New Roman"> </font><font size=4 face="Calibri"><br>
</font><font size=3 face="Times New Roman"> </font><font size=4 face="Calibri"><br>
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><font size=3 face="Times New Roman">
</font><font size=4 face="Calibri"><br>
</font><font size=3 face="Times New Roman"> </font><font size=4 face="Calibri"><br>
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><font size=3 face="Calibri"><br>
</font><font size=3 face="Times New Roman"> </font><font size=4 face="Calibri"><br>
Thanks, Peter</font><font size=3 face="Times New Roman"> </font><font size=4 face="Calibri"><br>
</font><font size=3 face="Times New Roman"> </font><font size=4 face="Calibri"><br>
==========================================================================</font><font size=3 face="Times New Roman">
</font><font size=4 face="Calibri"><br>
</font><font size=3 face="Times New Roman"> </font><font size=4 face="Calibri"><b><br>
SEA-R-2016-09-001 Request Agency Review of revised CCSDS SCID Code
Assignment Control Procedures</b></font><font size=3 face="Times New Roman">
</font><font size=4 face="Calibri"><br>
--------------------------------------------------------------------------------</font><font size=3 face="Times New Roman">
</font><font size=4 face="Calibri"><br>
</font><font size=3 face="Times New Roman"> </font><font size=4 face="Calibri"><br>
The <b>System Engineering Area,</b></font><font size=3 face="Times New Roman">
</font><font size=4 face="Calibri"><br>
</font><font size=3 face="Times New Roman"> </font><font size=4 face="Calibri"><b><br>
CONSIDERING</b> that:</font><font size=3 face="Times New Roman"> </font><font size=4 face="Calibri"><br>
</font><font size=3 face="Times New Roman"> </font><font size=4 face="Calibri"><br>
The SEA SANA Steering Group (SSG) has produced a revision of the existing
Blue Book called the CCSDS GLOBAL SPACECRAFT IDENTIFIER FIELD:</font><font size=3 face="Times New Roman">
</font><font size=4 face="Calibri"><br>
CODE ASSIGNMENT CONTROL PROCEDURES (CCSDS 320.0-B-6), and that</font><font size=3 face="Times New Roman">
</font><font size=4 face="Calibri"><br>
The source document, CCSDS 320.0-B-1, was originally directly published
as a CMC Blue Book document, and that</font><font size=3 face="Times New Roman">
</font><font size=4 face="Calibri"><br>
The specific major changes to the document have already been reviewed and
agreed to by the CESG and CMC, and that</font><font size=3 face="Times New Roman">
</font><font size=4 face="Calibri"><br>
All of the requested updates have been made to satisfy the identified conditions.</font><font size=3 face="Times New Roman">
</font><font size=4 face="Calibri"><br>
</font><font size=3 face="Times New Roman"> </font><font size=4 face="Calibri"><br>
And <b>RECOGNIZING</b> that: <br>
</font><font size=3 face="Times New Roman"> </font><font size=4 face="Calibri"><br>
A CCSDS Area Director is responsible for requesting CESG concurrence prior
to publication, and that</font><font size=3 face="Times New Roman"> </font><font size=4 face="Calibri"><br>
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><font size=3 face="Times New Roman">
</font><font size=4 face="Calibri"><br>
notify the Chief Technical Editor.</font><font size=3 face="Times New Roman">
</font><font size=4 face="Calibri"><br>
</font><font size=3 face="Times New Roman"> </font><font size=4 face="Calibri"><br>
And <b>RECOGNIZING</b> that:</font><font size=3 face="Times New Roman">
</font><font size=4 face="Calibri"><br>
</font><font size=3 face="Times New Roman"> </font><font size=4 face="Calibri"><br>
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><font size=3 face="Times New Roman"> </font><font size=4 face="Calibri"><br>
Sec 6.2.7 requires periodic review and re-confirmation of Normative Track
documents.</font><font size=3 face="Times New Roman"> </font><font size=4 face="Calibri"><br>
</font><font size=3 face="Times New Roman"> </font><font size=4 face="Calibri"><b><br>
RESOLVES</b> to request:</font><font size=3 face="Times New Roman"> </font><font size=4 face="Calibri"><br>
</font><font size=3 face="Times New Roman"> </font><font size=4 face="Calibri"><br>
That the Chief Technical Editor ready the document for review, and that</font><font size=3 face="Times New Roman">
</font><font size=4 face="Calibri"><br>
The document be re-classified as a Magenta Book, to properly characterize
it based on its contents, and that</font><font size=3 face="Times New Roman">
</font><font size=4 face="Calibri"><br>
The Secretariat create the necessary CESG poll to request the CESG review
and approve release of this document for Agency Review, and that</font><font size=3 face="Times New Roman">
</font><font size=4 face="Calibri"><br>
Once the CESG poll succeeds that the CMC be polled to approve the document
for Agency Review.</font><font size=3 face="Times New Roman"> </font><font size=4 face="Calibri"><br>
</font><font size=3 face="Times New Roman"> </font><font size=4 face="Calibri"><br>
</font><font size=3 face="Times New Roman"> </font><font size=4 face="Calibri"><br>
[attachment "320x0b6c1_mods_7-23Sep16.docx" deleted by Gian
Paolo Calzolari/esoc/ESA] </font><font size=2 face="Courier New">_______________________________________________<br>
CESG mailing list<br>
CESG@mailman.ccsds.org</font><font size=3 color=blue face="Times New Roman"><u><br>
</u></font><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg"><font size=2 color=blue face="Courier New"><u>https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg</u></font></a>
<br><font size=2 face="Courier New">This message and any attachments are
intended for the use of the addressee or addressees only.</font>
<br><font size=2 face="Courier New">The unauthorised disclosure, use, dissemination
or copying (either in whole or in part) of its</font>
<br><font size=2 face="Courier New">content is not permitted.</font>
<br><font size=2 face="Courier New">If you received this message in error,
please notify the sender and delete it from your system.</font>
<br><font size=2 face="Courier New">Emails can be altered and their integrity
cannot be guaranteed by the sender.</font>
<br><font size=2 face="Courier New"> </font>
<br><font size=2 face="Courier New">Please consider the environment before
printing this email.</font>
<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>