<font size=2 face="sans-serif">Greg,</font>
<br>
<br><font size=2 face="sans-serif">please find a few comments specifically
on the interface USLP-C&S.</font>
<br>
<br><font size=2 face="sans-serif">On the point 3 below, I'm afraid I'm
completely against the approach taken: unless you are suggesting to disband
the C&S WG, I don't see how SLP can propose a new C&S book at all,
without having even discussed this</font>
<br><font size=2 face="sans-serif">in the C&S WG. </font>
<br>
<br><font size=2 face="sans-serif">Best regards,</font>
<br><font size=2 face="sans-serif">Massimo</font>
<br>
<br>
<br><font size=2 face="sans-serif"><br>
---------------------------------------------------<br>
Massimo Bertinelli<br>
Communication Systems Engineer<br>
ESA/Estec<br>
<br>
Tel. +31 (0)71 5653435<br>
--------------------------------------------------</font>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">"Kazz, Greg J
(312B)" <greg.j.kazz@jpl.nasa.gov></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">"sls-slp@mailman.ccsds.org"
<sls-slp@mailman.ccsds.org>, </font>
<br><font size=1 color=#5f5f5f face="sans-serif">Cc:
</font><font size=1 face="sans-serif">"Sank, Victor
J. (GSFC-560.0)[AS and D, Inc.]" <victor.j.sank@nasa.gov>, "Massimo.Bertinelli@esa.int"
<Massimo.Bertinelli@esa.int>, "Hamkins, Jon (3320)" <jon.hamkins@jpl.nasa.gov>,
"Andrews, Kenneth S (332B)" <kenneth.s.andrews@jpl.nasa.gov></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">07/07/2015 01:14</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">Updated Draft
USLP White Book for SLP WG and interested parties review</font>
<br>
<hr noshade>
<br>
<br>
<br><font size=4 face="Calibri">All,</font>
<br>
<br><font size=4 face="Calibri">Please find an updated USLP White Book
in the SLP WG area of the CWE under this URL for the Fall CCSDS meeting
in Darmstadt, Germany:</font>
<br>
<br><a href=http://tinyurl.com/nuu9xt8><font size=4 color=blue face="Calibri"><b><u>http://tinyurl.com/nuu9xt8</u></b></font></a>
<br>
<br><font size=4 face="Calibri">I would very much appreciate it if you
would please review this document and send me back you comments. Ideally
I would like you to do this before August 1. Note that this draft white
book contains references to several new draft books under construction
below:</font>
<br>
<br><font size=2 face="sans-serif">1. </font><font size=4 face="Calibri">COP-U
(a draft specification that attempts to create a COP for both Proximity
and Telecommand Applications). See </font><a href=http://tinyurl.com/q4d5fyy><font size=4 color=blue face="Calibri"><b><u>http://tinyurl.com/q4d5fyy</u></b></font></a>
<br><font size=2 face="sans-serif">2. </font><font size=4 face="Calibri">SOM
– Session Operations Management Sublayer of USLP – Currently our thought
is to make this separate from the USLP White Book. (Note that the USLP
White Book is modeled based upon the existing TC, TM, AOS Space Data Link
Layer books and NOT the Proximity-1 Space Data Link Book which doesn’t
conform as well to the other three.) See </font><a href=http://tinyurl.com/p55g3oj><font size=4 color=blue face="Calibri"><b><u>http://tinyurl.com/p55g3oj</u></b></font></a>
<br><font size=2 face="sans-serif">3. </font><font size=4 face="Calibri">C&S-USLP
(a draft specification to gather our thoughts about the interactions between
USLP and the C&S sublayer). Clearly this work will eventually be done
by the C&S WG, when the time comes to undertake it. </font><a href=http://tinyurl.com/od43f9t><font size=4 color=blue face="Calibri"><b><u>http://tinyurl.com/od43f9t</u></b></font></a>
<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><PRE>This message and any attachments are intended for the use of the addressee or addressees only.
The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its
content is not permitted.
If you received this message in error, please notify the sender and delete it from your system.
Emails can be altered and their integrity cannot be guaranteed by the sender.
Please consider the environment before printing this email.
</PRE>