<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:"Tms Rmn";
panose-1:2 11 6 4 2 2 2 2 2 4;}
@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:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:TimesNewRomanPSMT;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:"Courier New \,serif";
panose-1:2 7 3 9 2 2 5 2 4 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
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;
font-size:10.0pt;
font-family:"Courier New",serif;}
tt
{mso-style-priority:99;
font-family:"Courier New",serif;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle25
{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;}
/* List Definitions */
@list l0
{mso-list-id:118575197;
mso-list-template-ids:-1886076124;}
@list l0:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1
{mso-list-id:424375988;
mso-list-template-ids:1081104932;}
@list l1:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2
{mso-list-id:567686479;
mso-list-template-ids:-2038791264;}
@list l2:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3
{mso-list-id:1201674704;
mso-list-template-ids:-841455826;}
@list l3:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4
{mso-list-id:1281840145;
mso-list-type:hybrid;
mso-list-template-ids:1769354894 67698705 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l4:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l4:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l4:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span class="EmailStyle25">Hi Jon,<o:p></o:p></span></p>
<p class="MsoNormal"><span class="EmailStyle25"><o:p> </o:p></span></p>
<p class="MsoNormal"><span class="EmailStyle25">Actually, what I meant by “deal with the fundamental issues” is that I wish to present the point of view that we are working from in this document first. This discussion is first and foremost about this SCCS-ARD
document.<o:p></o:p></span></p>
<p class="MsoNormal"><span class="EmailStyle25"><o:p> </o:p></span></p>
<p class="MsoNormal"><span class="EmailStyle25">As with so many things, looked at from the bottom up things look one way, they look different from the top down. This SCCS-ARD document is a top down perspective, as it must be in order to describe how over seventy-five
(75) standards fit together, like a jig-saw puzzle. This is to help the users of this “CCSDS Suite” of standards understand how they can be used to create end-to-end information systems for missions, create ground stations and their supporting infrastructure,
design spacecraft on-board systems, and also the mission operations systems that deal with all of these communications issues.<o:p></o:p></span></p>
<p class="MsoNormal"><span class="EmailStyle25"><o:p> </o:p></span></p>
<p class="MsoNormal"><span class="EmailStyle25">This is a big job, and no insult intended, these VCM issues are a very small piece of the overall picture. I’ve intentionally exaggerated for effect, but we really want to avoid anything like the attached picture.<o:p></o:p></span></p>
<p class="MsoNormal"><span class="EmailStyle25"><o:p> </o:p></span></p>
<p class="MsoNormal"><span class="EmailStyle25">This is my proposed agenda for this discussion of the SCCS-ARD “omnibus” architecture document and how this VCM topic fits into it:<o:p></o:p></span></p>
<p class="MsoNormal"><span class="EmailStyle25"><o:p> </o:p></span></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l4 level1 lfo5">Present, briefly, the overall structure of the SCCS-ARD<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l4 level1 lfo5">Describe the different viewpoints that it covers<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l4 level1 lfo5">Describe how we have handled the VCM “suite” of standards and why we chose to handle them that way<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l4 level1 lfo5">Try and reach closure on an overall approach<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l4 level1 lfo5">And then deal with the specific details in that context<o:p></o:p></li></ol>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks, Peter<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">PS – we also described all of the Internet protocols, a massive body of work, as “the Internet Protocol Suite (IPS)”. See References, pg 36. We handle the “DTN suite” in a similar way. No one has complained.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">See <a href="https://en.wikipedia.org/wiki/Internet_protocol_suite">
https://en.wikipedia.org/wiki/Internet_protocol_suite</a><o:p></o:p></p>
<p class="MsoNormal"><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"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">Jon Hamkins <Jon.Hamkins@jpl.nasa.gov><br>
<b>Date: </b>Wednesday, December 1, 2021 at 12:00 PM<br>
<b>To: </b>Peter Shames <peter.m.shames@jpl.nasa.gov>, Space Link Coding & Synchronization Working Group <sls-cc@mailman.ccsds.org>, "sls-rfm@mailman.ccsds.org" <sls-rfm@mailman.ccsds.org><br>
<b>Cc: </b>"Ignacio.Aguilar.Sanchez@esa.int" <Ignacio.Aguilar.Sanchez@esa.int><br>
<b>Subject: </b>Re: [EXTERNAL] Re: [SLS-CC] Fw: WebEx meeting invitation: SCCS-ARD update review scheduled for Tuesday, 23 Nov, 2021 at 0700 AM PST<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p>Okay, sounds good. I hope we can find a time that the C&S/RFM chairs and champions of the involved standards can be present.<o:p></o:p></p>
<p>I am requesting the meeting so that I can describe my concerns and discuss a way to reach consensus. I suggest a one-hour block at the beginning for me to present them, in a two-hour meeting. This conversation will quickly get at the issue of the “suite”
label, so I think that fits in with Peter's plan, and there are a number of unrelated fundamental issues relating to factual errors, omissions, complexity, etc., as well.<o:p></o:p></p>
<p> ----Jon<o:p></o:p></p>
<div>
<p class="MsoNormal"><strong><span style="font-family:"Calibri",sans-serif">Jon Hamkins</span></strong><br>
Chief Technologist, Communications, Tracking, and Radar Division<br>
<strong><span style="font-family:"Calibri",sans-serif">O</span></strong> 818-354-4764 |
<strong><span style="font-family:"Calibri",sans-serif">M</span></strong> 626-658-6220<br>
<br>
<strong><span style="font-family:"Calibri",sans-serif">JPL</span></strong> | jpl.nasa.gov<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">On 11/30/2021 10:32 AM, Shames, Peter M (US 312B) wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Thanks Jon. I will fire off a Doodle to pick a time for a Webex.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">As far as I am concerned we need to deal with the fundamental issues that I raised. The handling of the details in the document will be a direct result of that discussion.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Thanks, Peter<o:p></o:p></p>
<p class="MsoNormal"> <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"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">Jon Hamkins
<a href="mailto:Jon.Hamkins@jpl.nasa.gov"><Jon.Hamkins@jpl.nasa.gov></a><br>
<b>Date: </b>Monday, November 29, 2021 at 7:29 PM<br>
<b>To: </b>Peter Shames <a href="mailto:peter.m.shames@jpl.nasa.gov"><peter.m.shames@jpl.nasa.gov></a>, Space Link Coding & Synchronization Working Group
<a href="mailto:sls-cc@mailman.ccsds.org"><sls-cc@mailman.ccsds.org></a>, <a href="mailto:sls-rfm@mailman.ccsds.org">
"sls-rfm@mailman.ccsds.org"</a> <a href="mailto:sls-rfm@mailman.ccsds.org"><sls-rfm@mailman.ccsds.org></a><br>
<b>Cc: </b><a href="mailto:Ignacio.Aguilar.Sanchez@esa.int">"Ignacio.Aguilar.Sanchez@esa.int"</a>
<a href="mailto:Ignacio.Aguilar.Sanchez@esa.int"><Ignacio.Aguilar.Sanchez@esa.int></a><br>
<b>Subject: </b>Re: [EXTERNAL] Re: [SLS-CC] Fw: WebEx meeting invitation: SCCS-ARD update review scheduled for Tuesday, 23 Nov, 2021 at 0700 AM PST</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<p>Thanks, Peter. I think we will make faster progress with a webex meeting rather than email. I would like to resolve each of the six comments.<o:p></o:p></p>
<p> ----Jon<o:p></o:p></p>
<div>
<p class="MsoNormal"><strong><span style="font-family:"Calibri",sans-serif">Jon Hamkins</span></strong><br>
Chief Technologist, Communications, Tracking, and Radar Division<br>
<strong><span style="font-family:"Calibri",sans-serif">O</span></strong> 818-354-4764 |
<strong><span style="font-family:"Calibri",sans-serif">M</span></strong> 626-658-6220<br>
<br>
<strong><span style="font-family:"Calibri",sans-serif">JPL</span></strong> | jpl.nasa.gov<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">On 11/29/2021 3:29 PM, Shames, Peter M (US 312B) wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Hi Jon and all our other SLS C&S and RFM WG colleagues.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">In the context of the Space Communication Cross Support (SCCS) Architecture Requirements Document (ARD) we have this on-going discussion of the state of the SLS “VCM Suite” of variable coding and modulation standards. Jon has pointed out,
at length, that there is no term “VCM suite” defined within the C&S WG or within any of the SLS Area literature. I have to agree that this statement, taken by itself, is true.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">What Jon has then requested is that this term “VCM Suite”, and the diagram we have constructed to explain the complexities of this situation, be replaced in the SCCS-ARD by the single term “the VCM protocol” and also be shown as three separate
boxes in figure 6-1, Layering of CCSDS link layer protocols. <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Last week we held a 2 hour review of all of the major changes we have introduced in the SCCS-ARD. These changes are due to the usual 5 year document review and the addition of many new standards, several of which had only been forecast
in the original edition. Among these were the DVB-S2 (CCSDS 131.1-B-2), the SCCC (CCSDS 131.2-B-2), and the VCM (CCSDS 431.1-B-1). What cannot be in question is that all three of these describe themselves as “VCM protocols”. Even the 431.1 document describes
all three of these, separately, as VCM protocols.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">See the two attachments for screen shots of the 431.1 document where these statements are made and where some of the differences are described, in text.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">The 431.1-B-1 document also makes this statement, in Sec 1.2 Purpose and Scope<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<span style="font-size:12.0pt;font-family:"TimesNewRomanPSMT",serif;color:#0070C0">The purpose of this Recommended Standard is to specify various combinations of coding and modulations in references [1], [2], [4], and [5], that can operate under the VCM protocol
defined in references [2] and [4]. This enables, for example, some of the CCSDS recommended channel codes (reference [1]) and modulations (reference [5]) to be used with the CCSDS VCM protocol.
</span><o:p></o:p></p>
<p class="MsoNormal">In reading through this 431.1-B-1 document, again, I am struck fact that the document, in two different sentences, says “there are three different VCM protocols”, and then “there is one ‘CCSDS VCM protocol’”. Just looking again at these
documents, all three of them, three things are very clear:<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l2 level1 lfo1">There are three separate documents, each of which is defined as a “VCM protocol”.
<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l2 level1 lfo1">The three are similar, but, in detailed fact, are different and cannot interoperate.
<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l2 level1 lfo1">The third of these, CCSDS 431.1 cannot stand alone, it is meaningless without heavy reliance on major parts of DVB-S2 and SCCC, which it terms as Type 1 and Type 2 VCM schemes.
<o:p></o:p></li></ol>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">I am not going to un-Earth the history of how we got into this situation, but I firmly believe that if we asked any knowledgeable, independent, reviewer with relevant technical background to review these three standards they would ask “Why
do you have three nearly identical standards when one would do?”. <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">But the facts are that we do have two nearly identical standards and a third one that could not exist at all without the other two, which it is (almost) entirely dependent upon. This is unique in CCSDS.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">As for SCCS-ARD, the attached PPT file will make clear how we propose to handle this situation. Instead of showing the Telemetry S&C, and the Telecommand S&C, and three separate, different, but admittedly nearly identical, VCM protocols,
we have chosen to call this set of triplets the “VCM suite”, to show how these fit with the other related standards, and to show their similarities and differences. We think that this both provides visibility to this VCM technique, allows us to state what
value they bring (primarily for high rate downlink missions), and also to not overly complicate an already complicated diagram with three essentially identical VCM protocols.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">We called this trio of VCM standards the “VCM suite”. If you all have a better name to suggest we are open to hearing it. All of the other people we have had review this agree that this is a suitably simple, and effective, way to deal
with this complicated situation.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">If we need to have a WebEx to discuss this I am more than willing to set one up.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Thanks, Peter<o:p></o:p></p>
<p class="MsoNormal"> <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"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">SLS-CC
<a href="mailto:sls-cc-bounces@mailman.ccsds.org"><sls-cc-bounces@mailman.ccsds.org></a> on behalf of Jon Hamkins via SLS-CC
<a href="mailto:sls-cc@mailman.ccsds.org"><sls-cc@mailman.ccsds.org></a><br>
<b>Reply-To: </b>Jon Hamkins <a href="mailto:jon.hamkins@jpl.nasa.gov"><jon.hamkins@jpl.nasa.gov></a><br>
<b>Date: </b>Sunday, November 14, 2021 at 11:05 PM<br>
<b>To: </b>Space Link Coding & Synchronization Working Group <a href="mailto:sls-cc@mailman.ccsds.org">
<sls-cc@mailman.ccsds.org></a>, <a href="mailto:sls-rfm@mailman.ccsds.org">"sls-rfm@mailman.ccsds.org"</a>
<a href="mailto:sls-rfm@mailman.ccsds.org"><sls-rfm@mailman.ccsds.org></a>, CCSDS Engineering Steering Group - CESG All
<a href="mailto:cesg-all@mailman.ccsds.org"><cesg-all@mailman.ccsds.org></a><br>
<b>Subject: </b>[EXTERNAL] Re: [SLS-CC] Fw: WebEx meeting invitation: SCCS-ARD update review scheduled for Tuesday, 23 Nov, 2021 at 0700 AM PST</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<p>Thank you for the invitation to review the SCCS-ARD. I regret that I will not be able to discuss the SCCS-ARD in person on 23 Nov. I will be on vacation that week. I give my comments here, with the hope that this is enough in advance of the meeting for each
of the individual comments to be read and discussed at the meeting.<o:p></o:p></p>
<p>My primary comment is that updating the SCCS-ARD is clearly a large undertaking, and I would like to congratulate John Pietras and Peter Shames for on the production of a quality document. It is difficult to absorb such a large swath of CCSDS standards and
integrate them into a helpful summary of the interfaces as this SCCS-ARD does.<o:p></o:p></p>
<p>My other comments primarily relate to the new VCM content. There are six main comments, with more detailed description, recommendation, and justification for each. These comments are written based on the latest SCCS-ARD, but I also repeat portions of my
June-23 comments if they were not yet addressed. I believe the SCCS-ARD will be much improved if we adopt these recommendations.<o:p></o:p></p>
<ol start="1" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo2">
The phrase "VCM suite" <o:p></o:p></li></ol>
<ol start="1" type="1">
<ol start="1" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level2 lfo2">
Description: This phrase is introduced in this SCCS-ARD. It occurs in Table 6-1, and throughout Section 6.1.2, Table 6-8, Table 6-12.
<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level2 lfo2">
Recommendation: Remove this phrase in all places and replace with "the VCM protocol."
<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level2 lfo2">
Justification <o:p></o:p></li></ol>
</ol>
<ol start="1" type="1">
<ol start="3" type="1">
<ol start="1" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level3 lfo2">
CCSDS does not have a "VCM suite" and I think it is a mistake to invent this new concept here, especially since it would risk confusing the reader into thinking that there is more than one VCM protocol.
<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level3 lfo2">
131.2 and 131.3 are not members of a supposed "VCM suite." They are not even the same kind of thing that 431.1 is. 431.1 is a protocol book, while 131.2 and 131.3 describes codes, modulation, and VCM.
<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level3 lfo2">
One VCM protocol. As we worked out in the C&S and RFM WGs at the time we negotiated the VCM protocol blue book (431.1-B-1), there is one VCM protocol that can be used with multiple sets of codes and modulations described in other blue books. There are some
variations and options in this protocol, but it is fundamentally one protocol that operates in the same way, namely, with a header signaled with pi/2-BPSK and protected with a specific RM code, followed by code symbols using a higher order modulation. This
is why the VCM blue book has the title "Variable Coded Modulation Protocol" with no plural word or "suite."
<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level3 lfo2">
In other words, the protocol is singular. What is plural is the set of VCM tables that can be used in conjunction with the protocol. Incidentally, in other areas CCSDS doesn't refer to a "code suite," or a "ranging suite" or a "frequencies suite" where there
are clearly multiple options. <o:p></o:p></li></ol>
</ol>
</ol>
<ol start="2" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo2">
Table 6-1 organization. <o:p></o:p></li></ol>
<ol start="2" type="1">
<ol start="1" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level2 lfo2">
Description: Table 6-1 lists three references for the VCM "Suite": 131.2, 131.3, and 431.1.
<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level2 lfo2">
Recommendation: put 131.2, 131.3, and 431.1 each on their own row of the table, using their Blue Book name, like the other rows of the table do.
<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level2 lfo2">
Justification <o:p></o:p></li></ol>
</ol>
<ol start="2" type="1">
<ol start="3" type="1">
<ol start="1" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level3 lfo2">
Books that are the same type of thing are treated differently in the table. <o:p>
</o:p></li></ol>
</ol>
</ol>
<ol start="2" type="1">
<ol start="3" type="1">
<ol start="1" type="1">
<ol start="1" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level4 lfo2">
As we know, there are 4 CCSDS coding standards that ingest TM/AOS/USLP frames (what we might previously call space-to-ground links): 131.0 (turbo/LDPC), 131.2 (SCCC), 131.3 (DVB-S2 LDPC), and 142.1 (SCPPM). These references should appear together in Table 6-1
in the same way, not with 131.0 in its own row and 131.2 and 131.3 relegated to a secondary category within "VCM suite." The SCCS-ARD should be about interfaces (in this case, ingestion of TM, AOS, or USLP Transfer Frames). Treating them differently in the
table doesn't make sense. <o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level4 lfo2">
In particular, Table 6-1 as written calls out 142.1 and 131.0 as "coding" books and 131.2 and 131.3 as members of a supposed "VCM suite." But 131.2 and 131.3 are primarily about the codes they define -- the SCCC codes and DVB-S2 LDPC codes. When C&S negotiated
their acceptance, the discussion was primarily about the coding performance, complexity, maturity, etc., and not their associated VCM approaches (which are nearly identical).
<o:p></o:p></li></ol>
</ol>
</ol>
</ol>
<ol start="2" type="1">
<ol start="3" type="1">
<ol start="2" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level3 lfo2">
Books that are different are treated as though they are the same in the table <o:p>
</o:p></li></ol>
</ol>
</ol>
<ol start="2" type="1">
<ol start="3" type="1">
<ol start="2" type="1">
<ol start="1" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level4 lfo2">
131.2, 131.3, and 431.1 cannot be listed as though they are the same type of thing
<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level4 lfo2">
431.1 is fundamentally different in structure from 131.2 and 131.3. 431.1 is the unifying description of the (one) CCSDS VCM protocol, and refers back to 131.2 and 131.3 in describing the differences of the two minor variations (types). Whereas 131.2 and 131.3
describe codes and modulations. <o:p></o:p></li></ol>
</ol>
</ol>
</ol>
<ol start="2" type="1">
<ol start="3" type="1">
<ol start="3" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level3 lfo2">
This would be consistent with the rest of the table. <o:p></o:p></li></ol>
</ol>
</ol>
<ol start="3" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo2">
Table 6-1 "space-to-ground links". <o:p></o:p></li></ol>
<ol start="3" type="1">
<ol start="1" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level2 lfo2">
Description: The table has a left-column heading labeled "Space-to-Ground Links."
<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level2 lfo2">
Recommendation: <o:p></o:p></li></ol>
</ol>
<ol start="3" type="1">
<ol start="2" type="1">
<ol start="1" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level3 lfo2">
Remove or reword "Space-to-Ground Links" <o:p></o:p></li></ol>
</ol>
</ol>
<ol start="3" type="1">
<ol start="3" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level2 lfo2">
Justification: <o:p></o:p></li></ol>
</ol>
<ol start="3" type="1">
<ol start="3" type="1">
<ol start="1" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level3 lfo2">
This may be outdated terminology, given our renewed interest in allowing a variety of link directions for the standards.
<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level3 lfo2">
Or, if we are keeping the concept of direction, why is the TC coding book listed in this category? Also, why is there no corresponding "Ground-to-Space Links" category?
<o:p></o:p></li></ol>
</ol>
</ol>
<ol start="4" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo2">
Figure 6-1 <o:p></o:p></li></ol>
<ol start="4" type="1">
<ol start="1" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level2 lfo2">
Description: Figure 6-1 shows boxes for TM sync and channel coding, VCM suite, and RF and modulation, with some lines between some of them.
<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level2 lfo2">
Recommendation: Revise the figure to include an "SCCC coding" box, a "DVB-S2 LDPC coding" (or similar) box, and redraw the VCM box to encompass those boxes as well as the "TM sync and channel coding" and "RF and Modulation" boxes. Also, update the lines to
make clear which frame types may enter each of the boxes on the coding sublayer.
<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level2 lfo2">
Justification: As drawn, this figure is not clear and bordering on inaccurate. <o:p>
</o:p></li></ol>
</ol>
<ol start="4" type="1">
<ol start="3" type="1">
<ol start="1" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level3 lfo2">
There is a box labeled VCM suite, presumably meant to include 131.2, 131.3, and 431.1 in this box. If so, then why is TM Sync And Channel Coding outside of this box? Why is RF and Modulation outside of this box? Those are specified as part of 431.1.
<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level3 lfo2">
It does not make sense for turbo/LDPC codes to get their own box in this figure, but not SCCC and DVB-S2 codes. These make the same type of specification at the same layer. Where SCCS-ARD can be of service is in explaining where the interfaces are the same
in the various books. <o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level3 lfo2">
VCM is a standard about both coding and modulation and so should be drawn to encompass the coding and modulation functions.
<o:p></o:p></li></ol>
</ol>
</ol>
<ol start="5" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo2">
Section 6.1.2.2.1 <o:p></o:p></li></ol>
<ol start="5" type="1">
<ol start="1" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level2 lfo2">
Description. This section: <o:p></o:p></li></ol>
</ol>
<ol start="5" type="1">
<ol start="1" type="1">
<ol start="1" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level3 lfo2">
States that the VCM suite is not a single protocol but rather three separate protocols, then says they are "very similar," and finally then says they are all subsumed into one, using the phrase "the VCM protocol."
<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level3 lfo2">
Refers to 131.2 and 131.3 as "VCM standards" <o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level3 lfo2">
Says that 431.1 subsumes the functionality of 131.2 and 131.3 <o:p></o:p></li></ol>
</ol>
</ol>
<ol start="5" type="1">
<ol start="2" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level2 lfo2">
Recommendation: Rewrite the paragraph from scratch to include these features <o:p>
</o:p></li></ol>
</ol>
<ol start="5" type="1">
<ol start="2" type="1">
<ol start="1" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level3 lfo2">
Refer to 131.0, 131.2, and 131.3 on equal footing as standards for turbo/LDPC, SCCC, and DVB-S2 LDPC codes, and a variety of modulations.
<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level3 lfo2">
Refer to 431.1 ("the VCM protocol") as allowing the codes specified in these three standards to be used with a common protocol with two variations called Type 1 and Type 2; and that the VCM protocol is easily updated to accommodate other codes and/or modulations
with the additional of new VCM tables. <o:p></o:p></li></ol>
</ol>
</ol>
<ol start="5" type="1">
<ol start="3" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level2 lfo2">
Justification: <o:p></o:p></li></ol>
</ol>
<ol start="5" type="1">
<ol start="3" type="1">
<ol start="1" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level3 lfo2">
As written, the paragraph is self-contradictory. The protocol cannot simultaneously be three separate things, two very similar things, and all subsumed into one thing.
<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level3 lfo2">
The simplicity of the concept of unifying VCM into a common protocol that can be used with SCCC, DVB-S2 and turbo/LDPC codes is missing from this paragraph.
<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level3 lfo2">
Saying 431.1 "subsumes" 131.2 and 131.3 makes it seem like 131.2 and 131.3 are not needed. They are needed, because they are what specifies the codes and modulations. 431.1
<i>refers</i> to 131.2 and 131.3. <o:p></o:p></li></ol>
</ol>
</ol>
<ol start="6" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo2">
Figure 6-2 <o:p></o:p></li></ol>
<ol start="6" type="1">
<ol start="1" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level2 lfo2">
Description. The figure purports to show component standards of "the VCM suite." <o:p>
</o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level2 lfo2">
Recommendation: <o:p></o:p></li></ol>
</ol>
<ol start="6" type="1">
<ol start="2" type="1">
<ol start="1" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level3 lfo2">
Remove this figure from the SCCS-ARD. <o:p></o:p></li></ol>
</ol>
</ol>
<ol start="6" type="1">
<ol start="3" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level2 lfo2">
Justification. This figure is unnecessary, redundant, artificially complex, misleading, and incomplete.
<o:p></o:p></li></ol>
</ol>
<ol start="6" type="1">
<ol start="3" type="1">
<ol start="1" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level3 lfo2">
Unnecessary <o:p></o:p></li></ol>
</ol>
</ol>
<ol start="6" type="1">
<ol start="3" type="1">
<ol start="1" type="1">
<ol start="1" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level4 lfo2">
There is no "VCM suite." <o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level4 lfo2">
The purpose of the SCCS-ARD is to explain how things fit together. But this figure purportedly shows three standards -- 131.2, 431.1, and 131.3 --
<i>that do not interact with each other</i> (there are no lines between the three main boxes)<i>.
</i>This makes it unnecessary for the SCCS-ARD to address. <o:p></o:p></li></ol>
</ol>
</ol>
</ol>
<ol start="6" type="1">
<ol start="3" type="1">
<ol start="2" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level3 lfo2">
Redundant, artificially complex <o:p></o:p></li></ol>
</ol>
</ol>
<ol start="6" type="1">
<ol start="3" type="1">
<ol start="2" type="1">
<ol start="1" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level4 lfo2">
No information would be lost if the 131.2 and 131.3 columns were deleted in their entirety. All of the SCCC encoding is shown within the middle (431) box, for example. This duplication is confusing and artificially adds complexity where there is none.
<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level4 lfo2">
The things that are common -- functions like slicing, ASM, modulation, pilot -- are drawn multiple times, giving the impression that they are different.
<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level4 lfo2">
There is so much stuff on this figure that it has been shrunk so that the font is 6 pts. This is not legible without zooming.
<o:p></o:p></li></ol>
</ol>
</ol>
</ol>
<ol start="6" type="1">
<ol start="3" type="1">
<ol start="3" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level3 lfo2">
Misleading <o:p></o:p></li></ol>
</ol>
</ol>
<ol start="6" type="1">
<ol start="3" type="1">
<ol start="3" type="1">
<ol start="1" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level4 lfo2">
The duplication mentioned above may confuse a reader into believing that there is more than one VCM protocol that applies to SCCC codes (similarly, for DVB-S2 codes). This is the opposite of what this figure should be doing.
<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level4 lfo2">
The slicer for DVB is shown within the ETSI standard, when it is really part of the CCSDS standard (131.3).
<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level4 lfo2">
The boxes labeled "variable coding and modulation" contain no coding and no modulation. I think you mean VCM control.
<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level4 lfo2">
The circle-plus notation in the figure is confusing. In other CCSDS standards, that notation means XOR, which is not what is going on here.
<o:p></o:p></li></ol>
</ol>
</ol>
</ol>
<ol start="6" type="1">
<ol start="3" type="1">
<ol start="4" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level3 lfo2">
Incomplete <o:p></o:p></li></ol>
</ol>
</ol>
<ol start="6" type="1">
<ol start="3" type="1">
<ol start="4" type="1">
<ol start="1" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level4 lfo2">
Few of the salient features of the VCM protocol are actually present in the figure. The VCM header is transmitted with pi/2-BPSK modulation, for example. The pilots are optional. The header has two parts, a sync marker and a signaling structure (PLS or frame
descriptor). The frame descriptor is protected with a (32,6) code. All of that is missing.
<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level4 lfo2">
The input to the "VCM suite" is not labeled. The interfaces are the most important part of showing how things fit together.
<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level4 lfo2">
The output of the "VCM suite" is not labeled. Again, that should be the important part.
<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level4 lfo2">
No VCM control is shown as an input to the TM codes. <o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level4 lfo2">
No VCM control is shown for the pilots. <o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level4 lfo2">
No VCM control is shown for the slicer. <o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level4 lfo2">
Arrows showing direction of flow are missing throughout. <o:p></o:p></li></ol>
</ol>
</ol>
</ol>
<p> ----Jon<o:p></o:p></p>
<div>
<p class="MsoNormal"><strong><span style="font-family:"Calibri",sans-serif">Jon Hamkins</span></strong><br>
Chief Technologist, Communications, Tracking, and Radar Division<br>
<strong><span style="font-family:"Calibri",sans-serif">O</span></strong> 818-354-4764 |
<strong><span style="font-family:"Calibri",sans-serif">M</span></strong> 626-658-6220<br>
<br>
<strong><span style="font-family:"Calibri",sans-serif">JPL</span></strong> | jpl.nasa.gov
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">On 11/10/2021 11:58 PM, <a href="mailto:Andrea.Modenini@esa.int">
Andrea.Modenini@esa.int</a> wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">FYI</span>
<br>
<br>
<b><span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:gray">ESA - European Space Agency</span></b>
<br>
<b><span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:#00A1E0">Ph.D. Andrea Modenini</span></b><b><span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:gray"><br>
TT&C Communications Systems Engineer</span></b><b><span style="font-size:12.0pt;font-family:"Tms Rmn",serif">
</span></b><span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:gray"><br>
TT&C and PDT Systems & Techniques Section (TEC-EST)<br>
RF Systems Division<b><br>
ESTEC</b><br>
Keplerlaan 1, PO Box 299<br>
NL-2200 AG Noordwijk, The Netherlands</span><u><span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:blue"><br>
</span></u><span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:gray"><a href="mailto:andrea.modenini@esa.int">andrea.modenini@esa.int</a> |
</span><a href="https://urldefense.us/v3/__http:/www.esa.int/__;!!PvBDto6Hs4WbVuu7!c_W6kQBKFsU715uHT0ZbEI-Zxyzva6CZAw_475CJiUtC49HEKgcsDEvKn5iiAOkOz9Y62n8$"><span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:#8F8F8F">www.esa.int</span></a><span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:gray"><br>
T +31 71 56 53439, M +31 6 484 56 527</span> <br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:purple">----- Forwarded by Andrea Modenini/estec/ESA on 11-11-21 08:57 -----</span>
<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">"Shames, Peter M\(US 312B\) via CESG-All"
<a href="mailto:cesg-all@mailman.ccsds.org"><cesg-all@mailman.ccsds.org></a></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">"CCSDS Engineering Steering Group - CESG All"
<a href="mailto:cesg-all@mailman.ccsds.org"><cesg-all@mailman.ccsds.org></a></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">"EXTERNAL-Pietras, John V\(US 332C-Affiliate\)"
<a href="mailto:john.pietras@gst.com"><john.pietras@gst.com></a>, "SEA-SA" <a href="mailto:sea-sa@mailman.ccsds.org">
<sea-sa@mailman.ccsds.org></a></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">10-11-21 23:55</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">[Cesg-all] FW: [EXTERNAL] WebEx meeting invitation: SCCS-ARD update review scheduled for Tuesday,
23 Nov, 2021 at 0700 AM PST</span> <br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Sent by: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"CESG-All"
<a href="mailto:cesg-all-bounces@mailman.ccsds.org"><cesg-all-bounces@mailman.ccsds.org></a></span>
<o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="0" width="100%" noshade="" style="color:#A0A0A0" align="center">
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"> <o:p></o:p></p>
<p style="margin:0in">Dear CCSDS AD and WG chairs,<o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in">The review of the SCCS-ARD has been scheduled for Tuesday, 23 Nov, 2021 at 0700 AM PST. The draft of the document, which is in rough, “track changes”, form is available on-line. The proposed updates to the ABA subsections of sections
4, 5, and 6 (except for the security-specific subsections) and posted the draft to the CWE at:<o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in"><a href="https://urldefense.us/v3/__https:/cwe.ccsds.org/sea/docs/SEA-SA/Draft*20Documents/SCCS-ARD-ADD*20Revisions*202020/SCCS-ARD*20draft*20documents/SCCS-ARD-901x1p1_10-211108.doc?d=wd389d0c8026d47a591fbc35f2e261b58__;JSUlJSU!!PvBDto6Hs4WbVuu7!YAgXpQsrLJbeeQgotEG0WUNrvYYDosRiqy6GyJr5YS38sxD0qn-wbyDWHlnAyZkngUHY_hIq$"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#813F62">https://cwe.ccsds.org/sea/docs/SEA-SA/Draft%20Documents/SCCS-ARD-ADD%20Revisions%202020/SCCS-ARD%20draft%20documents/SCCS-ARD-901x1p1_10-211108.doc?d=wd389d0c8026d47a591fbc35f2e261b58</span></a><o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in">Feel free to download this and review the sections that are of interest most interest to you (or all of it if you wish). If there are members of your WG who can usefully contribute to this review please feel free to invite them as well.<o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in">The Space Communications Cross Support Architecture document (SCCS-ARD) is a cross-cutting Magenta Book that largely covers the SLS, SIS, CSS, and SEA areas and their working groups. We have being working on an update to this document
that primarily covers what are called “ABA” mission configurations, which are those that involve a single mission ops center, a single spacecraft, and a ground station. The Solar System Internet (SSI) configurations, which involve multiple spacecraft, mission
centers, and comm assets, and use the DTN (or IP) protocols, will be in a future update that builds on this foundation.<o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in">There have been a number of changes to the CCSDS standards landscape since the last edition was published. These include:<o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<ol start="1" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l3 level1 lfo3">
USLP protocol <o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l3 level1 lfo3">
The “VCM suite” of variable coding and modulation standards <o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l3 level1 lfo3">
New CSTS services <o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l3 level1 lfo3">
New Service Management standards <o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l3 level1 lfo3">
Updates to the Synch and Channel coding specs, the liberal approaches <o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l3 level1 lfo3">
New security features in several sections <o:p></o:p></li></ol>
<p class="MsoNormal"> <o:p></o:p></p>
<p style="margin:0in">In addition to these new / updated standards we wish to address the following issues as well:<o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<ol start="1" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo4">
Improved handling of cross references from the Services viewpoint to the protocol stack details (interface binding signatures)
<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo4">
Revised section structures and cross referencing <o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo4">
Inclusion of “recommended” options and clarification of optional and mandatory features
<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo4">
Discussion of incomplete / optional capabilities like forward file service, handling of details of complexities like MAP service and VC/MC multiplexing, COP on the USLP return link, and CADUs in FF-CSTS given new Pseudo-randomized “Only Idle Data” (OID) frames
<o:p></o:p></li></ol>
<p class="MsoNormal"> <o:p></o:p></p>
<p style="margin:0in">Hope to see you at this review.<o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in">Thanks, Peter Shames & John Pietras<o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in"><b><span style="font-size:12.0pt">From: </span></b><span style="font-size:12.0pt">Peter Shames
<a href="mailto:messenger@webex.com"><messenger@webex.com></a><b><br>
Reply-To: </b>Peter Shames <a href="mailto:peter.m.shames@jpl.nasa.gov"><peter.m.shames@jpl.nasa.gov></a><b><br>
Date: </b>Thursday, November 4, 2021 at 3:07 PM<b><br>
To: </b>Peter Shames <a href="mailto:peter.m.shames@jpl.nasa.gov"><peter.m.shames@jpl.nasa.gov></a><b><br>
Subject: </b>[EXTERNAL] (Forward to others) WebEx meeting invitation: SCCS-ARD update review</span><o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" align="left" width="100%" style="width:100.0%;border-collapse:collapse;margin-bottom:5.75pt">
<tbody>
<tr style="height:6.0pt">
<td width="100%" style="width:100.0%;padding:0in 0in 0in 0in;height:6.0pt">
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" align="left" width="525" style="width:393.75pt;border-collapse:collapse;margin-bottom:5.75pt">
<tbody>
<tr style="height:6.0pt">
<td width="525" valign="top" style="width:393.75pt;padding:0in 0in 0in 0in;height:6.0pt">
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="100%" style="width:100.0%;border-collapse:collapse">
<tbody>
<tr style="height:6.0pt">
<td width="100%" style="width:100.0%;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal" style="line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<span style="font-size:12.0pt;line-height:106%;font-family:"Arial",sans-serif;color:#5F5F5F">You can forward this invitation to others.
</span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p style="margin:0in;line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<span style="font-size:12.0pt;line-height:106%;font-family:"Arial",sans-serif;color:#5F5F5F"> </span><o:p></o:p></p>
<p class="MsoNormal" style="line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<o:p></o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="525" style="width:393.75pt;border-collapse:collapse">
<tbody>
<tr style="height:6.0pt">
<td width="525" style="width:393.75pt;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal" style="line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<span style="font-size:12.0pt;line-height:106%;font-family:"Arial",sans-serif;color:#4F4F4F">Hello,
</span><o:p></o:p></p>
</td>
</tr>
<tr style="height:6.0pt">
<td width="525" style="width:393.75pt;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal" style="line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<span style="font-size:12.0pt;line-height:106%;font-family:"Arial",sans-serif;color:#4F4F4F">Peter Shames invites you to join this WebEx meeting.
</span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p style="margin:0in;line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<span style="font-size:12.0pt;line-height:106%;font-family:"Arial",sans-serif;color:#5F5F5F"> </span><o:p></o:p></p>
<p class="MsoNormal" style="line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<o:p></o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="525" style="width:393.75pt;border-collapse:collapse">
<tbody>
<tr style="height:6.0pt">
<td width="525" style="width:393.75pt;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal" style="line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<span style="font-size:12.0pt;line-height:106%;font-family:"Arial",sans-serif;color:#5F5F5F"> </span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p style="margin:0in;line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<span style="font-size:12.0pt;line-height:106%;font-family:"Arial",sans-serif;color:#5F5F5F"> </span><o:p></o:p></p>
<p class="MsoNormal" style="line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<o:p></o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="100%" style="width:100.0%;border-collapse:collapse">
<tbody>
<tr style="height:6.0pt">
<td width="100%" style="width:100.0%;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal" style="line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<b><span style="font-size:12.0pt;line-height:106%;font-family:"Arial",sans-serif;color:#4F4F4F">SCCS-ARD update review</span></b><o:p></o:p></p>
</td>
</tr>
<tr style="height:6.0pt">
<td style="padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal" style="line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<span style="font-size:12.0pt;line-height:106%;font-family:"Arial",sans-serif;color:#5F5F5F">Tuesday, November 23, 2021
</span><o:p></o:p></p>
</td>
</tr>
<tr style="height:6.0pt">
<td style="padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal" style="line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<span style="font-size:12.0pt;line-height:106%;font-family:"Arial",sans-serif;color:#5F5F5F">7:00 AM | (UTC-07:00) Pacific Time (US & Canada) | 1 hr 30 mins
</span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p style="margin:0in;line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<span style="font-size:12.0pt;line-height:106%;font-family:"Arial",sans-serif;color:#5F5F5F"> </span><o:p></o:p></p>
<p class="MsoNormal" style="line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<o:p></o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="334" style="width:250.5pt;border-collapse:collapse">
<tbody>
<tr style="height:6.0pt">
<td width="334" style="width:250.5pt;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal" style="line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<span style="font-size:12.0pt;line-height:106%;font-family:"Arial",sans-serif;color:#5F5F5F">Meeting number (access code): 2761 585 8804
</span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p style="margin:0in;line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<span style="font-size:12.0pt;line-height:106%;font-family:"Arial",sans-serif;color:#5F5F5F"> </span><o:p></o:p></p>
<p class="MsoNormal" style="line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<o:p></o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="243" style="width:182.25pt;border-collapse:collapse">
<tbody>
<tr style="height:6.0pt">
<td width="243" style="width:182.25pt;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal" style="line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<span style="font-size:12.0pt;line-height:106%;font-family:"Arial",sans-serif;color:#5F5F5F">Meeting password: 9JRpYBGHp72</span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:2.5in;margin-left:0in;line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<span style="font-size:12.0pt;line-height:106%;font-family:"Arial",sans-serif;color:#5F5F5F"> </span><o:p></o:p></p>
<p class="MsoNormal" style="line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<o:p></o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="525" style="width:393.75pt;border-collapse:collapse">
<tbody>
<tr style="height:6.0pt">
<td width="525" style="width:393.75pt;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal" style="line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<span style="font-size:12.0pt;line-height:106%;font-family:"Arial",sans-serif;color:#5F5F5F"> </span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p style="margin:0in;line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<span style="font-size:12.0pt;line-height:106%;font-family:"Arial",sans-serif;color:#5F5F5F"> </span><o:p></o:p></p>
<p class="MsoNormal" style="line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<o:p></o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="116" style="width:87.0pt;border-collapse:collapse">
<tbody>
<tr style="height:6.0pt">
<td width="116" style="width:87.0pt;padding:0in 0in 0in 0in;height:6.0pt">
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="117" style="width:87.75pt;border-collapse:collapse">
<tbody>
<tr style="height:6.0pt">
<td width="111" style="width:83.25pt;border:ridge #00823B 2.25pt;background:#00823B;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal" align="center" style="text-align:center;line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<span style="color:black"><a href="https://jpl.webex.com/jpl/j.php?MTID=m19aa1606d8ed2742fa89cd2d8d4b0afa"><span style="font-size:15.0pt;line-height:106%;font-family:"Arial",sans-serif;color:white">Join meeting</span></a></span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
<p style="margin:0in;line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<span style="font-size:12.0pt;line-height:106%;font-family:"Arial",sans-serif;color:#5F5F5F"> </span><o:p></o:p></p>
<p class="MsoNormal" style="line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<o:p></o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="525" style="width:393.75pt;border-collapse:collapse">
<tbody>
<tr style="height:6.0pt">
<td width="525" style="width:393.75pt;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal" style="line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<span style="font-size:12.0pt;line-height:106%;font-family:"Arial",sans-serif;color:#5F5F5F"> </span>
<o:p></o:p></p>
</td>
</tr>
<tr style="height:6.0pt">
<td width="525" style="width:393.75pt;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal" style="line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<b><span style="font-family:"Arial",sans-serif">More ways to join:</span></b><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p style="margin:0in;line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<span style="font-size:12.0pt;line-height:106%;font-family:"Arial",sans-serif;color:#5F5F5F"> </span><o:p></o:p></p>
<p class="MsoNormal" style="line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<o:p></o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="525" style="width:393.75pt;border-collapse:collapse">
<tbody>
<tr style="height:6.0pt">
<td width="525" style="width:393.75pt;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal" style="line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<span style="font-size:12.0pt;line-height:106%;font-family:"Arial",sans-serif;color:#5F5F5F"> </span>
<o:p></o:p></p>
</td>
</tr>
<tr style="height:6.0pt">
<td width="525" style="width:393.75pt;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal" style="line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<b><span style="font-size:9.0pt;line-height:106%;font-family:"Arial",sans-serif">Join from the meeting link</span></b>
<o:p></o:p></p>
</td>
</tr>
<tr style="height:6.0pt">
<td width="525" style="width:393.75pt;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal" style="line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<a href="https://jpl.webex.com/jpl/j.php?MTID=m19aa1606d8ed2742fa89cd2d8d4b0afa" target="_blank"><span style="font-family:"Arial",sans-serif;color:#006062">https://jpl.webex.com/jpl/j.php?MTID=m19aa1606d8ed2742fa89cd2d8d4b0afa</span></a><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p style="margin:0in;line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<span style="font-size:12.0pt;line-height:106%;font-family:"Arial",sans-serif;color:#5F5F5F"> </span><o:p></o:p></p>
<p class="MsoNormal" style="line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<o:p></o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="525" style="width:393.75pt;border-collapse:collapse">
<tbody>
<tr style="height:6.0pt">
<td width="525" style="width:393.75pt;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal" style="line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<span style="font-size:12.0pt;line-height:106%;font-family:"Arial",sans-serif;color:#5F5F5F"> </span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p style="margin:0in;line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<span style="font-size:12.0pt;line-height:106%;font-family:"Arial",sans-serif;color:#5F5F5F"> </span><o:p></o:p></p>
<p class="MsoNormal" style="line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<o:p></o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="525" style="width:393.75pt;border-collapse:collapse">
<tbody>
<tr style="height:6.0pt">
<td width="525" style="width:393.75pt;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal" style="line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<span style="font-size:12.0pt;line-height:106%;font-family:"Arial",sans-serif;color:#5F5F5F"> </span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p style="margin:0in;line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<span style="font-size:12.0pt;line-height:106%;font-family:"Arial",sans-serif;color:#5F5F5F"> </span><o:p></o:p></p>
<p class="MsoNormal" style="line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<o:p></o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="525" style="width:393.75pt;border-collapse:collapse">
<tbody>
<tr style="height:6.0pt">
<td width="525" style="width:393.75pt;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal" style="line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<b><span style="font-size:9.0pt;line-height:106%;font-family:"Arial",sans-serif">Join from a video system or application</span></b>
<o:p></o:p></p>
</td>
</tr>
<tr style="height:6.0pt">
<td width="525" style="width:393.75pt;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal" style="line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<span style="font-family:"Arial",sans-serif;color:#2F2F2F">Dial </span><a href="%20sip:27615858804@jpl.webex.com"><span style="font-size:12.0pt;line-height:106%;font-family:"Arial",sans-serif;color:#006062">27615858804@jpl.webex.com</span></a>
<o:p></o:p></p>
</td>
</tr>
<tr style="height:6.0pt">
<td width="525" style="width:393.75pt;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal" style="line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<span style="font-family:"Arial",sans-serif;color:#2F2F2F">You can also dial 207.182.190.20 and enter your meeting number.</span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p style="margin:0in;line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<span style="font-size:12.0pt;line-height:106%;font-family:"Arial",sans-serif;color:#5F5F5F"> </span><o:p></o:p></p>
<p class="MsoNormal" style="line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<o:p></o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="525" style="width:393.75pt;border-collapse:collapse">
<tbody>
<tr style="height:6.0pt">
<td width="525" style="width:393.75pt;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal" style="line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<b><span style="font-size:9.0pt;line-height:106%;font-family:"Arial",sans-serif">Join by phone</span></b>
<o:p></o:p></p>
</td>
</tr>
<tr style="height:6.0pt">
<td width="525" style="width:393.75pt;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal" style="line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<span style="font-family:"Arial",sans-serif;color:#2F2F2F">+1-510-210-8882 USA Toll</span>
<o:p></o:p></p>
</td>
</tr>
<tr style="height:6.0pt">
<td width="525" style="width:393.75pt;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal" style="line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<span style="font-family:"Arial",sans-serif;color:#2F2F2F">+44-203-457-5798 U.K. Toll</span>
<o:p></o:p></p>
</td>
</tr>
<tr style="height:6.0pt">
<td width="525" style="width:393.75pt;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal" style="line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<a href="https://jpl.webex.com/jpl/globalcallin.php?MTID=m5e38422f279e390de6b43d836a8711d0"><span style="font-family:"Arial",sans-serif;color:#006062">Global call-in numbers</span></a><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p style="margin:0in;line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<span style="font-size:12.0pt;line-height:106%;font-family:"Arial",sans-serif;color:#5F5F5F"> </span><o:p></o:p></p>
<p class="MsoNormal" style="line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<o:p></o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="525" style="width:393.75pt;border-collapse:collapse">
<tbody>
<tr style="height:6.0pt">
<td width="525" style="width:393.75pt;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal" style="line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<span style="font-size:12.0pt;line-height:106%;font-family:"Arial",sans-serif;color:#5F5F5F"> </span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p style="margin:0in;line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<span style="font-size:12.0pt;line-height:106%;font-family:"Arial",sans-serif;color:#5F5F5F"> </span><o:p></o:p></p>
<p class="MsoNormal" style="line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<o:p></o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="525" style="width:393.75pt;border-collapse:collapse">
<tbody>
<tr style="height:6.0pt">
<td width="525" style="width:393.75pt;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal" style="line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<b><span style="font-size:12.0pt;line-height:106%;font-family:"Arial",sans-serif;color:#5F5F5F">Local: 818-35(4-4044)</span></b><o:p></o:p></p>
</td>
</tr>
<tr style="height:6.0pt">
<td width="525" style="width:393.75pt;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal" style="line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<b><span style="font-size:12.0pt;line-height:106%;font-family:"Arial",sans-serif;color:#5F5F5F">Toll Free: 844-JPL-WEBX (844-575-9329)</span></b><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p style="margin:0in;line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<span style="font-size:12.0pt;line-height:106%;font-family:"Arial",sans-serif;color:#5F5F5F"> </span><o:p></o:p></p>
<p class="MsoNormal" style="line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<o:p></o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="525" style="width:393.75pt;border-collapse:collapse">
<tbody>
<tr style="height:6.0pt">
<td width="525" style="width:393.75pt;padding:0in 0in 0in 0in;height:6.0pt">
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="525" style="width:393.75pt;border-collapse:collapse">
<tbody>
<tr style="height:6.0pt">
<td width="525" style="width:393.75pt;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal" style="line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<span style="font-size:12.0pt;line-height:106%;font-family:"Arial",sans-serif;color:#5F5F5F"> </span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p style="margin:0in;line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<span style="font-size:10.0pt;line-height:106%;font-family:"Arial",sans-serif;color:#5F5F5F">Can't join the meeting?
</span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p style="margin:0in;line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<span style="font-size:12.0pt;line-height:106%;font-family:"Arial",sans-serif;color:#5F5F5F"> </span><o:p></o:p></p>
<p class="MsoNormal" style="line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<o:p></o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="525" style="width:393.75pt;border-collapse:collapse">
<tbody>
<tr style="height:6.0pt">
<td width="525" style="width:393.75pt;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal" style="line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<span style="font-size:12.0pt;line-height:106%;font-family:"Arial",sans-serif;color:#5F5F5F"> </span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p style="margin:0in;line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<span style="font-size:12.0pt;line-height:106%;font-family:"Arial",sans-serif;color:#5F5F5F"> </span><o:p></o:p></p>
<p class="MsoNormal" style="line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<o:p></o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="525" style="width:393.75pt;border-collapse:collapse">
<tbody>
<tr style="height:6.0pt">
<td width="525" style="width:393.75pt;padding:0in 0in 0in 0in;height:6.0pt">
<p class="MsoNormal" style="line-height:106%;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<span style="font-size:9.0pt;line-height:106%;font-family:"Arial",sans-serif;color:#A2A2A2">IMPORTANT NOTICE: Please note that this Webex service allows audio and other information sent during the session to be recorded, which may be discoverable in a legal
matter. By joining this session, you automatically consent to such recordings. If you do not consent to being recorded, discuss your concerns with the host or do not join the session.</span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
<p style="margin:0in"><span style="color:white"> [attachment "Webex_Meeting.ics" </span>
deleted by Andrea Modenini/estec/ESA] <tt><span style="font-size:10.0pt">_______________________________________________</span></tt><span style="font-size:10.0pt;font-family:"Courier New ,serif",serif"><br>
</span><tt><span style="font-size:10.0pt">CESG-All mailing list</span></tt><span style="font-size:10.0pt;font-family:"Courier New ,serif",serif"><br>
</span><tt><span style="font-size:10.0pt"><a href="mailto:CESG-All@mailman.ccsds.org">CESG-All@mailman.ccsds.org</a></span></tt><span style="font-size:10.0pt;font-family:"Courier New ,serif",serif"><br>
</span><a href="https://urldefense.us/v3/__https:/mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg-all__;!!PvBDto6Hs4WbVuu7!c_W6kQBKFsU715uHT0ZbEI-Zxyzva6CZAw_475CJiUtC49HEKgcsDEvKn5iiAOkOJm26tok$"><tt><span style="font-size:10.0pt">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg-all</span></tt></a><o:p></o:p></p>
<pre>This message is intended only for the recipient(s) named above. It may contain proprietary information and/or<o:p></o:p></pre>
<pre>protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received<o:p></o:p></pre>
<pre>this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect<o:p></o:p></pre>
<pre>personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (<a href="mailto:dpo@esa.int">dpo@esa.int</a>).<o:p></o:p></pre>
<p class="MsoNormal"><br>
<br>
<br>
<br>
<o:p></o:p></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>SLS-CC mailing list<o:p></o:p></pre>
<pre><a href="mailto:SLS-CC@mailman.ccsds.org">SLS-CC@mailman.ccsds.org</a><o:p></o:p></pre>
<pre><a href="https://urldefense.us/v3/__https:/mailman.ccsds.org/cgi-bin/mailman/listinfo/sls-cc__;!!PvBDto6Hs4WbVuu7!c_W6kQBKFsU715uHT0ZbEI-Zxyzva6CZAw_475CJiUtC49HEKgcsDEvKn5iiAOkOmu4K-Qo$">https://urldefense.us/v3/__https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sls-cc__;!!PvBDto6Hs4WbVuu7!c_W6kQBKFsU715uHT0ZbEI-Zxyzva6CZAw_475CJiUtC49HEKgcsDEvKn5iiAOkOmu4K-Qo$</a> <o:p></o:p></pre>
</blockquote>
</blockquote>
</blockquote>
</div>
</body>
</html>