Hi Kishen I am not proposing using MQTT as OCF transport. Just as you mentioned below
> However, I assume your comments were coming more from an open-source > tool perspective, in that establishing OCF<->MQTT interop in IoTivity might > enable developers to more easily prototype IoT applications. > If so, I would agree, and that alone should be doable. Need to have the following enabled: 1) MQTT client connects to MQTT broker and publishes some topics to it. MQTT broker/GW creates OCF resources corresponding to the topics and handles OCF clients access to the resources corresponding to the topics. 2) OCF resources access an MQTT G/W that acts as a MQTT client that publishes the OCF resources as topics to a MQTT broker. The OCF resources keep pushing their data to the MQTT G/W which publishes the updates to the MQTT broker. I should start by 1 as 2 is straightforward. Best regards, Khaled On Tue, Aug 21, 2018 at 7:47 PM, Maloor, Kishen <[email protected]> wrote: > Hi Khaled, > > > > MQTT is not formally adopted by the OCF specifications. > > While there is general interest to add PubSub capabilities to the > > OCF protocol in the medium term, it isn't something > > to expect imminently. Even so, that solution may or may not involve > > MQTT. > > > > There are other and related proposals that might facilitate > > using MQTT as a transport and within the confines of OCF's existing > > security model. I am involved with one such proposal within OCF > > on the standards front. The goal there of course is to bring it into OCF > > certified products so all the corner cases need to be fully fleshed out. > > > > However, I assume your comments were coming more from an open-source > > tool perspective, in that establishing OCF<->MQTT interop in IoTivity might > > enable developers to more easily prototype IoT applications. > > If so, I would agree, and that alone should be doable. > > > > As you might be aware, I lead and maintain the IoTivity-Constrained > > (nowadays called IoTivity-Lite) project, so if you'd like to work > > on (or have people contribute to) an MQTT binding, I'd be willing to > > review and accept those contributions. If you'd like to propose an > > architecture for this with IoTivity-Lite, you may share it with > > me. (https://github.com/iotivity/iotivity-constrained -- I recollect that > > you've previously submitted a patch) > > > > I am very interested in your thoughts and insights on possible > > use case scenarios (or other architectural benefits) that an > > OCF<->MQTT binding might enable. That could contribute to discussions > > I routinely engage in on the OCF standards side. > > > > Thanks, > > -Kishen. > > > > > > > > -- > > Kishen Maloor > > Intel Open Source Technology Center > > > > *From: *<[email protected]> on behalf of Khaled Elsayed < > [email protected]> > *Reply-To: *"[email protected]" <[email protected]> > *Date: *Monday, August 20, 2018 at 4:28 AM > *To: *iotivity-dev <[email protected]> > *Subject: *[dev] MQTT G/W > > > > 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? > > > > Best regards, > > > > Khaled > > > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#9891): https://lists.iotivity.org/g/iotivity-dev/message/9891 Mute This Topic: https://lists.iotivity.org/mt/24817907/21656 Group Owner: [email protected] Unsubscribe: https://lists.iotivity.org/g/iotivity-dev/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
