<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:"Times New Roman \(Body CS\)";
panose-1:2 2 6 3 5 4 5 2 3 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:12.0pt;
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>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Dear SLP WG (Keith and Tomaso too),<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I took the liberty of adding the USLP space data link protocol to the IP over CCSDS blue book, since it was missing this key space data link protocol (SDLP).<o:p></o:p></p>
<p class="MsoNormal">Please see the update I produced in our SLP WG CWE directory under the following URL:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><a href="https://cwe.ccsds.org/sls/docs/Forms/AllItems.aspx?RootFolder=%2Fsls%2Fdocs%2FSLS%2DSLP%2FMeeting%20Materials%2F2022%2FFall%2FIPoC&View=%7BAE8FB44C%2DE80A%2D42CF%2D8558%2DFB495ABB675F%7D&&InitialTabId=Ribbon%2ERead&VisibilityContext=WSSTabPersistence">https://cwe.ccsds.org/sls/docs/Forms/AllItems.aspx?RootFolder=%2Fsls%2Fdocs%2FSLS%2DSLP%2FMeeting%20Materials%2F2022%2FFall%2FIPoC&View=%7BAE8FB44C%2DE80A%2D42CF%2D8558%2DFB495ABB675F%7D&&InitialTabId=Ribbon%2ERead&VisibilityContext=WSSTabPersistence</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Upon updating IPoC, I noticed that USLP was missing the Virtual Channel Packet (VCP) and Virtual Channel Access Service (VCA). For IPoC, it seemed odd that all the other SDLPs had VCP, but USLP didn’t.<o:p></o:p></p>
<p class="MsoNormal">I think the rationale for not including it was essentially, USLP has both MAP Packet Service and MAP Access Service, and if a user didn’t plan on really using MAP IDs and preferred to use the GVCID as the SAP, then one would simply set
the MAP ID to default value 0, and be done. However, that is not consistent with Telecommand (TC) in that it has provision for both MAP Packet and VC Packet, and as documented in IPoC, a user could use either service to interface with IPoC. Therefore, I think
the short cut we may in USLP doesn’t help and I truly believe there will be users that want VCP or VCA service and don’t plan on using any MAPs at all. So I am requesting both SLS WG and SIS Area folks to take a look at this updated IPoC document. It will
be a topic for discussion at the SLP WG meeting at the Fall 2022 meeting. SLP WG will coordinate final changes with SIS area.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The other document for the SLP WG folks to review and comment on is USLP blue book. I added the VCP service and VCA service to the document. This involves mostly adding the service parameters and primitives which are well known and documented
in Telecommand (TC) with only a few changes due to the document references for the COP-1 and SDLS Core Protocol. The last change I added has to do with relaxing the USLP constraint of only limiting the “Maximum number of transfer frames given to the C&S Sublayer
as a Single Data Unit” from 1 to Integer. Rationale is that NASA/JPL has the SRL (Surface Retrieval Lander) plans on using multiple TC frames within a CLTU. So in weaker signal environments, missions like SRL plan on packing as many TC frames into a CLTU as
possible, to minimize the overhead (maximize the efficiency) in the number of uplink bits they transmit. In addition, since TC also allows for one or more TC frames to be contained within a CLTU, there is no advantage to be different in this respect with TC.
I recall that the SLP WG was trying to see if any space agency would place more than one frame within a CLTU, and now we do have that use case, so we need to respond to it and ease up on that constraint, which quite frankly is too imposing and doesn’t provide
us any advantage to be so rigid.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">So the sections in the USLP Blue book impacted are:<o:p></o:p></p>
<p class="MsoNormal">Section 3, Annex A (PICS Proforma) – adding VCP and VCA services<o:p></o:p></p>
<p class="MsoNormal">Section 2.4.1, 4.2.10.7 (All frames generation), 4.3.10.1.6 (All Frames Reception), Note in 4.3.10.2, Table 5-1 Managed Parameter, Annex A PICs Proforma for the value of that Managed Parameter (from one to Integer)<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The USLP Blue Book updates are under the following URL:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><a href="https://cwe.ccsds.org/sls/docs/Forms/AllItems.aspx?RootFolder=%2Fsls%2Fdocs%2FSLS%2DSLP%2FMeeting%20Materials%2F2022%2FFall%2FUSLP%20Blue%20Book&FolderCTID=0x012000439B56FF51847E41B5728F9730D7B55F&View=%7BAE8FB44C%2DE80A%2D42CF%2D8558%2DFB495ABB675F%7D">https://cwe.ccsds.org/sls/docs/Forms/AllItems.aspx?RootFolder=%2Fsls%2Fdocs%2FSLS%2DSLP%2FMeeting%20Materials%2F2022%2FFall%2FUSLP%20Blue%20Book&FolderCTID=0x012000439B56FF51847E41B5728F9730D7B55F&View=%7BAE8FB44C%2DE80A%2D42CF%2D8558%2DFB495ABB675F%7D</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">See file with August 1 in the file name. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">All of these updates are done in the Word Revision Feature so they show up in RED underlined text.
<o:p></o:p></p>
<p class="MsoNormal">These updates will also be discussed at the Fall 2022 SLP WG meeting. Your review and comments are essential and most welcome.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best regards,<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">Chair SLP WG<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></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">312B Project Protection, Project Software, and End to End Information System Engineering<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: greg.j.kazz@jpl.nasa.gov
</span><span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>