<font size=2 face="sans-serif"><br>
<br>
---------------------------------------------------------------------------------------------------------<br>
Dr. Colin R. Haddow,<br>
HSO-GI, European Space Agency,<br>
European Space Operations Centre,<br>
Robert-Bosch-Str 5,<br>
64293 Darmstadt,<br>
Germany.<br>
<br>
Phone; +49 6151 90 2896<br>
Fax; +49 6151 90 3010<br>
E-Mail; colin.haddow@esa.int<br>
---------------------------------------------------------------------------------------------------------<br>
</font>
<br><font size=1 color=#800080 face="sans-serif">----- Forwarded by Colin
Haddow/esoc/ESA on 17/01/2017 18:09 -----</font>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">Martin Unal/esoc/ESA</font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">Colin Haddow/esoc/ESA@ESA</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">22/12/2016 16:45</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">CCSDS service
catalog review</font>
<br>
<hr noshade>
<br>
<br><font size=2 face="sans-serif">Hello</font>
<br>
<br><font size=2 face="sans-serif">The version I reviewed:<br>
<br>
</font>
<br><font size=2 face="sans-serif">1) SANA registry idea is good. </font>
<br><font size=2 face="sans-serif">I have done a quick check, most of the
registry entry are useless, empty or outdated.</font>
<br>
<br><font size=2 face="sans-serif">2) The "constraints" definition
looks strange to me.</font>
<br><font size=2 face="sans-serif">e.g : Is the cltu service not availble
to Ka or Optical link ?</font>
<br><font size=2 face="sans-serif">If this is coming from the cltu definition,
a reference to the CCSDS document defining the cltu standard may be more
adequate.</font>
<br><font size=2 face="sans-serif">This comment applies to all service
"contraint" paragraph in the Chapter 3.</font>
<br>
<br><font size=2 face="sans-serif">This document shall only list what needs
to be in an Agency Service Catalog, (Or I missed the purpose of the this
document)</font>
<br>
<br><font size=2 face="sans-serif">3) </font><font size=3 face="Times New Roman">5.2
<b>SCCS SERVICE COMMITMENT PROCESS</b></font>
<br><font size=2 face="sans-serif">It looks a bit dangerous to mention
commitment process in a standard.</font>
<br><font size=2 face="sans-serif">This may vary a lot depending of each
User/Provider relation and needs.</font>
<br><font size=2 face="sans-serif">A standard should only define process
and terminology to be used if one party wants or needs to commit.</font>
<br>
<br><font size=2 face="sans-serif"><b>Overall</b>) the scope is not clear
to me. What is the intention of this document ?</font>
<br><font size=2 face="sans-serif">- As a standard, I beleive it should
only provides rule and terminology to build a "provider specific"
service catalog. </font>
<br><font size=2 face="sans-serif">In the way it is written, it seems to
impose a list of service to be implemented by a certain date. It looks
more like a "project plan" to me.</font>
<br>
<br><font size=2 face="sans-serif">- What is RD.1 ?</font>
<br>
<br><font size=2 face="sans-serif">- Is this a commitment for ESTRACK implementation
? => </font><font size=3 color=#800000 face="Times New Roman"><i>The
core services are to be implemented by all IOAG agencies by 2020</i></font>
<br>
<br>
<br><font size=2 face="sans-serif">For reference:</font>
<p><font size=3 color=#800000 face="Times New Roman"><i>1.2
<b>Scope </i></b></font>
<div><font size=3 color=#800000 face="Times New Roman"><i>The document
is based on the list of services contained in Service Catalog #1 (SC#1,
RD.1), produced by the Interagency Operations Advisory Group (IOAG). IOAG
describes its services as “core” or “extended”. </i></font><font size=3 color=red face="Times New Roman"><b><i>The
core services are to be implemented by all IOAG agencies by 2020, while
the extended services are to be considered for bilateral cross support.</i></b></font>
<p><font size=3 color=#800000 face="Times New Roman"><i>The Recommended
Practice provides a summary of the services and parameters that need to
be included in an Agency's Service Catalog in order that it may support
the planning and implementation of SCCS services based on those listed
in SC#1. </i></font>
<br><font size=2 face="sans-serif"><br>
Regards<br>
________________________________________<br>
Martin UNAL<br>
Ground Operation Manager<br>
Ground Facilities Ops HSO - ONO<br>
H-376<br>
ESOC<br>
Robert-Bosch Strasse 5<br>
64 293 Darmstadt<br>
Germany<br>
Tel +49 6151 90 2959 Fax +49 6151 90 3190<br>
________________________________________</font>
<br></div><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>