<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body>
<div dir="auto">Matt, </div>
<div dir="auto">I still think that a note would not hurt. While we cannot avoid a legacy system to be formally not compliant to the new standard, we could still provide a guideline to prevent a system engineer to select a wrong configuration and avoid later
painful adjustments. </div>
<div dir="auto"><br>
</div>
<div dir="auto">Cheers</div>
<div dir="auto">Marco</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Matt Cosby <matt.cosby@goonhilly.org><br>
<b>Sent:</b> Tuesday, November 7, 2023 12:31:18 PM<br>
<b>To:</b> Marco Rovatti <Marco.Rovatti@esa.int>; Kazz, Greg (US 312B) <greg.j.kazz@jpl.nasa.gov>; sls-slp@mailman.ccsds.org <sls-slp@mailman.ccsds.org><br>
<b>Subject:</b> RE: RID resolution to AOS Space Data Link Protocol (SDLP) 732.0-B</font>
<div> </div>
</div>
<style>
<!--
@font-face
{font-family:"Cambria Math"}
@font-face
{font-family:Calibri}
p.x_MsoNormal, li.x_MsoNormal, div.x_MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif}
a:link, span.x_MsoHyperlink
{color:#0563C1;
text-decoration:underline}
span.x_EmailStyle20
{font-family:"Calibri",sans-serif;
color:windowtext}
.x_MsoChpDefault
{font-size:10.0pt}
@page WordSection1
{margin:72.0pt 72.0pt 72.0pt 72.0pt}
div.x_WordSection1
{}
-->
</style>
<div lang="EN-GB" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="x_WordSection1">
<p class="x_MsoNormal"><span style="">Hi Marco,</span></p>
<p class="x_MsoNormal"><span style=""> </span></p>
<p class="x_MsoNormal"><span style="">Greg and I have just had the same conversation. We agree that the changes should not impact “legacy systems”, as the 5 bits will be set to zero for frames that legacy systems are able to support.
</span></p>
<p class="x_MsoNormal"><span style=""> </span></p>
<p class="x_MsoNormal"><span style="">I also think that a note is not required, as legacy systems will be compatible with the pink sheets as they will only be able to support the smaller frame sizes – which means the smaller FHPs</span></p>
<p class="x_MsoNormal"><span style=""> </span></p>
<p class="x_MsoNormal"><span style="">Thanks, Matt.</span></p>
<p class="x_MsoNormal"><span style=""> </span></p>
<div>
<p class="x_MsoNormal"><b><span style="color:black"> </span></b></p>
<p class="x_MsoNormal"><b><span style="color:black">Matthew Cosby</span></b><span style="color:black"></span></p>
<p class="x_MsoNormal"><b><span style="layout-grid-mode:line">Chief Technology Officer
</span></b></p>
<p class="x_MsoNormal"><b><span style="color:black">Goonhilly Earth Station Ltd</span></b></p>
<p class="x_MsoNormal"><b><span style="color:black"> </span></b></p>
<p class="x_MsoNormal"><span style="color:black"><img width="565" height="141" id="x_Picture_x0020_1" src="cid:image001.jpg@01DA116D.EEDDED40" alt="signature_1318327456" style="width:5.8854in; height:1.4687in"></span><span style=""></span></p>
</div>
<p class="x_MsoNormal"><span style=""> </span></p>
<div>
<div style="border:none; border-top:solid #E1E1E1 1.0pt; padding:3.0pt 0cm 0cm 0cm">
<p class="x_MsoNormal"><b><span lang="EN-US" style="">From:</span></b><span lang="EN-US" style=""> SLS-SLP <sls-slp-bounces@mailman.ccsds.org>
<b>On Behalf Of </b>Marco Rovatti via SLS-SLP<br>
<b>Sent:</b> Tuesday, November 7, 2023 11:27 AM<br>
<b>To:</b> Kazz, Greg (US 312B) <greg.j.kazz@jpl.nasa.gov>; sls-slp@mailman.ccsds.org<br>
<b>Subject:</b> Re: [Sls-slp] RID resolution to AOS Space Data Link Protocol (SDLP) 732.0-B</span></p>
</div>
</div>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal"><span style="">Dear Greg, all, </span></p>
<p class="x_MsoNormal"><span style=""> </span></p>
<p class="x_MsoNormal"><span style="">First of all, my apologies for not having been able to join the Fall Meeting, unfortunately I am in Bremen working for Copernicus Expansion missions.
</span></p>
<p class="x_MsoNormal"><span style=""> </span></p>
<p class="x_MsoNormal"><span style="">Perhaps the way I see this is a bit naïve, however, the need for using a longer FHP is driven by the selected C&S standard.
</span></p>
<p class="x_MsoNormal"><span style="">New missions planning to use AOS 4.1 over DVB-2 or ACM and wanting to benefit from legacy HW/SW would need to restrain the max length of Transfer Frame to 2048 bytes at mission level.
</span></p>
<p class="x_MsoNormal"><span style="">In this way, the legacy unit’s “non-compliance” would have no practical consequences. Even an AOS4.1 compliant transmitter would never generate a FHP “longer than 11 bit”, meaning the most significant bits of the FHP will
be set to zeroes as a consequence of the shorter Transfer Frame length. </span>
</p>
<p class="x_MsoNormal"><span style=""> </span></p>
<p class="x_MsoNormal"><span style="">Maybe, instead of keeping the old text, either as an optional requirement or as a note, we can just put a note in the blue book to highlight this constraint in case a mix of legacy equipment and new standards are used.
</span></p>
<p class="x_MsoNormal"><span style=""> </span></p>
<p class="x_MsoNormal"><span style="">What do you think? </span></p>
<p class="x_MsoNormal"><span style=""> </span></p>
<p class="x_MsoNormal"><span style="">Best regards</span></p>
<p class="x_MsoNormal"><span style="">Marco </span></p>
<p class="x_MsoNormal"><span style=""> </span></p>
<div>
<div style="border:none; border-top:solid #E1E1E1 1.0pt; padding:3.0pt 0cm 0cm 0cm">
<p class="x_MsoNormal"><b><span lang="EN-US" style="">From:</span></b><span lang="EN-US" style=""> SLS-SLP <<a href="mailto:sls-slp-bounces@mailman.ccsds.org">sls-slp-bounces@mailman.ccsds.org</a>>
<b>On Behalf Of </b>Kazz, Greg (US 312B) via SLS-SLP<br>
<b>Sent:</b> Tuesday, November 7, 2023 10:37 AM<br>
<b>To:</b> <a href="mailto:sls-slp@mailman.ccsds.org">sls-slp@mailman.ccsds.org</a><br>
<b>Subject:</b> [Sls-slp] RID resolution to AOS Space Data Link Protocol (SDLP) 732.0-B</span></p>
</div>
</div>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal"><span lang="EN-US">Dear SLP WG,</span></p>
<p class="x_MsoNormal"><span lang="EN-US"> </span></p>
<p class="x_MsoNormal"><span lang="EN-US">I believe I sent out this provisional RID disposition to the SLP WG already, but since it the AOS SDLP pink sheet review is not over until Dec 11, I would like to see if we can come to consensus on the RID disposition
at this Fall meeting.</span></p>
<p class="x_MsoNormal"><span lang="EN-US"> </span></p>
<p class="x_MsoNormal"><span lang="EN-US">I had planned to walk through it yesterday, but it seems to have fallen off the agenda.</span></p>
<p class="x_MsoNormal"><span lang="EN-US">Nevertheless, I do believe the solution is rather straightforward.</span></p>
<p class="x_MsoNormal"><span lang="EN-US"> </span></p>
<p class="x_MsoNormal"><span lang="EN-US">The RID comes from ESA (Andrea Modenini).</span></p>
<p class="x_MsoNormal"><span lang="EN-US">The subject is the expansion of the First Header Pointer in AOS SDLP from 11 bits to 16 bits, using the current 5 spare bits in the M_PDU header so that AOS can accommodate up to the maximum size transfer frames as
USLP does, i.e., 64K frames.</span></p>
<p class="x_MsoNormal"><span lang="EN-US">The RID focuses on how CCSDS should reconcile legacy missions use with new mission use of this expanded field.</span></p>
<p class="x_MsoNormal"><span lang="EN-US"> </span></p>
<p class="x_MsoNormal"><span lang="EN-US">Attached as word document (which I have placed into the CWE) is my provisional response to Andrea subject to your comments. Andrea has written me back and agrees that a NOTE is better than changing the normative text.</span></p>
<p class="x_MsoNormal"><span lang="EN-US"> </span></p>
<p class="x_MsoNormal"><span lang="EN-US" style="background:yellow">Please let me know if you have any concerns or issue with this resolution. Depending upon your replies, we will carry on by email. By 12/11/2023, we will see if any additional RIDs arrive and
then we will need to disposition them by email as well.</span><span lang="EN-US"></span></p>
<p class="x_MsoNormal"><span lang="EN-US"> </span></p>
<p class="x_MsoNormal"><span lang="EN-US">Best regards,</span></p>
<p class="x_MsoNormal"><span lang="EN-US">Greg</span></p>
<p class="x_MsoNormal"><span style="">This message is intended only for the recipient(s) named above. It may contain proprietary information and/or protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received
this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (<a href="mailto:dpo@esa.int">dpo@esa.int</a>).
</span></p>
</div>
</div>
This message is intended only for the recipient(s) named above. It may contain proprietary information and/or protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received this e-mail in error, please notify
the sender immediately. ESA applies appropriate organisational measures to protect personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo@esa.int).
</body>
</html>