Details
Description
It must be ensured that the MR_REGISTER and REGISTER_VENDOR_SPECIFIC_ATTRIBUTE services are properly decoupled. In no case should such a redundant setup trigger two CL3 indications for just one service request. However, this is unlikely to occur.
It does not make logical sense for the REGISTER_VENDOR_SPECIFIC_ATTRIBUTE service to successfully process an MR_REGISTERed object class when the mechanisms are redundant.
Check the decoupling and ensure there are no overlaps or conflicts between the two services. Additionally, the implementation should be updated to reflect the current documentation and forbid the REGISTER_VENDOR_SPECIFIC_ATTRIBUTE registration for MR-REGISTERED classes.