<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=utf-8">
<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:Consolas;
panose-1:2 11 6 9 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:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
tt
{mso-style-priority:99;
font-family:"Courier New";}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
p.xxmsonormal, li.xxmsonormal, div.xxmsonormal
{mso-style-name:x_x_msonormal;
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.xxmsonormal0, li.xxmsonormal0, div.xxmsonormal0
{mso-style-name:x_x_msonormal0;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.xxmsochpdefault, li.xxmsochpdefault, div.xxmsochpdefault
{mso-style-name:x_x_msochpdefault;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:10.0pt;
font-family:"Calibri",sans-serif;}
span.xxmsohyperlink
{mso-style-name:x_x_msohyperlink;
color:blue;
text-decoration:underline;}
span.xxmsohyperlinkfollowed
{mso-style-name:x_x_msohyperlinkfollowed;
color:purple;
text-decoration:underline;}
span.xxhtmlpreformattedchar
{mso-style-name:x_x_htmlpreformattedchar;
font-family:Consolas;}
span.xxemailstyle21
{mso-style-name:x_x_emailstyle21;
font-family:"Georgia",serif;
color:#1F497D;}
span.xxemailstyle23
{mso-style-name:x_x_emailstyle23;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle30
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.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;}
--></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">Hi John,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Ok. Got it. So these ffinitiatorid's are really a sort of low-level id of the entity that initially is establishing, or responding to, a BIND request. Right? If I recall correctly, there must still be an IP address and a Port associated
with the BIND. Isn't there also an (optional) password for the BIND to provide a sort of normal "login userid / password" authentication pair, or am I way off base here?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I'm not sure if I have unwound this correctly, but in any event I get that if there is a registry of these ffinitiatorid's that this would be an asset protected by the service supplier and that any registry of passwords would (should) itself
be encrypted when at rest or in use. Right?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks, Peter<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-left:.5in"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">SMWG <smwg-bounces@mailman.ccsds.org> on behalf of John Pietras <john.pietras@gst.com><br>
<b>Date: </b>Tuesday, December 10, 2019 at 9:10 AM<br>
<b>To: </b>SMWG <smwg@mailman.ccsds.org><br>
<b>Cc: </b>Wolfgang Hell <wo_._he@t-online.de><br>
<b>Subject: </b>Re: [cssm] [Css-csts] [EXTERNAL] Re: Issue regarding initiator-identifier and responder-identifier<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt;color:black;background:white">This is a re-send of the message below, which was stopped by the SMWG mail list on the first attempt due to technical issues. My apologies if you are seeing
this message a second time.</span><span style="font-size:12.0pt;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt;color:black;background:white">Best regards,</span><span style="font-size:12.0pt;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt;color:black;background:white">John</span><span style="font-size:12.0pt;color:black"><o:p></o:p></span></p>
</div>
<div class="MsoNormal" align="center" style="margin-left:.5in;text-align:center">
<hr size="0" width="100%" align="center">
</div>
<div id="divRplyFwdMsg">
<p class="MsoNormal" style="margin-left:.5in"><b><span style="color:black">From:</span></b><span style="color:black"> John Pietras <jpietras@gst.com><br>
<b>Sent:</b> Tuesday, December 10, 2019 9:29 AM<br>
<b>To:</b> Shames, Peter M (US 312B) via SMWG <smwg@mailman.ccsds.org>; Barkley, Erik J (US 3970) <erik.j.barkley@jpl.nasa.gov>; Holger.Dreihahn@esa.int <Holger.Dreihahn@esa.int><br>
<b>Cc:</b> CSS-CSTS <css-csts-bounces@mailman.ccsds.org>; CCSDS_CSTSWG (css-csts@mailman.ccsds.org) <css-csts@mailman.ccsds.org><br>
<b>Subject:</b> Re: [Css-csts] [EXTERNAL] Re: Issue regarding initiator-identifier and responder-identifier</span>
<o:p></o:p></p>
<div>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt;color:black">Peter,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt;color:black">The initiatorId and responderId parameters (and their OIDs) are (will be) registered as part of every SLE and CSTS functional resource in the SANA Functional Resource Registry.
e.g., the name of the initiatorId parameter is ffInitiatorId, with the OID:<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt;color:black"> { iso(1) identified organizations(3) standard producing organization(112) ccsds(4) css(4) <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt;color:black"> crossSupportResources(2) crossSupportFunctinalities(2) FwdFrameCstsProvider(1000)<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt;color:black"> parameter-type(1) ffInitiatorId(4) version1(1) }<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt;color:black">[where the "1000" value for <span style="background:white">FwdFrameCstsProvider is a temporary placeholder until the actual value is assigned when it's uploaded to SANA].</span><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt;color:black;background:white"><br>
<br>
</span><span style="font-size:12.0pt;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt;color:black;background:white">Regarding the *values* of the initiatorId and responderId parameters, that has been a topic of discussion. According to Wolfgang, these have been traditionally
bilaterally negotiated between Provider CSSS and User Mission, and known only to a few members of those two parties, essentially the same as passwords. The discussion that we were having in CSTSWG was whether these value should ever appear information entities
such as the Service Agreement and Configuration Profiles, or whether they should continue to be negotiated and recorded by some other "more secure/more limited access" method. This latter line of thinking presupposes that Service Agreements and Configuration
Profiles will essentially be readily available to many people in the affected oganizations, of which only a relatively few should have access to the actual values of the initiatorId and responderId parameters. The intended caveat in the definitions of these
parameters ("</span><i><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#323130;background:white">A comment will be added in the semantic definition"</span></i><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#323130;background:white">)
will essentially defer to the authors of those documents whether they should be included or not, based on the security policies of the specific </span><span style="font-size:12.0pt;color:black;background:white">Provider CSSS and User Mission. The CSSMWG should
consider how to ensure that the different cases (e.g., included vs excluded) are supported by the affected Service Management information entities.</span><span style="font-size:12.0pt;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt;color:black;background:white"><br>
<br>
</span><span style="font-size:12.0pt;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt;color:black;background:white">By the way - I did not receive Erik's original message nor Holger's reply, both sent on Thursday. I know about this thread only because I just now read
Erik's and Peter's follow-up emails that they sent yesterday. That's likely due to an IT "situation" that hit GST last week. I need to check with our IT dept. to ensure that I'm not losing any more email. But if anyone sent me an email between Thursday afternoon
and Monday it might be a good idea to send it again.</span><span style="font-size:12.0pt;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt;color:black;background:white"><br>
<br>
</span><span style="font-size:12.0pt;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt;color:black;background:white">Thanks and sorry for the inconvenience.</span><span style="font-size:12.0pt;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt;color:black;background:white"><br>
<br>
</span><span style="font-size:12.0pt;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt;color:black;background:white">John </span><span style="font-size:12.0pt;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt;color:black;background:white"><br>
<br>
</span><span style="font-size:12.0pt;color:black"><o:p></o:p></span></p>
</div>
<div class="MsoNormal" align="center" style="margin-left:.5in;text-align:center">
<hr size="0" width="100%" align="center">
</div>
<div id="x_divRplyFwdMsg">
<p class="MsoNormal" style="margin-left:.5in"><b><span style="color:black">From:</span></b><span style="color:black"> SMWG <smwg-bounces@mailman.ccsds.org> on behalf of Shames, Peter M (US 312B) via SMWG <smwg@mailman.ccsds.org><br>
<b>Sent:</b> Monday, December 9, 2019 1:36 PM<br>
<b>To:</b> Barkley, Erik J (US 3970) <erik.j.barkley@jpl.nasa.gov>; Holger.Dreihahn@esa.int <Holger.Dreihahn@esa.int><br>
<b>Cc:</b> CSS-CSTS <css-csts-bounces@mailman.ccsds.org>; CCSDS Service Mgmt WG <smwg@mailman.ccsds.org>; CCSDS_CSTSWG (css-csts@mailman.ccsds.org) <css-csts@mailman.ccsds.org><br>
<b>Subject:</b> Re: [cssm] [Css-csts] [EXTERNAL] Re: Issue regarding initiator-identifier and responder-identifier</span>
<o:p></o:p></p>
<div>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="xxmsonormal" style="margin-left:.5in">I am curious if these initiator-ID and responder-ID use the OIDs defined in the SANA Org registry or something else? If "something else" is the answer, how are these related to the registered orgs, or is that
also a separate FR specific registry?<o:p></o:p></p>
<p class="xxmsonormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="xxmsonormal" style="margin-left:.5in">Thanks, Peter<o:p></o:p></p>
<p class="xxmsonormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="xxmsonormal" style="margin-left:.5in"> <o:p></o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="xxmsonormal" style="margin-left:1.0in"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">CSS-CSTS <css-csts-bounces@mailman.ccsds.org> on behalf of CSTS-WG <css-csts@mailman.ccsds.org><br>
<b>Reply-To: </b>Erik Barkley <erik.j.barkley@jpl.nasa.gov><br>
<b>Date: </b>Monday, December 9, 2019 at 10:18 AM<br>
<b>To: </b>"Holger.Dreihahn@esa.int" <Holger.Dreihahn@esa.int><br>
<b>Cc: </b>CSS-CSTS <css-csts-bounces@mailman.ccsds.org>, SMWG <smwg@mailman.ccsds.org>, CSTS-WG <css-csts@mailman.ccsds.org><br>
<b>Subject: </b>Re: [Css-csts] [EXTERNAL] Re: Issue regarding initiator-identifier and responder-identifier</span><o:p></o:p></p>
</div>
<div>
<p class="xxmsonormal" style="margin-left:1.0in"> <o:p></o:p></p>
</div>
<p class="xxmsonormal" style="margin-left:1.0in"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">Hello Holger,</span><o:p></o:p></p>
<p class="xxmsonormal" style="margin-left:1.0in"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="xxmsonormal" style="margin-left:1.0in"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">Thank you for the quick update. What you have noted sounds very good and I think we are indeed in agreement.</span><o:p></o:p></p>
<p class="xxmsonormal" style="margin-left:1.0in"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="xxmsonormal" style="margin-left:1.0in"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">Best regards,</span><o:p></o:p></p>
<p class="xxmsonormal" style="margin-left:1.0in"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D">-Erik</span><o:p></o:p></p>
<p class="xxmsonormal" style="margin-left:1.0in"><span style="font-size:14.0pt;font-family:"Georgia",serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="xxmsonormal" style="margin-left:1.0in"><b>From:</b> Holger.Dreihahn@esa.int <Holger.Dreihahn@esa.int>
<br>
<b>Sent:</b> Thursday, December 5, 2019 23:07<br>
<b>To:</b> Barkley, Erik J (US 3970) <erik.j.barkley@jpl.nasa.gov><br>
<b>Cc:</b> CCSDS_CSTSWG (css-csts@mailman.ccsds.org) <css-csts@mailman.ccsds.org>; CSS-CSTS <css-csts-bounces@mailman.ccsds.org>; EXTERNAL-Pietras, John V (US 332C-Affiliate) <john.pietras@gst.com>; CCSDS Service Mgmt WG <smwg@mailman.ccsds.org>; Wolfgang Hell
<wo_._he@t-online.de><br>
<b>Subject:</b> [EXTERNAL] Re: [Css-csts] Issue regarding initiator-identifier and responder-identifier<o:p></o:p></p>
<p class="xxmsonormal" style="margin-left:1.0in"> <o:p></o:p></p>
<p class="xxmsonormal" style="margin-left:1.0in"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Hi Erik,</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">For the business of the initiator identifier and responder identifier we noted yesterday the following:</span>
<br>
<br>
<i><span style="font-size:10.0pt;font-family:"Arial",sans-serif">The WG agrees that initiator ID, responder ID and responder port ID are in the FR model. Wolfgang will add them for SLE. A comment will be added in the semantic definition. John will use that
approach as well.</span></i> <o:p></o:p></p>
<p style="margin-left:1.0in"><i><span style="font-size:10.0pt;font-family:"Arial",sans-serif">The decision if these parameters (like all parameters) are used for a particular MD SI configuration within a service agreement / configuration profiles is left to
Service Management.</span></i> <o:p></o:p></p>
<p style="margin-left:1.0in"><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">So the FRM will be complete and CSSM will take care when they are used. I think this should address your point and to me it feels right to go that way.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Best regards,</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Holger</span> <br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Holger Dreihahn<br>
European Spacecraft Operations Centre | European Space Agency | S-431<br>
+49 6151 90 2233 | </span><a href="http://www.esa.int/esoc"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">http://www.esa.int/esoc</span></a>
<br>
<br>
<br>
<br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">From: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif">"Barkley, Erik J\(US 3970\) via CSS-CSTS" <<a href="mailto:css-csts@mailman.ccsds.org">css-csts@mailman.ccsds.org</a>></span>
<br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">To: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif">"EXTERNAL-Pietras, John V (US 332C-Affiliate)" <<a href="mailto:john.pietras@gst.com">john.pietras@gst.com</a>>,
"CCSDS_CSTSWG (<a href="mailto:css-csts@mailman.ccsds.org">css-csts@mailman.ccsds.org</a>)" <<a href="mailto:css-csts@mailman.ccsds.org">css-csts@mailman.ccsds.org</a>>, "Wolfgang Hell" <<a href="mailto:wo_._he@t-online.de">wo_._he@t-online.de</a>></span>
<br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">Cc: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif">"CCSDS Service Mgmt WG" <<a href="mailto:smwg@mailman.ccsds.org">smwg@mailman.ccsds.org</a>></span>
<br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">Date: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif">05/12/2019 23:09</span>
<br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">Subject: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif">Re: [Css-csts] Issue regarding initiator-identifier and responder-identifier</span>
<br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">Sent by: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif">"CSS-CSTS" <<a href="mailto:css-csts-bounces@mailman.ccsds.org">css-csts-bounces@mailman.ccsds.org</a>></span>
<o:p></o:p></p>
<div style="margin-left:.5in">
<div class="MsoNormal" align="center" style="margin-left:.5in;text-align:center">
<hr size="0" width="100%" noshade="" style="color:#A0A0A0" align="center">
</div>
</div>
<p class="xxmsonormal" style="margin-left:1.0in"><br>
<br>
<br>
<span style="font-size:12.0pt;font-family:"Georgia",serif;color:#004080">John et al,</span>
<br>
<span style="font-size:12.0pt;font-family:"Georgia",serif;color:#004080"> </span>
<br>
<span style="font-size:12.0pt;font-family:"Georgia",serif;color:#004080">I think this is one of the issues that needs to be coordinated at the area level. As you have noted via your reference to the technote, the CSSM WG intends to essentially base the detailed
content of the configuration profile on the parameters stated in the FRM. It seems to me that it will be a substantially non-trivial enough job to pull off without having to resort to yet another mechanism other than FRs for stating the various initiator and
responder identifiers. I can appreciate the sensitive info/security concerns, but I think having the complete model is also important. From the CSSM perspective, it may in fact be more secure if this information is carried in the service package – SPDF book
-- (via modified result data set) such that you could in effect have “rolling” identifiers specific for instances that change tracking-pass to tracking-pass (assuming that the SP is itself encrypted signed and/or block-chained, etc). I think this might need
a broader discussion and so I am also copying the CSSM WG for cognizance. Unfortunately I was not able to attend the CSTS WG telecon scheduled for earlier today so perhaps this is overcome by events but I just wanted to see if we might come to a broader consensus
-- I tend to agree with your approach 3.</span> <br>
<span style="font-size:12.0pt;font-family:"Georgia",serif;color:#004080"> </span>
<br>
<span style="font-size:12.0pt;font-family:"Georgia",serif;color:#004080">Best regards,</span>
<br>
<span style="font-size:12.0pt;font-family:"Georgia",serif;color:#004080">-Erik </span>
<br>
<span style="font-size:12.0pt;font-family:"Georgia",serif;color:#004080"> </span>
<br>
<b><span style="font-size:12.0pt">From:</span></b><span style="font-size:12.0pt"> CSS-CSTS <<a href="mailto:css-csts-bounces@mailman.ccsds.org">css-csts-bounces@mailman.ccsds.org</a>>
<b>On Behalf Of </b>John Pietras<b><br>
Sent:</b> Tuesday, December 3, 2019 08:10<b><br>
To:</b> CCSDS_CSTSWG (<a href="mailto:css-csts@mailman.ccsds.org">css-csts@mailman.ccsds.org</a>) <<a href="mailto:css-csts@mailman.ccsds.org">css-csts@mailman.ccsds.org</a>>; Wolfgang Hell <<a href="mailto:wo_._he@t-online.de">wo_._he@t-online.de</a>><b><br>
Subject:</b> [EXTERNAL] [Css-csts] Issue regarding initiator-identifier and responder-identifier</span>
<br>
<span style="font-size:12.0pt"> </span> <br>
<span style="font-size:12.0pt">CSTSWG colleagues ---</span> <br>
<span style="font-size:12.0pt">Recently (perhaps in Darmstadt?) Wolfgang and I discussed whether the initiator-identifier and responder-identifier parameters of the Association Control procedure should be in the list of configuration parameters for a(n) SLE/CS
Transfer Service Provider FR. I had envisioned including them but Wolfgang has excluded them from his SLE TS Provider FRs (FCLTU, RAF, etc.). When we discussed it he stated his belief that they should not be in the FR definition because that is sensitive information
that should not be accessible by, for instance, MD-CSTS. Rather, Wolfgang argued, this information should be exchanged by some “other” (not specified by CCSDS) means. Conceptually, this other mechanism would contain these identifiers in a table that has as
a key into it the service-instance-identifier, which *<b>is</b>* in the FR definition. In particular Wolfgang said that he did not think that these parameters should be included in the configuration profiles that would be used for scheduling Service Packages.
Wolfgang’s argument made sense to me and I agreed with his logic, and planned to remove those parameters from the CSTS Provider FRs for which I am responsible – Forward Frame, Monitored Data, and Tracking Data.</span>
<br>
<span style="font-size:12.0pt"> </span> <br>
<span style="font-size:12.0pt">HOWEVER, I now realize that the FF, MD, and TD books *<b>all</b>* identify these two parameters as “service management” parameters and assign them their service-specific classifiers. The assignment of the classifiers implies that
these are to be registered as configuration parameters of the respective FRs, and there is *<b>no</b>* indication in any of the documentation that they are to be treated in a special manner – i.e., be excluded from the definition of the FRs that are registered
in SANA. </span><br>
<span style="font-size:12.0pt"> </span> <br>
<span style="font-size:12.0pt">Off the top of my head, I can think of several ways that we might remedy this problem:</span>
<o:p></o:p></p>
<p class="xxmsonormal" style="margin-left:1.5in;text-indent:-.25in">1.<span style="font-size:7.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:12.0pt">Somehow redefine them as some sort of “special” configuration parameters (nor “normal” service management parameters) in the FF, TD, and MD service specifications. E.g., no classifiers would be specified. This would involve
tweaking the FF book (relatively easy), TD book (a bit harder since it’s already been submitted to the Secretariat) and the MD book (involves a TC since it has already been published).</span>
<o:p></o:p></p>
<p class="xxmsonormal" style="margin-left:1.5in;text-indent:-.25in">2.<span style="font-size:7.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:12.0pt">Leave them as configuration parameters of the FRs and add them to the SANA Registry FR definitions, but include caveats on their definitions that recommend that they not be included in configuration profile and GET-able
only under highly secure circumstances. This approach (a) has no impact on the CSTS books and (b) allows whatever mechanisms that *<b>are</b>* used to leverage the existing information architecture – e.g., a privileged, secure instance of MD-CSTS could be
implemented that would be permitted to read these values (e.g., to confirm their real-time setting if the service user is having problems binding).</span>
<o:p></o:p></p>
<p class="xxmsonormal" style="margin-left:1.5in;text-indent:-.25in">3.<span style="font-size:7.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:12.0pt">Similar to option 2, leave them as configuration parameters of the FRs and add them to the SANA Registry FR definitions, but let the SMWG decide on and enforce the restrictions in the Configuration Profile specification,
and let the Agencies/Providers decide who can read these parameters.</span><o:p></o:p></p>
<p class="xxmsonormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:1.0in">
<span style="font-size:12.0pt">My preference would be for something along the lines of options 2 or 3.
</span><br>
<span style="font-size:12.0pt"> </span> <br>
<span style="font-size:12.0pt">In a somewhat related topic, there is also the responder-port-id parameter that is specified in the existing CSTS specifications as a service management parameter. Whatever we decide to do about the initiator-identifier and responder-identifier
parameters, we need to include the responder-port-id parameter as a parameter of FR because it *<b>does</b>* need to be in the configuration profiles in order to support the dynamic allocation method of TCP Socket scheduling that the SMWG wants to support
(see section 3.4.2 of </span><a href="https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Tech%20Note%20Development/Config%20Profile%20Svc%20Agreement%20Tech%20Note/Simplified%20ConfigProfilesAndSvcAgreements_TechNote-v1x4-clean.docx?Web=1"><span style="font-size:12.0pt;color:#0082BF">https://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Tech%20Note%20Development/Config%20Profile%20Svc%20Agreement%20Tech%20Note/Simplified%20ConfigProfilesAndSvcAgreements_TechNote-v1x4-clean.docx?Web=1</span></a><span style="font-size:12.0pt">)</span>
<br>
<span style="font-size:12.0pt"> </span> <br>
<span style="font-size:12.0pt">I don’t know if we’ll have time to discuss this on Thursday but we do need to resolve these issues.</span>
<br>
<span style="font-size:12.0pt"> </span> <br>
<span style="font-size:12.0pt">Best regards,</span> <br>
<span style="font-size:12.0pt">John</span> <br>
<span style="font-size:12.0pt"> </span><tt><span style="font-size:10.0pt">_______________________________________________</span></tt><span style="font-size:10.0pt;font-family:"Courier New""><br>
<tt>CSS-CSTS mailing list</tt><br>
<tt><a href="mailto:CSS-CSTS@mailman.ccsds.org">CSS-CSTS@mailman.ccsds.org</a></tt><br>
</span><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/css-csts"><tt><span style="font-size:10.0pt">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/css-csts</span></tt></a><span style="font-size:10.0pt;font-family:"Courier New""><br>
<br>
</span><o:p></o:p></p>
<pre style="margin-left:1.0in">This message is intended only for the recipient(s) named above. It may contain proprietary information and/or<o:p></o:p></pre>
<pre style="margin-left:1.0in">protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received<o:p></o:p></pre>
<pre style="margin-left:1.0in">this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect<o:p></o:p></pre>
<pre style="margin-left:1.0in">personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (<a href="mailto:dpo@esa.int">dpo@esa.int</a>).<o:p></o:p></pre>
</div>
</div>
</div>
</div>
</body>
</html>