[arin-ppml] Opposed to 2010-9 and 2010-12
On 10/15/10 11:08 AM, michael.dillon at bt.com wrote:
>> Why not we make it a /28, and thus give the customer a /60? The
>> customer still gets 16 subnets for his house, and when 6rd goes away
>> (since, as you point out there are other disadvantages beyond address
>> space use compared to native IPv6), then the subnet will be /56 (since,
>> following your reasoning, that is what competitors with native IPv6
>> access will be providing).
> Because these allocations are intended to be returned to ARIN within
> about 10 years and there is not even the shadow of a suspicion that
> there will be any kind of IPv6 address shortage within ten years.
> We should not encourage bad engineering practices solely because
> some people have a phobia caused by past events with IPv4.
>> I would point out that the only ISP I am aware of that is conducting
>> residential trials of IPv6 seems to be talking about giving only a /64
>> to the home by default due to CPE issues. To me, that is a much greater
>> problem than having a /60 instead of a /56, because with a /64 you
>> can't do any subnetting at all.
> Some ISPs will make dumb engineering decisions but that is not really ARIN's
> problem. The marketplace will sort that out once customers realise that they
> are being shortchanged and can't get their new InternetHDTV home theater system
> working because it expects to have its own /64 assignment.
Or, the CPE vendors could figure out how to manage with a single /64 if
that's the least common denominator offered. It won't work as well as it
could have, will cause more problems, cost more overall, etc. than if
routing were available, but if it works just well enough to mask the
feedback loop to the Marketplace that you are counting on here, then the
battle is lost. Never underestimate the power of local optimization.
> --Michael Dillon
> You are receiving this message because you are subscribed to
> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
> Unsubscribe or manage your mailing list subscription at:
> Please contact info at arin.net if you experience any issues.