<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:ArialMT;
panose-1:2 11 6 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">Hi Gippo and Jonathan,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I think that Jonathan is "right" in that some added formality would make these MIB values be more easily interpreted and exchanged for interoperability.<o:p></o:p></p>
<p>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. "<span style="font-family:"ArialMT",serif">List of integers</span>", 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.<o:p></o:p></p>
<p>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.<o:p></o:p></p>
<p>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,<o:p></o:p></p>
<p>I think a little more clarity in the specs that include MIBs would be a benefit to everyone.<o:p></o:p></p>
<p>Cheers, Peter<o:p></o:p></p>
<p><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-left:.5in"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">Gian Paolo Calzolari <Gian.Paolo.Calzolari@esa.int><br>
<b>Date: </b>Monday, February 3, 2020 at 5:38 AM<br>
<b>To: </b>"Wilmot, Jonathan J. (GSFC-5820)" <jonathan.j.wilmot@nasa.gov><br>
<b>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><br>
<b>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<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Jonathan,</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"> first of all, it is our understating that the specific comment addressed by this discussion is a comment and not a condition.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Can you please confirm?</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">For the remaining part of this e-mail I include in cc also Greg as you expressed similar comments for SLP documents.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">You are talking about the "</span><span style="color:#004080">formality of protocol MIB definitions</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif">" and in your attached file
you actually start from the tables in CCSDS 131.3-P-1.0 Chapter 5 adding two columns.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">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>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The real addition is column "Data Type" that is really computer oriented; i.e. an implementation detail IMO.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">However section APPLICABILITY for this book (and for most of the SLS Area books) clearly states that "<span style="color:red">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>" giving a full justification for the way Managed Parameters are
presented.</span> <br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">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>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Even sympathising with the fact that "</span><span style="color:#004080">missions could exchange the MIB configuration data</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif">",
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>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Best regards</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Gian Paolo</span> <br>
<br>
<br>
<br>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">From: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"Wilmot, Jonathan J. (GSFC-5820)" <jonathan.j.wilmot@nasa.gov></span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">To: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"Gian.Paolo.Calzolari@esa.int" <Gian.Paolo.Calzolari@esa.int></span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Cc: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"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>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Date: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">31-01-20 20:46</span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Subject: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">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>
<o:p></o:p></p>
<div class="MsoNormal" align="center" style="margin-left:.5in;text-align:center">
<hr size="0" width="100%" noshade="" style="color:#A0A0A0" align="center">
</div>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
<o:p> </o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Gian Paolo</span><span style="color:#004080">,</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<span style="color:#004080"> </span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<span style="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><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<span style="color:#004080"> </span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<span style="color:#004080">Please let me know if the attachment makes sense. </span>
<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<span style="color:#004080"> </span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<span style="color:#004080"> </span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<span style="color:#004080"> Kind regards,</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<span style="color:#004080"> </span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<span style="color:#004080"> Jonathan</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<span style="color:#004080"> </span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<span style="color:#004080">Jonathan Wilmot</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<span style="color:#004080">NASA/GSFC Code 582</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<span style="color:#004080">cFS Software Architect</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<span style="color:#004080">CCSDS SOIS Area Director</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<span style="color:#004080">301-286-2623</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<span style="color:#004080"> </span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<span style="color:#004080"> </span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<span style="color:#004080"> </span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<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<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<span style="font-size:12.0pt;font-family:"Times New Roman",serif"> </span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Jonathan,</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
here attached the mail already sent to Peter etc.</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><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:12.0pt;font-family:"Times New Roman",serif">
<br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
With respect to your specicif comment "<span style="color:blue">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>." 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:12.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
Otherwise there is no way to consider this comment.</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
<br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
Best regards</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
<br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
Gian Paolo</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
<br>
</span><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:purple"><br>
----- Forwarded by Gian Paolo Calzolari/esoc/ESA on 28-01-20 10:11 -----</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
<br>
</span><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
From: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">Gian Paolo Calzolari/esoc/ESA</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
To: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"Shames, Peter M \(312B\)" <</span><a href="mailto:peter.m.shames@jpl.nasa.gov"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">peter.m.shames@jpl.nasa.gov</span></a><span style="font-size:9.0pt;font-family:"Arial",sans-serif">></span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
Cc: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"Andrews, Kenneth S \(332B\)" <</span><a href="mailto:Kenneth.S.Andrews@jpl.nasa.gov"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">Kenneth.S.Andrews@jpl.nasa.gov</span></a><span style="font-size:9.0pt;font-family:"Arial",sans-serif">>,
"Gilles Moury" <</span><a href="mailto:Gilles.Moury@cnes.fr"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">Gilles.Moury@cnes.fr</span></a><span style="font-size:9.0pt;font-family:"Arial",sans-serif">>, Massimo Bertinelli/estec/ESA@ESA, "Tom
Gannett" <</span><a href="mailto:thomas.gannett@tgannett.net"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">thomas.gannett@tgannett.net</span></a><span style="font-size:9.0pt;font-family:"Arial",sans-serif">>, "Burleigh, Scott C \(312B\)" <</span><a href="mailto:scott.c.burleigh@jpl.nasa.gov"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">scott.c.burleigh@jpl.nasa.gov</span></a><span style="font-size:9.0pt;font-family:"Arial",sans-serif">>,
"Erik Barkley" <</span><a href="mailto:Erik.Barkley@jpl.nasa.gov"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">Erik.Barkley@jpl.nasa.gov</span></a><span style="font-size:9.0pt;font-family:"Arial",sans-serif">></span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
Date: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">27-01-20 18:18</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
Subject: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">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:12.0pt;font-family:"Times New Roman",serif">
</span><o:p></o:p></p>
<div class="MsoNormal" align="center" style="margin-left:.5in;text-align:center">
<hr size="0" width="100%" noshade="" style="color:#A0A0A0" align="center">
</div>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
Dear Peter,</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
I wonder if you had time to consider this SLS reply.</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
<br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><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:12.0pt;font-family:"Times New Roman",serif">
<br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><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:12.0pt;font-family:"Times New Roman",serif">
<br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
Thank you all for a prompt reaction to fix this issue.</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
<br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
Gian Paolo</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
<br>
<br>
<br>
</span><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
From: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">Gian Paolo Calzolari/esoc/ESA</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
To: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"Shames, Peter M \(312B\)" <</span><a href="mailto:peter.m.shames@jpl.nasa.gov"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">peter.m.shames@jpl.nasa.gov</span></a><span style="font-size:9.0pt;font-family:"Arial",sans-serif">></span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
Cc: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"Andrews, Kenneth S \(332B\)" <</span><a href="mailto:Kenneth.S.Andrews@jpl.nasa.gov"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">Kenneth.S.Andrews@jpl.nasa.gov</span></a><span style="font-size:9.0pt;font-family:"Arial",sans-serif">>,
"Gilles Moury" <</span><a href="mailto:Gilles.Moury@cnes.fr"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">Gilles.Moury@cnes.fr</span></a><span style="font-size:9.0pt;font-family:"Arial",sans-serif">>, Massimo Bertinelli/estec/ESA@ESA, "Tom
Gannett" <</span><a href="mailto:thomas.gannett@tgannett.net"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">thomas.gannett@tgannett.net</span></a><span style="font-size:9.0pt;font-family:"Arial",sans-serif">></span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
Date: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">20-01-20 17:43</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
Subject: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">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:12.0pt;font-family:"Times New Roman",serif">
</span><o:p></o:p></p>
<div class="MsoNormal" align="center" style="margin-left:.5in;text-align:center">
<hr size="0" width="100%" noshade="" style="color:#A0A0A0" align="center">
</div>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:2.5in;margin-left:.5in">
<span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
Dear Peter,</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><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:12.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
The conditions are attached (thanks to Gilles!).</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
<br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
Here below the SLS position.</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
-------------------------------</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><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:12.0pt;font-family:"Times New Roman",serif">
<br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
.C&S WG has currently 3 CWE projects running:</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
<br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
1) Space link protocols over ETSI DVB-S2 standard, Issue 2</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><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:12.0pt;font-family:"Times New Roman",serif">
<u><span style="color:blue"><br>
</span></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:10.0pt;font-family:"Arial",sans-serif">https://cwe.ccsds.org/fm/Lists/Projects/DispForm.aspx?ID=692&ContentTypeId=0x0100B63160D64FE81342BE42A874DE7E703D</span></a><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
This is the project undergoing poll for Agency review.</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
<br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
2)“TM Synchronization and Channel Coding” Issue 4</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><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:12.0pt;font-family:"Times New Roman",serif">
<u><span style="color:blue"><br>
</span></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:10.0pt;font-family:"Arial",sans-serif">https://cwe.ccsds.org/fm/Lists/Projects/DispForm.aspx?ID=688&ContentTypeId=0x0100B63160D64FE81342BE42A874DE7E703D</span></a><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
This project is pending on NASA input.</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
<br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
3) Flexible Advanced Coding and Modulation Scheme for High Rate Telemetry Applications, Issue 2</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><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:12.0pt;font-family:"Times New Roman",serif">
<u><span style="color:blue"><br>
</span></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:10.0pt;font-family:"Arial",sans-serif">https://cwe.ccsds.org/fm/Lists/Projects/DispForm.aspx?ID=690&ContentTypeId=0x0100B63160D64FE81342BE42A874DE7E703D</span></a><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
This project is pending on ESA input.</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
<br>
</span><b><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
Therefore there is no reason to defer the start of the Agency Review for the Pink Sheets to 131.3-B.</span></b><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
--------------------------------------------</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
<br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
Best regards</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
<br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
Gian Paolo</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
<br>
<br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
[attachment "PS DVBS2 condition.docx" deleted by Gian Paolo Calzolari/esoc/ESA] </span>
<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<span style="font-size:10.0pt;font-family:"Courier New"">This message is intended only for the recipient(s) named above. It may contain proprietary information and/or</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<span style="font-size:10.0pt;font-family:"Courier New"">protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<span style="font-size:10.0pt;font-family:"Courier New"">this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<span style="font-size:10.0pt;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:10.0pt;font-family:"Courier New"">dpo@esa.int</span></a><span style="font-size:10.0pt;font-family:"Courier New"">).[attachment
"DVB_S2 MIB tables.xlsx" deleted by Gian Paolo Calzolari/esoc/ESA] </span><o:p></o:p></p>
<pre style="margin-left:.5in">This message is intended only for the recipient(s) named above. It may contain proprietary information and/or<o:p></o:p></pre>
<pre style="margin-left:.5in">protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received<o:p></o:p></pre>
<pre style="margin-left:.5in">this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect<o:p></o:p></pre>
<pre style="margin-left:.5in">personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo@esa.int).<o:p></o:p></pre>
</div>
</body>
</html>