<span style=" font-size:10pt;font-family:sans-serif">Dear Dennis,</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">recognizing that
in the 401 glossary we have </span>
<br>
<br><span style=" font-size:11pt;font-family:Times New Roman">sps or s/s
Symbols Per Second</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">what about using
coded (M) (k) sps instead of coded (M) (k) sym/s? Other views are for using
coded (M) (k) symbol/s.</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Of course we will
need to change the glossary once also the telemetry recommendations are
aligned and s/s does not exist anymore.</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Regards, Enrico</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif"> </span>
<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">Enrico
Vassallo/esoc/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">"Lee,
Dennis K (332G)" <Dennis.K.Lee@jpl.nasa.gov></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Cc:
</span><span style=" font-size:9pt;font-family:sans-serif">"Andres,
Brent (GSFC-567.0)[AS and D, Inc.]" <brent.r.andres@nasa.gov>,
"Charlson, Deane R. (GSFC-5670)" <deane.r.charlson@nasa.gov>,
"Kazz, Greg J (312B)" <Greg.J.Kazz@jpl.nasa.gov>, "GARON,
Howard M (GSFC-567.0)[MUNIZ] (howard.garon@nasa.gov)" <howard.garon@nasa.gov>,
"Hamkins, Jon (3320)" <Jon.Hamkins@jpl.nasa.gov>, "Andrews,
Kenneth S (332B)" <Kenneth.S.Andrews@jpl.nasa.gov>, "Powers,
Michael K. (GSFC-5670)" <michael.k.powers@nasa.gov>, "Rodriguez,
Shannon (GSFC-5670)" <shannon.rodriguez-1@nasa.gov>, "'victor.j.sank@nasa.gov'"
<victor.j.sank@nasa.gov>, "'wai.h.fong@nasa.gov'" <wai.h.fong@nasa.gov>,
"HUANG, WEI-CHUNG. (GSFC-5670) (weichung.huang@nasa.gov)" <weichung.huang@nasa.gov>,
sls-rfm@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">10/12/2018
09:34</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-rfm] Proposed editorial changes to telecommand recommendations in
401</span>
<br>
<hr noshade>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Dear Dennis,</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">I agree with NASA's
proposal. Gian Paolo had even suggested adding the picture you are quoting
so ESA and NASA are in line on this one.</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">I will take care
if this and I kindly ask you to make a proposal for the rest of the Blue
Book, in time for the next meeting.</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Regards, Enrico</span>
<br>
<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">"Lee,
Dennis K (332G)" <Dennis.K.Lee@jpl.nasa.gov></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"
<Enrico.Vassallo@esa.int></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Cc:
</span><span style=" font-size:9pt;font-family:sans-serif">"'victor.j.sank@nasa.gov'"
<victor.j.sank@nasa.gov>, "Hamkins, Jon (3320)" <Jon.Hamkins@jpl.nasa.gov>,
"Andrews, Kenneth S (332B)" <Kenneth.S.Andrews@jpl.nasa.gov>,
"Kazz, Greg J (312B)" <Greg.J.Kazz@jpl.nasa.gov>, "GARON,
Howard M (GSFC-567.0)[MUNIZ] (howard.garon@nasa.gov)" <howard.garon@nasa.gov>,
"'wai.h.fong@nasa.gov'" <wai.h.fong@nasa.gov>, "Rodriguez,
Shannon (GSFC-5670)" <shannon.rodriguez-1@nasa.gov>, "Andres,
Brent (GSFC-567.0)[AS and D, Inc.]" <brent.r.andres@nasa.gov>,
"HUANG, WEI-CHUNG. (GSFC-5670) (weichung.huang@nasa.gov)" <weichung.huang@nasa.gov>,
"Powers, Michael K. (GSFC-5670)" <michael.k.powers@nasa.gov>,
"Charlson, Deane R. (GSFC-5670)" <deane.r.charlson@nasa.gov></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Date:
</span><span style=" font-size:9pt;font-family:sans-serif">10/12/2018
08:25</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-rfm] Proposed editorial changes to telecommand recommendations in
401</span>
<br>
<hr noshade>
<br>
<br>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">Enrico,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">There
were comments from a number of NASA reviewers that “s/s” is a confusing
notation that should not be used. The abbreviation “s” is used
to mean two different things in the numerator and denominator. Furthermore,
“s” as an abbreviation for symbol is ambiguous since it doesn’t differentiate
between code symbols and channel symbols. </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">The
NASA proposal is to replace “s/s” with “coded sym/s”, and “ks/s”
with “coded ksym/s”. This would be aligned with the terminology
in 211.2-B-2 (see Figure 1-2 attached), and help differentiate from the
common use of “symbol” to mean “baud” in the literature and in industry.
Ultimately, we would like to see the rest of the 401 Blue Book aligned
this way as well, with references to "symbols" to be clarified
as either "coded symbols" or "channel symbols"</span><span style=" font-size:12pt;font-family:Times New Roman">,
"</span><span style=" font-size:11pt;color:#004080;font-family:Calibri">s/s"
to be replaced by "coded sym/s" or "channel sym/s"
as appropriate, and "R_s" to be clarified as either "R_cs"
or "R_chs". </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">Thanks,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">Denis</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"><b>From:</b>
SLS-RFM <sls-rfm-bounces@mailman.ccsds.org> <b>On Behalf Of </b>Enrico.Vassallo@esa.int<b><br>
Sent:</b> Wednesday, December 5, 2018 3:12 AM<b><br>
To:</b> sls-rfm@mailman.ccsds.org<b><br>
Subject:</b> [Sls-rfm] Proposed editorial changes to telecommand recommendations
in 401</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Times New Roman"> </span></p>
<p style="margin-top:0px;margin-Bottom:240px"><span style=" font-size:10pt;font-family:Arial">Dear
All,</span><span style=" font-size:12pt;font-family:Times New Roman"> <br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
as you know all our missions have used or are currently using the standard
telecommand BCH (63,56) encoding. For all these cases, the bandwidth expansion
is 1.125 which basically means bit rate equals symbol rate. For this and
other historical reasons, all 401 recommendations for telecommand only
talk about bit rates assuming that they are actually symbol rates.</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><br>
With the first missions considering LDPC 1/2 for telecommand, there is
a need to remove the confusion by changing bit rates into symbol rates
while keeping the same limits as in present recommendations. I think this
is just a purely editorial issue.</span><span style=" font-size:12pt;font-family:Times New Roman">
<br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
Please let me know if you agree with my proposal and if anything is missing
in the attachments. If I do not hear from you by December 12, I assume
your concurrence and will submit the attached document (or its amended
version in case of suggestions) to the CCSDS editor.</span><span style=" font-size:12pt;font-family:Times New Roman">
<br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
Best Regards, Enrico</span><span style=" font-size:12pt;font-family:Times New Roman">
</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">This
message is intended only for the recipient(s) named above. It may contain
proprietary information and/or</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">protected
content. Any unauthorised disclosure, use, retention or dissemination is
prohibited. If you have received</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">this
e-mail in error, please notify the sender immediately. ESA applies appropriate
organisational measures to protect</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">personal
data, in case of data privacy queries, please contact the ESA Data Protection
Officer (</span><a href=mailto:dpo@esa.int><span style=" font-size:10pt;color:#0082bf;font-family:Courier New"><u>dpo@esa.int</u></span></a><span style=" font-size:10pt;font-family:Courier New">).[attachment
"Screen Shot 2018-12-05 at 3.20.40 PM.png" deleted by Enrico
Vassallo/esoc/ESA] </span></p>
<p style="margin-top:0px;margin-Bottom:0px"></p>
<p style="margin-top:0px;margin-Bottom:0px"></p>
<p style="margin-top:0px;margin-Bottom:0px"></p>
<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>