<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: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:"Brush Script MT";
panose-1:3 6 8 2 4 4 6 7 3 4;}
@font-face
{font-family:"\@Brush Script MT";}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-ligatures:standardcontextual;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@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" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Hi Gabriele,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Nice to meet you, even if it is only via email.<o:p></o:p></p>
<p class="MsoNormal">I included the entire SLP WG on this distribution, since the topic is an important one.<o:p></o:p></p>
<p class="MsoNormal">The Prox-1 physical layer standard (CCSDS 211.1-B-4) specifies Channel 1 as the hailing channel for UHF at Mars
<span style="font-family:"Times New Roman",serif">in which Ch 1 is defined as </span>
435.6 MHz forward and 404.4 MHz return.<o:p></o:p></p>
<p class="MsoNormal"><o:p></o:p></p>
<p class="MsoNormal">I realize that the Mars Program deviated from this standard and utilized Channel 0 as their Hailing Channel and their working channel.
<o:p></o:p></p>
<p class="MsoNormal">So this difference is a de-facto vs de-jure issue.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">CCSDS 211.1-B-4 also says in a NOTE (which is non-normative) that “Enterprise-specific hailing channel frequencies can be defined in the default configuration of the Physical Layer parameters”. Furthermore, in another follow on NOTE (non-normative)
in the same section, it says, “if transceivers are compatibly configured, hailing can occur on an agreed-to channel. The first generation transceivers are fixed frequency and use Channel 0”.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">So, I believe the Mars Program backward compatibility issue has been documented in 211.1-B-4. Would you agree ?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">From an international cross-support CCSDS standard point of view, what I have documented in this proposed Annex for default session control parameters is correct i.e., The Prox-1 standard (CCSDS 211.1-B-4) specifies Channel 1 as the hailing
channel for UHF at Mars at those frequencies above. Also per 211.1-B-4, Ch 0 is defined as the forward 437.1 MHz frequency, and the return frequency 401.585625.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best regards,<o:p></o:p></p>
<p class="MsoNormal">Greg<o:p></o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span lang="EN-GB" style="font-size:12.0pt;color:black;mso-ligatures:none">From:
</span></b><span lang="EN-GB" style="font-size:12.0pt;color:black;mso-ligatures:none">DONA' Gabriele <gabriele.dona@thalesaleniaspace.com><br>
<b>Date: </b>Thursday, November 16, 2023 at 1:35 AM<br>
<b>To: </b>"Kazz, Greg (US 312B)" <greg.j.kazz@jpl.nasa.gov><br>
<b>Cc: </b>"Brice.Dellandrea@esa.int" <Brice.Dellandrea@esa.int><br>
<b>Subject: </b>[EXTERNAL] RE: Updated Proximity-1 Directives and Default Session Control Parameters for Lunar Operations<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="mso-ligatures:none"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span style="color:#1F497D">Dear Greg,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I’m not sure whether I should reply to you or to the whole WGs. Anyway here’s my comment about the default parameters used to establish hailing.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">In Section A1.1 UHF BAND HAILING CHANNEL PARAMETERS, I believe the default hailing channel should be Channel 0 and not Channel 1. That is important to keep backward compatibility with existing transceivers. By
the way, there is a typo: Ch 0 (404.4 MHz) should read Ch 1 (404.4 MHz) instead. Then, if the intention is to allow hailing on other channels (e.g. channel 1), on specific cases/missions, then I have no objections.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I hope this comments helps.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Gabriele.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">P.S. In case you wandered, I am the engineering responsible for the UHF subsystems of the ExoMars missions for Thales Alenia Space.<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="color:#1F497D;mso-ligatures:none"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:18.0pt;font-family:"Brush Script MT";color:#002060;mso-ligatures:none;mso-fareast-language:FR">Gabriele Donà, Ph.D.</span><span lang="EN-GB" style="color:#1F497D;mso-ligatures:none;mso-fareast-language:FR"><br>
</span><span lang="EN-GB" style="color:#5ABED3;mso-ligatures:none;mso-fareast-language:FR">Thales Specialist<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#5ABED3;mso-ligatures:none;mso-fareast-language:FR">Head of Data Systems & Communication Department</span><span lang="EN-GB" style="color:#1F497D;mso-ligatures:none;mso-fareast-language:FR"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D;mso-ligatures:none;mso-fareast-language:FR"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#5ABED3;mso-ligatures:none;mso-fareast-language:FR">Phone:
</span><span lang="EN-GB" style="color:black;mso-ligatures:none;mso-fareast-language:FR">+39 011 7180 555<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-GB" style="color:#5ABED3;mso-ligatures:none;mso-fareast-language:FR">Mobile:
</span><span lang="EN-GB" style="color:black;mso-ligatures:none;mso-fareast-language:FR">+39 380 591 6240<o:p></o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-GB" style="color:#5ABED3;mso-ligatures:none;mso-fareast-language:FR">Personal Meeting Room:
</span></b><span lang="EN-GB" style="color:black;mso-ligatures:none;mso-fareast-language:FR">3080044019<b><o:p></o:p></b></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#5ABED3;mso-ligatures:none;mso-fareast-language:FR">Link:
</span><span lang="EN-GB" style="color:#1F497D;mso-ligatures:none;mso-fareast-language:FR"><a href="https://urldefense.us/v3/__https:/join3.thalesgroup.com/__;!!PvBDto6Hs4WbVuu7!L1wAVo628dCMgtpAAumuBTZAr-X3maH_jE88g_kNyAIz5t8dXwpN9AfIWXmU1LBJ8LslZfBgCPKTxNV-al8m1fXa6YllEl-cROvbRj7H$"><span style="color:blue">https://join3.thalesgroup.com/</span></a></span><span lang="EN-GB" style="color:black;mso-ligatures:none;mso-fareast-language:FR"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#5ABED3;mso-ligatures:none;mso-fareast-language:FR">Participant PIN:
</span><span lang="EN-GB" style="color:black;mso-ligatures:none;mso-fareast-language:FR">988 455<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="mso-ligatures:none">From:</span></b><span style="mso-ligatures:none"> SLS-SLP <sls-slp-bounces@mailman.ccsds.org>
<b>On Behalf Of </b>Kazz, Greg (US 312B) via SLS-SLP<br>
<b>Sent:</b> 15 November 2023 23:29<br>
<b>To:</b> Kazz, Greg (US 312B) via SLS-SLP <sls-slp@mailman.ccsds.org>; Space Link Coding & Synchronization Working Group <sls-cc@mailman.ccsds.org>; sls-rfm@mailman.ccsds.org<br>
<b>Cc:</b> Brice Dellandrea <Brice.Dellandrea@esa.int><br>
<b>Subject:</b> [Sls-slp] Updated Proximity-1 Directives and Default Session Control Parameters for Lunar Operations<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal">Dear CCSDS SLP, C&S, and RFM WGs,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I took the liberty of updating both the Proximity-1 Directive Set as well as the Default Session Control Parameters for Lunar Operations, based upon the inputs provided at the Fall CCSDS Meeting recently concluded in The Hague (Joint meeting
held on Nov. 10, 2023).<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The update to both the Lunar Proximity directives and the default session parameters is in the CWE now under this SLP WG directory:<o:p></o:p></p>
<p class="MsoNormal"><a href="https://urldefense.us/v3/__https:/cwe.ccsds.org/sls/docs/Forms/AllItems.aspx?RootFolder=*2Fsls*2Fdocs*2FSLS*2DSLP*2FMeeting*20Materials*2F2023*2FFall*2FPost*20Meeting*20Prox*201*20work&FolderCTID=0x012000439B56FF51847E41B5728F9730D7B55F&View=*7BAE8FB44C*2DE80A*2D42CF*2D8558*2DFB495ABB675F*7D__;JSUlJSUlJSUlJSUlJSUlJSUlJQ!!PvBDto6Hs4WbVuu7!L1wAVo628dCMgtpAAumuBTZAr-X3maH_jE88g_kNyAIz5t8dXwpN9AfIWXmU1LBJ8LslZfBgCPKTxNV-al8m1fXa6YllEl-cRGoUqlwQ$">https://cwe.ccsds.org/sls/docs/Forms/AllItems.aspx?RootFolder=%2Fsls%2Fdocs%2FSLS%2DSLP%2FMeeting%20Materials%2F2023%2FFall%2FPost%20Meeting%20Prox%201%20work&FolderCTID=0x012000439B56FF51847E41B5728F9730D7B55F&View=%7BAE8FB44C%2DE80A%2D42CF%2D8558%2DFB495ABB675F%7D</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">There are still several TBDs remaining to be resolved including the action items taken by the RFM WG (e.g., define specific hailing and working channel frequencies at S-band, etc)<o:p></o:p></p>
<p class="MsoNormal">I am also interested to know if you have specific values for the new parameter: Mod Index.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Please let me know if you have comments, so that I can incorporate them into these two normative annexes which will reside in the restructured Space Data Link Protocol Session Control Blue Book.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best regards,<o:p></o:p></p>
<p class="MsoNormal">Greg<o:p></o:p></p>
</div>
</body>
</html>