Dear IoTivity team I have a couple of questions I hope you can help me clarifying:
1. According to the OCI transport specification, BLE is supposed to use 6loPAN, but the current implementation (head of iotivity git branch) seems to use a "proprietary" specification implemented on top of GATT (In code comments referred to as the OIC GATT profile - I have not been able to find a description of this profile anywhere). We are interested in knowing what will be the final protocol to implement for a BLE device. Could you please let us know what to support? - and if it is the OIC GATT profile, a link to a profile description would be much appreciated, as reverse engineering the current implementation will most likely be error prone and not be able to handle every aspect of the specification. 2. As the current BLE implementation only supports point-to-point Bluetooth connections, have you considered using BLE Mesh as transport layer for IoTivity. This would allow a large network of BLE devices to be connected without the need for a route manager and a complex setup of connections. Additionally the network would be less sensitive to device replacements. Imagine a light bulb which function as gateway for some BLE sensor(s) or as a range extender needs to be replaced. With the current connection based BLE implementation, the user would need not only to on-board the new light bulb, but also "re-on-board" all the devices which the light bulb had connections to. With BLE mesh this could be avoided, as mesh repeaters/relays will merely forward all received messages. Thanks, Allan -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160616/8ff3162e/attachment.html>
