Customer IPv6 range assignments.

[Andrew Alston]

We take a slightly different approach, assigning V6 to EDU institutions within .za.
 
Our rule is simple, we assign /48s on /44 boundaries, and where institutions have more than one physical campus they can have more than a /48.  So if I look at some of our institutions where they have 4 campuses for example, I'd assign them a /46.  The maximum allocation an  institution can have is a /44 though.
 
We do this to allow for better route aggregation within the institutions inter-campus networks, allowing them to assign /64s per lab/network segment, and aggregating back to a single /48 per physically diverse campus.
 
I know this strategy is a little contrarversial, but its certainly worked well for us so far.
 
Andrew Alston
TENET - Chief Technology Officer

________________________________

From: ipv6-ops-bounces+aa=tenet.ac.za at lists.cluenet.de on behalf of Iljitsch van Beijnum
Sent: Wed 7/26/2006 10:49 PM
To: Stephen Fulton
Cc: IPv6 Ops list
Subject: Re: Customer IPv6 range assignments.



On 26-jul-2006, at 21:40, Stephen Fulton wrote:

> According to the ARIN documentation we've read, the standard 
> assignment to end-users (whether a single person or a large 
> corporation) should be a /48.  Regardless of the amount of address 
> space available with IPv6, this seems like an awful waste of 
> space.  I'm curious if this policy is still current, or have I mis-
> interpreted the documentation?  Would we be breaking rules if we 
> assigned a /64 or /56 to a small client?

I don't think so, but you should check the rules so you don't run 
into trouble when you need more IPv6 space.

I understand there is movement in the direction of /56 in ARIN 
country, but I'm not sure how far along that is. Personally, I think /
56 is a bad choice because it's still too much for most people and 
too little for enough people that will shoot themselves in the foot 
by trying with a /56 first that having /60 + /48 is better than 
having /56 for everyone.

But why don't you ask your customer how much they want?

Iljitsch


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.cluenet.de/pipermail/ipv6-ops/attachments/20060726/00662ad1/attachment.htm>