<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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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;}
@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:11.0pt;
font-family:"Calibri",sans-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;}
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.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
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:11.0pt;
font-family:"Calibri",sans-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:windowtext;}
.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;}
/* List Definitions */
@list l0
{mso-list-id:1731147292;
mso-list-type:hybrid;
mso-list-template-ids:376308590 67698705 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1
{mso-list-id:1963076161;
mso-list-template-ids:1670675598;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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">All,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Here is a follow on to the telecon that occurred today between myself, Gian-Paolo, Stefan Veit, and Ed Greenberg.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We are searching for the right approach to revise the SPP.<o:p></o:p></p>
<p class="MsoNormal">We are still in the brainstorming part of development. All inquiries and ideas are most invited!<o:p></o:p></p>
<p class="MsoNormal">As we discussed in the Haag in Nov. 2017, the Space Packet provides a duality of functionality: It is both an Application Layer (AP) Data Structure and Format as well as a data link layer transport mechanism i.e. it is transported within
the frame data field of CCSDS transfer frames.<o:p></o:p></p>
<p class="MsoNormal">We all seem to agree that there should be no mention of multiple subnetworks and routing in the future SPP. These things are handled much better by DTN, IP, etc.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We go back to the basic structure of what we shall describe in the SPP Blue Book: (<b>This is where I would like to get consensus on</b>
<b>first</b>)<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo2">In the Application Layer, there are multiple users (data sources) including the SPP Packet Assembly Function (out of strings it makes packets) that request the
<i>transfer </i>of Space Packets out of the Application Layer by supplying the <i>
APID, APID_Qualifier (optional), QoS Rqmt (optional) – </i>as currently defined by the SPP. This is accomplished by generating the
<i>packet.request </i>primitive in SPP. So multiple users are producing packets with different APIDs under management control and outside the purview of CCSDS.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo2">In the Application Layer, those packets provided by those multiple users and SPP Packet Assembly Function, shall be multiplexed to produce a
<i>single packet stream</i> in the appropriate order set by management whose algorithm is not specified by CCSDS – as currently defined by SPP. (SPP talks about a single Queue, but use of the term “stream” is better because it is implementation agnostic)<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo2">NOW HERE COMES SOME CONTENTION – Do we want the SPP to have the capability of
<i>forwarding data</i> (not routing data) on-board (mostly envisioned for on-board the spacecraft) within a single closed subnetwork in an A-B-A configuration ? If the answer is yes (I think it is yes), then
<i>APID_Qualifier </i>needs to be well and unambiguously defined for SPP. I can supply a use case from the ISS. For Telecommand, Space Station uses Logical Data Path – Endpoint as the
<i>APID_Qualifier</i> (this field occurs in the packet 2<sup>nd</sup> Header, which is currently non-compliant with SPP because there is currently no standard packet 2<sup>nd</sup> header defined) to forward commands to user modules on-board the ISS. In this
case, Logical Data Path is short circuited to be a Logical Data Path Endpoint. OR Gian Paolo contents that we should retire the concept of Logical Data Path completely, and only leave a historical note in SPP about its previous existence?<o:p></o:p></li></ol>
<p class="MsoListParagraph">We may need to hold open the possibility of Logical Data Path Endpoint or something similar until we get clarification from all agencies and the SIS area about their desires for eventually modifying the SPP packet 2<sup>nd</sup>
header in order to accomplish data forwarding on-board a spacecraft. Does this data forwarding function take place in the application layer ?<o:p></o:p></p>
<ol style="margin-top:0in" start="4" type="1">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo2">In the Data Link Layer, the
<i>transfer across the space link</i> of those Space Packets is requested. Here an additional multiplexing step
<i>may </i>take place, packets of multiple PVNs are multiplexed into the stream, before packets are placed into the transfer frame data fields of frames. Each single packet stream is then injected into the TF data field of a specific VC frame by sending it
to the instance of the Packet Processing Function for that VC that transports packets as defined in the appropriate
<i>SDLP Packet Processing Function</i>. The most generic way of expressing this primitive is to use Encapsulation.request (Data Unit, SDLP_Channel, PVN, EPI). Of course, one could also accomplish this transfer by using VCP.request (only for AOS or TM) or MAPP.request
(TC) or (USLP) or Packet Service in Prox-1.<o:p></o:p></li></ol>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Makes sense ?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks!<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Greg<o:p></o:p></p>
<p class="MsoNormal">Chairman SLP WG<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">"Gian.Paolo.Calzolari@esa.int" <Gian.Paolo.Calzolari@esa.int><br>
<b>Date: </b>Wednesday, January 31, 2018 at 6:30 AM<br>
<b>To: </b>John Pietras <john.pietras@gst.com><br>
<b>Cc: </b>Greg Kazz <greg.j.kazz@jpl.nasa.gov>, "sls-slp@mailman.ccsds.org" <sls-slp@mailman.ccsds.org><br>
<b>Subject: </b>Packet channel multiplexing no longer needed? : [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>
</div>
<p class="MsoNormal"><a name="_MailOriginalBody"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">John,</span></a><span style="mso-bookmark:_MailOriginalBody">
<br>
</span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"> I think that Packet channel multiplexing is still needed and surely implemented by space agencies.</span></span><span style="mso-bookmark:_MailOriginalBody">
<br>
</span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">The point is that those implementation are not exposed and I find this correct.</span></span><span style="mso-bookmark:_MailOriginalBody">
<br>
</span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Let's say that we should keep the same approach we have had in the past; i.e. SPP book shall mention that Packet channel multiplexing is to be
performed but leaving the implementation to users as loong as there no for a commen service (either SLS or CSTS).</span></span><span style="mso-bookmark:_MailOriginalBody">
<br>
</span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">If you think this is the same that happened with the TC standard and FSP.</span></span><span style="mso-bookmark:_MailOriginalBody">
<br>
</span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">The TC Standard mentioned that TC Frames were multiplexed over VCs/MAPs but gave no definition.</span></span><span style="mso-bookmark:_MailOriginalBody">
<br>
</span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">When SLE FSP was done it was realised that the TC Frame multiplexing required to be defined and in fact you have relevant clauses and an Annex
in FSP.</span></span><span style="mso-bookmark:_MailOriginalBody"> <br>
<br>
</span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">The same for TM frame, they are multiplexed over a Master Channel and their multiplexing is mentioned but not defined (specially because that multiplexing
is normally done on board a spacecrat :o).</span></span><span style="mso-bookmark:_MailOriginalBody">
<br>
</span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
Regards</span></span><span style="mso-bookmark:_MailOriginalBody"> <br>
<br>
</span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Gian Paolo</span></span><span style="mso-bookmark:_MailOriginalBody">
<br>
<br>
<br>
<br>
</span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">From: </span></span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">John
Pietras <john.pietras@gst.com></span></span><span style="mso-bookmark:_MailOriginalBody">
<br>
</span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">To: </span></span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"Gian.Paolo.Calzolari@esa.int"
<Gian.Paolo.Calzolari@esa.int>, "Kazz, Greg J (312B)" <greg.j.kazz@jpl.nasa.gov></span></span><span style="mso-bookmark:_MailOriginalBody">
<br>
</span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Cc: </span></span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"sls-slp@mailman.ccsds.org"
<sls-slp@mailman.ccsds.org>, SLS-SLP <sls-slp-bounces@mailman.ccsds.org></span></span><span style="mso-bookmark:_MailOriginalBody">
<br>
</span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Date: </span></span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">30/01/2018
19:06</span></span><span style="mso-bookmark:_MailOriginalBody"> <br>
</span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Subject: </span></span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">Re:
[Sls-slp] Results of Discussion with Takahiro Yamada on Revising SPP Blue Book</span></span><span style="mso-bookmark:_MailOriginalBody">
<br>
</span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Sent by: </span></span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"SLS-SLP"
<sls-slp-bounces@mailman.ccsds.org></span></span><span style="mso-bookmark:_MailOriginalBody">
<o:p></o:p></span></p>
<div class="MsoNormal" align="center" style="text-align:center"><span style="mso-bookmark:_MailOriginalBody">
<hr size="0" width="100%" noshade="" style="color:#A0A0A0" align="center">
</span></div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="mso-bookmark:_MailOriginalBody"><o:p> </o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="mso-bookmark:_MailOriginalBody"><span style="color:#004080">All,</span><o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="mso-bookmark:_MailOriginalBody"><span style="color:#004080">In an earlier email in this thread, Greg commented that he understood that many missions multiplex different “packet channels” into the same
VC, but that he did not see this happening in an interoperable way. I think that Greg has hit on the important factor here – what is exposed in an interoperable, cross-supported way?</span><o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="mso-bookmark:_MailOriginalBody"><span style="color:#004080"> </span><o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="mso-bookmark:_MailOriginalBody"><span style="color:#004080">Back when we wrote the original AOS book, we had the notion that “cross support” users would be able to access individual packet channels via
standard intefaces. This notion was formalized in the Cross Support Reference Model, Part 1 – Space Link Extension Services Blue Book (colloquially known as the “SLE Ref Model”), which envisioned two “flavors” of Forward Space Packet (TC and AOS) and one Return
Space Packet service. Those services would have allowed multiple FSP instances to carry packete channels all destined for the same VC.</span><o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="mso-bookmark:_MailOriginalBody"><span style="color:#004080"> </span><o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="mso-bookmark:_MailOriginalBody"><span style="color:#004080">As it turned out, only the TC flavor of the Forward Space Packet service was ever realized. Different instances of the (TC) FSP service are
indeed capable of carrying different packet channels destined for the same VC. The FSP service uses MAP, so the necessary packet channel multiplexing into VCs is accomplished (indirectly) through MAP Multiplexing.
</span><o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="mso-bookmark:_MailOriginalBody"><span style="color:#004080"> </span><o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="mso-bookmark:_MailOriginalBody"><span style="color:#004080">But had the AOS FSP been realized, it *<b>would</b>* have required the packet channel muxing that currently resides in the SPP. But since it
wasn’t realized, the main use case (that I know of) disappears, and perhaps packet channel multiplexing is indeed no longer needed at a cross-support interoperability level, which I agree with Greg is the important factor in considering whether to retain the
specification in the SPP (or migrate it back into one or more of the SDLP books).
</span><o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="mso-bookmark:_MailOriginalBody"><span style="color:#004080"> </span><o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="mso-bookmark:_MailOriginalBody"><span style="color:#004080">Best regards,</span><o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="mso-bookmark:_MailOriginalBody"><span style="color:#004080">John</span><o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="mso-bookmark:_MailOriginalBody"><span style="color:#004080"> </span><o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="mso-bookmark:_MailOriginalBody"><span style="color:#004080"> </span><o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="mso-bookmark:_MailOriginalBody"><b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">From:</span></b></span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">
Gian.Paolo.Calzolari@esa.int [</span></span><a href="mailto:Gian.Paolo.Calzolari@esa.int"><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">mailto:Gian.Paolo.Calzolari@esa.int</span></span><span style="mso-bookmark:_MailOriginalBody"></span></a><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">]
<b><br>
Sent:</b> Tuesday, January 30, 2018 8:55 AM<b><br>
To:</b> Kazz, Greg J (312B)<b><br>
Cc:</b> John Pietras; sls-slp@mailman.ccsds.org; SLS-SLP<b><br>
Subject:</b> Re: [Sls-slp] Results of Discussion with Takahiro Yamada on Revising SPP Blue Book</span><o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"> </span><o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Greg,</span></span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span></span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
what we have to be sure it captured in our CCSDS books is the following situation (e.g. for a TM/AOS link)</span></span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span><o:p></o:p></span></p>
<ul type="disc">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo1">
<span style="mso-bookmark:_MailOriginalBody"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">There multiple sources generating packet contents and asking creation of packets</span></span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span></span><span style="mso-bookmark:_MailOriginalBody"><o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo1">
<span style="mso-bookmark:_MailOriginalBody"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Those packets are created with different APIDs depending on the source</span></span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span></span><span style="mso-bookmark:_MailOriginalBody"><o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo1">
<span style="mso-bookmark:_MailOriginalBody"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Those different APIDs shall be multiplexed to produce a single packet stream:</span></span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span></span><span style="mso-bookmark:_MailOriginalBody"><o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo1">
<span style="mso-bookmark:_MailOriginalBody"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">This single packet stream is then injected in in a VC</span></span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span></span><span style="mso-bookmark:_MailOriginalBody"><o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo1">
<span style="mso-bookmark:_MailOriginalBody"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"> </span></span><span style="mso-bookmark:_MailOriginalBody"><o:p></o:p></span></li></ul>
<p class="MsoNormal"><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">It is then correct that "The current AOS SDLP version i.e., CCSDS 732.0-B-3 Sept 2015 is agnostic about “packet channels” and “Individual
CCSDS packets from multiple sources” (implying multiple APIDs). It is really only concerned about multiplexing of packets with different PVNs onto VCs." In fact AOS would only see that single stream.</span></span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span></span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
</span></span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"> </span></span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
All the rest shall be done above the SDLP.</span></span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
<br>
</span></span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
We shall check also what we lost with respect to CCSDS 103.0-B-2 (now silver) where there was a nice picture for which I attach a detail.</span></span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span></span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
Another document to be checked for losses is CCSDS 203.0-B-2 and even FSP that mention APID multiplexing if I remember well.</span></span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
<br>
</span></span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
Finally we shall verify all fits within the encapsulation service.</span></span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
<br>
</span></span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
Ciao</span></span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
<br>
</span></span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
Gian Paolo</span></span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
<br>
</span></span><span style="mso-bookmark:_MailOriginalBody"><img border="0" width="687" height="411" style="width:7.1562in;height:4.2812in" id="_x0000_i1025" src="cid:image001.gif@01D39AA9.92F69360" alt="cid:image001.gif@01D399A9.B32BEF00"><br>
</span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:10.0pt;font-family:"Courier New"">This message and any attachments are intended for the use of the addressee or addressees only.</span></span><span style="mso-bookmark:_MailOriginalBody">
<br>
</span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:10.0pt;font-family:"Courier New"">The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its</span></span><span style="mso-bookmark:_MailOriginalBody">
<br>
</span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:10.0pt;font-family:"Courier New"">content is not permitted.</span></span><span style="mso-bookmark:_MailOriginalBody">
<br>
</span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:10.0pt;font-family:"Courier New"">If you received this message in error, please notify the sender and delete it from your system.</span></span><span style="mso-bookmark:_MailOriginalBody">
<br>
</span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:10.0pt;font-family:"Courier New"">Emails can be altered and their integrity cannot be guaranteed by the sender.</span></span><span style="mso-bookmark:_MailOriginalBody">
<br>
</span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:10.0pt;font-family:"Courier New""> </span></span><span style="mso-bookmark:_MailOriginalBody">
<br>
</span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:10.0pt;font-family:"Courier New"">Please consider the environment before printing this email.</span></span><span style="mso-bookmark:_MailOriginalBody">
<br>
</span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:10.0pt;font-family:"Courier New""> </span></span><span style="mso-bookmark:_MailOriginalBody">
<o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"> </span><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="mso-bookmark:_MailOriginalBody"><br>
</span><span style="mso-bookmark:_MailOriginalBody"><tt><span style="font-size:10.0pt">_______________________________________________</span></tt></span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:10.0pt;font-family:"Courier New""><br>
<tt>SLS-SLP mailing list</tt><br>
<tt>SLS-SLP@mailman.ccsds.org</tt><br>
</span></span><span style="mso-bookmark:_MailOriginalBody"></span><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sls-slp"><span style="mso-bookmark:_MailOriginalBody"><tt><span style="font-size:10.0pt">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sls-slp</span></tt></span><span style="mso-bookmark:_MailOriginalBody"></span></a><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:10.0pt;font-family:"Courier New""><br>
<br>
</span></span><span style="mso-bookmark:_MailOriginalBody"><o:p></o:p></span></p>
<pre><span style="mso-bookmark:_MailOriginalBody">This message and any attachments are intended for the use of the addressee or addressees only.<o:p></o:p></span></pre>
<pre><span style="mso-bookmark:_MailOriginalBody">The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its<o:p></o:p></span></pre>
<pre><span style="mso-bookmark:_MailOriginalBody">content is not permitted.<o:p></o:p></span></pre>
<pre><span style="mso-bookmark:_MailOriginalBody">If you received this message in error, please notify the sender and delete it from your system.<o:p></o:p></span></pre>
<pre><span style="mso-bookmark:_MailOriginalBody">Emails can be altered and their integrity cannot be guaranteed by the sender.<o:p></o:p></span></pre>
<pre><span style="mso-bookmark:_MailOriginalBody"><o:p> </o:p></span></pre>
<pre><span style="mso-bookmark:_MailOriginalBody">Please consider the environment before printing this email.<o:p></o:p></span></pre>
<span style="mso-bookmark:_MailOriginalBody"></span>
<pre><o:p> </o:p></pre>
</div>
</body>
</html>