<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 18px; font-family: Calibri, sans-serif;">
<div>
<div>
<div>Yeah. I think in the text of what I sent I used ‘application support protocols’ and in one case ‘the services provided by these protocols…’. That seems consistent with what you say here, I think.</div>
<div><br>
</div>
<div><span class="Apple-tab-span" style="white-space:pre"></span>—keith</div>
<div>
<div id="MAC_OUTLOOK_SIGNATURE"></div>
</div>
</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:12pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Peter Shames<br>
<span style="font-weight:bold">Date: </span>Tuesday, August 11, 2015 at 11:27 AM<br>
<span style="font-weight:bold">To: </span>"Scott, Keith L.", "<a href="mailto:Mario.Merri@esa.int">Mario.Merri@esa.int</a>"<br>
<span style="font-weight:bold">Cc: </span>Nestor Peccia, Brian Oliver, CCSDS Exec<br>
<span style="font-weight:bold">Subject: </span>Re: [CESG] Comment on the CSS Area portion of the CCSDS strategic plan<br>
</div>
<div><br>
</div>
<div>
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>I think I would avoid using terms like “network service”, because these protocols only nominally offer anything like a Service Access Point. I do agree that AMS is more of the nature of what I called an “Application Support” protocol. I’m not hard over
on the term, but we need some way, I think, to distinguish these support protocols that are nominally in the “Application” layer, but whose role is to provide varius kinds of data transfer services in support of other applications. I think if we reseve the
term “Applications” or even “User Applications” for those apps that do user specific work, as opposed to moving bits about, we may get some leverage out of that.</div>
<div><br>
</div>
<div>My sensitivity about the reservation of the term “service” for things like SLE, CSTS, CSSM, etc, as well as future Robotics services, mission planning services, etc, is that these all expose specific application specific service interfaces, where the interface
is an essential part of the specification instead of an optional abstraction.</div>
<div><br>
</div>
<div>Does this distinction make sense?</div>
<div><br>
</div>
<div>Regards, Peter</div>
<div><br>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span><<a href="mailto:cesg-bounces@mailman.ccsds.org">cesg-bounces@mailman.ccsds.org</a>> on behalf of Keith Scott <<a href="mailto:kscott@mitre.org">kscott@mitre.org</a>><br>
<span style="font-weight:bold">Date: </span>Tuesday, August 11, 2015 at 8:01 AM<br>
<span style="font-weight:bold">To: </span>Mario Merri <<a href="mailto:Mario.Merri@esa.int">Mario.Merri@esa.int</a>><br>
<span style="font-weight:bold">Cc: </span>Nestor Peccia <<a href="mailto:Nestor.Peccia@esa.int">Nestor.Peccia@esa.int</a>>, Brian Oliver <<a href="mailto:briano@aiaa.org">briano@aiaa.org</a>>, CCSDS Engineering Steering Group - CESG Exec <<a href="mailto:cesg@mailman.ccsds.org">cesg@mailman.ccsds.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [CESG] Comment on the CSS Area portion of the CCSDS strategic plan<br>
</div>
<div><br>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 18px; font-family: Calibri, sans-serif;">
<div>
<div>
<div>OK, and yes, there is an historical inconsistency there. I think what you’re suggesting is the same thing I want — to get people (like MOIMS, SOIS, etc.) to think of applications over network rather than just applications (and not thinking of what’s under
them, but probably assuming link). SIS took on ‘applications' like CFDP and AMS, though our main focus is network and transport (and maybe I should add in ‘application support’ protocols per Peter’s email. I’ve always had difficulty with ‘application support'
(e.g. HTTP, I think, can be used for both, depending on context; when I invoke ftp from the command line, I think of it as THE application I’m using, but if some other application invokes an ftp file transfer, is FTP then an application service?). To the
transport layer, AMS looks like an application, but I concur that it’s intended to be used by OTHER applications as a … well, service, rather than a ‘direct-user’ application. Maybe I want people to think of ‘application-over-network OR application-over-network-service’.</div>
<div><br>
</div>
<div>I’ve revised the text to add ‘application-service’ protocols in the initial definition, and changed goal 3 to ‘develop application support protocols that facilitate…’</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><span class="Apple-tab-span" style="white-space:pre"></span>—keith</div>
<div>
<div id=""></div>
</div>
</div>
<div>
<div id=""></div>
</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:12pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>"<a href="mailto:Mario.Merri@esa.int">Mario.Merri@esa.int</a>"<br>
<span style="font-weight:bold">Date: </span>Monday, August 10, 2015 at 9:46 AM<br>
<span style="font-weight:bold">To: </span>"Scott, Keith L."<br>
<span style="font-weight:bold">Cc: </span>Brian Oliver, CCSDS Exec, Nestor Peccia<br>
<span style="font-weight:bold">Subject: </span>Re: [CESG] Comment on the CSS Area portion of the CCSDS strategic plan<br>
</div>
<div><br>
</div>
<div>
<div><font size="2" face="Arial">Keith,</font> <br>
<br>
<font size="2" face="Arial">1) 3rd goal: I proposed that change to make the goal consistent with your proposed change in the 2nd paragraph on top where you substituted "Application" with "Transport". No problem in leaving "applications", but then you should
better qualify or limit the goal. Below a few relevant considerations from my side.</font><br>
<br>
<font size="2" face="Arial">Video and Audio: my understanding is that these WGs aim at identifying interoperable solutions in terms of communications, protocol and data formats. We had already many joint meetings with Rodney on having on top of this standard
Video/Camera services that could be based on MO Services. I would think the same apply to Voice. AMS is concerned with message transfer, so it is still at transport level. CFDP is a file transfer mechanism: there is already an identified MO service, the File
Management Service, that will use CFDP if this is required by the mission.</font><br>
<br>
<font size="2" face="Arial">2) I think that there is no disagreement here. The main reason of my proposed change is that the MOIMS is not developing applications, but data (e.g. NAV formats) and services (e.g. MO services), therefore technically there is no
"MOIMS application". </font><br>
<br>
<font size="2" face="Arial">Regards,</font> <br>
<br>
<font size="2" face="Arial">__Mario</font> <br>
<br>
<br>
<br>
<font size="1" color="#5f5f5f" face="sans-serif">From: </font><font size="1" face="sans-serif">"Scott, Keith L." <<a href="mailto:kscott@mitre.org">kscott@mitre.org</a>></font><br>
<font size="1" color="#5f5f5f" face="sans-serif">To: </font><font size="1" face="sans-serif">"<a href="mailto:Mario.Merri@esa.int">Mario.Merri@esa.int</a>" <<a href="mailto:Mario.Merri@esa.int">Mario.Merri@esa.int</a>>,
</font><br>
<font size="1" color="#5f5f5f" face="sans-serif">Cc: </font><font size="1" face="sans-serif">Brian Oliver <<a href="mailto:briano@aiaa.org">briano@aiaa.org</a>>, "<a href="mailto:cesg@mailman.ccsds.org">cesg@mailman.ccsds.org</a>" <<a href="mailto:cesg@mailman.ccsds.org">cesg@mailman.ccsds.org</a>>,
"<a href="mailto:Nestor.Peccia@esa.int">Nestor.Peccia@esa.int</a>" <<a href="mailto:Nestor.Peccia@esa.int">Nestor.Peccia@esa.int</a>></font><br>
<font size="1" color="#5f5f5f" face="sans-serif">Date: </font><font size="1" face="sans-serif">10/08/2015 15:14</font><br>
<font size="1" color="#5f5f5f" face="sans-serif">Subject: </font><font size="1" face="sans-serif">Re: [CESG] Comment on the CSS Area portion of the CCSDS strategic plan</font><br>
<hr noshade="">
<br>
<br>
<br>
<font size="4" face="Calibri">Mario,</font> <br>
<br>
<font size="4" face="Calibri">Thanks for the feedback.</font> <br>
<br>
<font size="4" face="Calibri">I’d like to leave ‘applications’ in the third SIS goal, at least for the moment. We’ve got the Voice and Motion Imaging WGs finishing up their work, and SIS is also home to things like CFDP and AMS. I do agree that MOIMS owns
at least a large piece of the ‘applications’ space within CCSDS and it is NOT SIS’ intent to pursue application development where such applications can be taken on by other areas (e.g. MOIMS, SOIS, CSS).</font><br>
<br>
<font size="4" face="Calibri">You also replaced ‘MOIMS <b><i>applications</i></b> over SIS internetworks’ with ‘MOIMS
<b><i>data and services</i></b> over SIS internetworks’. I’m fine with that but I thought there was an advantage (in promoting the SIS view of the world, at least) to ‘applications’ there as it reinforced the notion that SIS was doing internetwork stuff and
the things running OVER the internetwork were applications. Regardless of the language, this (apps over network) is the view SIS would like to promote. Are you strongly in favor of the ‘data and services’ language? Is there a reason for your suggested change
that I’m missing?</font> <br>
<br>
<br>
<font size="4" face="Calibri">V/r,</font> <br>
<br>
<font size="4" face="Calibri">—keith</font> <br>
<br>
<font size="3" face="Calibri"><b>From: </b>"</font><a href="mailto:Mario.Merri@esa.int"><font size="3" color="blue" face="Calibri"><u>Mario.Merri@esa.int</u></font></a><font size="3" face="Calibri">"<b><br>
Date: </b>Monday, August 10, 2015 at 8:56 AM<b><br>
To: </b>"Scott, Keith L."<b><br>
Cc: </b>Brian Oliver, CCSDS Exec, Nestor Peccia<b><br>
Subject: </b>Re: [CESG] Comment on the CSS Area portion of the CCSDS strategic plan</font><br>
<br>
<font size="2" face="Arial">Hi Keith,</font><font size="4" face="Calibri"> <br>
</font><font size="2" face="Arial"><br>
my comments embedded. Please note that for some reason, Word has decided to use the same colour (red) for both your and my changes, at least on my computer. I've unsuccessfully tried to change it.</font><font size="4" face="Calibri"><br>
</font><font size="2" face="Arial"><br>
Regards,</font><font size="4" face="Calibri"> <br>
</font><font size="2" face="Arial"><br>
__Mario</font><font size="4" face="Calibri"> <br>
<br>
<br>
<br>
<br>
</font><font size="1" color="#5f5f5f" face="sans-serif"><br>
From: </font><font size="1" face="sans-serif">"Scott, Keith L." <</font><a href="mailto:kscott@mitre.org"><font size="1" color="blue" face="sans-serif"><u>kscott@mitre.org</u></font></a><font size="1" face="sans-serif">></font><font size="1" color="#5f5f5f" face="sans-serif"><br>
To: </font><font size="1" face="sans-serif">"</font><a href="mailto:Nestor.Peccia@esa.int"><font size="1" color="blue" face="sans-serif"><u>Nestor.Peccia@esa.int</u></font></a><font size="1" face="sans-serif">" <</font><a href="mailto:Nestor.Peccia@esa.int"><font size="1" color="blue" face="sans-serif"><u>Nestor.Peccia@esa.int</u></font></a><font size="1" face="sans-serif">>,
</font><font size="1" color="#5f5f5f" face="sans-serif"><br>
Cc: </font><font size="1" face="sans-serif">Brian Oliver <</font><a href="mailto:briano@aiaa.org"><font size="1" color="blue" face="sans-serif"><u>briano@aiaa.org</u></font></a><font size="1" face="sans-serif">>, "CESG -- CCSDS-Engineering Steering Group
\(</font><a href="mailto:cesg@mailman.ccsds.org"><font size="1" color="blue" face="sans-serif"><u>cesg@mailman.ccsds.org</u></font></a><font size="1" face="sans-serif">\) \(</font><a href="mailto:cesg@mailman.ccsds.org"><font size="1" color="blue" face="sans-serif"><u>cesg@mailman.ccsds.org</u></font></a><font size="1" face="sans-serif">\)"
<</font><a href="mailto:cesg@mailman.ccsds.org"><font size="1" color="blue" face="sans-serif"><u>cesg@mailman.ccsds.org</u></font></a><font size="1" face="sans-serif">></font><font size="1" color="#5f5f5f" face="sans-serif"><br>
Date: </font><font size="1" face="sans-serif">10/08/2015 14:18</font><font size="1" color="#5f5f5f" face="sans-serif"><br>
Subject: </font><font size="1" face="sans-serif">Re: [CESG] Comment on the CSS Area portion of the CCSDS strategic plan</font><font size="1" color="#5f5f5f" face="sans-serif"><br>
Sent by: </font><a href="mailto:cesg-bounces@mailman.ccsds.org"><font size="1" color="blue" face="sans-serif"><u>cesg-bounces@mailman.ccsds.org</u></font></a><font size="4" face="Calibri"><br>
</font>
<hr noshade="">
<font size="4" face="Calibri"><br>
<br>
<br>
Proposed changes to the SIS Strategic Plan attached as a Word Document with Track Changes on.<br>
<br>
V/r, <br>
<br>
—keith </font><font size="1" face="sans-serif"><br>
[attachment "Online strategic Plan 20150810.docx" deleted by Mario Merri/esoc/ESA]
</font><font size="2" face="Calibri">_______________________________________________<br>
CESG mailing list</font><font size="2" color="blue" face="Calibri"><u><br>
</u></font><a href="mailto:CESG@mailman.ccsds.org"><font size="2" color="blue" face="Calibri"><u>CESG@mailman.ccsds.org</u></font></a><font size="4" color="blue" face="Calibri"><u><br>
</u></font><a href="http://mailman.ccsds.org/mailman/listinfo/cesg"><font size="2" color="blue" face="Calibri"><u>http://mailman.ccsds.org/mailman/listinfo/cesg</u></font></a><font size="4" face="Calibri"><br>
</font><br>
<font size="4" face="Calibri">This message and any attachments are intended for the use of the addressee or addressees only.<br>
The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its<br>
content is not permitted.<br>
If you received this message in error, please notify the sender and delete it from your system.<br>
Emails can be altered and their integrity cannot be guaranteed by the sender.<br>
<br>
Please consider the environment before printing this email.<br>
</font><br>
<pre>This message and any attachments are intended for the use of the addressee or addressees only.
The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its
content is not permitted.
If you received this message in error, please notify the sender and delete it from your system.
Emails can be altered and their integrity cannot be guaranteed by the sender.
Please consider the environment before printing this email.
</pre>
</div>
</div>
</span></div>
</div>
</blockquote>
</span></div>
</div>
</span>
</body>
</html>