Hi Ravee, Nice to see you reading the Specification so carefully!
This language is a bit vague, I agree… the OBT is literally free to select whatever value it wants to, including the value already installed on the Device. In some cases, the Device Mfr may provision a /doxm.deviceuuid that is unique and usable for the Device’s lifetime, and Mfr-provided OBT would not change it. In other cases, the Device Mfr may provision a Nil UUID for the /doxm.deviceuuid, in which case the OBT would need to update. Other combinations are also allowed. Note that the IoTivity provisioningclient sample application is not meant to be a full-featured OBT, but rather a combination unit test and useful example for some aspects of device mgmt, so I wouldn’t be surprised if this feature is missing from it. Thanks, Nathan From: iotivity-dev-boun...@lists.iotivity.org [mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of Raveendranath Kondrakunta Sent: Thursday, March 1, 2018 1:17 AM To: iotivity-dev@lists.iotivity.org Subject: [dev] New Device UUID update by DOXS Hi, [Inline image 1] Looks, the current implementation of the stack is not doing this. DOXS is only updating the /doxm.devowneruui and /doxm.rowneruuid. But, as per spec, it is supposed to update the /doxm.deviceuuid as well, correct? -Ravee
_______________________________________________ iotivity-dev mailing list iotivity-dev@lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev
