subject:"\[riot\-devel\] Network Stack Task Force"

[riot-devel] Network stack task force meeting April 30th

2015-04-28 Thread Emmanuel Baccelli

Hi everyone!

We now have a confirmed time and location for the next network stack task
force meeting: we will meet Thursday April 30th in the morning, from 10:00
to 12:00 CEST, in room 049 of the computer science building of FU Berlin
(Takustr. 9 | 14195 Berlin).

The tentative agenda with a list of items is available on the wiki [1].
Feel free to add your items.

Remote participation is welcome! Please refer to the usual guide [2] and a
PlaceCam link will be sent around before the meeting Thursday morning.

See you then,

Emmanuel

[1]
https://github.com/RIOT-OS/RIOT/wiki/minutes-network-stack-task-force-april-2015
[2]
https://github.com/RIOT-OS/RIOT/wiki/Instructions-for-remote-participation
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Network Stack Task Force

2015-02-06 Thread Hauke Petersen


Good Morning again,

we will continue with the network stack soon.

If you want to join remotely, here is the PlaceCam link:
http://placecam.de/call.php?c=0~dA5j0OrfTdsesyQKlqIZvQi7bo1YKYGdMORGFmqL8- 



How-To use it? 
https://github.com/RIOT-OS/RIOT/wiki/Instructions-for-remote-participation


Cheers,
Hauke


On 05.02.2015 10:03, Martine Lenders wrote:

Good Morning,

here is the placecam link 
http://placecam.de/call.php?c=0~dA5j0OrfTdsesyQKlqIZvQi7bo1YKYGdMORGFmqL8- 



How-To use it? 
https://github.com/RIOT-OS/RIOT/wiki/Instructions-for-remote-participation


Cheers,
Martine

2015-02-04 22:32 GMT+01:00 Matthias Waehlisch 
mailto:m.waehli...@fu-berlin.de>>:


Hi Jan,

On Wed, 4 Feb 2015, Jan Wagner wrote:

> i just installed placecam, do you send out the meeting link to this
> mailing list or person based emails?. i would like to join tomorrow
> and if needed would request that link.
>
  Hauke will provide the link tomorrow via the mailing list.

>  ps. do i need a cam or is audiio only ok?
>
  You don't need a cam, audio is fine.


Cheers
  matthias

--
Matthias Waehlisch
.  Freie Universitaet Berlin, Inst. fuer Informatik, AG CST
.  Takustr. 9, D-14195 Berlin, Germany
.. mailto:waehli...@ieee.org  ..
http://www.inf.fu-berlin.de/~waehl

:. Also: http://inet.cpt.haw-hamburg.de .. http://www.link-lab.net
___
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
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Network Stack Task Force

2015-02-06 Thread Martine Lenders

Hello Martin,

2015-02-06 9:02 GMT+01:00 Martin :
>
> thx again for recording the audio for the introducing presentation.
> It was a great help to get a more descend look at the information from the
> slides and the idea for the message based network stack approach.
>

Great!


> Yesterday we got the foundamental concept how the new network stack will
> evolve, which  "modules" are covered yet and what parts are open for
> discussion/definition.
> As I couldn't attend, I humbly ask how the meeting will proceed today, and
> if there was discussion/consensus on open topics?
>

Yesterday after the talk we discussed how to solve routing in the network
stack. Basically we decided, that for proactive routing the FIB (for a
given destination address it gives an PID/interface + next hop address) you
proposed is sufficient. For reactive routing we concluded, that it is
probably best for the FIB to return for a given destination address the PID
of the routing protocol with next hop address == NULL, if a next hop is not
available. This way we only need to check in IP if the next hop address is
!= NULL to lookup the link layer address in the NIB and then send the
packet to the given PID. The routing protocol is in case of reactive
routing then responsible for the packet and might either send it itself to
the link layer or resend it to IP after a next hop was found or drop it if
not.

We also discussed error management for sending and receiving. The result
was, that we introduce a 6th message type for netapi to communicate the
status of a packet for a certain layer, and a protocol can register to
those via netreg. I'll propose an interface for this at today's meeting.

The plan for today is to discuss Header Options, ICMPv6, neighbor discovery
and something something I forgot right now ^^

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

Re: [riot-devel] Network Stack Task Force

2015-02-06 Thread Martin

Hi,

thx again for recording the audio for the introducing presentation.
It was a great help to get a more descend look at the information from 
the slides and the idea for the message based network stack approach.

Yesterday we got the foundamental concept how the new network stack will 
evolve, which  "modules" are covered yet and what parts are open for 
discussion/definition.
As I couldn't attend, I humbly ask how the meeting will proceed today, 
and if there was discussion/consensus on open topics?

Best regards,
Martin

On 05.02.2015 15:22, Landsmann, Martin wrote:

Hi,

thx

Best regards,
Martin

*Von:* devel [devel-boun...@riot-os.org]" im Auftrag von "Martine 
Lenders [authmille...@gmail.com]

*Gesendet:* Donnerstag, 5. Februar 2015 15:08
*An:* RIOT OS kernel developers
*Betreff:* Re: [riot-devel] Network Stack Task Force

Hello,
attached you find the links to the audio recordings of the talks of 
the network stack task force meeting.

http://download.riot-os.org/nstf/meeting1/nstf-meeting1.mp3
http://download.riot-os.org/nstf/meeting1/nstf-meeting2.mp3

Regards,
Martine

2015-02-05 11:18 GMT+01:00 Jan Wagner <mailto:m...@jwagner.eu>>:

they mean this in a context of a mutli user operating system? or not?

Emmanuel Baaccelli mailto:emmanuel.bacce...@inria.fr>> hat am 5. Februar 2015 um
11:16 geschrieben:

the paper I'm about to mention in the meeting:
https://www.usenix.org/system/files/conference/osdi12/osdi12-final-183.pdf

On Thu, Feb 5, 2015 at 10:03 AM, Martine Lenders
mailto:authmille...@gmail.com>> wrote:

Good Morning,

here is the placecam link

http://placecam.de/call.php?c=0~dA5j0OrfTdsesyQKlqIZvQi7bo1YKYGdMORGFmqL8-

<http://placecam.de/call.php?c=0%7EdA5j0OrfTdsesyQKlqIZvQi7bo1YKYGdMORGFmqL8->

How-To use it?

https://github.com/RIOT-OS/RIOT/wiki/Instructions-for-remote-participation

Cheers,
Martine

2015-02-04 22:32 GMT+01:00 Matthias Waehlisch
mailto:m.waehli...@fu-berlin.de>>:

Hi Jan,

On Wed, 4 Feb 2015, Jan Wagner wrote:

> i just installed placecam, do you send out the meeting
link to this
> mailing list or person based emails?. i would like to
join tomorrow
> and if needed would request that link.
>
Hauke will provide the link tomorrow via the mailing list.

> ps. do i need a cam or is audiio only ok?
>
You don't need a cam, audio is fine.

Cheers
matthias

--
Matthias Waehlisch
. Freie Universitaet Berlin, Inst. fuer Informatik, AG CST
. Takustr. 9, D-14195 Berlin, Germany
.. mailto:waehli...@ieee.org <mailto:waehli...@ieee.org>
.. http://www.inf.fu-berlin.de/~waehl
<http://www.inf.fu-berlin.de/%7Ewaehl>
:. Also: http://inet.cpt.haw-hamburg.de ..
http://www.link-lab.net
___
devel mailing list
devel@riot-os.org <mailto:devel@riot-os.org>
http://lists.riot-os.org/mailman/listinfo/devel

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

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

___
devel mailing list
devel@riot-os.org <mailto: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
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Network Stack Task Force

2015-02-05 Thread Landsmann, Martin

Hi,

thx

Best regards,
Martin

Von: devel [devel-boun...@riot-os.org]" im Auftrag von "Martine Lenders 
[authmille...@gmail.com]
Gesendet: Donnerstag, 5. Februar 2015 15:08
An: RIOT OS kernel developers
Betreff: Re: [riot-devel] Network Stack Task Force

Hello,
attached you find the links to the audio recordings of the talks of the network 
stack task force meeting.

http://download.riot-os.org/nstf/meeting1/nstf-meeting1.mp3
http://download.riot-os.org/nstf/meeting1/nstf-meeting2.mp3

Regards,
Martine

2015-02-05 11:18 GMT+01:00 Jan Wagner mailto:m...@jwagner.eu>>:
they mean this in a context of a mutli user operating system? or not?
Emmanuel Baaccelli 
mailto:emmanuel.bacce...@inria.fr>> hat am 5. 
Februar 2015 um 11:16 geschrieben:

the paper I'm about to mention in the meeting: 
https://www.usenix.org/system/files/conference/osdi12/osdi12-final-183.pdf

On Thu, Feb 5, 2015 at 10:03 AM, Martine Lenders 
mailto:authmille...@gmail.com>> wrote:
Good Morning,

here is the placecam link 
http://placecam.de/call.php?c=0~dA5j0OrfTdsesyQKlqIZvQi7bo1YKYGdMORGFmqL8-

How-To use it? 
https://github.com/RIOT-OS/RIOT/wiki/Instructions-for-remote-participation

Cheers,
Martine

2015-02-04 22:32 GMT+01:00 Matthias Waehlisch 
mailto:m.waehli...@fu-berlin.de>>:
Hi Jan,

On Wed, 4 Feb 2015, Jan Wagner wrote:

> i just installed placecam, do you send out the meeting link to this
> mailing list or person based emails?. i would like to join tomorrow
> and if needed would request that link.
>
Hauke will provide the link tomorrow via the mailing list.

> ps. do i need a cam or is audiio only ok?
>
You don't need a cam, audio is fine.


Cheers
matthias

--
Matthias Waehlisch
. Freie Universitaet Berlin, Inst. fuer Informatik, AG CST
. Takustr. 9, D-14195 Berlin, Germany
.. mailto:waehli...@ieee.org<mailto:waehli...@ieee.org> .. 
http://www.inf.fu-berlin.de/~waehl
:. Also: http://inet.cpt.haw-hamburg.de .. http://www.link-lab.net
___
devel mailing list
devel@riot-os.org<mailto:devel@riot-os.org>
http://lists.riot-os.org/mailman/listinfo/devel


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



___
devel mailing list
devel@riot-os.org<mailto: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

Re: [riot-devel] Network Stack Task Force

2015-02-05 Thread Martine Lenders

Hello,
attached you find the links to the audio recordings of the talks of the
network stack task force meeting.

http://download.riot-os.org/nstf/meeting1/nstf-meeting1.mp3
http://download.riot-os.org/nstf/meeting1/nstf-meeting2.mp3

Regards,
Martine

2015-02-05 11:18 GMT+01:00 Jan Wagner :

