<font size=2 face="Arial">Hi Francois,</font>
<br>
<br><font size=2 face="Arial">sorry for the delay of my answer. However,
I did forward your email to Sam immediately when I received it as he is
working on the configuration service. </font>
<br>
<br><font size=2 face="Arial">I have not had any discussion on this topic
so far, but I find your charts very helpful. I will check with Sam if he
would like to have a short webex with you to clarify any of the concepts.
</font>
<br>
<br><font size=2 face="Arial">Thanks for these inputs!</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">Francois Allard/estec/ESA</font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">Mario Merri/esoc/ESA@ESA,
</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">23/01/2015 17:16</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">Re: [Moims-sc]
Actions for the Configuration service</font>
<br>
<hr noshade>
<br>
<br><font size=2 face="sans-serif">Mario</font>
<br>
<br><font size=2 face="sans-serif">The attached is preliminary. </font>
<br><font size=2 face="sans-serif">For now it summarizes where we are within
MOSSG. Which is not very detailed as an output</font>
<br><font size=2 face="sans-serif">However here it is. Know we will be
revisiting it at the MOSSG face to face meeting in March and may be at
an SMC MOSSG meeting like we did in London. Are you interested in that
idea?</font>
<br><font size=2 face="sans-serif">Best Regards</font>
<br>
<br>
<br><font size=2 face="sans-serif">Francois Allard<br>
Ground Segment Maintenance and Operations Manager<br>
ESTEC HSO-ICG<br>
Tel: +31 715653250<br>
Mob: +31 652062149<br>
e-mail: francois.allard@esa.int</font>
<br><font size=2 face="sans-serif">[attachment "MOSSG Telecon 22 January
2015.pptx" deleted by Mario Merri/esoc/ESA] </font>
<br>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">Mario Merri/esoc/ESA</font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">Francois Allard/estec/ESA@ESA,
</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">16/01/2015 12:24</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">[Moims-sc] Actions
for the Configuration service</font>
<br>
<hr noshade>
<br>
<br><font size=2 face="Arial">Hi Francois,</font>
<br>
<br><font size=2 face="Arial">Happy New Year.</font>
<br>
<br><font size=2 face="Arial">I attach a recent note from Sam which is
asking for inputs on the configuration services. This was a request from
the MOSSG. Maybe you want to distribute this note the the MOSSG group and
ask fro their use cases.</font>
<br>
<br><font size=2 face="Arial">Thanks</font>
<br>
<br><font size=2 face="Arial">__Mario</font>
<br><font size=1 color=#800080 face="sans-serif">----- Forwarded by Mario
Merri/esoc/ESA on 16/01/2015 12:22 -----</font>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">"Sam Cooper"
<Sam.Cooper@scisys.co.uk></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif"><moims-sc@mailman.ccsds.org>,
</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">13/01/2015 11:05</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">[Moims-sc] Actions
for the Configuration service</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Sent by:
</font><font size=1 face="sans-serif">moims-sc-bounces@mailman.ccsds.org</font>
<br>
<hr noshade>
<br>
<br>
<br><font size=2 face="Arial">Dear All,</font>
<br><font size=2 face="Arial"> </font>
<br><font size=2 face="Arial">This is a quick reminder that there was a
couple of actions on us all to review the need for the access control service
and also to provide use cases for the configuration service. Specifically
this would be how you would expect to use the configuration service and
what information you would expect to see in it.</font>
<br><font size=2 face="Arial"> </font>
<br><font size=2 face="Arial">From the minutes of the meeting (and as a
reminder):</font>
<br><font size=3 face="Arial"> </font>
<br><font size=2 face="Arial">Access Control Service. This service is currently
not in the book. The basic idea of the service is to manage the access
to functions. This service is also considered as a way to match the new
PUS-C feature to manage compound checking functions. After some discussion,
it was not clear if this requirement is needed at all. </font>
<br><font size=2 face="Calibri"><b><i>Action 141111-01 ALL to provide SC
with use cases that justify the need for the Access Control Service. Due
10Dec14.</i></b></font>
<br><font size=3 face="Arial"> </font>
<br><font size=2 face="Arial">Configuration Service: Currently the service
contains only 1 operation to activate a given configuration. It was discussed
if the service should be expanded to include also other capabilities, for
instance the ability to ingest/deliver a specific configuration. Also,
the availability of a standard (file) format to hold the configuration
could be useful: in this way the service provider and consumer could be
automatically configure their ends. </font>
<br><font size=2 face="Calibri"><b><i>Action 141111-04 ALL, including the
MOSSG, to provide SC with use cases for the Configuration Service. Due
10Dec14.</i></b></font>
<br><font size=2 face="Arial"> </font>
<br><font size=2 face="Arial">Myself and Cesar have proposed a solution
to the access control issue with the mapping to PUS-C check protection
so my immediate feeling is that as Access Control is not a problem that
we can quickly address if we want to keep the moment going we should put
it on the back burner for now.</font>
<br><font size=2 face="Arial"> </font>
<br><font size=2 face="Arial">Regarding Configuration, my idea is to have
it such that you can request from a service provider its configuration,
that there would be a standard format for that configuration, and that
you can request the configuration for a service provider that may cover
several services i.e. of the application rather than one specific service
of that application. Cesar has also suggested that the Directory service
should allow you to request the XML service specification which I also
think is a good idea. This fits with MOSSG’s request for automatic configuration
of clients.</font>
<br><font size=2 face="Arial"> </font>
<br><font size=2 face="Arial">If you could send me any thoughts you have
by the beginning of next week that would help me a lot.</font>
<br><font size=2 face="Arial"> </font>
<br><font size=2 face="Arial">Best regards,</font>
<br><font size=2 face="Arial">Sam.</font>
<br><font size=2 face="Arial"> </font>
<br><font size=2 face="Arial"> </font>
<br><font size=2 color=#a11f12 face="Arial">__________________________________________________________________</font>
<br><font size=2 color=#a11f12 face="Arial"><b><br>
Sam Cooper</b></font>
<br><font size=2 color=#a11f12 face="Arial">Systems Architect – Space
Division</font>
<br><font size=2 color=#e01f25 face="Arial"><b>SCISYS UK Limited</b></font>
<br><font size=2 color=#2f2f2f face="Arial">T: +44 (0)117 916 5127 | F:
+44 (0)117 916 5299</font>
<br><font size=2 color=#2f2f2f face="Arial">E: sam.cooper@scisys.co.uk
| </font><a href=www.scisys.co.uk><font size=2 color=#2f2f2f face="Arial">www.scisys.co.uk</font></a>
<br><font size=2 face="Calibri"> </font>
<p><a href=gfidisc.scisys.co.uk></a>
<p><font size=2 color=blue face="Tahoma"> </font>
<p><font size=2 color=#808080 face="Arial">SCISYS UK Limited. Registered
in England and Wales No. 4373530.</font>
<br><font size=2 color=#808080 face="Arial">Registered Office: Methuen
Park, Chippenham, Wiltshire SN14 0GB, UK.</font>
<br><font size=3> </font>
<br><font size=1 color=#008000 face="Arial">Before printing, please think
about the environment.</font>
<p><a href=gfidisc.scisys.co.uk></a><tt><font size=2>_______________________________________________<br>
Moims-sc mailing list<br>
Moims-sc@mailman.ccsds.org<br>
</font></tt><a href="http://mailman.ccsds.org/mailman/listinfo/moims-sc"><tt><font size=2>http://mailman.ccsds.org/mailman/listinfo/moims-sc</font></tt></a><tt><font size=2><br>
</font></tt>
<p><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>