public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [Bulk] Re: [Bulk] Re: [gentoo-user] /etc/hosts include file?
Date: Tue, 12 Mar 2013 02:37:25 +0200	[thread overview]
Message-ID: <513E78C5.1010409@gmail.com> (raw)
In-Reply-To: <254522.97043.bm@smtp119.mail.ird.yahoo.com>

On 12/03/2013 01:31, Kevin Chadwick wrote:
>>>> NAT behind a home router is bad, too. For IPv4, it's only necessary
>>>> because there aren't enough IPv4 addresses to let everyone have a unique
>>>> one.  
>>>
>>>   The best real reason for moving to IPV6 is address space (or lack
>>> thereof, in the case of IPV4).  The people who are truly interested in
>>> speeding up IPV6 adoption should do their best to shut up the internet
>>> hippies who constantly rant and rave about how "NAT is evil".  Don't let
>>> the cause get distracted by that unrelated issue.  Focus on the core
>>> issue.
>>>
> 
> I completely agree divide and conquer tactics.
> 
>>
>> You are being over-simplistic.
>>
>> Lack of IPv4 address space *caused* NAT to happen, the two are
>> inextricably intertwined. Even worse, people now have NAT conflated with
>> all sorts of other things. Like for example NAT and security.
>>
> 
> NAT was around way earlier and may I state again also that I have
> externally facing servers and games machines behind NAT.

I fail to see your point, and you have answered a question I did not ask.

I too have that same circumstance, as likely does every one else here
who works in networks for a living. So what? We have that because the
environment gives us little choice. It doesn't make it good, bad,
desirable or undesirable. it simply is and we have few realistic
alternative choices.

> 
> So are you saying that you think it is good for every machine to be in
> a DMZ, few chosen ones yes. 

That's also a question I did not ask, and one I do not care to debate.

>I disagree completely as I do with the
> usefullness of push-email.
> 
>> 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.
> 
> NAT has more uses than those two, NAT type of functionality is
> apparently desired by some ipv6 networks to allow easier ISP
> migration.

You are going to have to back that up with some reasoned arguments.

The only reason I can see why some might desire that is their reluctance
to give up on old habits. happy to be shown to be wrong though.


> 
> It's true NAT distracts from the bad points of ipv6 and which is the
> only part irrelevent for ipv4 modded to work with a larger address space
> (ipv5).
> 
> I wonder if this is an example of how these technologies can get so
> convoluted?

McKinnon's Law of Human Implementation of Solutions:

Any sufficiently large and representative group of humans when faced
with making new choices to solve old problems, will always decide on the
most complex convoluted solution that can be implemented soonest.

Relevant? I dunno. But it sure sounds good.

-- 
Alan McKinnon
alan.mckinnon@gmail.com



  reply	other threads:[~2013-03-12  0:39 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
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 [this message]
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=513E78C5.1010409@gmail.com \
    --to=alan.mckinnon@gmail.com \
    --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