[SLS-CC] CCSDS 230.1-G-2.1 - Green Book TC - approved with comments - please check deadline

Andrea.Modenini at esa.int Andrea.Modenini at esa.int
Fri Sep 3 06:50:35 UTC 2021


Dear Ken,
 thanks a lot for the good work. I believe as well that this completes our 
action and the GB is ready for publication.

I kindly ask Ignacio to raise a resolution for publication of 230.1-G-2.1 
as in attachment, and put in CC Tom for information.

Thanks everybody,
Andrea
 


ESA - European Space Agency
Ph.D. Andrea Modenini
Communication Systems & Technologies Engineer 
TT&C and PDT Systems & Techniques Section (TEC-EST)
RF Systems Division
ESTEC
Keplerlaan 1, PO Box 299
NL-2200 AG Noordwijk, The Netherlands
andrea.modenini at esa.int | www.esa.int
T +31 71 56 53439, M +31 6 484 56 527



From:   "Andrews, Kenneth S (US 332B)" <kenneth.s.andrews at jpl.nasa.gov>
To:     "Andrea Modenini (external)" <Andrea.Modenini at esa.int>
Cc:     "Space Link Coding & Synchronization Working Group" 
<sls-cc at mailman.ccsds.org>, "Ignacio.Aguilar.Sanchez at esa.int" 
<Ignacio.Aguilar.Sanchez at esa.int>
Date:   03-09-21 06:52
Subject:        Re: [SLS-CC] CCSDS 230.1-G-2.1 - Green Book TC - approved 
with comments - please check deadline



Andrea, 

Finally, an updated version of the TC Green Book is attached, in both 
.docx and .pdf formats (showing change tracking).  The only change from 
the prior version, dated July 8, is that I reverted the modifications that 
were intended to address point 2.  This means that Section 10.1 now reads 
the same as it did prior to the CESG poll, and I deleted references [8] 
and [9] again (which were cited in Section 10.1 as references for CFDP and 
LTP).  As for change tracking, I took the time to accept each change that 
was caused by Microsoft’s automatic renumbering.  The result (I hope) is 
that the change tracking now shows all human-made edits since the CESG 
poll, in a readable way.

I believe this completes our action with respect to the “Approve with 
Conditions” result from the CESG poll for publication, and these changes 
can now go back to Tom Gannett for one more update.  After that, I don’t 
know if the CCSDS procedure is to get Peter Shames’s concurrence (as the 
CESG member who imposed these conditions), or to repeat the full CESG 
poll, or whether it can now proceed to the CMC poll for publication.

-Ken



On Aug 19, 2021, at 6:46 AM, Andrea Modenini (external) <
Andrea.Modenini at esa.int> wrote:

Dear Ken, 
 following the comments we received, I believe we had WG consensus. All 
points are accepted, except 2). 

If you could please provide us an updated draft accordingly and then we 
can ask for a SLS AD resolution. 
I guess it is sufficient to reject the edit in Section 10.1, but please 
let me know. 


Thanks in advance, 
Kind Regards 


HE Space Operations for ESA - European Space Agency 
Ph.D. Andrea Modenini
Communication Systems & Technologies Engineer 
TT&C and PDT Systems & Techniques Section (TEC-EST)
RF Systems Division
ESTEC
Keplerlaan 1, PO Box 299
NL-2200 AG Noordwijk, The Netherlands
andrea.modenini at esa.int | www.esa.int
T +31 71 56 53439, M +31 6 484 56 527 



From:        Andrea Modenini/estec/ESA 
To:        "Space Link Coding & Synchronization Working Group" <
sls-cc at mailman.ccsds.org> 
Date:        28-07-21 16:01 
Subject:        [SLS-CC] CCSDS 230.1-G-2.1 - Green Book TC - approved with 
comments - please check deadline 


Dear colleagues, 
 with reference to the Green Book of the TC, at CESG pool, we got an 
approval with conditions from SEA AD, with the feedback below. 
Following discussion with the SLS AD and DAD, it was decided to re-iterate 
such conditions at WG level. 

Kindly, Ken already took action to provide a draft of the TC Green Book 
implementing such edits (see attachment). 

I myself reviewed the comments: 
-Point 3, 4, and 5, look normal editorials. 
-point 1) is about including USLP. This appear in line with the Blue Book 
review that we had recently 
-point 2) implies instead the introduction of CFDP and LTP for TC. 
Personally I am not aware that we had any discussion/input in the WG for 
allowing the use of such protocols for TC, nor I see any content in the 
BlueBook. 
If this is the case, my personal opinion would be to discard this last 
point. 


Starting from this, could you please assess my conclusions and let me know 
any disagreement no later than 13rd August EOB? 

In case deadline does not fit because of planned vacation, please also let 
me know that I will consider an extension. 

Kind Regards 




---- 

It's great that this doc is now being updated, given all of the changes in 
the C&S WG and other SLS standards.  I identify the following Issues:
1) There is no mention of USLP, expecially in the variable length frame 
mode.  Only TC is included.  This must be fixed.  Too many sections to 
list.
2) In sec 10.3.3.1 (and 10.3.3.4) the only option described for handling 
"long wait times" on deep space links is the repeat function.  However, 
equally viable methods are to use CFDP of even LTP to provide automated 
file or link layer reliability.  These should be addressed.
3) The term "CODEWORD", "Codeword", and "codeword" are all used, sometimes 
in the same sentence.  They look different but apparently mean the same 
thing.  Provide some description of this early in the doc to avoid any 
possible confusion.  Too many sections to list.
4) In Glossary "codeword" is not really defined, just a reference is 
provided.  Fix this.  Also, both encoding and decoding definitions only 
mention BCH, not LDPC.  Please fix this throughout.
5) There are many new scholarly references, which is fine.  At least one, 
[27], appears to have no reference identified in the body of the text. 
Please fix this.


HE Space Operations for ESA - European Space Agency 
Ph.D. Andrea Modenini
Communication Systems & Technologies Engineer 
TT&C and PDT Systems & Techniques Section (TEC-EST)
RF Systems Division
ESTEC
Keplerlaan 1, PO Box 299
NL-2200 AG Noordwijk, The Netherlands
andrea.modenini at esa.int | www.esa.int
T +31 71 56 53439, M +31 6 484 56 527 

This message is intended only for the recipient(s) named above. It may 
contain proprietary information and/or
protected content. Any unauthorised disclosure, use, retention or 
dissemination is prohibited. If you have received
this e-mail in error, please notify the sender immediately. ESA applies 
appropriate organisational measures to protect
personal data, in case of data privacy queries, please contact the ESA 
Data Protection Officer (dpo at esa.int).

<TC Green 2021July8.docx>_______________________________________________
SLS-CC mailing list
SLS-CC at mailman.ccsds.org
https://urldefense.us/v3/__https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sls-cc__;!!PvBDto6Hs4WbVuu7!cIc9E32LLHyMjJ-uo1Oqz86iETs6la0_4ahaNg3YU-oMMPxxVlmDEmHkS2d8i13z_ClyRnNF$ 





This message is intended only for the recipient(s) named above. It may contain proprietary information and/or
protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received
this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect
personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo at esa.int).

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/sls-cc/attachments/20210903/e1ffa47c/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: TC Green 2021Sept2.docx
Type: application/octet-stream
Size: 2426384 bytes
Desc: not available
URL: <http://mailman.ccsds.org/pipermail/sls-cc/attachments/20210903/e1ffa47c/attachment-0001.obj>


More information about the SLS-CC mailing list