[Sls-slp] [SLP] Some rewording for selected sections of Chapter 2 of the USLP draft Blue Book

Gian.Paolo.Calzolari at esa.int Gian.Paolo.Calzolari at esa.int
Thu Feb 11 15:11:47 UTC 2016

Dear Greg,
        can you please in the Agenda for the next USLP Telecon/Meeting the 
discussion of the the attached file containing Some rewording for selected 
sections of Chapter 2 of the USLP draft Blue Book?

The comments included on the side try to explain the rational for the 
proposed rewording.
I also think that two explicit questions shall be made to the SLP WG; i.e.
1) Shall USLP retain the TC Coding capability that a protocol data unit 
transferred can contain several frames?
The fact that TC coding allows it does not exclude a possible limitation 
on the USLP side (e.g. SLE FSP explicitly forbids the option of including 
several TC frames in a CLTU).
Note that I have no position on this topic, but we shall remeber that 
several frames in a CLTU do decrease performances.
2) Shall any reference to Proximity-1 coding be removed from the USLP Blue 
Book as long as there is no agreed adaptation for that blue book?

Best regards

Gian Paolo

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.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/sls-slp/attachments/20160211/14eecf22/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: USLP Space Data Link	Protocol_Jan_20_post_telecon1+codingReferences.pdf
Type: application/octet-stream
Size: 94676 bytes
Desc: not available
URL: <http://mailman.ccsds.org/pipermail/sls-slp/attachments/20160211/14eecf22/attachment.obj>

More information about the SLS-SLP mailing list