[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140225022310.GH6598@order.stressinduktion.org>
Date: Tue, 25 Feb 2014 03:23:10 +0100
From: Hannes Frederic Sowa <hannes@...essinduktion.org>
To: Ben Hutchings <ben@...adent.org.uk>
Cc: David Miller <davem@...emloft.net>, dcbw@...hat.com,
mcgrof@...not-panic.com, zoltan.kiss@...rix.com,
netdev@...r.kernel.org, xen-devel@...ts.xenproject.org,
kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
kuznet@....inr.ac.ru, jmorris@...ei.org, yoshfuji@...ux-ipv6.org,
kaber@...sh.net
Subject: Re: [RFC v2 2/4] net: enables interface option to skip IP
On Tue, Feb 25, 2014 at 02:01:59AM +0000, Ben Hutchings wrote:
> On Mon, 2014-02-24 at 19:12 -0500, David Miller wrote:
> > From: Ben Hutchings <ben@...adent.org.uk>
> > Date: Tue, 25 Feb 2014 00:02:00 +0000
> >
> > > You can run an internal network, or access network, as v6-only with
> > > NAT64 and DNS64 at the border. I believe some mobile networks are doing
> > > this; it was also done on the main FOSDEM wireless network this year.
> >
> > This seems to be bloating up the networking headers of the internal
> > network, for what purpose?
> >
> > For mobile that's doubly inadvisable.
>
> I don't know what the reasoning is for the mobile network operators.
> They're forced to do NAT for v4 somewhere, and maybe v6-only makes the
> access network easier to manage.
Yes, it seems the way to go:
<http://www.dslreports.com/shownews/TMobile-Goes-IPv6-Only-on-Android-44-Devices-126506>
I can't comment on the 464xlat that much because I haven't looked at an
implementation yet, but it can very well be the case it still needs IPv4
on the outgoing interface, I don't know (from the spec pov it doesn't
look like that).
Greetings,
Hannes
--
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