D-Bus hierarchy for mctpd has transitioned from /xyz/openbmc_project/mctp to /au/com/codeconstruct/mctp1. The documentation notes that this was done to move to a dedicated namespace and add versioning via the 1 suffix.
Meaning of the "1" suffix:
Does the "1" in the object path specifically represent the MCTP specification version, or is it an internal versioning scheme for the mctpd implementation/API itself?
Future Changes: Is the versioning intended to reflect breaking changes in the D-Bus API? Under what circumstances would this suffix be incremented (e.g., mctp2)?
D-Bus hierarchy for mctpd has transitioned from /xyz/openbmc_project/mctp to /au/com/codeconstruct/mctp1. The documentation notes that this was done to move to a dedicated namespace and add versioning via the 1 suffix.
Meaning of the "1" suffix:
Does the "1" in the object path specifically represent the MCTP specification version, or is it an internal versioning scheme for the mctpd implementation/API itself?
Future Changes: Is the versioning intended to reflect breaking changes in the D-Bus API? Under what circumstances would this suffix be incremented (e.g., mctp2)?