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

2015-03-24 Thread Oleg Hahm
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's
seeding!


pgp_fMF3eDL1o.pgp
Description: PGP signature
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel


[riot-devel] Upcoming ETSI Plugtests

2015-03-24 Thread Oleg Hahm
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- 6lo in Buenos Aires co-located with IETF 95

Cheers,
Oleg
-- 
/* We are root, all done! */
RIOT/sys/net/rpl/rpl.c


pgp0a1tccJ_qB.pgp
Description: PGP signature
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel


Re: [riot-devel] Upcoming ETSI Plugtests

2015-03-24 Thread Thomas Watteyne
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 oliver.h...@inria.fr wrote:

 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- 6lo in Buenos Aires co-located with IETF
 95

 Cheers,
 Oleg
 --
 /* We are root, all done! */
 RIOT/sys/net/rpl/rpl.c

 ___
 devel mailing list
 devel@riot-os.org
 https://lists.riot-os.org/mailman/listinfo/devel


___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel


[riot-devel] Riot Software Update

2015-03-24 Thread Thomas C. Schmidt

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 considering??

Cheers,
 Thomas
--

Prof. Dr. Thomas C. Schmidt
° Hamburg University of Applied Sciences   Berliner Tor 7 °
° Dept. Informatik, Internet Technologies Group20099 Hamburg, Germany °
° http://www.haw-hamburg.de/inet   Fon: +49-40-42875-8452 °
° http://www.informatik.haw-hamburg.de/~schmidtFax: +49-40-42875-8409 °

--

Prof. Dr. Thomas C. Schmidt
° Hamburg University of Applied Sciences   Berliner Tor 7 °
° Dept. Informatik, Internet Technologies Group20099 Hamburg, Germany °
° http://www.haw-hamburg.de/inet   Fon: +49-40-42875-8452 °
° http://www.informatik.haw-hamburg.de/~schmidtFax: +49-40-42875-8409 °
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel


Re: [riot-devel] Riot Software Update

2015-03-24 Thread Cédric Adjih
  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 already envisionned ?

best regards,
-- Cedric

