<span style=" font-size:10pt;font-family:sans-serif">Dear All,</span>
<br><span style=" font-size:10pt;font-family: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:10pt;font-family:sans-serif">For the other
remark I am getting more doubts.</span>
<br><span style=" font-size:10pt;font-family: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:10pt;font-family: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:10pt;font-family:sans-serif">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>
<br><span style=" font-size:10pt;font-family:sans-serif">If we split it,
I read something like this</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></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>
<br><span style=" font-size:10pt;font-family: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:10pt;font-family:sans-serif">The same issue
rises also with the rewording proposed by John.</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">A possible improvement
could then be something like this:</span>
<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>
<br>
<br><span style=" font-size:10pt;font-family: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:10pt;font-family:sans-serif">I also guess that
a similar improvement should apply to 2.2.3.7 for the sentence "</span><span style=" font-size:11pt">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">"
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:10pt;font-family:sans-serif">Best regards</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Gian Paolo</span>
<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">27-10-20
22:53</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]
FW: [EXTERNAL] RE: Updated TM & AOS 5-year review files from SLP WG
meeting Oct 27</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;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 <john.pietras@gst.com><b><br>
Date: </b>Tuesday, October 27, 2020 at 2:23 PM<b><br>
To: </b>"Kazz, Greg J (US 312B)" <greg.j.kazz@jpl.nasa.gov><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;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>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 <sls-slp@mailman.ccsds.org><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:sans-serif">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:sans-serif">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><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>