<html 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)">
<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:11.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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
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.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
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;}
--></style>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">I agree. Indeed, there have actually been missions who don’t use a fixed pattern in the OID frames nor Idle packets.
<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">SLS-SLP <sls-slp-bounces@mailman.ccsds.org> on behalf of "Gian.Paolo.Calzolari@esa.int" <Gian.Paolo.Calzolari@esa.int><br>
<b>Date: </b>Wednesday, January 31, 2018 at 1:29 PM<br>
<b>To: </b>"Moore, Kevan L. (MSFC-HP27)[HOSC SERVICES CONTRACT]" <kevan.l.moore@nasa.gov><br>
<b>Cc: </b>"sls-slp@mailman.ccsds.org" <sls-slp@mailman.ccsds.org><br>
<b>Subject: </b>Re: [Sls-slp] Idle Packet Idle Pattern<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><a name="_MailOriginalBody">Of course we shall not confuse OID frames with Idle Packets.
<o:p></o:p></a></p>
<div>
<p class="MsoNormal"><span style="mso-bookmark:_MailOriginalBody"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="mso-bookmark:_MailOriginalBody">Having said this, I have dome doubts about storing this as managed parameter (no matter for frames or packets) as we cannot be sure this will always be a fixed pattern. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="mso-bookmark:_MailOriginalBody"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="mso-bookmark:_MailOriginalBody">BTW in the C&S wg some time ago there was an issue with OID frames generating spectrum issues because of the constant pattern. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="mso-bookmark:_MailOriginalBody"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="mso-bookmark:_MailOriginalBody">Just my cent, but worth a discussion <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="mso-bookmark:_MailOriginalBody"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="mso-bookmark:_MailOriginalBody">Gian Paolo<o:p></o:p></span></p>
<div id="AppleMailSignature">
<p class="MsoNormal"><span style="mso-bookmark:_MailOriginalBody">Sent from my iPhone<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="mso-bookmark:_MailOriginalBody"><br>
On 31. Jan 2018, at 21:59, Moore, Kevan L. (MSFC-HP27)[HOSC SERVICES CONTRACT] <</span><a href="mailto:kevan.l.moore@nasa.gov"><span style="mso-bookmark:_MailOriginalBody">kevan.l.moore@nasa.gov</span><span style="mso-bookmark:_MailOriginalBody"></span></a><span style="mso-bookmark:_MailOriginalBody">>
wrote:<o:p></o:p></span></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span style="mso-bookmark:_MailOriginalBody"><span style="color:#1F497D">I came to the same conclusino as John and had already implemented a PHYSICAL_CHANNEL_OID_Frame_Content managed parameter. The pattern repeats to fill the required
space.</span><o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailOriginalBody"><span style="color:#1F497D"> </span><o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailOriginalBody"><span style="color:#1F497D">Happy to change to whatever the working group decides.</span><o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailOriginalBody"><span style="color:#1F497D"> </span><o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailOriginalBody"><span style="color:#1F497D">Just happy to finally get one right. :)</span><o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailOriginalBody"><span style="color:#1F497D"> </span><o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailOriginalBody"><span style="color:#1F497D">Kevan</span><o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailOriginalBody"><span style="color:#1F497D">MSFC</span><o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailOriginalBody"><span style="color:#1F497D"> </span><o:p></o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><span style="mso-bookmark:_MailOriginalBody"><b>From:</b></span><span style="mso-bookmark:_MailOriginalBody"> SLS-SLP [</span><a href="mailto:sls-slp-bounces@mailman.ccsds.org"><span style="mso-bookmark:_MailOriginalBody">mailto:sls-slp-bounces@mailman.ccsds.org</span><span style="mso-bookmark:_MailOriginalBody"></span></a><span style="mso-bookmark:_MailOriginalBody">]
<b>On Behalf Of </b>John Pietras<br>
<b>Sent:</b> Wednesday, January 31, 2018 2:42 PM<br>
<b>To:</b> </span><a href="mailto:sls-slp@mailman.ccsds.org"><span style="mso-bookmark:_MailOriginalBody">sls-slp@mailman.ccsds.org</span><span style="mso-bookmark:_MailOriginalBody"></span></a><span style="mso-bookmark:_MailOriginalBody"><br>
<b>Subject:</b> [Sls-slp] Idle Packet Idle Pattern<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span style="mso-bookmark:_MailOriginalBody"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:12.0pt">Dear All,</span><o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:12.0pt">I’m sorry that I wasn’t able to participate in today’s telecon, due to a prior commitment. Having not participated, I don’t know the final fate of the SPP book.
But there is one other item that I came across that I’d like to bring to the WG’s attention as something else to consider in the process of cleaning up (or replacing) the SPP book.</span><o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:12.0pt"> </span><o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:12.0pt">The Packet Processing function of the AOS SDLP includes generation of Idle Packets when no packets containing user data are available. The definition of “Idle Packet”
is cross-referenced to the SPP book.</span><o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:12.0pt"> </span><o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:12.0pt">The SPP book states “If the Packet is an Idle Packet, the User Data Field shall contain Idle Data”, and follows this with the NOTE “The
bit pattern of Idle Data is not specified in this Recommendation.” The trail goes cold there.</span><o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:12.0pt"> </span><o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:12.0pt">A similar situation exists for the multiplexing schemes for VCs and MCs (that is they are not defined by the SDLP Recommended Standards),
but in those cases the multiplexing schemes are identified as Managed Parameters. Given that “Managed Parameters” is another way of saying “stuff that has to be configured that is not defined in the book itself”, I suggest that the packet Idle Pattern also
be treated as a Managed Parameter. </span><o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:12.0pt"> </span><o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:12.0pt">Best regards,</span><o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:12.0pt">John</span><o:p></o:p></span></p>
</div>
</blockquote>
</div>
<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>
<pre><span style="mso-bookmark:_MailOriginalBody"><o:p> </o:p></span></pre>
</div>
</body>
</html>