<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";}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
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.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
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">Enrico,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Yes, the 414.0-G-2 and 414.1-B-1 documents I mentioned
</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">are not ones that is affected by the proposal in SLS-CS_20-03 in the first place because they do not have polynomials, it just has the patterns of the components.. This is exactly the point
we are trying to make. Stating the pattern or showing a diagram of the generator shift register is unique, the polynomial is not. The 414 books are the only ones we noticed that have no ambiguity since they do not have polynomials. Hence our suggestion
to not state polynomials in future CCSDS books, unless some standard is decided upon.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Victor</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><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> Friday, June 26, 2020 8:09 AM<br>
<b>To:</b> Sank, Victor J. (GSFC-567.0)[SCIENCE SYSTEMS AND APPLICATIONS INC] <victor.j.sank@nasa.gov><br>
<b>Cc:</b> Kazz, Greg J (JPL-312B)[Jet Propulsion Laboratory] <greg.j.kazz@jpl.nasa.gov>; Border, James S (JPL-335D)[Jet Propulsion Laboratory] <james.s.border@jpl.nasa.gov>; sls-rfm@mailman.ccsds.org<br>
<b>Subject:</b> RE: [EXTERNAL] [Sls-rfm] CCSDS RFM WG AI_20-01 (PN register convention)<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">Victor,</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">I must say that I do not understand your proposal. The document you mention is not one that is affected by the proposal in SLS-CS_20-03 in the first place.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Anyway, I think we should proceed with agency review of REC 2.5.7B assuming I do not get other comments today. I would use the version just sent out by Jim, having just encapsulated the latest inclusion
in a note since this is not normative as suggested by our beloved AD.</span> <br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The PN action is due next September, so we have time to discuss.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Cheers, Enrico</span>
<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">"Sank, Victor J. (GSFC-567.0)[SCIENCE SYSTEMS AND APPLICATIONS INC]" <<a href="mailto:victor.j.sank@nasa.gov">victor.j.sank@nasa.gov</a>></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">"<a href="mailto:Enrico.Vassallo@esa.int">Enrico.Vassallo@esa.int</a>" <<a href="mailto:Enrico.Vassallo@esa.int">Enrico.Vassallo@esa.int</a>>,
"<a href="mailto:sls-rfm@mailman.ccsds.org">sls-rfm@mailman.ccsds.org</a>" <<a href="mailto:sls-rfm@mailman.ccsds.org">sls-rfm@mailman.ccsds.org</a>>, "Border, James S (JPL-335D)[Jet Propulsion Laboratory]" <<a href="mailto:james.s.border@jpl.nasa.gov">james.s.border@jpl.nasa.gov</a>></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">"Kazz, Greg J (JPL-312B)[Jet Propulsion Laboratory]" <<a href="mailto:greg.j.kazz@jpl.nasa.gov">greg.j.kazz@jpl.nasa.gov</a>></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">25/06/20 21:14</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: [EXTERNAL] [Sls-rfm] CCSDS RFM WG AI_20-01 (PN register convention)</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"> I have a very simple solution to the issue of PN generator diagrams and the associated polynomial. Do not state the polynomial
in CCSDS documents. </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"> In our CCSDS books we always show the generator diagram which is (unique) necessary and sufficient. </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">We can avoid the editing issue by not changing the existing books but going forward, let’s not publish the ambiguous polynomial. At least
one of our books shows the generator diagram and never states a polynomial (414.1-B).</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 generator shift register diagram (Fibonacci, Galois, Gold) produces a unique pattern and in a specific direction of flow. The polynomial
is ambiguous. For maximal patterns there are two polynomials that produce patterns with the same statistic but when represented as a bit pattern, the bit flow is in opposite directions. When doing abstract algebra, this may not matter. When used in communications,
it does matter. For example a communications de-randomizer must flow in the same direction at the randomizer. In the case where a pattern is truncated, using the same starting point, the statistics will be different depending on the flow direction. </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">Victor</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 <<a href="mailto:sls-rfm-bounces@mailman.ccsds.org">sls-rfm-bounces@mailman.ccsds.org</a>>
<b>On Behalf Of </b><a href="mailto:Enrico.Vassallo@esa.int">Enrico.Vassallo@esa.int</a><b><br>
Sent:</b> Monday, June 22, 2020 5:32 AM<b><br>
To:</b> <a href="mailto:sls-rfm@mailman.ccsds.org">sls-rfm@mailman.ccsds.org</a>; Border, James S (JPL-335D)[Jet Propulsion Laboratory] <<a href="mailto:james.s.border@jpl.nasa.gov">james.s.border@jpl.nasa.gov</a>><b><br>
Cc:</b> Kazz, Greg J (JPL-312B)[Jet Propulsion Laboratory] <<a href="mailto:greg.j.kazz@jpl.nasa.gov">greg.j.kazz@jpl.nasa.gov</a>><b><br>
Subject:</b> [EXTERNAL] [Sls-rfm] CCSDS RFM WG AI_20-01 (PN register convention)</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>
please find my response <b>as both ESA representative in RFM WG and as RFM WG chair</b> to the action item:</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
AI_20-01 Report about the PN register proposal in CS_20-03, the possible need to have a similar standard representation and, in case, the preferred way forward</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
Input paper CS_20-03 recommends changes to the following RFM WG books: </span><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
1) 415.1-B-1, dated 2011</span> <br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
2) 415.1-G-1, dated 2013</span> <br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
3) 401.1-B REC 2.5.7B-white</span> <br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
Document CS_20-03 proposes to adopt the Matlab convention. <br>
Main differences between what's in documents 1-3 and the proposal in CS_20-03 is the fact that in the pictures the output register is numbered N in 1-3 as opposed to 0 in the proposal; additionally, the first register is numbered 1 (zero is not used in 1-3).</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
Documents 1-2-3 are consistent. <br>
Document 2 (green book) provides in page 3-3 a detailed explanation of the convention used, addresses different conventions in literature, and links the drawing of the picture with resulting equations and polynomials. This info is in sections 3.4 to 3.8.</span>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
Document 1 (blue book) provides some explanation of the convention used in section 1.6.2.</span>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
Document 3 has two pictures in Annex A with no explanation while the polynomials are in the main body of the recommendation.
</span><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
Documents 1-2 were mainly NASA's (GFSC) inputs aimed at extending the SNIP agreement (latest version from 1998) between ESA, NASA and NASDA (now JAXA) for which the latest version dates November 1998 to encompass more CCSDS agencies.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
The change request in CS_20-03 would entail editing the following number of pictures: 5 (doc 1) + 10 (doc 2) + 2 doc (3) = 17 in addition to adjusting the related text.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
Given that documents 1 and 2 have been used for almost a decade with no report of implementation mistakes by ESA equipment developers, and the changes in CS_20-03 would result in full disagreement with the SNIP document, it is proposed NOT to adopt the Matlab
convention for the RFM WG books. However, concerning the draft DDOR recommendation 2.5.7B under development, some explanation could be added as done in 1 (or even in 2.)</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
It is possible that other WGs of the SLS area may prefer a different approach for their books but as long as the recommendations of the same WG are consistent, I do not see this as an issue.</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"">).</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>