<span style=" font-size:10pt;font-family:sans-serif">Dear Greg, </span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Regarding <b><u>Proposed
PID 1:</u></b></span>
<br><span style=" font-size:10pt;font-family:sans-serif">The restriction
is also stated in para 2.2.4 </span>
<br>
<br><img src=cid:_1_19DC158019DC0F84003F2BF4C1258678 style="border:0px solid;">
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">I think your explanation
is correct. The Insert Zone Service was thought to carry small chunks of
fixed length user data in each Transfer Frame transmitted on the Physical
Channel in order to provide a low latency, "high priority",  synchronous
service. </span>
<br><span style=" font-size:10pt;font-family:sans-serif">In the presence
of Master Channel Service or Virtual Channel Service, this goal cannot
be achieved because the sequence of Insert Zone SDUs  would eventually
present gaps which are incompatible with the intended purpose of the service.
</span>
<br><span style=" font-size:10pt;font-family:sans-serif">However the above
is true if we assume that the users of MCF or VCF Services do not include
a blank place holder in their TFs to accommodate an Insert Zone SDU. </span>
<br><span style=" font-size:10pt;font-family:sans-serif">In principle the
above restriction might be removed if the user of MCF or VCF Servicea are
constrained to provide a Transfer Frame format compliant with the presence
of the insert zone. </span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Open for discussion.
</span>
<br>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Regarding <b><u>Proposed
PID 2</u></b></span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">I concur with
the explanation you provided. Port is used as a synonym of SAP. No ESA
on-board implementation is broken by the removal of the term from the standard.
I expect that also Ground implementation are not affected but maybe Gippo
knows better. </span>
<br>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Best regards</span>
<br><span style=" font-size:10pt;font-family:sans-serif">Marco</span>
<br>
<br>
<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">"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">To:
       </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">10/02/2021
00:29</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Subject:
       </span><span style=" font-size:9pt;font-family:sans-serif">[Sls-slp]
PIDs concerning AOS & TC SDLP Pink Sheets</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: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">I
was informed by Peter Shames, SEA Area Director, that he is considering
generating two PIDs (Area Director Level) one for the attached AOS (732.0)
and one for the TC (232.0) SDLP pink sheets.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Calibri">My
purpose of this email is to see if we (SLP WG) can come up with adequate
changes to the text in question or provide adequate rationale for these
specific pink sheet changes for example in the NOTE section of the documents.</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"><u>Proposed
PID 1: AOS Section 3.2.6 AOS Transfer Frame – why exclude the Insert Zone
under the condition ?</u></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">FROM:
3.2.6<i>.</i> “ The following restriction apply to AOS Transfer Frames:
if at least a Virtual Channel Frame or a Master Channel Frame service exists,
all AOS Transfer Frames on the Physical Channel shall not include the Transfer
Frame Insert Zone.”</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Calibri">TO:
?</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">The
issue the PID brings up, is “what is the rationale for this restriction
?” Why can’t the physical channel contain an Insert Zone under this condition
? Provide the rationale in the document, in order to avoid confusing the
user.</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">I
believe the rationale has to do with the fact, that if a service user subscribes
to either the VCF or the MCF service, then that user provides either complete
Master Channel Frames or complete Virtual Channel Frames to the service
provider. However, in those cases, there is an ambiguity concerning the
use of the Insert Zone service by that user. The protocol only allows for
one use of the Insert Zone service on the Physical Channel. Therefore to
avoid any ambiguity, under this condition, there cannot be an Insert Zone.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Calibri">If
I am incorrect, please let me know.</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">So
in order to address the PID, we could either modify 3.2.6 or provide clarification
in the NOTE below it. </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Calibri">Your
suggestions are welcome.</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"><u>Proposed
PID 2: TC SDLP Section 2.2.1 (and reoccurring) – removal of the term,
“ports”</u></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">Issue:
Why was the term, “ports” removed throughout the document ? By removing
it from the document, does it break any implementations?</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">I
noticed that the term “port” is not defined in both the 2003 as well
as the current version of 232.0. I believe the SLP WG removed the term,
“port(s)” because it was undefined and was not connected to the TC SDLP.
In other words, “port(s)” was just a notional term, but never part of
the actual TC SDLP. The only question remaining in the PID is “does it
break any existing agency implementation, if that term is removed from
the protocol” ? </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Calibri">I
would like the SLP WG to weigh in on that question. I am not aware of any
implementation issues from the NASA side.</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">Please
try and respond back to me by the end of this week i.e., no later than
Feb. 12.</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:
greg.j.kazz@jpl.nasa.gov </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Calibri"> [attachment
"732x0p30_CESG_Approval.pdf" deleted by Marco Rovatti/estec/ESA]
[attachment "232x0b3_CESG_Approval.pdf" deleted by Marco Rovatti/estec/ESA]
</span></p>
<br><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>
<br>
<br> <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>