<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="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
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;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.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 lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">Dear Secretariat,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">After consultation with the SLS AD and members of his WG based on their feedback to the original submission, and after discussing this with my local experts, I must make some minor adjustments to the documents associated with this resolution.
Please see attached a revised version of CCSDS 320.0-M-7, with mark ups, and a new Excel spreadsheet containing the updates to Table 2-1. These changes are required to provide a more "official" international reference for the Frequency Band Designators (FBD)
and a more accurate set of references to the actual ITU assigned frequencies. A copy of the ITU Radio Regulations is also attached for reference.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Notes are added to help ensure that the table will be correctly used.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In the interests of full disclosure it must be stated that the implementation of these changes in the SANA will involve some effort. These have been discussed with the SANA operator and what I believe is a viable path forward has been
identified. This requires accessing the actual SFCG managed set of frequency allocations to ensure that the currently registered spacecraft are assigned to the correct ITU defined frequency bands based on assigned operating frequencies. What we discovered
through this analysis is that our use, from the outset, of what could be inherently inaccurate frequency band "letter" designators, has propagated a problem which must be rectified if our set of FBDs and assignments is to be sufficiently fool proof.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks, Peter<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-left:.5in"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">Peter Shames <Peter.M.Shames@jpl.nasa.gov><br>
<b>Date: </b>Monday, December 17, 2018 at 11:51 AM<br>
<b>To: </b>CCSDS Secretariat <secretariat@mailman.ccsds.org>, CCSDS Engineering Steering Group - CESG Exec <cesg@mailman.ccsds.org><br>
<b>Cc: </b>"SANA Steering Group (SSG)" <ssg@mailman.ccsds.org><br>
<b>Subject: </b>SEA-R-2018-12-01 - initiate a corrigendum to update the CCSDS 320.0-M-7 SCID assignment Magenta Book document and the table of frequency bins<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black">Dear Secretariat,<br>
<br>
Please find below the SEA resolution to update the SCID procedure and the table of frequency bins<br>
<br>
Summary of resolution:</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black"><br>
Resolution 1: initiate a corrigendum to update the CCSDS 320.0-M-7 SCID Assignment Magenta Book document and the table of frequency bins to align with the commonly allocated ITU frequencies for SRS, EES, and FSS, such that they associate with the ranges of
frequencies that spacecraft are required, by international agreement, to operate at. </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black"><br>
Thanks, Peter<br>
<br>
======================================================================</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in;caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="color:black"><br>
SEA-R-2018-12-01 Initiate a corrigendum to update the CCSDS 320.0-M-7 SCID assignment Magenta Book document and the table of frequency bins to align with the commonly allocated ITU frequencies for SRS, EES, and FSS, such that they associate with
the ranges of frequencies that spacecraft are required, by international agreement, to operate at. </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black"><br>
The System Engineering Area,<br>
<br>
<b>CONSIDERING that:</b><br>
<br>
The ITU has defined a set of frequencies for space research (SRS), Earth exploration (EESE), and fixed satellite (FSS) services, and that</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black">All spacecraft are allocated operating frequencies that align with these frequency ranges, and that</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in;caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="color:black">The current Table 2-1 in CCSDS 320.0-M-7 used the IEEE Std 521TM-2002(R2009) boundaries for RADAR frequency bins, and that</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black">The frequency bins defined by the ITU and the IEEE standard do not exactly align, and that
</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in;caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="color:black">The SANA Spacecraft Identifiers registry,<span class="apple-converted-space"> </span><a href="http://sanaregistry.org/r/spacecraftid/"><span style="color:#954F72">http://sanaregistry.org/r/spacecraftid/</span></a> uses the IEEE bins
documented in the current CCSDS 320.0-M-7, and that</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in;caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="color:black">Recent users of the SCID procedure have pointed out this discrepancy.<br>
<br>
<br>
<br>
</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in;caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<b><span style="font-size:12.0pt;color:black">And RECOGNIZING that:</span></b><span style="font-size:12.0pt;color:black"><br>
<br>
The CCSDS Organization and Processes (A02.1-Y-4 cor 2) Sec 6.2.7.2.3 states:</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.75in;caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<b><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:#0070C0">6.2.7.2.3 Corrigenda</span></b><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.75in;caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<b><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:#0070C0">Minor technical changes may be made to published normative documents via corrigenda</span></b><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.75in;caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:#0070C0">a) The AD shall supply an Area<span class="apple-converted-space"> </span>resolution via e-mail to the Secretariat and CESG-exec lists<span class="apple-converted-space"> </span>requesting
that a corrigendum be issued.<span class="apple-converted-space"> </span></span><o:p></o:p></p>
<p style="margin-left:.75in;caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:#0070C0">b) The CCSDS Chief Technical Editor shall</span><o:p></o:p></p>
<p style="margin-left:1.25in;caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:#0070C0">1) prepare the corrigendum form (see annex D) and document markup and initiate CESG and CMC polls to approve and authorize the corrigendum; and</span><o:p></o:p></p>
<p style="margin-left:1.25in;caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:#0070C0">2) upon successful completion of the CESG and CMC polls, release the updated document and corrigendum form for publication.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in;caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="font-size:12.0pt;color:black">and that,</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in;caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="font-size:12.0pt;color:black">The CCSDS Organization and Processes (A02.1-Y-4 cor 2) requires that an AD shall ask the CESG and CMC to review and approve corrigenda, and that</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in;caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="font-size:12.0pt;color:black">The SEA AD has reviewed these documents and registries and determined that a change via corrigendum is appropriate.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in;caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="font-size:12.0pt;color:black"><br>
<b>RESOLVES to request:</b><br>
<br>
That the Secretariat prepare the necessary corrigendum to CCSDS 320.0-M-7 to update Table 2-1 with the attached revision, and that</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in;caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="font-size:12.0pt;color:black">The Secretariat initiate a poll requesting CESG and CMC approval to make these changes and publish the Corrigendum, and that
</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt;color:black">After this resolution is approved the SANA Operator revise the existing SCID registry</span><span style="color:black">,<span class="apple-converted-space"> </span><a href="http://sanaregistry.org/r/spacecraftid/"><span style="color:#954F72">http://sanaregistry.org/r/spacecraftid/</span></a>,<span class="apple-converted-space"> </span></span><span style="font-size:12.0pt;color:black">to
correct the frequency band alignment, and that</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in;caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="font-size:12.0pt;color:black">The SANA Operator review the existing allocations to identify any spacecraft that might be affected by this, and propose any specific new SCID allocations to resolve identified discrepancies.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
</div>
</body>
</html>