<span style=" font-size:10pt;font-family:sans-serif">John,</span>
<br><span style=" font-size:10pt;font-family:sans-serif">
my wording yesterday evening was just a late nigh
effort :o)</span>
<br><span style=" font-size:10pt;font-family:sans-serif">In such sense
that verbose splitting had the main task of identifying the issue.</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">I do share your
main concern "</span><span style=" font-size:11pt;color:#004080;font-family:Calibri">to
eliminate any misinterpretation that there could be only one VCF or MCF
service instance per space link</span><span style=" font-size:10pt;font-family:sans-serif">"</span>
<br><span style=" font-size:10pt;font-family:sans-serif">Considering the
original formulation</span>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#104160;font-family:Calibri">“The
Virtual Channel Frame Service transfers the independently created AOS Transfer
Frames through a space link, possibly together with AOS Transfer Frames
identified by other GVCID values created by the service provider itself.”
</span></p>
<br><span style=" font-size:10pt;font-family:sans-serif">a relatively simple
improvement could be the following:</span>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#104160;font-family:Calibri">“The
Virtual Channel Frame Service transfers the independently created AOS Transfer
Frames through a space link</span><span style=" font-size:12pt;color:red;font-family:Calibri">.
The existence of a Virtual Channel Frame Service on a given Virtual Channel
does not prevent existence of other services of the same type or different
type on other channels identified by other GVCID values</span><span style=" font-size:12pt;color:#104160;font-family:Calibri">."</span></p>
<p style="margin-top:0px;margin-Bottom:0px"></p>
<br><span style=" font-size:10pt;font-family:sans-serif">Similarly the
sentence in 2.2.3.7 "</span><span style=" font-size:10pt;color:#0062e1;font-family:sans-serif">The
Master Channel Frame Service transfers the
independently created AOS Transfer Frames
through the space link, together with
AOS Transfer Frames created by the
service provider itself. </span><span style=" font-size:10pt;font-family:sans-serif">"
could change to</span>
<br><span style=" font-size:10pt;font-family:sans-serif">"</span><span style=" font-size:10pt;color:#0062e1;font-family:sans-serif">The
Master Channel Frame Service transfers the
independently created AOS Transfer Frames
through the space link</span><span style=" font-size:12pt;color:red;font-family:Calibri">.
The existence of a Virtual Channel Frame Service on a given Master Channel
does not prevent existence of other services of the same type or different
type on other channels identified by other MCID values</span><span style=" font-size:12pt;color:#104160;font-family:Calibri">.</span><span style=" font-size:10pt;color:#0062e1;font-family:sans-serif">
</span><span style=" font-size:10pt;font-family:sans-serif">"</span>
<br>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Arial">I
used the formulation "does not prevent" for a sort of alignment
to the MCF/VCF remarks in section 2.2.4 RESTRICTIONS ON SERVICES, i.e.:
</span></p>
<br><span style=" font-size:10pt;font-family:Arial">
b) If the Master Channel Frame Service exists on a Master
Channel, other services shall not exist simultaneously on that Master Channel.
</span>
<br><span style=" font-size:10pt;font-family:Arial">
c) If the Virtual Channel Frame Service exists on a Virtual
Channel, other services shall not exist simultaneously on that Virtual
Channel.</span>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Arial">but
of course also an active form may be used, e.g.:</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:red;font-family:Calibri">"Together
with a Virtual Channel Frame Service on a given Virtual Channel, other
services of the same type or different type can exist on other channels
identified by other GVCID values</span><span style=" font-size:12pt;color:#104160;font-family:Calibri">."</span></p>
<p style="margin-top:0px;margin-Bottom:0px"></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Arial">Finally,
as non-native English speaker, I am always open to linguistic improvement.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:sans-serif">Could
one of the two proposed shorter texts satisfy the real needs for improvement?</span></p>
<p style="margin-top:0px;margin-Bottom:0px"></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:sans-serif">Best
regards</span></p>
<p style="margin-top:0px;margin-Bottom:0px"></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:sans-serif">Gian
Paolo</span></p>
<p style="margin-top:0px;margin-Bottom:0px"></p>
<p style="margin-top:0px;margin-Bottom:0px"></p>
<br>
<br>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">From:
</span><span style=" font-size:9pt;font-family:sans-serif">"John
Pietras" <john.pietras@gst.com></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">To:
</span><span style=" font-size:9pt;font-family:sans-serif">"Gian.Paolo.Calzolari@esa.int"
<Gian.Paolo.Calzolari@esa.int>, "Kazz, Greg J(US 312B)"
<greg.j.kazz@jpl.nasa.gov></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Cc:
</span><span style=" font-size:9pt;font-family:sans-serif">"Kazz,
Greg J\(US 312B\) via SLS-SLP" <sls-slp@mailman.ccsds.org></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Date:
</span><span style=" font-size:9pt;font-family:sans-serif">28-10-20
00:06</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Subject:
</span><span style=" font-size:9pt;font-family:sans-serif">Re:
[Sls-slp] AOS 5-year review: typo and VCF Service issues</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">"SLS-SLP"
<sls-slp-bounces@mailman.ccsds.org></span>
<br>
<hr noshade>
<br>
<br>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">Gian
Paolo,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">I
was trying to make minimal changes to the existing (new) text, but I agree
with you that trying to squeeze multiple thoughts into a single sentence
is problematic. </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">My
main concern was to eliminate any misinterpretation that there could be
only one VCF or MCF service instance per space link – I’m particularly
sensitive to this point, having just completed the Forward Frame CSTS book,
the main point of which is to allow multiple external (with respect to
the ground station) sources of VC frames to share the same space link,
where each FF-CSTS instance has its own dedicated VC and therefore maps
into a separate instance of the VCF service.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">I
think that your wording is an improvement on my proposal. In any case,
I would be happy with any wording that makes clear that there can possibly
be:</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">-
one or more instances of the VCF service (each with its own GVCID); </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">-
one or more instances of MCF Service (each with its own MCID, where multiple
MCs on the same space link are valid);</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">-
one or more VCs (each with its own GVCID) generated by the service provider
itself; and/or</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">-
one or more MCs (each with its own MCID) generated by the service provider
itself </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">[NOTE
– I believe that MCs that are populated by frames received through instances
of the VC Frame service should be considered to be MCs created by the provider
system, since those frames come into the MC through the service provider’s
VC Mux function]</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">Best
regards,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri">John</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"><b>From:</b>
SLS-SLP [</span><a href="mailto:sls-slp-bounces@mailman.ccsds.org"><span style=" font-size:11pt;font-family:Calibri">mailto:sls-slp-bounces@mailman.ccsds.org</span></a><span style=" font-size:11pt;font-family:Calibri">]
<b>On Behalf Of </b>Gian.Paolo.Calzolari@esa.int<b><br>
Sent:</b> Tuesday, October 27, 2020 6:31 PM<b><br>
To:</b> Kazz, Greg J(US 312B) <greg.j.kazz@jpl.nasa.gov><b><br>
Cc:</b> Kazz, Greg J (US 312B) via SLS-SLP <sls-slp@mailman.ccsds.org><b><br>
Subject:</b> [Sls-slp] AOS 5-year review: typo and VCF Service issues</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Times New Roman"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Arial">Dear
All,</span><span style=" font-size:12pt;font-family:Times New Roman"> </span><span style=" font-size:10pt;font-family:Arial"><br>
the typo remark as presented in John's e-mail
looks correct (but I did not check the documents).</span><span style=" font-size:12pt;font-family:Times New Roman">
<br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
For the other remark I am getting more doubts.</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><br>
The current sentence is not looking correct to me, but I am not sure the
proposed correction is the best one.</span><span style=" font-size:12pt;font-family:Times New Roman">
<br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
As specified in 2.2.4 RESTRICTIONS ON SERVICES bullet c: If the Virtual
Channel Frame Service exists on a Virtual Channel, other services shall
not exist simultaneously on that Virtual Channel. <br>
Let's consider the original sentence: </span><span style=" font-size:12pt;color:#104160;font-family:Calibri"> “The
Virtual Channel Frame Service transfers the independently created AOS Transfer
Frames through a space link, possibly together with AOS Transfer Frames
identified by other GVCID values created by the service provider itself.”
</span><span style=" font-size:10pt;font-family:Arial"><br>
If we split it, I read something like this</span><span style=" font-size:12pt;font-family:Times New Roman">
</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#104160;font-family:Calibri"> “The
Virtual Channel Frame Service transfers the independently created AOS Transfer
Frames through a space link.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#104160;font-family:Calibri"> The
Virtual Channel Frame Service transfers possibly also AOS Transfer Frames
identified by other GVCID values created by the service provider itself.”
</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Arial"><br>
In other words it looks as the other frames are also transferred by the
VCF Service while they are transferred by other services (or service instances)
on other VCs/MCs.</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:10pt;font-family:Arial"><br>
The same issue rises also with the rewording proposed by John.</span><span style=" font-size:12pt;font-family:Times New Roman">
<br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
A possible improvement could then be something like this:</span><span style=" font-size:12pt;font-family:Times New Roman">
</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#104160;font-family:Calibri">“<u>Each</u>
Virtual Channel Frame Service <u>instance</u> transfers the independently
created AOS Transfer Frames through a space link.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#104160;font-family:Calibri">Those
AOS Transfer Frames are possibly multiplexed on the space link together
with other AOS Transfer Frames identified by different GVCID/MCID values.
</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#104160;font-family:Calibri">These
other AOS Transfer Frames can have been created <u>by other VCF/MCF Service
instances and/or</u> by the service provider itself.”</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Times New Roman"><br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
I understand this is likely not to be the best formulation, but may be
a good starting point for a less ambiguous formulation.</span><span style=" font-size:12pt;font-family:Times New Roman">
<br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
I also guess that a similar improvement should apply to 2.2.3.7 for the
sentence "</span><span style=" font-size:11pt;font-family:Times New Roman">The
Master Channel Frame Service transfers the independently created AOS Transfer
Frames through the space link, together with AOS Transfer Frames created
by the service provider itself.</span><span style=" font-size:10pt;font-family:Arial">"
noting that <If the Master Channel Frame Service exists on a Master
Channel, other services shall not exist simultaneously on that Master Channel.>.</span><span style=" font-size:12pt;font-family:Times New Roman">
<br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
Best regards</span><span style=" font-size:12pt;font-family:Times New Roman">
<br>
</span><span style=" font-size:10pt;font-family:Arial"><br>
Gian Paolo</span><span style=" font-size:12pt;font-family:Times New Roman">
<br>
<br>
<br>
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
From: </span><span style=" font-size:9pt;font-family:Arial">"Kazz,
Greg J\(US 312B\) via SLS-SLP" <</span><a href="mailto:sls-slp@mailman.ccsds.org"><span style=" font-size:9pt;color:blue;font-family:Arial"><u>sls-slp@mailman.ccsds.org</u></span></a><span style=" font-size:9pt;font-family:Arial">></span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
To: </span><span style=" font-size:9pt;font-family:Arial">"Kazz,
Greg J (US 312B) via SLS-SLP" <</span><a href="mailto:sls-slp@mailman.ccsds.org"><span style=" font-size:9pt;color:blue;font-family:Arial"><u>sls-slp@mailman.ccsds.org</u></span></a><span style=" font-size:9pt;font-family:Arial">></span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
Date: </span><span style=" font-size:9pt;font-family:Arial">27-10-20
22:53</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
Subject: </span><span style=" font-size:9pt;font-family:Arial">[Sls-slp]
FW: [EXTERNAL] RE: Updated TM & AOS 5-year review files from SLP WG
meeting Oct 27</span><span style=" font-size:12pt;font-family:Times New Roman">
</span><span style=" font-size:9pt;color:#5f5f5f;font-family:Arial"><br>
Sent by: </span><span style=" font-size:9pt;font-family:Arial">"SLS-SLP"
<</span><a href="mailto:sls-slp-bounces@mailman.ccsds.org"><span style=" font-size:9pt;color:blue;font-family:Arial"><u>sls-slp-bounces@mailman.ccsds.org</u></span></a><span style=" font-size:9pt;font-family:Arial">></span><span style=" font-size:12pt;font-family:Times New Roman">
</span></p>
<div align=center>
<hr noshade></div>
<p style="margin-top:0px;margin-Bottom:240px"><span style=" font-size:12pt;font-family:Times New Roman"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Dear
SLP WG members,</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">John
Pietras has what I believe are some good points below.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Please
let me know your opinion of his proposed changes below</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!<br>
Greg</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Chair
SLP WG</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>John Pietras <</span><a href=mailto:john.pietras@gst.com><span style=" font-size:12pt;color:blue;font-family:Calibri"><u>john.pietras@gst.com</u></span></a><span style=" font-size:12pt;font-family:Calibri">><b><br>
Date: </b>Tuesday, October 27, 2020 at 2:23 PM<b><br>
To: </b>"Kazz, Greg J (US 312B)" <</span><a href=mailto:greg.j.kazz@jpl.nasa.gov><span style=" font-size:12pt;color:blue;font-family:Calibri"><u>greg.j.kazz@jpl.nasa.gov</u></span></a><span style=" font-size:12pt;font-family:Calibri">><b><br>
Subject: </b>[EXTERNAL] RE: Updated TM & AOS 5-year review files from
SLP WG meeting Oct 27</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;color:#104160;font-family:Calibri">Dear
Greg and all,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#104160;font-family:Calibri">I’ve
taken a quick look at the updates TM and AOS books and I found a typo and
a statement that I think is misleading.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#104160;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#104160;font-family:Calibri">First
the typo – As modified, the first sentence of the second paragraph under
2.2.3.6 of the AOS book now reads “For a given service instance, only
one user, identified with the GVCID of the Virtual Channel, and each VCF
Service instance on a physical channel must utilize a unique GVCID value.”
The phrase “can use this service on a Virtual Channel” has been erroneously
deleted. </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#104160;font-family:Calibri">The
sentence should read “For a given service instance, only one user, identified
with the GVCID of the Virtual Channel, <u>can use this service on a Virtual
Channel,</u> and each VCF Service instance on a physical channel must utilize
a unique GVCID value.”</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#104160;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#104160;font-family:Calibri">What
I believe to be a misleading statement appears in two forms in both the
AOS and TM books. The first sentence of the third paragraph under 2.2.3.6
of the AOS book now reads “The Virtual Channel Frame Service transfers
the independently created AOS Transfer Frames through a space link, possibly
together with AOS Transfer Frames identified by other GVCID values created
by the service provider itself.” </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#104160;font-family:Calibri">My
interpretation of this sentence is that there can be only one instance
of the VCF Service per space link, with the implication that all other
VCs on the space link are generated “by the service provider itself”.
</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#104160;font-family:Calibri">I
believe that a more accurate, less ambiguous statement is </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#104160;font-family:Calibri">“<u>Each</u>
Virtual Channel Frame Service <u>instance</u> transfers the independently
created AOS Transfer Frames through a space link, possibly together with
AOS Transfer Frames identified by other GVCID values created <u>by users
of other VCF Service instances, users of Master Channel Frame service instances
(see 2.2.3.7), and/or</u> by the service provider itself.”</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#104160;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#104160;font-family:Calibri">If
my suggestion is accepted, the same change should be applied to 2.2.3.6
of the TM book. </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#104160;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#104160;font-family:Calibri">The
analogous situation applies to the MCF Service. The equivalent modification
would be to change first sentence of the third paragraph under 2.2.3.7
of the AOS book (and 2.2.9 of the TM book) to read “<u>Each</u> Master
Channel Frame Service <u>instance</u> transfers the independently created
AOS Transfer Frames through the space link, possibly together with AOS
Transfer Frames identified by other MCID values created <u>by users of
other MCF Service instances or</u> by the service provider itself.“</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#104160;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#104160;font-family:Calibri">Best
regards,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#104160;font-family:Calibri">John
</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;color:#104160;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;color:#004080;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"><b>From:</b>
SLS-SLP [</span><a href="mailto:sls-slp-bounces@mailman.ccsds.org"><span style=" font-size:11pt;color:blue;font-family:Calibri"><u>mailto:sls-slp-bounces@mailman.ccsds.org</u></span></a><span style=" font-size:11pt;font-family:Calibri">]
<b>On Behalf Of </b>Kazz, Greg J (US 312B) via SLS-SLP<b><br>
Sent:</b> Tuesday, October 27, 2020 12:43 PM<b><br>
To:</b> Kazz, Greg J (US 312B) via SLS-SLP <</span><a href="mailto:sls-slp@mailman.ccsds.org"><span style=" font-size:11pt;color:blue;font-family:Calibri"><u>sls-slp@mailman.ccsds.org</u></span></a><span style=" font-size:11pt;font-family:Calibri">><b><br>
Subject:</b> [Sls-slp] Updated TM & AOS 5-year review files from SLP
WG meeting Oct 27</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Calibri">Dear
SLP WG,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Calibri">Attached
please find two files as a result of the 5-year review:</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Arial">1.
</span><span style=" font-size:12pt;font-family:Calibri">Updated
132.0-B TM SDLP book modified during our SLP WG meeting today on Oct 27.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Arial">2.
</span><span style=" font-size:12pt;font-family:Calibri">Updated
732.0-B AOS SDLP book modified during our SLP WG meeting today on Oct 27.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Calibri">When
I have a chance, I will load both of them to the SLP WG CWE directory under
the Fall 2020 meeting.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Calibri">Best
regards,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Greg
Kazz</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Principal
Engineer</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Technical
Group Supervisor,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">PSSE/EEISE/PPSE
(312B)</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Jet
Propulsion Laboratory</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">4800
Oak Grove Dr., M/S 301-490</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Pasadena,
CA 91109</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">1+(818)393
6529(voice)</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">1+(818)393
6871(fax)</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">email:
</span><a href=mailto:greg.j.kazz@jpl.nasa.gov><span style=" font-size:11pt;color:#0082bf;font-family:Calibri"><u>greg.j.kazz@jpl.nasa.gov</u></span></a><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"> </span><span style=" font-size:10pt;font-family:Courier New">_______________________________________________<br>
SLS-SLP mailing list</span><span style=" font-size:10pt;color:blue;font-family:Courier New"><u><br>
</u></span><a href="mailto:SLS-SLP@mailman.ccsds.org"><span style=" font-size:10pt;color:blue;font-family:Courier New"><u>SLS-SLP@mailman.ccsds.org</u></span></a><span style=" font-size:12pt;color:blue;font-family:Times New Roman"><u><br>
</u></span><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sls-slp"><span style=" font-size:10pt;color:blue;font-family:Courier New"><u>https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sls-slp</u></span></a></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">This
message is intended only for the recipient(s) named above. It may contain
proprietary information and/or</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">protected
content. Any unauthorised disclosure, use, retention or dissemination is
prohibited. If you have received</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">this
e-mail in error, please notify the sender immediately. ESA applies appropriate
organisational measures to protect</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Courier New">personal
data, in case of data privacy queries, please contact the ESA Data Protection
Officer (</span><a href=mailto:dpo@esa.int><span style=" font-size:10pt;color:blue;font-family:Courier New"><u>dpo@esa.int</u></span></a><span style=" font-size:10pt;font-family:Courier New">).</span><tt><span style=" font-size:10pt">_______________________________________________<br>
SLS-SLP mailing list<br>
SLS-SLP@mailman.ccsds.org<br>
</span></tt><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sls-slp"><tt><span style=" font-size:10pt">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sls-slp</span></tt></a><tt><span style=" font-size:10pt"><br>
</span></tt></p>
<p style="margin-top:0px;margin-Bottom:0px"></p>
<p style="margin-top:0px;margin-Bottom:0px"></p>
<PRE>This message is intended only for the recipient(s) named above. It may contain proprietary information and/or
protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received
this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect
personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo@esa.int).
</PRE>