[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHaKRvKFwXSucvyrZVqxAZ8sa9tNBofPtJUK4hMRavTcZK9JZw@mail.gmail.com>
Date: Tue, 25 Feb 2014 11:50:38 -0800
From: Paul Marks <pmarks@...gle.com>
To: David Miller <davem@...emloft.net>
Cc: ben@...adent.org.uk, 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 Mon, Feb 24, 2014 at 4:12 PM, David Miller <davem@...emloft.net> 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?
The primary purpose of IPv6 is to bloat up network headers, because
the IPv4 headers were too small to address all the endpoints.
NAT64 is an intriguing solution to the problem of "I have too many
customers for 10.0.0.0/8". Here's are some slides on the topic from
this week's APNIC conference:
https://conference.apnic.net/data/37/464xlat-apricot-2014_1393236641.pdf
A kernel with disable_ipv4 would be fairly usable on such a network
today, as long as you avoid AF_INET-specific apps.
--
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