Network stack refactoring: TODO list

[miri64]

Next steps (as result from the network stack task force meeting):

All new modules are to be prepended with the prefix ng_.

• define protocol types (@authmillenon) [merged -> nettype: intial import #2397]
• implement packet abstraction (@authmillenon) [merged -> pkt: simplify API #2342]
• define configuration types (@haukepetersen) [merged -> ng_net: add global configuration options #2399]
• define netdev interface (@haukepetersen) [merged -> net: add ng version of the netdev interface #2398]
• define netapi interface (@haukepetersen) [merged -> ng_net: add new version of NETAPI #2400]
• implement packet buffer (@authmillenon) [merged -> pktbuf: port to use pkt_t instead of void* #2285]
• define and implement netreg (@authmillenon) [merged -> netreg: Initial import #2404]
• define a generic link layer header (@haukepetersen) [merged -> net: added generic network interface header format #2449]
• adjust nomac MAC layer (@haukepetersen) [merged -> net: added ng_nomac MAC implementation #2426]
• remodel at86rf2xx driver (@haukepetersen) [merged -> drivers: new driver for at86rf2xx radios #2825]
• adjust nativenet to netdev (@authmillenon) [under review -> ng_tapnet: initial import of a pure Ethernet device for native #2558] (@kaspar030) [merged -> sys: net: introduce low-level ethernet driver API #2766]
• adjust netdev dummy (@haukepetersen) [postponed]
• add network interface module (@authmillenon) [merged -> netif: Initial import of ng_* version #2417]
• get IPv6 to run (@authmillenon) [merged -> ng_ipv6: initial import #2454]:
  • Address architecture [merged -> ng_ipv6_addr: initial import #2433]
  • IPv6 Interfaces [merged -> ng_ipv6: provide support for ng_netif #2437]
  • neighbor cache [merged -> net: initial import of an IPv6 neighbor cache #2461]
  • extension headers [merged -> ng_ipv6_ext: initial import of extension header handling (including RPL SRH) #2898]
• reimplement ICMPv6 (@authmillenon) [under review -> ng_icmpv6: Initial import #2555]
• get NDP to run (@authmillenon)
  • Address resolution [merged -> ng_ndp: initial import of address resolution #2910]
  • Router discovery [WIP -> [WIP] ng_ndp: Initial import of router discovery #2612] [merged -> gnrc_ndp_router: Initial import of router behavior of router discovery #3049]
• reimplement 6LoWPAN as seperate module (@authmillenon)
  • raw IPv6 [merged -> ng_sixlowpan: initial import #2614]
  • fragmentation [merged -> ng_sixlowpan: Initial import of datagram fragmentation #2781]
  • IPHC [merged -> ng_sixlowpan: Initial import of IP header compression #2806]
  • NHC
  • NDP optimization [merged -> gnrc_sixlowpan_nd_border_router: initial import of border router behavior of 6LoWPAN-ND #3134]
• define and implement FIB (@BytesGalore) [merged -> sys/net/network_layer added a core implementation of a FIB  #2211]
• adjust RPL to new FIB (@BytesGalore) [under review -> routing/rpl: adjusted RPL to use the FIB #2765] [this was for the old RPL implementation]
• reimplement RPL (@cgundogan) [under review -> ng_rpl: port to the new network stack #3050]
• adjust AODV to new FIB (@Lotterleben) [under review -> aodvv2: port to new network stack #3445]
• reimplement UDP (@haukepetersen) [merged -> net: added ng_udp implementation #2430]
• reimplement TCP (@brummer-simon) [under review -> [WIP]gnrc_tcp #2827]
• add shell commands for new API (@haukepetersen) [merged -> sys/shell: added (ng_)netif shell commands #2525]

Open topics

• adjust CC2420 radio
• adjust CC1100 radio
• ICMPv6 error messages [under review -> gnrc_icmpv6_error: initial import #3184]
• Redirect behavior of NDP
• reimplement sockets [merged -> posix: redo socket API to use conn #3646]

[miri64]

@OlegHahm can we please use the Network Stack Task Force Milestone only for PR's that are explicitly mentioned in this list? Otherwise we risk getting people easily confused.

[miri64]

The last critical component was merged. From now on it's Happy Hacking!

[OlegHahm]

@OlegHahm can we please use the Network Stack Task Force Milestone only for PR's that are explicitly mentioned in this list? Otherwise we risk getting people easily confused.

Ah, haven't seen this before. Will do.

[miri64]

@OlegHahm can we please use the Network Stack Task Force Milestone only for PR's that are explicitly mentioned in this list? Otherwise we risk getting people easily confused.

Just a little update on my rational for assigning the milestone: PR's or features that are explicitly mentioned here and any fix- or follow-up to those.

[miri64]

Updated list.

[miri64]

Though there are still some things under construction, since PRs exist I would deem this issue as complete, so close.