From: Alexander Aring <aahringo@redhat.com>
To: Stefan Schmidt <stefan@datenfreihafen.org>
Cc: linux-wpan - ML <linux-wpan@vger.kernel.org>,
linux-bluetooth@vger.kernel.org,
Network Development <netdev@vger.kernel.org>
Subject: Re: 6lowpan netlink
Date: Thu, 16 Jun 2022 09:00:08 -0400 [thread overview]
Message-ID: <CAK-6q+h7497czku9rf9E4E=up5k5gm_NT0agPU2bUZr4ADKioQ@mail.gmail.com> (raw)
In-Reply-To: <e3efe652-eb22-4a3f-a121-be858fe2696b@datenfreihafen.org>
Hi,
On Thu, Jun 16, 2022 at 3:57 AM Stefan Schmidt
<stefan@datenfreihafen.org> wrote:
>
> Hello Alex.
>
> On 13.06.22 05:44, Alexander Aring wrote:
> > Hi all,
> >
> > I want to spread around that I started to work on some overdue
> > implementation, a netlink 6lowpan configuration interface, because
> > rtnetlink is not enough... it's for configuring very specific 6lowpan
> > device settings.
>
> Great, looking forward to it!
I would like to trigger a discussion about rtnetlink or generic. I can
put a nested rtnetlink for some device specific settings but then the
whole iproute2 (as it's currently is) would maintain a specific
6lowpan setting which maybe the user never wants...
I think we should follow this way when there is a strict ipv6 device
specific setting e.g. l2 neighbor information in ipv6 ndisc.
- Alex
next prev parent reply other threads:[~2022-06-16 13:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 3:44 6lowpan netlink Alexander Aring
2022-06-16 7:57 ` Stefan Schmidt
2022-06-16 13:00 ` Alexander Aring [this message]
2022-06-16 16:34 ` Jakub Kicinski
2022-06-27 2:31 ` Alexander Aring
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='CAK-6q+h7497czku9rf9E4E=up5k5gm_NT0agPU2bUZr4ADKioQ@mail.gmail.com' \
--to=aahringo@redhat.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-wpan@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stefan@datenfreihafen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.