>   they mean this in a context of a mutli user operating system? or not?
>
> Emmanuel Baaccelli  hat am 5. Februar 2015 um
> 11:16 geschrieben:
>
>  the paper I'm about to mention in the meeting:
> https://www.usenix.org/system/files/conference/osdi12/osdi12-final-183.pdf
>
>  On Thu, Feb 5, 2015 at 10:03 AM, Martine Lenders 
> wrote:
>
>Good Morning,
>
>  here is the placecam link
> http://placecam.de/call.php?c=0~dA5j0OrfTdsesyQKlqIZvQi7bo1YKYGdMORGFmqL8-
>
>  How-To use it?
> https://github.com/RIOT-OS/RIOT/wiki/Instructions-for-remote-participation
>
>  Cheers,
> Martine
>
>   2015-02-04 22:32 GMT+01:00 Matthias Waehlisch :
>
>
>  Hi Jan,
>
> On Wed, 4 Feb 2015, Jan Wagner wrote:
>
> > i just installed placecam, do you send out the meeting link to this
> > mailing list or person based emails?. i would like to join tomorrow
> > and if needed would request that link.
> >
>  Hauke will provide the link tomorrow via the mailing list.
>
> > ps. do i need a cam or is audiio only ok?
> >
>  You don't need a cam, audio is fine.
>
>
> Cheers
>  matthias
>
> --
> Matthias Waehlisch
> . Freie Universitaet Berlin, Inst. fuer Informatik, AG CST
> . Takustr. 9, D-14195 Berlin, Germany
> .. mailto:waehli...@ieee.org .. http://www.inf.fu-berlin.de/~waehl
> :. Also: http://inet.cpt.haw-hamburg.de .. http://www.link-lab.net
>  ___
> 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
> 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
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Network Stack Task Force

2015-02-05 Thread Jan Wagner

they mean this in a context of a mutli user operating system? or not?

> Emmanuel Baaccelli  hat am 5. Februar 2015 um
> 11:16 geschrieben:
> 
>  the paper I'm about to mention in the meeting:
> https://www.usenix.org/system/files/conference/osdi12/osdi12-final-183.pdf
> 
>  On Thu, Feb 5, 2015 at 10:03 AM, Martine Lenders   > wrote:
>> >Good Morning,
> > 
> >here is the placecam link
> > http://placecam.de/call.php?c=0~dA5j0OrfTdsesyQKlqIZvQi7bo1YKYGdMORGFmqL8-
> > 
> >How-To use it?
> > https://github.com/RIOT-OS/RIOT/wiki/Instructions-for-remote-participation
> > 
> >Cheers,
> >Martine
> > 
> >2015-02-04 22:32 GMT+01:00 Matthias Waehlisch  >  >:
> >  > > >  Hi Jan,
> > > 
> > >  On Wed, 4 Feb 2015, Jan Wagner wrote:
> > > 
> > >  > i just installed placecam, do you send out the meeting link to this
> > >  > mailing list or person based emails?. i would like to join tomorrow
> > >  > and if needed would request that link.
> > >  >
> > >  Hauke will provide the link tomorrow via the mailing list.
> > > 
> > >  > ps. do i need a cam or is audiio only ok?
> > >  >
> > >  You don't need a cam, audio is fine.
> > > 
> > > 
> > >  Cheers
> > >  matthias
> > > 
> > >  --
> > >  Matthias Waehlisch
> > >  . Freie Universitaet Berlin, Inst. fuer Informatik, AG CST
> > >  . Takustr. 9, D-14195 Berlin, Germany
> > >  .. mailto:waehli...@ieee.org  ..
> > > http://www.inf.fu-berlin.de/~waehl
> > >  :. Also: http://inet.cpt.haw-hamburg.de .. http://www.link-lab.net
> > >  ___
> > >  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
>  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

Re: [riot-devel] Network Stack Task Force

2015-02-05 Thread Emmanuel Baccelli

the paper I'm about to mention in the meeting:
https://www.usenix.org/system/files/conference/osdi12/osdi12-final-183.pdf

On Thu, Feb 5, 2015 at 10:03 AM, Martine Lenders 
wrote:

> Good Morning,
>
> here is the placecam link
> http://placecam.de/call.php?c=0~dA5j0OrfTdsesyQKlqIZvQi7bo1YKYGdMORGFmqL8-
>
> How-To use it?
> https://github.com/RIOT-OS/RIOT/wiki/Instructions-for-remote-participation
>
> Cheers,
> Martine
>
> 2015-02-04 22:32 GMT+01:00 Matthias Waehlisch :
>
>> Hi Jan,
>>
>> On Wed, 4 Feb 2015, Jan Wagner wrote:
>>
>> > i just installed placecam, do you send out the meeting link to this
>> > mailing list or person based emails?. i would like to join tomorrow
>> > and if needed would request that link.
>> >
>>   Hauke will provide the link tomorrow via the mailing list.
>>
>> >  ps. do i need a cam or is audiio only ok?
>> >
>>   You don't need a cam, audio is fine.
>>
>>
>> Cheers
>>   matthias
>>
>> --
>> Matthias Waehlisch
>> .  Freie Universitaet Berlin, Inst. fuer Informatik, AG CST
>> .  Takustr. 9, D-14195 Berlin, Germany
>> .. mailto:waehli...@ieee.org .. http://www.inf.fu-berlin.de/~waehl
>> :. Also: http://inet.cpt.haw-hamburg.de .. http://www.link-lab.net
>> ___
>> 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
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Network Stack Task Force

2015-02-05 Thread Martine Lenders

Good Morning,

here is the placecam link
http://placecam.de/call.php?c=0~dA5j0OrfTdsesyQKlqIZvQi7bo1YKYGdMORGFmqL8-

How-To use it?
https://github.com/RIOT-OS/RIOT/wiki/Instructions-for-remote-participation

Cheers,
Martine

2015-02-04 22:32 GMT+01:00 Matthias Waehlisch :

> Hi Jan,
>
> On Wed, 4 Feb 2015, Jan Wagner wrote:
>
> > i just installed placecam, do you send out the meeting link to this
> > mailing list or person based emails?. i would like to join tomorrow
> > and if needed would request that link.
> >
>   Hauke will provide the link tomorrow via the mailing list.
>
> >  ps. do i need a cam or is audiio only ok?
> >
>   You don't need a cam, audio is fine.
>
>
> Cheers
>   matthias
>
> --
> Matthias Waehlisch
> .  Freie Universitaet Berlin, Inst. fuer Informatik, AG CST
> .  Takustr. 9, D-14195 Berlin, Germany
> .. mailto:waehli...@ieee.org .. http://www.inf.fu-berlin.de/~waehl
> :. Also: http://inet.cpt.haw-hamburg.de .. http://www.link-lab.net
> ___
> 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

Re: [riot-devel] Network Stack Task Force

2015-02-04 Thread Matthias Waehlisch

Hi Jan,

On Wed, 4 Feb 2015, Jan Wagner wrote:

> i just installed placecam, do you send out the meeting link to this 
> mailing list or person based emails?. i would like to join tomorrow 
> and if needed would request that link.
>
  Hauke will provide the link tomorrow via the mailing list.

>  ps. do i need a cam or is audiio only ok?
>
  You don't need a cam, audio is fine.


Cheers
  matthias

-- 
Matthias Waehlisch
.  Freie Universitaet Berlin, Inst. fuer Informatik, AG CST
.  Takustr. 9, D-14195 Berlin, Germany
.. mailto:waehli...@ieee.org .. http://www.inf.fu-berlin.de/~waehl
:. Also: http://inet.cpt.haw-hamburg.de .. http://www.link-lab.net___
devel mailing list
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Network Stack Task Force

2015-02-04 Thread Jan Wagner

NICE slides btw. some of the technical pages of course have far to mutch text on
the slided  but I think it's ok
if you do not use  a beamer at all or a tiny room. Perfect for reading as PDF.
thanks!
 

> Hauke Petersen  hat am 4. Februar 2015 um 18:57
> geschrieben:
>
>
> Hello again,
>
> Martine and me prepared a slide-deck (see attachment) we intend to
> present tomorrow in the morning. The intend is to bring everyone
> involved up-to-speed on the current development status and to use these
> slides as a base-line for further activities.
>
> The slides are neither complete nor are they meant to function
> stand-alone as network stack documentation - they are very much early WIP!
>
> Cheers,
> Hauke
>
>
> On 04.02.2015 12:05, Hauke Petersen wrote:
> > Hi everyone!
> >
> > We now have a confirmed location for the task force meeting: We will
> > start tomorrow at 10AM in room K40 in the basement of the computer
> > science building of FU Berlin (Takustr. 9 | 14195 Berlin).
> >
> > A PlaceCam link for remote participation will be send around before
> > the meeting tomorrow morning.
> >
> > See you tomorrow,
> > Hauke
> >
> >
> >
> > On 16.01.2015 19:08, Hauke Petersen wrote:
> >> Dear RIOTers,
> >>
> >> we recently came up with the idea to create task forces around
> >> special topics in RIOT to concentrate and speed up the development of
> >> key parts. The idea is to bring all people that are interested in
> >> this topic and are prepared to spend some on it together in a
> >> (virtual) room and start out by a 2-3 day workshop style event. This
> >> first period should be used to discuss the topic in detail to bring
> >> everyone involved on the same page, to come up with a clear
> >> architecture, and define interfaces and sub-modules. The hope is,
> >> that we can go into a very productive implementing phase afterward
> >> and speed up the overall development.
> >>
> >> The first key topic we want to try out this concept is the ongoing
> >> re-structuring of the network stack. I propose the following plan for
> >> this:
> >> - we use next week to coordinate (who wants to join, what is the
> >> current state, what are the most pressing open questions)
> >> - we block 2 days in the last week of January for a (virtual)
> >> white-board centered workshop
> >>
> >> For the workshop I propose January 27-28, but its just a proposal...
> >>
> >>
> >> Regarding technical aspects that are currently under (heavy)
> >> construction or need to be clarified (@Martine: please hit me if I
> >> have it completely wrong here...):
> >> - optimizations to the netdev interface
> >> - optimizations to the netapi interface
> >> - analysis of possible data loss using netapi in its current state
> >> - how to pass data/headers/packets around the stack
> >> - possible generalization and/or quotas in the packet buffer
> >> - concepts of global protocol/module list and global protocol handler
> >> registry
> >> - API definition for the neighbor table
> >> - API definition for the forwarding table
> >> - possible join for neighbor and forwarding table
> >> - hooks for various routing protocols
> >> - ???
> >>
> >> This is just a initial list of topics to be further discussed - I
> >> hope we can detail it out over the next week to have a good idea
> >> about the questions that need time for discussion!
> >>
> >>
> >> So concluding:
> >> - who is interested (and/or) wiling to joing this effort?
> >> - are there any ideas on the concrete organization of such a task-force?
> >> - are there technical aspects I forgot?
> >>
> >> Looking forward to your feedback!
> >>
> >> Cheers,
> >> Hauke
> >>
> >> ___
> >> 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
> 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

Re: [riot-devel] Network Stack Task Force

2015-02-04 Thread Jan Wagner

hi hauke
 
i just installed placecam, do you send out the meeting link to this mailing list
or person based emails?.
i would like to join tomorrow and if needed would request that link.
 
ps. do i need a cam or is audiio only ok?
 
