From: Alexander Aring <alex.aring@gmail.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Jukka Rissanen <jukka.rissanen@linux.intel.com>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org
Subject: Re: Question about IPv6 neighbor discovery and 6lowpan
Date: Fri, 22 Nov 2013 06:30:16 +0100 [thread overview]
Message-ID: <20131122053015.GA14675@omega> (raw)
In-Reply-To: <692AEC23-372B-48A9-BEA7-02C2F6C13A47@holtmann.org>
On Fri, Nov 22, 2013 at 10:29:06AM +0700, Marcel Holtmann wrote:
> Hi Jukka,
>
> >>> 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.
>
> if it can be shared between 802.15.4 and Bluetooth, then I would propose to use ARPHRD_6LOWPAN and also convert the 802.15.4 stack to use that one.
>
Yea, that would be great. :-)
- Alex
prev parent reply other threads:[~2013-11-22 5:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 15:02 Question about IPv6 neighbor discovery and 6lowpan Jukka Rissanen
2013-11-21 15:34 ` Alexander Aring
2013-11-21 15:52 ` Jukka Rissanen
2013-11-21 16:13 ` Alexander Aring
2013-11-22 3:29 ` Marcel Holtmann
2013-11-22 5:30 ` Alexander Aring [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131122053015.GA14675@omega \
--to=alex.aring@gmail.com \
--cc=davem@davemloft.net \
--cc=jukka.rissanen@linux.intel.com \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).