[Sls-slp] Idle Packet Idle Pattern

[Moore, Kevan L. (MSFC-HP27)[HOSC SERVICES CONTRACT]]

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.

Happy to change to whatever the working group decides.

Just happy to finally get one right. :)

Kevan
MSFC

From: SLS-SLP [mailto:sls-slp-bounces at mailman.ccsds.org] On Behalf Of John Pietras
Sent: Wednesday, January 31, 2018 2:42 PM
To: sls-slp at mailman.ccsds.org
Subject: [Sls-slp] Idle Packet Idle Pattern

Dear All,
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.

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.

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.

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.

Best regards,
John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/sls-slp/attachments/20180131/0fc2c791/attachment.html>