[narten@us.ibm.com: PI addressing in IPv6 advances in ARIN]

[James Jun]

> that's just because there _is_ no argument against IPv6 PI which
> withstands any real life counter arguments.

Absolutely.

People need to realize that by the time IPv6 has deaggregation and
'messy-routes' problems, we should be jumping up and down in joy that
everyone has converted to IPv6.  Or, we can just continue to talk hot air
while the whole world laughs off of us and never adapts to IPv6.

This whole IPv6 thing started about a decade ago and still the move to IPv6
around the world is quite unimpressive.  Many people who are against IPv6
deployment have made clear message: "we can multihome in IPv4 but cannot in
IPv6.  I don't care if its next-gen internet, if it's not going to provide
reliability, it's useless"

Making up policy restrictions (some of them are as dumb as "only the big
ISPs should be having PI space") and deriving protocols that take away the
traffic-engineering rights of network operators (see: shim6) is definitely
the wrong tool we need at the wrong place and at the wrong time.

And for those shim6 advocates who just won't go away, well if you (IETF)
didn't get the memo, the operator's community at least here in the States
have flat out rejected shim6 as a viable method.  So there you have it.

If you want to solve scalability problems, work on revising the algorithms
and routing protocols (i.e. BGP) and forwarding apparatus to be able to
scale up with billions+ routes in the table.  The scalability problem that
many people talk hot air about in IPv6 is at the routing table, not at
people using the internet.  Let them use it; fix the problems where they
exist, and stop restricting who gets a routing slot.

james