<span style=" font-size:10pt;font-family:sans-serif">Dear all, </span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">a very brief summary
of our discussion:</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">- <b>OID</b></span>
<br><span style=" font-size:10pt;font-family:sans-serif"> Most of
the participants agreed to make the proposal (OID random pattern) mandatory.</span>
<br><span style=" font-size:10pt;font-family:sans-serif"> Participants
from NASA/GSFC asked for more time to confirm (or not) the decision
</span>
<br><span style=" font-size:10pt;font-family:sans-serif"> The proposal,
once agreed, will be anyway subject to Agency Review</span>
<br><span style=" font-size:10pt;font-family:sans-serif"> <u>AI (V.
Sank): report NASA/GSFC position by end of December 12</u></span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">- <b>TERMINOLOGY</b></span>
<br><span style=" font-size:10pt;font-family:sans-serif"> 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>
<br><span style=" font-size:10pt;font-family:sans-serif"> book (231.0-B)</span>
<br><span style=" font-size:10pt;font-family:sans-serif"> 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>
<br><span style=" font-size:10pt;font-family:sans-serif"> 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>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">- USLP</span>
<br><span style=" font-size:10pt;font-family:sans-serif"> 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>
<br><span style=" font-size:10pt;font-family:sans-serif"> It was agreed
background underlying the actual need for this change (possibly linked
to Lunar missions) will be provide.</span>
<br><span style=" font-size:10pt;font-family:sans-serif"> Besides,
it was agreed to provide material (presentation/paper...) to show how the
use of USLP would not be detrimental</span>
<br><span style=" font-size:10pt;font-family:sans-serif"> to the TC
service</span>
<br><span style=" font-size:10pt;font-family:sans-serif"><u>AI (G. Kazz):
provide rationale for the change</u></span>
<br><span style=" font-size:10pt;font-family:sans-serif"><u> AI (G.
Kazz): provide material about use of USLP with TC, showing compatibility</u></span>
<br><span style=" font-size:10pt;font-family: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><span style=" font-size:10pt;font-family:sans-serif">__________________</span>
<br>
<br>
<br>
<br><span style=" font-size:9pt;font-family:Default MultiLingual">Dear
all,</span>
<br>
<br><span style=" font-size:9pt;font-family:Default MultiLingual">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>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">- 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>
<br><span style=" font-size:9pt;font-family:Default MultiLingual"><br>
<br>
-- Do not delete or change any of the following text. --<br>
<br>
Join Skype for Business Online Meeting<br>
<br>
</span><a href=https://meet.lync.com/esa.int/massimo.bertinelli/RPA8NUNC><span style=" font-size:9pt;font-family:Default MultiLingual">https://meet.lync.com/esa.int/massimo.bertinelli/RPA8NUNC</span></a><span style=" font-size:9pt;font-family:Default MultiLingual"><br>
<br>
Join by phone<br>
Toll Number: +31202588798<br>
Conference ID: 684255790<br>
<br>
Forgot your Dial-In PIN:<br>
</span><a href=https://mysettings.lync.com/pstnconferencing><span style=" font-size:9pt;font-family:Default MultiLingual">https://mysettings.lync.com/pstnconferencing</span></a><span style=" font-size:9pt;font-family:Default MultiLingual"><br>
<br>
Global call-in numbers<br>
</span><a href="https://dialin.lync.com/24f2f848-5af2-4842-8cf5-07a5ac61afc3"><span style=" font-size:9pt;font-family:Default MultiLingual">https://dialin.lync.com/24f2f848-5af2-4842-8cf5-07a5ac61afc3</span></a><span style=" font-size:9pt;font-family:Default MultiLingual"><br>
<br>
or download:<br>
</span><a href="https://esabox.esa.int/sfb/SfB_Global_Call-In_Numbers.pdf"><span style=" font-size:9pt;font-family:Default MultiLingual">https://esabox.esa.int/sfb/SfB_Global_Call-In_Numbers.pdf</span></a><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>