<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>Ciao Gippo,</div>
<div><br>
</div>
<div>Glad to have your input on this. I just looked again at the IOAG RF asset fregistry that is out on the SANA. It still has controlled access, but I have asked for, and been given, access. That registry uses the same sort of frequency bins as were in
that table I provided. A snapshot is attached.</div>
<div><br>
</div>
<div>It has headers like “UHF-Band uplink”, “C-Band Uplink”, and also some like "2 Ghz-Band (S-Band)”. So it is a mix of numbers (in some cases) and band-identifiers (in all cases). So just what are you suggesting here:</div>
<ol>
<li>That we exclusively use the frequencies like 2 Ghz?</li><li>That we exclusively use the band-identifiers, like Ka-Band?</li><li>Or that we use a mix of these as the current RF Assets registry does?</li></ol>
<div>Did you have any issue with the proposal to adopt these “Band Bins” as a way of managing the sets of SCIDs that can be assigned, or were you favoring having one table for each band (many of which would be very sparsely populated)?</div>
<div><br>
</div>
<div>Thanks, 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><<a href="mailto:ssg-bounces@mailman.ccsds.org">ssg-bounces@mailman.ccsds.org</a>> on behalf of Gian Paolo Calzolari <<a href="mailto:Gian.Paolo.Calzolari@esa.int">Gian.Paolo.Calzolari@esa.int</a>><br>
<span style="font-weight:bold">Date: </span>Tuesday, August 4, 2015 at 6:29 AM<br>
<span style="font-weight:bold">To: </span>CCSDS Engineering Steering Group - CESG Exec <<a href="mailto:cesg@mailman.ccsds.org">cesg@mailman.ccsds.org</a>><br>
<span style="font-weight:bold">Cc: </span>"SANA Steering Group (SSG)" <<a href="mailto:ssg@mailman.ccsds.org">ssg@mailman.ccsds.org</a>><br>
<span style="font-weight:bold">Subject: </span>[SSG] [CESG] ?Band Bins? for 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>
<div><font size="2" face="sans-serif">Peter,</font> <br>
<font size="2" face="sans-serif"> with respect to your proposal below, if imit will be implemented I do recommend keeping consistency with the headers of the IOAG RF assets table (to be modified I think) where the frequency bands are explicity addressed
with numbers.</font> <br>
<br>
<font size="2" face="Calibri">Purely based on pragmatic considerations I would suggest that we could create “Band Bins” that looked like this:</font>
<ul>
<li><font size="2" face="Calibri">Everything below S-Band (HF, VHF, UHF, L)</font></li><li><font size="2" face="Calibri">S-Band & C-Band</font> </li><li><font size="2" face="Calibri">X-Band</font> </li><li><font size="2" face="Calibri">K-Band (Ku, K, Ka)</font> </li><li><font size="2" face="Calibri">None or unstated</font></li></ul>
<br>
<font size="2" face="sans-serif">Regards</font> <br>
<br>
<font size="2" face="sans-serif">Gian Paolo</font> <br>
<ul>
<li></li></ul>
<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>
</div>
</div>
</blockquote>
</span>
</body>
</html>