<span style=" font-size:10pt;font-family:sans-serif">Dear Massimo, dear
all</span>
<br><span style=" font-size:10pt;font-family:sans-serif"> for the
Blue Book, I have just a single comment:</span>
<br>
<ul>
<li>
<li><span style=" font-size:10pt;font-family:Courier New">Sentence 4.4.3,
about LDPC fill data, should be modified as well. Currently it reads as
</span></ul>
<br><span style=" font-size:10pt;font-family:Courier New">
"The fill
data shall be added before randomization and randomized with the Transfer
Frame." </span>
<br>
<br><span style=" font-size:10pt;font-family:Courier New">Possible Suggestion
could be </span>
<br>
<br><span style=" font-size:10pt;font-family:Courier New">
"The fill
data shall be added before encoding and randomized as part of the codeword".</span>
<br>
<br>
<br>
<br><span style=" font-size:8pt;color:#808080;font-family:Verdana"><b>HE
Space Operations for ESA - European Space Agency</b></span>
<br><span style=" font-size:8pt;color:#00a1e0;font-family:Verdana"><b>Ph.D.
Andrea Modenini</b></span><span style=" font-size:8pt;color:#808080;font-family:Verdana"><b><br>
Communication Systems & Technologies Engineer</b></span><span style=" font-size:12pt;font-family:Tms Rmn"><b>
</b></span><span style=" font-size:8pt;color:#808080;font-family:Verdana"><br>
TT&C and PDT Systems & Techniques Section (TEC-EST)<br>
RF Systems Division<b><br>
ESTEC</b><br>
Keplerlaan 1, PO Box 299<br>
NL-2200 AG Noordwijk, The Netherlands</span><span style=" font-size:8pt;color:blue;font-family:Verdana"><u><br>
</u></span><span style=" font-size:8pt;color:#808080;font-family:Verdana">andrea.modenini@esa.int
| </span><a href=http://www.esa.int/><span style=" font-size:8pt;color:#8f8f8f;font-family:Verdana"><u>www.esa.int</u></span></a><span style=" font-size:8pt;color:#808080;font-family:Verdana"><br>
T +31 71 56 53439</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">"Space
Link Coding & Synchronization Working Group" <sls-cc@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">27/01/2020
09:39</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]
TC coding blue book (231.0-B), new draft</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>
Ken provided a new draft version of the TC Coding Blue Book (231.0-B),
following action AI_19_16.</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:sans-serif"><br>
The main change, discussed and agreed in Darmstadt last year, is about
the order inversion of encoding and randomisation when LDPC coding is used.</span><span style=" font-size:12pt">
</span><span style=" font-size:10pt;font-family:sans-serif"><br>
Ken also added an annex with PICs. I don't remember whether this was agreed
(and I don't have any evidence in my minutes) but of course I could have
simply forgotten. In any case,</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:sans-serif"><br>
we should have a look and discuss about it.</span><span style=" font-size:12pt">
</span><span style=" font-size:10pt;font-family:sans-serif"><br>
Could you please send your comments by Monday 2 March (4 weeks from now,
as agreed in AI_19_17)?</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:sans-serif"><br>
Following this deadline and based on the comments received, I will trigger
the process for the Agency Review.</span><span style=" font-size:12pt">
<br>
</span><span style=" font-size:10pt;font-family:sans-serif"><br>
Best regards,</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:sans-serif"><br>
Massimo</span><span style=" font-size:12pt"> <br>
</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>
<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>
[attachment "TC SandC Blue Doc.v2.doc" deleted by Andrea Modenini/estec/ESA]
</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><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>