<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=us-ascii">
<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:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
tt
{mso-style-priority:99;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle23
{mso-style-type:personal-reply;
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">Enrico,<o:p></o:p></p>
<p class="MsoNormal"> I did not understand you comment. I said “My question is general CCSDS standards. I would like to see a standard, MatLab, IEEE, or whatever.”<o:p></o:p></p>
<p class="MsoNormal">I am simply looking for a standard. I suggested IEEE and you seem to be criticizing that. I don’t understand.
<o:p></o:p></p>
<p class="MsoNormal">Victor<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b>From:</b> Enrico.Vassallo@esa.int <Enrico.Vassallo@esa.int>
<br>
<b>Sent:</b> Tuesday, June 1, 2021 9:38 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)[JPL Employee] <greg.j.kazz@jpl.nasa.gov>; Andrews, Kenneth S (JPL-332B)[JPL Employee] <kenneth.s.andrews@jpl.nasa.gov>; Rodriguez, Shannon (GSFC-5670) <shannon.rodriguez-1@nasa.gov>; Kazz, Greg J(US 312B) via SLS-SLP <sls-slp@mailman.ccsds.org>;
SLS-SLP <sls-slp-bounces@mailman.ccsds.org>; Fong, Wai H. (GSFC-5670) <wai.h.fong@nasa.gov>; Lee, Wing-tsz (GSFC-5670) <wing-tsz.lee-1@nasa.gov>; Gian.Paolo.Calzolari@esa.int<br>
<b>Subject:</b> [EXTERNAL] Re: [Sls-slp] Your LFSR OID frame RIDs affecting USLP, TM, AOS SDLPs<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Normally the two of us tend to disagree on PN and PN-like signals. I see you are trying to extend the disagreement to PN registers nomenclature !!!</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">I think I did not say anything but being a senior IEEE member I would not accept non-IEEE terminology....</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">In any case, Greg made a nice proposal, I would subscribe too.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">No more on this from me,</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">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\] via SLS-SLP" <<a href="mailto:sls-slp@mailman.ccsds.org">sls-slp@mailman.ccsds.org</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">"Andrews, Kenneth S (JPL-332B)[JPL Employee]" <<a href="mailto:kenneth.s.andrews@jpl.nasa.gov">kenneth.s.andrews@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\)\[JPL Employee\]" <<a href="mailto:greg.j.kazz@jpl.nasa.gov">greg.j.kazz@jpl.nasa.gov</a>>,
"Kazz, Greg J\(US 312B\) via SLS-SLP" <<a href="mailto:sls-slp@mailman.ccsds.org">sls-slp@mailman.ccsds.org</a>>, "Fong, Wai H.\(GSFC-5670\)" <<a href="mailto:wai.h.fong@nasa.gov">wai.h.fong@nasa.gov</a>>, "Rodriguez, Shannon\(GSFC-5670\)" <<a href="mailto:shannon.rodriguez-1@nasa.gov">shannon.rodriguez-1@nasa.gov</a>>,
"Lee, Wing-tsz\(GSFC-5670\)" <<a href="mailto:wing-tsz.lee-1@nasa.gov">wing-tsz.lee-1@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">01/06/21 04:11</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-slp] Your LFSR OID frame RIDs affecting USLP, TM, AOS SDLPs</span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Sent by: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"SLS-SLP" <<a href="mailto:sls-slp-bounces@mailman.ccsds.org">sls-slp-bounces@mailman.ccsds.org</a>></span>
<o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" 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">Ken,<o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"> Did you have any comment about the use of Fibonacci vs Galois for maximal pattern randomizers? If so I think I missed it. As I remember Greg asked you to explain the difference in the seeds for the
two representations and said that both representations would be shown in his book. <o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt">My question is general CCSDS standards. I would like to see a standard, MatLab, IEEE, or whatever. For coding like BCH, that uses a polynomial that is not irreducible (only 4 terms and it is “reducible”, g(x) =
x^7+x^6 + x^2 + 1 can be factored into (x + 1)(x^6 + x + 1)), I do not know if a Fibonacci equivalent can generate the parity. Can it? If it can, then for the following reason, I suggest that for any future CCSDS book, we use Fibonacci for all shift registers
diagrams.<o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt">A maximal pattern register diagram can be either in the Fibonacci or Galois type representation, as you have submitted for the long randomizer. I am recommending Fibonacci be used in CCSDS books at least where maximal
and Gold codes are covered, since the output pattern is easily seen based on the register contents. Since CCSDS does not recommend implementation, the user is free to use Galois for implementation if that is their preference. It would be nice if we can
help the understanding of engineers in the field that are not PhDs. The fact that you were asked to explain why the seeds for the Fibonacci and Galois are different is telling.
<o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"> I do not agree with the comment made by Enrico? or was it GP?, that since the BCH or other code in the book used a Galois type format, that the maximal or Gold code representation used should therefore
be in Galois format. <o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"> I would love to hear your comments. (and can the BCH be shown in a Fibonacci format?) <o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt">Thanks,<o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt">Victor <o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"> <o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><b>From:</b> Sank, Victor J. (GSFC-567.0)[SCIENCE SYSTEMS AND APPLICATIONS INC]
<b><br>
Sent:</b> Monday, May 17, 2021 1:16 PM<b><br>
To:</b> Andrews, Kenneth S (JPL-332B)[JPL Employee] <<a href="mailto:kenneth.s.andrews@jpl.nasa.gov">kenneth.s.andrews@jpl.nasa.gov</a>><b><br>
Cc:</b> Kazz, Greg J (US 312B) via SLS-SLP <<a href="mailto:sls-slp@mailman.ccsds.org">sls-slp@mailman.ccsds.org</a>>; Kazz, Greg J (US 312B) <<a href="mailto:greg.j.kazz@jpl.nasa.gov">greg.j.kazz@jpl.nasa.gov</a>><b><br>
Subject:</b> RE: Your LFSR OID frame RIDs affecting USLP, TM, AOS SDLPs<o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt">Ken,<o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"> Maximal pattern shift registers. LFSR<o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"> CCSDS is not supposed to make recommendations about implementation. For implementing I understand that the Galois shift register is sometimes preferred over the Fibonacci form. However, for understanding
and for setting an initial seed, Fibonacci has tremendous advantage because WYSIWYG, if you remember that phrase from the early Apple computers, what you see is what you get.<o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"> You might also remember that we had a recent go-around in the code and synch WG about how to show these shift registers and we (GSFC) were recommending Fibonacci with particular labeling of the cells
so that the polynomial is directly related to the cells that are tapped. Yes, I realize that this can also be done for the Galois form. Another value of the Fibonacci with the particular cell numbering is that it is what MatLab uses. So when people are
doing simulations, no conversion is needed. <o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"> As you might remember there is an ambiguity between the associated polynomial and the shift register labeling. A particular pattern can be generated in one direction or the reverse. We had a particular
proposal and it turned out that MatLab used the same convention. Our proposal was discarded since it would be too much editing to get all the books to follow the same convention, and maybe other reasons. <o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"> But in any case, seems better from an understanding point of view to use Fibonacci. <o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"> <o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt">Victor<o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"> <o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><b>From:</b> Kazz, Greg J (US 312B) <<a href="mailto:greg.j.kazz@jpl.nasa.gov"><span style="color:#0082BF">greg.j.kazz@jpl.nasa.gov</span></a>>
<b><br>
Sent:</b> Monday, May 17, 2021 12:31 PM<b><br>
To:</b> Andrews, Kenneth S (JPL-332B)[JPL Employee] <<a href="mailto:kenneth.s.andrews@jpl.nasa.gov"><span style="color:#0082BF">kenneth.s.andrews@jpl.nasa.gov</span></a>><b><br>
Cc:</b> Sank, Victor J. (GSFC-567.0)[SCIENCE SYSTEMS AND APPLICATIONS INC] <<a href="mailto:victor.j.sank@nasa.gov"><span style="color:#0082BF">victor.j.sank@nasa.gov</span></a>>; Kazz, Greg J (US 312B) via SLS-SLP <<a href="mailto:sls-slp@mailman.ccsds.org"><span style="color:#0082BF">sls-slp@mailman.ccsds.org</span></a>><b><br>
Subject:</b> Your LFSR OID frame RIDs affecting USLP, TM, AOS SDLPs<o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:12.0pt">Hi Ken,</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:12.0pt">The SLP WG decided to put both of your diagrams into a new non-normative annex in USLP, TM, and AOS.</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:12.0pt">The text in the normative part of the link layer books will state:</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">The TFDZ of an OID Transfer Frame shall be generated by use of a 32-cell Linear Feedback Shift Register (LFSR) with polynomial 1 + D + D<sup>2</sup> + D<sup>22</sup> +D<sup>32</sup></span><span style="font-size:12.0pt;font-family:"Courier New"">,
see Annex X.</span> <o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:12.0pt">Where Annex X is TBD and will be added by me to the document.</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:12.0pt">We have some questions and requests for you:</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">1. Why does the initialization data differ from one figure to the other one?</span><span style="font-size:14.0pt">
</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">2. </span><span style="font-size:12.0pt">The ‘1’ in the figures are misleading to some WG members, please replace ‘1’ with D sub zero i.e., D<sup>0</sup>
in the figures.</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">3. </span><span style="font-size:12.0pt">Consensus of WG was to specify the initialization vector
</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:12.0pt">Thanks!</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:12.0pt">Greg</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt">Greg Kazz<o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt">Principal Engineer<o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt">Technical Group Supervisor,<o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt">PSSE/EEISE/PPSE (312B)<o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt">Jet Propulsion Laboratory<o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt">4800 Oak Grove Dr., M/S 301-490<o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt">Pasadena, CA 91109<o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt">1+(818)393 6529(voice)<o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt">1+(818)393 6871(fax)<o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt">email: <a href="mailto:greg.j.kazz@jpl.nasa.gov">
<span style="color:#0082BF">greg.j.kazz@jpl.nasa.gov</span></a> <o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
<tt><span style="font-size:10.0pt">_______________________________________________</span></tt><span style="font-size:10.0pt;font-family:"Courier New""><br>
<tt>SLS-SLP mailing list</tt><br>
<tt><a href="mailto:SLS-SLP@mailman.ccsds.org">SLS-SLP@mailman.ccsds.org</a></tt><br>
</span><a href="https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailman.ccsds.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fsls-slp&data=04%7C01%7Cvictor.j.sank%40nasa.gov%7Ccdbc9a2fb41f41e2f5a408d925027dd0%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C637581514904341896%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Yl9CO2uufNpQBjYE4Mr1lZTmP15Nl8fz2fUGZM2OiPQ%3D&reserved=0"><tt><span style="font-size:10.0pt">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sls-slp</span></tt></a><span style="font-size:10.0pt;font-family:"Courier New""><br>
<br>
</span><o:p></o:p></p>
</div>
<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>