[address-policy-wg] [Ticket#2012110601002595] Status of /24 PI IPv4 from last /8

Hi,

On Wed, Nov 07, 2012 at 12:03:36PM +0000, Nick Hilliard wrote:
> On 07/11/2012 11:36, Jan Zorz @ go6.si wrote:
> > So, they are stuck (all of a sudden, what a surprise).
> > 
> > Another option is to start working on IPv6 solutions so the whole thing
> > becomes usable for them - whatever that might be and whatever efforts that
> > may include ;)
> > 
> > At some point this really needs to end.
> 
> I agree but we haven't reached that point yet, and as long as these two graphs:
> 
> https://www.inex.ie/noncms/img/inex-lan1-ipv6-20121107.png
> https://www.inex.ie/noncms/img/inex-lan1-ipv4-20121107.png
> 
> ... differ from each other by a factor of 1000, it's unrealistic to say that:
> 
> - ipv6 is a viable alternative to IPv4 right now
> - ipv4 is deprecated / legacy / historic / whatever

Actually, looking at traffic graphs is misleading at best.  These show
whether big telcos that have sat on their huge IPv6 allocations for
a long time finally get around to IPv6-enable their customers (or 
continue stalling), but do not really say anything about the *usability*
of IPv6 for Joe Average User.

Since the context of this discussion is "WE MUST HAVE IPv4 PI!!!", this
statement might need some adjustment to "there is no IPv4 PI, can we do
something else?", like "can we use IPv6 PI plus double-IPv4-PA?"  or 
"can we use IPv6 PI plus our ISP's friendly NAT64 translator?"...

These seem much more relevant questions to me than "can we look around
in the decks below the water line for additional deck chairs?".

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (89) 32356-444            USt-IdNr.: DE813185279