<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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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-top:12.0pt;
margin-right:0in;
margin-bottom:0in;
margin-left:0in;
margin-bottom:.0001pt;
text-align:justify;
line-height:14.0pt;
font-size:12.0pt;
font-family:"Times New Roman",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:12.0pt;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
mso-add-space:auto;
text-align:justify;
line-height:14.0pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParagraphCxSpFirst
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:12.0pt;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
mso-add-space:auto;
text-align:justify;
line-height:14.0pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, div.MsoListParagraphCxSpMiddle
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
mso-add-space:auto;
text-align:justify;
line-height:14.0pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, div.MsoListParagraphCxSpLast
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
mso-add-space:auto;
text-align:justify;
line-height:14.0pt;
font-size:12.0pt;
font-family:"Times New Roman",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:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Georgia",serif;
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Georgia",serif;
color:windowtext;}
span.EmailStyle22
{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:2108693029;
mso-list-type:hybrid;
mso-list-template-ids:656819912 51823632 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-start-at:0;
mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Times New Roman",serif;
mso-fareast-font-family:"Times New Roman";}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
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"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Erik,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">I haven’t developed such a tool – in particular a spreadsheet - as you are describing. Given the still-fluid nature of the specific configuration parameters of
many of the FRs and the low level of resources (very part time for Wolfgang and me) that have been able to be applied to nailing them down so far, I have been concentrating on (a) getting the “big picture” Config Profile/Svg Agreement concepts nailed down
(a recent example being how the assignment of TCP Sockets to SLE TS and CSTS instances can be accomplished under both the legacy “SICF method” and the newer “dynamic allocation method that are described in 3.4.2 of the Tech Note) and (b) working with Wolfgang
to iron out the specific configuration parameters of the FRs for publication in the SANA FR Registry. As an intermediate step, I’ve included the tables of names of the FR configuration parameters in the Tech Note under each of the FRs, with the actual definitions
of those parameters being deferred to the (admittedly still-under-construction) SANA FR Registry.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">The closest thing to a “tool” such as you suggest that I have envisioned (at least until now) has been to develop XML schemas for the space link service profiles
as the config parameters of their constituent FRs get nailed down. A couple of years ago I did develop preliminary XML schemas for the F-CLTU Space Link Service Profile and the F-CLTU Space Link Service Configuration Profile (partial XML Spy diagrams for which
are presented in figures 7-9 and 7-10 of the Tech Note, respectively) and a listing of an example F-CLTU Space Link Service Configuration Profile XML file in 7.1.1.7 of the Tech Note). Please note that the details of these examples need to be updated, but
they give the gist of my thinking.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Having said that, the XML schemas themselves are admittedly *<b>not</b>* the most reader-friendly way to convey the parameters, especially for those who are less-
(or non-) conversant in XML. So I think that your proposal for something like a spreadsheet representation is a good idea eventually (e.g., by the time that the corresponding Blue Book is published). Once the FR config parameters are nailed down, then the
XML schemas can be nailed down as well as the details of any such spreadsheets.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">We’ve got several “entities” in various stages of development that are closely related to functional resources (FR Reference Model Tech Note, Holger’s FRM development
tool, SANA FR Registry, CP/SA Tech Note, and the planned CP/SA Formats Blue Book), and it’s easy to wonder how they all relate to each other. The following diagram represents my take on how they all fit – please (anyone) feel free to comment or express a different
opinion. I think that it’s mostly self-explanatory bit if anyone is interested we can discuss this at next Tuesday’s CSSMWG telecon and/or at the Spring Workshop.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><img width="1098" height="618" style="width:11.4375in;height:6.4375in" id="Picture_x0020_3" src="cid:image001.jpg@01D4F124.D1938650"></span><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"><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>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" align="left" style="margin-top:0in;text-align:left;line-height:normal">
<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"> Barkley, Erik J (3970) <erik.j.barkley@jpl.nasa.gov>
<br>
<b>Sent:</b> Thursday, April 11, 2019 2:36 PM<br>
<b>To:</b> John Pietras <john.pietras@gst.com><br>
<b>Cc:</b> CCSDS SMWG ML (smwg@mailman.ccsds.org) <smwg@mailman.ccsds.org><br>
<b>Subject:</b> RE: [Smwg] Updated Configuration Profile andCWE Service Agreement Tech Note on<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" align="left" style="text-align:left"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">John,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">I have been surveying the technote and I must say it is quite the oeuvre!
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">For those of use attempting to parse this into some sort of configuration profile book initial outline, I was wondering for all the various service profiles developed
if you had something like a spreadsheet that listed the parameters per FR grouping. For example, one of the groups in the Forward CLTU space link service profile (7.1.1) is fwd401SpaceLinkCarrierXmitFr and in here we have<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="line-height:normal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">fwd401CarrierXmitEirp<o:p></o:p></span></p>
<p class="MsoNormal" style="line-height:normal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">fwd401CarrierXmitPolarization, etc<o:p></o:p></span></p>
<p class="MsoNormal" style="line-height:normal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"><br>
And there is, of course, something similar for Telecommand Real-Time Multiplexed space link service profile (7.1.2)<o:p></o:p></span></p>
<p class="MsoNormal" style="line-height:normal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="line-height:normal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">I think it might make digesting this a bit easier if there is some sort of tool like a spreadsheet that had the service profiles indexed
by major functional groups and listed the parameters accordingly. I think that could also help to tease out more about how to structure the eventual service agreement/configuration profile for consumption by "mere mortals"
</span><span style="font-size:14.0pt;font-family:Wingdings;color:#1F497D">J</span><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">
<o:p></o:p></span></p>
<p class="MsoNormal" style="line-height:normal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="line-height:normal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">If there is no such tool please note I'm not asking that this be generated only if there is some sort of organizing tool that you might
have in the background.<o:p></o:p></span></p>
<p class="MsoNormal" style="line-height:normal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="line-height:normal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal" style="line-height:normal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">-Erik<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Georgia",serif;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" align="left" style="margin-top:0in;text-align:left;line-height:normal">
<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"> SMWG <<a href="mailto:smwg-bounces@mailman.ccsds.org">smwg-bounces@mailman.ccsds.org</a>>
<b>On Behalf Of </b>John Pietras<br>
<b>Sent:</b> Thursday, February 28, 2019 14:08<br>
<b>To:</b> CCSDS SMWG ML (<a href="mailto:smwg@mailman.ccsds.org">smwg@mailman.ccsds.org</a>) <<a href="mailto:smwg@mailman.ccsds.org">smwg@mailman.ccsds.org</a>><br>
<b>Subject:</b> [Smwg] Updated Configuration Profile andCWE Service Agreement Tech Note on<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" align="left" style="text-align:left"><o:p> </o:p></p>
<p class="MsoNormal" align="left" style="text-align:left"><span style="font-family:"Arial",sans-serif">CSSMWG colleagues –<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span style="font-family:"Arial",sans-serif">I have uploaded the latest update of the
<i>Requirements for Simple Configuration Profiles and Service Agreements</i> Tech Note to the CWE at URL:<o:p></o:p></span></p>
<p class="MsoListParagraph" align="left" style="text-align:left;text-indent:-.25in;mso-list:l0 level1 lfo2">
<![if !supportLists]><span style="mso-list:Ignore">-<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]><span style="font-family:"Arial",sans-serif"><a href="https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Tech%20Note%20Development/Config%20Profile%20Svc%20Agreement%20Tech%20Note/Simplified%20ConfigProfilesAndSvcAgreements_TechNote-v1x3.docx?Web=1">https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Tech%20Note%20Development/Config%20Profile%20Svc%20Agreement%20Tech%20Note/Simplified%20ConfigProfilesAndSvcAgreements_TechNote-v1x3.docx?Web=1</a><o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span style="font-family:"Arial",sans-serif">The major pieces of the update are:<o:p></o:p></span></p>
<p class="MsoListParagraphCxSpFirst" align="left" style="margin-left:13.75pt;mso-add-space:auto;text-align:left;text-indent:-9.0pt;mso-list:l0 level1 lfo2">
<![if !supportLists]><span style="mso-list:Ignore">-<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]><span style="font-family:"Arial",sans-serif">Updated material in section 4 to be consistent with the W-0.07 (December 2018) version of the SMURF White Book and current concepts for the Service Package Data Format.<o:p></o:p></span></p>
<p class="MsoListParagraphCxSpMiddle" align="left" style="margin-left:13.75pt;mso-add-space:auto;text-align:left;text-indent:-9.0pt;mso-list:l0 level1 lfo2">
<![if !supportLists]><span style="mso-list:Ignore">-<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]><span style="font-family:"Arial",sans-serif">Additional material in section 4 describing the adaptation of the Configuration Profiles and Service Agreements to support both pre-arranged SICF port allocation vs. dynamic port allocation
for SLE and CSTS transfer service instances.<o:p></o:p></span></p>
<p class="MsoListParagraphCxSpMiddle" align="left" style="margin-left:13.75pt;mso-add-space:auto;text-align:left;text-indent:-9.0pt;mso-list:l0 level1 lfo2">
<![if !supportLists]><span style="mso-list:Ignore">-<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]><span style="font-family:"Arial",sans-serif">Added placeholder sections for USLP Frame-based forward Space Link Service Profiles in section 7.<o:p></o:p></span></p>
<p class="MsoListParagraphCxSpMiddle" align="left" style="margin-left:13.75pt;mso-add-space:auto;text-align:left;text-indent:-9.0pt;mso-list:l0 level1 lfo2">
<![if !supportLists]><span style="mso-list:Ignore">-<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]><span style="font-family:"Arial",sans-serif">Updated Forward CADU and Forward AOS Frame Space Link Service Profiles in section 7 to include more details on fixed-length data unit sync and channel coding, consistent with the evolution
of the Forward Frame Cross Support Transfer Service.<o:p></o:p></span></p>
<p class="MsoListParagraphCxSpLast" align="left" style="margin-left:13.75pt;mso-add-space:auto;text-align:left;text-indent:-9.0pt;mso-list:l0 level1 lfo2">
<![if !supportLists]><span style="mso-list:Ignore">-<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]><span style="font-family:"Arial",sans-serif">Partially updated examples of the use of Configuration Profiles in Service Package Requests in section 8.<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span style="font-family:"Arial",sans-serif">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span style="font-family:"Arial",sans-serif">John<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><o:p> </o:p></p>
</div>
</body>
</html>