From thomas.gannett at tgannett.net  Thu Aug 10 18:07:47 2023
From: thomas.gannett at tgannett.net (=?UTF-8?B?Q0NTRFMgU2VjcmV0YXJpYXQ=?=)
Date: Thu, 10 Aug 2023 13:07:47 -0500
Subject: [CESG] =?utf-8?q?CESG_Poll_Closure_Reminder?=
Message-ID: <FileMaker.64d51963.1.1808@tgannett.net>

Dear CESG Members,

The closure date for the polls below is 14 August 2023.

- CESG-P-2023-07-001 Approval to release CCSDS 732.1-P-2.1, Unified Space Data Link Protocol (Sheets, Issue 2.1) for CCSDS Agency review
- CESG-P-2023-07-002 Approval to publish CCSDS 131.0-B-5, TM Synchronization and Channel Coding (Blue Book, Issue 5)

These polls can be accessed via the following link:

https://cwe.ccsds.org/fm/Lists/CESGPollQuestion/open.aspx


From thomas.gannett at tgannett.net  Tue Aug 15 16:13:03 2023
From: thomas.gannett at tgannett.net (=?UTF-8?B?Q0NTRFMgU2VjcmV0YXJpYXQ=?=)
Date: Tue, 15 Aug 2023 11:13:03 -0500
Subject: [CESG] =?utf-8?q?CESG_Poll_Closure_Extension?=
Message-ID: <FileMaker.64db95ff.1.1164@tgannett.net>

Dear CESG Members,

The CESG polls below failed to achieve quorum within the allotted polling period. The closure date for these polls has therefore been extended by THREE DAYS. The new closure date is August 17, 2023.

- CESG-P-2023-07-001 Approval to release CCSDS 732.1-P-2.1, Unified Space Data Link Protocol (Sheets, Issue 2.1) for CCSDS Agency review
- CESG-P-2023-07-002 Approval to publish CCSDS 131.0-B-5, TM Synchronization and Channel Coding (Blue Book, Issue 5)

These polls can be accessed via the following link:

https://cwe.ccsds.org/fm/Lists/CESGPollQuestion/open.aspx


From peter.m.shames at jpl.nasa.gov  Thu Aug 17 23:09:59 2023
From: peter.m.shames at jpl.nasa.gov (Shames, Peter M (US 312B))
Date: Thu, 17 Aug 2023 23:09:59 +0000
Subject: [CESG] CCSDS resolution: SEA-R-2023-08-001: Request for publication
 of Time Management Green Book, CCSDS xxxx0r1
Message-ID: <73C7C3B9-F493-4A0E-95F1-36B8978D4468@jpl.nasa.gov>

Dear CCSDS Secretariat,

Resolution: SEA-R-2023-08-001: Request for publication of Time Management Green Book, CCSDS xxxx0r1

The Systems Engineering Area,

CONSIDERING that the SEA Time Management WG has completed the development for the CCSDS Time Management Green Book (which does not yet appear to have a CCSDS number assigned),
And that the WG has asked that the document be forwarded for publication,
And that the SEA AD has reviewed the document (attached) and concurs with the WG request.

And RECOGNIZING that responsibility for requesting publication of a document is an AD responsibility,

RESOLVES to request Secretariat to process the document and submit it for CESG approval to publish, and

REQUESTS that the CESG poll be conducted to accomplish this.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/cesg/attachments/20230817/41c8776f/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2023-05-12-Time-Management-green-book-draft-v03-SEA.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 22501034 bytes
Desc: 2023-05-12-Time-Management-green-book-draft-v03-SEA.docx
URL: <http://mailman.ccsds.org/pipermail/cesg/attachments/20230817/41c8776f/attachment-0001.docx>

From peter.m.shames at jpl.nasa.gov  Thu Aug 17 23:43:36 2023
From: peter.m.shames at jpl.nasa.gov (Shames, Peter M (US 312B))
Date: Thu, 17 Aug 2023 23:43:36 +0000
Subject: [CESG] [EXTERNAL]  LunaNet Interoperability Specification
Message-ID: <62680C52-DF67-4852-8764-7C11CD8EBAD4@jpl.nasa.gov>

Dear Klaus-Juergen, and the CESG team,

I sent this original email out on 8 June.   I have myself been on travel for part of the time since then, so I may have missed any replies or commentary, but I went searching for them and found nothing.  I do recognize that August tends to be vacation month in Europe, so maybe that is the cause of the strange silence.

Or maybe we just really do not have a clue how to deal with this?

After reading through the LNIS, LunaNet, ICSIS, and related specs, and digging for technical details, I am finding that there appear to be some major architectural disconnects.  These are touted as being “interoperability” specs, and yet they fail that test upon closer examination.  An example of this is the attached table, from a recent presentation by Jim Schier.

Note the following in this table:

  1.  LNIS is specing IPv4 or v6 over IPSEC
  2.  DTN is speced as BPv6 or v7 over TCP CLA (over IPSEC)
  3.  Therefore TCP/IP is being assumed everywhere, even out to the Moon

As I read that table it says “DTN over TCP CLA over IPSEC”.   That means DTN is being deployed as an “overlay network” on top of TCP/IP, but many of us realize that TCP/IP will not work at GEO distances, let alone Lunar or Mars.  No mention of a DTN over CCSDS Space Link CLA.  No mention of “islands of IP connected via DTN”.  I see no mention of any sort of protocol translating gateways in any of these docs.  Let alone mapping any other application layer protocols to Bundle delivery (and out again).

Different people seem to read these specs in different ways, to mean different things.  This is not a surprise since they include a variety of different specs, but no consistent architecture.  As such they seem to be more of a “shopping list” than an interoperability spec.

Please, provide some feedback.  Anything would be better than this echoing silence.

Thanks, Peter


From: CESG <cesg-bounces at mailman.ccsds.org> on behalf of CESG <cesg at mailman.ccsds.org>
Reply-To: Peter Shames <peter.m.shames at jpl.nasa.gov>
Date: Thursday, June 8, 2023 at 3:44 PM
To: Klaus-Juergen Schulz <Klaus-Juergen.Schulz at esa.int>, Tim Pham <timothy.t.pham at jpl.nasa.gov>, CESG <cesg at mailman.ccsds.org>
Cc: Sami Asmar <sami.w.asmar at jpl.nasa.gov>
Subject: [EXTERNAL] [CESG] LunaNet Interoperability Specification

Dear Klaus-Juergen and the rest of the CESG team,

During last week’s CMC meeting several of the topics relating to the “NASA / ESA LunaNet Interoperability Specification” were explored.  The CESG discussed it again on Tuesday, with specific emphasis on the LunaNet Position, Navigation, and Timing spec (or lack of info on this).  A set of PPT materials were presented to the CMC last week and these will be made available.

I believe that it is the case that the strongest motivation for digging into this specification is that there are at least three separate missions, from three separate agencies, that are intending to (or have) asserted compliance with this spec.  These are:


  *   NASA’s Lunar Communications Relay and Navigation Systems (LCRNS)
  *   ESA’s Moonlight
  *   JAXA’s “LNSS” mission (I missed the name, anyone???)

