[Cesg-all] Results of CESG Polls closing 8 June 2018

[CCSDS Secretariat]

CESG E-Poll Identifier: CESG-P-2018-05-007 Approval to release CCSDS 
123.0-P-1.1, Low-Complexity Lossless and Near-Lossless Multispectral 
and Hyperspectral Image Compression (Proposed Pink Book, Issue 1.1) 
for CCSDS Agency review
Results of CESG poll beginning 24 May 2018 and ending 8 June 2018:

                  Abstain:  2 (33.33%) (Merri, Behal)
  Approve Unconditionally:  4 (66.67%) (Barkley, Burleigh, Moury, Wilmot)
  Approve with Conditions:  0 (0%)
  Disapprove with Comment:  0 (0%)

Total Respondents: 6
No response was received from the following Area(s):

SEA

SECRETARIAT INTERPRETATION OF RESULTS:  Approved Unconditionally
PROPOSED SECRETARIAT ACTION:            Generate CMC poll

* * * * * * * * * * * * * * * * * * * * * * * *

CESG E-Poll Identifier: CESG-P-2018-05-008 Approval to release CCSDS 
142.0-R-1, Optical Communications Coding and Synchronization (Red 
Book, Issue 1) for CCSDS Agency review
Results of CESG poll beginning 24 May 2018 and ending 8 June 2018:

                  Abstain:  2 (33.33%) (Merri, Behal)
  Approve Unconditionally:  4 (66.67%) (Barkley, Burleigh, Moury, Wilmot)
  Approve with Conditions:  0 (0%)
  Disapprove with Comment:  0 (0%)

Total Respondents: 6
No response was received from the following Area(s):

SEA

SECRETARIAT INTERPRETATION OF RESULTS:  Approved Unconditionally
PROPOSED SECRETARIAT ACTION:            Generate CMC poll

* * * * * * * * * * * * * * * * * * * * * * * *

CESG E-Poll Identifier: CESG-P-2018-05-009 Approval to publish CCSDS 
A13.1-Y-1, CCSDS Recommended Procedures for Cloud-Based 
Interoperability Testing (Yellow Book, Issue 1)
Results of CESG poll beginning 24 May 2018 and ending 8 June 2018:

                  Abstain:  0 (0%)
  Approve Unconditionally:  6 (100%) (Barkley, Merri, Behal, 
Burleigh, Moury, Wilmot)
  Approve with Conditions:  0 (0%)
  Disapprove with Comment:  0 (0%)

Total Respondents: 6
No response was received from the following Area(s):

SEA

SECRETARIAT INTERPRETATION OF RESULTS:  Approved Unconditionally
PROPOSED SECRETARIAT ACTION:            Generate CMC poll

* * * * * * * * * * * * * * * * * * * * * * * *

CESG E-Poll Identifier: CESG-P-2018-05-010 Approval to publish CCSDS 
870.10-Y-1, MO Services and SOIS Electronic Datasheets (Yellow Book, Issue 1)
Results of CESG poll beginning 24 May 2018 and ending 8 June 2018:

                  Abstain:  1 (16.67%) (Calzolari)
  Approve Unconditionally:  3 (50%) (Barkley, Burleigh, Wilmot)
  Approve with Conditions:  2 (33.33%) (Merri, Behal)
  Disapprove with Comment:  0 (0%)

CONDITIONS/COMMENTS:

Mario Merri (Approve with Conditions): We have re-introduced some 
comments, where they were not implemented.

Main problem:

The real overlap between MO and SOIS is at "application layer" 
on-board. A good scenario to discuss the relationship between MO and 
SOIS should be a device exposed onboard as MO service and consumed by 
other MO services on-board and on the ground.

The document is instead so convoluted that it does not make this 
overlap clear and does not propose a clear solution, roadmap, approach, ...

In all examples, discussions MO is on the ground and SOIS on-board. 
Only in the last part of the document in analysis part, possible 
approaches are provided.

Proposal:

It is not good enough to be able to translate from EDS to MAL, etc. 
CCSDS should define a clean architecture that avoids overlaps of 
different standards.

Option 1. SOIS EDS shall be limited to low-level HW interfaces 
description and shall explicitly avoid application layer api 
specification. SOIS specification shall explicitly point to MO for 
application level interface specification. The MO services on board, 
should at the other side use SOIS services at implementation time. MO 
Specs shall make reference to SOIS for this purpose.

Option 2. Merge MAL and EDS (more complex): MAL shall become an 
integrated part of EDS for API/Applicaiton level Service 
specification for APIs. This means the EDS section that defines the 
application layer interface to a hardware device shall natively use 
MAL keywords.

We do not see the purpose and the usefulness of publishing this 
document as it is today. What is its intended use and which problem 
does it solve?

Please take note that we have collected detailed comments in the 
attached annotated pdf.

Bigette Behal (Approve with Conditions): See MOIMS AD State conditions


Total Respondents: 6
No response was received from the following Area(s):

SEA

SECRETARIAT INTERPRETATION OF RESULTS:  Approved with Conditions
PROPOSED SECRETARIAT ACTION:            Generate CMC poll after 
conditions have been addressed

* * * * * * * * * * * * * * * * * * * * * * * *