search

RIOT-OS / RIOT

RIOT - The friendly OS for IoT
https://riot-os.org
GNU Lesser General Public License v2.1
4.91k stars 1.98k forks source link

RFC: Divide sixlowpan into more than just ipv6 and sixlowpan #1655

Closed miri64 closed 9 years ago

miri64 commented 10 years ago

Deviding sixlowpan into 2 seperate modules makes sense from an architectural standpoint. But additionally regarding space constraints I wonder if it would be even more plausible to devide them further up with a dependency graph as follows (in git-log --graph like syntax ;-)):

* ipv6                   # core IPv6 functionality (without the stuff routers do)
|\ 
| * sixlowpan            # core 6LoWPAN functionality (without the 6LR-ND and 6LBR-ND part)
* | ipv6_router          # IPv6 router functionalities
|\ 
* | sixlowpan_router     # 6LR-ND
* | sixlowpan_border     # 6LBR-ND
  * rpl, olsr2, aodv2, …

I guess this way we can save a lot of space (no forwarding table, neighbor cache size == 1, less code) and overhead in general in the network stack.

miri64 commented 10 years ago

Never the less, for process' sake I would first make the sixlowpan/ipv6 split and continue from there.

OlegHahm commented 10 years ago

Sounds quite sensible to me.

OlegHahm commented 9 years ago

Fixed in gnrc.