- Original Message -
| From: Thomas C. Schmidt schm...@informatik.haw-hamburg.de
| To: RIOT OS kernel developers devel@riot-os.org
| Sent: Tuesday, March 24, 2015 10:01:01 AM
| Subject: [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 considering??
| 
| Cheers,
|   Thomas
| --
| 
| Prof. Dr. Thomas C. Schmidt
| ° Hamburg University of Applied Sciences   Berliner
| Tor 7 °
| ° Dept. Informatik, Internet Technologies Group20099 Hamburg,
| Germany °
| ° http://www.haw-hamburg.de/inet   Fon:
| +49-40-42875-8452 °
| ° http://www.informatik.haw-hamburg.de/~schmidtFax:
| +49-40-42875-8409 °
__
| devel mailing list
| devel@riot-os.org
| https://lists.riot-os.org/mailman/listinfo/devel
| 
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel


Re: [riot-devel] Riot Software Update

2015-03-24 Thread Ludwig Ortmann
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!

 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?

 Cheers,
 Oleg
 --
 My computer is so slow that sometimes it gets a timeout from
 http://localhost.
 ___
 devel mailing list
 devel@riot-os.org
 https://lists.riot-os.org/mailman/listinfo/devel



___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel


Re: [riot-devel] Riot Software Update

2015-03-24 Thread Emmanuel Baccelli
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 updates
(rrlated but different from firmware updates) and the automatic aspect,
which also include a network/transport/distribution aspect.

So in a nutshell: I think this aspect is of utmost importance indeed.
Having a really good way to do that could be a decisive advantage of RIOT
over other OS. In any case: the IoT will only become the IoT the day such
evolutive mechanisms are in place and usable.

I was thinking that this could/should be the main focus of RIOT in upcoming
H2020 project proposals for instance.

best,

Emmanuel

[1]
https://lists.riot-os.org/pipermail/devel/attachments/20150211/7e2772a3/attachment-0001.pdf
[2] https://github.com/RIOT-OS/RIOT/wiki/minutes-OTA-meetup-13.2.2015
[3] https://lists.stillroot.org/pipermail/devel/2015-January/001738.html
 Le 24 mars 2015 10:01, Thomas C. Schmidt 
schm...@informatik.haw-hamburg.de a écrit :

 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 considering??

 Cheers,
  Thomas
 --

 Prof. Dr. Thomas C. Schmidt
 ° Hamburg University of Applied Sciences   Berliner Tor 7 °
 ° Dept. Informatik, Internet Technologies Group20099 Hamburg, Germany °
 ° http://www.haw-hamburg.de/inet   Fon: +49-40-42875-8452
 °
 ° http://www.informatik.haw-hamburg.de/~schmidtFax: +49-40-42875-8409
 °

 --

 Prof. Dr. Thomas C. Schmidt
 ° Hamburg University of Applied Sciences   Berliner Tor 7 °
 ° Dept. Informatik, Internet Technologies Group20099 Hamburg, Germany °
 ° http://www.haw-hamburg.de/inet   Fon: +49-40-42875-8452
 °
 ° http://www.informatik.haw-hamburg.de/~schmidtFax: +49-40-42875-8409
 °
 ___
 devel mailing list
 devel@riot-os.org
 https://lists.riot-os.org/mailman/listinfo/devel

___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel


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

2015-03-24 Thread Martine Lenders
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
TZNAME:CEST
DTSTART:19700329T02
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=-1SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
TZNAME:CET
DTSTART:19701025T03
RRULE:FREQ=YEARLY;BYMONTH=10;BYDAY=-1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=Europe/Berlin:20150325T14
DTEND;TZID=Europe/Berlin:20150325T15
DTSTAMP:20150324T154427Z
UID:jpp1u2ivlued8qdtp50jsb1...@google.com
RECURRENCE-ID;TZID=Europe/Berlin:20150325T10
CREATED:20141212T130850Z
DESCRIPTION:Developer discussions. Remote participation will be provided.\n
 View your event at https://www.google.com/calendar/event?action=VIEWeid=an
 BwMXUyaXZsdWVkOHFkdHA1MGpzYjFzZ2tfMjAxNTAzMjVUMDkwMDAwWiBrM3FsOHNldHY3bDQ4b
 2Zub2wwdGZ1dTZ0c0Bn.
LAST-MODIFIED:20150324T154426Z
LOCATION:
SEQUENCE:1
STATUS:CONFIRMED
SUMMARY:Biweekly virtual meeting
TRANSP:OPAQUE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:This is an event reminder
TRIGGER:-P0DT12H0M0S
END:VALARM
END:VEVENT
END:VCALENDAR


invite.ics
Description: application/ics
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel


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

2015-03-24 Thread Peter Kietzmann

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 » 
https://www.google.com/calendar/event?action=VIEWeid=anBwMXUyaXZsdWVkOHFkdHA1MGpzYjFzZ2sgazNxbDhzZXR2N2w0OG9mbm9sMHRmdXU2dHNAZw



  Biweekly virtual meeting

Developer discussions. Remote participation will be provided.
/When/
Every 2 weeks from 10am to 11am on Wednesday Berlin
/Calendar/
RIOT Events
/Who/

•   
Ludwig Ortmann - creator

Invitation from Google Calendar https://www.google.com/calendar/

You are receiving this email at the account peterschme...@gmail.com 
because you are subscribed for notifications on calendar RIOT Events.


To stop receiving these emails, please log in to 
https://www.google.com/calendar/ and change your notification settings 
for this calendar.




___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel


--
Peter Kietzmann

Hamburg University of Applied Sciences
Dept. Informatik, Internet Technologies Group
Berliner Tor 7, 20099 Hamburg, Germany
Fon: +49-40-42875-8426
Web: http://www.haw-hamburg.de/inet

___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel


Re: [riot-devel] Removing thirdparty repositories

2015-03-24 Thread Fabian Nack

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 STs standard library and therefore would need to be completely rewritten.



I think RIOT is currently missing an implementation for the RTC periph low-level driver for the STM32F4 series or have I overlooked something? Probably that should be added first anyhow before thinking about including any kind of RTC functionality in the LPM-Interface.



Best,

Fabian


Gesendet:Montag, 23. Mrz 2015 um 11:35 Uhr
Von:Hauke Petersen hauke.peter...@fu-berlin.de
An:RIOT OS kernel developers de...@lists.stillroot.org, RIOT OS kernel developers devel@riot-os.org
Betreff:Re: [riot-devel] Removing thirdparty repositories

Hi,

I think its fine to close the repo. As for the PRs, the sleep mode one
is the only one containing an interesting feature. This we have already
partly implemented (lpm states, RTC). Also the implementation in that PR
does not fit into our architecture, so it would have to be hard
refactored anyhow... In the end, I am not really sure how much
functionality is in that PR that we have not already merged into master...

Cheers,
Hauke

On 23.03.2015 08:53, Peter Kietzmann wrote:
 Hi,

 no objections from my side but I agree with @gabart that the LPM stuff
 might be interesting. Maybe Fabian Nack (@fnack) can tell whether
 something can be taken out of this PR?

 Best,
 Peter


 Am 22.03.2015 um 06:58 schrieb Joakim Gebart:
 I havent looked too closely, but I think at least the ideas put
 forward in https://github.com/RIOT-OS/thirdparty_cpu/pull/3 are
 useful. The PRs are old so they probably wont work on the current
 master but the LPM stuff is interesting.
 On the thirdparty_boards repo I didnt find anything interesting.

 Best regards,
 Joakim Gebart
 www.eistec.se


 On Sun, Mar 22, 2015 at 12:12 AM, Oleg Hahm oliver.h...@inria.fr
 wrote:
 Dear rousing IoTlers,

 since we dont need the thirdparty repositories for CPUs and boards
 any more
 for quite some time, I think we should finally remove them. Any
 objections?
 Can anyone with some experience with the Cortex ports take a look at
 the PRs
 in these repos that are still open and see if they contain anything
 useful
 that might be applied to the current implementation in RIOT master?

 Cheers,
 Oleg
 --
 arrival order packet joke is critical to good a make

 ___
 devel mailing list
 devel@riot-os.org
 http://lists.riot-os.org/mailman/listinfo/devel

 ___
 devel mailing list
 devel@riot-os.org
 http://lists.riot-os.org/mailman/listinfo/devel


___
devel mailing list
de...@lists.stillroot.org
https://lists.stillroot.org/mailman/listinfo/devel




___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel


[riot-devel] IEEE 802.15.4 addressing

2015-03-24 Thread Martine Lenders
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 over since then in [4]
* 64-bit long address.

As far as I read [5], there is not really any use-case for PAN ID + long
address.

The API proposed in netdev/netapi need no change for this. It's rather a
question what the drivers and 6LoWPAN should accept and generate as
addressing formats for packets.

Tell me what you think.

Cheers,
Martine

[1] https://github.com/RIOT-OS/RIOT/pull/2614
[2] https://github.com/RIOT-OS/RIOT/pull/2627
[3] https://github.com/RIOT-OS/RIOT/pull/2695
[4] https://github.com/RIOT-OS/RIOT/pull/925
[5] http://standards.ieee.org/getieee802/download/802.15.4-2011.pdf
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel


Re: [riot-devel] Riot Software Update

2015-03-24 Thread Oleg Hahm
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 question was: do the OTA task force wants to work on the
actual update distribution mechanisms (including security) in a second step or
would it make more sense trying to charter a task force that works on this in
parallel? (If the latter, I would recommend to rename it.)

Cheers,
Oleg
-- 
The bad thing about HTML DOM jokes is that everyone has their own
interpretations, so you have to tell them 9000 different ways.


pgpSFGlWeiziK.pgp
Description: PGP signature
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel


Re: [riot-devel] OTA meetup 11.2.2015

2015-03-24 Thread Ludwig Ortmann
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 infrastructure that supports
activating a downloaded image first, before we can go ahead and
implement specific update management facilities on top of this
infrastructure.

Cheers,
Ludwig


On Sun, Mar 22, 2015 at 07:06:09PM +0100, Emmanuel Baccelli wrote:
 Hi everyone,
 
 reading the minutes from the OTA workforce meeting [1], it's not obvious
 what the position is with respect to the mechanism OMA LWM2M specified for
 firmware updates. Is it planned to use this spec as base for some of the
 mechanisms we need? If not, why? If yes, let's clearly separate the
 mechanisms that we need/plan which are not specified by LWM2M.
 
 Best,
 
 Emmanuel
 
 [1] https://github.com/RIOT-OS/RIOT/wiki/minutes-OTA-meetup-13.2.2015
 
 On Tue, Mar 17, 2015 at 4:14 PM, Baptiste Clenet bapcle...@gmail.com
 wrote:
 
  Hi Ludwig,
 
  That's fine :-)
  Great! I'm looking forward to seeing it.
  I'm not on a early deadline but you know the sooner it is, the better it
  will be ;-)
 
  Cheers,
 
  2015-03-17 15:45 GMT+01:00 Ludwig Ortmann ludwig.ortm...@fu-berlin.de:
 
  Hi Baptiste,
 
  I was/am extremely busy with non-RIOT work, so please bear with me ;)
  An update will follow soonish.
 
  If you're on a deadline say so and I can look if I can squeeze it in
  somehow.
 
  Cheers,
  Ludwig
 
  Baptiste Clenet schrieb:
   Arvid, Ludwig, any improvements concerning OTA?
  
   Cheers,
  
  
  
   2015-03-09 15:12 GMT+01:00 Baptiste Clenet bapcle...@gmail.com:
  
   Hi,
  
   Ludwig, how is the planning going ?
   Could you create a wiki page (like [1]) or an issue (like [2])  with
   description of the work to do as well as assignment for each task?
   Everybody will know how it is going then.
   What do you think about it?
  
   Cheers,
  
   [1] https://github.com/RIOT-OS/RIOT/wiki/Timer-Task-Force
   [2] https://github.com/RIOT-OS/RIOT/issues/2278#issuecomment-73411503
  
   2015-02-22 10:35 GMT+01:00 Ludwig Ortmann ludwig.ortm...@fu-berlin.de
  :
  
   Hi,
  
   On Mon, Feb 16, 2015 at 06:41:05PM +0100, Oleg Hahm wrote:
 the minutes from the meeting have been added to our wiki:
 https://github.com/RIOT-OS/RIOT/wiki/minutes-OTA-meetup-13.2.2015
   
Have there any concrete next steps been identified? Did you conclude
   in
   some
kind of a schedule for upcoming tasks and who is gonna work on what?
  
   There has been some preliminary scheduling, we will announce more
   concrete planning soon, possibly in the form of an issue.
  
   Cheers, Ludwig
   ___
   devel mailing list
   devel@riot-os.org
   http://lists.riot-os.org/mailman/listinfo/devel
  
  
  
  
   --
   *Clenet Baptiste*
  
  
  
  
   --
  
   *Clenet BaptisteFR: +33 6 29 73 05 39*
   ___
   devel mailing list
   devel@riot-os.org
   http://lists.riot-os.org/mailman/listinfo/devel
  
 
 
  ___
  devel mailing list
  devel@riot-os.org
  http://lists.riot-os.org/mailman/listinfo/devel
 
 
 
 
  --
 
  *Clenet BaptisteFR: +33 6 29 73 05 39 %2B33%206%2029%2073%2005%2039*
 
 
  ___
  devel mailing list
  devel@riot-os.org
  http://lists.riot-os.org/mailman/listinfo/devel
 
 

 ___
 devel mailing list
 de...@lists.stillroot.org
 https://lists.stillroot.org/mailman/listinfo/devel

___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel