> > > > > > The 802.15.4 mac layer has some neighbor discovery issues which are not > > > solved currently. It's about two kinds of mac addresses, for bluetooth > > > it should be fine. A small description about this problem is here [1]. > > > > > > We need some way to trigger 6LoWPAN/Layer 2 data across the IPv6 layer > > > and this isn't easy. Everything what we do on runtime decisions makes > > > the IPv6 stack slower and we should avoid that. > > > > Yep, agreed. > > > > That's the big challenge to make an acceptable mainline solution. :-) > > At the end it should be acked by IPv6 community, they should scream if a > solution makes runtime decisions which slower down the stack too much. > btw. I need L2 data in the neighbor discovery cache to handle the "two kinds mac addresses". I will try to find a way after the rework of the mac layer. This was discussed at [0]. - Alex [0] http://marc.info/?l=linux-netdev&m=140724093516806&w=2 -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
