In a architecture where there is a dedicated IoTivity Client whose design is closely in sync with the Non-OCF Bridge Server and the server is not intended to be part of any other OCF network, also both Client and Server runs on a same system.
In this case, implementing Provisioning and Security is necessary ? On Nov 27, 2017 1:09 PM, "Dwarkaprasad Dayama" <[email protected]> wrote: Assuming your server is going to be discovered in OCF network as well, YES it must support at least 1 OTM for being onboarded on OCF network. Regards Dwarka *---------------------------------------------------------------------------------------------* Samsung Research | R&D Strategy Team | Open Source Group *Open Connectivity Foundation (OCF) | Iotivity | Javascript Foundation (JSF)* *From:* [email protected] [mailto: [email protected]] *On Behalf Of *UDAY M.S *Sent:* Sunday, November 26, 2017 10:37 AM *To:* [email protected] *Subject:* [dev] Query : Is IoTivity Security Implementation required for IoTivity Server bridging to Non-OCF Devices Hi All, Section 7.3.1 of *OCF Security Specification VERSION 1.0.0 *mandates to implement at least one of the OTMs(owner transfer methods) in an OCF Device. For a server which is developed to bridge a Non-OCF protocol based device (WiFi, BLE, ZigBee) as per Section 5.6, Bridging to Non- OCF ecosystem of *OCF Core Specifiation VERSION 1.0.0 | June 2017 Part 1, *Is it mandatory to implement one of the OTM ? Thanks In Advance
_______________________________________________ iotivity-dev mailing list [email protected] https://lists.iotivity.org/mailman/listinfo/iotivity-dev
