https://openconnectivity.org/specs/OCF_Security_Specification_v1.3.1.pdf recommends (SHOULD) using a “temporary, non-repeated” piid value on RESET. But, as you said, that kind of change can break useful scenarios for some Device owners. That’s the reason why the spec uses SHOULD here, rather than SHALL.
The access mode to the piid property is Read-Only, so its value won’t change after RESET. BTW, I see that in this version of the spec we didn’t fix yet all the instances where piid is mentioned as a property of /oic/p. It is a property of /oic/d. Dan From: Andreas Zisowsky <[email protected]> Sent: Tuesday, April 3, 2018 1:05 AM To: Daniel Mihai (WINDOWS) <[email protected]>; [email protected] Subject: RE: [dev] difference between "Platform ID" and "PIID" ? Hi, just for clarification: If this ID is protocol agnostic, then it does not change when the device is onboarded or reset? Or does it change then for all protocols? I just wonder what happens, if someone already uses the printer (coming back to this example) via another protocol and then the PIID changes due to onboarding it. Thanks, Andreas — Andreas Zisowsky Senior Software Engineer, Lynx Technology T +49 30 91 51 36 58 [email protected]<mailto:[email protected]> [cid:15B0CE3E-F4E3-4ED9-B5FA-33C68AE9CA98] follow us Linkedin<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.linkedin.com%2Fcompany%2Flynx-technology-llc&data=02%7C01%7CDaniel.Mihai%40microsoft.com%7C855cb574c5d6497431ea08d59939a85e%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636583395276290256&sdata=jRNY%2BPqxL0SzSJPl5MwYP%2F8nursx0YByzLgOaCQACco%3D&reserved=0> | Twitter<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftwitter.com%2FLynxTechLLC&data=02%7C01%7CDaniel.Mihai%40microsoft.com%7C855cb574c5d6497431ea08d59939a85e%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636583395276290256&sdata=ZsCviXGalghINLF9SOKsgWALJ52KFWD0%2BliCs8J8E7I%3D&reserved=0> | Google+<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplus.google.com%2Fb%2F109652098423390642252%2F109652098423390642252%2Fabout&data=02%7C01%7CDaniel.Mihai%40microsoft.com%7C855cb574c5d6497431ea08d59939a85e%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636583395276290256&sdata=Vd2AakCUsKTsSI1oCfl%2F%2F7oMQYBcPXJkZmuXxLaNtq8%3D&reserved=0> J.M. Driver LLC From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> On Behalf Of Daniel Mihai (WINDOWS) via iotivity-dev Sent: Montag, 2. April 2018 21:04 To: Gregg Reynolds <[email protected]<mailto:[email protected]>> Cc: iotivity-dev <[email protected]<mailto:[email protected]>> Subject: Re: [dev] difference between "Platform ID" and "PIID" ? That sounds like a reasonable clarification to me. I believe the OCF Architecture Task Group would have to review that kind of proposal, if you guys want to bring a spec Change Request to them. Dan From: Gregg Reynolds <[email protected]<mailto:[email protected]>> Sent: Monday, April 2, 2018 12:00 PM To: Daniel Mihai (WINDOWS) <[email protected]<mailto:[email protected]>> Cc: Heldt-Sheller, Nathan <[email protected]<mailto:[email protected]>>; Nash, George <[email protected]<mailto:[email protected]>>; iotivity-dev <[email protected]<mailto:[email protected]>> Subject: Re: [dev] difference between "Platform ID" and "PIID" ? On Mon, Apr 2, 2018, 1:51 PM Daniel Mihai (WINDOWS) <[email protected]<mailto:[email protected]>> wrote: ... Nathan, I think your statement “PIID is the Protocol-agnostic ID that can be used by a Client to correlate multiple Platforms (OCF and non-OCF)” would be more clear if you used “correlate multiple Protocols”, instead of “correlate multiple Platforms”. Maybe "multiple application-layer protocols"?
_______________________________________________ iotivity-dev mailing list [email protected] https://lists.iotivity.org/mailman/listinfo/iotivity-dev
