[arin-ppml] ARIN-prop-132: ISP Sub-assignments Do Not Require Specific Customer Relationships
On Fri, Feb 11, 2011 at 5:32 PM, George Bonser <gbonser at seven.com> wrote:
>> I'm not opposed, but I am confused. Don't we want to prevent and/or
>> retard de-aggregation? Are the consequences of de-aggregation of less
>> magnitude than the consequences of
>> failing to detach the notion of the LIR from the notion of the ISP?
> Too late for that at this point. V4 is going to shatter into a million
> tiny pieces now. Where it will make a difference is in v6. Many don't
> take smaller than a /32 out of PA space but that will change as the
> pressure from v4 eases up and they aren't trying to run dual-stack. The
> only thing really pressuring not taking more specific than a /32 out of
> PA in v6 is v4 bloat and its impact on dual-stack routers.
> 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.
Certainly this is outside the scope of ARIN-prop-132, but wouldn't we
be frying a bigger fish by tackling what qualifies as justification
and requiring more efficient use of space? I've seen hosting providers
offering some really silly justification to ARIN and giving out one or
more /24's with a dedicated server in exchange for a small fee.
Perhaps single customers of /24's and shorter should have to remit
their justification directly to ARIN on a revolving basis to prevent
waste and fraud. If I tell a customer that their justification is poor
and refuse to issue space, some other provider will become more
creative with the justification and grant them the same. Centralizing
the justification of space at a more micro level would certainly have
Jeffrey Lyon, Leadership Team
jeffrey.lyon at blacklotus.net | http://www.blacklotus.net
Black Lotus Communications - AS32421
First and Leading in DDoS Protection Solutions