greets jan
> Hauke Petersen  hat am 4. Februar 2015 um 18:57
> geschrieben:
>
>
> Hello again,
>
> Martine and me prepared a slide-deck (see attachment) we intend to
> present tomorrow in the morning. The intend is to bring everyone
> involved up-to-speed on the current development status and to use these
> slides as a base-line for further activities.
>
> The slides are neither complete nor are they meant to function
> stand-alone as network stack documentation - they are very much early WIP!
>
> Cheers,
> Hauke
>
>
> On 04.02.2015 12:05, Hauke Petersen wrote:
> > Hi everyone!
> >
> > We now have a confirmed location for the task force meeting: We will
> > start tomorrow at 10AM in room K40 in the basement of the computer
> > science building of FU Berlin (Takustr. 9 | 14195 Berlin).
> >
> > A PlaceCam link for remote participation will be send around before
> > the meeting tomorrow morning.
> >
> > See you tomorrow,
> > Hauke
> >
> >
> >
> > On 16.01.2015 19:08, Hauke Petersen wrote:
> >> Dear RIOTers,
> >>
> >> we recently came up with the idea to create task forces around
> >> special topics in RIOT to concentrate and speed up the development of
> >> key parts. The idea is to bring all people that are interested in
> >> this topic and are prepared to spend some on it together in a
> >> (virtual) room and start out by a 2-3 day workshop style event. This
> >> first period should be used to discuss the topic in detail to bring
> >> everyone involved on the same page, to come up with a clear
> >> architecture, and define interfaces and sub-modules. The hope is,
> >> that we can go into a very productive implementing phase afterward
> >> and speed up the overall development.
> >>
> >> The first key topic we want to try out this concept is the ongoing
> >> re-structuring of the network stack. I propose the following plan for
> >> this:
> >> - we use next week to coordinate (who wants to join, what is the
> >> current state, what are the most pressing open questions)
> >> - we block 2 days in the last week of January for a (virtual)
> >> white-board centered workshop
> >>
> >> For the workshop I propose January 27-28, but its just a proposal...
> >>
> >>
> >> Regarding technical aspects that are currently under (heavy)
> >> construction or need to be clarified (@Martine: please hit me if I
> >> have it completely wrong here...):
> >> - optimizations to the netdev interface
> >> - optimizations to the netapi interface
> >> - analysis of possible data loss using netapi in its current state
> >> - how to pass data/headers/packets around the stack
> >> - possible generalization and/or quotas in the packet buffer
> >> - concepts of global protocol/module list and global protocol handler
> >> registry
> >> - API definition for the neighbor table
> >> - API definition for the forwarding table
> >> - possible join for neighbor and forwarding table
> >> - hooks for various routing protocols
> >> - ???
> >>
> >> This is just a initial list of topics to be further discussed - I
> >> hope we can detail it out over the next week to have a good idea
> >> about the questions that need time for discussion!
> >>
> >>
> >> So concluding:
> >> - who is interested (and/or) wiling to joing this effort?
> >> - are there any ideas on the concrete organization of such a task-force?
> >> - are there technical aspects I forgot?
> >>
> >> Looking forward to your feedback!
> >>
> >> Cheers,
> >> Hauke
> >>
> >> ___
> >> 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
> 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

Re: [riot-devel] Network Stack Task Force

2015-02-04 Thread Hauke Petersen


Hi everyone!

We now have a confirmed location for the task force meeting: We will 
start tomorrow at 10AM in room K40 in the basement of the computer 
science building of FU Berlin (Takustr. 9 | 14195 Berlin).


A PlaceCam link for remote participation will be send around before the 
meeting tomorrow morning.


See you tomorrow,
Hauke



On 16.01.2015 19:08, Hauke Petersen wrote:

Dear RIOTers,

we recently came up with the idea to create task forces around special 
topics in RIOT to concentrate and speed up the development of key 
parts. The idea is to bring all people that are interested in this 
topic and are prepared to spend some on it together in a (virtual) 
room and start out by a 2-3 day workshop style event. This first 
period should be used to discuss the topic in detail to bring everyone 
involved on the same page, to come up with a clear architecture, and 
define interfaces and sub-modules. The hope is, that we can go into a 
very productive implementing phase afterward and speed up the overall 
development.


The first key topic we want to try out this concept is the ongoing 
re-structuring of the network stack. I propose the following plan for 
this:
- we use next week to coordinate (who wants to join, what is the 
current state, what are the most pressing open questions)
- we block 2 days in the last week of January for a (virtual) 
white-board centered workshop


For the workshop I propose January 27-28, but its just a proposal...


Regarding technical aspects that are currently under (heavy) 
construction or need to be clarified (@Martine: please hit me if I 
have it completely wrong here...):

- optimizations to the netdev interface
- optimizations to the netapi interface
- analysis of possible data loss using netapi in its current state
- how to pass data/headers/packets around the stack
- possible generalization and/or quotas in the packet buffer
- concepts of global protocol/module list and global protocol handler 
registry

- API definition for the neighbor table
- API definition for the forwarding table
- possible join for neighbor and forwarding table
- hooks for various routing protocols
- ???

This is just a initial list of topics to be further discussed - I hope 
we can detail it out over the next week to have a good idea about the 
questions that need time for discussion!



So concluding:
- who is interested (and/or) wiling to joing this effort?
- are there any ideas on the concrete organization of such a task-force?
- are there technical aspects I forgot?

Looking forward to your feedback!

Cheers,
Hauke

___
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

Re: [riot-devel] Network Stack Task Force

2015-02-03 Thread Jonas Remmert

Hi RIOTers,

sry for my late reply.  I would like to attend the Network Stack Task 
Force personally and will be in Berlin on Thursday and Friday.

Oleg told me that the meeting will most likely take place at the 
University instead of C-Base.

Could someone provide the location and time for the meeting?

Tanks,

Best
Jonas

On 29.01.2015 19:23, Hauke Petersen wrote:

Hi RIOTers,

as Martine already posted, the network stack task force will meet next 
week Thursday and Friday (Feb 5&6). Following I tried to draft the 
main goals as well as a preliminary schedule:

GOALS:
--
- synchronize everyone involved on the ongoing activities
- collect use cases
- map them on the current state of the architecture and see if the 
architecture holds

- refine the network stack architecture
- detail out a concrete work-plan

As mentioned earlier, the goal is not to end up with a prototypical 
implementation or similar - we should really focus on the concepts and 
architecture, so we end up with a clear idea (and plan) for the 
implementation afterward.

PRELIMINARY SCHEDULE:
--
Thursday before lunch:
Martine and me will present in detail the current state of the network 
stack architecture and concepts, so everyone involved is synchronized. 
The current state can then be used as a base-line for further 
discussion and refinement (or we end up by completely re-designing it...)

Thursday after lunch:
We collect use cases for the network stack (as in: what happens in 
this situation, what module is needing what kind of data, who is 
talking to whom). We then map these use cases to the proposed 
architecture to identify short-comings and come up with a list of open 
topics that need to be discussed further.

Friday:
Based on the open topics and design short-comings, I suggest we go 
through them item by item and come up with solutions :-)

Please append anything that we should add to the discussion or any 
ideas for making the 'workshop' as efficient as possible!

See (hear) you next week,
Hauke

On 27.01.2015 08:26, Martine Lenders wrote:

Hello Paul,
the workshop will be held at Freie Universität Berlin and (probably, 
as far as I can see from the attendees) HAW Hamburg, simultaneously, 
but will also provide the PlaceCam-Link [1] that will connect the two 
events and allow for remote participation.

Details for the schedule will be posted in the next few days.

Cheers,

Martine

[1] placecam.de 

Am 26.01.2015 19:05 schrieb mailto:gnu...@dds.nl>>:

Is this a webbased meeting or a meeting in Berlin ?.

Paul.

Peter Kietzmann mailto:peter.kietzm...@haw-hamburg.de>> schreef:

Hi,

I'm fine.

Cheers,
Peter

Am 26.01.2015 um 10:56 schrieb Martine Lenders:

Hi,
looks like it's gonna be February 5th and 6th (a Thursday
and a Friday). Martin is the only one that is not
available on Thursday. Is everyone okay with that?

Cheers,
Martine

2015-01-19 17:30 GMT+01:00 Hauke Petersen
mailto:hauke.peter...@fu-berlin.de>
>>:

   Hi everyone,

   sandwiching the H&A is indeed not a good idea, I agree.

   Thanks Martine for the doodle, let's wait until
Thursday and
   decide on the dates based on the outcome of the doodle
then.

   Cheers,
   Hauke

   On 19.01.2015 13:17, Martine Lenders wrote:

   Hi,
   Since this thread has gained some traction now I
would propose to
   use to dudle it out. The two days adjacent to each
other where
   most are available would be the date:
https://dudle.inf.tu-dresden.de/RIOT-NSFT1/

   Cheers,
   Martine

   Am 19.01.2015 12:29 schrieb "Emmanuel Baccelli"
   mailto:emmanuel.bacce...@inria.fr>
>>:

   Hi Thomas,
   damn, your right, I misread the dates. So
Hack'nAck would be
   "sandwiched" inside the workshop, and I guess
that's not
   great. How about 28-29, or 29-30, then?
   Best
   Emmanuel

   On Mon, Jan 19, 2015 at 11:24 AM, Thomas Eichinger
   mailto:thomas.eichin...@fu-berlin.de>
   >> wrote:

   Hi,

   I?d also like to attend. I?d prefer a date

Re: [riot-devel] Network Stack Task Force

2015-01-29 Thread Hauke Petersen

Hi RIOTers,

as Martine already posted, the network stack task force will meet next 
week Thursday and Friday (Feb 5&6). Following I tried to draft the main 
goals as well as a preliminary schedule:

GOALS:
--
- synchronize everyone involved on the ongoing activities
- collect use cases
- map them on the current state of the architecture and see if the 
architecture holds

- refine the network stack architecture
- detail out a concrete work-plan

As mentioned earlier, the goal is not to end up with a prototypical 
implementation or similar - we should really focus on the concepts and 
architecture, so we end up with a clear idea (and plan) for the 
implementation afterward.

PRELIMINARY SCHEDULE:
--
Thursday before lunch:
Martine and me will present in detail the current state of the network 
stack architecture and concepts, so everyone involved is synchronized. 
The current state can then be used as a base-line for further discussion 
and refinement (or we end up by completely re-designing it...)

Thursday after lunch:
We collect use cases for the network stack (as in: what happens in this 
situation, what module is needing what kind of data, who is talking to 
whom). We then map these use cases to the proposed architecture to 
identify short-comings and come up with a list of open topics that need 
to be discussed further.

Friday:
Based on the open topics and design short-comings, I suggest we go 
through them item by item and come up with solutions :-)

Please append anything that we should add to the discussion or any ideas 
for making the 'workshop' as efficient as possible!

See (hear) you next week,
Hauke

On 27.01.2015 08:26, Martine Lenders wrote:

Hello Paul,
the workshop will be held at Freie Universität Berlin and (probably, 
as far as I can see from the attendees) HAW Hamburg, simultaneously, 
but will also provide the PlaceCam-Link [1] that will connect the two 
events and allow for remote participation.