The LNIS spec is out in the public domain.  It can be found here (https://esc.gsfc.nasa.gov/static-files/LunaNet%20Interoperability%20Specification.pdf), and at several other locations as well.  If you know what to look for it is there.  Just search for “LunaNet Interoperability  Specification”.   When you do that you will find several versions of the spec, related articles and papers, etc.   There are also links, if you dig for them, to the ESA Moonlight project (https://www.esa.int/Applications/Connectivity_and_Secure_Communications/Moonlight<https://urldefense.us/v3/__https:/www.esa.int/Applications/Connectivity_and_Secure_Communications/Moonlight__;!!PvBDto6Hs4WbVuu7!IUsGwWkeWVVBX4UoYb9RVLGgmkGw3aw9QAXpwp7vZNn_2KBTvS5jQzRcevTJIrjFaiHaJgxKCf4wFQdJ1FNGLixPtsE$>) and to the JAXA LNSS plans (https://www.unoosa.org/documents/pdf/icg/2022/ICG16/WG-B/ICG16_WG-B_03.pdf<https://urldefense.us/v3/__https:/www.unoosa.org/documents/pdf/icg/2022/ICG16/WG-B/ICG16_WG-B_03.pdf__;!!PvBDto6Hs4WbVuu7!IUsGwWkeWVVBX4UoYb9RVLGgmkGw3aw9QAXpwp7vZNn_2KBTvS5jQzRcevTJIrjFaiHaJgxKCf4wFQdJ1FNGueV6vqc$>).

There is an open question as to just how closely these separate agency Lunar comm and nav missions are coordinating, and if the LNIS is truly the coordinated comm and nav architecture for all three.  The LNIS document itself is a little confusing in this regard, in that it is a GSFC Code 453 document stated to be developed by the NASA LCRNS Project, and signed by the LCRNS Project Manager.  It mentions “This current version of the document was written and reviewed by NASA and the European Space Agency (ESA).”, but there is no ESA signature nor named contributor.  And there is no mention of JAXA.  The LNIS document, after a brief scan for my favorite DTN interoperability topics, was found to be vague on some key features, like the distinctly different DTN and IP semantics and the need for some sort of protocol matching “bridge”, which is entirely missing.

There are many diagrams that appear to have been lifted from the IOAG comm and nav architecture specs, and the IOAG SISG and Lunar Comm Architecture documents are listed as References.  There are many tables that appear to be borrowed from the IOAG Lunar Comm doc that list many different CCSDS standards, including RFM, Coding, Link, DTN, and some SLE.  These are all essential to the comm architecture, but are given short shrift, and casually listed as “Other relevant documents”, when they should be listed as Requirements.

And there is a list of new “Applicable Documents”, which all appear to be, as of yet, TBD.   These Applicable Documents include:

[AD1] LunaNet and User Signal Structure Definition Document (LNIS4-TBD-AD0001)
[AD2] LunaNet Measurement Schema and Parameters Document (LNIS4-TBD-AD0002)
[AD3] LunaNet Detailed Message Definition Document (LNIS4-TBD-AD0003)
[AD4] LunaNet Location Services for Users Document (LNIS4-TBD-AD0004)
[AD5] Lunar Reference Frame Standard (LNIS4-TBD-AD0005)
[AD6] Lunar Time System Standard (LNIS4-TBD-AD0006)
[AD7] LunaNet LunaSAR Definition Document (LNIS4-TBD-AD0007)
[AD8] LunaNet Interoperability Security Specifications (LNIS4-TBD-AD0008)

The “mysteries” about how Lunar CPNT are intended to actually operate would appear to be hidden somewhere in these TBD docs.  My attempt to get any info about this from Cheryl Gramling, the NASA lead LNSS person, has yet to turn up anything useful.  Perhaps someone else, or in another agency like ESA, can provide some useful details of what the current thinking is?

At the CMC meeting we discussed the possibility of creating a new Lunar PNT WG in CCSDS to help support and structure this work and to give it a home in an international standards organization.  It is not yet clear whether this would be welcomed by the existing team or rejected because it might be seen as a constraint.   We do already have the MOIMS Nav WG, which provides many nav data interchange standards.  And we have in process the newly re-chartered SEA Time Management WG which is to include a time code, time exchange, and time distribution standard.  Plus there are some different SLS link and modulation layer standards that may be relevant, and even the possibility of using D-DOR for positioning info.

It seems to be an open question as to just how to tackle this, either in separate, but coordinated, WGs or in some new (or re-chartered) existing WG.

Regards, Peter



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/cesg/attachments/20230817/ad123532/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Schier Artemis, LNIS, ICSIS image001.png
Type: image/png
Size: 299301 bytes
Desc: Schier Artemis, LNIS, ICSIS image001.png
URL: <http://mailman.ccsds.org/pipermail/cesg/attachments/20230817/ad123532/attachment-0001.png>

From thomas.gannett at tgannett.net  Fri Aug 18 18:41:42 2023
From: thomas.gannett at tgannett.net (=?UTF-8?B?Q0NTRFMgU2VjcmV0YXJpYXQ=?=)
Date: Fri, 18 Aug 2023 13:41:42 -0500
Subject: [CESG] 
 =?utf-8?q?CESG-P-2023-07-001_Approval_to_release_CCSDS_73?=
 =?utf-8?q?2=2E1-P-2=2E1=2C_Unified_Space_Data_Link_Protocol_=28Sheets=2C_?=
 =?utf-8?q?Issue_2=2E1=29_for_CCSDS_Agency_review?=
Message-ID: <FileMaker.64dfad56.2.1908@tgannett.net>

Dear CESG Members,

Conditions for approval of CCSDS 732.1-P-2.1, Unified Space Data Link Protocol (Sheets, Issue 2.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:	Shames, Peter M (US 312B) <peter.m.shames at jpl.nasa.gov>
Sent:	Thursday, August 10, 2023 5:43 PM
To:	Kazz, Greg (US 312B); Thomas Gannett
Subject:	Re: [EXTERNAL] CESG poll to approve release of CCSDS 732.1-P-2.1, Unified 
Space Data Link Protocol (Pink Sheets, Issue 2.1) for CCSDS Agency review

Categories:	Poll Condition Closure

Thanks.  That works for me.

Peter


From: Greg Kazz <greg.j.kazz at jpl.nasa.gov> 
Date: Thursday, August 10, 2023 at 2:31 PM 
To: Peter Shames <peter.m.shames at jpl.nasa.gov>, Tom Gannett 
<thomas.gannett at tgannett.net> 
Subject: Re: [EXTERNAL] CESG poll to approve release of CCSDS 732.1-P-2.1, Unified Space Data 
Link Protocol (Pink Sheets, Issue 2.1) for CCSDS Agency review

Agreed.

Tom � Please add a note to the bottom of 6.5.2.2 Discussion as follows:

Note: These error conditions are detected either by the FARM and/or by the Frame Validation Check 
Procedure. To understand the reporting mechanisms with the FARM, one would go either to COP-1 Blue 
book or COP-P (currently within Prox-1 211.0) and examine the various frame rejection cases. These are 
reported in the CLCWs. Additionially and for links without ARQ, frame sequence counters are used to 
detect transfer frame gaps. For non-ARQ links, gaps are not reported but are detected by the receiving 
side via the frame sequence counter.

Thanks,
Greg

From: "Shames, Peter M (US 312B)" <peter.m.shames at jpl.nasa.gov> 
Date: Thursday, August 10, 2023 at 2:16 PM 
To: "Kazz, Greg (US 312B)" <greg.j.kazz at jpl.nasa.gov>, Thomas Gannett 
<thomas.gannett at tgannett.net> 
Subject: Re: [EXTERNAL] CESG poll to approve release of CCSDS 732.1-P-2.1, Unified Space Data 
Link Protocol (Pink Sheets, Issue 2.1) for CCSDS Agency review

Hi Greg,

From my PoV it would be better if in this document you stated that not only are the frames discarded, 
but that this is reported in the CLCW.

And my answer is yes to this question: �For non-ARQ links, gaps are not reported but are detected by 
the receiving side. Is a note to this effect warranted here ?�

Agreed?

I recognize that you do not want to repeat all of the contents of another spec every time one is 
referenced.  That said, if you are referencing a spec, as a sort of �black box�, I think it prudent to at least 
state what the gozintas and gozoutas are and what error conditions are signalled.

Thanks, Peter


From: Greg Kazz <greg.j.kazz at jpl.nasa.gov> 
Date: Thursday, August 10, 2023 at 11:00 AM 
To: Tom Gannett <thomas.gannett at tgannett.net>, Peter Shames 
<peter.m.shames at jpl.nasa.gov> 
Subject: Re: [EXTERNAL] CESG poll to approve release of CCSDS 732.1-P-2.1, Unified Space Data 
Link Protocol (Pink Sheets, Issue 2.1) for CCSDS Agency review

Hi Tom,

I searched the CESG copy of USLP and could only find this one comment by Peter (other than the typos 
you mentioned) highlighted in yellow. I put it into the attachment, but also reproduced it here with my 
response. If there is more, please let me know.

Peter � Please let us know if my response is sufficient ?

6.5.2.2 Discussion
*	The Frame Validation Check Procedure within the All Frames Reception Function includes the 
check of the FECF, if it is present. A transfer frame that fails any of these checks is discarded. 
*	FARM-1 function: the FARM-1 specified in reference [9] uses the Frame Sequence Number in 
the Primary Header of an incoming Type-A Transfer Frame to perform the Frame Acceptance 
Checks. If the checks indicate that the frame is out of sequence, FARM-1 discards the frame. 
Peter: �I�m a little surprised that the FVCP and FARM both silently discard frames.  Where are these 
error conditions caught and reported?�

Greg: Purpose was not to reproduce the FVCP and FARM procedures here, but to give sufficient 
background about the functionality. 1) These error conditions are detected either by the FARM and/or 
by the FVCP. To understand the reporting mechanisms with the FARM, one would go either to COP-1 
Blue book or COP-P (currently within Prox-1 211.0) and examine the various frame rejection cases. 
These are reported in the CLCWs. Additionally and for links without ARQ, frame sequence counters are 
used to detect transfer frame gaps. For non-ARQ links, gaps are not reported but are detected by the 
receiving side. Is a note to this effect warranted here ?

Thanks much,
Greg






From: Thomas Gannett <thomas.gannett at tgannett.net> 
Date: Thursday, August 10, 2023 at 10:18 AM 
To: "Kazz, Greg (US 312B)" <greg.j.kazz at jpl.nasa.gov> 
Cc: "Shames, Peter M (US 312B)" <peter.m.shames at jpl.nasa.gov> 
Subject: [EXTERNAL] CESG poll to approve release of CCSDS 732.1-P-2.1, Unified Space Data 
Link Protocol (Pink Sheets, Issue 2.1) for CCSDS Agency review

Greg:

Peter has some conditions for approval of the USLP pink sheets. In order to complete agency review 
prior to the fall meetings, the CMC poll will have to begin by the end of next week. So can you work with 
Peter to resolve his conditions within the next few days, like, by Tuesday next week? (I will fix any 
identified typos.)

Tom


Logothete, L.L.C.
thomas.gannett at tgannett.net
+1 443 472 0805


From LStafford at asrcfederal.com  Tue Aug 22 13:44:23 2023
From: LStafford at asrcfederal.com (Stafford, Laura L)
Date: Tue, 22 Aug 2023 13:44:23 +0000
Subject: [CESG] CESG-P-2023-08-001 Approval of SEA Time Management Working
 Group Chair
Message-ID: <SA0PR09MB7067929E31E3338FA22D550BB81FA@SA0PR09MB7067.namprd09.prod.outlook.com>

The CCSDS Engineering Steering Group:

CONSIDERING that the position of SEA Time Management WG Chair is open,
And that ESA has nominated Sinda Mejri, who has been the Deputy WG Chair, to fill that position;

and that Sinda has the necessary experience in the WG and excellent credentials;

and RECOGNIZING that responsibility for recommending a WG Chair is an AD responsibility,
And that approving the WG Chair is a CESG responsibility (CCSDS Org & Proc, A02.1-Y-4c2, Sec 2.3.2.3 CESG Responsibilities, Clause n);

RESOLVES to request CESG to approve the appointment of Sinda Mejri as the new SEA Time Management WG Chair.

________________________________

The preceding message (including attachments) is covered by the Electronic Communication Privacy Act, 18 U.S.C. sections 2510-2512, is intended only for the person or entity to which it is addressed, and may contain information that is confidential, protected by attorney-client or other privilege, or otherwise protected from disclosure by law. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error and destroy the original message and all copies.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/cesg/attachments/20230822/e268cd71/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: CESG Poll Closure.ics
Type: text/calendar
Size: 39708 bytes
Desc: CESG Poll Closure.ics
URL: <http://mailman.ccsds.org/pipermail/cesg/attachments/20230822/e268cd71/attachment-0001.ics>

From thomas.gannett at tgannett.net  Wed Aug 30 18:08:58 2023
From: thomas.gannett at tgannett.net (=?UTF-8?B?Q0NTRFMgU2VjcmV0YXJpYXQ=?=)
Date: Wed, 30 Aug 2023 13:08:58 -0500
Subject: [CESG] 
 =?utf-8?q?CESG-P-2023-06-005_Approval_to_publish_CCSDS_14?=
 =?utf-8?q?2=2E10-O-1=2C_Reed-Solomon_Product_Code_for_Optical_Communicati?=
 =?utf-8?q?on_=28Orange_Book=2C_Issue_1=29?=
Message-ID: <FileMaker.64ef77aa.1.1bf0@tgannett.net>

Dear CESG Members,

Conditions for approval of CCSDS 142.10-O-1, Reed-Solomon Product Code for Optical Communication (Orange Book, Issue 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 publication.
-------------- next part --------------
From:	Tomaso.deCola at dlr.de
Sent:	Wednesday, August 30, 2023 5:55 AM
To:	bernard.l.edwards at nasa.gov
Cc:	jon.hamkins at jpl.nasa.gov; Clemens.Heese at esa.int; 
thomas.gannett at tgannett.net; lena.e.braatz at nasa.gov; 
araki.tomohiro at jaxa.jp
Subject:	AW: CESG-P-2023-06-005 Approval to publish CCSDS 142.10-O-1, Reed-
Solomon Product Code for Optical Communication (Orange Book, Issue 1)

Categories:	Poll Condition Closure

Hi Bernie,

just checked the proposed modifications, which are ok for me. As such, my requests can be considered 
successfully fulfilled.

Regards,

Tomaso

From:	Barkley, Erik J (US 3970) <erik.j.barkley at jpl.nasa.gov>
Sent:	Friday, August 25, 2023 11:37 AM
To:	?????; Edwards, Bernard L. (GSFC-5600)
Cc:	Hamkins, Jon (US 3300); Thomas Gannett; Braatz, Lena E. (HQ-
DA000)[BOOZ ALLEN HAMILTON]; Clemens.Heese at esa.int; 
Hiroaki.Yamazoe at sony.com
Subject:	Re: [EXTERNAL] RE: CESG-P-2023-06-005 Approval to publish CCSDS 
142.10-O-1, Reed-Solomon Product Code for Optical Communication 
(Orange Book, Issue 1)

Categories:	Poll Condition Closure

The updated book looks very good. The condition is hereby retired. 

Best regards,
-Erik

 
From: ????? <araki.tomohiro at jaxa.jp> 
Sent: Friday, August 25, 2023 1:48:03 AM 
To: Edwards, Bernard L. (GSFC-5600) <bernard.l.edwards at nasa.gov>; Barkley, Erik J (US 3970) 
<erik.j.barkley at jpl.nasa.gov> 
Cc: Hamkins, Jon (US 3300) <jon.hamkins at jpl.nasa.gov>; Thomas Gannett 
<thomas.gannett at tgannett.net>; Braatz, Lena E. (HQ-DA000)[BOOZ ALLEN HAMILTON] 
<lena.e.braatz at nasa.gov>; Clemens.Heese at esa.int <Clemens.Heese at esa.int>; 
Hiroaki.Yamazoe at sony.com <Hiroaki.Yamazoe at sony.com> 
Subject: RE: [EXTERNAL] RE: CESG-P-2023-06-005 Approval to publish CCSDS 142.10-O-1, Reed-Solomon 
Product Code for Optical Communication (Orange Book, Issue 1) 
 
Bernie,
 
I apologies!
I understand well now. 
Updated file is attached on this email.
 
Regards,
 
Tomohiro Araki, JAXA
 
From: Edwards, Bernard L. (GSFC-5600) <bernard.l.edwards at nasa.gov>  
Sent: Friday, August 25, 2023 5:34 PM 
To: ????? <araki.tomohiro at jaxa.jp>; Barkley, Erik J (JPL-3970)[JPL Employee] 
<erik.j.barkley at jpl.nasa.gov> 
Cc: Hamkins, Jon (JPL-3300)[JPL Employee] <jon.hamkins at jpl.nasa.gov>; Thomas Gannett 
<thomas.gannett at tgannett.net>; Braatz, Lena E. (HQ-DA000)[BOOZ ALLEN HAMILTON] 
<lena.e.braatz at nasa.gov>; Clemens.Heese at esa.int 
Subject: Re: [EXTERNAL] RE: CESG-P-2023-06-005 Approval to publish CCSDS 142.10-O-1, Reed-Solomon 
Product Code for Optical Communication (Orange Book, Issue 1)
 
Hi Tomohiro, 
 
It should be 8b/10b. The �1� is missing!
 
Bernie
From: "?????" <araki.tomohiro at jaxa.jp> 
Subject: [EXTERNAL] RE: CESG-P-2023-06-005 Approval to publish CCSDS 142.10-O-1, Reed-Solomon 
Product Code for Optical Communication (Orange Book, Issue 1) 
Date: 25 August 2023 00:04 
To: "Edwards, Bernard L. (GSFC-5600)" <bernard.l.edwards at nasa.gov>, "Barkley, Erik J (JPL-3970)[JPL 
Employee]" <erik.j.barkley at jpl.nasa.gov> 
Cc: "Hamkins, Jon (JPL-3300)[JPL Employee]" <jon.hamkins at jpl.nasa.gov>, "Thomas Gannett" 
<thomas.gannett at tgannett.net>, "Braatz, Lena E. (HQ-DA000)[BOOZ ALLEN HAMILTON]" 
<lena.e.braatz at nasa.gov>, "Clemens.Heese at esa.int" <Clemens.Heese at esa.int> 

CAUTION: This email originated from outside of NASA.  Please take care when clicking links or opening 
attachments.  Use the "Report Message" button to report suspicious messages to the NASA SOC. 

Dear Bernie,
 
Corrected figure is attached on this email.
Is my understanding right?
If right, I will send you updated document file.
 
Regards,
 
Tomohiro Araki
 
From: Edwards, Bernard L. (GSFC-5600) <bernard.l.edwards at nasa.gov>  
Sent: Friday, August 25, 2023 5:05 AM 
To: Barkley, Erik J (JPL-3970)[JPL Employee] <erik.j.barkley at jpl.nasa.gov> 
Cc: Hamkins, Jon (JPL-3300)[JPL Employee] <jon.hamkins at jpl.nasa.gov>; Thomas 
Gannett <thomas.gannett at tgannett.net>; Braatz, Lena E. (HQ-DA000)[BOOZ ALLEN 
HAMILTON] <lena.e.braatz at nasa.gov>; ????? <araki.tomohiro at jaxa.jp>; 
Clemens.Heese at esa.int 
Subject: RE: CESG-P-2023-06-005 Approval to publish CCSDS 142.10-O-1, Reed-Solomon 
Product Code for Optical Communication (Orange Book, Issue 1) 
Importance: High
 
Hi Tomohiro,
 
We need you to make the change because  you have the latest figure.  After you do, can 
you send it to this thread?  It needs to be approved by Erik and Tom Gannett eventually 
needs it.
 
Thanks,
Bernie
 
From: Barkley, Erik J (US 3970) <erik.j.barkley at jpl.nasa.gov>  
Sent: Wednesday, August 23, 2023 5:11 PM 
To: Edwards, Bernard L. (GSFC-5600) <bernard.l.edwards at nasa.gov> 
Cc: Hamkins, Jon (JPL-3300)[JPL Employee] <jon.hamkins at jpl.nasa.gov>; Thomas 
Gannett <thomas.gannett at tgannett.net>; Braatz, Lena E. (HQ-DA000)[BOOZ ALLEN 
HAMILTON] <lena.e.braatz at nasa.gov>; ????? <araki.tomohiro at jaxa.jp>; 
Clemens.Heese at esa.int 
Subject: [EXTERNAL] RE: CESG-P-2023-06-005 Approval to publish CCSDS 142.10-O-1, 
Reed-Solomon Product Code for Optical Communication (Orange Book, Issue 1)
 
Hi Bernie,
 
It�s pretty close, but not quite there.  Just missing the �1� from �10�.  Please see 
screenshot from the latest book below.
 
Best regards,
-Erik
 
 
 
From: Edwards, Bernard L. (GSFC-5600) <bernard.l.edwards at nasa.gov>  
Sent: Wednesday, August 23, 2023 11:16 
To: Barkley, Erik J (US 3970) <erik.j.barkley at jpl.nasa.gov> 
Cc: Hamkins, Jon (US 3300) <jon.hamkins at jpl.nasa.gov>; Thomas Gannett 
<thomas.gannett at tgannett.net>; Braatz, Lena E. (HQ-DA000)[BOOZ ALLEN HAMILTON] 
<lena.e.braatz at nasa.gov>; ????? <araki.tomohiro at jaxa.jp>; 
Clemens.Heese at esa.int 
Subject: Re: CESG-P-2023-06-005 Approval to publish CCSDS 142.10-O-1, Reed-Solomon 
Product Code for Optical Communication (Orange Book, Issue 1)
 
Hi Erik,
 
We believe JAXA has met your condition in the attached version.  Please let us know if 
you concur.
 
Thanks,
Bernie Edwards
Here were the conditions levied:
 
 
 
-----Original Message-----
From: ????? <araki.tomohiro at jaxa.jp> 
Sent: Sunday, August 6, 2023 10:11 PM
To: Edwards, Bernard L. (GSFC-5600) 
<bernard.l.edwards at nasa.gov>
Cc: Hamkins, Jon (JPL-3300)[JPL Employee] 
<jon.hamkins at jpl.nasa.gov>; 
Clemens.Heese at esa.int; Braatz, Lena E. 
(HQ-DA000)[BOOZ ALLEN HAMILTON] 
<lena.e.braatz at nasa.gov>; Yamazoe, 
Hiroaki (JSC-OA111)[Sony Computer Science 
Laboratories, Inc] 
<hiroaki.yamazoe at sony.com>
Subject: [EXTERNAL] RE: CESG-P-2023-06-
005 Approval to publish CCSDS 142.10-O-1, 
Reed-Solomon Product Code for Optical 
Communication (Orange Book, Issue 1)
 
CAUTION: This email originated from 
outside of NASA.  Please take care when 
clicking links or opening 
attachments.  Use the "Report Message" 
button to report suspicious messages to 
the NASA SOC.
 
 
 
 
Dear Bernie,
 
How are you doing in this hot summer?
In Tsukuba and also Tokyo is extreme hot 
every day.
 
My colleague Yamazoesan and I made 
updated and final orange book draft 
reflecting CESG conditions as attached.
Please check and go forward.
I apologies our slow response.
 
Regards,
 
+++++++++++++++++++++++++++++++++++++
Tomohiro Araki
Optical Communication Research Team,
R&D directorate, JAXA
 
araki.tomohiro at jaxa.jp
+81-70-3117-7383
+++++++++++++++++++++++++++++++++++++
 
 
 
 
-----Original Message-----
From: Edwards, Bernard L. (GSFC-5600) 
<bernard.l.edwards at nasa.gov>
Sent: Tuesday, July 18, 2023 11:33 PM
To: ????? <araki.tomohiro at jaxa.jp>
Cc: Hamkins, Jon (JPL-3300)[JPL Employee] 
<jon.hamkins at jpl.nasa.gov>; 
Clemens.Heese at esa.int; Braatz, Lena E. 
(HQ-DA000)[BOOZ ALLEN HAMILTON] 
<lena.e.braatz at nasa.gov>
Subject: Re: CESG-P-2023-06-005 Approval 
to publish CCSDS 142.10-O-1, Reed-Solomon 
Product Code for Optical Communication 
(Orange Book, Issue 1)
 
Dear Tomohiro,
 
I hope you are doing well and that it is 
not too hot and humid in Japan this 
summer.
 
The JAXA Orange Book poll is complete and 
that there are conditions that must be 
met before publication.  See below.
 
As the email below indicates, disposition 
of the conditions must be negotiated 
directly with the AD(s) who submitted the 
conditions, and the Secretariat must be 
cc:d on all related correspondence. Tom 
Gannett will be responsible for making 
any required changes to the text, as he 
now maintains the most recent version of 
the book.  Of course, we can help you 
with this process.
 
Let me know if you have any questions.
 
Thanks,
Bernie
 
-----Original Message-----
From: CCSDS Secretariat 
<thomas.gannett at tgannett.net>
Sent: Tuesday, July 11, 2023 3:38 PM
To: bernard.l.edwards at nasa.gov; Braatz, 
Lena [USA] <braatz_lena at bah.com>
Cc: Erik.Barkley at jpl.nasa.gov; 
Tomaso.deCola at dlr.de
Subject: [External] Re: CESG-P-2023-06-
005 Approval to publish CCSDS 142.10-O-1, 
Reed-Solomon Product Code for Optical 
Communication (Orange Book, Issue 1)
 
Dear Document Rapporteur,
 
The CESG poll to approve publication of 
CCSDS 142.10-O-1, Reed-Solomon Product 
Code for Optical Communication (Orange 
Book, Issue 1) concluded with conditions. 
Please negotiate disposition of the 
conditions directly with the AD(s) who 
voted to approve with conditions and CC 
the Secretariat on all related 
correspondence.
 
 
CESG E-Poll Identifier:  CESG-P-2023-06-
005 Approval to publish CCSDS 142.10-O-1, 
Reed-Solomon Product Code for Optical 
Communication (Orange Book, Issue 1)
 
Results of CESG poll beginning 26 June 
2023 and ending 10 July 2023:
 
                 Abstain:  0 (0%)
 Approve Unconditionally:  2 (50%) 
(Aguilar Sanchez, Wilmot)  Approve with 
Conditions:  2 (50%) (Barkley, 
Cola)  Disapprove with Comment:  0 (0%)
 
CONDITIONS/COMMENTS:
 
     Erik Barkley (Approve with 
Conditions):  Pg 3-1 Figure 3-1 -- for 
clarity, in figure 3-1, suggest changing 
the box labeled "8b10b" to be "8b/10b 
Encoding"
 
     Tomaso de Cola (Approve with 
Conditions):  1) References [8] and [9] 
in section 1.8 do not appear to be 
normative (i.e. not recalled in the 
experimental specification part).
 
