Hi Hermant, For your question, Let me deduce the Easy Setup requirement step by step. IoTivity current Easy Setup component(SDK) already covers the OnBroading/Network Provisioning (Wi-Fi credential). If we look into detail the Network Provisioning, we can find out this will be done thru OIC POST request. Furthermore, Each resource request should be done after ACL defined from the OIC security point of view. Them, Ownership Transfer (ACL) should be streamlined in the middle between OnBroading and Network Provisioning (Wi-Fi credential) step. so that, I think Easy Setup should include the Onwership transfer step thru one set of high level API.
Anyway, Could you share your one set APIs as concept level? BR, Uze Choi From: HEMANT MAHSKY [mailto:[email protected]] Sent: Tuesday, January 05, 2016 7:11 PM To: Uze Choi; lanka.madan at samsung.com Cc: Ganesh Kumar T; ashok.channa at samsung.com; iotivity- dev at lists.iotivity.org Subject: Integration with security APIs [ Multi PHY Easy Setup ] Hi, We are integrating ownership transfer feature into Multi PHY Easy setup service (OBT). This feature ensures Device needs to be owned by network before going through network provisioning. Though the device will able to connect with home network after network provisioning, but it will not be accessible by other device nor it can access other devices/resource. Some one needs to set the ACL & do credential provisioning & pairing with other devices ( as per current security implementation). The term 'set-up' will not be over until user is not able to access the device and it is up & fully functional with other devices in the network. Multi PHY Easy set-up is having an SDK, where a device being enrolled into the network is represented by "Enrollee". The "Enrollee" goes through various states during the set-up i.e. On-boarding, ownership transfer, network provisioned etc. It is a very natural flow that "Enrollee" should go for ACL & Credential provisioning after joining the network. Multi PHY Easy Setup provides easy to use high level APIs for developers. It will be a cumbersome job for developer to destroy the "Enrollee" instance after device joined the network & start a fresh new flow for ACL, Credentials provisioning etc. with entirely different set of APIS. So shouldn't Multi PHY Easy setup incorporate ACL, credential provisioning etc. into it's scope so that overall flow can be streamline from unboxing to get device operational through one set of high level APIs ? Regards, Hemant -------------- next part -------------- HTML ?????? ??????????????... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160106/a5b23842/attachment.html>
