<font size=2 face="sans-serif">Greg,</font>
<br><font size=2 face="sans-serif"> with
respect to the COPs I think we need some discussion in Cleveland at least
to fix some ideas/decisions.</font>
<br><font size=2 face="sans-serif">In addition to what Tomaso asks, we
may want to point out about COP-1 usage vs. protocols.</font>
<br><font size=2 face="sans-serif">Clearly the CLCW has a 6 bits VC identifier
to it can report about data received either within a TC frame or via a
USLP Frame as both of them have the same size VC identifier.</font>
<br><font size=2 face="sans-serif">In other words it is possible to have
a link with TC Frames in Uplink and USLP Frames in downlink as well as
having a link with USLP Frames in both directions.</font>
<br><font size=2 face="sans-serif">This may need to be verified, agreed
and spelled out in the document.</font>
<br>
<br><font size=2 face="sans-serif">Another point is that it looks as USLP
Managed Parametrs have nothing about usage with Proximity-1 and COP-P.</font>
<br><font size=2 face="sans-serif">This is clearly an inheratanche from
the fact that Proximity-1 unfortunately has no (formal) section for Managed
Parameters.</font>
<br><font size=2 face="sans-serif">STill there is the need of importing/defining
some USLP managed parameter for usage with Proximity-1 and COP-P (e.g.
PLCW_Repeat_Interval, PLCW Timer, etc.).</font>
<br><font size=2 face="sans-serif">I fear this task may be a little more
complex to the "catch all" nature of Proximity-1 SDLP book and
an action may need to be assigned and, at the very extreme, the need for
a Magenta may be investigated.</font>
<br>
<br><font size=2 face="sans-serif">In general USLP docs just says:</font>
<br><font size=3 color=blue face="Times New Roman">The use of either the
COP-1, or COP-P procedures are optional and both are compatible with the
USLP. The Protocol Data Units (CLCW for COP-1 and PLCW for COP-P) and operational
procedures for both COP-1 and COP-P are not identical but similar and are
transparent to USLP.</font>
<br>
<br><font size=2 face="sans-serif">It may be an Annex could clarify how
they are supposed to work with USLP.</font>
<br>
<br><font size=2 face="sans-serif">It may a dedicated agenda (sub)point
about USLP vs. COPs should be added.</font>
<br>
<br><font size=2 face="sans-serif">Regards</font>
<br>
<br><font size=2 face="sans-serif">Gian Paolo</font>
<br>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif"><Tomaso.deCola@dlr.de></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif"><greg.j.kazz@jpl.nasa.gov></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Cc:
</font><font size=1 face="sans-serif">sls-slp@mailman.ccsds.org</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">10/03/2016 09:11</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">[Sls-slp] RE:
March 8 Telecon #4 Meeting Minutes now on CWE</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Sent by:
</font><font size=1 face="sans-serif">sls-slp-bounces@mailman.ccsds.org</font>
<br>
<hr noshade>
<br>
<br>
<br><font size=2 color=#004080 face="Calibri">Greg,</font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri">Actually I don’t ask to
add 1 byte but to make a more efficient use of the 5+8 bits, which are
defined at the moment to protocol information and possible extensions.
What I personally don’t like much is the fact that we’ll have a field
where we’ll be mixing together protocol identifier and COP signaling indication
(as also pointed out by Gian Paolo), which should instead go separated
in my view.</font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri">I’d indeed appreciate if
you could add these points in the Cleveland agenda, so that we can reach
an easy and quick agreement on how to proceed with this.</font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri">Best Regards,</font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri">Tomaso</font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#5f5f5f face="Arial">————————————————————————</font><font size=3 color=#004080 face="Times New Roman">
</font><font size=2 color=#5f5f5f face="Arial"><b><br>
Deutsches Zentrum für Luft- und Raumfahrt</b> (DLR)</font><font size=3 color=#004080 face="Times New Roman">
</font><font size=2 color=#5f5f5f face="Arial"><br>
German Aerospace Center</font><font size=3 color=#004080 face="Times New Roman">
</font><font size=2 color=#5f5f5f face="Arial"><br>
Institute of Communications and Navigation | Satellite Networks | Oberpfaffenhofen
| 82234 Wessling | Germany</font><font size=3 color=#004080 face="Times New Roman">
</font>
<br><font size=2 color=#5f5f5f face="Arial"><b>Tomaso de Cola, Ph.D.</b></font><font size=2 color=#004080 face="Calibri">
</font><font size=2 color=#5f5f5f face="Arial"><br>
Telefon +49 8153 28-2156 | Telefax +49 8153 28-2844 |</font><font size=2 color=#004080 face="Arial">
</font><a href=mailto:tomaso.decola@dlr.de><font size=2 color=blue face="Arial"><u>tomaso.decola@dlr.de</u></font></a><font size=2 color=#004080 face="Calibri">
</font><font size=2 color=blue face="Arial"><u><br>
</u></font><a href=http://www.dlr.de/kn/institut/abteilungen/san><font size=2 color=blue face="Arial"><u>http://www.dlr.de/kn/institut/abteilungen/san</u></font></a><font size=2 color=#004080 face="Calibri">
</font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 face="Tahoma"><b>From:</b> Kazz, Greg J (312B) [</font><a href=mailto:greg.j.kazz@jpl.nasa.gov><font size=2 face="Tahoma">mailto:greg.j.kazz@jpl.nasa.gov</font></a><font size=2 face="Tahoma">]
<b><br>
Sent:</b> Wednesday, March 09, 2016 17:18<b><br>
To:</b> Cola, Tomaso de<b><br>
Cc:</b> sls-slp@mailman.ccsds.org<b><br>
Subject:</b> Re: March 8 Telecon #4 Meeting Minutes now on CWE</font>
<br><font size=3 face="Times New Roman"> </font>
<br><font size=4 face="Calibri">Tomaso,</font>
<br><font size=4 face="Calibri"> </font>
<br><font size=3 color=#004080 face="Calibri">We heard your suggestions
and considered them but we believe that the original suggested 5 bit (32
protocols) was adequate but provided for unexpected growth by providing
the signaled inclusion of an additional 255 IDs. Why add a byte when
we don’t need it? Of course, this can be discussed further in CLE.</font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 color=#004080 face="Calibri">Best regards,</font>
<br><font size=3 color=#004080 face="Calibri">Greg</font>
<br><font size=4 face="Calibri"> </font>
<br><font size=2 face="Calibri"><b>From: </b>"</font><a href=mailto:Tomaso.deCola@dlr.de><font size=2 color=blue face="Calibri"><u>Tomaso.deCola@dlr.de</u></font></a><font size=2 face="Calibri">"
<</font><a href=mailto:Tomaso.deCola@dlr.de><font size=2 color=blue face="Calibri"><u>Tomaso.deCola@dlr.de</u></font></a><font size=2 face="Calibri">><b><br>
Date: </b>Wednesday, March 9, 2016 at 5:02 AM<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:sls-slp@mailman.ccsds.org"><font size=2 color=blue face="Calibri"><u>sls-slp@mailman.ccsds.org</u></font></a><font size=2 face="Calibri">"
<</font><a href="mailto:sls-slp@mailman.ccsds.org"><font size=2 color=blue face="Calibri"><u>sls-slp@mailman.ccsds.org</u></font></a><font size=2 face="Calibri">><b><br>
Subject: </b>RE: March 8 Telecon #4 Meeting Minutes now on CWE</font>
<br><font size=4 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri">Greg,</font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri">Just a clarification about
the field transporting the protocol identifiers. In the past weeks, we
discussed with Ed, Gian Paolo and Keith about the large space allocated
so far (8+5 bits) and somehow agreed that we can simply have 8 bits (256
combinations are enough to account all different protocol and extensions
where applicable) and leave the remaining 5 (which help for 32-bits alignment)
as reserved. However, I cannot see this point reflected in the current
version of the book. If this solution could be implemented in the book,
then we could use any of the 5-reseved bits to bring information about
the COP stuff, without mixing together COP and proto identifiers in the
8 bits field.</font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri">Best Regards,</font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri">Tomaso</font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#5f5f5f face="Arial">————————————————————————<b><br>
Deutsches Zentrum für Luft- und Raumfahrt</b> (DLR)<br>
German Aerospace Center<br>
Institute of Communications and Navigation | Satellite Networks | Oberpfaffenhofen
| 82234 Wessling | Germany</font>
<br><font size=2 color=#5f5f5f face="Arial"><b>Tomaso de Cola, Ph.D.</b><br>
Telefon +49 8153 28-2156 | Telefax +49 8153 28-2844 |</font><a href=mailto:tomaso.decola@dlr.de><font size=2 color=blue face="Arial"><u>tomaso.decola@dlr.de</u></font></a><font size=2 color=blue face="Arial"><u><br>
</u></font><a href=http://www.dlr.de/kn/institut/abteilungen/san><font size=2 color=blue face="Arial"><u>http://www.dlr.de/kn/institut/abteilungen/san</u></font></a>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 face="Tahoma"><b>From:</b> </font><a href="mailto:sls-slp-bounces@mailman.ccsds.org"><font size=2 color=blue face="Tahoma"><u>sls-slp-bounces@mailman.ccsds.org</u></font></a><font size=2 face="Tahoma">
[</font><a href="mailto:sls-slp-bounces@mailman.ccsds.org"><font size=2 color=blue face="Tahoma"><u>mailto:sls-slp-bounces@mailman.ccsds.org</u></font></a><font size=2 face="Tahoma">]
<b>On Behalf Of </b>Kazz, Greg J (312B)<b><br>
Sent:</b> Tuesday, March 08, 2016 19:06<b><br>
To:</b> </font><a href="mailto:sls-slp@mailman.ccsds.org"><font size=2 color=blue face="Tahoma"><u>sls-slp@mailman.ccsds.org</u></font></a><font size=2 face="Tahoma"><b><br>
Subject:</b> [Sls-slp] March 8 Telecon #4 Meeting Minutes now on CWE</font>
<br><font size=3 face="Times New Roman"> </font>
<br><font size=4 face="Calibri">Dear SLP WG,</font>
<br><font size=4 face="Calibri"> </font>
<br><font size=4 face="Calibri">Please find the minutes of USLP Draft White
Book Telecon #4 on the CWE under the following URL:</font>
<br><font size=4 face="Calibri"> </font>
<br><a href=http://tinyurl.com/jf9j6u3><font size=4 color=blue face="Calibri"><u>http://tinyurl.com/jf9j6u3</u></font></a>
<br><font size=4 face="Calibri"> </font>
<br><font size=4 face="Calibri"><u>The filename is: USLP Telecon 4 minutes
March 08_2016</u></font>
<br><font size=4 face="Calibri"> </font>
<br><font size=3 face="Calibri"><u>B</u></font><font size=4 face="Calibri"><u>est
regards,</u></font>
<br><font size=3 face="Times New Roman"> </font>
<br><font size=4 face="Calibri"><u>Greg</u></font><tt><font size=2>_______________________________________________<br>
Sls-slp mailing list<br>
Sls-slp@mailman.ccsds.org<br>
</font></tt><a href="http://mailman.ccsds.org/mailman/listinfo/sls-slp"><tt><font size=2>http://mailman.ccsds.org/mailman/listinfo/sls-slp</font></tt></a><tt><font size=2><br>
</font></tt>
<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>