<span style=" font-size:10pt;font-family:sans-serif">Dear All,</span>
<br><span style=" font-size:10pt;font-family:sans-serif">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. </span>
<br><span style=" font-size:10pt;font-family:sans-serif">At the CESG Meeting
in Mountain View we noted the following:</span>
<br><span style=" font-size:10pt;font-family:sans-serif"><i>“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>
<br><span style=" font-size:10pt;font-family:sans-serif">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. </span>
<br><span style=" font-size:10pt;font-family:sans-serif">The MoM of the
Darmstadt meeting records the following action(s) :</span>
<div><span style=" font-size:10pt;font-family:sans-serif"><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>
<br><span style=" font-size:10pt;font-family:sans-serif"><i>-
<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>
<br><span style=" font-size:10pt;font-family:sans-serif"><i>-
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>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">I think we shall
keep pursuing the definition of a CCSDS “formalism” for data representation.</span>
<br><span style=" font-size:10pt;font-family:sans-serif">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 </span>
<br><span style=" font-size:10pt;font-family:sans-serif">Finally, I'd like
to ask Jonathan to let us have an update at the upcoming CESG Telecon.</span>
<br><span style=" font-size:10pt;font-family:sans-serif">Kind regards,<br>
Margherita</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">--------------------------------------------------------------<br>
</span><span style=" font-size:8pt;color:#00a1e0;font-family:Verdana"><b>Margherita
di Giulio</b></span>
<br><span style=" font-size:8pt;color:#5f5f5f;font-family:Verdana">Ground
Station Systems Division</span>
<br><span style=" font-size:8pt;color:#5f5f5f;font-family:Verdana">Backend
Software Section (OPS-GSB)</span>
<br>
<br>
<br><span style=" font-size:8pt;color:#5f5f5f;font-family:Verdana"><b>European
Space Agency ESA/ESOC</b><br>
Robert-Bosch-Str. 5<br>
D-64293 Darmstadt - Germany<br>
Tel: +49-6151-902779<br>
e-mail: Margherita.di.Giulio@esa.int</span><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif"><br>
<br>
</span>
<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">"Shames,
Peter M\(US 312B\) via CESG" <cesg@mailman.ccsds.org></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>, "Wilmot, Jonathan J. (GSFC-5820)"
<jonathan.j.wilmot@nasa.gov></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>,
"Kazz, Greg J\(US 312B\)" <greg.j.kazz@jpl.nasa.gov>, "Tom
Gannett" <thomas.gannett@tgannett.net>, "Massimo.Bertinelli@esa.int"
<Massimo.Bertinelli@esa.int>, "Andrews, Kenneth S\(US 332B\)"
<kenneth.s.andrews@jpl.nasa.gov></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Date:
</span><span style=" font-size:9pt;font-family:sans-serif">03/02/2020
21:33</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 Agency review</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Sent
by: </span><span style=" font-size:9pt;font-family:sans-serif">"CESG"
<cesg-bounces@mailman.ccsds.org></span>
<br>
<hr noshade>
<br>
<br>
<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>
<br><span style=" font-size:12pt">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.</span>
<br><span style=" font-size:12pt">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.</span>
<br><span style=" font-size:12pt">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,</span>
<br><span style=" font-size:12pt">I think a little more clarity in the
specs that include MIBs would be a benefit to everyone.</span>
<br><span style=" font-size:12pt">Cheers, Peter</span>
<br><span style=" font-size:12pt"> </span>
<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 <Gian.Paolo.Calzolari@esa.int><b><br>
Date: </b>Monday, February 3, 2020 at 5:38 AM<b><br>
To: </b>"Wilmot, Jonathan J. (GSFC-5820)" <jonathan.j.wilmot@nasa.gov><b><br>
Cc: </b>Gilles Moury <Gilles.Moury@cnes.fr>, Kenneth Andrews <kenneth.s.andrews@jpl.nasa.gov>,
"Massimo.Bertinelli@esa.int" <Massimo.Bertinelli@esa.int>,
Peter Shames <peter.m.shames@jpl.nasa.gov>, Tom Gannett <thomas.gannett@tgannett.net>,
Greg Kazz <greg.j.kazz@jpl.nasa.gov><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">
<br>
</span><span style=" font-size:10pt;font-family:Arial"><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">
<br>
</span><span style=" font-size:10pt;font-family:Arial"><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">
<br>
</span><span style=" font-size:10pt;font-family:Arial"><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">
<br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
Best regards</span><span style=" font-size:11pt;font-family:Calibri"> <br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
Gian Paolo</span><span style=" font-size:11pt;font-family:Calibri"> <br>
<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)" <jonathan.j.wilmot@nasa.gov></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">"Gian.Paolo.Calzolari@esa.int"
<Gian.Paolo.Calzolari@esa.int></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">"Massimo.Bertinelli@esa.int"
<Massimo.Bertinelli@esa.int>, "Gilles Moury" <Gilles.Moury@cnes.fr>,
"Andrews, Kenneth S (JPL-332B)[Jet Propulsion Laboratory]" <kenneth.s.andrews@jpl.nasa.gov>,
"Tom Gannett" <thomas.gannett@tgannett.net>, "Shames,
Peter M (JPL-312B)[Jet Propulsion Laboratory]" <peter.m.shames@jpl.nasa.gov></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="margin-top:0px;margin-Bottom:240px"><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">,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#004080"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#004080">
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"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#004080">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"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#004080"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#004080">
Kind regards,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#004080"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#004080">
Jonathan</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#004080"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#004080">Jonathan
Wilmot</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#004080">NASA/GSFC
Code 582</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#004080">cFS
Software Architect</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#004080">CCSDS
SOIS Area Director</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#004080">301-286-2623</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#004080"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#004080"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#004080"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt"><b>From:</b>
Gian.Paolo.Calzolari@esa.int <Gian.Paolo.Calzolari@esa.int> <b><br>
Sent:</b> Tuesday, January 28, 2020 4:15 AM<b><br>
To:</b> Wilmot, Jonathan J. (GSFC-5820) <jonathan.j.wilmot@nasa.gov><b><br>
Cc:</b> Massimo.Bertinelli@esa.int; Gilles Moury <Gilles.Moury@cnes.fr>;
Andrews, Kenneth S (JPL-332B)[Jet Propulsion Laboratory] <kenneth.s.andrews@jpl.nasa.gov>;
Tom Gannett <thomas.gannett@tgannett.net><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-Bottom:0px"><span style=" font-size:12pt;font-family:Times New Roman"> </span></p>
<p style=";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>
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-Bottom:0px"><span style=" font-size:10pt;font-family:Arial"><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">
<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">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-Bottom:3600px"><span style=" font-size:10pt;font-family:Arial"><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"><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"><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"><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">
<br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
<br>
[attachment "PS DVBS2 condition.docx" deleted by Gian Paolo Calzolari/esoc/ESA]
</span></p>
<p style=" "-■"-╠,Å;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-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-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-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">).[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 (dpo@esa.int).</span><tt><span style=" font-size:10pt">_______________________________________________<br>
CESG mailing list<br>
CESG@mailman.ccsds.org<br>
</span></tt><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg"><tt><span style=" font-size:10pt">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg</span></tt></a><tt><span style=" font-size:10pt"><br>
</span></tt></p>
<p style="margin-top:0px;margin-Bottom:0px"></p>
<p style="margin-top:0px;margin-Bottom:0px"></p></div>
<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>