<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">Thank you for your quick response.<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">Yes, I mistyped in bullet (1) – SPP should indeed have been EPP.<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">Thanks for pointing out those items regarding USLP – we will certainly take those into account.<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"> Gian.Paolo.Calzolari@esa.int [mailto:Gian.Paolo.Calzolari@esa.int]
<br>
<b>Sent:</b> Wednesday, November 18, 2020 12:43 PM<br>
<b>To:</b> John Pietras <john.pietras@gst.com><br>
<b>Cc:</b> Holger.Dreihahn@esa.int; sls-slp@mailman.ccsds.org; SLS-SLP <sls-slp-bounces@mailman.ccsds.org>; Wolfgang Hell <wo_._he@t-online.de><br>
<b>Subject:</b> Re: [Sls-slp] Questions about Encapsulation Packet Protocol<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">John,</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"> here may cent waiting whatever additional clarification Greg or others may add.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">1) Clearly you refer to EOPP and not to SPP.
</span><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Clause </span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> 3.2.1.2
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"> can be understood considering Table 4-2.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">2) Indeed, a segment header is required to split packets over multiple frames. VCP Service has no segment header and therefore can only allow blocking (as per Figure 4-14) while MAP Packet Service
allows bot blocking and segmentation (as per Figure 4-9).</span> <br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">TM and AOS have a first header pointer - in Frame Header and M_PDU respectively - and this allows "packets spanning over several frames"</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">A first header pointer is available also in USLP (see clause 4.1.4.2.2.2.1 for TFDZ Construction Rule ‘000’ indicating a fixed-length TFDZ). [you do not mention this in your item #2.]</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Conversely, USLPTFDZ Construction Rules ‘100’, ‘101’, and ‘110’ (indicating a variable-length TFDZ) can be used "a la TC' for "packets spanning over several frames"
</span><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">3) I cannot say whether it was "</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">intention of the SLPWG that the multiplexing of Encap packets been done on a FIFO basis</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif">".
I would simply guess that nobody thought to require a multiplexing there :o)</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">In other words, I think there is nothing preventing an EPP implementation to implement a Multiplexing Scheme. I guess that if an agency has this need, SLP WG could discuss such input.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Despite limitation to FIFO looks to me very reasonable for Functional Resources, I think that absence of a precise statement leaves freedom.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">4) we shall pass this to Tom Gannett.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Greg and others are welcome to complement my opinion.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">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">"John Pietras" <<a href="mailto:john.pietras@gst.com">john.pietras@gst.com</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">"<a href="mailto:sls-slp@mailman.ccsds.org">sls-slp@mailman.ccsds.org</a>" <<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">Cc: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"Wolfgang Hell" <<a href="mailto:wo_._he@t-online.de">wo_._he@t-online.de</a>>, "<a href="mailto:Holger.Dreihahn@esa.int">Holger.Dreihahn@esa.int</a>"
<<a href="mailto:Holger.Dreihahn@esa.int">Holger.Dreihahn@esa.int</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">18-11-20 17:29</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] Questions about Encapsulation Packet Protocol</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">SLPWG colleagues ---</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">As you may be aware, the Cross Support Services Area is developing a Functional Resource Model (FRM) that defines the functional resources that abstractly
represent the various functions performed by Earth Space Link Terminals (i.e., ground stations). The purpose of these functional resources is facilitate the definition of configuration profiles (used in scheduling) and to support the monitoring and control
of the physical resources that are represented by those functional resources in cross support situations. (For those of you familiar with the concept of a Management Information Base (MIB) in the context of network management protocols such as TCP/IP’s Simple
Network Management Protocol (SNMP) or the ISO/OSI Common Management Information Protocol (CMIP), the FRM is essentially the “MIB” for space data systems.)</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">We are in the process of completing the definitions of the functional resources that correspond to the CCSDS space data link protocol functions: TC SDLP,
TM SDLP, AOS SDLP, USLP, Space Packet Protocol (SPP), and Encapsulation Packet Protocol (EPP). In exploring the interactions among the Encapsulation Function defined in the EPP and the various underlying SDLPs, we have developed a question and several interpretations
that I am now posing to you for comment:</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. Section 3.2.1.2 of the SPP (CCSDS 133.1-B-1) specifies that “the maximum length of a data unit that can be accommodated in an encapsulating packet
is 4,294,967,287 octets for the Encapsulation Packet.” Is this just the consequence of that being the size supported by the 4-octet PACKET LENGTH field (LENGTH OF LENGTHS = ‘11’), or are there identified operational use cases for this large a packet?
</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">2. Section 3.2.2.2 confirms that Encap Packets can be transferred via the Virtual Channel Packet (VCP) service of the TM, TC, and AOD SDLPs, and
via the MAP Packet (MAPP) service of TC SDLP and USLP. We make the observation that the only time that the underlying SDLP constrains the size of the Encap packet is when the underlying service is the TC VCP service, where the maximum size of data unit carried
by the Encap Packet is constrained to be 1015 octets. For the other SDLP services:
</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">a. When Encapsulation Packets are transferred via the TC MAPP and USLP MAPP services, segmentation is used to break large Encap Packets in order
to fit into TC/USLP transfer frames.</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">b. When Encapsulation Packets are transferred via the TM VCP and AOS VCP services, the respective Packet Processing functions break up the encap
packets as necessary to fit them into M_PDUs.</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">If we have misinterpreted anything here please let us know.</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">3. The Encapsulation Function performs a multiplexing function by forming Encap packets from data units from different “protocol users”, and multiplexing
those packets into a single stream of Encap packets for the underlying Packet service. We observe that, unlike other CCSDS SDLP functions that perform multiplexing (Space Packets, Packets, VC Frames, and MC Frames), there is no mention in the EPP Blue Book
of multiplexing priority. We interpret that as the intention of the SLPWG that the multiplexing of Encap packets been done on a FIFO basis. We concur with this approach, as we can see no practical reason for other multiplexing schemes, and we plan to define
this aspect of the corresponding functional resource to be FIFO only.</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">4. Finally, here’s an editorial error that should be fixed in the next editorial-level update of the EPP Blue Book: although the title of the book
was changed from <i>Encapsulation Service</i> to <i>Encapsulation Packet Protocol</i>, the heading on each page in B-3still reads “CCSDS RECOMMENDED STANDARD FOR ENCAPSULATION SERVICE”.</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 in advance for any comments that you may have.</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">Best regards,</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</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><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>