Hi Rajesh
This is a delicate issue. On the one hand, if the API conformance defines attributes as optional, it means that a consumer expecting to meet a conforming implementation will "know" that it doesn't need to send those attributes. And then when it encounters your implementation with these attributes as mandatory it will fail.
On the other hand, vendors and other API implementers may want the freedom to define additional mandatory attributes for the proper functioning of their business.
It's best taken up with the CTK focal
@Henrique Rodrigues, who can hopefully explain how to adjust the CTK to support additional mandatory attributes and yet still achieve a positive conformance result.
Hope it helps
------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
------------------------------