[SLS-CC] Fw: 131.x0 Agency Review (LDPC slicing), RIDs discussion - results of the 2nd discussion

Mon May 1 09:54:12 UTC 2017

Dear All,
        after reading the proposals from Victor and Jon I got more and 
more puzzled.
It looks to me as the "catch all clause" is the main reason for the 
difficult understanding of the real requirement so I do recommend a 
different approach (i.e. divide et impera) as per attached file.
Clearly some fine tuning on the wording is likely to be needed (and I did 
include some alternative formulations).

I shall also remark that my proposal takes also into account that the 
original NOTE stating "Synchronization is acquired on the receiving end by 
recognizing the specific bit pattern of the ASM in the Physical Channel 
data stream; synchronization is then verified by making further checks." 
is now wrong when CSM is used.

Regards

Gian Paolo

From:   "Jon Hamkins" <jon.hamkins at jpl.nasa.gov>
To:     Massimo.Bertinelli at esa.int, "Space Link Coding & Synchronization 
Working Group" <sls-cc at mailman.ccsds.org>, Gian.Paolo.Calzolari at esa.int, 
"Kazz, Greg J(312B)" <greg.j.kazz at jpl.nasa.gov>
Cc:     Enrico.Vassallo at esa.int
Date:   27/04/2017 21:45
Subject:        Re: [SLS-CC] Fw: 131.x0 Agency Review (LDPC slicing), RIDs 
discussion - results of the 2nd discussion

I suggest three minor changes:

o change "when aligned with a Transfer Frames" to "when aligned with 
Transfer Frames"

o add a comma after "Turbo codewords" (to emphasize that "Turbo 
codewords" and "LDPC Codewords when aligned with Transfer Frames" are 
two distinct concepts)

o change "Transfer frames" to "Transfer Frames" (for consistency in 
capitalization in this book)

      ----Jon

On 04/26/2017 02:02 PM, Massimo.Bertinelli at esa.int wrote:
> Dear colleagues,
>
> Victor has kindly provided the following proposal for the disposition of
> ESA-RID_AM08 (as a reminder, the disposition was agreed already during
> the last teleconf
> discussion, but the precise text was left open and Victor volunteered to
> provide it).
> I'm fine with Victor's proposal and I'm ready to implement it.
> In case you have comments, please provide them by Tuesday 02 May close
> of business, otherwise I'll consider this closed.
>
> Best regards,
> Massimo
>
>
> ---------------------------------------------------
> Massimo Bertinelli
> Communication Systems Engineer
> ESA/Estec
>
> Tel. +31 (0)71 5653435
> --------------------------------------------------
>
>
> -----"SLS-CC" <sls-cc-bounces at mailman.ccsds.org
> <mailto:sls-cc-bounces at mailman.ccsds.org>> wrote: -----
> To: "Space Link Coding & Synchronization Working Group"
> <sls-cc at mailman.ccsds.org <mailto:sls-cc at mailman.ccsds.org>>,
> Gian.Paolo.Calzolari at esa.int <mailto:Gian.Paolo.Calzolari at esa.int>,
> "Kazz, Greg J\(312B\)" <greg.j.kazz at jpl.nasa.gov
> <mailto:greg.j.kazz at jpl.nasa.gov>>
> From: Massimo.Bertinelli at esa.int <mailto:Massimo.Bertinelli at esa.int>
> Sent by: "SLS-CC"
> Date: 04/06/2017 05:51PM
> Cc: Enrico.Vassallo at esa.int <mailto:Enrico.Vassallo at esa.int>
> Subject: [SLS-CC] Fw: 131.x0 Agency Review (LDPC slicing), RIDs
> discussion - results of the 2nd discussion
>
> Dear all,
>
> to simplify the verification work, this is the list of the RIDs
> processed and dispositioned yesterday:
>
> ESA: GPC-06, GPC-07, GPC-08, GPC-09, GPC-10, AM-01, AM-02, AM-03, AM-04,
> AM-05, AM-06, AM-07, AM-08
>
> Best regards,
> Massimo
> ---------------------------------------------------
> Massimo Bertinelli
> Communication Systems Engineer
> ESA/Estec
>
> Tel. +31 (0)71 5653435
> --------------------------------------------------
> ----- Forwarded by Massimo Bertinelli/estec/ESA on 04/06/2017 05:48 PM
> -----
>
> From:        Massimo.Bertinelli at esa.int <
mailto:Massimo.Bertinelli at esa.int>
> To:        Gian.Paolo.Calzolari at esa.int
> <mailto:Gian.Paolo.Calzolari at esa.int>, greg.j.kazz at jpl.nasa.gov
> <mailto:greg.j.kazz at jpl.nasa.gov>, sls-cc at mailman.ccsds.org
> <mailto:sls-cc at mailman.ccsds.org>
> Cc:        Enrico.Vassallo at esa.int <mailto:Enrico.Vassallo at esa.int>
> Date:        04/06/2017 04:35 PM
> Subject:        [SLS-CC] 131.x0 Agency Review (LDPC slicing), RIDs
> discussion - results of the 2nd discussion
> Sent by:        "SLS-CC" <sls-cc-bounces at mailman.ccsds.org
> <mailto:sls-cc-bounces at mailman.ccsds.org>>
> ------------------------------------------------------------------------
>
>
>
> Dear colleagues,
>
> thank you for participating to the second round of discussions for the
> RIDs disposition of the CCSDS 131.0-B Agency Review (introduction of
> LDPC slicing).
> You can find the RIDs disposition, as well as the Book updated
> accordingly, in CWE, under the San Antonio folder:
> _
> __http://tiny.cc/9lfcky_
>
> I would recommend that you have a look at the edited Book, to verify
> that the dispositions have been implemented faithfully.
> For AM-08, that was accepted but requiring a new formulation, Victor
> will provide one, I'll update the Book and the RIDs file once this is 
done.
>
> As a recap, we still need to process the following RIDs:
> ESA: MA-01, MA-02
> EUM: XE-001, XE-002, XE-003, XE-004, XE-005, XE-006, XE-007
> NASA: JN-01, JN-02, JN-03, JN-04, JN-05, JH-01, GK-01, GK-02
>
> Important: XE-003 raises an issue of the reset of the randomizer in the
> case of LDPC applied to a stream of CADUs. I would recommend everyone
> (and especially the proponents
> of this coding options) to consider this problem and arrive prepared at
> our San Antonio meeting (with e.g. analysis).
>
> Given the number of RIDs still open, I will book a full session (am or
> pm) for it at the meeting.
>
> Best regards,
> Massimo
>
> ---------------------------------------------------
> Massimo Bertinelli
> Communication Systems Engineer
> ESA/Estec
>
> Tel. +31 (0)71 5653435
> --------------------------------------------------
> 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.
>
> _______________________________________________
> SLS-CC mailing list
> SLS-CC at mailman.ccsds.org <mailto:SLS-CC at mailman.ccsds.org>
> https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sls-cc
> 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.
>
> _______________________________________________
> SLS-CC mailing list
> SLS-CC at mailman.ccsds.org <mailto:SLS-CC at mailman.ccsds.org>
> https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sls-cc
>
> 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.
>
>
>
> _______________________________________________
> SLS-CC mailing list
> SLS-CC at mailman.ccsds.org
> https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sls-cc
>

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-cc/attachments/20170501/3a1d1a51/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ESA-RIDs_AM-08.GPCproposal20170428.docx
Type: application/octet-stream
Size: 26681 bytes
Desc: not available
URL: <http://mailman.ccsds.org/pipermail/sls-cc/attachments/20170501/3a1d1a51/attachment.obj>