Details for the schedule will be posted in the next few days.

Cheers,

Martine

[1] placecam.de 

Am 26.01.2015 19:05 schrieb mailto:gnu...@dds.nl>>:

Is this a webbased meeting or a meeting in Berlin ?.

Paul.

Peter Kietzmann mailto:peter.kietzm...@haw-hamburg.de>> schreef:

Hi,

I'm fine.

Cheers,
Peter

Am 26.01.2015 um 10:56 schrieb Martine Lenders:

Hi,
looks like it's gonna be February 5th and 6th (a Thursday
and a Friday). Martin is the only one that is not
available on Thursday. Is everyone okay with that?

Cheers,
Martine

2015-01-19 17:30 GMT+01:00 Hauke Petersen
mailto:hauke.peter...@fu-berlin.de>
>>:

   Hi everyone,

   sandwiching the H&A is indeed not a good idea, I agree.

   Thanks Martine for the doodle, let's wait until
Thursday and
   decide on the dates based on the outcome of the doodle
then.

   Cheers,
   Hauke

   On 19.01.2015 13:17, Martine Lenders wrote:

   Hi,
   Since this thread has gained some traction now I
would propose to
   use to dudle it out. The two days adjacent to each
other where
   most are available would be the date:
https://dudle.inf.tu-dresden.de/RIOT-NSFT1/

   Cheers,
   Martine

   Am 19.01.2015 12:29 schrieb "Emmanuel Baccelli"
   mailto:emmanuel.bacce...@inria.fr>
>>:

   Hi Thomas,
   damn, your right, I misread the dates. So
Hack'nAck would be
   "sandwiched" inside the workshop, and I guess
that's not
   great. How about 28-29, or 29-30, then?
   Best
   Emmanuel

   On Mon, Jan 19, 2015 at 11:24 AM, Thomas Eichinger
   mailto:thomas.eichin...@fu-berlin.de>
   >> wrote:

   Hi,

   I?d also like to attend. I?d prefer a date
without H&A
   in-between (as these tend to
   end late at night, which would make it hard
to start with
   NSTF early again) but
   wouldn?t object if there is a majority in
favour of this.

   Best, Thomas

Re: [riot-devel] Network Stack Task Force

2015-01-26 Thread Martine Lenders

Hello Paul,
the workshop will be held at Freie Universität Berlin and (probably, as far
as I can see from the attendees) HAW Hamburg, simultaneously, but will also
provide the PlaceCam-Link [1] that will connect the two events and allow
for remote participation.

Details for the schedule will be posted in the next few days.

Cheers,

Martine

[1] placecam.de
Am 26.01.2015 19:05 schrieb :

> Is this a webbased meeting or a meeting in Berlin ?.
>
> Paul.
>
> Peter Kietzmann  schreef:
>
>  Hi,
>>
>> I'm fine.
>>
>> Cheers,
>> Peter
>>
>> Am 26.01.2015 um 10:56 schrieb Martine Lenders:
>>
>>> Hi,
>>> looks like it's gonna be February 5th and 6th (a Thursday and a Friday).
>>> Martin is the only one that is not available on Thursday. Is everyone okay
>>> with that?
>>>
>>> Cheers,
>>> Martine
>>>
>>> 2015-01-19 17:30 GMT+01:00 Hauke Petersen >> >:
>>>
>>>Hi everyone,
>>>
>>>sandwiching the H&A is indeed not a good idea, I agree.
>>>
>>>Thanks Martine for the doodle, let's wait until Thursday and
>>>decide on the dates based on the outcome of the doodle then.
>>>
>>>Cheers,
>>>Hauke
>>>
>>>
>>>
>>>On 19.01.2015 13:17, Martine Lenders wrote:
>>>

Hi,
Since this thread has gained some traction now I would propose to
use to dudle it out. The two days adjacent to each other where
most are available would be the date:
https://dudle.inf.tu-dresden.de/RIOT-NSFT1/

Cheers,
Martine

Am 19.01.2015 12:29 schrieb "Emmanuel Baccelli"
mailto:emmanuel.bacce...@inria.fr>>:

Hi Thomas,
damn, your right, I misread the dates. So Hack'nAck would be
"sandwiched" inside the workshop, and I guess that's not
great. How about 28-29, or 29-30, then?
Best
Emmanuel

On Mon, Jan 19, 2015 at 11:24 AM, Thomas Eichinger
>>>> wrote:

Hi,

I?d also like to attend. I?d prefer a date without H&A
in-between (as these tend to
end late at night, which would make it hard to start with
NSTF early again) but
wouldn?t object if there is a majority in favour of this.

Best, Thomas

> On 16 Jan 2015, at 19:08, Hauke Petersen
>>>> wrote:
>
> Dear RIOTers,
>
> we recently came up with the idea to create task forces
around special topics in RIOT to concentrate and speed up
the development of key parts. The idea is to bring all
people that are interested in this topic and are prepared
to spend some on it together in a (virtual) room and
start out by a 2-3 day workshop style event. This first
period should be used to discuss the topic in detail to
bring everyone involved on the same page, to come up with
a clear architecture, and define interfaces and
sub-modules. The hope is, that we can go into a very
productive implementing phase afterward and speed up the
overall development.
>
> The first key topic we want to try out this concept is
the ongoing re-structuring of the network stack. I
propose the following plan for this:
> - we use next week to coordinate (who wants to join,
what is the current state, what are the most pressing
open questions)
> - we block 2 days in the last week of January for a
(virtual) white-board centered workshop
>
> For the workshop I propose January 27-28, but its just
a proposal...
>
>
> Regarding technical aspects that are currently under
(heavy) construction or need to be clarified (@Martine:
please hit me if I have it completely wrong here...):
> - optimizations to the netdev interface
> - optimizations to the netapi interface
> - analysis of possible data loss using netapi in its
current state
> - how to pass data/headers/packets around the stack
> - possible generalization and/or quotas in the packet
buffer
> - concepts of global protocol/module list and global
protocol handler registry
> - API definition for the neighbor table
> - API definition for the forwarding table
> - possible join for neighbor and forwarding table
> -

Re: [riot-devel] Network Stack Task Force

2015-01-26 Thread gnupic


Is this a webbased meeting or a meeting in Berlin ?.

Paul.

Peter Kietzmann  schreef:


Hi,

I'm fine.

Cheers,
Peter

Am 26.01.2015 um 10:56 schrieb Martine Lenders:

Hi,
looks like it's gonna be February 5th and 6th (a Thursday and a  
Friday). Martin is the only one that is not available on Thursday.  
Is everyone okay with that?


Cheers,
Martine

2015-01-19 17:30 GMT+01:00 Hauke Petersen  
mailto:hauke.peter...@fu-berlin.de>>:


   Hi everyone,

   sandwiching the H&A is indeed not a good idea, I agree.

   Thanks Martine for the doodle, let's wait until Thursday and
   decide on the dates based on the outcome of the doodle then.

   Cheers,
   Hauke



   On 19.01.2015 13:17, Martine Lenders wrote:


   Hi,
   Since this thread has gained some traction now I would propose to
   use to dudle it out. The two days adjacent to each other where
   most are available would be the date:
   https://dudle.inf.tu-dresden.de/RIOT-NSFT1/

   Cheers,
   Martine

   Am 19.01.2015 12:29 schrieb "Emmanuel Baccelli"
   mailto:emmanuel.bacce...@inria.fr>>:

   Hi Thomas,
   damn, your right, I misread the dates. So Hack'nAck would be
   "sandwiched" inside the workshop, and I guess that's not
   great. How about 28-29, or 29-30, then?
   Best
   Emmanuel

   On Mon, Jan 19, 2015 at 11:24 AM, Thomas Eichinger
   mailto:thomas.eichin...@fu-berlin.de>> wrote:

   Hi,

   I?d also like to attend. I?d prefer a date without H&A
   in-between (as these tend to
   end late at night, which would make it hard to start with
   NSTF early again) but
   wouldn?t object if there is a majority in favour of this.

   Best, Thomas

   > On 16 Jan 2015, at 19:08, Hauke Petersen
   mailto:hauke.peter...@fu-berlin.de>> wrote:
   >
   > Dear RIOTers,
   >
   > we recently came up with the idea to create task forces
   around special topics in RIOT to concentrate and speed up
   the development of key parts. The idea is to bring all
   people that are interested in this topic and are prepared
   to spend some on it together in a (virtual) room and
   start out by a 2-3 day workshop style event. This first
   period should be used to discuss the topic in detail to
   bring everyone involved on the same page, to come up with
   a clear architecture, and define interfaces and
   sub-modules. The hope is, that we can go into a very
   productive implementing phase afterward and speed up the
   overall development.
   >
   > The first key topic we want to try out this concept is
   the ongoing re-structuring of the network stack. I
   propose the following plan for this:
   > - we use next week to coordinate (who wants to join,
   what is the current state, what are the most pressing
   open questions)
   > - we block 2 days in the last week of January for a
   (virtual) white-board centered workshop
   >
   > For the workshop I propose January 27-28, but its just
   a proposal...
   >
   >
   > Regarding technical aspects that are currently under
   (heavy) construction or need to be clarified (@Martine:
   please hit me if I have it completely wrong here...):
   > - optimizations to the netdev interface
   > - optimizations to the netapi interface
   > - analysis of possible data loss using netapi in its
   current state
   > - how to pass data/headers/packets around the stack
   > - possible generalization and/or quotas in the packet
   buffer
   > - concepts of global protocol/module list and global
   protocol handler registry
   > - API definition for the neighbor table
   > - API definition for the forwarding table
   > - possible join for neighbor and forwarding table
   > - hooks for various routing protocols
   > - ???
   >
   > This is just a initial list of topics to be further
   discussed - I hope we can detail it out over the next
   week to have a good idea about the questions that need
   time for discussion!
   >
   >
   > So concluding:
   > - who is interested (and/or) wiling to joing this effort?
   > - are there any ideas on the concrete organization of
   such a task-force?
   > - are there technical aspects I forgot?
   >
   > Looking forward to your feedback!
   >
   > Cheers,
   > Hauke
   >
   > ___
   > devel mailing list
   > devel@riot-os.org 
   > http://lists.riot-os.org/mailman/listinfo/devel

   _

Re: [riot-devel] Network Stack Task Force

2015-01-26 Thread Martin

Hi,

I can probably attend on thursday from afternoon.
Thats bad for me, but I will just squeeze Lotte, Peter and Raphael ;) .
So it okay for me too.

Best regards,
Martin

On 26.01.2015 10:56, Martine Lenders wrote:

Hi,
looks like it's gonna be February 5th and 6th (a Thursday and a 
Friday). Martin is the only one that is not available on Thursday. Is 
everyone okay with that?

Cheers,
Martine

2015-01-19 17:30 GMT+01:00 Hauke Petersen >:

Hi everyone,

sandwiching the H&A is indeed not a good idea, I agree.

Thanks Martine for the doodle, let's wait until Thursday and
decide on the dates based on the outcome of the doodle then.

Cheers,
Hauke

On 19.01.2015 13:17, Martine Lenders wrote:

Hi,
Since this thread has gained some traction now I would propose to
use to dudle it out. The two days adjacent to each other where
most are available would be the date:
https://dudle.inf.tu-dresden.de/RIOT-NSFT1/

Cheers,
Martine

Am 19.01.2015 12:29 schrieb "Emmanuel Baccelli"
mailto:emmanuel.bacce...@inria.fr>>:

Hi Thomas,
damn, your right, I misread the dates. So Hack'nAck would be
"sandwiched" inside the workshop, and I guess that's not
great. How about 28-29, or 29-30, then?
Best
Emmanuel

On Mon, Jan 19, 2015 at 11:24 AM, Thomas Eichinger
mailto:thomas.eichin...@fu-berlin.de>> wrote:

Hi,

I’d also like to attend. I’d prefer a date without H&A
in-between (as these tend to
end late at night, which would make it hard to start with
NSTF early again) but
wouldn’t object if there is a majority in favour of this.

Best, Thomas

> On 16 Jan 2015, at 19:08, Hauke Petersen
mailto:hauke.peter...@fu-berlin.de>> wrote:
>
> Dear RIOTers,
>
> we recently came up with the idea to create task forces
around special topics in RIOT to concentrate and speed up
the development of key parts. The idea is to bring all
people that are interested in this topic and are prepared
to spend some on it together in a (virtual) room and
start out by a 2-3 day workshop style event. This first
period should be used to discuss the topic in detail to
bring everyone involved on the same page, to come up with
a clear architecture, and define interfaces and
sub-modules. The hope is, that we can go into a very
productive implementing phase afterward and speed up the
overall development.
>
> The first key topic we want to try out this concept is
the ongoing re-structuring of the network stack. I
propose the following plan for this:
> - we use next week to coordinate (who wants to join,
what is the current state, what are the most pressing
open questions)
> - we block 2 days in the last week of January for a
(virtual) white-board centered workshop
>
> For the workshop I propose January 27-28, but its just
a proposal...
>
>
> Regarding technical aspects that are currently under
(heavy) construction or need to be clarified (@Martine:
please hit me if I have it completely wrong here...):
> - optimizations to the netdev interface
> - optimizations to the netapi interface
> - analysis of possible data loss using netapi in its
current state
> - how to pass data/headers/packets around the stack
> - possible generalization and/or quotas in the packet
buffer
> - concepts of global protocol/module list and global
protocol handler registry
> - API definition for the neighbor table
> - API definition for the forwarding table
> - possible join for neighbor and forwarding table
> - hooks for various routing protocols
> - ???
>
> This is just a initial list of topics to be further
discussed - I hope we can detail it out over the next
week to have a good idea about the questions that need
time for discussion!
>
>
> So concluding:
> - who is interested (and/or) wiling to joing this effort?
> - are there any ideas on the concrete organization of
such a task-force?
> - are there technical aspects I forgot?
>
> Looking forward to your feedback!
>
> Cheers,
> Hauke
>
> ___
> devel

Re: [riot-devel] Network Stack Task Force

2015-01-26 Thread Peter Kietzmann

Hi,

I'm fine.

Cheers,
Peter

Am 26.01.2015 um 10:56 schrieb Martine Lenders:

Hi,
looks like it's gonna be February 5th and 6th (a Thursday and a 
Friday). Martin is the only one that is not available on Thursday. Is 
everyone okay with that?

Cheers,
Martine

2015-01-19 17:30 GMT+01:00 Hauke Petersen >:

Hi everyone,

sandwiching the H&A is indeed not a good idea, I agree.

Thanks Martine for the doodle, let's wait until Thursday and
decide on the dates based on the outcome of the doodle then.

Cheers,
Hauke

On 19.01.2015 13:17, Martine Lenders wrote:

Hi,
Since this thread has gained some traction now I would propose to
use to dudle it out. The two days adjacent to each other where
most are available would be the date:
https://dudle.inf.tu-dresden.de/RIOT-NSFT1/

Cheers,
Martine

Am 19.01.2015 12:29 schrieb "Emmanuel Baccelli"
mailto:emmanuel.bacce...@inria.fr>>:

Hi Thomas,
damn, your right, I misread the dates. So Hack'nAck would be
"sandwiched" inside the workshop, and I guess that's not
great. How about 28-29, or 29-30, then?
Best
Emmanuel

On Mon, Jan 19, 2015 at 11:24 AM, Thomas Eichinger
mailto:thomas.eichin...@fu-berlin.de>> wrote:

Hi,

I’d also like to attend. I’d prefer a date without H&A
in-between (as these tend to
end late at night, which would make it hard to start with
NSTF early again) but
wouldn’t object if there is a majority in favour of this.

Best, Thomas

> On 16 Jan 2015, at 19:08, Hauke Petersen
mailto:hauke.peter...@fu-berlin.de>> wrote:
>
> Dear RIOTers,
>
> we recently came up with the idea to create task forces
around special topics in RIOT to concentrate and speed up
the development of key parts. The idea is to bring all
people that are interested in this topic and are prepared
to spend some on it together in a (virtual) room and
start out by a 2-3 day workshop style event. This first
period should be used to discuss the topic in detail to
bring everyone involved on the same page, to come up with
a clear architecture, and define interfaces and
sub-modules. The hope is, that we can go into a very
productive implementing phase afterward and speed up the
overall development.
>
> The first key topic we want to try out this concept is
the ongoing re-structuring of the network stack. I
propose the following plan for this:
> - we use next week to coordinate (who wants to join,
what is the current state, what are the most pressing
open questions)
> - we block 2 days in the last week of January for a
(virtual) white-board centered workshop
>
> For the workshop I propose January 27-28, but its just
a proposal...
>
>
> Regarding technical aspects that are currently under
(heavy) construction or need to be clarified (@Martine:
please hit me if I have it completely wrong here...):
> - optimizations to the netdev interface
> - optimizations to the netapi interface
> - analysis of possible data loss using netapi in its
current state
> - how to pass data/headers/packets around the stack
> - possible generalization and/or quotas in the packet
buffer
> - concepts of global protocol/module list and global
protocol handler registry
> - API definition for the neighbor table
> - API definition for the forwarding table
> - possible join for neighbor and forwarding table
> - hooks for various routing protocols
> - ???
>
> This is just a initial list of topics to be further
discussed - I hope we can detail it out over the next
week to have a good idea about the questions that need
time for discussion!
>
>
> So concluding:
> - who is interested (and/or) wiling to joing this effort?
> - are there any ideas on the concrete organization of
such a task-force?
> - are there technical aspects I forgot?
>
> Looking forward to your feedback!
>
> Cheers,
> Hauke
>
> ___
> devel mailing list
> devel@riot-os.org 
> http://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Network Stack Task Force

2015-01-26 Thread Martine Lenders

Hi,
looks like it's gonna be February 5th and 6th (a Thursday and a Friday).
Martin is the only one that is not available on Thursday. Is everyone okay
with that?

Cheers,
Martine

2015-01-19 17:30 GMT+01:00 Hauke Petersen :

>  Hi everyone,
>
> sandwiching the H&A is indeed not a good idea, I agree.
>
> Thanks Martine for the doodle, let's wait until Thursday and decide on the
> dates based on the outcome of the doodle then.
>
> Cheers,
> Hauke
>
>
>
> On 19.01.2015 13:17, Martine Lenders wrote:
>
> Hi,
> Since this thread has gained some traction now I would propose to use to
> dudle it out. The two days adjacent to each other where most are available
> would be the date: https://dudle.inf.tu-dresden.de/RIOT-NSFT1/
>
> Cheers,
> Martine
> Am 19.01.2015 12:29 schrieb "Emmanuel Baccelli" <
> emmanuel.bacce...@inria.fr>:
>
>> Hi Thomas,
>> damn, your right, I misread the dates. So Hack'nAck would be "sandwiched"
>> inside the workshop, and I guess that's not great. How about 28-29, or
>> 29-30, then?
>> Best
>> Emmanuel
>>
>> On Mon, Jan 19, 2015 at 11:24 AM, Thomas Eichinger <
>> thomas.eichin...@fu-berlin.de> wrote:
>>
>>> Hi,
>>>
>>> I’d also like to attend. I’d prefer a date without H&A in-between (as
>>> these tend to
>>> end late at night, which would make it hard to start with NSTF early
>>> again) but
>>> wouldn’t object if there is a majority in favour of this.
>>>
>>> Best, Thomas
>>>
>>> > On 16 Jan 2015, at 19:08, Hauke Petersen 
>>> wrote:
>>> >
>>> > Dear RIOTers,
>>> >
>>> > we recently came up with the idea to create task forces around special
>>> topics in RIOT to concentrate and speed up the development of key parts.
>>> The idea is to bring all people that are interested in this topic and are
>>> prepared to spend some on it together in a (virtual) room and start out by
>>> a 2-3 day workshop style event. This first period should be used to discuss
>>> the topic in detail to bring everyone involved on the same page, to come up
>>> with a clear architecture, and define interfaces and sub-modules. The hope
>>> is, that we can go into a very productive implementing phase afterward and
>>> speed up the overall development.
>>> >
>>> > The first key topic we want to try out this concept is the ongoing
>>> re-structuring of the network stack. I propose the following plan for this:
>>> > - we use next week to coordinate (who wants to join, what is the
>>> current state, what are the most pressing open questions)
>>> > - we block 2 days in the last week of January for a (virtual)
>>> white-board centered workshop
>>> >
>>> > For the workshop I propose January 27-28, but its just a proposal...
>>> >
>>> >
>>> > Regarding technical aspects that are currently under (heavy)
>>> construction or need to be clarified (@Martine: please hit me if I have it
>>> completely wrong here...):
>>> > - optimizations to the netdev interface
>>> > - optimizations to the netapi interface
>>> > - analysis of possible data loss using netapi in its current state
>>> > - how to pass data/headers/packets around the stack
>>> > - possible generalization and/or quotas in the packet buffer
>>> > - concepts of global protocol/module list and global protocol handler
>>> registry
>>> > - API definition for the neighbor table
>>> > - API definition for the forwarding table
>>> > - possible join for neighbor and forwarding table
>>> > - hooks for various routing protocols
>>> > - ???
>>> >
>>> > This is just a initial list of topics to be further discussed - I hope
>>> we can detail it out over the next week to have a good idea about the
>>> questions that need time for discussion!
>>> >
>>> >
>>> > So concluding:
>>> > - who is interested (and/or) wiling to joing this effort?
>>> > - are there any ideas on the concrete organization of such a
>>> task-force?
>>> > - are there technical aspects I forgot?
>>> >
>>> > Looking forward to your feedback!
>>> >
>>> > Cheers,
>>> > Hauke
>>> >
>>> > ___
>>> > 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
>> devel@riot-os.org
>> http://lists.riot-os.org/mailman/listinfo/devel
>>
>>
>
> ___
> devel mailing 
> listdevel@riot-os.orghttp://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
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Network Stack Task Force

2015-01-19 Thread Hauke Petersen


Hi everyone,

sandwiching the H&A is indeed not a good idea, I agree.