2) Section 2.1: the scope of the 
recommendation is state to be for 
spacecraft altitude at 1000-5000 km. Why 
nothing below 1000 km? Then aftewards 
still in Section 2.1 it is stated that 
the specification can apply also to 
longer distances. Up to deep space then?
 
3) Clause 3.2.3: Note 1 reports about 
supporting non-CCSDS frames (I guess 
those subject then to GFP), then note 2 
clarifies this may also happen through 
USLP multiplexing (I guess as user 
defined octet stream isn't it?). Wouldn't 
it better to have a note about CCSDS 
frames overall and then another one 
saying how one could support non-CCSDS 
protocols?
 
4) Annex B: it is claimed that an bit 
error rate simulations were conducted 
over AWGN channel with a fading channel: 
what does it mean exactly?
 
5) Annex B: where can one find evidence 
that the proposed scheme really works as 
stated? The Annex B title is about 
simulation results, but I cannot see any 
reported results in fact. If these are 
available in existing documents, please 
add reference to them.
 
 
Total Respondents:  4
 
No response was received from the 
following Area(s):
 
     SEA
     MOIMS
 
 
 
SECRETARIAT INTERPRETATION OF 
RESULTS:  Approved with Conditions
PROPOSED SECRETARIAT 
ACTION:            Generate CMC poll 
after conditions have been addressed
 
