[arin-ppml] IPv6 End-User Initial Assignment Policy (or: Please don't me make do ULA + NAT66)

[Gary T. Giesen]

I'd argue that everyone that qualifies for more than a /48 be allocated a
/40 merely on the basis of internal aggregateability. A /44 is pretty hard
to have any sort of hierarchy in your address scheme if you have multiple
locations nationally. And like you said, the routing slot for a /40 costs
the same as for a /44.

GTG

-----Original Message-----
From: arin-ppml-bounces at arin.net [mailto:arin-ppml-bounces at arin.net] On
Behalf Of Bill Buhler
Sent: February 18, 2015 5:59 PM
To: james machado; William Herrin
Cc: Gary T. Giesen; arin-ppml at arin.net
Subject: Re: [arin-ppml] IPv6 End-User Initial Assignment Policy (or: Please
don't me make do ULA + NAT66)

I second that, I fail to see the harm in allowing any company that qualifies
for a direct ipv6 be allocated a /40. There are many companies in the US
that would never use up all 256 internal /48s, and there are some that would
need more, or want to perhaps move the site mask to a /56, but with an
automatic initial assignment of that size it would be easy to justify as a
future proof allocation to the executive team. It also seems to me that
entities larger than this are more likely to have multiple AS numbers and be
using multiple routing slots anyway so multiple blocks might make more
sense...

Best regards,

Bill Buhler

-----Original Message-----
From: arin-ppml-bounces at arin.net [mailto:arin-ppml-bounces at arin.net] On
Behalf Of james machado
Sent: Wednesday, February 18, 2015 3:47 PM
To: William Herrin
Cc: Gary T. Giesen; arin-ppml at arin.net
Subject: Re: [arin-ppml] IPv6 End-User Initial Assignment Policy (or: Please
don't me make do ULA + NAT66)

So we argue for a /48 for each home user site but we toss out that argument
when it comes to a smaller business with multiple sites?

I applaud the intent but think it is too short sighted William. It should
take no more routing slots for an aggregated /40 or /44 than for a /48 and
the /40 or /44 are in line with the v6 paradigm that has been fronted on
this list and others.

On Wed, Feb 18, 2015 at 1:28 PM, William Herrin <bill at herrin.us> wrote:
> On Wed, Feb 18, 2015 at 12:59 PM, William Herrin <bill at herrin.us> wrote:
>> I think that for now any end user willing to pay ARIN's fee should 
>> qualify for a /48 regardless of any technical criteria.
>
> This got me thinking. Who would choke on a policy proposal which 
> looked like the following?
>
> Add to section 6.5.8.1:
>
> (f) All end user organizations who do not qualify for addresses under
> (a) through (e) qualify for a direct assignment of exactly one /48.
> This section (f) shall expire upon determination by ARIN staff that
> IPv6 has become the "dominant" network protocol on the public 
> Internet. The expiry shall not impact prior assignments made under 
> this section.
>
> Regards,
> Bill Herrin
>
> --
> William Herrin ................ herrin at dirtside.com  bill at herrin.us 
> Owner, Dirtside Systems ......... Web: <http://www.dirtside.com/> 
> _______________________________________________
> PPML
> 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:
> http://lists.arin.net/mailman/listinfo/arin-ppml
> Please contact info at arin.net if you experience any issues.
_______________________________________________
PPML
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:
http://lists.arin.net/mailman/listinfo/arin-ppml
Please contact info at arin.net if you experience any issues.
_______________________________________________
PPML
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:
http://lists.arin.net/mailman/listinfo/arin-ppml
Please contact info at arin.net if you experience any issues.