<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" 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;}
@font-face
{font-family:-webkit-standard;
panose-1:2 11 6 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.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;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:black">Dear Secretariat,<o:p></o:p></span></p>
<p class="MsoNormal" style="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"> <o:p></o:p></span></p>
<p class="MsoNormal" style="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><i><span style="color:black">This resolution rescinds and replaces SEA-R-2018-12-01.
<o:p></o:p></span></i></b></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black">After yet more consultation with the SLS AD and members of his various Working Groups based on their feedback to the original submission, and after discussing this with JPL local experts on frequency allocation,
I must make some (hopefully) final adjustments to the document associated with this resolution. Please see attached a revised version of CCSDS 320.0-M-7, dated 4Feb19, with mark ups, and a new Excel spreadsheet containing the updates to Table 2-1, dated 23Jan19a.
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. The version of the table to be used is on the tab marked
"Enrico Proposed 320x0M7". A copy of the ITU Radio Regulations is also attached for reference.<o:p></o:p></span></p>
<p class="MsoNormal" style="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"> <o:p></o:p></span></p>
<p class="MsoNormal" style="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">Notes are added in the corrigendum to help ensure that the table will be correctly interpreted and used. The primary change in this iteration is that we have reached an agreement that the frequency bins that will be created in the
SANA will <b><i>exactly</i></b> correspond to the frequency ranges identified by the ITU for specific SRS, EESS, and SOS allocations, for near Earth and also deep space. This version of the document also includes explicit coverage for the USLP protocol in
the SCID assignment process and in the SANA registries. It also aligns this document with terminology harmonization being performed in the SLS Area.<o:p></o:p></span></p>
<p class="MsoNormal" style="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"> <o:p></o:p></span></p>
<p class="MsoNormal" style="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">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></span></p>
<p class="MsoNormal" style="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"> <o:p></o:p></span></p>
<p class="MsoNormal" style="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">Thanks, Peter<o:p></o:p></span></p>
<div style="mso-element:para-border-div;border:none;border-bottom:double windowtext 2.25pt;padding:0in 0in 1.0pt 0in">
<p class="MsoNormal" style="border:none;padding:0in;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"> <o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black">Summary of resolution:<o:p></o:p></span></p>
<p class="MsoNormal" style="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>
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 SOS, such that they associate with the ranges of
frequencies that spacecraft are required to operate at, by international agreement. Also incorporate support for USLP and harmonize terminology usage.<o:p></o:p></span></p>
<p class="MsoNormal" style="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>
Thanks, Peter<br>
<br>
======================================================================<o:p></o:p></span></p>
<p class="MsoNormal" style="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>
<b>SEA-R-2019-02-01</b> 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 SOS, such that they associate with
the ranges of frequencies that spacecraft are required, by international agreement, to operate at. This update also adds coverage for the registry requirements of the Unified Space Link Protocol (USLP), CCSDS 732x1b1, dated Oct 2018.<o:p></o:p></span></p>
<p class="MsoNormal" style="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>
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 Space Operations (SOS) services, and that<o:p></o:p></span></p>
<p class="MsoNormal" style="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">All spacecraft are allocated operating frequencies that align with these specific frequency ranges, and that<o:p></o:p></span></p>
<p class="MsoNormal" style="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<o:p></o:p></span></p>
<p class="MsoNormal" style="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 frequency bins defined by the ITU and the IEEE standard do not exactly align, and that<o:p></o:p></span></p>
<p class="MsoNormal" style="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><span class="apple-converted-space"> </span>uses
the IEEE bins documented in the current CCSDS 320.0-M-7, and that<o:p></o:p></span></p>
<p class="MsoNormal" style="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, and that<br>
The new USLP Protocol requires SCID assignment procedures, and that<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">The SLS Area has been working to harmonize terminology across all of the link layer protocols.<br>
<br>
<o:p></o:p></span></p>
<p class="MsoNormal" style="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="color:black">And RECOGNIZING that:</span></b><span style="color:black"><br>
<br>
The CCSDS Organization and Processes (A02.1-Y-4 cor 2) Sec 6.2.7.2.3 states:<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.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">
<b><span style="font-family:"Times New Roman",serif;color:#0070C0">6.2.7.2.3 Corrigenda</span></b><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.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">
<b><span style="font-family:"Times New Roman",serif;color:#0070C0">Minor technical changes may be made to published normative documents via corrigenda</span></b><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.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-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><span style="color:black"><o:p></o:p></span></p>
<p style="margin-left:.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">b) The CCSDS Chief Technical Editor shall</span><span style="font-family:"-webkit-standard",serif;color:black"><o:p></o:p></span></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">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><span style="font-family:"-webkit-standard",serif;color:black"><o:p></o:p></span></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">2) upon successful completion of the CESG and CMC polls, release the updated document and corrigendum form for publication.</span><span style="font-family:"-webkit-standard",serif;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="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">and that,</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="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 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<o:p></o:p></span></p>
<p class="MsoNormal" style="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 SEA AD has reviewed these documents and registries and determined that a change via corrigendum is appropriate, and that<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">The SLS AD and relevant WG chairs have also reviewed and participated in refining these changes.<o:p></o:p></span></p>
<p class="MsoNormal" style="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>
<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<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">The corrigendum includes changes to CCSDS 320.0-M-7 needed to support the SCID assignments for USLP, and that<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">The corrigendum includes other changes to CCSDS 320.0-M-7 needed to align with current terminology in use across SLS, and that<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">The Secretariat initiate a poll requesting CESG and CMC approval to make these changes and publish the Corrigendum, and that<o:p></o:p></span></p>
<p class="MsoNormal" style="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">After this resolution is approved the SANA Operator revise the existing SCID 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>,<span class="apple-converted-space"> </span>to
correct the frequency band alignment, and that<o:p></o:p></span></p>
<p class="MsoNormal" style="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 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.<o:p></o:p></span></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"> <o:p></o:p></span></p>
</div>
</body>
</html>