* * * * * * * * * * * * * * * * * * * * * 
* * *
 
 
 

From thomas.gannett at tgannett.net  Thu Aug 31 20:54:58 2023
From: thomas.gannett at tgannett.net (=?UTF-8?B?Q0NTRFMgU2VjcmV0YXJpYXQ=?=)
Date: Thu, 31 Aug 2023 15:54:58 -0500
Subject: [CESG] =?utf-8?q?New_CESG_Polls?=
Message-ID: <FileMaker.64f0f012.1.670@tgannett.net>

Dear CESG Members,

Six new CESG polls have been posted to the CWE:

- CESG-P-2023-08-002 Approval to publish CCSDS 232.0-B-4 Cor. 1, Technical Corrigendum  to CCSDS 232.0-B-4, Issued October 2021
- CESG-P-2023-08-003 Approval to release CCSDS 732.0-P-4.1, AOS Space Data Link Protocol (Sheets, Issue 4.1) for CCSDS Agency review
- CESG-P-2023-08-004 Approval to publish CCSDS 509.0-B-1 Cor. 2, Technical Corrigendum 2 to CCSDS 509.0-B-1, Issued February 2018
- CESG-P-2023-08-005 Approval to publish CCSDS 876.1-M-1, Spacecraft Onboard Interface Services—Specification for Dictionary of Terms for Electronic Data Sheets (Magenta Book, Issue 1)
- CESG-P-2023-08-006 Approval to publish CCSDS 702.1-B-1 Cor. 2, Technical Corrigendum 2 to CCSDS 702.1-B-1, issued September 2012
- CESG-P-2023-08-007 Approval to publish CCSDS 734.1-B-1 Cor. 1, Technical Corrigendum  to CCSDS 734.1-B-1, Issued May 2015

These polls can be accessed via the following link:

https://cwe.ccsds.org/fm/Lists/CESGPollQuestion/open.aspx

The closure date for these polls is 14 September 2023

NOTE TO CC RECIPIENTS:  Only Area Directors and Deputy Area Directors vote on CESG polls.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: CESG Poll Closure.ics
Type: text/calendar
Size: 2308 bytes
Desc: not available
URL: <http://mailman.ccsds.org/pipermail/cesg/attachments/20230831/3f29caf0/attachment.ics>

