Re: [riot-devel] Upcoming ETSI Plugtests

as well: * October 30 - November 1, 2015 - 6tisch in Yokohama co-located with IETF 94 (note that the dates for the second 6lo/6tisch plugtests are tentative, but the first ones have been announced and will happen) Lot's of fun coding ahead :-) Thomas On Tue, Mar 24, 2015 at 5:11 PM, Oleg Hahm

[riot-devel] Upcoming ETSI Plugtests

Dear reading IOTlers, the next upcoming Plugtests organized by ETSI which are of interest for RIOT are announced as follows: * July 17-19, 2015 - 6tisch in Prague co-located with IETF 93 * October 30 - November 1, 2015 - 6lo in Yokohama co-located with IETF 94 * March 2016

Re: [riot-devel] Riot Software Update

Hi, Yes, I think (and wrote in a separate mail in this thread already): working groups for different distribution implementations should be created by people who are interested in those. If it helps preventing confusion I'm happy with renaming the first iteration to whatever you suggest, or "OT

[riot-devel] IEEE 802.15.4 addressing

Hi, now that we start to get in IEEE 802.15.4/6LoWPAN territory with netdev/netapi [1-3] I wonder if it makes sense to not have 2 (16-bit/64-bit) but 3 addressing modes: * 16-bit short address * 32-bit (16-bit PAN ID + 16-bit short address) as originally introduced to RIOT, but somehow ignored ove

Re: [riot-devel] Riot Software Update

Hi Ludwig! > yes, we agreed that in order to get software updates we need a foundation > for activating new firmware images first. > The working assumption for the first incarnation/iteration of this is that > an image has been saved to some memory of the device already. Okay, basically my questi

Re: [riot-devel] Removing thirdparty repositories

Hey guys,   I agree with Hauke on the LPM pull request from the thirdparty-repo. It is an interesting approach but the PR is based on ST's standard library and therefore would need to be completely rewritten.   I think RIOT is currently missing an implementation for the RTC periph low-level dr

Re: [riot-devel] Riot Software Update

Hi, yes, we agreed that in order to get software updates we need a foundation for activating new firmware images first. The working assumption for the first incarnation/iteration of this is that an image has been saved to some memory of the device already. Cheers, Ludwig Oleg Hahm schrieb: > Hi!

Re: [riot-devel] Riot Software Update

Hi! > I see the upgrade distribution process as mostly independent from the > software infrastructure needed to activate new images. Do I get this right, that the OTA task force is excluding the OTA part of the software update from their work? Or are you just considering the single hop case? Che

Re: [riot-devel] Riot Software Update

Hi, I see the upgrade distribution process as mostly independent from the software infrastructure needed to activate new images. Also, there are probably several ways to do this right (depending on the requirements, environment, ...), so there will be no single best distribution model. In this sen

[riot-devel] Updated Invitation: Biweekly virtual meeting @ Wed Mar 25, 2015 2pm - 3pm (RIOT Events)

BEGIN:VCALENDAR PRODID:-//Google Inc//Google Calendar 70.9054//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:REQUEST X-GOOGLE-CALID:k3ql8setv7l48ofnol0tfuu...@group.calendar.google.com BEGIN:VTIMEZONE TZID:Europe/Berlin X-LIC-LOCATION:Europe/Berlin BEGIN:DAYLIGHT TZOFFSETFROM:+0100 TZOFFSETTO:+0200 TZNA

Re: [riot-devel] Riot Software Update

Hello, Indeed, that presentation was rather interesting. and secure updates indeed as part of security; Looking at the OTA, the discussions are "excluding network protocol", so maybe one step in that direction would be to have some secure protocol for sending them ? Is there something alrea

Re: [riot-devel] Riot Software Update

Hi Thomas, there are some initial efforts on-going in the community, such as [1] [2] [3], and upcoming GSOC projects on implementing LWM2M amd dynamic linking. However, this is not sufficient to get the whole nine yards. To have the full picture, there lacks security/crypto aspects, software upda

[riot-devel] Riot Software Update

Hi, yesterday in the IAB technical plenary, Hannes Tschofening stressed the need for system software maintenance. This raises the question: Have we spent enough thoughts on automated secure software updates for RIOT, are we approaching this subject? It might be some thing worth while conside

Re: [riot-devel] Notification: Biweekly virtual meeting @ Every 2 weeks from 10am to 11am on Wednesday (RIOT Events)

Hi Peter! > just to avoid confusion: Didn't we agree to have the meeting tomorrow at 2pm > CET? Thanks for asking: Yes, we did, but I think no one cared to update the calendar. PlaceCam will be on at 2pm CET! Cheers, Oleg -- I'm working on a bittorrent joke, but I only have about 30% and nobody

Re: [riot-devel] Notification: Biweekly virtual meeting @ Every 2 weeks from 10am to 11am on Wednesday (RIOT Events)

Hi all, just to avoid confusion: Didn't we agree to have the meeting tomorrow at 2pm CET? Best, Peter Am 24.03.2015 um 09:59 schrieb Google Calendar: more details »

Re: [riot-devel] OTA meetup 11.2.2015

Hi, I'm not familiar with the LWM2M specifications, but the everything that has to do with mechanisms for upgrade availability detection, downloading etc have been excluded so far. It is excluded precisely because there are way too many right ways to do this. We agreed that we need to build an inf