From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alexander Aring Subject: Re: Question about IPv6 neighbor discovery and 6lowpan Date: Thu, 21 Nov 2013 17:13:11 +0100 Message-ID: <20131121161310.GA10513@omega> References: <1385046178.2723.17.camel@jrissane-mobl.ger.corp.intel.com> <20131121153414.GA9960@omega> <1385049135.2723.25.camel@jrissane-mobl.ger.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Cc: David Miller , netdev@vger.kernel.org To: Jukka Rissanen Return-path: Received: from mail-wi0-f170.google.com ([209.85.212.170]:59652 "EHLO mail-wi0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752124Ab3KUQNX (ORCPT ); Thu, 21 Nov 2013 11:13:23 -0500 Received: by mail-wi0-f170.google.com with SMTP id f4so318682wiw.3 for ; Thu, 21 Nov 2013 08:13:22 -0800 (PST) Content-Disposition: inline In-Reply-To: <1385049135.2723.25.camel@jrissane-mobl.ger.corp.intel.com> Sender: netdev-owner@vger.kernel.org List-ID: Hi Jukka, On Thu, Nov 21, 2013 at 05:52:15PM +0200, Jukka Rissanen wrote: > On to, 2013-11-21 at 16:34 +0100, Alexander Aring wrote: > > Hi Jukka, > > > > On Thu, Nov 21, 2013 at 05:02:58PM +0200, Jukka Rissanen wrote: > > > Hi, > > > > > > I am investigating RFC 6775 (Neighbor Discovery Optimization for IPv6 > > > over Low-Power Wireless Personal Area Networks (6LoWPANs)) > > > http://tools.ietf.org/html/rfc6775 > > > > > > The RFC suggests some changes to neighbor discovery procedure for the > > > 6LoWPAN networks. I was looking net/ipv6/ndisc.c and it seems that > > > ARPHRD type (from type field in net_device struct) is the only way to > > > detect and change the discovery procedure in the ndisc.c code. Am I > > > right with this assumption here? > > > > > I think you are right, there was some patches on linux-zigbee-devel who > > use exact the same idea to check the ARPHRD type. > > Ok. The reason I was interested in about this is that I proposed new > ARPHRD_RAWIP earlier that I could use in BT LE 6lowpan code. Now I think > that type might be too generic and perhaps I should have ARPHRD_6LOWPAN > or even ARPHRD_BT_6LOWPAN. > > > > > But I am investigating for rfc6775, too. :-) > > > > > > At the moment I see too many unsolved issues in the ieee802154/6lowpan > > implementation which should be fixed at first. :( > > > > - Alex > > No worries, the rfc6775 is common for both zigbee and bluetooth so > whoever implements the rfc gets support for both of them at the same > time. > Yea, I did not begin yet and you are welcome to implement it. :-) - Alex