M&C: Support for Configurations

[CesarCoelho]

Necessary changes:
1.
Add the following requirement to all the services in the High Level Requirements sections:
"The service should be reconfigurable by to the provider. For this, the service needs to provide to the provider: reload of configurations; retrieval of the current configuration; notification of a configuration change."
(it's a should requirement once again)

Add the following requirement to all the operations that change the configuration of a certain service.
"The service should notify the provider of a configuration change if no error is raised."
(it's a should requirement)

A good way to find which services need this additional requirement is to check the Service Operations table and check the "Support in Replay" field. If no, most likely the operation needs to have the requirement to notify that the configuration has been changed.

---

Please notice that to make the M&C services "reconfigurable" is is not necessary to have the Configuration service. All we need is to allow the provider to reload configurations, get the current and receive notifications of changes from the services.
Additionally, I would suggest to move some of the data structures of the configuration service (the ones necessary to hold a configuration of a certain service/provider) to the MAL book (2013 was the release, so in the next 2018 iteration we could add it). This would remove the dependency to the Common API from the implementation of the services.
Suggested here: SamCooper/MAL_SPEC_RIDS#5

[SamCooper]

I'm not sure about this as it seems to be more about implementation than service specification.

[CesarCoelho]

WG review:

Support for configuration should not be explicit added/mentioned in this specification.
However, the WG acknowledges Cesar right to come back in two years time and say "I told you so!" when we need this.