Behavior of TAPI Client configured attributes to be clarified

[kgkishore]

Definitions of TAPI RIA indicates that certain Mandatory TAPI Client configured attributes configured by a TAPI Client user in the intent of of connectivity service provisioning are retrievable, as attributes are R/W.

TAPI RIA definition need to clarify the behavior of such TAPI Client configured attributes upon connectivity service,CSEPs etc upon the changes in those attributes that are triggered from TAPI Server how these need to be notified , whether TAPI Client configured attributes need to be preserved or need to update with the TAPI client configured attributes upon connectivity service,cseps based on changes triggered from the TAPI servers.

Need clarity whether updated changes to be notified on connections or connectivity services

[nigel-r-davis]

Some properties in connectity service must not be changed, others can be changed, others may not be set initially but once set, they become intent.

Any changes in the connectivity service must be streamed or notified.

[bcjohnso99]

1. Intent should remain according to the desire of the primary controller.
2. Changes detected in the network should be notified against the connection. The controller decides the severity of any conflicts and determines if any corrective action is required. The role of the receiving controller (primary vs backup) should be considered in the determination of corrective action.
3. In the case of hierarchical controllers, if a change to intent is made by the lower controller, then the change should be notified against the connectivity service.
4. TAPI controller redundancy capability would be required to journal intent changes from the primary controller to backup controller(s)