Hi Kamal,
Thank you very much for the detailed response, it gives me a lot of homework to do...
Regarding RFC8299, In the beginning RFC8299 was a very good candidate to model the service, since It describes the customer perspective (customer sites model), however breaking the customer perspective into resources/network perspective was not trivial, and requires many assumptions.
In the last year there was another IEFT initiative called L3NM (NM is network model) which is much more suitable to my need, since it usage the network perspective , as such include nodes, VRFs , routing protocols etc.
Assuming a provider's management system breaks RFC8299 into L3NM , my system need to accept the L3NM model and provision a service based on it.
The question is how to treat the nodes and EPs , as sub service or resources , and should the provider management system can edit the resources as independent entities (TMF639) or only via the service API (TMF640).
Thanks,
Erez
___________________________________________________________________________
This e-mail message is intended for the recipient only and contains information which is
CONFIDENTIAL and which may be proprietary to ECI Telecom. If you have received this
transmission in error, please inform us by e-mail, phone or fax, and then delete the original
and all copies thereof.
___________________________________________________________________________