[Moims-dai] FW: [MOIMS] [CESG] MOSSG Report

[David Giaretta]

In case this not get to MOIMS-DAI

 

From: MOIMS [mailto:moims-bounces at mailman.ccsds.org] On Behalf Of
Mario.Merri at esa.int
Sent: 27 September 2016 18:26
To: moims at mailman.ccsds.org
Subject: Re: [MOIMS] [CESG] MOSSG Report

 

FYI 
----- Forwarded by Mario Merri/esoc/ESA on 27/09/2016 19:26 ----- 

From:        "Shames, Peter M (312B)" <peter.m.shames at jpl.nasa.gov
<mailto:peter.m.shames at jpl.nasa.gov> > 
To:        "Nestor.Peccia at esa.int <mailto:Nestor.Peccia at esa.int> "
<Nestor.Peccia at esa.int <mailto:Nestor.Peccia at esa.int> >, "CCSDS Engineering
Steering Group - CESG Exec(cesg" <cesg at mailman.ccsds.org
<mailto:cesg at mailman.ccsds.org> > 
Date:        26/09/2016 23:22 
Subject:        Re: [CESG] MOSSG Report 
Sent by:        "CESG" <cesg-bounces at mailman.ccsds.org
<mailto:cesg-bounces at mailman.ccsds.org> > 

  _____  




Nestor, 
  
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: 
  
1)       They ignore IOAG Cat #1 and Cat #2.  If there is a relationship it
is unstated.   
2)       They ignore all of the underlying CCSDS and Internet standards that
provide the essential communications fabric that any applications services
require. 
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. 
4)       They take random pot-shots at IOAG Cat#2 and internetworking, such
as stating (on pg 13): "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. "  In fact, what they do appear to
require is the "global framework that is the Interoperability Framework",
but that  is not defined in any clear set of interoperable specs.  As this
is worded there is no one set of "framework" specs. 
5)       They do not clearly define the set of information / data objects
that must appear at any set of application level interfaces. 
  
Feel free to use this as you see fit. 
  
Regards, Peter 
  
  
  
From: CESG <cesg-bounces at mailman.ccsds.org
<mailto:cesg-bounces at mailman.ccsds.org> > on behalf of Nestor Peccia
<Nestor.Peccia at esa.int <mailto:Nestor.Peccia at esa.int> >
Date: Monday, August 22, 2016 at 3:00 PM
To: CCSDS Engineering Steering Group - CESG Exec <cesg at mailman.ccsds.org
<mailto:cesg at mailman.ccsds.org> >
Subject: [CESG] MOSSG Report 
  
Dear all 

FYI and review 
I will add a point on the agenda of  the next CESG webex 

If it is possible, your views are more than welcome (preferqbly prior to the
7th Sept) 


ciao 
\nestor 


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._______________________________________________
CESG mailing list
CESG at mailman.ccsds.org <mailto:CESG at mailman.ccsds.org> 
 <https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg>
https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg

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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/moims-dai/attachments/20160927/702c359e/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: IOAG Service Catalog Three_20160728-SEA.docx
Type: application/octet-stream
Size: 2319741 bytes
Desc: not available
URL: <http://mailman.ccsds.org/pipermail/moims-dai/attachments/20160927/702c359e/attachment.obj>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: Untitled attachment 00234.txt
URL: <http://mailman.ccsds.org/pipermail/moims-dai/attachments/20160927/702c359e/attachment.txt>