This is of course need to be investigated. For a start I think of having the MQTT broker handle all OCF security as currently implemented in iotivity code. For MQTT part, I am not an expert, so I can start assuming the client just publish without constraints.
On Mon, Aug 20, 2018 at 10:52 PM, Mats Wichmann <m...@wichmann.us> wrote: > On 08/20/2018 05:28 AM, Khaled Elsayed wrote: > > Hi, > > > > Has anyone developed a MQTT gateway that would host a MQTT broker > receiving > > the MQTT publish requests and creates OCF resources corresponding to the > > MQTT topics and handles the update of the resources data. It should not > be > > that difficult so I am asking it is already there to avoid doing it > again. > > > > If it does not exist, would it be interesting for the IoTivity community > to > > have OCF/iotivity and MQTT inter-operability? > > There is a desire for pub/sub functionality in OCF, last I knew. At the > very least for a backchannel comms method so a device can send an > unsolicted message - like for an emergency. > > It seems like it might be a little tricky to craft with the security > model, however. I'm thinking of how to do access control when there are > three parties to a conversation, and the producer and consumer don't > necessarily know each other. The broker might have to handle this so > there's a negotiation before someone can subscribe to a particular > server's messages. > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#9888): https://lists.iotivity.org/g/iotivity-dev/message/9888 Mute This Topic: https://lists.iotivity.org/mt/24817907/21656 Group Owner: iotivity-dev+ow...@lists.iotivity.org Unsubscribe: https://lists.iotivity.org/g/iotivity-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
