<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<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.<br>
</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.<br>
</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.<br>
</p>
<ul>
<li>The phrase "VCM suite"</li>
<ul>
<li>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.</li>
<li>Recommendation: Remove this phrase in all places and replace
with "the VCM protocol."<br>
</li>
<li>Justification</li>
<ul>
<li>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.<br>
</li>
<li>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.<br>
</li>
<li>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."</li>
<li>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.</li>
</ul>
</ul>
<li>Table 6-1 organization.<br>
</li>
<ul>
<li>Description: Table 6-1 lists three references for the VCM
"Suite": 131.2, 131.3, and 431.1.</li>
<li>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.<br>
</li>
<li>Justification</li>
<ul>
<li>Books that are the same type of thing are treated
differently in the table.</li>
<ul>
<li>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.</li>
<li>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).<br>
</li>
</ul>
<li>Books that are different are treated as though they are
the same in the table</li>
<ul>
<li>131.2, 131.3, and 431.1 cannot be listed as though they
are the same type of thing<br>
</li>
<li>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.<br>
</li>
</ul>
<li>This would be consistent with the rest of the table.</li>
</ul>
</ul>
<li>Table 6-1 "space-to-ground links".</li>
<ul>
<li>Description: The table has a left-column heading labeled
"Space-to-Ground Links." <br>
</li>
<li>Recommendation:</li>
<ul>
<li>Remove or reword "Space-to-Ground Links"</li>
</ul>
<li>Justification:</li>
<ul>
<li>This may be outdated terminology, given our renewed
interest in allowing a variety of link directions for the
standards.</li>
<li>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?<br>
</li>
</ul>
</ul>
<li>Figure 6-1</li>
<ul>
<li>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.<br>
</li>
<li>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.<br>
</li>
<li>Justification: As drawn, this figure is not clear and
bordering on inaccurate.</li>
<ul>
<li>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.<br>
</li>
<li>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.<br>
</li>
<li>VCM is a standard about both coding and modulation and so
should be drawn to encompass the coding and modulation
functions.</li>
</ul>
</ul>
<li>Section 6.1.2.2.1</li>
<ul>
<li>Description. This section:<br>
</li>
<ul>
<li>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."</li>
<li>Refers to 131.2 and 131.3 as "VCM standards"<br>
</li>
<li>Says that 431.1 subsumes the functionality of 131.2 and
131.3</li>
</ul>
<li>Recommendation: Rewrite the paragraph from scratch to
include these features</li>
<ul>
<li>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.<br>
</li>
<li>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.</li>
</ul>
<li>Justification:</li>
<ul>
<li>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.</li>
<li>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.</li>
<li>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.</li>
</ul>
</ul>
<li>Figure 6-2</li>
<ul>
<li>Description. The figure purports to show component standards
of "the VCM suite."<br>
</li>
<li>Recommendation:</li>
<ul>
<li>Remove this figure from the SCCS-ARD.</li>
</ul>
<li>Justification. This figure is unnecessary, redundant,
artificially complex, misleading, and incomplete.<br>
</li>
<ul>
<li>Unnecessary</li>
<ul>
<li>There is no "VCM suite."</li>
<li>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.</li>
</ul>
<li>Redundant, artificially complex<br>
</li>
<ul>
<li>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.</li>
<li>The things that are common -- functions like slicing,
ASM, modulation, pilot -- are drawn multiple times, giving
the impression that they are different.</li>
<li>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.</li>
</ul>
<li>Misleading<br>
</li>
<ul>
<li>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.</li>
<li>The slicer for DVB is shown within the ETSI standard,
when it is really part of the CCSDS standard (131.3).</li>
<li>The boxes labeled "variable coding and modulation"
contain no coding and no modulation. I think you mean VCM
control.<br>
</li>
<li>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.</li>
</ul>
<li>Incomplete<br>
</li>
<ul>
<li>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.</li>
<li>The input to the "VCM suite" is not labeled. The
interfaces are the most important part of showing how
things fit together.<br>
</li>
<li>The output of the "VCM suite" is not labeled. Again,
that should be the important part.</li>
<li>No VCM control is shown as an input to the TM codes.</li>
<li>No VCM control is shown for the pilots.</li>
<li>No VCM control is shown for the slicer.<br>
</li>
<li>Arrows showing direction of flow are missing throughout.</li>
</ul>
</ul>
</ul>
</ul>
<p> ----Jon<br>
</p>
<div class="moz-signature"><strong>Jon Hamkins</strong><br>
Chief Technologist, Communications, Tracking, and Radar Division<br>
<strong>O</strong> 818-354-4764 | <strong>M</strong>
626-658-6220<br>
<br>
<strong>JPL</strong> | jpl.nasa.gov <br>
</div>
<div class="moz-cite-prefix">On 11/10/2021 11:58 PM,
<a class="moz-txt-link-abbreviated" href="mailto:Andrea.Modenini@esa.int">Andrea.Modenini@esa.int</a> wrote:<br>
</div>
<blockquote type="cite"
cite="mid:21368_1636617486_618CCD0E_21368_1301_1_OF9AC517EF.566F3E1E-ONC125878A.002BC16B-C125878A.002BC55E@esa.int">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<span style=" font-size:10pt;font-family:sans-serif">FYI</span>
<br>
<br>
<span style=" font-size:8pt;color:#808080;font-family:Verdana"><b>ESA
- European Space Agency</b></span>
<br>
<span style=" font-size:8pt;color:#00a1e0;font-family:Verdana"><b>Ph.D.
Andrea Modenini</b></span><span style="
font-size:8pt;color:#808080;font-family:Verdana"><b><br>
TT&C Communications Systems Engineer</b></span><span
style=" font-size:12pt;font-family:Tms Rmn"><b>
</b></span><span style="
font-size:8pt;color:#808080;font-family:Verdana"><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><span style="
font-size:8pt;color:blue;font-family:Verdana"><u><br>
</u></span><span style="
font-size:8pt;color:#808080;font-family:Verdana"><a class="moz-txt-link-abbreviated" 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$"
moz-do-not-send="true"><span style="
font-size:8pt;color:#8f8f8f;font-family:Verdana"><u>www.esa.int</u></span></a><span
style=" font-size:8pt;color:#808080;font-family:Verdana"><br>
T +31 71 56 53439, M +31 6 484 56 527</span>
<br>
<span style=" font-size:9pt;color:#800080;font-family:sans-serif">-----
Forwarded by Andrea Modenini/estec/ESA on 11-11-21 08:57 -----</span>
<br>
<br>
<span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">From:
</span><span style="
font-size:9pt;font-family:sans-serif">"Shames,
Peter M\(US 312B\) via CESG-All"
<a class="moz-txt-link-rfc2396E" href="mailto:cesg-all@mailman.ccsds.org"><cesg-all@mailman.ccsds.org></a></span>
<br>
<span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">To:
</span><span style="
font-size:9pt;font-family:sans-serif">"CCSDS
Engineering Steering Group - CESG All"
<a class="moz-txt-link-rfc2396E" href="mailto:cesg-all@mailman.ccsds.org"><cesg-all@mailman.ccsds.org></a></span>
<br>
<span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Cc:
</span><span style="
font-size:9pt;font-family:sans-serif">"EXTERNAL-Pietras,
John V\(US 332C-Affiliate\)" <a class="moz-txt-link-rfc2396E" href="mailto:john.pietras@gst.com"><john.pietras@gst.com></a>,
"SEA-SA"
<a class="moz-txt-link-rfc2396E" href="mailto:sea-sa@mailman.ccsds.org"><sea-sa@mailman.ccsds.org></a></span>
<br>
<span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Date:
</span><span style="
font-size:9pt;font-family:sans-serif">10-11-21
23:55</span>
<br>
<span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Subject:
</span><span style="
font-size:9pt;font-family: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:9pt;color:#5f5f5f;font-family:sans-serif">Sent
by: </span><span style="
font-size:9pt;font-family:sans-serif">"CESG-All"
<a class="moz-txt-link-rfc2396E" href="mailto:cesg-all-bounces@mailman.ccsds.org"><cesg-all-bounces@mailman.ccsds.org></a></span>
<br>
<hr noshade="noshade">
<br>
<br>
<p style="margin-top:0px;margin-Bottom:0px"><span style="
font-size:11pt;font-family:Calibri">Dear
CCSDS AD and WG chairs,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style="
font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style="
font-size:11pt;font-family:Calibri">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:</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style="
font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><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$"
moz-do-not-send="true"><span style="
font-size:12pt;color:#813f62;font-family:Arial"><u>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</u></span></a></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style="
font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style="
font-size:11pt;font-family:Calibri">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.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style="
font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style="
font-size:11pt;font-family:Calibri">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.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style="
font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style="
font-size:11pt;font-family:Calibri">There
have been a number of changes to the CCSDS standards landscape
since the
last edition was published. These include:</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style="
font-size:11pt;font-family:Calibri"> </span></p>
<ul>
<li><span style=" font-size:11pt;font-family:Calibri">USLP
protocol</span>
</li>
<li><span style=" font-size:11pt;font-family:Calibri">The “VCM
suite”
of variable coding and modulation standards</span>
</li>
<li><span style=" font-size:11pt;font-family:Calibri">New CSTS
services</span>
</li>
<li><span style=" font-size:11pt;font-family:Calibri">New
Service Management
standards</span>
</li>
<li><span style=" font-size:11pt;font-family:Calibri">Updates to
the Synch
and Channel coding specs, the liberal approaches</span>
</li>
<li><span style=" font-size:11pt;font-family:Calibri">New
security features
in several sections</span></li>
</ul>
<span style=" font-size:11pt;font-family:Calibri"> </span>
<p style="margin-top:0px;margin-Bottom:0px"><span style="
font-size:11pt;font-family:Calibri">In
addition to these new / updated standards we wish to address
the following
issues as well:</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style="
font-size:11pt;font-family:Calibri"> </span></p>
<ul>
<li><span style=" font-size:11pt;font-family:Calibri">Improved
handling
of cross references from the Services viewpoint to the
protocol stack details
(interface binding signatures)</span>
</li>
<li><span style=" font-size:11pt;font-family:Calibri">Revised
section structures
and cross referencing</span>
</li>
<li><span style=" font-size:11pt;font-family:Calibri">Inclusion
of “recommended”
options and clarification of optional and mandatory features</span>
</li>
<li><span style=" font-size:11pt;font-family:Calibri">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</span></li>
</ul>
<span style=" font-size:11pt;font-family:Calibri"> </span>
<p style="margin-top:0px;margin-Bottom:0px"><span style="
font-size:11pt;font-family:Calibri">Hope
to see you at this review.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style="
font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style="
font-size:11pt;font-family:Calibri">Thanks,
Peter Shames & John Pietras</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style="
font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style="
font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style="
font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style="
font-size:12pt;font-family:Calibri"><b>From:
</b>Peter Shames <a class="moz-txt-link-rfc2396E" href="mailto:messenger@webex.com"><messenger@webex.com></a><b><br>
Reply-To: </b>Peter Shames
<a class="moz-txt-link-rfc2396E" 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 class="moz-txt-link-rfc2396E" 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></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style="
font-size:11pt;font-family:Calibri"> </span></p>
<br>
<table style="border-collapse:collapse;" width="100%" align="left">
<tbody>
<tr height="8">
<td style="border-style:none none none
none;border-color:#000000;border-width:0px 0px 0px
0px;padding:0px 0px;" width="100%">
<table style="border-collapse:collapse;" width="525"
align="left">
<tbody>
<tr valign="top" height="8">
<td style="border-style:none none none
none;border-color:#000000;border-width:0px 0px 0px
0px;padding:0px 0px;" width="525">
<table style="border-collapse:collapse;"
width="100%">
<tbody>
<tr height="8">
<td style="border-style:none none none
none;border-color:#000000;border-width:0px
0px 0px 0px;padding:0px 0px;" width="100%"><span
style="
font-size:12pt;color:#5f5f5f;font-family:Arial">You
can forward this invitation to others. </span></td>
</tr>
</tbody>
</table>
<p style="margin-top:0px;margin-Bottom:0px"><span
style="
font-size:12pt;color:#5f5f5f;font-family:Arial"> </span></p>
<br>
<table style="border-collapse:collapse;"
width="525">
<tbody>
<tr height="8">
<td style="border-style:none none none
none;border-color:#000000;border-width:0px
0px 0px 0px;padding:0px 0px;" width="525"><span
style="
font-size:12pt;color:#4f4f4f;font-family:Arial">Hello,
</span>
</td>
</tr>
<tr height="8">
<td style="border-style:none none none
none;border-color:#000000;border-width:0px
0px 0px 0px;padding:0px 0px;" width="525"><span
style="
font-size:12pt;color:#4f4f4f;font-family:Arial">Peter
Shames invites you to join this WebEx
meeting. </span></td>
</tr>
</tbody>
</table>
<p style="margin-top:0px;margin-Bottom:0px"><span
style="
font-size:12pt;color:#5f5f5f;font-family:Arial"> </span></p>
<br>
<table style="border-collapse:collapse;"
width="525">
<tbody>
<tr height="8">
<td style="border-style:none none none
none;border-color:#000000;border-width:0px
0px 0px 0px;padding:0px 0px;" width="525"><span
style="
font-size:12pt;color:#5f5f5f;font-family:Arial"> </span></td>
</tr>
</tbody>
</table>
<p style="margin-top:0px;margin-Bottom:0px"><span
style="
font-size:12pt;color:#5f5f5f;font-family:Arial"> </span></p>
<br>
<table style="border-collapse:collapse;"
width="100%">
<tbody>
<tr height="8">
<td style="border-style:none none none
none;border-color:#000000;border-width:0px
0px 0px 0px;padding:0px 0px;" width="100%"><span
style="
font-size:12pt;color:#4f4f4f;font-family:Arial"><b>SCCS-ARD
update review</b> </span>
</td>
</tr>
<tr height="8">
<td style="border-style:none none none
none;border-color:#000000;border-width:0px
0px 0px 0px;padding:0px 0px;"><span
style="
font-size:12pt;color:#5f5f5f;font-family:Arial">Tuesday,
November 23, 2021 </span>
</td>
</tr>
<tr height="8">
<td style="border-style:none none none
none;border-color:#000000;border-width:0px
0px 0px 0px;padding:0px 0px;"><span
style="
font-size:12pt;color:#5f5f5f;font-family:Arial">7:00
AM | (UTC-07:00) Pacific Time (US
& Canada) | 1
hr 30 mins </span></td>
</tr>
</tbody>
</table>
<p style="margin-top:0px;margin-Bottom:0px"><span
style="
font-size:12pt;color:#5f5f5f;font-family:Arial"> </span></p>
<br>
<table style="border-collapse:collapse;"
width="334">
<tbody>
<tr height="8">
<td style="border-style:none none none
none;border-color:#000000;border-width:0px
0px 0px 0px;padding:0px 0px;" width="334"><span
style="
font-size:12pt;color:#5f5f5f;font-family:Arial">Meeting
number (access code): 2761 585 8804 </span></td>
</tr>
</tbody>
</table>
<p style="margin-top:0px;margin-Bottom:0px"><span
style="
font-size:12pt;color:#5f5f5f;font-family:Arial"> </span></p>
<br>
<table style="border-collapse:collapse;"
width="243">
<tbody>
<tr height="8">
<td style="border-style:none none none
none;border-color:#000000;border-width:0px
0px 0px 0px;padding:0px 0px;" width="243"><span
style="
font-size:12pt;color:#5f5f5f;font-family:Arial">Meeting
password: 9JRpYBGHp72</span></td>
</tr>
</tbody>
</table>
<p style="margin-top:0px;margin-Bottom:240px"><span
style="
font-size:12pt;color:#5f5f5f;font-family:Arial"> </span></p>
<br>
<table style="border-collapse:collapse;"
width="525">
<tbody>
<tr height="8">
<td style="border-style:none none none
none;border-color:#000000;border-width:0px
0px 0px 0px;padding:0px 0px;" width="525"><span
style="
font-size:12pt;color:#5f5f5f;font-family:Arial"> </span></td>
</tr>
</tbody>
</table>
<p style="margin-top:0px;margin-Bottom:0px"><span
style="
font-size:12pt;color:#5f5f5f;font-family:Arial"> </span></p>
<br>
<table style="border-collapse:collapse;"
width="116">
<tbody>
<tr height="8">
<td style="border-style:none none none
none;border-color:#000000;border-width:0px
0px 0px 0px;padding:0px 0px;" width="116">
<table style="border-collapse:collapse;"
width="117">
<tbody>
<tr height="8">
<td style="border-style:ridge ridge
ridge
ridge;border-color:#00823B;border-width:1px
1px 1px 1px;padding:0px 0px;"
width="111" bgcolor="#00823b">
<div align="center"><a
href="https://jpl.webex.com/jpl/j.php?MTID=m19aa1606d8ed2742fa89cd2d8d4b0afa"
moz-do-not-send="true"><span
style="
font-size:15pt;color:white;font-family:Arial">Join
meeting</span></a></div>
</td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
<p style="margin-top:0px;margin-Bottom:0px"><span
style="
font-size:12pt;color:#5f5f5f;font-family:Arial"> </span></p>
<br>
<table style="border-collapse:collapse;"
width="525">
<tbody>
<tr height="8">
<td style="border-style:none none none
none;border-color:#000000;border-width:0px
0px 0px 0px;padding:0px 0px;" width="525"><span
style="
font-size:12pt;color:#5f5f5f;font-family:Arial"> </span>
</td>
</tr>
<tr height="8">
<td style="border-style:none none none
none;border-color:#000000;border-width:0px
0px 0px 0px;padding:0px 0px;" width="525"><span
style="
font-size:11pt;font-family:Arial"><b>More
ways to join:</b></span></td>
</tr>
</tbody>
</table>
<p style="margin-top:0px;margin-Bottom:0px"><span
style="
font-size:12pt;color:#5f5f5f;font-family:Arial"> </span></p>
<br>
<table style="border-collapse:collapse;"
width="525">
<tbody>
<tr height="8">
<td style="border-style:none none none
none;border-color:#000000;border-width:0px
0px 0px 0px;padding:0px 0px;" width="525"><span
style="
font-size:12pt;color:#5f5f5f;font-family:Arial"> </span>
</td>
</tr>
<tr height="8">
<td style="border-style:none none none
none;border-color:#000000;border-width:0px
0px 0px 0px;padding:0px 0px;" width="525"><span
style=" font-size:9pt;font-family:Arial"><b>Join
from the meeting link</b></span>
</td>
</tr>
<tr height="8">
<td style="border-style:none none none
none;border-color:#000000;border-width:0px
0px 0px 0px;padding:0px 0px;" width="525"><a
href="https://jpl.webex.com/jpl/j.php?MTID=m19aa1606d8ed2742fa89cd2d8d4b0afa"
target="_blank" moz-do-not-send="true"><span
style="
font-size:11pt;color:#006062;font-family:Arial">https://jpl.webex.com/jpl/j.php?MTID=m19aa1606d8ed2742fa89cd2d8d4b0afa</span></a></td>
</tr>
</tbody>
</table>
<p style="margin-top:0px;margin-Bottom:0px"><span
style="
font-size:12pt;color:#5f5f5f;font-family:Arial"> </span></p>
<br>
<table style="border-collapse:collapse;"
width="525">
<tbody>
<tr height="8">
<td style="border-style:none none none
none;border-color:#000000;border-width:0px
0px 0px 0px;padding:0px 0px;" width="525"><span
style="
font-size:12pt;color:#5f5f5f;font-family:Arial"> </span></td>
</tr>
</tbody>
</table>
<p style="margin-top:0px;margin-Bottom:0px"><span
style="
font-size:12pt;color:#5f5f5f;font-family:Arial"> </span></p>
<br>
<table style="border-collapse:collapse;"
width="525">
<tbody>
<tr height="8">
<td style="border-style:none none none
none;border-color:#000000;border-width:0px
0px 0px 0px;padding:0px 0px;" width="525"><span
style="
font-size:12pt;color:#5f5f5f;font-family:Arial"> </span></td>
</tr>
</tbody>
</table>
<p style="margin-top:0px;margin-Bottom:0px"><span
style="
font-size:12pt;color:#5f5f5f;font-family:Arial"> </span></p>
<br>
<table style="border-collapse:collapse;"
width="525">
<tbody>
<tr height="8">
<td style="border-style:none none none
none;border-color:#000000;border-width:0px
0px 0px 0px;padding:0px 0px;" width="525"><span
style=" font-size:9pt;font-family:Arial"><b>Join
from a video system or application</b></span>
</td>
</tr>
<tr height="8">
<td style="border-style:none none none
none;border-color:#000000;border-width:0px
0px 0px 0px;padding:0px 0px;" width="525"><span
style="
font-size:11pt;color:#2f2f2f;font-family:Arial">Dial
</span><a
href="%20sip:27615858804@jpl.webex.com"
moz-do-not-send="true"><span style="
font-size:12pt;color:#006062;font-family:Arial">27615858804@jpl.webex.com</span></a>
</td>
</tr>
<tr height="8">
<td style="border-style:none none none
none;border-color:#000000;border-width:0px
0px 0px 0px;padding:0px 0px;" width="525"><span
style="
font-size:11pt;color:#2f2f2f;font-family:Arial">You
can also dial 207.182.190.20 and enter
your meeting number.</span></td>
</tr>
</tbody>
</table>
<p style="margin-top:0px;margin-Bottom:0px"><span
style="
font-size:12pt;color:#5f5f5f;font-family:Arial"> </span></p>
<br>
<table style="border-collapse:collapse;"
width="525">
<tbody>
<tr height="8">
<td style="border-style:none none none
none;border-color:#000000;border-width:0px
0px 0px 0px;padding:0px 0px;" width="525"><span
style=" font-size:9pt;font-family:Arial"><b>Join
by phone</b></span>
</td>
</tr>
<tr height="8">
<td style="border-style:none none none
none;border-color:#000000;border-width:0px
0px 0px 0px;padding:0px 0px;" width="525"><span
style="
font-size:11pt;color:#2f2f2f;font-family:Arial">+1-510-210-8882
USA Toll</span>
</td>
</tr>
<tr height="8">
<td style="border-style:none none none
none;border-color:#000000;border-width:0px
0px 0px 0px;padding:0px 0px;" width="525"><span
style="
font-size:11pt;color:#2f2f2f;font-family:Arial">+44-203-457-5798
U.K. Toll</span>
</td>
</tr>
<tr height="8">
<td style="border-style:none none none
none;border-color:#000000;border-width:0px
0px 0px 0px;padding:0px 0px;" width="525"><a
href="https://jpl.webex.com/jpl/globalcallin.php?MTID=m5e38422f279e390de6b43d836a8711d0"
moz-do-not-send="true"><span style="
font-size:11pt;color:#006062;font-family:Arial">Global
call-in numbers</span></a></td>
</tr>
</tbody>
</table>
<p style="margin-top:0px;margin-Bottom:0px"><span
style="
font-size:12pt;color:#5f5f5f;font-family:Arial"> </span></p>
<br>
<table style="border-collapse:collapse;"
width="525">
<tbody>
<tr height="8">
<td style="border-style:none none none
none;border-color:#000000;border-width:0px
0px 0px 0px;padding:0px 0px;" width="525"><span
style="
font-size:12pt;color:#5f5f5f;font-family:Arial"> </span></td>
</tr>
</tbody>
</table>
<p style="margin-top:0px;margin-Bottom:0px"><span
style="
font-size:12pt;color:#5f5f5f;font-family:Arial"> </span></p>
<br>
<table style="border-collapse:collapse;"
width="525">
<tbody>
<tr height="8">
<td style="border-style:none none none
none;border-color:#000000;border-width:0px
0px 0px 0px;padding:0px 0px;" width="525"><span
style="
font-size:12pt;color:#5f5f5f;font-family:Arial"><b>Local:
818-35(4-4044)</b> </span>
</td>
</tr>
<tr height="8">
<td style="border-style:none none none
none;border-color:#000000;border-width:0px
0px 0px 0px;padding:0px 0px;" width="525"><span
style="
font-size:12pt;color:#5f5f5f;font-family:Arial"><b>Toll
Free: 844-JPL-WEBX (844-575-9329)</b>
</span></td>
</tr>
</tbody>
</table>
<p style="margin-top:0px;margin-Bottom:0px"><span
style="
font-size:12pt;color:#5f5f5f;font-family:Arial"> </span></p>
<br>
<table style="border-collapse:collapse;"
width="525">
<tbody>
<tr height="8">
<td style="border-style:none none none
none;border-color:#000000;border-width:0px
0px 0px 0px;padding:0px 0px;" width="525">
<table style="border-collapse:collapse;"
width="525">
<tbody>
<tr height="8">
<td style="border-style:none none
none
none;border-color:#000000;border-width:0px
0px 0px 0px;padding:0px 0px;"
width="525"><span style="
font-size:12pt;color:#5f5f5f;font-family:Arial"> </span></td>
</tr>
</tbody>
</table>
<p
style="margin-top:0px;margin-Bottom:0px"><span
style="
font-size:10pt;color:#5f5f5f;font-family:Arial">Can't
join the meeting? </span></p>
</td>
</tr>
</tbody>
</table>
<p style="margin-top:0px;margin-Bottom:0px"><span
style="
font-size:12pt;color:#5f5f5f;font-family:Arial"> </span></p>
<br>
<table style="border-collapse:collapse;"
width="525">
<tbody>
<tr height="8">
<td style="border-style:none none none
none;border-color:#000000;border-width:0px
0px 0px 0px;padding:0px 0px;" width="525"><span
style="
font-size:12pt;color:#5f5f5f;font-family:Arial"> </span></td>
</tr>
</tbody>
</table>
<p style="margin-top:0px;margin-Bottom:0px"><span
style="
font-size:12pt;color:#5f5f5f;font-family:Arial"> </span></p>
<br>
<table style="border-collapse:collapse;"
width="525">
<tbody>
<tr height="8">
<td style="border-style:none none none
none;border-color:#000000;border-width:0px
0px 0px 0px;padding:0px 0px;" width="525"><span
style="
font-size:9pt;color:#a2a2a2;font-family:Arial">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></td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
<p style="margin-top:0px;margin-Bottom:0px"><span style="
font-size:11pt;font-family:Calibri"> [attachment
"Webex_Meeting.ics" deleted by Andrea Modenini/estec/ESA] </span><tt><span
style=" font-size:10pt">_______________________________________________<br>
CESG-All mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:CESG-All@mailman.ccsds.org">CESG-All@mailman.ccsds.org</a><br>
</span></tt><a
href="https://urldefense.us/v3/__https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg-all__;!!PvBDto6Hs4WbVuu7!c_W6kQBKFsU715uHT0ZbEI-Zxyzva6CZAw_475CJiUtC49HEKgcsDEvKn5iiAOkOJm26tok$"
moz-do-not-send="true"><tt><span style=" font-size:10pt">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg-all</span></tt></a><tt><span
style=" font-size:10pt"><br>
</span></tt></p>
<pre>This message is intended only for the recipient(s) named above. It may contain proprietary information and/or
protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received
this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect
personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (<a class="moz-txt-link-abbreviated" href="mailto:dpo@esa.int">dpo@esa.int</a>).
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
SLS-CC mailing list
<a class="moz-txt-link-abbreviated" href="mailto:SLS-CC@mailman.ccsds.org">SLS-CC@mailman.ccsds.org</a>
<a class="moz-txt-link-freetext" 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>
</pre>
</blockquote>
</body>
</html>