<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body 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>As a general principle I think it is important to keep in mind that we (and many other orgs) have purposely adopted the layers defined in the ISO Basic Reference Model (BRM), ISO/IEC 8498. We have, of course adapted it to our purposes, so we have separately
identified Modulation as a standardization topic (associated with the ISO Physical Layer, and Coding, as a sub-layer of the Link Layer.</div>
<div><br>
</div>
<div>The original ISO BRM dates back to 1979, a time when “Applications” were things like FTP (for file transfer) and Telnet (for remote login). The only other network “apps” were system utilities and things that users wrote using the socket layer. There
was no web, browsers, HTTP, XML, message busses, or any of that other stuff we all rely upon and carry around strapped to our belts. In this age we probably need to distinguish Applications (as in all sorts of user apps), from Application Support (HTTP, message
bus, SMTP, etc). With that parsing of the layers, all of the SIS application level standardards fall into Application Support. All of the MOIMS mission operations standards fall into Applications, whether they are the MAL (a framework that must be adapted
to support mission applications), or data and process standards such as the Nav and DAI produce. Any MOIMS MO services, like Robotics, also fall into this Applications Layer.</div>
<div><br>
</div>
<div>It’s worth noting that CSS also produces services, for cross support; services are not exclusive to MOIMS. And SOIS has also defined services in their on-board environment. The distinctions are tied to the domains in which they operate, cross support,
spacecraft on-board, and mission operations.</div>
<div><br>
</div>
<div>Perhaps we need to document these distinctions for CCSDS purposes, but in general these are understood as stated.</div>
<div><br>
</div>
<div>Regards, Peter</div>
<div><br>
</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 Mario Merri <<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 6:46 AM<br>
<span style="font-weight:bold">To: </span>Keith Scott <<a href="mailto:kscott@mitre.org">kscott@mitre.org</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><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>
</blockquote>
</span>
</body>
</html>