<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=us-ascii">
<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:Georgia;
panose-1:2 4 5 2 5 4 5 2 3 3;}
/* 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;}
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:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Georgia",serif;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.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:920526982;
mso-list-type:hybrid;
mso-list-template-ids:-1761735570 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:1330399917;
mso-list-type:hybrid;
mso-list-template-ids:-325813828 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
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="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">Erik,<o:p></o:p></p>
<p class="MsoNormal">To address two of your questions:<o:p></o:p></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo3"><![if !supportLists]><span style="color:#1F497D"><span style="mso-list:Ignore">1.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]>The most-recently-posted version of the FR Reference Model Tech Note (0.14, dated July 2018, at URL<span style="color:#1F497D">
<br>
https://cwe.ccsds.org/css/docs/CSS%20Area/CWE%20Private/Functional%20Resources%20and%20Service%20Components/FunctionalResourcesRefModel_TechNote-TN-0.14-180730.docx</span>)
<br>
has placeholder sections for USLP in the forward direction (section 3.4.3) and return direction (section 3.4.5). However, these are truly merely placeholders at this point, and another possibility might be to combine the forward asynchronous form of USLP functionality
into the existing Forward Telecommand SLP Transmission FRs (section 3.4.1 of the FR Reference Model), the forward synchronous form of USDP functionality into the existing Forward AOS SLP Transmission FRs* (section 3.4.2 of the FR Ref Model), and the return
USLP functionality into the existing Return TM/AOS SLP Reception FRs (section 3.4.4 of the FR Ref Model). Indeed, the Return TM/AOS SLP Reception FRs already form a precedent for such combining of functionality in that they represent both the TM and AOS variants
of the return space data link protocols.<br>
[*Keep in mind that the Forward AOS <i>Space Data Link Protocol</i> functionality is already standardized. It is the Forward AOS
<i>Sync and Channel Coding</i> functions that are still being defined.] <span style="color:#1F497D">
<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo3"><![if !supportLists]><span style="color:#1F497D"><span style="mso-list:Ignore">2.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]>The Forward Frame CSTS is already set up to accommodate USLP. We deliberately made FF-CSTS as “agnostic” as possible with respect to the underlying space data link protocols, sync and channel coding schemes, and physical channel
(i.e., media – RF or optical), and in particular I endeavored to make sure that there was nothing about USLP that would make it incompatible with the Forward Frame service.<span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal">As of now, nothing has been done to assign the managed parameters, pending the decision as to whether to address the USLP functionality through dedicated FRs or through combining them with existing FRs. Going forward, I can start to investigate
this and make a recommendation (although I will not have a it completed by the Fall Workshop).<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Let me propose to put together a briefing for the Fall Workshop that introduces the Forward Frame service: what it does (with an emphasis on the user perception of the service and only minimal discussion of the internal composition such
as how it’s built on SFW procedures) and how it interacts with the forward space data link protocol functions and forward sync and channel coding functions. I would be willing to call into a WebEx of the joint meeting with the USLP folks at whatever time you
can set it up. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hopefully, the briefing would also have use beyond that one session, as an introduction for reviewers of the Forward Frame Red Book. The CSTSWG had originally hoped that the Red-1 review would have been completed by the Fall Workshop (optimism
springs eternal!) but given that the review period will almost certainly begin no sooner than the Fall Workshop the briefing could be a top-level ‘roadmap” as to why a reviewer should care about the service.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">And even if a joint session with the USLP folks doesn’t pan out, it might still be useful for the CSS Area itself.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">If it’s agreed that such a presentation would be useful, let me know and I’ll get started on it ASAP.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">One final observation regard USLP – although the Forward Frame CSTS has been made essentially underlying-protocol-agnostic, I don’t think that the same can be said for the SLE Forward Space Packet service, the definition of which is highly
intertwined with the Telecommand SDLP. Is it better to (a) “stretch” the FSP service to encompass USLP (and if so, would it only address the asynchronous form, which corresponds to TC, or both asynchronous and synchronous forms?), (b) restructure SLE FSP to
make it as agnostic as possible to the particular SDLP so as to support both TC and USLP, or (c) spin up a new CSTS FSP that covers TC and forward USLP and leave SLE FSP for legacy TC-only missions?<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">John<o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"><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"><b>From:</b> SMWG [mailto:smwg-bounces@mailman.ccsds.org] <b>
On Behalf Of </b>Barkley, Erik J (3970)<br>
<b>Sent:</b> Tuesday, September 25, 2018 8:41 PM<br>
<b>To:</b> css-csts@mailman.ccsds.org; CCSDS Service Mgmt WG <smwg@mailman.ccsds.org><br>
<b>Subject:</b> [Smwg] Proposed topic for joint meeting: USLP + CSS Area<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Georgia",serif">CSTS and CSSM Colleagues,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Georgia",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Georgia",serif">The USLP (Universal Space Link Protocol) recommendation is currently undergoing CESG polling in consideration for being approved as Blue Book. I think this merits some discussion
at our joint session for the upcoming fall meetings. In particular, I think it would be good to check re:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Georgia",serif"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo2"><![if !supportLists]><span style="font-size:12.0pt;font-family:"Georgia",serif"><span style="mso-list:Ignore">1)<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:12.0pt;font-family:"Georgia",serif">USLP vs Functional resource model – do we have new resources to add and/or existing ones to update?<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo2"><![if !supportLists]><span style="font-size:12.0pt;font-family:"Georgia",serif"><span style="mso-list:Ignore">2)<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:12.0pt;font-family:"Georgia",serif">How do FF-CSTS and USLP fit together? (in particular in reference to the diagram below from the USLP draft recommendation)<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo2"><![if !supportLists]><span style="font-size:12.0pt;font-family:"Georgia",serif"><span style="mso-list:Ignore">3)<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:12.0pt;font-family:"Georgia",serif">Inclusion of managed parameters in service management configuration profile and/or service agreement<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Georgia",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Georgia",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Georgia",serif">---USLP sending protocol entity organization (per USLP draft recommendation)---
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Georgia",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><img width="688" height="459" id="Picture_x0020_1" src="cid:image001.png@01D45575.9B34CB50"><span style="font-size:12.0pt;font-family:"Georgia",serif"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Georgia",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Georgia",serif"><o:p> </o:p></span></p>
</div>
</body>
</html>