<span style=" font-size:10pt;font-family:sans-serif">Dear Ken,</span>
<br><span style=" font-size:10pt;font-family:sans-serif"> following
the comments we received, I believe we had WG consensus. All points are
accepted, except 2).</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">If you could please
provide us an updated draft accordingly and then we can ask for a SLS AD
resolution. </span>
<br><span style=" font-size:10pt;font-family:sans-serif">I guess it is
sufficient to reject the edit in Section 10.1, but please let me know.</span>
<br>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Thanks in advance,</span>
<br><span style=" font-size:10pt;font-family:sans-serif">Kind Regards</span>
<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, M +31 6 484 56 527</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">Andrea
Modenini/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">"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">28-07-21
16:01</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]
CCSDS 230.1-G-2.1 - Green Book TC - approved with comments - please check
deadline</span>
<br>
<hr noshade>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Dear colleagues,</span>
<br><span style=" font-size:10pt;font-family:sans-serif"> with reference
to the Green Book of the TC, at CESG pool, we got an approval with conditions
from SEA AD, with the feedback below.</span>
<br><span style=" font-size:10pt;font-family:sans-serif">Following discussion
with the SLS AD and DAD, it was decided to re-iterate such conditions at
WG level.</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Kindly, Ken already
took action to provide a draft of the TC Green Book implementing such edits
(see attachment).</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">I myself reviewed
the comments: </span>
<br><span style=" font-size:10pt;font-family:sans-serif">-Point 3, 4, and
5, look normal editorials.</span>
<br><span style=" font-size:10pt;font-family:sans-serif">-point 1) is about
including USLP. This appear in line with the Blue Book review that we had
recently</span>
<br><span style=" font-size:10pt;font-family:sans-serif">-point 2) implies
instead the introduction of CFDP and LTP for TC. Personally I am not aware
that we had any discussion/input in the WG for allowing the use of such
protocols for TC, nor I see any content in the BlueBook. </span>
<br><span style=" font-size:10pt;font-family:sans-serif">If this is the
case, my personal opinion would be to discard this last point.</span>
<br>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Starting from
this, could you please assess my conclusions and let me know any disagreement
no later than <b>13rd August EOB</b>?</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">In case deadline
<b><u>does not fit</u></b> because of planned vacation, please also let
me know that I will consider an extension.</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Kind Regards</span>
<br>
<br>
<br>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">----</span>
<br>
<br>
<p style="margin-top:0px;margin-Bottom:10px"><span style=" font-size:10pt;font-family:Segoe UI"><i>It's
great that this doc is now being updated, given all of the changes in the
C&S WG and other SLS standards. I identify the following Issues:</i></span></p>
<p style="margin-top:0px;margin-Bottom:10px"><span style=" font-size:10pt;font-family:Segoe UI"><i>1)
There is no mention of USLP, expecially in the variable length frame mode.
Only TC is included. This must be fixed. Too many sections
to list.</i></span></p>
<p style="margin-top:0px;margin-Bottom:10px"><span style=" font-size:10pt;font-family:Segoe UI"><i>2)
In sec 10.3.3.1 (and 10.3.3.4) the only option described for handling "long
wait times" on deep space links is the repeat function. However,
equally viable methods are to use CFDP of even LTP to provide automated
file or link layer reliability. These should be addressed.</i></span></p>
<p style="margin-top:0px;margin-Bottom:10px"><span style=" font-size:10pt;font-family:Segoe UI"><i>3)
The term "CODEWORD", "Codeword", and "codeword"
are all used, sometimes in the same sentence. They look different
but apparently mean the same thing. Provide some description of this
early in the doc to avoid any possible confusion. Too many sections
to list.</i></span></p>
<p style="margin-top:0px;margin-Bottom:10px"><span style=" font-size:10pt;font-family:Segoe UI"><i>4)
In Glossary "codeword" is not really defined, just a reference
is provided. Fix this. Also, both encoding and decoding definitions
only mention BCH, not LDPC. Please fix this throughout.</i></span></p>
<p style="margin-top:0px;margin-Bottom:10px"><span style=" font-size:10pt;font-family:Segoe UI"><i>5)
There are many new scholarly references, which is fine. At least
one, [27], appears to have no reference identified in the body of the text.
Please fix this.</i></span></p>
<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, M +31 6 484 56 527</span>
<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>