<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
tt
{mso-style-priority:99;
font-family:"Courier New";}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Gian Paolo,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">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.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">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.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">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:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">- one or more instances of the VCF service (each with its own GVCID);
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">- one or more instances of MCF Service (each with its own MCID, where multiple MCs on the same space link are valid);<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">- one or more VCs (each with its own GVCID) generated by the service provider itself; and/or<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">- one or more MCs (each with its own MCID) generated by the service provider itself
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">[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]<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">John<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> SLS-SLP [mailto:sls-slp-bounces@mailman.ccsds.org]
<b>On Behalf Of </b>Gian.Paolo.Calzolari@esa.int<br>
<b>Sent:</b> Tuesday, October 27, 2020 6:31 PM<br>
<b>To:</b> Kazz, Greg J(US 312B) <greg.j.kazz@jpl.nasa.gov><br>
<b>Cc:</b> Kazz, Greg J (US 312B) via SLS-SLP <sls-slp@mailman.ccsds.org><br>
<b>Subject:</b> [Sls-slp] AOS 5-year review: typo and VCF Service issues<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Dear All,</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"> the typo remark as presented in John's e-mail looks correct (but I did not check the documents).</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">For the other remark I am getting more doubts.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The current sentence is not looking correct to me, but I am not sure the proposed correction is the best one.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">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.
</span><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Let's consider the original sentence:
</span><span style="font-family:"Calibri",sans-serif;color:#104160"> “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><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">If we split it, I read something like this</span>
<o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif;color:#104160"> “The Virtual Channel Frame Service transfers the independently created AOS Transfer Frames through a space link.</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif;color:#104160"> The Virtual Channel Frame Service transfers possibly also AOS Transfer Frames identified by other GVCID values created by the service provider itself.”
</span><o:p></o:p></p>
<p class="MsoNormal"><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">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>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The same issue rises also with the rewording proposed by John.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">A possible improvement could then be something like this:</span>
<o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif;color:#104160">“<u>Each</u> Virtual Channel Frame Service
<u>instance</u> transfers the independently created AOS Transfer Frames through a space link.</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif;color:#104160">Those AOS Transfer Frames are possibly multiplexed on the space link together with other AOS Transfer Frames identified by different GVCID/MCID values.
</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif;color:#104160">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><o:p></o:p></p>
<p class="MsoNormal"><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">I understand this is likely not to be the best formulation, but may be a good starting point for a less ambiguous formulation.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">I also guess that a similar improvement should apply to 2.2.3.7 for the sentence "</span><span style="font-size:11.0pt">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:10.0pt;font-family:"Arial",sans-serif">" noting that <If the Master Channel Frame Service exists on a Master Channel, other
services shall not exist simultaneously on that Master Channel.>.</span> <br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Best regards</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Gian Paolo</span> <br>
<br>
<br>
<br>
<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">"Kazz, Greg J\(US 312B\) via SLS-SLP" <<a href="mailto:sls-slp@mailman.ccsds.org">sls-slp@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">"Kazz, Greg J (US 312B) via SLS-SLP" <<a href="mailto:sls-slp@mailman.ccsds.org">sls-slp@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">27-10-20 22:53</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">[Sls-slp] FW: [EXTERNAL] RE: Updated TM & AOS 5-year review files from SLP WG meeting Oct 27</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">"SLS-SLP" <<a href="mailto:sls-slp-bounces@mailman.ccsds.org">sls-slp-bounces@mailman.ccsds.org</a>></span>
<o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="3" 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;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Dear SLP WG members,</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">John Pietras has what I believe are some good points below.</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Please let me know your opinion of his proposed changes below</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Thanks!<br>
Greg</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Chair SLP WG</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><b><span style="font-family:"Calibri",sans-serif">From:
</span></b><span style="font-family:"Calibri",sans-serif">John Pietras <<a href="mailto:john.pietras@gst.com">john.pietras@gst.com</a>><b><br>
Date: </b>Tuesday, October 27, 2020 at 2:23 PM<b><br>
To: </b>"Kazz, Greg J (US 312B)" <<a href="mailto:greg.j.kazz@jpl.nasa.gov">greg.j.kazz@jpl.nasa.gov</a>><b><br>
Subject: </b>[EXTERNAL] RE: Updated TM & AOS 5-year review files from SLP WG meeting Oct 27</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif;color:#104160">Dear Greg and all,</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif;color:#104160">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><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif;color:#104160"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif;color:#104160">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><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif;color:#104160">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><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif;color:#104160"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif;color:#104160">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><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif;color:#104160">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><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif;color:#104160">I believe that a more accurate, less ambiguous statement is
</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif;color:#104160">“<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><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif;color:#104160"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif;color:#104160">If my suggestion is accepted, the same change should be applied to 2.2.3.6 of the TM book.
</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif;color:#104160"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif;color:#104160">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><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif;color:#104160"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif;color:#104160">Best regards,</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif;color:#104160">John </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif;color:#104160"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#004080"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> SLS-SLP [</span><a href="mailto:sls-slp-bounces@mailman.ccsds.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">mailto:sls-slp-bounces@mailman.ccsds.org</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">]
<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 <<a href="mailto:sls-slp@mailman.ccsds.org">sls-slp@mailman.ccsds.org</a>><b><br>
Subject:</b> [Sls-slp] Updated TM & AOS 5-year review files from SLP WG meeting Oct 27</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">Dear SLP WG,</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">Attached please find two files as a result of the 5-year review:</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">1. </span><span style="font-family:"Calibri",sans-serif">Updated 132.0-B TM SDLP book modified during our SLP WG meeting today on Oct 27.</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">2. </span><span style="font-family:"Calibri",sans-serif">Updated 732.0-B AOS SDLP book modified during our SLP WG meeting today on Oct 27.</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">When I have a chance, I will load both of them to the SLP WG CWE directory under the Fall 2020 meeting.</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif">Best regards,</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Greg Kazz</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Principal Engineer</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Technical Group Supervisor,</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">PSSE/EEISE/PPSE (312B)</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Jet Propulsion Laboratory</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">4800 Oak Grove Dr., M/S 301-490</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Pasadena, CA 91109</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">1+(818)393 6529(voice)</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">1+(818)393 6871(fax)</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">email:
</span><a href="mailto:greg.j.kazz@jpl.nasa.gov"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0082BF">greg.j.kazz@jpl.nasa.gov</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">
</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Calibri",sans-serif"> </span><tt><span style="font-size:10.0pt">_______________________________________________</span></tt><span style="font-size:10.0pt;font-family:"Courier New""><br>
<tt>SLS-SLP mailing list</tt><br>
<tt><a href="mailto:SLS-SLP@mailman.ccsds.org">SLS-SLP@mailman.ccsds.org</a></tt><br>
</span><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sls-slp"><tt><span style="font-size:10.0pt">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sls-slp</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>
</div>
</body>
</html>