<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)">
<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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:12.0pt;
font-family:"Calibri",sans-serif;
mso-ligatures:standardcontextual;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
font-size:12.0pt;
font-family:"Calibri",sans-serif;
mso-ligatures:standardcontextual;}
span.EmailStyle21
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1064913848;
mso-list-type:hybrid;
mso-list-template-ids:-1925021020 67698705 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt"> The Set V(R) is a function of COP-P, which seems out-of-place to me. Do we need that? Isn’t this only used for resyncing. If we get out of sync, doesn’t everything reset naturally?
<o:p></o:p></span></p>
<p class="MsoListParagraph"><span style="font-size:11.0pt">Similarly, I think PLCW requests are not really needed. Is that true? I think it is best to minimize COP-P influence.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;mso-ligatures:none">From:</span></b><span style="font-size:11.0pt;mso-ligatures:none"> Kazz, Greg (US 312B) <greg.j.kazz@jpl.nasa.gov>
<br>
<b>Sent:</b> Thursday, May 11, 2023 2:30 PM<br>
<b>To:</b> Stuart Golden <sgolden@vulcanwireless.com>; Kazz, Greg (US 312B) via SLS-SLP <sls-slp@mailman.ccsds.org>; Sank, Victor J. (GSFC-567.0)[SCIENCE SYSTEMS AND APPLICATIONS INC] <victor.j.sank@nasa.gov><br>
<b>Subject:</b> Revision of Composite Directive for Lunar<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Dear SLP WG,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Attached is a revision of the Lunar Prox-1 directive (SPDU).
<o:p></o:p></p>
<p class="MsoNormal">It differs from the one I presented at the meeting, because in the joint RF&MOD/C&S/SLP WG meeting, it was decided that all of the Type 1 SPDU directives would only be used at UHF band and NOT apply to Lunar. However, there are some parameters
such as duplex, RNMD, SET V(R), etc that are required by the protocol which are not currently defined in the draft SPDU Type 3 (Lunar SPDU). Ergo, I added them, which only leave 1 spare bit. I ended up reducing the MODCOD field from 21 bits to 13 bits, which
I still feel is adequate. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Part of the problem here is that some of these fields won’t be used as frequently as some of the other parameters but overall I don’t think it will be an efficiency killer.<o:p></o:p></p>
<p class="MsoNormal"><o:p></o:p></p>
<p class="MsoNormal">Please review this latest version, and really take a close look to see if the number of bits assigned to each field is adequate or too much.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks much,<o:p></o:p></p>
<p class="MsoNormal">Greg<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;mso-ligatures:none">Greg Kazz<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;mso-ligatures:none">Principal Engineer<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;mso-ligatures:none">Technical Group Supervisor,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;mso-ligatures:none">312B Project Protection, Project Software, and End to End Information System Engineering<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;mso-ligatures:none">Jet Propulsion Laboratory<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;mso-ligatures:none">4800 Oak Grove Dr., M/S 301-490<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="ES-MX" style="font-size:11.0pt;mso-ligatures:none">Pasadena, CA 91109</span><span style="font-size:11.0pt;mso-ligatures:none"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="ES-MX" style="font-size:11.0pt;mso-ligatures:none">1+(818)393 6529(voice)</span><span style="font-size:11.0pt;mso-ligatures:none"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;mso-ligatures:none">1</span><span lang="ES-MX" style="font-size:11.0pt;mso-ligatures:none">+(818)393 6871(fax)</span><span style="font-size:11.0pt;mso-ligatures:none"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="ES-MX" style="font-size:11.0pt;mso-ligatures:none">email:
<a href="mailto:greg.j.kazz@jpl.nasa.gov">greg.j.kazz@jpl.nasa.gov</a> </span><span style="font-size:11.0pt;mso-ligatures:none"><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>