<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)">
<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;}
/* 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;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
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><!--[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">CSSMWG colleagues ---<o:p></o:p></p>
<p class="MsoNormal">U have uploaded my slides from today’s discussion of the Simplified Configuration Profile and Service Agreement Tech Note. I have modified the slides to summarize what I understood to be the consensus on a couple of discussion items: (a)
that the Configuration Profiles would be maintained as part of the Service Agreement (the alternative was to keep them as separate information entities. Both approaches are viable: the important point is that configuration profiles are stand-alone in the information
they contain and do not need to be validated against allowed range/value constraints some other part of the Service Agreement) and (b) the Service Agreement will contain statically-defined default TCP sockets for each transfer service at each supporting ESLT,
but that it would be possible for a Provider CSSS to override those defaults and return dynamically-assigned TCP sockets as part of the Service Package Result. Also, the updated slides corrects the “home” of the statically-defined TCP Sockets as the so-called
proxy files, and not the SICF.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The slides can be found in the meeting materials folder at:<o:p></o:p></p>
<p class="MsoNormal"><a href="https://cwe.ccsds.org/css/docs/CSS-SM/Meeting%20Materials/2018/Fall/ConfigurationProfilesAndServiceProfiles-181015A.pptx">https://cwe.ccsds.org/css/docs/CSS-SM/Meeting%20Materials/2018/Fall/ConfigurationProfilesAndServiceProfiles-181015A.pptx</a><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>
</div>
</body>
</html>