Hi Minho The UUID -- if it will exist -- will be part of the security / onboarding solution. Since we haven't implemented that yet, it's hard to say even whether an UUID will exist.
I've been pushing for a discussion on this topic on whether we can get away from even having a UUID. For example, it could be the checksum of the client's certificate, which it will have to generate at onboarding time. But despite the method, we *need* a globally unique identifier that allows you to track a client if its IP address changed or if you reached it over a different medium. On Thursday 23 April 2015 08:56:03 ??? wrote: > Hi, > > I have a question regarding uniqueness of things in IoTivity. > > Are there any mechanisms to generate UUID for a specific device exist in > IoTivity? when I assume that a particular service exist and this service > uses IoTivity, can I guarantee a specific thing is globally unique so that > any other things can't use same UUID? Also as client of this service can I > recognize this thing after this thing rebooted and IP/Port # is changed? > I heard currently there are no mechanisms regarding this defined in OIC > standard track so nobody can guarantee global uniqueness of things in OIC > now. > What is IoTivity's situation regarding this or any plan exist? > > Thank you > > Regards, > Andy Minho Lee > > > > > > -------- > Lee Min Ho > Principal Engineer > > IoT Solution Lab. > Web & Convergence Team > Software Center > SAMSUNG ELECTRONICS CO.,LTD > > TEL . 82-31-279-7888 > FAX . 82-31-279-0523 > Mobile . 82-10-6228-8340 > E-Mail . minho03.lee at samsung.com > > > > -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
