WE HAVE TO THINK what added value will this file gives to OpenNCP, and if it solves any existing problem
What kind of file has each PN to prepare in order to register its services (something like tsl?)
Will it be a replacement for TSL? If yes, we have to assume for replacement of tsleditor and tslsync
Is service locator aware of the status of the service (up-down)?
Service locator shall also have information about test systems?
Is it meant only for the purpose of providing information about the location of the capability services?
As a central service, which can be used/requested by the senders, e.g. accessing by OpenNCP
Problem: what about the technical network connections and configurations necessary, e.g. firewall restrictions. For example currently you can download the TSL file from the configuration service, the local OpenNCP database is updated with the endpoint information, the certificates are installed in the truststore, but to be able to connect successfully, the firewall rules of the receiving site must allow access from the caller´s side, the VPN connection must be configured properly, ...
As a component of OpenNCP ? Not in my opinion, central service, but OpenNCP may register there at startup
As a central service, which can be used/requested by the senders, e.g. accessing by OpenNCP

Action Items:

Versions Compared