<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); "><div style="font-family: Calibri, sans-serif; font-size: 20px; ">Enrico,</div><div style="font-family: Calibri, sans-serif; font-size: 20px; "><br></div><div style="font-family: Calibri, sans-serif; font-size: 20px; ">I intended to send it sooner, but got sick with the Flu from which I am still recovering. During this time the USA celebrated our Thanksgiving Day Holidays. (Nov 24-27)</div><div style="font-family: Calibri, sans-serif; font-size: 20px; ">Regarding extending the deadline from Dec 1 to Dec 8, I would gladly do so, but it is not my call. If the SLS-AD is OK with this then I will hold off from sending my update of the DLL book until then. If I do not hear from him before Dec 1, then I will still send it in to Tom Gannett to meet my action item as requested of me.</div><div style="font-family: Calibri, sans-serif; font-size: 20px; "><br></div><div style="font-family: Calibri, sans-serif; font-size: 20px; ">Regarding your other comments thank you for them.</div><div style="font-family: Calibri, sans-serif; font-size: 20px; ">The updated version is now on the CWE with the date of Nov29 in the filenames.</div><div style="font-family: Calibri, sans-serif; font-size: 20px; "><br></div><div style="font-family: Calibri, sans-serif; font-size: 20px; "><span class="Apple-style-span" style="font-family: sans-serif; font-size: small; ">1) Data rate tables OK now corrected in all three places.</span></div><div style="font-family: Calibri, sans-serif; font-size: 20px; "><span class="Apple-style-span" style="font-family: sans-serif; font-size: small; ">2) Data rate pictures (figure 1.2) - OK I had problems with placing the new picture from G.P. That is why I put in the comment. However, using your word copy of the PL book, I was able to insert it this time.</span></div><div style="font-family: Calibri, sans-serif; font-size: 20px; "><span class="Apple-style-span" style="font-family: sans-serif; font-size: small; ">3) MRO Annex</span></div><div style="font-family: Calibri, sans-serif; font-size: 20px; "><span class="Apple-style-span" style="font-family: sans-serif; font-size: small; "><br></span></div><div><font class="Apple-style-span" face="sans-serif" size="2">This text came from the Electra team and reviewed by the Mars Program Chief Telecom Engineer. Apparently they think it is good enough for an informative annex. They delivered the implemention to MRO. However I have made the following changes:</font></div><div><font class="Apple-style-span" face="sans-serif" size="2"><br></font></div><div><font class="Apple-style-span" face="sans-serif" size="2">I) </font><span class="Apple-style-span" style="font-size: 20px; font-family: Calibri, sans-serif; "><font size="2" face="sans-serif">"The Electra radio supports two standard symbol encodings" to read "</font></span><span class="Apple-style-span" style="font-size: 20px; font-family: Calibri, sans-serif; "><font size="3" face="Times New Roman">The Electra radio supports two standard symbol modulations".</font></span></div><div><span class="Apple-style-span" style="font-size: 20px; font-family: Calibri, sans-serif; "><font size="3" face="Times New Roman"><br></font></span></div><div><span class="Apple-style-span" style="font-size: 20px; font-family: Calibri, sans-serif; "><font size="3" face="Times New Roman">II) I moved the following text right up to the front of Annex E because it should be emphasized in the beginning and as you say not burried in the text. I used your formulation:</font></span></div><div><span class="Apple-style-span" style="font-size: 20px; font-family: Calibri, sans-serif; "><font size="3" face="Times New Roman"><br></font></span></div><div><span class="Apple-style-span" style="font-size: 20px; font-family: Calibri, sans-serif; "><font size="3" face="Times New Roman">Note: </font></span><span class="Apple-style-span" style="font-family: sans-serif; font-size: small; ">for symbol rate above 512 ksps, projects interoperating with MRO should consider using NRZ-L instead of bi-phase-L unless the performance achievable with bi-phase-L is sufficient for the mission concerned.</span></div><div><span class="Apple-style-span" style="font-family: sans-serif; font-size: small; "><br></span></div><div><span class="Apple-style-span" style="font-family: sans-serif; font-size: small; ">III) For </span><span class="Apple-style-span" style="font-family: 'Times New Roman'; ">A1.7.8 </span><span class="Apple-style-span" style="font-family: 'Times New Roman'; "><b>Carrier Modulation</b></span></div><div><span class="Apple-style-span" style="font-family: 'Times New Roman'; "><b><br></b></span></div><div><span class="Apple-style-span" style="font-family: 'Times New Roman'; "><b>I now have put: </b></span><span class="Apple-style-span" style="font-family: 'Times New Roman'; ">Options c) and d) are not required for cross-support</span></div><div><span class="Apple-style-span" style="font-family: 'Times New Roman'; "><br></span></div><div><span class="Apple-style-span" style="font-family: 'Times New Roman'; ">(We should all keep in mind however that the Electra Radio is software programmable, so changes can be made in flight when required I did not add this parenthetical it is just for your information)</span></div><div><font class="Apple-style-span" face="Times New Roman"><br></font></div><div><font class="Apple-style-span" face="Times New Roman">However for </font><span class="Apple-style-span" style="font-size: 20px; font-family: Calibri, sans-serif; "><font size="2" face="sans-serif">A1.7.6 </font></span><span class="Apple-style-span" style="font-size: 20px; font-family: Calibri, sans-serif; "><font size="3" face="Times New Roman"><b>Carrier Mode Select I made no changes, since Electra does indeed support Supressed Carrier Mode while using BPSK (and other agencies e.g., British Space Agency plan on implementing it in their transceiver for Mars for interoperability with MRO). </b></font></span></div><div><font class="Apple-style-span" face="Times New Roman"><b><br></b></font></div><div><span class="Apple-style-span" style="font-size: 20px; font-family: Calibri, sans-serif; "><font size="3" face="Times New Roman"><b><br></b></font></span></div><div><span class="Apple-style-span" style="font-size: 20px; font-family: Calibri, sans-serif; "><font size="3" face="Times New Roman"><b>Best regards,</b></font></span></div><div><span class="Apple-style-span" style="font-size: 20px; font-family: Calibri, sans-serif; "><font size="3" face="Times New Roman"><b><br></b></font></span></div><div><span class="Apple-style-span" style="font-size: 20px; font-family: Calibri, sans-serif; "><font size="3" face="Times New Roman"><b>Greg</b></font></span></div><div><font class="Apple-style-span" face="sans-serif" size="2"><br></font></div><span id="OLK_SRC_BODY_SECTION" style="font-size: 20px; font-family: Calibri, sans-serif; "><div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt"><span style="font-weight:bold">From: </span> "<a href="mailto:Enrico.Vassallo@esa.int">Enrico.Vassallo@esa.int</a>" <<a href="mailto:Enrico.Vassallo@esa.int">Enrico.Vassallo@esa.int</a>><br><span style="font-weight:bold">Date: </span> Tue, 29 Nov 2011 05:56:49 -0800<br><span style="font-weight:bold">To: </span> "Kazz, Greg J (313B)" <<a href="mailto:greg.j.kazz@jpl.nasa.gov">greg.j.kazz@jpl.nasa.gov</a>><br><span style="font-weight:bold">Cc: </span> "<a href="mailto:Gian.Paolo.Calzolari@esa.int">Gian.Paolo.Calzolari@esa.int</a>" <<a href="mailto:Gian.Paolo.Calzolari@esa.int">Gian.Paolo.Calzolari@esa.int</a>>, "<a href="mailto:Massimo.Bertinelli@esa.int">Massimo.Bertinelli@esa.int</a>" <<a href="mailto:Massimo.Bertinelli@esa.int">Massimo.Bertinelli@esa.int</a>>, Cosby Matthew <<a href="mailto:MCOSBY@qinetiq.com">MCOSBY@qinetiq.com</a>>, "<a href="mailto:sls-slp-bounces@mailman.ccsds.org">sls-slp-bounces@mailman.ccsds.org</a>" <<a href="mailto:sls-slp-bounces@mailman.ccsds.org">sls-slp-bounces@mailman.ccsds.org</a>>, "Lee, Dennis K (332C)" <<a href="mailto:dennis.k.lee@jpl.nasa.gov">dennis.k.lee@jpl.nasa.gov</a>><br><span style="font-weight:bold">Subject: </span> Re: Updated Prox-1 DLL book ready for your review<br></div><div><br></div><font size="2" face="sans-serif">Greg,</font><br><br><font size="2" face="sans-serif">you do not give us much chance
for a in-depth review. One day is not so much especially since we are not
working on CCSDS at 100% of our time.</font><br><br><font size="2" face="sans-serif">Here's a list of things I spotted in
a rush. I could not talk to Gian Paolo and therefore he may have more questions.
We may be forced to come back during Agency Review if we missed other points.</font><br><font size="2" face="sans-serif">Can you not extend the deadline for
our comments by a week? The document is dated 21 Nov but we only got it
today! </font><br><br><font size="2" face="sans-serif">1) Data rate tables</font><br><br><font size="2" face="sans-serif">In section "A.1.2.3.5.4 Proximity-1
Coded Symbol (Rcs) and Data Rate (Rd) Table", the column for uncoded
data rates Rd is obviously wrong since </font><font size="3" face="Times New Roman">Rd
= .5 * Rcs should read instead Rd = Rcs and all the numbers doubled</font><font size="2" face="sans-serif">.</font><br><br><font size="2" face="sans-serif">Same story for </font><font size="3" face="Times New Roman">A.1.4.6.4
</font><font size="2" face="sans-serif">and A.1.7.9</font><br><br><font size="2" face="sans-serif">2) Data rate pictures (figure 1.2)</font><br><br><font size="2" face="sans-serif">Additionally, for the data rate figure
instead of asking the editor to change the text, you could just replace
it with the one in the PL that is already as per Exomars comments.</font><br><br><font size="2" face="sans-serif">3) MRO Annex</font><br><br><font size="2" face="sans-serif">In the Annex for MRO, I think that at
least you should change "The Electra radio supports two standard symbol
encodings" to read "</font><font size="3" face="Times New Roman">The
Electra radio supports two standard symbol modulations".</font><br><br><font size="2" face="sans-serif">The Annex is marked informative and
it is mostly text from Wikipedia and text books not 100% in synch with
CCSDS. Sometimes, you talk about waveforms for NRZ and bi-phase, some timesabout modulations, etc. I think you should be consistent. I do not think
we should put Wikipedia text and drawings in a CCSDS document. Can you
not ask the diligent Dennis to provide you with a clean and reasonable
text for this Annex?</font><br><br><font size="2" face="sans-serif">Additionally, in the middle of this
divulgative text (and informative annex) you entered an almost mandatory
clause:</font><div><p><font size="3" face="Times New Roman Bold"><b>For maximum performance
with the NASA MRO Electra implementation, it is recommended that NRZ-L
encoded waveforms be utilized instead of bi-phase-L (Manchester) waveforms
for cross-support with the NASA MRO Electra for Proximity-1 symbol rates
above 512 ksps. </b></font><br><br><font size="2" face="sans-serif">Can you not say what I had proposed:
for symbol rate above 512 ksps, projects interoperating with MRO should
consider using NRZ-L instead of bi-phase-L unless the performance achievable
with bi-phase-L is sufficient for the mission concerned.</font><br><br><font size="2" face="sans-serif">The Annex E also has the following text:</font></p><div><p><font size="3" face="Times New Roman"><b>FSK Modulation:</b></font></p><p><font size="3" face="Times New Roman">FSK modulation is currently not
implemented on the NASA MRO Electra transceiver.</font></p><p><font size="3" face="Times New Roman"><b>QPSK Modulation:</b></font></p><p><font size="3" face="Times New Roman">QPSK modulation is currently not
implemented on the NASA MRO Electra transceiver.</font><br><br><br><font size="2" face="sans-serif">However, in A.1.7.8 you state that FSK
and OQPSK are needed to interoperate with MRO:</font></p><p><font size="3" face="Times New Roman">A1.7.8 <b>Carrier
Modulation</b></font></p><div><p><font size="3" face="Times New Roman">Bits 3-4 of the </font><font size="2" face="Times New Roman"><b>SET
PL EXTENSIONS </b></font><font size="3" face="Times New Roman">directive
shall indicate the type of carrier modulation to be used:</font><br><font size="3" face="Times New Roman">a) 00
= No Modulation;</font><br><font size="3" face="Times New Roman">b) 01
= PSK;</font><br><font size="3" face="Times New Roman">c) 10
= FSK;</font><br><font size="3" face="Times New Roman">d) 11
= QPSK.</font></p><div><p><font size="3" face="Times New Roman">Options c) and d) are not required
for cross-support except for those missions required to interoperate with
NASA MRO. See Annex E. </font><br><br><font size="2" face="sans-serif">Clearly this statement is incorrect.
My proposed solution: in A1.7.8 you remove the text after cross support.</font><br><br><font size="2" face="sans-serif">The same goes with A1.7.6 </font><font size="3" face="Times New Roman"><b>Carrier
Mode Select</b></font></p><div><p><font size="3" face="Times New Roman">Bits 7-8 of the </font><font size="2" face="Times New Roman"><b>SET
PL EXTENSIONS </b></font><font size="3" face="Times New Roman">directive
shall indicate the type of carrier suppression used:</font><br><font size="3" face="Times New Roman">a) 00
= Suppressed Carrier (Requires transmit side utilize Modulation Index of
90°and transmit/receive sides utilize Differential Mark Encoding/Decoding);</font><br><font size="3" face="Times New Roman">b) 01
= Residual Carrier;</font><br><font size="3" face="Times New Roman">c) 10
= Reserved;</font><br><font size="3" face="Times New Roman">d) 11
= Reserved.</font></p><div><p><font size="3" face="Times New Roman">Option a) is not required for cross-support
except for those missions required to interoperate with NASA MRO. See AnnexE. </font></p><p><br><font size="2" face="sans-serif">My proposed solution: in A1.7.6 you
remove the text after cross support.</font><br><br><font size="2" face="sans-serif">Cheers, Enrico</font><br><br><br><table width="100%"><tbody><tr valign="top"><td><font size="1" color="#5f5f5f" face="sans-serif">From:</font></td><td><font size="1" face="sans-serif">"Kazz, Greg J (313B)" <<a href="mailto:greg.j.kazz@jpl.nasa.gov">greg.j.kazz@jpl.nasa.gov</a>></font></td></tr><tr valign="top"><td><font size="1" color="#5f5f5f" face="sans-serif">To:</font></td><td><font size="1" face="sans-serif">"<a href="mailto:Gian.Paolo.Calzolari@esa.int">Gian.Paolo.Calzolari@esa.int</a>"
<<a href="mailto:Gian.Paolo.Calzolari@esa.int">Gian.Paolo.Calzolari@esa.int</a>>, "<a href="mailto:Massimo.Bertinelli@esa.int">Massimo.Bertinelli@esa.int</a>"
<<a href="mailto:Massimo.Bertinelli@esa.int">Massimo.Bertinelli@esa.int</a>>, "<a href="mailto:Enrico.Vassallo@esa.int">Enrico.Vassallo@esa.int</a>"
<<a href="mailto:Enrico.Vassallo@esa.int">Enrico.Vassallo@esa.int</a>>, Cosby Matthew <<a href="mailto:MCOSBY@qinetiq.com">MCOSBY@qinetiq.com</a>></font></td></tr><tr><td valign="top"><font size="1" color="#5f5f5f" face="sans-serif">Cc:</font></td><td><font size="1" face="sans-serif">"<a href="mailto:sls-slp-bounces@mailman.ccsds.org">sls-slp-bounces@mailman.ccsds.org</a>"
<<a href="mailto:sls-slp-bounces@mailman.ccsds.org">sls-slp-bounces@mailman.ccsds.org</a>></font></td></tr><tr valign="top"><td><font size="1" color="#5f5f5f" face="sans-serif">Date:</font></td><td><font size="1" face="sans-serif">28/11/2011 18:53</font></td></tr><tr valign="top"><td><font size="1" color="#5f5f5f" face="sans-serif">Subject:</font></td><td><font size="1" face="sans-serif">Updated Prox-1 DLL book ready for your
review</font></td></tr></tbody></table><br></p><hr noshade=""><br><br><br><font size="4" face="Calibri">All,</font><br><br><font size="4" face="Calibri">Please go to the following URL to download
the updated version (based upon the discussions held in Boulder and on
a few follow on discussions conducted over email) of the Proximity-1 Space
Data Link Layer blue book. </font><br><br><a href="http://tinyurl.com/3n9qx9r"><font size="4" color="blue" face="Calibri"><b><u>http://tinyurl.com/3n9qx9r</u></b></font></a><br><br><font size="4" face="Calibri"><b>There are two new word files there and
both contain the date Nov 21 embedded in the filename. One is a clean copy
with out redlines. The other has the redlines.</b></font><br><br><font size="4" face="Calibri">Please let me know before Nov 30, if I
have addressed your concerns adequately or if you have any further comment.I believe I have done so. On Dec 1, I will send this document on to Tom
Gannett, who has already been briefed about its arrival. </font><br><br><font size="4" face="Calibri">Thanks again for making this book consistent
with the other books.</font><br><br><font size="4" face="Calibri">Best regards,</font><br><br><font size="4" face="Calibri">Greg Kazz</font><br><font size="4" face="Calibri">Chairman SLS-SLP WG</font><br><br></div></div></div></div></div></div></span></body></html>