[NMOP] SIMAP Issue 113: Sergio Belotti - Service->Resource

[Olga Havel <[e-mail]>]

Hi Sergio,

Your comment in regards to Section 3.1.1 is as follows:

The text is a bit confused. . In this text seems as though the SIMAP is a set of APIs related to various services, while in other previous part of the text I was supposing SIMAP is a data model for topology.
The basic concept I can understand here is that SIMAP should be able to have enough information to permit an application to retrieve , as written " the topology for selected services".
The rest of the text would need to be simplified and maybe is not needed.


We clarified already relation between API and Model and as Benoit suggested, the client application access the model via APIs so the use cases can still use API term. We added the SIMAP API, SIMAP client application and SIMAP server definitions for clarification. We also addressed the issue 125  https://github.com/ietf-wg-nmop/draft-ietf-nmop-digital-map-concept/issues/125 based on Chongfeng comment to clarify the motivation and added some text that Christopher Janz suggested.

The current section is as follows, please let me know if anything is still confusiong. I propose to close the Issue 113.

Service -> Resource
The SIMAP APIs can be invoked to retrieve all Services for selected service types. A SIMAP client application that triggers such a request will be able to retrieve the topology for selected Services via the SIMAP APIs and, from the response, it will be able to navigate top-down to the lower layers via the supporting relationship provided by the SIMAP server. In doing so, the SIMAP client application will be able to determine what logical resources are used by a Service. The supporting relations to the lowest layer, provided by the SIMAP server, will help the SIMAP client application to determine what physical resources are used by the Service. This addresses a requirement for systems to be able to provide topology and resource views of services, at different levels of abstraction, using the SIMAP [REF: ETSI ZSM 019 Clause 6]. Knowing the physical resources a service uses enables capacity planning, fault isolation, performance monitoring, and accurate billing.


Best Regards,
Olga