BMCA algorithm cannot be disabled

[niloda]

Some implementations allow the Best Master Clock Algorithm (BMCA) to be disabled; however, the current model does not include an explicit attribute to support this behavior.

It is therefore proposed to introduce at least one attribute within the ptp-sync-pac container—for example, bmca-is-on—to enable or disable the execution of BMCA.

Additionally, a capability attribute—e.g., disabling-bmca-is-avail—can be defined to indicate whether a given implementation supports disabling BMCA.

When BMCA is disabled, the role of each PTP port must be configured statically. To support this configuration, it is also proposed to add a new parameter in the ptp-lp-spec grouping, for example ptp-static-port-role, which may assume one of the following values:

• MASTER
• SLAVE
• PASSIVE

[openBackhaul]

Decision during the LF ONMI x-haul meeting on 19th of November 2025:

The following changes to be made to the Synchronization modelling:

• adding a read-only PtpSync_Pac::disablingBmcaIsAvail: Boolean = false attribute with comment "true = the device supports deactivating the Best Master Clock Algorithm (BMCA)."
• adding a read/write PtpSync_Pac::bmcaIsOn: Boolean = true attribute with comment "true = the Best Master Clock Algorithm (BMCA) is activated and is automatically configuring the role of the PTP ports."
• creating a PtpPortConfig enumeration with the following values:
  • MASTER
  • SLAVE
  • PASSIVE
  • NOT_YET_DEFINED
• adding a read/write Ptp_Pac::ptpStaticPortRole: PtpPortConfig = NOT_YET_DEFINED attribute with comment "Allows to manually configure the role of the PTP port, when the Best Master Clock Algorithm (BMCA) is deactivated."