Hi, Kishen. It's clear for me now. Thanks for your kind reply.
All the best. 2019년 11월 7일 (목) 오전 9:43, Maloor, Kishen <kishen.mal...@intel.com>님이 작성: > Hi, > > > > > I have one more question. > > > oc_reset() changes the client's UUID. > > > Is it intended? > > > > In the current specifications, OBTs must configure a "deviceuuid" each > time the device is > > onboarded. So, expect a device's UUID to change. After a device is RESET, > its UUID could > > be anything (even zeroed out). Any OBT/applicaton/device should not rely > on "deviceuuid" > > consistency. > > > > > In my opinion, reset to RFOTM means change status for OTM but UUID. > > > If UUID is changed, obt or server will think that it's a different > device. > > > > Fyi, the specfications currently recommend using /oid/d.piid to return a > fixed and unchanging UUID that > > survives power and RESET cycles. IoTvity-Lite supports this model. > Applications have an API > > (oc_set_immutable_device_identifier()) to configure one (look in > apps/smart_home_server_linux), and if apps > > don't, a UUID is randomly chosen the first time the device starts up and > sticks. As such, any Client (OBT or > > otherwise) can rely on this UUID being consistent. > > > > > In my case, after oc_reset() or deleting creds directory, I must go back > to the first step "Select IUT" and > > > I selected a device of new UUID. > > > To pass Confermance test shall be run three times. > > > > With the CTT, you'd RESET the IUT whenever it asks you. When the CTT tries > to re-discover a device following > > a RESET, it knows to not rely on "deviceuuid". Rather I believe it uses > some heuristic to pick the > > right device for further tests. > > > > Thanks, > > -Kishen. > > > > -- > > Kishen Maloor > > Intel Corporation > > > > *From: *<iotivity-dev@lists.iotivity.org> on behalf of 김정진 < > j....@vinetech.com> > *Date: *Wednesday, November 6, 2019 at 1:11 AM > *To: *"iotivity-dev@lists.iotivity.org" <iotivity-dev@lists.iotivity.org> > *Subject: *Re: [dev] Question About CT2.2.6 on CTT1903.0.00 and How to > reeset client OTM? > > > > Hi, Kishen. > > I can pass the CT2.2.6 due to your advice. > I'm appreciated for you so much. > > I have one more question. > oc_reset() changes the client's UUID. > Is it intended? > > In my opinion, reset to RFOTM means change status for OTM but UUID. > If UUID is changed, obt or server will think that it's a different device. > > In my case, after oc_reset() or deleting creds directory, I must go back > to the first step "Select IUT" and I selected a device of new UUID. > To pass Confermance test shall be run three times. > > Best regards. > Kim. > > > -- 김정진 책임연구원 (Jeongjin Kim) Mobile. 010-4223-8152 j....@vinetech.com ㈜바인테크 Vinetech Co., Ltd. | IoT Platform Lab | New Technology BU (신기술사업부) Dir Tel: 82-2-2182-8392 | Tel: 82-2-2182-8300 | Fax: 82-2-2182-8399 (05836) 서울시 송파구 법원로11길 7, C동 1207호 (문정동, 현대지식산업센터) #1207~1210, 7, Beobwon-ro 11-gil, Songpa-gu, Seoul, 05836, Rep. of KOREA -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#10284): https://lists.iotivity.org/g/iotivity-dev/message/10284 Mute This Topic: https://lists.iotivity.org/mt/42101102/21656 Group Owner: iotivity-dev+ow...@lists.iotivity.org Unsubscribe: https://lists.iotivity.org/g/iotivity-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
