Also consider this…

Your ability to get additional space from ARIN is tied to the smallest block 
size
you give out to customers by default…

From NRPM:

2.15. Provider Assignment Unit (IPv6)

When applied to IPv6 policies, the term "provider assignment unit" shall mean 
the prefix of the smallest block a given ISP assigns to end sites (recommended 
/48).
6.5.2.1. Size
All allocations shall be made on nibble boundaries. 
In no case shall an LIR receive smaller than a /32 unless they specifically 
request a /36. In no case shall an ISP receive more than a /16 initial 
allocation. 
The maximum allowable allocation shall be the smallest nibble-boundary aligned 
block that can provide an equally sized nibble-boundary aligned block to each 
of the requesters serving sites large enough to satisfy the needs of the 
requesters largest single serving site using no more than 75% of the available 
addresses. 

This calculation can be summarized as /N where N = P-(X+Y) and P is the 
organization's Provider Allocation Unit X is a multiple of 4 greater than 
4/3*serving sites and Y is a multiple of 4 greater than 4/3*end sites served by 
largest serving site.
For purposes of the calculation in (c), an end site which can justify more than 
a /48 under the end-user assignment criteria in 6.5.8 shall count as the 
appropriate number of /48s that would be assigned under that policy. 
For purposes of the calculation in (c), an LIR which has subordinate LIRs shall 
make such allocations according to the same policies and criteria as ARIN. In 
such a case, the prefixes necessary for such an allocation should be treated as 
fully utilized in determining the block sizing for the parent LIR. LIRs which 
do not receive resources directly from ARIN will not be able to make such 
allocations to subordinate LIRs and subordinate LIRs which need more than a /32 
shall apply directly to ARIN. 
An LIR is not required to design or deploy their network according to this 
structure. It is strictly a mechanism to determine the largest IP address block 
to which the LIR is entitled.


So it is worth noting that if you hand out /56 to residential customers, when 
you go back to ARIN for more for your business customers, you’re going to have 
to explain why each and every business you gave a /48 to needed 256 /56s 
instead of being able to just say “I gave out X /48s”.

OTOH, if you just give out /48s to everyone, life is good and you can just go 
back to ARIN with “I gave out x /48s” no questions asked (about various sizes 
of subnets).

Owen


> On Aug 13, 2015, at 16:47 , Ron Grant <[email protected]> wrote:
> 
> Based on that new nibble of info about ARIN "sparse allocating", I would 
> probably bump my "default smallest" alloc from /56 to /48. Makes things so 
> much easier - almost like classful routing!!! Anyone remember that, or am I 
> dating myself? :-)
> 
> 
> 
> On 2015-08-13 4:41 PM, William Herrin wrote:
>> On Thu, Aug 13, 2015 at 6:59 PM, John Santos <[email protected]> wrote:
>>> Maybe off-topic, but the recommendation for assigning a /48 to each of
>>> the ISP's customers...  Does that apply only to business customers
>>> and organizations, etc., or does it also apply to residential customers?
>> Hi John,
>> 
>> It has been discussed to death. Here's a summary of the results:
>> 
>> /48 to business customers by default: strong consensus
>> /48 to all customers by default: IETF likes. Owen likes. Healthy mix of 
>> others.
>> /56 to residential customers by default: I like. Healthy mix of others.
>> Never less than a /60 to any external customer (not /128, not /64):
>> strong consensus
>> Always on a nibble boundary (mask divisible by 4): strong consensus
>> 
>> Regards,
>> Bill Herrin
>> 
>> 
> 
> -- 
> Ron Grant                                Managed DSL/T1/Wireless/Fibre
> Skyway West Business Internet          Internet and Private Networking
> [email protected] <mailto:[email protected]>                  Bonding 
> and Fail Over Solutions
> ph:  604 737 2113               Virtual Data Centre and Private Clouds
> fax: 604 482 1299                            http://www.skywaywest.com 
> <http://www.skywaywest.com/>
> 
> Sales, Support and Billing    http://www.skywaywest.com/contact-us.htm 
> <http://www.skywaywest.com/contact-us.htm>
> 
> ca.linkedin.com/in/obiron <http://ca.linkedin.com/in/obiron>
> 
> _______________________________________________
> PPML
> You are receiving this message because you are subscribed to
> the ARIN Public Policy Mailing List ([email protected] 
> <mailto:[email protected]>).
> Unsubscribe or manage your mailing list subscription at:
> http://lists.arin.net/mailman/listinfo/arin-ppml 
> <http://lists.arin.net/mailman/listinfo/arin-ppml>
> Please contact [email protected] <mailto:[email protected]> if you experience any 
> issues.

_______________________________________________
PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List ([email protected]).
Unsubscribe or manage your mailing list subscription at:
http://lists.arin.net/mailman/listinfo/arin-ppml
Please contact [email protected] if you experience any issues.

Reply via email to