From: "Walter Dnes" <waltdnes@waltdnes.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [Bulk] Re: [gentoo-user] /etc/hosts include file?
Date: Mon, 11 Mar 2013 18:45:49 -0400 [thread overview]
Message-ID: <20130311224549.GA30808@waltdnes.org> (raw)
In-Reply-To: <513D944F.4090401@gmail.com>
On Mon, Mar 11, 2013 at 10:22:39AM +0200, Alan McKinnon wrote
> You are being over-simplistic.
>
> Lack of IPv4 address space *caused* NAT to happen, the two are
> inextricably intertwined.
Agreed. But we shouldn't be pointing out that NAT has partially solved
the problem, and giving people false hope that NAT will solve the
shortage problem forever. We should be pounding away on the fact that
we're running out of IP addresses... period... end of story. If people
ask about NAT, then mention that the undersupply will be so bad that
even NAT won't help.
> Even worse, people now have NAT conflated with all sorts of other
> things. Like for example NAT and security.
That's why I wwant to avoid that propaganda battle. It's been lost
already. Deal with it. Don't waste time and effort on it. Put your
effort into pounding away on a simple issue that people do understand...
we're running out of IP addresses.
> NAT is the context of an IPv6 discussion is *very* relevant, it's
> one of the points you have to raise to illustrate what bits inside
> people's heads needs to be identified and changed.
>
> Until you change the content of people's heads, IPv6 is just not
> going to happen.
I disagree with you there. IPV6 adoption will be driven by shortage
of addresses, which people can understand. It will not be accomplished
by sermons about the evils of NAT whilst people's eyes glaze over.
"A preachment, dear friends, you are about to receive, is on John
Barleycorn, Nicotine, and the Temptations of NAT".
And if it comes down to it, I'd much rather have IPV6 with IPV6 NAT
being available, rather than no IPV6.
--
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications
next prev parent reply other threads:[~2013-03-11 22:46 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 22:24 [gentoo-user] /etc/hosts include file? Alan McKinnon
2013-03-07 23:50 ` Michael Mol
2013-03-08 0:29 ` Michael Mol
2013-03-08 8:32 ` Alan McKinnon
2013-03-08 13:40 ` Michael Mol
2013-03-08 13:54 ` Alan McKinnon
2013-03-08 19:50 ` [Bulk] " Kevin Chadwick
2013-03-08 19:55 ` Michael Mol
2013-03-08 21:49 ` Kevin Chadwick
2013-03-08 22:36 ` Pandu Poluan
2013-03-09 0:50 ` Kevin Chadwick
2013-03-09 3:27 ` Michael Mol
2013-03-09 12:53 ` Kevin Chadwick
2013-03-10 21:28 ` Michael Mol
2013-03-11 23:09 ` Kevin Chadwick
2013-03-12 5:05 ` Michael Mol
2013-03-09 0:13 ` Walter Dnes
2013-03-09 0:41 ` Michael Mol
2013-03-10 1:42 ` Walter Dnes
2013-03-10 4:59 ` Michael Orlitzky
2013-03-10 21:09 ` Michael Mol
2013-03-10 5:19 ` Alan McKinnon
2013-03-10 21:07 ` Michael Mol
2013-03-10 21:43 ` Alan McKinnon
2013-03-10 22:02 ` Michael Mol
2013-03-11 4:00 ` Walter Dnes
2013-03-11 4:37 ` Michael Mol
2013-03-11 8:22 ` Alan McKinnon
2013-03-11 22:45 ` Walter Dnes [this message]
2013-03-11 23:39 ` Kevin Chadwick
2013-03-12 3:58 ` Walter Dnes
2013-03-12 0:25 ` Alan McKinnon
2013-03-12 2:02 ` Michael Mol
2013-03-12 11:29 ` Alan McKinnon
2013-03-13 0:26 ` [Bulk] " Kevin Chadwick
2013-03-11 23:31 ` Kevin Chadwick
2013-03-12 0:37 ` Alan McKinnon
2013-03-09 0:45 ` Kevin Chadwick
2013-03-09 3:21 ` Michael Mol
2013-03-09 12:53 ` Kevin Chadwick
2013-03-10 22:00 ` Michael Mol
2013-03-11 1:56 ` Michael Orlitzky
2013-03-11 2:33 ` Michael Mol
2013-03-11 22:34 ` Kevin Chadwick
2013-03-12 3:36 ` Michael Mol
2013-03-08 15:39 ` Florian Philipp
2013-03-08 4:30 ` Pandu Poluan
2013-03-08 8:23 ` Alan McKinnon
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=20130311224549.GA30808@waltdnes.org \
--to=waltdnes@waltdnes.org \
--cc=gentoo-user@lists.gentoo.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