<span style=" font-size:10pt;font-family:sans-serif">Fully agreed, Jonathan.</span>
<br><span style=" font-size:10pt;font-family:sans-serif">Let's focus on
it at CESG level and eventually we can involve WGs.</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Regards</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Gian Paolo</span>
<br>
<br>
<br>
<br>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">From:
</span><span style=" font-size:9pt;font-family:sans-serif">"Wilmot,
Jonathan J. (GSFC-5820)" <jonathan.j.wilmot@nasa.gov></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">To:
</span><span style=" font-size:9pt;font-family:sans-serif">"Gian.Paolo.Calzolari@esa.int"
<Gian.Paolo.Calzolari@esa.int></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Cc:
</span><span style=" font-size:9pt;font-family:sans-serif">"CCSDS
Engineering Steering Group - CESG Exec" <cesg@mailman.ccsds.org>,
"CESG" <cesg-bounces@mailman.ccsds.org>, "Kazz, Greg
J (JPL-312B)[Jet Propulsion Laboratory]" <greg.j.kazz@jpl.nasa.gov>,
"Andrews, Kenneth S (JPL-332B)[Jet Propulsion Laboratory]" <kenneth.s.andrews@jpl.nasa.gov>,
"Margherita.di.Giulio@esa.int" <Margherita.di.Giulio@esa.int>,
"Massimo.Bertinelli@esa.int" <Massimo.Bertinelli@esa.int>,
"Shames, Peter M (JPL-312B)[Jet Propulsion Laboratory]" <peter.m.shames@jpl.nasa.gov>,
"Tom Gannett" <thomas.gannett@tgannett.net></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Date:
</span><span style=" font-size:9pt;font-family:sans-serif">05-02-20
16:21</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Subject:
</span><span style=" font-size:9pt;font-family:sans-serif">RE:
[CESG] SOIS Comment on MIB configuration data: [EXTERNAL] Fw: SLS reply
to SEA Conditions on Poll CESG-P-2019-12-002 Approval to release CCSDS
131.3-P-1.1, CCSDS Space Link Protocols over ETSI DVB-S2 Standard (Pink
Sheets, Issue 1.1) for CCSDS Agen...</span>
<br>
<hr noshade>
<br>
<br>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">Gian
Paolo,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">
Agreed. I withdraw my poll conditions, but it is also
important to continue the discussion on policy. It is my belief that the
standards are less interoperable if there are no common operational interfaces.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">
Kind regards,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">
Jonathan</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">Jonathan
Wilmot</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">NASA/GSFC
Code 580</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">cFS
Software Architect</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">CCSDS
SOIS Area Director</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">301-286-2623</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"><b>From:</b>
Gian.Paolo.Calzolari@esa.int <Gian.Paolo.Calzolari@esa.int> <b><br>
Sent:</b> Wednesday, February 5, 2020 10:06 AM<b><br>
To:</b> Wilmot, Jonathan J. (GSFC-5820) <jonathan.j.wilmot@nasa.gov><b><br>
Cc:</b> CCSDS Engineering Steering Group - CESG Exec <cesg@mailman.ccsds.org>;
CESG <cesg-bounces@mailman.ccsds.org>; Kazz, Greg J (JPL-312B)[Jet
Propulsion Laboratory] <greg.j.kazz@jpl.nasa.gov>; Andrews, Kenneth
S (JPL-332B)[Jet Propulsion Laboratory] <kenneth.s.andrews@jpl.nasa.gov>;
Margherita.di.Giulio@esa.int; Massimo.Bertinelli@esa.int; Shames, Peter
M (JPL-312B)[Jet Propulsion Laboratory] <peter.m.shames@jpl.nasa.gov>;
Tom Gannett <thomas.gannett@tgannett.net><b><br>
Subject:</b> RE: [CESG] SOIS Comment on MIB configuration data: [EXTERNAL]
Fw: SLS reply to SEA Conditions on Poll CESG-P-2019-12-002 Approval to
release CCSDS 131.3-P-1.1, CCSDS Space Link Protocols over ETSI DVB-S2
Standard (Pink Sheets, Issue 1.1) for CCSDS Agen...</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Times New Roman"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Arial">Jonathan,</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><br>
we will tackle general modifications to CCSDS
books (if necessary) after a CESG policy is finally agreed.</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><br>
Regards</span><span style=" font-size:12pt;font-family:Times New Roman">
<br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
Gian Paolo</span><span style=" font-size:12pt;font-family:Times New Roman">
<br>
<br>
<br>
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
From: </span><span style=" font-size:9pt;font-family:Arial">"Wilmot,
Jonathan J. (GSFC-5820)" <</span><a href=mailto:jonathan.j.wilmot@nasa.gov><span style=" font-size:9pt;color:blue;font-family:Arial"><u>jonathan.j.wilmot@nasa.gov</u></span></a><span style=" font-size:9pt;font-family:Arial">></span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
To: </span><span style=" font-size:9pt;font-family:Arial">"</span><a href=mailto:Margherita.di.Giulio@esa.int><span style=" font-size:9pt;color:blue;font-family:Arial"><u>Margherita.di.Giulio@esa.int</u></span></a><span style=" font-size:9pt;font-family:Arial">"
<</span><a href=mailto:Margherita.di.Giulio@esa.int><span style=" font-size:9pt;color:blue;font-family:Arial"><u>Margherita.di.Giulio@esa.int</u></span></a><span style=" font-size:9pt;font-family:Arial">>,
"Shames, Peter M (JPL-312B)[Jet Propulsion Laboratory]" <</span><a href=mailto:peter.m.shames@jpl.nasa.gov><span style=" font-size:9pt;color:blue;font-family:Arial"><u>peter.m.shames@jpl.nasa.gov</u></span></a><span style=" font-size:9pt;font-family:Arial">></span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
Cc: </span><span style=" font-size:9pt;font-family:Arial">"CCSDS
Engineering Steering Group - CESG Exec" <</span><a href=mailto:cesg@mailman.ccsds.org><span style=" font-size:9pt;color:blue;font-family:Arial"><u>cesg@mailman.ccsds.org</u></span></a><span style=" font-size:9pt;font-family:Arial">>,
"CESG" <</span><a href="mailto:cesg-bounces@mailman.ccsds.org"><span style=" font-size:9pt;color:blue;font-family:Arial"><u>cesg-bounces@mailman.ccsds.org</u></span></a><span style=" font-size:9pt;font-family:Arial">>,
"</span><a href=mailto:Gian.Paolo.Calzolari@esa.int><span style=" font-size:9pt;color:blue;font-family:Arial"><u>Gian.Paolo.Calzolari@esa.int</u></span></a><span style=" font-size:9pt;font-family:Arial">"
<</span><a href=mailto:Gian.Paolo.Calzolari@esa.int><span style=" font-size:9pt;color:blue;font-family:Arial"><u>Gian.Paolo.Calzolari@esa.int</u></span></a><span style=" font-size:9pt;font-family:Arial">>,
"Kazz, Greg J (JPL-312B)[Jet Propulsion Laboratory]" <</span><a href=mailto:greg.j.kazz@jpl.nasa.gov><span style=" font-size:9pt;color:blue;font-family:Arial"><u>greg.j.kazz@jpl.nasa.gov</u></span></a><span style=" font-size:9pt;font-family:Arial">>,
"Andrews, Kenneth S (JPL-332B)[Jet Propulsion Laboratory]" <</span><a href=mailto:kenneth.s.andrews@jpl.nasa.gov><span style=" font-size:9pt;color:blue;font-family:Arial"><u>kenneth.s.andrews@jpl.nasa.gov</u></span></a><span style=" font-size:9pt;font-family:Arial">>,
"</span><a href=mailto:Massimo.Bertinelli@esa.int><span style=" font-size:9pt;color:blue;font-family:Arial"><u>Massimo.Bertinelli@esa.int</u></span></a><span style=" font-size:9pt;font-family:Arial">"
<</span><a href=mailto:Massimo.Bertinelli@esa.int><span style=" font-size:9pt;color:blue;font-family:Arial"><u>Massimo.Bertinelli@esa.int</u></span></a><span style=" font-size:9pt;font-family:Arial">>,
"Tom Gannett" <</span><a href=mailto:thomas.gannett@tgannett.net><span style=" font-size:9pt;color:blue;font-family:Arial"><u>thomas.gannett@tgannett.net</u></span></a><span style=" font-size:9pt;font-family:Arial">></span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
Date: </span><span style=" font-size:9pt;font-family:Arial">04-02-20
16:56</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
Subject: </span><span style=" font-size:9pt;font-family:Arial">RE:
[CESG] SOIS Comment on MIB configuration data: [EXTERNAL] Fw: SLS reply
to SEA Conditions on Poll CESG-P-2019-12-002 Approval to release CCSDS
131.3-P-1.1, CCSDS Space Link Protocols over ETSI DVB-S2 Standard (Pink
Sheets, Issue 1.1) for CCSDS Agen...</span><span style=" font-size:12pt;font-family:Times New Roman">
</span></p>
<div align=center>
<hr noshade></div>
<p style="margin-top:0px;margin-Bottom:240px"><span style=" font-size:12pt;font-family:Times New Roman"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">Margherita,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">
Thank you. I agree with the plan. In the near term I think
it still makes sense to at least have unambiguous names for MIB terms in
the Blue books. The issue of data types we could leave for future discussion.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">For
example: instead of the MIB term “Transmission mode” the CCSDS SPACE
LINK PROTOCOLS OVER ETSI DVB-S2 Blue Book should use the term “DVB_S2_TransmissionMode”.
This is a minor update but allows the term to be unambiguously named in
SANA without having to change the Blue Book.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">
Kind regards,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">
Jonathan</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">Jonathan
Wilmot</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">NASA/GSFC
Code 582</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">cFS
Software Architect</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">CCSDS
SOIS Area Director</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">301-286-2623</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"><b>From:</b>
</span><a href=mailto:Margherita.di.Giulio@esa.int><span style=" font-size:11pt;color:blue;font-family:Calibri"><u>Margherita.di.Giulio@esa.int</u></span></a><span style=" font-size:11pt;font-family:Calibri">
<</span><a href=mailto:Margherita.di.Giulio@esa.int><span style=" font-size:11pt;color:blue;font-family:Calibri"><u>Margherita.di.Giulio@esa.int</u></span></a><span style=" font-size:11pt;font-family:Calibri">>
<b><br>
Sent:</b> Tuesday, February 4, 2020 10:08 AM<b><br>
To:</b> Shames, Peter M (JPL-312B)[Jet Propulsion Laboratory] <</span><a href=mailto:peter.m.shames@jpl.nasa.gov><span style=" font-size:11pt;color:blue;font-family:Calibri"><u>peter.m.shames@jpl.nasa.gov</u></span></a><span style=" font-size:11pt;font-family:Calibri">><b><br>
Cc:</b> CCSDS Engineering Steering Group - CESG Exec <</span><a href=mailto:cesg@mailman.ccsds.org><span style=" font-size:11pt;color:blue;font-family:Calibri"><u>cesg@mailman.ccsds.org</u></span></a><span style=" font-size:11pt;font-family:Calibri">>;
CESG <</span><a href="mailto:cesg-bounces@mailman.ccsds.org"><span style=" font-size:11pt;color:blue;font-family:Calibri"><u>cesg-bounces@mailman.ccsds.org</u></span></a><span style=" font-size:11pt;font-family:Calibri">>;
</span><a href=mailto:Gian.Paolo.Calzolari@esa.int><span style=" font-size:11pt;color:blue;font-family:Calibri"><u>Gian.Paolo.Calzolari@esa.int</u></span></a><span style=" font-size:11pt;font-family:Calibri">;
Kazz, Greg J (JPL-312B)[Jet Propulsion Laboratory] <</span><a href=mailto:greg.j.kazz@jpl.nasa.gov><span style=" font-size:11pt;color:blue;font-family:Calibri"><u>greg.j.kazz@jpl.nasa.gov</u></span></a><span style=" font-size:11pt;font-family:Calibri">>;
Wilmot, Jonathan J. (GSFC-5820) <</span><a href=mailto:jonathan.j.wilmot@nasa.gov><span style=" font-size:11pt;color:blue;font-family:Calibri"><u>jonathan.j.wilmot@nasa.gov</u></span></a><span style=" font-size:11pt;font-family:Calibri">>;
Andrews, Kenneth S (JPL-332B)[Jet Propulsion Laboratory] <</span><a href=mailto:kenneth.s.andrews@jpl.nasa.gov><span style=" font-size:11pt;color:blue;font-family:Calibri"><u>kenneth.s.andrews@jpl.nasa.gov</u></span></a><span style=" font-size:11pt;font-family:Calibri">>;
</span><a href=mailto:Massimo.Bertinelli@esa.int><span style=" font-size:11pt;color:blue;font-family:Calibri"><u>Massimo.Bertinelli@esa.int</u></span></a><span style=" font-size:11pt;font-family:Calibri">;
Tom Gannett <</span><a href=mailto:thomas.gannett@tgannett.net><span style=" font-size:11pt;color:blue;font-family:Calibri"><u>thomas.gannett@tgannett.net</u></span></a><span style=" font-size:11pt;font-family:Calibri">><b><br>
Subject:</b> Re: [CESG] SOIS Comment on MIB configuration data: [EXTERNAL]
Fw: SLS reply to SEA Conditions on Poll CESG-P-2019-12-002 Approval to
release CCSDS 131.3-P-1.1, CCSDS Space Link Protocols over ETSI DVB-S2
Standard (Pink Sheets, Issue 1.1) for CCSDS Agen...</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Times New Roman"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Arial">Dear
All,</span><span style=" font-size:12pt;font-family:Times New Roman"> </span><span style=" font-size:10pt;font-family:Arial"><br>
having seen the thread of discussions, I’d like to recall that there
is (or should be) an ongoing activity about the assessment of commonality
of data representation between Recommendations belonging to different CCSDS
domains. <br>
At the CESG Meeting in Mountain View we noted the following:</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><i><br>
“Management Information Base: different domains may have similar needs
to represent the information that they manage. There is , possibly,
an intersection between the Management Information Bases Electronic
Data Sheets (EDS: SOIS), the Functional Resource model (FR: CSS), and network
management concerns (SIS). This topic to be further explored by joint meetings
by involved Areas “</i></span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><br>
At the CESG Meeting in Darmstadt, Jonathan presented a couple of slides
(Title: “Operational Interfaces for On-Board Service Management, Protocol
Management Information Base (MIB)) which only introduced the topic. So,
this matter still needs to be actually tackled. <br>
The MoM of the Darmstadt meeting records the following action(s) :</span><span style=" font-size:12pt;font-family:Times New Roman">
</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Arial"><i>-
<b>AI/S19-1 JW : </i></b><i>JW to produce a
short presentation to introduce the notion of MIB, data formats (template)
, commonality and possible relationship to other Areas.</i></span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><i><br>
- <b>Status: </i></b><i>Not much progress since
the CESG Telecon. Some discussion took place during the Technical Meeting.
This action is closed, but a new AI is issued:</i></span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><i><br>
- New<b> AI </i></b><i>: J.Wilmot: to
call a Telecon involving SOIS, SIS, CSS to assess data representation
aspects (e.g. MIB) in different CCSDS domains and brainstorm about commonalities.
Outcome to be presented at CESG Mid-term Telecon.</i></span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><br>
<br>
I think we shall keep pursuing the definition of a CCSDS “formalism”
for data representation.</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><br>
With respect to Jonathan’s comments to the CESG Poll about “SLP
over ETSI DVB-S2 Standard” I think that only once the formalism has been
established it will make sense to request that CCSDS Recommendation,
which containing MIB or configuration data, shall stick to it <br>
Finally, I'd like to ask Jonathan to let us have an update at the upcoming
CESG Telecon.</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><br>
Kind regards,<br>
Margherita</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><br>
<br>
--------------------------------------------------------------</span><span style=" font-size:8pt;color:#00a1e0;font-family:Verdana"><b><br>
Margherita di Giulio</b></span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:8pt;color:#5f5f5f;font-family:Verdana"><br>
Ground Station Systems Division</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:8pt;color:#5f5f5f;font-family:Verdana"><br>
Backend Software Section (OPS-GSB)</span><span style=" font-size:12pt;font-family:Times New Roman">
<br>
</span><span style=" font-size:8pt;color:#5f5f5f;font-family:Verdana"><b><br>
<br>
European Space Agency ESA/ESOC</b><br>
Robert-Bosch-Str. 5<br>
D-64293 Darmstadt - Germany<br>
Tel: +49-6151-902779<br>
e-mail: </span><a href=mailto:Margherita.di.Giulio@esa.int><span style=" font-size:8pt;color:blue;font-family:Verdana"><u>Margherita.di.Giulio@esa.int</u></span></a><span style=" font-size:12pt;font-family:Times New Roman"><br>
<br>
<br>
<br>
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
<br>
From: </span><span style=" font-size:9pt;font-family:Arial">"Shames,
Peter M\(US 312B\) via CESG" <</span><a href=mailto:cesg@mailman.ccsds.org><span style=" font-size:9pt;color:blue;font-family:Arial"><u>cesg@mailman.ccsds.org</u></span></a><span style=" font-size:9pt;font-family:Arial">></span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
To: </span><span style=" font-size:9pt;font-family:Arial">"</span><a href=mailto:Gian.Paolo.Calzolari@esa.int><span style=" font-size:9pt;color:blue;font-family:Arial"><u>Gian.Paolo.Calzolari@esa.int</u></span></a><span style=" font-size:9pt;font-family:Arial">"
<</span><a href=mailto:Gian.Paolo.Calzolari@esa.int><span style=" font-size:9pt;color:blue;font-family:Arial"><u>Gian.Paolo.Calzolari@esa.int</u></span></a><span style=" font-size:9pt;font-family:Arial">>,
"Wilmot, Jonathan J. (GSFC-5820)" <</span><a href=mailto:jonathan.j.wilmot@nasa.gov><span style=" font-size:9pt;color:blue;font-family:Arial"><u>jonathan.j.wilmot@nasa.gov</u></span></a><span style=" font-size:9pt;font-family:Arial">></span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
Cc: </span><span style=" font-size:9pt;font-family:Arial">"CCSDS
Engineering Steering Group - CESG Exec" <</span><a href=mailto:cesg@mailman.ccsds.org><span style=" font-size:9pt;color:blue;font-family:Arial"><u>cesg@mailman.ccsds.org</u></span></a><span style=" font-size:9pt;font-family:Arial">>,
"Kazz, Greg J\(US 312B\)" <</span><a href=mailto:greg.j.kazz@jpl.nasa.gov><span style=" font-size:9pt;color:blue;font-family:Arial"><u>greg.j.kazz@jpl.nasa.gov</u></span></a><span style=" font-size:9pt;font-family:Arial">>,
"Tom Gannett" <</span><a href=mailto:thomas.gannett@tgannett.net><span style=" font-size:9pt;color:blue;font-family:Arial"><u>thomas.gannett@tgannett.net</u></span></a><span style=" font-size:9pt;font-family:Arial">>,
"</span><a href=mailto:Massimo.Bertinelli@esa.int><span style=" font-size:9pt;color:blue;font-family:Arial"><u>Massimo.Bertinelli@esa.int</u></span></a><span style=" font-size:9pt;font-family:Arial">"
<</span><a href=mailto:Massimo.Bertinelli@esa.int><span style=" font-size:9pt;color:blue;font-family:Arial"><u>Massimo.Bertinelli@esa.int</u></span></a><span style=" font-size:9pt;font-family:Arial">>,
"Andrews, Kenneth S\(US 332B\)" <</span><a href=mailto:kenneth.s.andrews@jpl.nasa.gov><span style=" font-size:9pt;color:blue;font-family:Arial"><u>kenneth.s.andrews@jpl.nasa.gov</u></span></a><span style=" font-size:9pt;font-family:Arial">></span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
Date: </span><span style=" font-size:9pt;font-family:Arial">03/02/2020
21:33</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
Subject: </span><span style=" font-size:9pt;font-family:Arial">Re:
[CESG] SOIS Comment on MIB configuration data: [EXTERNAL] Fw: SLS reply
to SEA Conditions on Poll CESG-P-2019-12-002 Approval to release CCSDS
131.3-P-1.1, CCSDS Space Link Protocols over ETSI DVB-S2 Standard (Pink
Sheets, Issue 1.1) for CCSDS Agency review</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
Sent by: </span><span style=" font-size:9pt;font-family:Arial">"CESG"
<</span><a href="mailto:cesg-bounces@mailman.ccsds.org"><span style=" font-size:9pt;color:blue;font-family:Arial"><u>cesg-bounces@mailman.ccsds.org</u></span></a><span style=" font-size:9pt;font-family:Arial">></span><span style=" font-size:12pt;font-family:Times New Roman">
</span></p>
<div align=center>
<hr noshade></div>
<p style="h 4^ 4.Å;margin-Bottom:3600px"><span style=" font-size:12pt;font-family:Times New Roman"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Hi
Gippo and Jonathan,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">It
may come as no surprise that I think both of you are "right"
in some sense, but that the best path may lie in the middle of the two
positions that you have staked out.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">I
think Gippo is "right" in that in most of our specs where we
have MIB specified we do not tend to make it be a formalized part of the
spec.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">I
think that Jonathan is "right" in that some added formality would
make these MIB values be more easily interpreted and exchanged for interoperability.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Times New Roman"><br>
Where I differ from Gippo is that I think you could add more clarity in
how the MIB and its fields are defined without straying into the "this
is how you implement it" territory. In fact, just using those
Tables 5-1 and 5-2 as examples, the only way to read that is that "transfer
frame length" is an integer with a range and that CRC is an enumerated
list that references specified, documented, algorithms. In the case
of Table 5-2 it is even clearer that Transmission Mode is an enumerated
list, Baseband pulse shaping is a float, and that scrambling code, and
other fields, are integers. That is what they state, either explicitly,
i.e. "List of integers", or implicitly, i.e. fractional numbers
with a decimal point. Specifying these as a data type and value range
pair instead of the ambiguous "allowed values" is not implementation,
just clarity. <br>
Where I differ from Jonathan is that some of the interface detail specificity
that is possible with the EDS and DoT may be overkill for this purpose,
which is not necessarily thought of as an "interface". It
may, as is pointed out in many specs that include a "MIB", just
be a list of the kinds of parameters that implementations may choose to
put into a table, or embed in code, in their implementations. From
the PoV of the standard these may be treated as "implementation concerns".
That means that there is not any "thou shall" language
about how to implement them. But that doesn't mean that they aren't
important, nor does it mean that treating them a little more formally wouldn't
be a good thing. <br>
From the PoV of our users I will assert that knowing just exactly which
choices were made during the implementation of programs that are intended
to interoperate is essential. It may not be a concern HOW they are
implemented, that is an implementation choice, but it certainly matters
THAT they are implemented and which options are available. This is
something that could well be handled in a fully specified PICS that fills
out the PICS pro forma for two (or more) imp[lementations. But that,
I will assert, would be made more simple if all of the data types and values
that might appear in a MIB were clearly identified, and in a way where
they are easy to document. Use of the EDS / DoT is a documented method
for doing this, but so is use of the PICS pro forma, as long as the data
type and value ranges that are possible are clearly specified along with
the options that are actually implemented, <br>
I think a little more clarity in the specs that include MIBs would be a
benefit to everyone. <br>
Cheers, Peter <br>
</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Calibri"><b>From:
</b>Gian Paolo Calzolari <</span><a href=mailto:Gian.Paolo.Calzolari@esa.int><span style=" font-size:12pt;color:blue;font-family:Calibri"><u>Gian.Paolo.Calzolari@esa.int</u></span></a><span style=" font-size:12pt;font-family:Calibri">><b><br>
Date: </b>Monday, February 3, 2020 at 5:38 AM<b><br>
To: </b>"Wilmot, Jonathan J. (GSFC-5820)" <</span><a href=mailto:jonathan.j.wilmot@nasa.gov><span style=" font-size:12pt;color:blue;font-family:Calibri"><u>jonathan.j.wilmot@nasa.gov</u></span></a><span style=" font-size:12pt;font-family:Calibri">><b><br>
Cc: </b>Gilles Moury <</span><a href=mailto:Gilles.Moury@cnes.fr><span style=" font-size:12pt;color:blue;font-family:Calibri"><u>Gilles.Moury@cnes.fr</u></span></a><span style=" font-size:12pt;font-family:Calibri">>,
Kenneth Andrews <</span><a href=mailto:kenneth.s.andrews@jpl.nasa.gov><span style=" font-size:12pt;color:blue;font-family:Calibri"><u>kenneth.s.andrews@jpl.nasa.gov</u></span></a><span style=" font-size:12pt;font-family:Calibri">>,
"</span><a href=mailto:Massimo.Bertinelli@esa.int><span style=" font-size:12pt;color:blue;font-family:Calibri"><u>Massimo.Bertinelli@esa.int</u></span></a><span style=" font-size:12pt;font-family:Calibri">"
<</span><a href=mailto:Massimo.Bertinelli@esa.int><span style=" font-size:12pt;color:blue;font-family:Calibri"><u>Massimo.Bertinelli@esa.int</u></span></a><span style=" font-size:12pt;font-family:Calibri">>,
Peter Shames <</span><a href=mailto:peter.m.shames@jpl.nasa.gov><span style=" font-size:12pt;color:blue;font-family:Calibri"><u>peter.m.shames@jpl.nasa.gov</u></span></a><span style=" font-size:12pt;font-family:Calibri">>,
Tom Gannett <</span><a href=mailto:thomas.gannett@tgannett.net><span style=" font-size:12pt;color:blue;font-family:Calibri"><u>thomas.gannett@tgannett.net</u></span></a><span style=" font-size:12pt;font-family:Calibri">>,
Greg Kazz <</span><a href=mailto:greg.j.kazz@jpl.nasa.gov><span style=" font-size:12pt;color:blue;font-family:Calibri"><u>greg.j.kazz@jpl.nasa.gov</u></span></a><span style=" font-size:12pt;font-family:Calibri">><b><br>
Subject: </b>SOIS Comment on MIB configuration data: [EXTERNAL] Fw: SLS
reply to SEA Conditions on Poll CESG-P-2019-12-002 Approval to release
CCSDS 131.3-P-1.1, CCSDS Space Link Protocols over ETSI DVB-S2 Standard
(Pink Sheets, Issue 1.1) for CCSDS Agency review</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Arial">Jonathan,</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:10pt;font-family:Arial"><br>
first of all, it is our understating that the specific
comment addressed by this discussion is a comment and not a condition.</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:10pt;font-family:Arial"><br>
Can you please confirm?</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:10pt;font-family:Arial"><br>
<br>
For the remaining part of this e-mail I include in cc also Greg as you
expressed similar comments for SLP documents.</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:10pt;font-family:Arial"><br>
<br>
You are talking about the "</span><span style=" font-size:11pt;color:#004080;font-family:Calibri">formality
of protocol MIB definitions</span><span style=" font-size:10pt;font-family:Arial">"
and in your attached file you actually start from the tables in CCSDS 131.3-P-1.0
Chapter 5 adding two columns.</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:10pt;font-family:Arial"><br>
Actually the column "Units" is not really an addition as the
column "Allowed Values" in the book actuary covers your two columns
Units and Range.</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:10pt;font-family:Arial"><br>
The real addition is column "Data Type" that is really computer
oriented; i.e. an implementation detail IMO.</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:10pt;font-family:Arial"><br>
However section APPLICABILITY for this book (and for most of the SLS Area
books) clearly states that "</span><span style=" font-size:10pt;color:red;font-family:Arial">The
Recommended Standard includes comprehensive specification
of the services and protocol for inter-Agency
cross support. It is neither a specification of, nor a design for,
real systems that may be implemented for existing or future missions.</span><span style=" font-size:10pt;font-family:Arial">"
giving a full justification for the way Managed Parameters are presented.</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:10pt;font-family:Arial"><br>
<br>
The details you are asking are really pointing to the implementation and
also depend on the way the real system is implemented (e.g. an hardware
encoder on board could use different programming languages and characteristics
with respect to an on ground decoder running over sophisticated software).</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:10pt;font-family:Arial"><br>
Even sympathising with the fact that "</span><span style=" font-size:11pt;color:#004080;font-family:Calibri">missions
could exchange the MIB configuration data</span><span style=" font-size:10pt;font-family:Arial">",
I find this is not pertinent for these SLS Books but it rather represents
something that should be addressed by other standards as e.g. your Electronic
Data Sheets or the exchange of Service Management Data or the CSTS Functional
Resource Model.</span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:10pt;font-family:Arial"><br>
<br>
Best regards</span><span style=" font-size:11pt;font-family:Calibri"> </span><span style=" font-size:10pt;font-family:Arial"><br>
<br>
Gian Paolo</span><span style=" font-size:11pt;font-family:Calibri"> <br>
<br>
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
<br>
<br>
From: </span><span style=" font-size:9pt;font-family:Arial">"Wilmot,
Jonathan J. (GSFC-5820)" <</span><a href=mailto:jonathan.j.wilmot@nasa.gov><span style=" font-size:9pt;color:blue;font-family:Arial"><u>jonathan.j.wilmot@nasa.gov</u></span></a><span style=" font-size:9pt;font-family:Arial">></span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
To: </span><span style=" font-size:9pt;font-family:Arial">"</span><a href=mailto:Gian.Paolo.Calzolari@esa.int><span style=" font-size:9pt;color:blue;font-family:Arial"><u>Gian.Paolo.Calzolari@esa.int</u></span></a><span style=" font-size:9pt;font-family:Arial">"
<</span><a href=mailto:Gian.Paolo.Calzolari@esa.int><span style=" font-size:9pt;color:blue;font-family:Arial"><u>Gian.Paolo.Calzolari@esa.int</u></span></a><span style=" font-size:9pt;font-family:Arial">></span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
Cc: </span><span style=" font-size:9pt;font-family:Arial">"</span><a href=mailto:Massimo.Bertinelli@esa.int><span style=" font-size:9pt;color:blue;font-family:Arial"><u>Massimo.Bertinelli@esa.int</u></span></a><span style=" font-size:9pt;font-family:Arial">"
<</span><a href=mailto:Massimo.Bertinelli@esa.int><span style=" font-size:9pt;color:blue;font-family:Arial"><u>Massimo.Bertinelli@esa.int</u></span></a><span style=" font-size:9pt;font-family:Arial">>,
"Gilles Moury" <</span><a href=mailto:Gilles.Moury@cnes.fr><span style=" font-size:9pt;color:blue;font-family:Arial"><u>Gilles.Moury@cnes.fr</u></span></a><span style=" font-size:9pt;font-family:Arial">>,
"Andrews, Kenneth S (JPL-332B)[Jet Propulsion Laboratory]" <</span><a href=mailto:kenneth.s.andrews@jpl.nasa.gov><span style=" font-size:9pt;color:blue;font-family:Arial"><u>kenneth.s.andrews@jpl.nasa.gov</u></span></a><span style=" font-size:9pt;font-family:Arial">>,
"Tom Gannett" <</span><a href=mailto:thomas.gannett@tgannett.net><span style=" font-size:9pt;color:blue;font-family:Arial"><u>thomas.gannett@tgannett.net</u></span></a><span style=" font-size:9pt;font-family:Arial">>,
"Shames, Peter M (JPL-312B)[Jet Propulsion Laboratory]" <</span><a href=mailto:peter.m.shames@jpl.nasa.gov><span style=" font-size:9pt;color:blue;font-family:Arial"><u>peter.m.shames@jpl.nasa.gov</u></span></a><span style=" font-size:9pt;font-family:Arial">></span><span style=" font-size:11pt;font-family:Calibri">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
Date: </span><span style=" font-size:9pt;font-family:Arial">31-01-20
20:46</span><span style=" font-size:11pt;font-family:Calibri"> </span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
Subject: </span><span style=" font-size:9pt;font-family:Arial">RE:
[EXTERNAL] Fw: SLS reply to SEA Conditions on Poll CESG-P-2019-12-002 Approval
to release CCSDS 131.3-P-1.1, CCSDS Space Link Protocols over ETSI DVB-S2
Standard (Pink Sheets, Issue 1.1) for CCSDS Agency review</span><span style=" font-size:11pt;font-family:Calibri">
</span></p>
<div align=center>
<hr noshade></div>
<p style="h 4^ 4.Å;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Arial">Gian
Paolo</span><span style=" font-size:12pt;color:#004080;font-family:Times New Roman">,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#004080;font-family:Times New Roman"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#004080;font-family:Times New Roman">
I think we should have a broader discussion on the issues with this
topic of operational interoperability. Maybe bring it up at the next
CESG telecon. CCSDS has been inconsistent with the formality of protocol
MIB definitions. I am pushing to have MIB definitions be complete enough
with unique names such that a missions could exchange the MIB configuration
data. This way both ends of a protocol would operationally match. </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#004080;font-family:Times New Roman"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#004080;font-family:Times New Roman">Please
let me know if the attachment makes sense. </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#004080;font-family:Times New Roman"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#004080;font-family:Times New Roman"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#004080;font-family:Times New Roman">
Kind regards,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#004080;font-family:Times New Roman"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#004080;font-family:Times New Roman">
Jonathan</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#004080;font-family:Times New Roman"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#004080;font-family:Times New Roman">Jonathan
Wilmot</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#004080;font-family:Times New Roman">NASA/GSFC
Code 582</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#004080;font-family:Times New Roman">cFS
Software Architect</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#004080;font-family:Times New Roman">CCSDS
SOIS Area Director</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#004080;font-family:Times New Roman">301-286-2623</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#004080;font-family:Times New Roman"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#004080;font-family:Times New Roman"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#004080;font-family:Times New Roman"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Times New Roman"><b>From:</b>
</span><a href=mailto:Gian.Paolo.Calzolari@esa.int><span style=" font-size:12pt;color:blue;font-family:Times New Roman"><u>Gian.Paolo.Calzolari@esa.int</u></span></a><span style=" font-size:12pt;font-family:Times New Roman">
<</span><a href=mailto:Gian.Paolo.Calzolari@esa.int><span style=" font-size:12pt;color:blue;font-family:Times New Roman"><u>Gian.Paolo.Calzolari@esa.int</u></span></a><span style=" font-size:12pt;font-family:Times New Roman">>
<b><br>
Sent:</b> Tuesday, January 28, 2020 4:15 AM<b><br>
To:</b> Wilmot, Jonathan J. (GSFC-5820) <</span><a href=mailto:jonathan.j.wilmot@nasa.gov><span style=" font-size:12pt;color:blue;font-family:Times New Roman"><u>jonathan.j.wilmot@nasa.gov</u></span></a><span style=" font-size:12pt;font-family:Times New Roman">><b><br>
Cc:</b> </span><a href=mailto:Massimo.Bertinelli@esa.int><span style=" font-size:12pt;color:blue;font-family:Times New Roman"><u>Massimo.Bertinelli@esa.int</u></span></a><span style=" font-size:12pt;font-family:Times New Roman">;
Gilles Moury <</span><a href=mailto:Gilles.Moury@cnes.fr><span style=" font-size:12pt;color:blue;font-family:Times New Roman"><u>Gilles.Moury@cnes.fr</u></span></a><span style=" font-size:12pt;font-family:Times New Roman">>;
Andrews, Kenneth S (JPL-332B)[Jet Propulsion Laboratory] <</span><a href=mailto:kenneth.s.andrews@jpl.nasa.gov><span style=" font-size:12pt;color:blue;font-family:Times New Roman"><u>kenneth.s.andrews@jpl.nasa.gov</u></span></a><span style=" font-size:12pt;font-family:Times New Roman">>;
Tom Gannett <</span><a href=mailto:thomas.gannett@tgannett.net><span style=" font-size:12pt;color:blue;font-family:Times New Roman"><u>thomas.gannett@tgannett.net</u></span></a><span style=" font-size:12pt;font-family:Times New Roman">><b><br>
Subject:</b> [EXTERNAL] Fw: SLS reply to SEA Conditions on Poll CESG-P-2019-12-002
Approval to release CCSDS 131.3-P-1.1, CCSDS Space Link Protocols over
ETSI DVB-S2 Standard (Pink Sheets, Issue 1.1) for CCSDS Agency review</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Times New Roman"><br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
Jonathan,</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><br>
here attached the mail already sent to Peter etc.</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><br>
The requested work on the other books is already in progress (approved
projects) and there is no reason to defer the start of the Agency Review
for the Pink Sheets to 131.3-B for this.</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><br>
<br>
With respect to your specicif comment "</span><span style=" font-size:10pt;color:blue;font-family:Arial">It
should be an overall goal to provide for common operational interfaces
for Managed parameters published in CCSDS standards. To that end, more
specific common data types should be provided: signed/unsigned Integer,
Boolean, Enumerations (ON, OFF), (Short, Normal, Both) …, float, etc.
This would allow the exchange of MIB parameters based on common names and
types between organizations. The binary encoding of those MIBs could be
specified in CCSDS Electronics data sheets, or XTCE</span><span style=" font-size:10pt;font-family:Arial">."
can you please clarify what you want precisely and formulate it one or
more PIDs in the usual FROM/TO from?</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><br>
Otherwise there is no way to consider this comment.</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><br>
<br>
Best regards</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><br>
<br>
Gian Paolo</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:9pt;color:#800080;font-family:Arial"><br>
<br>
----- Forwarded by Gian Paolo Calzolari/esoc/ESA on 28-01-20 10:11 -----</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
<br>
From: </span><span style=" font-size:9pt;font-family:Arial">Gian
Paolo Calzolari/esoc/ESA</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
To: </span><span style=" font-size:9pt;font-family:Arial">"Shames,
Peter M \(312B\)" <</span><a href=mailto:peter.m.shames@jpl.nasa.gov><span style=" font-size:9pt;color:blue;font-family:Arial"><u>peter.m.shames@jpl.nasa.gov</u></span></a><span style=" font-size:9pt;font-family:Arial">></span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
Cc: </span><span style=" font-size:9pt;font-family:Arial">"Andrews,
Kenneth S \(332B\)" <</span><a href=mailto:Kenneth.S.Andrews@jpl.nasa.gov><span style=" font-size:9pt;color:blue;font-family:Arial"><u>Kenneth.S.Andrews@jpl.nasa.gov</u></span></a><span style=" font-size:9pt;font-family:Arial">>,
"Gilles Moury" <</span><a href=mailto:Gilles.Moury@cnes.fr><span style=" font-size:9pt;color:blue;font-family:Arial"><u>Gilles.Moury@cnes.fr</u></span></a><span style=" font-size:9pt;font-family:Arial">>,
Massimo Bertinelli/estec/ESA@ESA, "Tom Gannett" <</span><a href=mailto:thomas.gannett@tgannett.net><span style=" font-size:9pt;color:blue;font-family:Arial"><u>thomas.gannett@tgannett.net</u></span></a><span style=" font-size:9pt;font-family:Arial">>,
"Burleigh, Scott C \(312B\)" <</span><a href=mailto:scott.c.burleigh@jpl.nasa.gov><span style=" font-size:9pt;color:blue;font-family:Arial"><u>scott.c.burleigh@jpl.nasa.gov</u></span></a><span style=" font-size:9pt;font-family:Arial">>,
"Erik Barkley" <</span><a href=mailto:Erik.Barkley@jpl.nasa.gov><span style=" font-size:9pt;color:blue;font-family:Arial"><u>Erik.Barkley@jpl.nasa.gov</u></span></a><span style=" font-size:9pt;font-family:Arial">></span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
Date: </span><span style=" font-size:9pt;font-family:Arial">27-01-20
18:18</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
Subject: </span><span style=" font-size:9pt;font-family:Arial">Re:
SLS reply to SEA Conditions on Poll CESG-P-2019-12-002 Approval to release
CCSDS 131.3-P-1.1, CCSDS Space Link Protocols over ETSI DVB-S2 Standard
(Pink Sheets, Issue 1.1) for CCSDS Agency review</span><span style=" font-size:12pt;font-family:Times New Roman">
</span></p>
<div align=center>
<hr noshade></div>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Arial"><br>
<br>
<br>
Dear Peter,</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><br>
I wonder if you had time to consider this SLS reply.</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><br>
<br>
I also copy Scott (that expressed your same condition) and Erik (that expressed
the same concern as comment) reiterating that the work to allow uplink
of AOS and USLP fixed-length frames is in progress for all the 3 coding
books concerned. However the contribution from some book editors is less
timely than the one from the 131.3 Book Editor.</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><br>
<br>
Unless there is clear intention of penalising the faster book editor, <b> there
is no reason to defer the start of the Agency Review for the Pink Sheets
to 131.3-B.</b></span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><br>
<br>
Thank you all for a prompt reaction to fix this issue.</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><br>
<br>
Gian Paolo</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
<br>
<br>
<br>
From: </span><span style=" font-size:9pt;font-family:Arial">Gian
Paolo Calzolari/esoc/ESA</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
To: </span><span style=" font-size:9pt;font-family:Arial">"Shames,
Peter M \(312B\)" <</span><a href=mailto:peter.m.shames@jpl.nasa.gov><span style=" font-size:9pt;color:blue;font-family:Arial"><u>peter.m.shames@jpl.nasa.gov</u></span></a><span style=" font-size:9pt;font-family:Arial">></span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
Cc: </span><span style=" font-size:9pt;font-family:Arial">"Andrews,
Kenneth S \(332B\)" <</span><a href=mailto:Kenneth.S.Andrews@jpl.nasa.gov><span style=" font-size:9pt;color:blue;font-family:Arial"><u>Kenneth.S.Andrews@jpl.nasa.gov</u></span></a><span style=" font-size:9pt;font-family:Arial">>,
"Gilles Moury" <</span><a href=mailto:Gilles.Moury@cnes.fr><span style=" font-size:9pt;color:blue;font-family:Arial"><u>Gilles.Moury@cnes.fr</u></span></a><span style=" font-size:9pt;font-family:Arial">>,
Massimo Bertinelli/estec/ESA@ESA, "Tom Gannett" <</span><a href=mailto:thomas.gannett@tgannett.net><span style=" font-size:9pt;color:blue;font-family:Arial"><u>thomas.gannett@tgannett.net</u></span></a><span style=" font-size:9pt;font-family:Arial">></span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
Date: </span><span style=" font-size:9pt;font-family:Arial">20-01-20
17:43</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
Subject: </span><span style=" font-size:9pt;font-family:Arial">SLS
reply to SEA Conditions on Poll CESG-P-2019-12-002 Approval to release
CCSDS 131.3-P-1.1, CCSDS Space Link Protocols over ETSI DVB-S2 Standard
(Pink Sheets, Issue 1.1) for CCSDS Agency review</span><span style=" font-size:12pt;font-family:Times New Roman">
</span></p>
<div align=center>
<hr noshade></div>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Arial"><br>
<br>
<br>
Dear Peter,</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><br>
despite the poll, will only close in some time, SLS have
internally discussed about your "APPROVE WITH CONDITIONS" vot.</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><br>
The conditions are attached (thanks to Gilles!).</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><br>
<br>
Here below the SLS position.</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><br>
-------------------------------</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><br>
The SLS Area and the C&S WG reject SEA AD Conditions because <b>the
work requested by SEA AD is already agreed and in progress in the C&S
WG.</b></span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><br>
<br>
.C&S WG has currently 3 CWE projects running:</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><br>
<br>
1) Space link protocols over ETSI DVB-S2 standard, Issue 2</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><br>
This update to the Blue Book will produce issue 2, enabling the use USLP
frames as well as allowing space-to-space and ground-to-space links applications.</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:12pt;color:blue;font-family:Times New Roman"><u><br>
</u></span><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__cwe.ccsds.org_fm_Lists_Projects_DispForm.aspx-3FID-3D692-26ContentTypeId-3D0x0100B63160D64FE81342BE42A874DE7E703D&d=DwMGaQ&c=ApwzowJNAKKw3xye91w7BE1XMRKi2LN9kiMk5Csz9Zk&r=oqaLKgbprssjRKcKzadGIePtu_DWF3UbezbcN7JWLp0&m=y4TtGXm6TkDunBbs9P1Em2yfE5oBSxV1BJ1Cd4YlA5c&s=PzChcllVokmqH0jxCpb_GDdB_LhVceNvGvKqrToyE2c&e="><span style=" font-size:10pt;color:blue;font-family:Arial"><u>https://cwe.ccsds.org/fm/Lists/Projects/DispForm.aspx?ID=692&ContentTypeId=0x0100B63160D64FE81342BE42A874DE7E703D</u></span></a><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><br>
This is the project undergoing poll for Agency review.</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><br>
<br>
2)“TM Synchronization and Channel Coding” Issue 4</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><br>
The Recommended Standard for TM Synchronization and Channel Coding contains
specifications to be used by space missions on synchronous communications
links. This update to the Blue Book will produce issue 4, and will add
a short chapter that specifies a subset of codes to be used in ground-to-space
links. Input of USLP frames will also be addressed.</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:12pt;color:blue;font-family:Times New Roman"><u><br>
</u></span><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__cwe.ccsds.org_fm_Lists_Projects_DispForm.aspx-3FID-3D688-26ContentTypeId-3D0x0100B63160D64FE81342BE42A874DE7E703D&d=DwMGaQ&c=ApwzowJNAKKw3xye91w7BE1XMRKi2LN9kiMk5Csz9Zk&r=oqaLKgbprssjRKcKzadGIePtu_DWF3UbezbcN7JWLp0&m=y4TtGXm6TkDunBbs9P1Em2yfE5oBSxV1BJ1Cd4YlA5c&s=UqJ6goEMo5EqD--DUhoYKj6A_wwlr7pQ6NWiPQO-N8o&e="><span style=" font-size:10pt;color:blue;font-family:Arial"><u>https://cwe.ccsds.org/fm/Lists/Projects/DispForm.aspx?ID=688&ContentTypeId=0x0100B63160D64FE81342BE42A874DE7E703D</u></span></a><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><br>
This project is pending on NASA input.</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><br>
<br>
3) Flexible Advanced Coding and Modulation Scheme for High Rate Telemetry
Applications, Issue 2</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><br>
This update to the Blue Book will produce issue 2, enabling the use USLP
frames as well as allowing space-to-space and ground-to-space links applications.</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:12pt;color:blue;font-family:Times New Roman"><u><br>
</u></span><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__cwe.ccsds.org_fm_Lists_Projects_DispForm.aspx-3FID-3D690-26ContentTypeId-3D0x0100B63160D64FE81342BE42A874DE7E703D&d=DwMGaQ&c=ApwzowJNAKKw3xye91w7BE1XMRKi2LN9kiMk5Csz9Zk&r=oqaLKgbprssjRKcKzadGIePtu_DWF3UbezbcN7JWLp0&m=y4TtGXm6TkDunBbs9P1Em2yfE5oBSxV1BJ1Cd4YlA5c&s=m-jQWJMjqGIB4v5yLNTSthDUDbwew435KmwbO3kkMOw&e="><span style=" font-size:10pt;color:blue;font-family:Arial"><u>https://cwe.ccsds.org/fm/Lists/Projects/DispForm.aspx?ID=690&ContentTypeId=0x0100B63160D64FE81342BE42A874DE7E703D</u></span></a><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><br>
This project is pending on ESA input.</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><b><br>
<br>
Therefore there is no reason to defer the start of the Agency Review for
the Pink Sheets to 131.3-B.</b></span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><br>
--------------------------------------------</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><br>
<br>
Best regards</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><br>
<br>
Gian Paolo</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><br>
<br>
<br>
[attachment "PS DVBS2 condition.docx" deleted by Gian Paolo Calzolari/esoc/ESA]
</span><span style=" font-size:10pt;font-family:Courier New"><br>
This message is intended only for the recipient(s) named above. It may
contain proprietary information and/or</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Courier New"><br>
protected content. Any unauthorised disclosure, use, retention or dissemination
is prohibited. If you have received</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Courier New"><br>
this e-mail in error, please notify the sender immediately. ESA applies
appropriate organisational measures to protect</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Courier New"><br>
personal data, in case of data privacy queries, please contact the ESA
Data Protection Officer (</span><a href=mailto:dpo@esa.int><span style=" font-size:10pt;color:blue;font-family:Courier New"><u>dpo@esa.int</u></span></a><span style=" font-size:10pt;font-family:Courier New">).[attachment
"DVB_S2 MIB tables.xlsx" deleted by Gian Paolo Calzolari/esoc/ESA]
</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">This
message is intended only for the recipient(s) named above. It may contain
proprietary information and/or</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">protected
content. Any unauthorised disclosure, use, retention or dissemination is
prohibited. If you have received</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">this
e-mail in error, please notify the sender immediately. ESA applies appropriate
organisational measures to protect</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">personal
data, in case of data privacy queries, please contact the ESA Data Protection
Officer (</span><a href=mailto:dpo@esa.int)._______________________________________________><span style=" font-size:10pt;color:blue;font-family:Courier New"><u>dpo@esa.int)._______________________________________________</u></span></a><span style=" font-size:10pt;font-family:Courier New"><br>
CESG mailing list</span><span style=" font-size:12pt;color:blue;font-family:Times New Roman"><u><br>
</u></span><a href=mailto:CESG@mailman.ccsds.org><span style=" font-size:10pt;color:blue;font-family:Courier New"><u>CESG@mailman.ccsds.org</u></span></a><span style=" font-size:12pt;color:blue;font-family:Times New Roman"><u><br>
</u></span><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__mailman.ccsds.org_cgi-2Dbin_mailman_listinfo_cesg&d=DwMGaQ&c=ApwzowJNAKKw3xye91w7BE1XMRKi2LN9kiMk5Csz9Zk&r=oqaLKgbprssjRKcKzadGIePtu_DWF3UbezbcN7JWLp0&m=SDlYvgxXn535X5n1PSOvR3nMHX4RF0vZZzg2w2L4_Hw&s=KcfkCZm7yp3dmq2prp9lvpipIYEfQ9hvcxw0Dwv6nQI&e="><span style=" font-size:10pt;color:blue;font-family:Courier New"><u>https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg</u></span></a></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">This
message is intended only for the recipient(s) named above. It may contain
proprietary information and/or</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">protected
content. Any unauthorised disclosure, use, retention or dissemination is
prohibited. If you have received</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">this
e-mail in error, please notify the sender immediately. ESA applies appropriate
organisational measures to protect</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">personal
data, in case of data privacy queries, please contact the ESA Data Protection
Officer (</span><a href=mailto:dpo@esa.int><span style=" font-size:10pt;color:blue;font-family:Courier New"><u>dpo@esa.int</u></span></a><span style=" font-size:10pt;font-family:Courier New">).</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">This
message is intended only for the recipient(s) named above. It may contain
proprietary information and/or</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">protected
content. Any unauthorised disclosure, use, retention or dissemination is
prohibited. If you have received</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">this
e-mail in error, please notify the sender immediately. ESA applies appropriate
organisational measures to protect</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">personal
data, in case of data privacy queries, please contact the ESA Data Protection
Officer (</span><a href=mailto:dpo@esa.int><span style=" font-size:10pt;color:blue;font-family:Courier New"><u>dpo@esa.int</u></span></a><span style=" font-size:10pt;font-family:Courier New">).</span></p>
<p style="margin-top:0px;margin-Bottom:0px"></p>
<p style="margin-top:0px;margin-Bottom:0px"></p>
<PRE>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@esa.int).
</PRE>