Re: [riot-devel] Iotivity, AllJoyn, Thread, Ipso Alliance
Hi! At least for IoTivity it should be fairly simple to port it to RIOT according to the response I got on their mailing list: http://lists.iotivity.org/pipermail/iotivity-dev/2015-March/000600.html The only problem I see is the incompatible license of their implementation. (Btw. the Contiki port seems to be more or less vaporware according to http://lists.iotivity.org/pipermail/iotivity-dev/2015-March/000606.html). Cheers, Oleg -- if (user_specified) /* Didn't work, but the user is convinced this is the * place. */ linux-2.4.0-test2/drivers/parport/parport_pc.c pgpYfYZcXTzql.pgp Description: PGP signature ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] Iotivity, AllJoyn, Thread, Ipso Alliance
Hi! I just realized that I'll probably learn something about IoTivity and AllJoyn today at the T2TRG meeting: https://github.com/t2trg/2015-ietf92/blob/master/agenda.md I guess there won't be now audio stream, but at least the slides should be online later this day. Concerning IoTBase, I would add that they're thinking about a stack for constrained devices [1] so it might be easier to implement on RIOT. Looks indeed interesting at a first glance. We should have an eye on this and see if someone's willing to give it a try with RIOT. As you said, Riot nodes will be connected to something more powerful but this kind of protocol avoids to create new proprietary protocols. Just for clarification: I (and I guess I'm speaking for most of us) want a (R)IOT device being able to be connected _directly_ to anything. Be it another RIOT powered device, a Contiki device, my home gateway, my smartphone, or any server in the Internet. Protocols for the IoT should not rely on the fact that there is something more powerful that translates their messages to the rest of the world. I found this link on stackoverflow where they compare AllJoyn and IoTivity.[2] Thanks for the pointer. Cheers, Oleg -- printk(Entering UltraSMPenguin Mode...\n); linux-2.2.16/arch/sparc64/kernel/smp.c pgptpor10Mxlt.pgp Description: PGP signature ___ devel mailing list devel@riot-os.org http://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] Iotivity, AllJoyn, Thread, Ipso Alliance
Oleg Hahm wrote: I (and I guess I'm speaking for most of us) want a (R)IOT device being able to be connected _directly_ to anything. Be it another RIOT powered device, a Contiki device, my home gateway, my smartphone, or any server in the Internet. That's why it's called Thing-to-thing research group! Protocols for the IoT should not rely on the fact that there is something more powerful that translates their messages to the rest of the world. There is nothing wrong with factoring in something more powerful for setup, human interface etc. But for doing their job, where thing-to-thing communication is the appropriate mode for that job, we should be able to do it. It's the Internet way... I'm also looking forward to the IoTivity and AllSeen talks today. Too bad we couldn't find someone from Thread to talk. Grüße, Carsten ___ devel mailing list devel@riot-os.org http://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] Iotivity, AllJoyn, Thread, Ipso Alliance
Hello Baptiste! 2015-03-20 9:02 GMT+01:00 Baptiste Clenet bapcle...@gmail.com: I agree with you about IETF protocols, everybody should use them and it will make communication easier. In my opinion IETF protocols have the most potential to become de facto standards. However IETF doesn't develop high level standards (above application level). They released CoAP, but they won't define structure of resources, and contents of messages. You may check OMA LWM2M [1] - it's heavilly based on IETF standards and compatible with IPSO. It's more suited for GSM devices though. Best Regards Maciej Wasilak [1] http://technical.openmobilealliance.org/Technical/technical-information/release-program/current-releases/oma-lightweightm2m-v1-0 ___ devel mailing list devel@riot-os.org http://lists.riot-os.org/mailman/listinfo/devel
[riot-devel] Iotivity, AllJoyn, Thread, Ipso Alliance
Hi Rioters, This question is not particularly about Riot but it makes sense to ask you since future Riot device might use one of this high level protocol (Iotivity, AllJoyn, Thread, Ipso Alliance). What do you think about them? In your opinion, which one will be mostly used? Is there any future developments planned on RIOT? Cheers, -- *Clenet BaptisteFR: +33 6 29 73 05 39* ___ devel mailing list devel@riot-os.org http://lists.riot-os.org/mailman/listinfo/devel