Thanks Martine for the doodle, let's wait until Thursday and decide on 
the dates based on the outcome of the doodle then.


Cheers,
Hauke


On 19.01.2015 13:17, Martine Lenders wrote:


Hi,
Since this thread has gained some traction now I would propose to use 
to dudle it out. The two days adjacent to each other where most are 
available would be the date: https://dudle.inf.tu-dresden.de/RIOT-NSFT1/


Cheers,
Martine

Am 19.01.2015 12:29 schrieb "Emmanuel Baccelli" 
mailto:emmanuel.bacce...@inria.fr>>:


Hi Thomas,
damn, your right, I misread the dates. So Hack'nAck would be
"sandwiched" inside the workshop, and I guess that's not great.
How about 28-29, or 29-30, then?
Best
Emmanuel

On Mon, Jan 19, 2015 at 11:24 AM, Thomas Eichinger
mailto:thomas.eichin...@fu-berlin.de>> wrote:

Hi,

I’d also like to attend. I’d prefer a date without H&A
in-between (as these tend to
end late at night, which would make it hard to start with NSTF
early again) but
wouldn’t object if there is a majority in favour of this.

Best, Thomas

> On 16 Jan 2015, at 19:08, Hauke Petersen
mailto:hauke.peter...@fu-berlin.de>> wrote:
>
> Dear RIOTers,
>
> we recently came up with the idea to create task forces
around special topics in RIOT to concentrate and speed up the
development of key parts. The idea is to bring all people that
are interested in this topic and are prepared to spend some on
it together in a (virtual) room and start out by a 2-3 day
workshop style event. This first period should be used to
discuss the topic in detail to bring everyone involved on the
same page, to come up with a clear architecture, and define
interfaces and sub-modules. The hope is, that we can go into a
very productive implementing phase afterward and speed up the
overall development.
>
> The first key topic we want to try out this concept is the
ongoing re-structuring of the network stack. I propose the
following plan for this:
> - we use next week to coordinate (who wants to join, what is
the current state, what are the most pressing open questions)
> - we block 2 days in the last week of January for a
(virtual) white-board centered workshop
>
> For the workshop I propose January 27-28, but its just a
proposal...
>
>
> Regarding technical aspects that are currently under (heavy)
construction or need to be clarified (@Martine: please hit me
if I have it completely wrong here...):
> - optimizations to the netdev interface
> - optimizations to the netapi interface
> - analysis of possible data loss using netapi in its current
state
> - how to pass data/headers/packets around the stack
> - possible generalization and/or quotas in the packet buffer
> - concepts of global protocol/module list and global
protocol handler registry
> - API definition for the neighbor table
> - API definition for the forwarding table
> - possible join for neighbor and forwarding table
> - hooks for various routing protocols
> - ???
>
> This is just a initial list of topics to be further
discussed - I hope we can detail it out over the next week to
have a good idea about the questions that need time for
discussion!
>
>
> So concluding:
> - who is interested (and/or) wiling to joing this effort?
> - are there any ideas on the concrete organization of such a
task-force?
> - are there technical aspects I forgot?
>
> Looking forward to your feedback!
>
> Cheers,
> Hauke
>
> ___
> 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
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
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Network Stack Task Force

2015-01-19 Thread Martine Lenders

Hi,
Since this thread has gained some traction now I would propose to use to
dudle it out. The two days adjacent to each other where most are available
would be the date: https://dudle.inf.tu-dresden.de/RIOT-NSFT1/

Cheers,
Martine
Am 19.01.2015 12:29 schrieb "Emmanuel Baccelli" :

> Hi Thomas,
> damn, your right, I misread the dates. So Hack'nAck would be "sandwiched"
> inside the workshop, and I guess that's not great. How about 28-29, or
> 29-30, then?
> Best
> Emmanuel
>
> On Mon, Jan 19, 2015 at 11:24 AM, Thomas Eichinger <
> thomas.eichin...@fu-berlin.de> wrote:
>
>> Hi,
>>
>> I’d also like to attend. I’d prefer a date without H&A in-between (as
>> these tend to
>> end late at night, which would make it hard to start with NSTF early
>> again) but
>> wouldn’t object if there is a majority in favour of this.
>>
>> Best, Thomas
>>
>> > On 16 Jan 2015, at 19:08, Hauke Petersen 
>> wrote:
>> >
>> > Dear RIOTers,
>> >
>> > we recently came up with the idea to create task forces around special
>> topics in RIOT to concentrate and speed up the development of key parts.
>> The idea is to bring all people that are interested in this topic and are
>> prepared to spend some on it together in a (virtual) room and start out by
>> a 2-3 day workshop style event. This first period should be used to discuss
>> the topic in detail to bring everyone involved on the same page, to come up
>> with a clear architecture, and define interfaces and sub-modules. The hope
>> is, that we can go into a very productive implementing phase afterward and
>> speed up the overall development.
>> >
>> > The first key topic we want to try out this concept is the ongoing
>> re-structuring of the network stack. I propose the following plan for this:
>> > - we use next week to coordinate (who wants to join, what is the
>> current state, what are the most pressing open questions)
>> > - we block 2 days in the last week of January for a (virtual)
>> white-board centered workshop
>> >
>> > For the workshop I propose January 27-28, but its just a proposal...
>> >
>> >
>> > Regarding technical aspects that are currently under (heavy)
>> construction or need to be clarified (@Martine: please hit me if I have it
>> completely wrong here...):
>> > - optimizations to the netdev interface
>> > - optimizations to the netapi interface
>> > - analysis of possible data loss using netapi in its current state
>> > - how to pass data/headers/packets around the stack
>> > - possible generalization and/or quotas in the packet buffer
>> > - concepts of global protocol/module list and global protocol handler
>> registry
>> > - API definition for the neighbor table
>> > - API definition for the forwarding table
>> > - possible join for neighbor and forwarding table
>> > - hooks for various routing protocols
>> > - ???
>> >
>> > This is just a initial list of topics to be further discussed - I hope
>> we can detail it out over the next week to have a good idea about the
>> questions that need time for discussion!
>> >
>> >
>> > So concluding:
>> > - who is interested (and/or) wiling to joing this effort?
>> > - are there any ideas on the concrete organization of such a task-force?
>> > - are there technical aspects I forgot?
>> >
>> > Looking forward to your feedback!
>> >
>> > Cheers,
>> > Hauke
>> >
>> > ___
>> > 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
> 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

Re: [riot-devel] Network Stack Task Force

2015-01-19 Thread Emmanuel Baccelli

Hi Thomas,
damn, your right, I misread the dates. So Hack'nAck would be "sandwiched"
inside the workshop, and I guess that's not great. How about 28-29, or
29-30, then?
Best
Emmanuel

On Mon, Jan 19, 2015 at 11:24 AM, Thomas Eichinger <
thomas.eichin...@fu-berlin.de> wrote:

> Hi,
>
> I’d also like to attend. I’d prefer a date without H&A in-between (as
> these tend to
> end late at night, which would make it hard to start with NSTF early
> again) but
> wouldn’t object if there is a majority in favour of this.
>
> Best, Thomas
>
> > On 16 Jan 2015, at 19:08, Hauke Petersen 
> wrote:
> >
> > Dear RIOTers,
> >
> > we recently came up with the idea to create task forces around special
> topics in RIOT to concentrate and speed up the development of key parts.
> The idea is to bring all people that are interested in this topic and are
> prepared to spend some on it together in a (virtual) room and start out by
> a 2-3 day workshop style event. This first period should be used to discuss
> the topic in detail to bring everyone involved on the same page, to come up
> with a clear architecture, and define interfaces and sub-modules. The hope
> is, that we can go into a very productive implementing phase afterward and
> speed up the overall development.
> >
> > The first key topic we want to try out this concept is the ongoing
> re-structuring of the network stack. I propose the following plan for this:
> > - we use next week to coordinate (who wants to join, what is the current
> state, what are the most pressing open questions)
> > - we block 2 days in the last week of January for a (virtual)
> white-board centered workshop
> >
> > For the workshop I propose January 27-28, but its just a proposal...
> >
> >
> > Regarding technical aspects that are currently under (heavy)
> construction or need to be clarified (@Martine: please hit me if I have it
> completely wrong here...):
> > - optimizations to the netdev interface
> > - optimizations to the netapi interface
> > - analysis of possible data loss using netapi in its current state
> > - how to pass data/headers/packets around the stack
> > - possible generalization and/or quotas in the packet buffer
> > - concepts of global protocol/module list and global protocol handler
> registry
> > - API definition for the neighbor table
> > - API definition for the forwarding table
> > - possible join for neighbor and forwarding table
> > - hooks for various routing protocols
> > - ???
> >
> > This is just a initial list of topics to be further discussed - I hope
> we can detail it out over the next week to have a good idea about the
> questions that need time for discussion!
> >
> >
> > So concluding:
> > - who is interested (and/or) wiling to joing this effort?
> > - are there any ideas on the concrete organization of such a task-force?
> > - are there technical aspects I forgot?
> >
> > Looking forward to your feedback!
> >
> > Cheers,
> > Hauke
> >
> > ___
> > 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
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Network Stack Task Force

2015-01-19 Thread Thomas Eichinger

Hi,

I’d also like to attend. I’d prefer a date without H&A in-between (as these 
tend to
end late at night, which would make it hard to start with NSTF early again) but
wouldn’t object if there is a majority in favour of this.

Best, Thomas

> On 16 Jan 2015, at 19:08, Hauke Petersen  wrote:
> 
> Dear RIOTers,
> 
> we recently came up with the idea to create task forces around special topics 
> in RIOT to concentrate and speed up the development of key parts. The idea is 
> to bring all people that are interested in this topic and are prepared to 
> spend some on it together in a (virtual) room and start out by a 2-3 day 
> workshop style event. This first period should be used to discuss the topic 
> in detail to bring everyone involved on the same page, to come up with a 
> clear architecture, and define interfaces and sub-modules. The hope is, that 
> we can go into a very productive implementing phase afterward and speed up 
> the overall development.
> 
> The first key topic we want to try out this concept is the ongoing 
> re-structuring of the network stack. I propose the following plan for this:
> - we use next week to coordinate (who wants to join, what is the current 
> state, what are the most pressing open questions)
> - we block 2 days in the last week of January for a (virtual) white-board 
> centered workshop
> 
> For the workshop I propose January 27-28, but its just a proposal...
> 
> 
> Regarding technical aspects that are currently under (heavy) construction or 
> need to be clarified (@Martine: please hit me if I have it completely wrong 
> here...):
> - optimizations to the netdev interface
> - optimizations to the netapi interface
> - analysis of possible data loss using netapi in its current state
> - how to pass data/headers/packets around the stack
> - possible generalization and/or quotas in the packet buffer
> - concepts of global protocol/module list and global protocol handler registry
> - API definition for the neighbor table
> - API definition for the forwarding table
> - possible join for neighbor and forwarding table
> - hooks for various routing protocols
> - ???
> 
> This is just a initial list of topics to be further discussed - I hope we can 
> detail it out over the next week to have a good idea about the questions that 
> need time for discussion!
> 
> 
> So concluding:
> - who is interested (and/or) wiling to joing this effort?
> - are there any ideas on the concrete organization of such a task-force?
> - are there technical aspects I forgot?
> 
> Looking forward to your feedback!
> 
> Cheers,
> Hauke
> 
> ___
> 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

