From: David Woodhouse <dwmw2@infradead.org>
To: Pierre Ossman <pierre-list@ossman.eu>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
"Pekka Savola (ipv6)" <pekkas@netcore.fi>,
James Morris <jmorris@namei.org>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
Patrick McHardy <kaber@trash.net>
Subject: Re: [RFC][PATCH] Export DNSSL RA option to userspace
Date: Tue, 14 Dec 2010 13:10:15 +0000 [thread overview]
Message-ID: <1292332218.15586.49.camel@i7.infradead.org> (raw)
In-Reply-To: <20101212144300.68e0fb16@mjolnir.ossman.eu>
On Sun, 2010-12-12 at 14:43 +0100, Pierre Ossman wrote:
> RFC 6106 specifies a new RA option for DNS resolver configuration that
> therefore needs to end up in userspace.
>
> This first patch just exports the new option, but I started thinking
> that this seems overly complex that the kernel needs to be updated
> every time there is something new of interest to userspace in the RA.
> So I also have a second patch that exports everything that the kernel
> doesn't want.
>
> Patches only compile tested so far as I'm still hacking away at
> userspace. Comments very much welcome though.
Totally untested userspace support:
http://git.infradead.org/users/dwmw2/connman.git
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@intel.com Intel Corporation
next prev parent reply other threads:[~2010-12-14 13:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-12 13:43 [RFC][PATCH] Export DNSSL RA option to userspace Pierre Ossman
2010-12-12 13:47 ` [RFC][PATCH] Export all RA options that we don't handle " Pierre Ossman
2011-01-20 8:15 ` Pierre Ossman
2011-11-20 14:00 ` Pierre Ossman
2011-11-20 16:29 ` David Miller
2011-03-03 1:30 ` Pierre Ynard
2010-12-12 14:07 ` [RFC][PATCH] Export DNSSL RA option " Pierre Ossman
2011-03-03 1:36 ` Pierre Ynard
2010-12-14 13:10 ` David Woodhouse [this message]
2010-12-14 13:43 ` Pierre Ossman
2010-12-16 1:18 ` Dan Williams
2011-03-03 1:27 ` Pierre Ynard
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=1292332218.15586.49.camel@i7.infradead.org \
--to=dwmw2@infradead.org \
--cc=davem@davemloft.net \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@vger.kernel.org \
--cc=pekkas@netcore.fi \
--cc=pierre-list@ossman.eu \
--cc=yoshfuji@linux-ipv6.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).