<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)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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:0cm;
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:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
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-GB" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Hi Marco,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">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.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">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<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Thanks, Matt.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><b><span style="color:black;mso-ligatures:none;mso-fareast-language:EN-US"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><b><span style="color:black;mso-ligatures:none;mso-fareast-language:EN-US">Matthew Cosby</span></b><span style="color:black;mso-ligatures:none;mso-fareast-language:EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="mso-ligatures:none;layout-grid-mode:line">Chief Technology Officer
<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="color:black;mso-ligatures:none;mso-fareast-language:EN-US">Goonhilly Earth Station Ltd<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="color:black;mso-ligatures:none;mso-fareast-language:EN-US"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><span style="color:black;mso-ligatures:none"><img width="565" height="141" style="width:5.8854in;height:1.4687in" id="Picture_x0020_1" src="cid:image001.jpg@01DA116D.EEDDED40" alt="signature_1318327456"></span><span style="mso-ligatures:none"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="mso-ligatures:none">From:</span></b><span lang="EN-US" style="mso-ligatures:none"> 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<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Dear Greg, all, <o:p>
</o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">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.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">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.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">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.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">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.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">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. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">What do you think? <o:p>
</o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Best regards<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Marco <o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="mso-ligatures:none">From:</span></b><span lang="EN-US" style="mso-ligatures:none"> 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<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-US">Dear SLP WG,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="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.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">I had planned to walk through it yesterday, but it seems to have fallen off the agenda.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Nevertheless, I do believe the solution is rather straightforward.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">The RID comes from ESA (Andrea Modenini).<o:p></o:p></span></p>
<p class="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.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">The RID focuses on how CCSDS should reconcile legacy missions use with new mission use of this expanded field.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="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.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="background:yellow;mso-highlight: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"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Greg<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-ligatures:none">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>).
<o:p></o:p></span></p>
</div>
</body>
</html>