[Sls-slp] Comments to USLP_Issues_20160226

[Gian.Paolo.Calzolari at esa.int]

Dear Greg,
        can you please check and fix the USLP_Issues_20160226 as per 
comments below.

1) The summary says Issue 2 Closed @ telecon #3 but no comment has been 
added to Issue 2 in the main body of the document and nothing is mentioned 
in Telcon #3 MoMs.
Please clarify accordingly.

2) The summary says Issue 11 Closed @ telecon #3 but no comment has been 
added to Issue 2 in the main body of the document and nothing is mentioned 
in Telcon #3 MoMs.
I think the conclusion is that the  construction of the USLP frame is 
constrained by the choice of channel coding book as follows:
a) references 3, 4 and 5 (TM, SCCC, DVB-S2) require fixed length frame and 
OID frames to be generated when no "valid" frame is available.
b) some coding schemes of  references 3, 4 and 5 (TM, SCCC, DVB-S2) 
require CRC-16 mandatorily present
c) references 6 and 7 (TC, Proximity-1) allow variable length frame and 
OID frames shall not be generated.
Moreover when reference 5 (TC) is used, the coding layer would accept 
several frames in a protocol data but is but it has been agreed that USLP 
will not allow this feature (see issue 15).
Issue 11 description should be updated accordingly

3) Issue 12 should report also that some coding schemes of  references 3, 
4 and 5 (TM, SCCC, DVB-S2) require CRC-16 mandatorily present

Ciao

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/20160229/be97bed6/attachment.html>