<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">Peter, i did not refer to VC multiplexing, fully defined in the soace data link protocols, but to the APID miltiplexing or similar issues. <div>Ciao</div><div>Gian Paoli<br><br><div id="AppleMailSignature">Sent from my iPhone</div><div><br>On 29. Jan 2018, at 20:20, Shames, Peter M (312B) <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>> wrote:<br><br></div><blockquote type="cite"><div>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
I think John is right. The distinction is between a “Space Packet Service “ that is a data encapsulation and multiplexing service within some “subnet” and a Packet Transfer Service that is the way Space Packets are transferred over an SDL. This does include
the SPP muxing into an SDL VC. SPP itself cannot assert responsibility for this since it has only virtual (or managed) knowledge of how the packets will be transferred over the subnet.
<div><br>
</div>
<div>Regards, Peter<br>
<br>
<div id="AppleMailSignature">Sent from Peter's JPL iPhone 7
<div><br>
</div>
<div>Everything should be made as simple as possible, </div>
<div>but not simpler. </div>
<div><br>
</div>
<div>~Albert Einstein</div>
</div>
<div><br>
On Jan 27, 2018, at 11:00 AM, "<a href="mailto:Gian.Paolo.Calzolari@esa.int">Gian.Paolo.Calzolari@esa.int</a>" <<a href="mailto:Gian.Paolo.Calzolari@esa.int">Gian.Paolo.Calzolari@esa.int</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>Good hint, John.
<div>It looks as we shall carry out a good comparison of the the homonymous services and determine the real deltas. It may be that in SPP only a Space Packet Multiplexing is required. </div>
<div>Regards</div>
<div>Gian Paolo<br>
<br>
<div id="AppleMailSignature">Sent from my iPhone</div>
<div><br>
On 27. Jan 2018, at 16:21, John Pietras <<a href="mailto:john.pietras@gst.com">john.pietras@gst.com</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<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:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.begin-antispam-voting-links
{mso-style-name:begin-antispam-voting-links;}
span.end-antispam-voting-links
{mso-style-name:end-antispam-voting-links;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@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]-->
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Members of the SLPWG,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">I have read through Greg’s summary of his conversation with Takahiro regarding suggested simplifications of the SPP book. One of those suggested changes is the removal of the Packet Service,
which the memo implied was redundant with this Packet Service provided by the Space Data Link Protocols. This is not quite true – the Packet Service that is provided by the SPP provides the additional functionality of muxing/demuxing Packets with different
APIDs into/out of a single VC. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Admittedly, I have been away from the day-to-day considerations of space link protocols for many years, but having been a member of the Panel 1 F/G team that wrote the original AOS Blue Book
I can attest to the fact that the ability to flow multiple “packet channels” through a single VC was an important aspect of the protocol stack, at least at the time (late 80s). Unless there is no longer a perceived need to do such packet channel muxing/demuxing,
such a capability would have to be retained in the SPP book or re-integrated into the various SDLP books as appropriate.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">I will agree that calling both the SPP “Packet Services” and the SLDP “Packet Services” by the same name is confusing and can lead to overlooking this additional functionality of the SPP flavor
of the service. Perhaps a different name to distinguish them would be useful.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Best regards, <o:p>
</o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">John Pietras<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> SLS-SLP [<a href="mailto:sls-slp-bounces@mailman.ccsds.org">mailto:sls-slp-bounces@mailman.ccsds.org</a>]
<b>On Behalf Of </b>Kazz, Greg J (312B)<br>
<b>Sent:</b> Thursday, January 25, 2018 5:41 PM<br>
<b>To:</b> <a href="mailto:sls-slp@mailman.ccsds.org">sls-slp@mailman.ccsds.org</a><br>
<b>Subject:</b> [Sls-slp] Results of Discussion with Takahiro Yamada on Revising SPP Blue Book<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Dear SLP WG,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Happy New Year 2018 !<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">This topic concerns the new project recently approved for revising the Space Packet Protocol (SPP) Blue book.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Please read the attached Word file that contains a discussion I had with Takahiro Yamada, the driving force in the CCSDS restructuring of the Packet Telemetry Blue Book. Parts of that book under Takahiro’s
guidance became the Space Packet Protocol, SPP, which we are now tasked to revise and update.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">I have made several suggestions about removing sections of the existing SPP document and I have asked Takahiro to give us his opinion about it.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">I would like to hold a 1 hour telecon on this subject in the very near future. I will set up a doodle poll to determine when the best time will be to discuss this topic. Please look forward to the invitation.
If you don’t see one, please let me know so that I can add you to the list, if I missed you.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Greg<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">CCSDS SLP WG Chairman<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Greg Kazz<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Principal Engineer<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Technical Group Supervisor,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Project Software and End-to-End Information Systems Engineering (312B)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Jet Propulsion Laboratory<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">4800 Oak Grove Dr., M/S 301-490<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="ES-MX" style="font-size:11.0pt">Pasadena, CA 91109</span><span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="ES-MX" style="font-size:11.0pt">1+(818)393 6529(voice)</span><span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">1</span><span lang="ES-MX" style="font-size:11.0pt">+(818)393 6871(fax)</span><span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="ES-MX" style="font-size:11.0pt">email: <a href="mailto:greg.j.kazz@jpl.nasa.gov">
greg.j.kazz@jpl.nasa.gov</a> </span><span style="font-size:11.0pt"><o:p></o:p></span></p>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman","serif""><o:p> </o:p></span></p>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<pre>This message and any attachments are intended for the use of the addressee or addressees only.
The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its
content is not permitted.
If you received this message in error, please notify the sender and delete it from your system.
Emails can be altered and their integrity cannot be guaranteed by the sender.
Please consider the environment before printing this email.
</pre>
</div>
</blockquote>
<blockquote type="cite">
<div><span>_______________________________________________</span><br>
<span>SLS-SLP mailing list</span><br>
<span><a href="mailto:SLS-SLP@mailman.ccsds.org">SLS-SLP@mailman.ccsds.org</a></span><br>
<span><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sls-slp">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sls-slp</a></span><br>
</div>
</blockquote>
</div>
</div></blockquote></div><PRE>This message and any attachments are intended for the use of the addressee or addressees only.
The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its
content is not permitted.
If you received this message in error, please notify the sender and delete it from your system.
Emails can be altered and their integrity cannot be guaranteed by the sender.
Please consider the environment before printing this email.
</PRE></body></html>