Re: [riot-devel] Network Stack Task Force

2015-01-19 Thread Emmanuel Baccelli

Hi,
I would also like to attend. I'm also of the opinion that Hack'n'Ack should
be a separated event from this taskforce meeting.
However, maybe 1,5 days could be enough for the workshop, and this would
mean that 27th +28th until Hack'n'Ack starts could still fit?
Cheers,
Emmanuel

On Mon, Jan 19, 2015 at 8:35 AM, Peter Kietzmann <
peter.kietzm...@haw-hamburg.de> wrote:

> Hi,
>
> I would like to attend. I also prefer separate days for Hack'n'ACK and
> this date.
>
> Best,
> Peter
>
>
> Am 16.01.2015 um 19:08 schrieb Hauke Petersen:
>
>  Dear RIOTers,
>>
>> we recently came up with the idea to create task forces around special
>> topics in RIOT to concentrate and speed up the development of key parts.
>> The idea is to bring all people that are interested in this topic and are
>> prepared to spend some on it together in a (virtual) room and start out by
>> a 2-3 day workshop style event. This first period should be used to discuss
>> the topic in detail to bring everyone involved on the same page, to come up
>> with a clear architecture, and define interfaces and sub-modules. The hope
>> is, that we can go into a very productive implementing phase afterward and
>> speed up the overall development.
>>
>> The first key topic we want to try out this concept is the ongoing
>> re-structuring of the network stack. I propose the following plan for this:
>> - we use next week to coordinate (who wants to join, what is the current
>> state, what are the most pressing open questions)
>> - we block 2 days in the last week of January for a (virtual) white-board
>> centered workshop
>>
>> For the workshop I propose January 27-28, but its just a proposal...
>>
>>
>> Regarding technical aspects that are currently under (heavy) construction
>> or need to be clarified (@Martine: please hit me if I have it completely
>> wrong here...):
>> - optimizations to the netdev interface
>> - optimizations to the netapi interface
>> - analysis of possible data loss using netapi in its current state
>> - how to pass data/headers/packets around the stack
>> - possible generalization and/or quotas in the packet buffer
>> - concepts of global protocol/module list and global protocol handler
>> registry
>> - API definition for the neighbor table
>> - API definition for the forwarding table
>> - possible join for neighbor and forwarding table
>> - hooks for various routing protocols
>> - ???
>>
>> This is just a initial list of topics to be further discussed - I hope we
>> can detail it out over the next week to have a good idea about the
>> questions that need time for discussion!
>>
>>
>> So concluding:
>> - who is interested (and/or) wiling to joing this effort?
>> - are there any ideas on the concrete organization of such a task-force?
>> - are there technical aspects I forgot?
>>
>> Looking forward to your feedback!
>>
>> Cheers,
>> Hauke
>>
>> ___
>> devel mailing list
>> devel@riot-os.org
>> http://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
> http://lists.riot-os.org/mailman/listinfo/devel
>
___
devel mailing list
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Network Stack Task Force

2015-01-18 Thread Peter Kietzmann


Hi,

I would like to attend. I also prefer separate days for Hack'n'ACK and 
this date.


Best,
Peter


Am 16.01.2015 um 19:08 schrieb Hauke Petersen:

Dear RIOTers,

we recently came up with the idea to create task forces around special 
topics in RIOT to concentrate and speed up the development of key 
parts. The idea is to bring all people that are interested in this 
topic and are prepared to spend some on it together in a (virtual) 
room and start out by a 2-3 day workshop style event. This first 
period should be used to discuss the topic in detail to bring everyone 
involved on the same page, to come up with a clear architecture, and 
define interfaces and sub-modules. The hope is, that we can go into a 
very productive implementing phase afterward and speed up the overall 
development.


The first key topic we want to try out this concept is the ongoing 
re-structuring of the network stack. I propose the following plan for 
this:
- we use next week to coordinate (who wants to join, what is the 
current state, what are the most pressing open questions)
- we block 2 days in the last week of January for a (virtual) 
white-board centered workshop


For the workshop I propose January 27-28, but its just a proposal...


Regarding technical aspects that are currently under (heavy) 
construction or need to be clarified (@Martine: please hit me if I 
have it completely wrong here...):

- optimizations to the netdev interface
- optimizations to the netapi interface
- analysis of possible data loss using netapi in its current state
- how to pass data/headers/packets around the stack
- possible generalization and/or quotas in the packet buffer
- concepts of global protocol/module list and global protocol handler 
registry

- API definition for the neighbor table
- API definition for the forwarding table
- possible join for neighbor and forwarding table
- hooks for various routing protocols
- ???

This is just a initial list of topics to be further discussed - I hope 
we can detail it out over the next week to have a good idea about the 
questions that need time for discussion!



So concluding:
- who is interested (and/or) wiling to joing this effort?
- are there any ideas on the concrete organization of such a task-force?
- are there technical aspects I forgot?

Looking forward to your feedback!

Cheers,
Hauke

___
devel mailing list
devel@riot-os.org
http://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
http://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Network Stack Task Force

2015-01-18 Thread Martin


Hi,

I would also like to attend.

Best regards,
Martin

On 16.01.2015 19:08, Hauke Petersen wrote:

Dear RIOTers,

we recently came up with the idea to create task forces around special 
topics in RIOT to concentrate and speed up the development of key 
parts. The idea is to bring all people that are interested in this 
topic and are prepared to spend some on it together in a (virtual) 
room and start out by a 2-3 day workshop style event. This first 
period should be used to discuss the topic in detail to bring everyone 
involved on the same page, to come up with a clear architecture, and 
define interfaces and sub-modules. The hope is, that we can go into a 
very productive implementing phase afterward and speed up the overall 
development.


The first key topic we want to try out this concept is the ongoing 
re-structuring of the network stack. I propose the following plan for 
this:
- we use next week to coordinate (who wants to join, what is the 
current state, what are the most pressing open questions)
- we block 2 days in the last week of January for a (virtual) 
white-board centered workshop


For the workshop I propose January 27-28, but its just a proposal...


Regarding technical aspects that are currently under (heavy) 
construction or need to be clarified (@Martine: please hit me if I 
have it completely wrong here...):

- optimizations to the netdev interface
- optimizations to the netapi interface
- analysis of possible data loss using netapi in its current state
- how to pass data/headers/packets around the stack
- possible generalization and/or quotas in the packet buffer
- concepts of global protocol/module list and global protocol handler 
registry

- API definition for the neighbor table
- API definition for the forwarding table
- possible join for neighbor and forwarding table
- hooks for various routing protocols
- ???

This is just a initial list of topics to be further discussed - I hope 
we can detail it out over the next week to have a good idea about the 
questions that need time for discussion!



So concluding:
- who is interested (and/or) wiling to joing this effort?
- are there any ideas on the concrete organization of such a task-force?
- are there technical aspects I forgot?

Looking forward to your feedback!

Cheers,
Hauke

___
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

Re: [riot-devel] Network Stack Task Force

2015-01-18 Thread David Lyon


On 2015-01-17 18:02, Frank wrote:

Hello,


The esp8266's are quite interesting. I know this is LUA code but it 
shows how to control a GPIO on a web server on another module.



-- Send a Web Instruction to another module on keypress
count = 0
delay = 0
buttonstate = false
gpio.mode(4,gpio.INT)

function transmit_msg()
   sk=net.createConnection(net.TCP, 0)
   sk:on("receive", function(sck, c) print(c) end )
   sk:on("connection", function(sck)
   if buttonstate then
   sk:send("GET index.html/?pin=OFF HTTP/1.0")
   print("Off Sent")
   else
   sk:send("GET index.html/?pin=ON HTTP/1.0")
   print("On Sent")
   end
   buttonstate = not buttonstate
   end )
   sk:connect(80,"192.168.0.13")
   tmr.delay(100)
   end

function buttonpress(level)
   x = tmr.now()
   if x > delay then
  delay = tmr.now()+5
  count = count + 1
  print(".")
  transmit_msg()
  end
   end

gpio.trig(4, "down",buttonpress)

--

more details here: 
http://forum.makehackvoid.com/t/esp8266-workshop-january-21-attempting-useful-things/222/8


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

Re: [riot-devel] Network Stack Task Force

2015-01-16 Thread Frank

Hello,

i'm interested joining this task force. My time is very limited so i can
do only limited work on this.
> - are there technical aspects I forgot?
* Encryption of every data send
* Joining new noes into an encrypted network
* What about over the air firmware upgrade? This routine must be small
including minimum network functionality and signature checking.
* Frequency change/hopping
* Energy optimization for battery powered nodes

Regards,

Frank


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

Re: [riot-devel] Network Stack Task Force

2015-01-16 Thread Jan Wagner

Hi!
 
I also would like to join this virtual room. I don't have deep knowledge about
the riot network stack(s)... yet :)
 
hf
Jan
> Hauke Petersen  hat am 16. Januar 2015 um 19:08
> geschrieben:
>
>
> Dear RIOTers,
>
> we recently came up with the idea to create task forces around special
> topics in RIOT to concentrate and speed up the development of key parts.
> The idea is to bring all people that are interested in this topic and
> are prepared to spend some on it together in a (virtual) room and start
> out by a 2-3 day workshop style event. This first period should be used
> to discuss the topic in detail to bring everyone involved on the same
> page, to come up with a clear architecture, and define interfaces and
> sub-modules. The hope is, that we can go into a very productive
> implementing phase afterward and speed up the overall development.
>
> The first key topic we want to try out this concept is the ongoing
> re-structuring of the network stack. I propose the following plan for this:
> - we use next week to coordinate (who wants to join, what is the current
> state, what are the most pressing open questions)
> - we block 2 days in the last week of January for a (virtual)
> white-board centered workshop
>
> For the workshop I propose January 27-28, but its just a proposal...
>
>
> Regarding technical aspects that are currently under (heavy)
> construction or need to be clarified (@Martine: please hit me if I have
> it completely wrong here...):
> - optimizations to the netdev interface
> - optimizations to the netapi interface
> - analysis of possible data loss using netapi in its current state
> - how to pass data/headers/packets around the stack
> - possible generalization and/or quotas in the packet buffer
> - concepts of global protocol/module list and global protocol handler
> registry
> - API definition for the neighbor table
> - API definition for the forwarding table
> - possible join for neighbor and forwarding table
> - hooks for various routing protocols
> - ???
>
> This is just a initial list of topics to be further discussed - I hope
> we can detail it out over the next week to have a good idea about the
> questions that need time for discussion!
>
>
> So concluding:
> - who is interested (and/or) wiling to joing this effort?
> - are there any ideas on the concrete organization of such a task-force?
> - are there technical aspects I forgot?
>
> Looking forward to your feedback!
>
> Cheers,
> Hauke
>
> ___
> 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

Re: [riot-devel] Network Stack Task Force

