<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;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
font-size:10.0pt;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
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><!--[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="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Dear SLP WG members,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Happy New Year ! We all hope it will be a better one than the last one.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I’ve now updated all the affected SDLP’s (TM, AOS, USLP) with the agreed to mandatory PN sequence generator to be used in generating the random data pattern within the transfer frame data field of OID frames.<o:p></o:p></p>
<p class="MsoNormal">Luckily the changes has not impacted these books very much and is rather easily accommodated.<o:p></o:p></p>
<p class="MsoNormal">Please go to the following URL on the CWE that contain the 3 new files (each one containing the final prefix _gk):<o:p></o:p></p>
<p class="MsoNormal"><b><a href="https://tinyurl.com/yxn7gecs">https://tinyurl.com/yxn7gecs</a><o:p></o:p></b></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">This change affects the following sections in these SDLP books:<o:p></o:p></p>
<p class="MsoNormal">Section 4.1.4.6 which is now split into separate requirements to accommodate the mandatory PN sequence generator.<o:p></o:p></p>
<p class="MsoNormal">The note directly below associated with the project providing the idle pattern, has now been changed to provide the motivation for the random PN sequence.<o:p></o:p></p>
<p class="MsoNormal">Finally, in each book, the acronym, LFSR (Linear Feedback Shift Register) has been added to the Acronym Annex in the back.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I have included the power point presentations supplied by Massimo Bertinelli as a reminder of the changes proposed by RF&M and C&S WGs back in Dec 2019, which SLP WG concurred upon. We are simply catching up on that action now.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">So given the short fuse associated with providing these documents for Agency Review, I request you review these changes and provide me with your feedback by Thursday, Jan 28.<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 Kazz – Chair SLP WG<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"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">"Massimo.Bertinelli@esa.int" <Massimo.Bertinelli@esa.int><br>
<b>Date: </b>Tuesday, January 26, 2021 at 7:41 AM<br>
<b>To: </b>"Kazz, Greg J (US 312B)" <greg.j.kazz@jpl.nasa.gov><br>
<b>Cc: </b>"Gian.Paolo.Calzolari@esa.int" <Gian.Paolo.Calzolari@esa.int>, "Gilles.Moury@cnes.fr" <Gilles.Moury@cnes.fr>, Matthew Cosby <matt.cosby@goonhilly.org><br>
<b>Subject: </b>Re: OID Frames with mandatory PN sequence: FW: [EXTERNAL] Re: [Sls-slp] [SLS-CC] Joint C&S/SLP<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Hi Greg,</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">the 32-cell LFSR agreed upon was presented in the document attached (slide 12-13).</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">In the document the initialisation of the register was an open question (3 options given).</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">In the end, one option was chosen as outlined in the C&S-SPL liaison presentation attached.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">I hope this can help.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Please let me know in case you need more information.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Best regards,</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Massimo</span> <br>
<br>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
<br>
---------------------------------------------------<br>
Massimo Bertinelli<br>
Communication Systems Engineer<br>
ESA/Estec<br>
<br>
Tel. +31 (0)71 5653435<br>
--------------------------------------------------</span> <br>
<br>
<br>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">From: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"Kazz, Greg J (US 312B)" <greg.j.kazz@jpl.nasa.gov></span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">To: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"Massimo.Bertinelli@esa.int" <Massimo.Bertinelli@esa.int>, "Gian.Paolo.Calzolari@esa.int" <Gian.Paolo.Calzolari@esa.int></span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Cc: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"Gilles.Moury@cnes.fr" <Gilles.Moury@cnes.fr>, "Matthew Cosby" <matt.cosby@goonhilly.org></span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Date: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">25/01/2021 22:56</span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Subject: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">Re: OID Frames with mandatory PN sequence: FW: [EXTERNAL] Re: [Sls-slp] [SLS-CC] Joint C&S/SLP</span>
<o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="0" width="100%" noshade="" style="color:#A0A0A0" align="center">
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<p style="margin:0in">OK. So it sounds like I need to add the same requirement into 3 SDLP books (TM, AOS, USLP)…something to the effect that the frame data field contents of OID transfer frames shall be generated by the use of the mandatory
<span style="font-size:12.0pt">PN sequence by means of the 32-cell LFSR. </span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt">Question – Can someone send me the specification (and the viewgraph presentation) for this PN sequence generator (32-cell LFSR), so that I can reference it in those documents?</span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt">Thanks!</span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt">Greg</span><o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in"><b><span style="font-size:12.0pt">From: </span></b><span style="font-size:12.0pt">"Massimo.Bertinelli@esa.int" <Massimo.Bertinelli@esa.int><b><br>
Date: </b>Monday, January 25, 2021 at 12:58 PM<b><br>
To: </b>"Gian.Paolo.Calzolari@esa.int" <Gian.Paolo.Calzolari@esa.int><b><br>
Cc: </b>"Gilles.Moury@cnes.fr" <Gilles.Moury@cnes.fr>, "Kazz, Greg J (US 312B)" <greg.j.kazz@jpl.nasa.gov>, Matthew Cosby <matt.cosby@goonhilly.org><b><br>
Subject: </b>Re: OID Frames with mandatory PN sequence: FW: [EXTERNAL] Re: [Sls-slp] [SLS-CC] Joint C&S/SLP</span><o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">no change foreseen or needed in the coding book...we'll eventually introduce a longer randomiser, but the OID pattern is indipendent.</span>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
The C&S books simply refer to the protocol books for the pattern</span> <span style="font-size:10.0pt;font-family:"Arial",sans-serif">
<br>
<br>
<br>
---------------------------------------------------<br>
Massimo Bertinelli<br>
Communication Systems Engineer<br>
ESA/Estec<br>
<br>
Tel. +31 (0)71 5653435<br>
--------------------------------------------------</span> <br>
<br>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
From: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">Gian Paolo Calzolari/esoc/ESA</span>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
To: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"Kazz, Greg J (US 312B)" <greg.j.kazz@jpl.nasa.gov></span>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
Cc: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"Matthew Cosby" <matt.cosby@goonhilly.org>, Massimo Bertinelli/estec/ESA@ESA, Gilles.Moury@cnes.fr</span>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
Date: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">25/01/2021 17:34</span>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
Subject: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">Re: OID Frames with mandatory PN sequence: FW: [EXTERNAL] Re: [Sls-slp] [SLS-CC] Joint C&S/SLP</span>
<o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="0" width="100%" noshade="" style="color:#A0A0A0" align="center">
</div>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:2.5in;margin-left:0in">
<br>
<br>
<span style="font-size:12.0pt"><br>
Greg, <br>
I am not sure there will be any pink sheets to coding book. <br>
Up to Massimo to confirm. <br>
Ciao</span> <br>
<span style="font-size:12.0pt"><br>
Gian Paolo</span><br>
<span style="font-size:12.0pt"><br>
Sent from my iPhone</span> <br>
<span style="font-size:12.0pt"><br>
On 25. Jan 2021, at 17:19, Kazz, Greg J (US 312B) <greg.j.kazz@jpl.nasa.gov> wrote:</span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt">Gian Paolo,</span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt">This new requirement on making the use of the PN sequence mandatory for OID frames is not in any of the SDLP books yet.</span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt">If you can email me the relevant pink sheets to the coding books regarding this new requirement, then I can generate the additional pink sheet changes to TM, AOS, and USLP SDLPs. Thereafter I will need to
send them out to the SLP WG for a quick review.</span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt">Regards,</span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt">Greg</span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p style="margin:0in"><b><span style="font-size:12.0pt">From: </span></b><span style="font-size:12.0pt">"Gian.Paolo.Calzolari@esa.int" <Gian.Paolo.Calzolari@esa.int><b><br>
Date: </b>Monday, January 25, 2021 at 7:39 AM<b><br>
To: </b>"Kazz, Greg J (US 312B)" <greg.j.kazz@jpl.nasa.gov><b><br>
Cc: </b>Matthew Cosby <Matt.Cosby@Goonhilly.org>, "Massimo.Bertinelli@esa.int" <Massimo.Bertinelli@esa.int>, "Gilles.Moury@cnes.fr" <Gilles.Moury@cnes.fr><b><br>
Subject: </b>OID Frames with mandatory PN sequence: FW: [EXTERNAL] Re: [Sls-slp] [SLS-CC] Joint C&S/SLP</span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Greg,</span><span style="font-size:12.0pt">
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
is this already in any of the Space Data Link Protocols books?</span><span style="font-size:12.0pt">
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
If not & needed, any chance to update the books before starting the CESG/CMC Polls for Agency Review?</span><span style="font-size:12.0pt">
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
<br>
Thanks</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
<br>
Gian Paolo</span><span style="font-size:12.0pt"> <br>
<br>
</span><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
<br>
From: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">Massimo Bertinelli/estec/ESA</span><span style="font-size:12.0pt">
</span><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
To: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"Kazz, Greg J (US 312B)" <greg.j.kazz@jpl.nasa.gov></span><span style="font-size:12.0pt">
</span><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
Cc: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"Gian.Paolo.Calzolari@esa.int" <Gian.Paolo.Calzolari@esa.int>, "Matthew Cosby" <Matt.Cosby@Goonhilly.org></span><span style="font-size:12.0pt">
</span><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
Date: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">23-01-21 21:58</span><span style="font-size:12.0pt">
</span><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
Subject: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">Re: FW: [EXTERNAL] Re: [Sls-slp] [SLS-CC] Joint C&S/SLP</span><span style="font-size:12.0pt">
</span><o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="0" width="100%" noshade="" style="color:#A0A0A0" align="center">
</div>
<p style="margin:0in"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
<br>
That's good news, thank you.</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
Sorry for losing track on this point, I should have kept better notes.</span><span style="font-size:12.0pt">
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
<br>
Best regards,</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
Massimo</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
<br>
<br>
---------------------------------------------------<br>
Massimo Bertinelli<br>
Communication Systems Engineer<br>
ESA/Estec<br>
<br>
Tel. +31 (0)71 5653435<br>
--------------------------------------------------</span><span style="font-size:12.0pt">
<br>
<br>
<br>
</span><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
<br>
From: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"Kazz, Greg J (US 312B)" <greg.j.kazz@jpl.nasa.gov></span><span style="font-size:12.0pt">
</span><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
To: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"Massimo.Bertinelli@esa.int" <Massimo.Bertinelli@esa.int></span><span style="font-size:12.0pt">
</span><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
Cc: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"Gian.Paolo.Calzolari@esa.int" <Gian.Paolo.Calzolari@esa.int>, "Matthew Cosby" <Matt.Cosby@Goonhilly.org></span><span style="font-size:12.0pt">
</span><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
Date: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">23/01/2021 18:48</span><span style="font-size:12.0pt">
</span><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
Subject: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">FW: [EXTERNAL] Re: [Sls-slp] [SLS-CC] Joint C&S/SLP</span><span style="font-size:12.0pt">
</span><o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="0" width="100%" noshade="" style="color:#A0A0A0" align="center">
</div>
<p><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt">Hi Massimo,</span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt">If I recall correctly at the joint meeting in Dec. 2019, SLP WG concurred with you back in May 2019 on the use of the mandatory PN sequence by means of the 32-cell LFSR as you stated in your last email to
me. The remaining undecided party at that time was NASA/GSFC, which later also agreed documented below in your email from Dec. 6. So as far as I can tell, the issue is resolved and can go now to agency review.</span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt">Best regards,</span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt">Greg</span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p style="margin:0in"><b><span style="font-size:12.0pt">From: </span></b><span style="font-size:12.0pt">SLS-SLP <sls-slp-bounces@mailman.ccsds.org> on behalf of "Massimo.Bertinelli@esa.int" <Massimo.Bertinelli@esa.int><b><br>
Date: </b>Friday, December 6, 2019 at 12:16 AM<b><br>
To: </b>"Enrico.Vassallo@esa.int" <Enrico.Vassallo@esa.int>, "Gian.Paolo.Calzolari@esa.int" <Gian.Paolo.Calzolari@esa.int>, Space Link Coding & Synchronization Working Group <sls-cc@mailman.ccsds.org>, "sls-slp@mailman.ccsds.org" <sls-slp@mailman.ccsds.org><b><br>
Subject: </b>[EXTERNAL] Re: [Sls-slp] [SLS-CC] Joint C&S/SLP</span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p style="margin:0in"><b><span style="font-size:10.0pt;font-family:"Verdana",sans-serif">This message has been archived. </span></b><a href="https://evserver1.jpl.nasa.gov/EnterpriseVault/ViewMessage.asp?VaultId=10036FD0C335539419F44551B26993E651110000evserver1&SavesetId=202006293430735~201912060816280000~Z~710AAF1FD87EBB11F6181E489D6055F1"><b><span style="font-size:10.0pt;font-family:"Verdana",sans-serif">View
the original item </span></b></a><o:p></o:p></p>
<p class="MsoNormal"><br>
<span style="font-size:10.0pt;font-family:"Verdana",sans-serif">A brief update:<br>
<br>
OID - the action on NASA/GSFC is closed. V. Sank confirmed the feasibility and the agreement (making the random pattern OID mandatory) is confirmed<br>
<br>
USLP - the second action refers specifically to the concerns raised by Wolfgang Hell about "systematic retransmission" in section 4.2.10.8 of USLP with respect to 231.0<br>
I'm sorry that my formulation in yesterday's notes was not clear.<br>
<br>
Best regards,<br>
Massimo<br>
<br>
---------------------------------------------------<br>
Massimo Bertinelli<br>
Communication Systems Engineer<br>
ESA/Estec<br>
<br>
Tel. +31 (0)71 5653435<br>
--------------------------------------------------<br>
<br>
<br>
<br>
From: Massimo.Bertinelli@esa.int<br>
To: brent.r.andres@nasa.gov, Enrico.Vassallo@esa.int, Gian.Paolo.Calzolari@esa.int, sls-cc@mailman.ccsds.org, sls-slp@mailman.ccsds.org<br>
Date: 05/12/2019 18:33<br>
Subject: [SLS-CC] Joint C&S/SLP<br>
Sent by: "SLS-CC" <sls-cc-bounces@mailman.ccsds.org><br>
________________________________<br>
<br>
<br>
<br>
Dear all,<br>
<br>
a very brief summary of our discussion:<br>
<br>
- OID<br>
Most of the participants agreed to make the proposal (OID random pattern) mandatory.<br>
Participants from NASA/GSFC asked for more time to confirm (or not) the decision<br>
The proposal, once agreed, will be anyway subject to Agency Review<br>
AI (V. Sank): report NASA/GSFC position by end of December 12<br>
<br>
- TERMINOLOGY<br>
G. Kazz/NASA presented a proposal to align the terminology (regarding re-transmission) of the protocol books (232.1-B-2 and 232.0-B-3) to that used in the coding<br>
book (231.0-B)<br>
G. P. Calzolari/AD stated that the change of terminology was not actually required, and proper referencing inside the protocol books would achieve the target.<br>
This will translate in actions internal to the SLP WG and the issue, from the joint C&S/SLP point of view, is closed<br>
<br>
- USLP<br>
G. Kazz/NASA presented the (limited) changes required in 231.0-B (TC coding book) in order to reference 732.1 (USLP), stating how USLP already foresees this service<br>
It was agreed background underlying the actual need for this change (possibly linked to Lunar missions) will be provide.<br>
Besides, it was agreed to provide material (presentation/paper...) to show how the use of USLP would not be detrimental<br>
to the TC service<br>
AI (G. Kazz): provide rationale for the change<br>
AI (G. Kazz): provide material about use of USLP with TC, showing compatibility<br>
<br>
<br>
---------------------------------------------------<br>
Massimo Bertinelli<br>
Communication Systems Engineer<br>
ESA/Estec<br>
<br>
Tel. +31 (0)71 5653435<br>
--------------------------------------------------<br>
<br>
__________________<br>
<br>
<br>
<br>
Dear all,<br>
<br>
based on the results of the poll, we are going to have a first joint C&S/SLP discussion on the following topics on Thursday 5 December, starting at 4pm (CET).<br>
<br>
- introduction of OID random pattern<br>
- possible alignment of terminology in the TC books regarding retransmission<br>
- additionally, SLP would like to discuss adding USLP to the TC coding book and assessing its impact (other books are mentioned in the presentation, but agreement on these ones has already been reached)<br>
<br>
<br>
<br>
-- Do not delete or change any of the following text. --<br>
<br>
Join Skype for Business Online Meeting</span><u><span style="font-size:12.0pt;color:blue"><br>
<br>
</span></u><a href="https://urldefense.us/v3/__https:/meet.lync.com/esa.int/massimo.bertinelli/RPA8NUNC__;!!PvBDto6Hs4WbVuu7!e85B61MhDEeyvwiLNu96uy7QNTIknhu0IBh_zVmF7mTLywzRcM8uJqrQJKIqNikz0lMQA4kh$"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif">https://meet.lync.com/esa.int/massimo.bertinelli/RPA8NUNC</span></a><span style="font-size:10.0pt;font-family:"Verdana",sans-serif"><br>
<br>
Join by phone<br>
Toll Number: +31202588798<br>
Conference ID: 684255790<br>
<br>
Forgot your Dial-In PIN:</span><u><span style="font-size:12.0pt;color:blue"><br>
</span></u><a href="https://urldefense.us/v3/__https:/mysettings.lync.com/pstnconferencing__;!!PvBDto6Hs4WbVuu7!e85B61MhDEeyvwiLNu96uy7QNTIknhu0IBh_zVmF7mTLywzRcM8uJqrQJKIqNikz0s-GEkYO$"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif">https://mysettings.lync.com/pstnconferencing</span></a><span style="font-size:10.0pt;font-family:"Verdana",sans-serif"><br>
<br>
Global call-in numbers</span><u><span style="font-size:12.0pt;color:blue"><br>
</span></u><a href="https://urldefense.us/v3/__https:/dialin.lync.com/24f2f848-5af2-4842-8cf5-07a5ac61afc3__;!!PvBDto6Hs4WbVuu7!e85B61MhDEeyvwiLNu96uy7QNTIknhu0IBh_zVmF7mTLywzRcM8uJqrQJKIqNikz0pRdGn4H$"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif">https://dialin.lync.com/24f2f848-5af2-4842-8cf5-07a5ac61afc3</span></a><span style="font-size:10.0pt;font-family:"Verdana",sans-serif"><br>
<br>
or download:</span><u><span style="font-size:12.0pt;color:blue"><br>
</span></u><a href="https://urldefense.us/v3/__https:/esabox.esa.int/sfb/SfB_Global_Call-In_Numbers.pdf__;!!PvBDto6Hs4WbVuu7!e85B61MhDEeyvwiLNu96uy7QNTIknhu0IBh_zVmF7mTLywzRcM8uJqrQJKIqNikz0opSsdOO$"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif">https://esabox.esa.int/sfb/SfB_Global_Call-In_Numbers.pdf</span></a><span style="font-size:10.0pt;font-family:"Verdana",sans-serif"><br>
This message is intended only for the recipient(s) named above. It may contain proprietary information and/or<br>
protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received<br>
this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect<br>
personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo@esa.int).<br>
<br>
_______________________________________________<br>
SLS-CC mailing list<br>
SLS-CC@mailman.ccsds.org</span><u><span style="font-size:12.0pt;color:blue"><br>
</span></u><a href="https://urldefense.us/v3/__https:/mailman.ccsds.org/cgi-bin/mailman/listinfo/sls-cc__;!!PvBDto6Hs4WbVuu7!e85B61MhDEeyvwiLNu96uy7QNTIknhu0IBh_zVmF7mTLywzRcM8uJqrQJKIqNikz0l9pUSOc$"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sls-cc</span></a><span style="font-size:10.0pt;font-family:"Verdana",sans-serif"><br>
<br>
<br>
<br>
This message is intended only for the recipient(s) named above. It may contain proprietary information and/or<br>
protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received<br>
this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect<br>
personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo@esa.int).</span>
<o:p></o:p></p>
<p style="margin:0in"><b><span style="font-size:10.0pt;font-family:"Verdana",sans-serif">Attachments:</span></b><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="100%" style="width:100.0%;border-collapse:collapse">
<tbody>
<tr style="height:6.0pt">
<td width="75%" style="width:75.0%;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal"><a href="https://evserver1.jpl.nasa.gov/EnterpriseVault/ViewMessage.asp?VaultId=10036FD0C335539419F44551B26993E651110000evserver1&SavesetId=202006293430735~201912060816280000~Z~710AAF1FD87EBB11F6181E489D6055F1&AttachmentId=1"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif">ATT00001.txt
</span></a><o:p></o:p></p>
</td>
<td width="25%" style="width:25.0%;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal"><span style="font-size:7.0pt;font-family:"Verdana",sans-serif">(0 KB)</span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p style="margin:0in"><span style="font-size:12.0pt;color:white"> </span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="12" style="width:9.0pt;border-collapse:collapse">
<tbody>
<tr style="height:6.0pt">
<td width="12" style="width:9.0pt;padding:0in 0in 0in 0in;height:6.0pt"></td>
</tr>
</tbody>
</table>
<p style="margin:0in"><span style="font-size:12.0pt"> [attachment "@" deleted by Massimo Bertinelli/estec/ESA]
</span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:10.0pt;font-family:"Courier New"">This message is intended only for the recipient(s) named above. It may contain proprietary information and/or</span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:10.0pt;font-family:"Courier New"">protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received</span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:10.0pt;font-family:"Courier New"">this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect</span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:10.0pt;font-family:"Courier New"">personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo@esa.int).</span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:10.0pt;font-family:"Courier New"">This message is intended only for the recipient(s) named above. It may contain proprietary information and/or</span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:10.0pt;font-family:"Courier New"">protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received</span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:10.0pt;font-family:"Courier New"">this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect</span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:10.0pt;font-family:"Courier New"">personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo@esa.int).</span><o:p></o:p></p>
<pre>This message is intended only for the recipient(s) named above. It may contain proprietary information and/or<o:p></o:p></pre>
<pre>protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received<o:p></o:p></pre>
<pre>this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect<o:p></o:p></pre>
<pre>personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo@esa.int).<o:p></o:p></pre>
</div>
</body>
</html>