All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ed W <lists@wildgooses.com>
To: "Krzysztof Olędzki" <ole@ans.pl>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: NAT66 : A first implementation
Date: Mon, 18 Jul 2011 09:38:51 +0100	[thread overview]
Message-ID: <4E23F11B.7020804@wildgooses.com> (raw)
In-Reply-To: <4E23764A.1080404@ans.pl>

On 18/07/2011 00:54, Krzysztof Olędzki wrote:
>>> Also, how would you imagine readressing such network one day, when you
>>> decide to change your ISP?
>>
>> Aha.  This is a statement that you don't believe PI space will become
>> easier to access when requesting IPV6 space?
> 
> IPv6 PI for everyone? Forget about it, we would shortly hit 1M or even
> 10M+ IPv6 prefixes and this way make BGP unreliable.

Agree entirely, but I think it's clear that were this an option then a
number of issues would disappear?

On a related note, plenty of people are pointing out that there are
enough IPv6 addresses to give every atom an entire IPV4 space. However,
the implementation of IPv6 appears to currently be to give out whacking
great blocks of space on the grounds that giving out small chunks would
lead to an unroutable situation..? Are we just heading for a repeat of
IPV4 exhaustion at some future point?

My understanding of IPv6 is way too limited at present, but it would
*appear* that IPV6 is really a kind of a 64bit address scheme (or
perhaps more like a 64-70bit), given that many of the standards assume
prefixes starting at /64 and getting shorter from there if you are a
larger user?  My ISP (IDNet) gives every customer a /48 for example...
It seems like DHCPv6 is needed to autoassign shorter prefixes than /64
(so I presume that /64 will be the shortest prefix given to soho users
for the time being?)

Seems absolutely baffling that we created a standard for this gigantic
address space and then we are scared to actually use it because it's
unroutable with today's hardware and so instead we hand it out in globs
large enough to make it only a tiny fraction of the size...

Ahh well

Ed W


--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2011-07-18  8:38 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
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 [this message]
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=4E23F11B.7020804@wildgooses.com \
    --to=lists@wildgooses.com \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=ole@ans.pl \
    /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.