[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1392858138.22693.21.camel@dcbw.local>
Date: Wed, 19 Feb 2014 19:02:18 -0600
From: Dan Williams <dcbw@...hat.com>
To: Hannes Frederic Sowa <hannes@...essinduktion.org>
Cc: "Luis R. Rodriguez" <mcgrof@...not-panic.com>,
Zoltan Kiss <zoltan.kiss@...rix.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
xen-devel@...ts.xenproject.org, kvm@...r.kernel.org,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"David S. Miller" <davem@...emloft.net>,
Alexey Kuznetsov <kuznet@....inr.ac.ru>,
James Morris <jmorris@...ei.org>,
Hideaki YOSHIFUJI <yoshfuji@...ux-ipv6.org>,
Patrick McHardy <kaber@...sh.net>
Subject: Re: [RFC v2 2/4] net: enables interface option to skip IP
On Thu, 2014-02-20 at 01:58 +0100, Hannes Frederic Sowa wrote:
> On Wed, Feb 19, 2014 at 06:56:17PM -0600, Dan Williams wrote:
> > Note that there isn't yet a disable_ipv4 knob though, I was
> > perhaps-too-subtly trying to get you to send a patch for it, since I can
> > use it too :)
>
> Do you plan to implement
> <http://datatracker.ietf.org/doc/draft-ietf-sunset4-noipv4/>?
>
> ;)
Well, not specifically, but with NetworkManager we do have a "disable
IPv4" method for IPv4, which now just doesn't do any kind of IPv4, but
obviously doesn't disable IPv4 entirely because that's not possible. I
was only thinking that it would be nice to actually guarantee that IPv4
was disabled, just like disable_ipv6 does.
But we could certainly implement that draft if a patch shows up or if it
bubbled up the priority stack :)
Dan
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists