[CESG] CESG-P-2020-09-002 Approval to release CCSDS 231.0-P-3.1, TC Synchronization and Channel Coding (Pink Sheets, Issue 3.1) for CCSDS Agency review
CCSDS Secretariat
thomas.gannett at tgannett.net
Wed Oct 21 21:13:33 UTC 2020
Dear CESG Members,
Conditions for approval of CCSDS 231.0-P-3.1, TC Synchronization and
Channel Coding (Pink Sheets, Issue 3.1) have been disposed to the
satisfaction of the AD(s) who voted to approve with conditions. The
Secretariat will now proceed with CMC polling to authorize release
for Agency review.
-------------- next part --------------
From: Gian.Paolo.Calzolari at esa.int
Sent: Sunday, October 18, 2020 1:11 PM
To: Shames, Peter M (US 312B)
Cc: Kazz, Greg J (US 312B); Andrews, Kenneth S (US 332B);
Massimo.Bertinelli at esa.int; Tom Gannett
Subject: Re: YES/NO Question: [EXTERNAL] Re: Way forward for the TC Sync
and Channel Coding Blue Book - RESEND for completeness
Dear Peter,
after internal consultation, I confirm that for SLS Area and C&S Chairs the following change is
acceptable.
Namely Annex C2. Change
FROM either to a variable length TC Transfer Frame or a variable length USLP Transfer Frame
TO either to a TC Transfer Frame, or a USLP Transfer Frame.
After this modification NOTE 1 to the definition of Transfer Frames will state
In this document, it refers exclusively either to a TC Transfer Frame or to a USLP
Transfer Frame.
I am also disappointed by the distrust on the SLS Area team (not only me), including also in this case at
least Gilles, Massimo, Ken, and Greg.
Best regards
Gian Paolo
From: "Shames, Peter M (US 312B)" <peter.m.shames at jpl.nasa.gov>
To: "Gian Paolo Calzolari" <Gian.Paolo.Calzolari at esa.int>
Cc: "Kazz, Greg J (US 312B)" <greg.j.kazz at jpl.nasa.gov>, "Massimo.Bertinelli at esa.int"
<Massimo.Bertinelli at esa.int>, "Andrews, Kenneth S (US 332B)" <kenneth.s.andrews at jpl.nasa.gov>, "Tom Gannett"
<thomas.gannett at tgannett.net>
Date: 16-10-20 23:57
Subject: Re: YES/NO Question: [EXTERNAL] Re: Way forward for the TC Sync and Channel Coding Blue Book -
RESEND for completeness
Dear Gippo,
Please ignore that last, partial email. Outlook ambushed me.
I have to be clear that I am disappointed at the level of resistance that has showed up to making these
simple changes for clarity and consistency within the suite of SLS standards.
That said, I have also seen that you and Greg are working to resolve the descriptive ambiguities in the
USLP spec. As I stated earlier, this is a separable issue, since that is a separate standard, but it is, as I
know you understand, related directly to the services that TC Synch and Channel Coding must provide to
support both TC and USLP. We will leave the details of that for a later discussion.
In the interests of moving this specific standard ahead I am agreeing that the following changes to what
was proposed will be an acceptable resolution of the PID I raised in the CESG review of TC Synch &
Channel Coding, CCSDS 231x0p30. I quoted here, for completeness, what Ken stated. The objectionable
terms are struck out. What remains should be acceptable, according to your email to Greg dated 15 Oct
2020 @ 320PM PDT.
there are only a few words to be changed in the TC Blue Book, and none of them change the technical
content. Their intent is merely to clarify the connections between the TC Coding book and the Data Link
Layer books. To summarize, those changes are:
1. Annex A2. Change sequence of variable-length Transfer Frames to sequence of TC or USLP
Transfer Frames.
2. Annex C2. Change either to a variable length TC Transfer Frame or a variable length USLP Transfer
Frame to either to a variable length TC Transfer Frame, a variable length USLP Transfer Frame, or a
USLP Transfer Frame with truncated header.
3. Annex C. Change this from Informative to Normative.
I dont think that any of these are the least bit controversial.
Let's get on with this.
Best regards, Peter
From: "Gian.Paolo.Calzolari at esa.int" <Gian.Paolo.Calzolari at esa.int>
Date: Thursday, October 15, 2020 at 3:20 PM
To: "Kazz, Greg J (US 312B)" <greg.j.kazz at jpl.nasa.gov>
Subject: Re: YES/NO Question: [EXTERNAL] Re: Way forward for the TC Sync and Channel
Coding Blue Book
Thank you , Greg.
I think also #1 is overdoing it (and changing the format of the service annex wr have sldo in
other books) and that it will be simpler and more correct changing Annex C2.
Change FROM either to a variable length TC Transfer Frame or a variable length USLP
Transfer Frame
TO
either to a TC Transfer Frame or a USLP Transfer Frame
With no mention of truncated frames and no mention there of variable length upfront the transfer
frame.
Regards
Gian Paolo
Sent from my iPhone
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).
More information about the CESG
mailing list