From: Rick Jones <rick.jones2@hp.com>
To: David Miller <davem@davemloft.net>
Cc: jengelh@medozas.de, T.Moes@student.ulg.ac.be,
netfilter-devel@vger.kernel.org
Subject: Re: NAT66 : A first implementation
Date: Thu, 14 Jul 2011 16:37:39 -0700 [thread overview]
Message-ID: <4E1F7DC3.5000407@hp.com> (raw)
In-Reply-To: <20110714.161717.1387261665409519132.davem@davemloft.net>
On 07/14/2011 04:17 PM, David Miller wrote:
> From: Jan Engelhardt<jengelh@medozas.de>
> Date: Fri, 15 Jul 2011 01:15:47 +0200 (CEST)
>
>> Of course yours is feature-richer. But the topic of IPv6 NAT has had
>> come up a number of unrecollectable times, and the response has been the
>> same everytime - NAT is still an ugly undesired hack whose recurrence
>> wants to be avoided.
>
> You can't avoid it.
>
> People want to hide the details of the topology of their
> internal networks, therefore we will have NAT with ipv6
> no matter what we think or feel.
>
> Everyone needs to stop being in denial, now.
So, does that imply there will be systems with only link-scope IP's
reaching-out to global-scope IPs, getting their link-scope's adjusted by
an IPv6 NAT?
rick jones
next prev parent reply other threads:[~2011-07-14 23:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-14 15:47 NAT66 : A first implementation Terry Moës
2011-07-14 16:22 ` Jan Engelhardt
2011-07-14 16:27 ` Terry Moës
2011-07-14 23:15 ` Jan Engelhardt
2011-07-14 23:17 ` David Miller
2011-07-14 23:37 ` Rick Jones [this message]
2011-07-15 15:43 ` Rick Jones
2011-07-14 23:55 ` Jan Engelhardt
2011-07-17 5:09 ` Krzysztof Olędzki
2011-07-17 22:23 ` Ed W
2011-07-17 23:54 ` Krzysztof Olędzki
2011-07-18 8:38 ` Ed W
2011-07-15 0:48 ` Jeff Haran
2011-07-15 2:29 ` Adam Roach
2011-07-15 22:12 ` Jeff Haran
2011-07-16 3:08 ` Adam Roach
2011-07-18 2:05 ` YOSHIFUJI Hideaki
2011-07-18 15:50 ` Patrick McHardy
2011-07-21 7:15 ` Harald Welte
2011-07-15 5:48 ` Philip Craig
2011-07-15 10:29 ` Jan Engelhardt
[not found] ` <4E20051D.7080208@student.ulg.ac.be>
2011-07-15 9:16 ` Terry Moës
2011-07-15 11:09 ` Jan Engelhardt
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=4E1F7DC3.5000407@hp.com \
--to=rick.jones2@hp.com \
--cc=T.Moes@student.ulg.ac.be \
--cc=davem@davemloft.net \
--cc=jengelh@medozas.de \
--cc=netfilter-devel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.