<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: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;}
/* 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:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
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;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle18
{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:1875120444;
mso-list-type:hybrid;
mso-list-template-ids:-1354627048 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;}
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="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">John,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Now that I’ve had a bit of time to digest this, some comments, questions.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="color:#1F497D"><span style="mso-list:Ignore">1)<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">Pg 6, it will probably be helpful if a diagram could be produced that illustrates the situation. I hope that is not a significant undertaking.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="color:#1F497D"><span style="mso-list:Ignore">2)<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">Assuming that the FRIN being used in the SII is as I think it is (the diagram will help), it does raise some potential concerns<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo1">
<![if !supportLists]><span style="color:#1F497D"><span style="mso-list:Ignore">a.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">If we assume that the next generation service package has the current B-1 capability (which I believe is the case per the current abstract service request engineering under way) to modify a configuration
profile (technically profile re-specification) for the duration of the service package, then do we assume that the addition of a CSTS instance as part of that modification for the service package will come with a “pre-validated” FRIN
</span><span style="font-family:Wingdings;color:#1F497D">à</span><span style="color:#1F497D"> SII ? Or am I missing something here? (“Turning off” as CSTS instance does not seem like a problem). Also, we would probably disallow modification of FRINs as part
of the service package configuration profile re-specification? <o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo1">
<![if !supportLists]><span style="color:#1F497D"><span style="mso-list:Ignore">b.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">It seems that for this approach, for things like MD-CSTS or TD-CSTS instances would have to be part of the service configuration profile. I’m not sure we have agreement that this would be the case
– I think we have asked questions like “are things like MD-CSTS just assumed to be there or do they need to be explicitly defined in the service configuration profile”? I will agree that it does not seem like a likely use case to have two MD-CSTS (or TD-CSTS)
instances running in parallel, but I would not put it past an implementation to think of “interesting” deployment options. Again, perhaps I’m mission something here.
<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:1.0in"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">-Erik<o:p></o:p></span></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> css-csts-bounces@mailman.ccsds.org [mailto:css-csts-bounces@mailman.ccsds.org]
<b>On Behalf Of </b>John Pietras<br>
<b>Sent:</b> Monday, June 01, 2015 9:33 AM<br>
<b>To:</b> CCSDS SMWG ML (smwg@mailman.ccsds.org); CCSDS_CSTSWG (css-csts@mailman.ccsds.org)<br>
<b>Subject:</b> [Css-csts] Relationship between CSTS Service Instance Identifier and Extensible SCCS-SM<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">CSSMWG and CSTSWG colleagues ---<o:p></o:p></p>
<p class="MsoNormal">As part of the review process of the Cross Support Transfer Service Specification Framework (CSTS SFW) prior to final submission to the Secretariat,
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Margherita di Giulio (CSTSWG chairperson) noticed that the Service Instance Identifier (SII) parameter of the CSTS BIND invocation message contained a “transferServiceProfileId’ subfield, for which
the content and syntax were not defined. In fact the transferServiceProfileId is an artifact of (Version 1) Service Management, but the question raise by Margherita initiated an examination of whether this was still appropriate for use in the SII. The conclusion
is that it is *<b>not</b>* the most appropriate identifier for use in the SII. Wolfgang Hell and I have developed an alternative approach based on Functional Resource concepts and constructs.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Because this represents a case of the intersection of Service Management and CSTS, I’ll be giving a presentation (attached) on the topic at tomorrow’s (Tuesday’s) CSSMWG telecon.
Wolfgang and I have convinced ourselves that he proposed approach is the right one, but we welcome any feedback that you might have.<o:p></o:p></span></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"><o:p> </o:p></p>
</div>
</body>
</html>