<font size=2 face="Arial">FYI</font>
<br><font size=1 color=#800080 face="sans-serif">----- Forwarded by Mario
Merri/esoc/ESA on 27/09/2016 19:26 -----</font>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">"Shames, Peter
M (312B)" <peter.m.shames@jpl.nasa.gov></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">"Nestor.Peccia@esa.int"
<Nestor.Peccia@esa.int>, "CCSDS Engineering Steering Group -
CESG Exec(cesg" <cesg@mailman.ccsds.org></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">26/09/2016 23:22</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">Re: [CESG] MOSSG
Report</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Sent by:
</font><font size=1 face="sans-serif">"CESG"
<cesg-bounces@mailman.ccsds.org></font>
<br>
<hr noshade>
<br>
<br>
<br><font size=2 face="Calibri">Nestor,</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">Here is the SEA feedback on this MOSSG
report. There are many issues, but to boil them down into just a
few major themes, it looks like this:</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">1) They ignore IOAG
Cat #1 and Cat #2. If there is a relationship it is unstated. </font>
<br><font size=2 face="Calibri">2) They ignore all
of the underlying CCSDS and Internet standards that provide the essential
communications fabric that any applications services require.</font>
<br><font size=2 face="Calibri">3) They state that
this is all about interoperability, but then do not tie down most of the
interfaces, application protocols, data objects, or communications layers
in a way where that could be achieved.</font>
<br><font size=2 face="Calibri">4) They take random
pot-shots at IOAG Cat#2 and internetworking, such as stating (on pg 13):
"</font><font size=3 color=#0082bf face="Times New Roman">They do
not require the overall, global management of a common resource like the
Solar System Internetwork in Service Catalog #2. Thus, a global Service
Management Framework is not required a priori. Service management is required
for MO services, however, and is supported via the Interoperability Framework.
</font><font size=2 face="Calibri">" In fact, what they do appear
to require is the "<b><i>global framework that is the Interoperability
Framework</i></b>", but that is not defined in any clear set
of interoperable specs. As this is worded there is no one set of
"framework" specs.</font>
<br><font size=2 face="Calibri">5) They do not clearly
define the set of information / data objects that must appear at any set
of application level interfaces.</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">Feel free to use this as you see fit.</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">Regards, Peter</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri"> </font>
<br><font size=3 face="Calibri"><b>From: </b>CESG <cesg-bounces@mailman.ccsds.org>
on behalf of Nestor Peccia <Nestor.Peccia@esa.int><b><br>
Date: </b>Monday, August 22, 2016 at 3:00 PM<b><br>
To: </b>CCSDS Engineering Steering Group - CESG Exec <cesg@mailman.ccsds.org><b><br>
Subject: </b>[CESG] MOSSG Report</font>
<br><font size=3 face="Times New Roman"> </font>
<br><font size=2 face="sans-serif">Dear all</font><font size=3 face="Times New Roman">
<br>
</font><font size=2 face="sans-serif"><br>
FYI and review</font><font size=3 face="Times New Roman"> </font><font size=2 face="sans-serif"><br>
I will add a point on the agenda of the next CESG webex</font><font size=3 face="Times New Roman">
<br>
</font><font size=2 face="sans-serif"><br>
If it is possible, your views are more than welcome (preferqbly prior to
the 7th Sept)</font><font size=3 face="Times New Roman"> <br>
<br>
</font><font size=2 face="sans-serif"><br>
ciao</font><font size=3 face="Times New Roman"> </font><font size=2 face="sans-serif"><br>
\nestor</font><font size=3 face="Times New Roman"> <br>
<br>
</font>
<br><font size=2 face="Courier New">This message and any attachments are
intended for the use of the addressee or addressees only.</font>
<br><font size=2 face="Courier New">The unauthorised disclosure, use, dissemination
or copying (either in whole or in part) of its</font>
<br><font size=2 face="Courier New">content is not permitted.</font>
<br><font size=2 face="Courier New">If you received this message in error,
please notify the sender and delete it from your system.</font>
<br><font size=2 face="Courier New">Emails can be altered and their integrity
cannot be guaranteed by the sender.</font>
<br><font size=2 face="Courier New"> </font>
<br><font size=2 face="Courier New">Please consider the environment before
printing this email.</font><tt><font size=2>_______________________________________________<br>
CESG mailing list<br>
CESG@mailman.ccsds.org<br>
</font></tt><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg"><tt><font size=2>https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg</font></tt></a><tt><font size=2><br>
</font></tt>
<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>