<font size=2 face="sans-serif">Greg,</font>
<br>
<br><font size=2 face="sans-serif">sorry to hear about that. Hope you are
now doing fine.</font>
<br>
<br><font size=2 face="sans-serif">I can live with your counter-proposals
although at least the one on BPSK would look weird. You may get RIDs from
others during Agency Review.</font>
<br>
<br><font size=2 face="sans-serif">As far as the deadline is concerned,
I leave it to Gian Paolo to decide: indeed it may take longer to ship the
document out; however, you may get fewer RIDs and therefore a faster publication.</font>
<br>
<br><font size=2 face="sans-serif">Regards, Enrico</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">From:</font>
<td><font size=1 face="sans-serif">"Kazz, Greg J (313B)" <greg.j.kazz@jpl.nasa.gov></font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">To:</font>
<td><font size=1 face="sans-serif">"Enrico.Vassallo@esa.int"
<Enrico.Vassallo@esa.int>, "Gian.Paolo.Calzolari@esa.int"
<Gian.Paolo.Calzolari@esa.int></font>
<tr>
<td valign=top><font size=1 color=#5f5f5f face="sans-serif">Cc:</font>
<td><font size=1 face="sans-serif">"Massimo.Bertinelli@esa.int"
<Massimo.Bertinelli@esa.int>, Cosby Matthew <MCOSBY@qinetiq.com>,
"sls-slp@mailman.ccsds.org" <sls-slp@mailman.ccsds.org>,
"Lee, Dennis K (332C)" <dennis.k.lee@jpl.nasa.gov></font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Date:</font>
<td><font size=1 face="sans-serif">30/11/2011 00:16</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Subject:</font>
<td><font size=1 face="sans-serif">Re: Updated Prox-1 DLL book ready for
your review</font></table>
<br>
<hr noshade>
<br>
<br>
<br><font size=4 face="Calibri">Enrico,</font>
<br>
<br><font size=4 face="Calibri">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)</font>
<br><font size=4 face="Calibri">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.</font>
<br>
<br><font size=4 face="Calibri">Regarding your other comments – thank
you for them.</font>
<br><font size=4 face="Calibri">The updated version is now on the CWE with
the date of Nov29 in the filenames.</font>
<br>
<br><font size=2 face="Calibri">1) Data rate tables – OK – now corrected
in all three places.</font>
<br><font size=2 face="Calibri">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.</font>
<br><font size=2 face="Calibri">3) MRO Annex</font>
<br>
<br><font size=2 face="sans-serif">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>
<br>
<br><font size=2 face="sans-serif">I) "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=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>
<br>
<br><font size=3 face="Times New Roman">Note: </font><font size=2>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>III) For </font><font size=3 face="Times New Roman">A1.7.8
<b>Carrier Modulation</b></font>
<br>
<br><font size=3 face="Times New Roman"><b>I now have put: </b>Options
c) and d) are not required for cross-support</font>
<br>
<br><font size=3 face="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)</font>
<br>
<br><font size=3 face="Times New Roman">However for </font><font size=2 face="sans-serif">A1.7.6
</font><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>
<br>
<br>
<br><font size=3 face="Times New Roman"><b>Best regards,</b></font>
<br>
<br><font size=3 face="Times New Roman"><b>Greg</b></font>
<br>
<br><font size=2 face="Calibri"><b>From: </b>"</font><a href=mailto:Enrico.Vassallo@esa.int><font size=2 color=blue face="Calibri"><u>Enrico.Vassallo@esa.int</u></font></a><font size=2 face="Calibri">"
<</font><a href=mailto:Enrico.Vassallo@esa.int><font size=2 color=blue face="Calibri"><u>Enrico.Vassallo@esa.int</u></font></a><font size=2 face="Calibri">><b><br>
Date: </b>Tue, 29 Nov 2011 05:56:49 -0800<b><br>
To: </b>"Kazz, Greg J (313B)" <</font><a href=mailto:greg.j.kazz@jpl.nasa.gov><font size=2 color=blue face="Calibri"><u>greg.j.kazz@jpl.nasa.gov</u></font></a><font size=2 face="Calibri">><b><br>
Cc: </b>"</font><a href=mailto:Gian.Paolo.Calzolari@esa.int><font size=2 color=blue face="Calibri"><u>Gian.Paolo.Calzolari@esa.int</u></font></a><font size=2 face="Calibri">"
<</font><a href=mailto:Gian.Paolo.Calzolari@esa.int><font size=2 color=blue face="Calibri"><u>Gian.Paolo.Calzolari@esa.int</u></font></a><font size=2 face="Calibri">>,
"</font><a href=mailto:Massimo.Bertinelli@esa.int><font size=2 color=blue face="Calibri"><u>Massimo.Bertinelli@esa.int</u></font></a><font size=2 face="Calibri">"
<</font><a href=mailto:Massimo.Bertinelli@esa.int><font size=2 color=blue face="Calibri"><u>Massimo.Bertinelli@esa.int</u></font></a><font size=2 face="Calibri">>,
Cosby Matthew <</font><a href=mailto:MCOSBY@qinetiq.com><font size=2 color=blue face="Calibri"><u>MCOSBY@qinetiq.com</u></font></a><font size=2 face="Calibri">>,
"</font><a href="mailto:sls-slp-bounces@mailman.ccsds.org"><font size=2 color=blue face="Calibri"><u>sls-slp-bounces@mailman.ccsds.org</u></font></a><font size=2 face="Calibri">"
<</font><a href="mailto:sls-slp-bounces@mailman.ccsds.org"><font size=2 color=blue face="Calibri"><u>sls-slp-bounces@mailman.ccsds.org</u></font></a><font size=2 face="Calibri">>,
"Lee, Dennis K (332C)" <</font><a href=mailto:dennis.k.lee@jpl.nasa.gov><font size=2 color=blue face="Calibri"><u>dennis.k.lee@jpl.nasa.gov</u></font></a><font size=2 face="Calibri">><b><br>
Subject: </b>Re: Updated Prox-1 DLL book ready for your review</font>
<br>
<br><font size=2 face="sans-serif">Greg,</font><font size=4 face="Calibri"><br>
</font><font size=2 face="sans-serif"><br>
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><font size=4 face="Calibri"><br>
</font><font size=2 face="sans-serif"><br>
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.<br>
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><font size=4 face="Calibri"><br>
</font><font size=2 face="sans-serif"><br>
1) Data rate tables</font><font size=4 face="Calibri"><br>
</font><font size=2 face="sans-serif"><br>
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><font size=4 face="Calibri"><br>
</font><font size=2 face="sans-serif"><br>
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><font size=4 face="Calibri"><br>
</font><font size=2 face="sans-serif"><br>
2) Data rate pictures (figure 1.2)</font><font size=4 face="Calibri"><br>
</font><font size=2 face="sans-serif"><br>
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><font size=4 face="Calibri"><br>
</font><font size=2 face="sans-serif"><br>
3) MRO Annex</font><font size=4 face="Calibri"><br>
</font><font size=2 face="sans-serif"><br>
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><font size=4 face="Calibri"><br>
</font><font size=2 face="sans-serif"><br>
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><font size=4 face="Calibri"><br>
</font><font size=2 face="sans-serif"><br>
Additionally, in the middle of this divulgative text (and informative annex)
you entered an almost mandatory clause:</font>
<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><font size=4 face="Calibri"><br>
</font><font size=2 face="sans-serif"><br>
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><font size=4 face="Calibri"><br>
</font><font size=2 face="sans-serif"><br>
The Annex E also has the following text:</font>
<p><font size=3 face="Times New Roman"><b>FSK Modulation:</b></font>
<p><font size=3 face="Times New Roman">FSK modulation is currently not
implemented on the NASA MRO Electra transceiver.</font>
<p><font size=3 face="Times New Roman"><b>QPSK Modulation:</b></font>
<p><font size=3 face="Times New Roman">QPSK modulation is currently not
implemented on the NASA MRO Electra transceiver.</font><font size=4 face="Calibri"><br>
<br>
</font><font size=2 face="sans-serif"><br>
However, in A.1.7.8 you state that FSK and OQPSK are needed to interoperate
with MRO:</font>
<p><font size=3 face="Times New Roman">A1.7.8 <b>Carrier
Modulation</b></font>
<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:<br>
a) ‘00’ = No Modulation;<br>
b) ‘01’ = PSK;<br>
c) ‘10’ = FSK;<br>
d) ‘11’ = QPSK.</font>
<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><font size=4 face="Calibri"><br>
</font><font size=2 face="sans-serif"><br>
Clearly this statement is incorrect. My proposed solution: in A1.7.8 you
remove the text after cross support.</font><font size=4 face="Calibri"><br>
</font><font size=2 face="sans-serif"><br>
The same goes with A1.7.6 </font><font size=3 face="Times New Roman"><b>Carrier
Mode Select</b></font>
<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:<br>
a) ‘00’ = Suppressed Carrier (Requires transmit
side utilize Modulation Index of 90°and transmit/receive sides utilize
Differential Mark Encoding/Decoding);<br>
b) ‘01’ = Residual Carrier;<br>
c) ‘10’ = Reserved;<br>
d) ‘11’ = Reserved.</font>
<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><font size=2 face="sans-serif"><br>
My proposed solution: in A1.7.6 you remove the text after cross support.</font><font size=4 face="Calibri"><br>
</font><font size=2 face="sans-serif"><br>
Cheers, Enrico</font><font size=4 face="Calibri"><br>
<br>
</font>
<table width=100%>
<tr valign=top>
<td width=3%><font size=1 color=#5f5f5f face="sans-serif">From:</font>
<td width=96%><font size=1 face="sans-serif">"Kazz, Greg J (313B)"
<</font><a href=mailto:greg.j.kazz@jpl.nasa.gov><font size=1 color=blue face="sans-serif"><u>greg.j.kazz@jpl.nasa.gov</u></font></a><font size=1 face="sans-serif">></font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">To:</font>
<td><font size=1 face="sans-serif">"</font><a href=mailto:Gian.Paolo.Calzolari@esa.int><font size=1 color=blue face="sans-serif"><u>Gian.Paolo.Calzolari@esa.int</u></font></a><font size=1 face="sans-serif">"
<</font><a href=mailto:Gian.Paolo.Calzolari@esa.int><font size=1 color=blue face="sans-serif"><u>Gian.Paolo.Calzolari@esa.int</u></font></a><font size=1 face="sans-serif">>,
"</font><a href=mailto:Massimo.Bertinelli@esa.int><font size=1 color=blue face="sans-serif"><u>Massimo.Bertinelli@esa.int</u></font></a><font size=1 face="sans-serif">"
<</font><a href=mailto:Massimo.Bertinelli@esa.int><font size=1 color=blue face="sans-serif"><u>Massimo.Bertinelli@esa.int</u></font></a><font size=1 face="sans-serif">>,
"</font><a href=mailto:Enrico.Vassallo@esa.int><font size=1 color=blue face="sans-serif"><u>Enrico.Vassallo@esa.int</u></font></a><font size=1 face="sans-serif">"
<</font><a href=mailto:Enrico.Vassallo@esa.int><font size=1 color=blue face="sans-serif"><u>Enrico.Vassallo@esa.int</u></font></a><font size=1 face="sans-serif">>,
Cosby Matthew <</font><a href=mailto:MCOSBY@qinetiq.com><font size=1 color=blue face="sans-serif"><u>MCOSBY@qinetiq.com</u></font></a><font size=1 face="sans-serif">></font>
<tr>
<td valign=top><font size=1 color=#5f5f5f face="sans-serif">Cc:</font>
<td><font size=1 face="sans-serif">"</font><a href="mailto:sls-slp-bounces@mailman.ccsds.org"><font size=1 color=blue face="sans-serif"><u>sls-slp-bounces@mailman.ccsds.org</u></font></a><font size=1 face="sans-serif">"
<</font><a href="mailto:sls-slp-bounces@mailman.ccsds.org"><font size=1 color=blue face="sans-serif"><u>sls-slp-bounces@mailman.ccsds.org</u></font></a><font size=1 face="sans-serif">></font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Date:</font>
<td><font size=1 face="sans-serif">28/11/2011 18:53</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Subject:</font>
<td><font size=1 face="sans-serif">Updated Prox-1 DLL book ready for your
review</font></table>
<br>
<p>
<hr noshade><font size=4 face="Calibri"><br>
<br>
</font><font size=4 face="Calibri"><br>
All,</font><font size=4 face="Calibri"><br>
</font><font size=4 face="Calibri"><br>
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><font size=4 face="Calibri"><br>
</font><font size=4 color=blue face="Calibri"><u><br>
</u></font><a href=http://tinyurl.com/3n9qx9r><font size=4 color=blue face="Calibri"><b><u>http://tinyurl.com/3n9qx9r</u></b></font></a><font size=4 face="Calibri"><br>
</font><font size=4 face="Calibri"><b><br>
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><font size=4 face="Calibri"><br>
</font><font size=4 face="Calibri"><br>
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><font size=4 face="Calibri"><br>
</font><font size=4 face="Calibri"><br>
Thanks again for making this book consistent with the other books.</font><font size=4 face="Calibri"><br>
</font><font size=4 face="Calibri"><br>
Best regards,</font><font size=4 face="Calibri"><br>
</font><font size=4 face="Calibri"><br>
Greg Kazz<br>
Chairman SLS-SLP WG</font><font size=4 face="Calibri"><br>
</font>
<p>
<p>