2015-01-16 Thread Martine Lenders

Hi Oleg,

2015-01-16 20:27 GMT+01:00 Oleg Hahm :

> Hi Martine!
>
> > Making the packet buffer thread-safe as possible could also be a topic
>
> Isn't the packet buffer thread-safe? (And isn't this a core requirement for
> this module?)


I realized that #2285 might break that, due to the moving payload_data
pointer as the packet propagates upwards in the network stack. I already
proposed a sketched-up alternative there, that would prevent that. Also,
there is room for improvement, since the mutex is currently only
buffer-wise, not packet-wise and can thus lead to priority inversion.

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

Re: [riot-devel] Network Stack Task Force

2015-01-16 Thread Martine Lenders

Hi,

2015-01-16 20:04 GMT+01:00 Oleg Hahm :

> Hey!
>
> > >>For the workshop I propose January 27-28, but its just a proposal...
> > >Keep in mind, that the next H&A is scheduled for January 27.
> > Of course I did not. :-) But I think thats a perfect fit!
>
> I'm not so convinced about that. To my understanding the H&A is mostly
> about
> speeding up the merge of existing code into RIOT, the task force is about
> concepts and designs. I think it would either decrease productivity of the
> H&A
> event by to many people discussing (instead of reviewing and hacking), or
> set
> an early deadline for the task force event on the first day. Also, if we
> start
> heavy brainstorming and discussing about the network stack in the morning,
> I'm
> pretty sure that my mind won't be very fresh for the H&A.
>

I think similar (and know me well enough to expect it), as Oleg does. I
would propose to just doodle it out for the span of the days after the H&A
and the week after.

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

Re: [riot-devel] Network Stack Task Force

2015-01-16 Thread Oleg Hahm

Hi!

> Is it going to be in cbase or somewhere else?

It's gonna be C-Base again.

Cheers,
Oleg
-- 
The best thing about Appletalk is that nobody is using it any more.


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

Re: [riot-devel] Network Stack Task Force

2015-01-16 Thread Oleg Hahm

Hi Martine!

> Making the packet buffer thread-safe as possible could also be a topic

Isn't the packet buffer thread-safe? (And isn't this a core requirement for
this module?)

Cheers,
Oleg
-- 
The best part about IPv6 jokes is that you don't have to make up the punchline
for 15 years.


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

Re: [riot-devel] Network Stack Task Force

2015-01-16 Thread Christian Mehlis


Am 16.01.2015 um 19:46 schrieb Oleg Hahm:

Hey Hauke!


For the workshop I propose January 27-28, but its just a proposal...


Keep in mind, that the next H&A is scheduled for January 27.


that's great, I take this day off work, can be there at any time...

Is it going to be in cbase or somewhere else?

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

Re: [riot-devel] Network Stack Task Force

2015-01-16 Thread Oleg Hahm

Hey!

> >>For the workshop I propose January 27-28, but its just a proposal...
> >Keep in mind, that the next H&A is scheduled for January 27.
> Of course I did not. :-) But I think thats a perfect fit!

I'm not so convinced about that. To my understanding the H&A is mostly about
speeding up the merge of existing code into RIOT, the task force is about
concepts and designs. I think it would either decrease productivity of the H&A
event by to many people discussing (instead of reviewing and hacking), or set
an early deadline for the task force event on the first day. Also, if we start
heavy brainstorming and discussing about the network stack in the morning, I'm
pretty sure that my mind won't be very fresh for the H&A.

Cheers,
Oleg
-- 
panic ("No CPUs found.  System halted.\n");
linux-2.4.3/arch/parisc/kernel/setup.c


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

Re: [riot-devel] Network Stack Task Force

2015-01-16 Thread Oleg Hahm

Hi!

> - who is interested (and/or) wiling to joing this effort?

Count me in.

> - are there any ideas on the concrete organization of such a task-force?

I think this depends on the size and distribution of the group.

> - are there technical aspects I forgot?

Did one of your proposed aspects already cover dead lock avoidance and
priority inversion?

Cheers,
Oleg
-- 
I'm working on a bittorrent joke, but I only have about 30% and nobody's
seeding!


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

Re: [riot-devel] Network Stack Task Force

2015-01-16 Thread Hauke Petersen


Hi,

On 16.01.2015 19:46, Oleg Hahm wrote:

Hey Hauke!


For the workshop I propose January 27-28, but its just a proposal...

Keep in mind, that the next H&A is scheduled for January 27.

Of course I did not. :-) But I think thats a perfect fit!

Cheers,
Hauke




Cheers,
Oleg


___
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

Re: [riot-devel] Network Stack Task Force

2015-01-16 Thread Lotte Steenbrink

Hi,

Am 16.01.2015 um 19:08 schrieb Hauke Petersen :

> Dear RIOTers,
> 
> we recently came up with the idea to create task forces around special topics 
> in RIOT to concentrate and speed up the development of key parts. The idea is 
> to bring all people that are interested in this topic and are prepared to 
> spend some on it together in a (virtual) room and start out by a 2-3 day 
> workshop style event. This first period should be used to discuss the topic 
> in detail to bring everyone involved on the same page, to come up with a 
> clear architecture, and define interfaces and sub-modules. The hope is, that 
> we can go into a very productive implementing phase afterward and speed up 
> the overall development.
> 
> The first key topic we want to try out this concept is the ongoing 
> re-structuring of the network stack. I propose the following plan for this:
> - we use next week to coordinate (who wants to join, what is the current 
> state, what are the most pressing open questions)
> - we block 2 days in the last week of January for a (virtual) white-board 
> centered workshop
> 
> For the workshop I propose January 27-28, but its just a proposal...
> 
> 
> Regarding technical aspects that are currently under (heavy) construction or 
> need to be clarified (@Martine: please hit me if I have it completely wrong 
> here...):
> - optimizations to the netdev interface
> - optimizations to the netapi interface
> - analysis of possible data loss using netapi in its current state
> - how to pass data/headers/packets around the stack
> - possible generalization and/or quotas in the packet buffer
> - concepts of global protocol/module list and global protocol handler registry
> - API definition for the neighbor table
> - API definition for the forwarding table
> - possible join for neighbor and forwarding table
> - hooks for various routing protocols
> - ???
> 
> This is just a initial list of topics to be further discussed - I hope we can 
> detail it out over the next week to have a good idea about the questions that 
> need time for discussion!
> 
> 
> So concluding:
> - who is interested (and/or) wiling to joing this effort?

I don't want to impose, but I'd love to attend!
Unfortunately, my last exam is on the 29th of january. :( But in case you 
decide to meet after that, count me in, if that's okay.

Cheers,
Lotte

> - are there any ideas on the concrete organization of such a task-force?
> - are there technical aspects I forgot?
> 
> Looking forward to your feedback!
> 
> Cheers,
> Hauke
> 
> ___
> 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

Re: [riot-devel] Network Stack Task Force

2015-01-16 Thread Oleg Hahm

Hey Hauke!

> For the workshop I propose January 27-28, but its just a proposal...

Keep in mind, that the next H&A is scheduled for January 27.

Cheers,
Oleg
-- 
The bad thing about Kerberos jokes is that I can't tell them to you because I
don't trust you and I don't know your name!


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

Re: [riot-devel] Network Stack Task Force

2015-01-16 Thread Martine Lenders

I'm of course on board.

2015-01-16 19:08 GMT+01:00 Hauke Petersen :

> Dear RIOTers,
>
> we recently came up with the idea to create task forces around special
> topics in RIOT to concentrate and speed up the development of key parts.
> The idea is to bring all people that are interested in this topic and are
> prepared to spend some on it together in a (virtual) room and start out by
> a 2-3 day workshop style event. This first period should be used to discuss
> the topic in detail to bring everyone involved on the same page, to come up
> with a clear architecture, and define interfaces and sub-modules. The hope
> is, that we can go into a very productive implementing phase afterward and
> speed up the overall development.
>
> The first key topic we want to try out this concept is the ongoing
> re-structuring of the network stack. I propose the following plan for this:
> - we use next week to coordinate (who wants to join, what is the current
> state, what are the most pressing open questions)
> - we block 2 days in the last week of January for a (virtual) white-board
> centered workshop
>
> For the workshop I propose January 27-28, but its just a proposal...
>
>
> Regarding technical aspects that are currently under (heavy) construction
> or need to be clarified (@Martine: please hit me if I have it completely
> wrong here...):
> - optimizations to the netdev interface
> - optimizations to the netapi interface
> - analysis of possible data loss using netapi in its current state
> - how to pass data/headers/packets around the stack
> - possible generalization and/or quotas in the packet buffer
> - concepts of global protocol/module list and global protocol handler
> registry
> - API definition for the neighbor table
> - API definition for the forwarding table
> - possible join for neighbor and forwarding table
> - hooks for various routing protocols
> - ???
>

Making the packet buffer thread-safe as possible could also be a topic


>
> This is just a initial list of topics to be further discussed - I hope we
> can detail it out over the next week to have a good idea about the
> questions that need time for discussion!
>
>
> So concluding:
> - who is interested (and/or) wiling to joing this effort?
> - are there any ideas on the concrete organization of such a task-force?
> - are there technical aspects I forgot?
>
> Looking forward to your feedback!
>
> Cheers,
> Hauke
>
> ___
> 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

[riot-devel] Network Stack Task Force

2015-01-16 Thread Hauke Petersen


Dear RIOTers,

we recently came up with the idea to create task forces around special 
topics in RIOT to concentrate and speed up the development of key parts. 
The idea is to bring all people that are interested in this topic and 
are prepared to spend some on it together in a (virtual) room and start 
out by a 2-3 day workshop style event. This first period should be used 
to discuss the topic in detail to bring everyone involved on the same 
page, to come up with a clear architecture, and define interfaces and 
sub-modules. The hope is, that we can go into a very productive 
implementing phase afterward and speed up the overall development.


The first key topic we want to try out this concept is the ongoing 
re-structuring of the network stack. I propose the following plan for this:
- we use next week to coordinate (who wants to join, what is the current 
state, what are the most pressing open questions)
- we block 2 days in the last week of January for a (virtual) 
white-board centered workshop


For the workshop I propose January 27-28, but its just a proposal...


Regarding technical aspects that are currently under (heavy) 
construction or need to be clarified (@Martine: please hit me if I have 
it completely wrong here...):

- optimizations to the netdev interface
- optimizations to the netapi interface
- analysis of possible data loss using netapi in its current state
- how to pass data/headers/packets around the stack
- possible generalization and/or quotas in the packet buffer
- concepts of global protocol/module list and global protocol handler 
registry

- API definition for the neighbor table
- API definition for the forwarding table
- possible join for neighbor and forwarding table
- hooks for various routing protocols
- ???

This is just a initial list of topics to be further discussed - I hope 
we can detail it out over the next week to have a good idea about the 
questions that need time for discussion!



So concluding:
- who is interested (and/or) wiling to joing this effort?
- are there any ideas on the concrete organization of such a task-force?
- are there technical aspects I forgot?

Looking forward to your feedback!

Cheers,
Hauke

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

42 matches

Mail list logo