<html 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">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Title" content="">
<meta name="Keywords" content="">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Courier New";
panose-1:2 7 3 9 2 2 5 2 4 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:sans-serif;
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Courier;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:Calibri;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body bgcolor="white" lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Nestor, et al,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">I proposed treating this documents as we had in the past, on “grand-fathered” grounds. I think that there is some justification for this, but I do understand where you are coming from.
I also think that we have had a similar situation in other cases, where other old “Blue” documents are now being re-classified as Magenta because they are procedural in nature. I think the only solid justification for treating this document differently is
that it was created as a “CMC Blue Book” to begin with. I am speculating, because it was before my time (but not Tom’s), but this was probably because the old Panel 1, 2, 3 structure did not have anything like a CESG or an SE arm.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">That said, I agree that it is reasonable to now subject this document to the same sort of rigor that we apply to all other documents that come up for review. Accordingly, I am asking the
Secretariat to please modify the resolution to reflect that this document will go through the normal CESG, CMC, and Agency review process.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">And that said, I do wish to point out to the CESG and the CMC that this is not something that we can delay or avoid. We will, very shortly, run out of Type 2, 8-bit, SCIDs, and when that
happens we will be in trouble. Even though, in fact, we could assign the exact same GSCID in different frequency bands, without fear of any repercussions or communications problems because of the actual physical separation that different frequency bands give
us, we have no means “officially” to do this. And thus we will be stuck with no way to register new Type 2 spacecraft.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Bottom line: while we can send this out for review, we must not allow this review to delay the adoption of this extended GSCID assignment and registration process.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Best regards, Peter<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-family:Calibri;color:black">From: </span>
</b><span style="font-family:Calibri;color:black">Nestor Peccia <Nestor.Peccia@esa.int><br>
<b>Date: </b>Tuesday, July 12, 2016 at 5:38 AM<br>
<b>To: </b>Tom Gannett <thomas.gannett@tgannett.net><br>
<b>Cc: </b>CCSDS Engineering Steering Group - CESG Exec <cesg@mailman.ccsds.org>, 'CESG' <cesg-bounces@mailman.ccsds.org>, Peter Shames <peter.m.shames@jpl.nasa.gov>, CCSDS Secretariat <secretariat@mailman.ccsds.org>, "SANA Steering Group (SSG)" <ssg@mailman.ccsds.org><br>
<b>Subject: </b>RE: UPDATE: [CESG] SEA Resolution SEA-R-2016-07-001: Request publication of revised CCSDS SCID Code Assignment Control Procedures<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<blockquote style="border:none;border-left:solid #B5C4DF 4.5pt;padding:0in 0in 0in 4.0pt;margin-left:3.75pt;margin-right:0in" id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE">
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"sans-serif","serif"">Dear Tom</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif"">Thanks for your feedback. Historical justification can not be good for this case and not for others past cases subjected to the rigor of the Proc & Org YB</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif"">I believe that the book contains details on frequency bands that deserves Agency review</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif"">Enrico has just sent comments on a pretended "book for publication", and I am sure more could come.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif"">therefore my suggestion as CESG Chair IS to go for Agency review</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif"">The suggestion can be ignored, by you and / or Peter, and the CESG poll can be issued. We will then evaluate the results.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif"">The other possibility is to publish it as YB</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif"">ciao</span> <br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif"">nestor</span> <o:p>
</o:p></p>
<pre>This message and any attachments are intended for the use of the addressee or addressees only.<o:p></o:p></pre>
<pre>The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its<o:p></o:p></pre>
<pre>content is not permitted.<o:p></o:p></pre>
<pre>If you received this message in error, please notify the sender and delete it from your system.<o:p></o:p></pre>
<pre>Emails can be altered and their integrity cannot be guaranteed by the sender.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Please consider the environment before printing this email.<o:p></o:p></pre>
</div>
</div>
</blockquote>
</div>
</body>
</html>