<span style=" font-size:9pt;color:#800080;font-family:sans-serif">-----
Forwarded by Enrico Vassallo/esoc/ESA on 06/12/2019 10:47 -----</span>
<br>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">From:
</span><span style=" font-size:9pt;font-family:sans-serif">Massimo
Bertinelli/estec/ESA</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">To:
</span><span style=" font-size:9pt;font-family:sans-serif">Enrico.Vassallo@esa.int,
Gian.Paolo.Calzolari@esa.int, "Space Link Coding & Synchronization
Working Group" <sls-cc@mailman.ccsds.org>, sls-slp@mailman.ccsds.org</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Date:
</span><span style=" font-size:9pt;font-family:sans-serif">06/12/2019
09:16</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Subject:
</span><span style=" font-size:9pt;font-family:sans-serif">Re:
[SLS-CC] Joint C&S/SLP</span>
<br>
<hr noshade>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">A brief update:</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">OID - the action
on NASA/GSFC is closed. V. Sank confirmed the feasibility and the agreement
(making the random pattern OID mandatory) is confirmed</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">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</span>
<br><span style=" font-size:10pt;font-family:sans-serif">I'm sorry that
my formulation in yesterday's notes was not clear.</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Best regards,</span>
<br><span style=" font-size:10pt;font-family:sans-serif">Massimo<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:9pt;color:#5f5f5f;font-family:sans-serif">From:
</span><span style=" font-size:9pt;font-family:sans-serif">Massimo.Bertinelli@esa.int</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">To:
</span><span style=" font-size:9pt;font-family:sans-serif">brent.r.andres@nasa.gov,
Enrico.Vassallo@esa.int, Gian.Paolo.Calzolari@esa.int, sls-cc@mailman.ccsds.org,
sls-slp@mailman.ccsds.org</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Date:
</span><span style=" font-size:9pt;font-family:sans-serif">05/12/2019
18:33</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Subject:
</span><span style=" font-size:9pt;font-family:sans-serif">[SLS-CC]
Joint C&S/SLP</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Sent
by: </span><span style=" font-size:9pt;font-family:sans-serif">"SLS-CC"
<sls-cc-bounces@mailman.ccsds.org></span>
<br>
<hr noshade>
<br>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Dear all, </span><span style=" font-size:12pt"><br>
</span><span style=" font-size:10pt;font-family:sans-serif"><br>
a very brief summary of our discussion:</span><span style=" font-size:12pt">
<br>
</span><span style=" font-size:10pt;font-family:sans-serif"><br>
- <b>OID</b></span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:sans-serif"><br>
Most of the participants agreed to make the proposal (OID random pattern)
mandatory.</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:sans-serif"><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</span><span style=" font-size:12pt">
</span><span style=" font-size:10pt;font-family:sans-serif"><br>
<u>AI (V. Sank): report NASA/GSFC position by end of December 12</u></span><span style=" font-size:12pt">
<br>
</span><span style=" font-size:10pt;font-family:sans-serif"><br>
- <b>TERMINOLOGY</b></span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:sans-serif"><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</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:sans-serif"><br>
book (231.0-B)</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:sans-serif"><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.</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:sans-serif"><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</span><span style=" font-size:12pt">
<br>
</span><span style=" font-size:10pt;font-family:sans-serif"><br>
- USLP</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:sans-serif"><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</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:sans-serif"><br>
It was agreed background underlying the actual need for this change (possibly
linked to Lunar missions) will be provide.</span><span style=" font-size:12pt">
</span><span style=" font-size:10pt;font-family:sans-serif"><br>
Besides, it was agreed to provide material (presentation/paper...) to
show how the use of USLP would not be detrimental</span><span style=" font-size:12pt">
</span><span style=" font-size:10pt;font-family:sans-serif"><br>
to the TC service</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:sans-serif"><u><br>
AI (G. Kazz): provide rationale for the change</u></span><span style=" font-size:12pt">
</span><span style=" font-size:10pt;font-family:sans-serif"><u><br>
AI (G. Kazz): provide material about use of USLP with TC, showing compatibility</u></span><span style=" font-size:12pt">
</span><span style=" font-size:10pt;font-family: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:12pt">
<br>
</span><span style=" font-size:10pt;font-family:sans-serif"><br>
__________________</span><span style=" font-size:12pt"> <br>
<br>
<br>
</span><span style=" font-size:9pt"><br>
Dear all,</span><span style=" font-size:12pt"> <br>
</span><span style=" font-size:9pt"><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).</span><span style=" font-size:12pt"> <br>
</span><span style=" font-size:10pt;font-family:sans-serif"><br>
- introduction of OID random pattern</span><span style=" font-size:12pt">
</span><span style=" font-size:10pt;font-family:sans-serif"><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)</span><span style=" font-size:12pt">
<br>
</span><span style=" font-size:9pt"><br>
<br>
<br>
-- Do not delete or change any of the following text. --<br>
<br>
Join Skype for Business Online Meeting<br>
</span><span style=" font-size:12pt;color:blue"><u><br>
</u></span><a href=https://meet.lync.com/esa.int/massimo.bertinelli/RPA8NUNC><span style=" font-size:9pt;color:blue"><u>https://meet.lync.com/esa.int/massimo.bertinelli/RPA8NUNC</u></span></a><span style=" font-size:9pt"><br>
<br>
Join by phone<br>
Toll Number: +31202588798<br>
Conference ID: 684255790<br>
<br>
Forgot your Dial-In PIN:</span><span style=" font-size:12pt;color:blue"><u><br>
</u></span><a href=https://mysettings.lync.com/pstnconferencing><span style=" font-size:9pt;color:blue"><u>https://mysettings.lync.com/pstnconferencing</u></span></a><span style=" font-size:9pt"><br>
<br>
Global call-in numbers</span><span style=" font-size:12pt;color:blue"><u><br>
</u></span><a href="https://dialin.lync.com/24f2f848-5af2-4842-8cf5-07a5ac61afc3"><span style=" font-size:9pt;color:blue"><u>https://dialin.lync.com/24f2f848-5af2-4842-8cf5-07a5ac61afc3</u></span></a><span style=" font-size:9pt"><br>
<br>
or download:</span><span style=" font-size:12pt;color:blue"><u><br>
</u></span><a href="https://esabox.esa.int/sfb/SfB_Global_Call-In_Numbers.pdf"><span style=" font-size:9pt;color:blue"><u>https://esabox.esa.int/sfb/SfB_Global_Call-In_Numbers.pdf</u></span></a>
<br><tt><span style=" font-size:12pt">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>
</span></tt>
<br><tt><span style=" font-size:10pt">_______________________________________________<br>
SLS-CC mailing list<br>
SLS-CC@mailman.ccsds.org<br>
</span></tt><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sls-cc"><tt><span style=" font-size:10pt">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sls-cc</span></tt></a><tt><span style=" font-size:10pt"><br>
</span></tt>
<br>
<br>
<br><PRE>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).
</PRE>