<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Dear Enrico,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">The consensus over here is that using coded (M) (k) symbol/s would be best. Also agree on the need to update the glossary.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Dennis<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Enrico.Vassallo@esa.int <Enrico.Vassallo@esa.int>
<br>
<b>Sent:</b> Thursday, December 13, 2018 12:44 AM<br>
<b>To:</b> Lee, Dennis K (332G) <Dennis.K.Lee@jpl.nasa.gov><br>
<b>Cc:</b> 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<br>
<b>Subject:</b> RE: [Sls-rfm] Proposed editorial changes to telecommand recommendations in 401<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Dear Dennis,</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">recognizing that in the 401 glossary we have
</span><br>
<br>
<span style="font-size:11.0pt">sps or s/s Symbols Per Second</span> <br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",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:10.0pt;font-family:"Arial",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:10.0pt;font-family:"Arial",sans-serif">Regards, Enrico</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"> </span> <br>
<br>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">From: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">Enrico Vassallo/esoc/ESA</span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">To: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"Lee, Dennis K (332G)" <</span><a href="mailto:Dennis.K.Lee@jpl.nasa.gov"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">Dennis.K.Lee@jpl.nasa.gov</span></a><span style="font-size:9.0pt;font-family:"Arial",sans-serif">></span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Cc: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"Andres, Brent (GSFC-567.0)[AS and D, Inc.]" <</span><a href="mailto:brent.r.andres@nasa.gov"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">brent.r.andres@nasa.gov</span></a><span style="font-size:9.0pt;font-family:"Arial",sans-serif">>,
"Charlson, Deane R. (GSFC-5670)" <</span><a href="mailto:deane.r.charlson@nasa.gov"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">deane.r.charlson@nasa.gov</span></a><span style="font-size:9.0pt;font-family:"Arial",sans-serif">>, "Kazz, Greg
J (312B)" <</span><a href="mailto:Greg.J.Kazz@jpl.nasa.gov"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">Greg.J.Kazz@jpl.nasa.gov</span></a><span style="font-size:9.0pt;font-family:"Arial",sans-serif">>, "GARON, Howard M (GSFC-567.0)[MUNIZ]
(</span><a href="mailto:howard.garon@nasa.gov"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">howard.garon@nasa.gov</span></a><span style="font-size:9.0pt;font-family:"Arial",sans-serif">)" <</span><a href="mailto:howard.garon@nasa.gov"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">howard.garon@nasa.gov</span></a><span style="font-size:9.0pt;font-family:"Arial",sans-serif">>,
"Hamkins, Jon (3320)" <</span><a href="mailto:Jon.Hamkins@jpl.nasa.gov"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">Jon.Hamkins@jpl.nasa.gov</span></a><span style="font-size:9.0pt;font-family:"Arial",sans-serif">>, "Andrews, Kenneth S (332B)"
<</span><a href="mailto:Kenneth.S.Andrews@jpl.nasa.gov"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">Kenneth.S.Andrews@jpl.nasa.gov</span></a><span style="font-size:9.0pt;font-family:"Arial",sans-serif">>, "Powers, Michael K. (GSFC-5670)" <</span><a href="mailto:michael.k.powers@nasa.gov"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">michael.k.powers@nasa.gov</span></a><span style="font-size:9.0pt;font-family:"Arial",sans-serif">>,
"Rodriguez, Shannon (GSFC-5670)" <</span><a href="mailto:shannon.rodriguez-1@nasa.gov"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">shannon.rodriguez-1@nasa.gov</span></a><span style="font-size:9.0pt;font-family:"Arial",sans-serif">>, "'victor.j.sank@nasa.gov'"
<</span><a href="mailto:victor.j.sank@nasa.gov"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">victor.j.sank@nasa.gov</span></a><span style="font-size:9.0pt;font-family:"Arial",sans-serif">>, "'wai.h.fong@nasa.gov'" <</span><a href="mailto:wai.h.fong@nasa.gov"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">wai.h.fong@nasa.gov</span></a><span style="font-size:9.0pt;font-family:"Arial",sans-serif">>,
"HUANG, WEI-CHUNG. (GSFC-5670) (</span><a href="mailto:weichung.huang@nasa.gov"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">weichung.huang@nasa.gov</span></a><span style="font-size:9.0pt;font-family:"Arial",sans-serif">)" <</span><a href="mailto:weichung.huang@nasa.gov"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">weichung.huang@nasa.gov</span></a><span style="font-size:9.0pt;font-family:"Arial",sans-serif">>,
</span><a href="mailto:sls-rfm@mailman.ccsds.org"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">sls-rfm@mailman.ccsds.org</span></a>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Date: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">10/12/2018 09:34</span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Subject: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">RE: [Sls-rfm] Proposed editorial changes to telecommand recommendations in 401</span>
<o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="3" width="100%" noshade="" style="color:#A0A0A0" align="center">
</div>
<p class="MsoNormal"><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Dear Dennis,</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",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:10.0pt;font-family:"Arial",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:10.0pt;font-family:"Arial",sans-serif">Regards, Enrico</span>
<br>
<br>
<br>
<br>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">From: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"Lee, Dennis K (332G)" <</span><a href="mailto:Dennis.K.Lee@jpl.nasa.gov"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">Dennis.K.Lee@jpl.nasa.gov</span></a><span style="font-size:9.0pt;font-family:"Arial",sans-serif">></span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">To: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"</span><a href="mailto:Enrico.Vassallo@esa.int"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">Enrico.Vassallo@esa.int</span></a><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"
<</span><a href="mailto:Enrico.Vassallo@esa.int"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">Enrico.Vassallo@esa.int</span></a><span style="font-size:9.0pt;font-family:"Arial",sans-serif">></span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Cc: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"'victor.j.sank@nasa.gov'" <</span><a href="mailto:victor.j.sank@nasa.gov"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">victor.j.sank@nasa.gov</span></a><span style="font-size:9.0pt;font-family:"Arial",sans-serif">>,
"Hamkins, Jon (3320)" <</span><a href="mailto:Jon.Hamkins@jpl.nasa.gov"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">Jon.Hamkins@jpl.nasa.gov</span></a><span style="font-size:9.0pt;font-family:"Arial",sans-serif">>, "Andrews, Kenneth S (332B)"
<</span><a href="mailto:Kenneth.S.Andrews@jpl.nasa.gov"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">Kenneth.S.Andrews@jpl.nasa.gov</span></a><span style="font-size:9.0pt;font-family:"Arial",sans-serif">>, "Kazz, Greg J (312B)" <</span><a href="mailto:Greg.J.Kazz@jpl.nasa.gov"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">Greg.J.Kazz@jpl.nasa.gov</span></a><span style="font-size:9.0pt;font-family:"Arial",sans-serif">>,
"GARON, Howard M (GSFC-567.0)[MUNIZ] (</span><a href="mailto:howard.garon@nasa.gov"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">howard.garon@nasa.gov</span></a><span style="font-size:9.0pt;font-family:"Arial",sans-serif">)" <</span><a href="mailto:howard.garon@nasa.gov"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">howard.garon@nasa.gov</span></a><span style="font-size:9.0pt;font-family:"Arial",sans-serif">>,
"'wai.h.fong@nasa.gov'" <</span><a href="mailto:wai.h.fong@nasa.gov"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">wai.h.fong@nasa.gov</span></a><span style="font-size:9.0pt;font-family:"Arial",sans-serif">>, "Rodriguez, Shannon (GSFC-5670)"
<</span><a href="mailto:shannon.rodriguez-1@nasa.gov"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">shannon.rodriguez-1@nasa.gov</span></a><span style="font-size:9.0pt;font-family:"Arial",sans-serif">>, "Andres, Brent (GSFC-567.0)[AS and D,
Inc.]" <</span><a href="mailto:brent.r.andres@nasa.gov"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">brent.r.andres@nasa.gov</span></a><span style="font-size:9.0pt;font-family:"Arial",sans-serif">>, "HUANG, WEI-CHUNG. (GSFC-5670) (</span><a href="mailto:weichung.huang@nasa.gov"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">weichung.huang@nasa.gov</span></a><span style="font-size:9.0pt;font-family:"Arial",sans-serif">)"
<</span><a href="mailto:weichung.huang@nasa.gov"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">weichung.huang@nasa.gov</span></a><span style="font-size:9.0pt;font-family:"Arial",sans-serif">>, "Powers, Michael K. (GSFC-5670)" <</span><a href="mailto:michael.k.powers@nasa.gov"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">michael.k.powers@nasa.gov</span></a><span style="font-size:9.0pt;font-family:"Arial",sans-serif">>,
"Charlson, Deane R. (GSFC-5670)" <</span><a href="mailto:deane.r.charlson@nasa.gov"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">deane.r.charlson@nasa.gov</span></a><span style="font-size:9.0pt;font-family:"Arial",sans-serif">></span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Date: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">10/12/2018 08:25</span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Subject: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">RE: [Sls-rfm] Proposed editorial changes to telecommand recommendations in 401</span>
<o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="3" width="100%" noshade="" style="color:#A0A0A0" align="center">
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#004080">Enrico,</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#004080"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#004080">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><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#004080"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#004080">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:11.0pt;font-family:"Calibri",sans-serif;color:#004080">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><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#004080"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#004080">Thanks,</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#004080">Denis</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#004080"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> SLS-RFM <</span><a href="mailto:sls-rfm-bounces@mailman.ccsds.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">sls-rfm-bounces@mailman.ccsds.org</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>
<b>On Behalf Of </b></span><a href="mailto:Enrico.Vassallo@esa.int"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Enrico.Vassallo@esa.int</span></a><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><br>
Sent:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Wednesday, December 5, 2018 3:12 AM<b><br>
To:</b> </span><a href="mailto:sls-rfm@mailman.ccsds.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">sls-rfm@mailman.ccsds.org</span></a><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><br>
Subject:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> [Sls-rfm] Proposed editorial changes to telecommand recommendations in 401</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"> <o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:2.5in;margin-left:0in">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Dear All,</span> <br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><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:10.0pt;font-family:"Arial",sans-serif"><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>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><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> <br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
Best Regards, Enrico</span> <o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Courier New"">This message is intended only for the recipient(s) named above. It may contain proprietary information and/or</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Courier New"">protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Courier New"">this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;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:10.0pt;font-family:"Courier New";color:#0082BF">dpo@esa.int</span></a><span style="font-size:10.0pt;font-family:"Courier New"">).[attachment
"Screen Shot 2018-12-05 at 3.20.40 PM.png" deleted by Enrico Vassallo/esoc/ESA] </span>
<o:p></o:p></p>
<pre>This message is intended only for the recipient(s) named above. It may contain proprietary information and/or<o:p></o:p></pre>
<pre>protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received<o:p></o:p></pre>
<pre>this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect<o:p></o:p></pre>
<pre>personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (<a href="mailto:dpo@esa.int">dpo@esa.int</a>).<o:p></o:p></pre>
</div>
</body>
</html>