From: Iljitsch van Beijnum (no email)
Date: Tue Jan 01 2008 - 06:57:17 EST
On 31 dec 2007, at 1:24, Mark Smith wrote:
> Another idea would be to give each non-/48 customer the
> first /56 out of each /48.
Right, so you combine the downsides of both approaches.
It doesn't work when ARIN does it:
* 24.122.32.0/20 4.68.1.166 0 0 3356 6453
11290 i
* 24.122.48.0/20 4.68.1.166 0 0 3356 6453
11290 i
* 24.122.64.0/20 4.68.1.166 0 0 3356 6453
11290 i
* 24.122.80.0/20 4.68.1.166 0 0 3356 6453
11290 i
* 24.122.96.0/20 4.68.1.166 0 0 3356 6453
11290 i
* 24.122.112.0/20 4.68.1.166 0 0 3356 6453
11290 i
* 24.122.128.0/20 4.68.1.166 0 0 3356 6453
11290 i
* 24.122.144.0/20 4.68.1.166 0 0 3356 6453
11290 i
* 24.122.160.0/20 4.68.1.166 0 0 3356 6453
11290 i
* 24.122.176.0/20 4.68.1.166 0 0 3356 6453
11290 i
* 24.122.192.0/19 4.68.1.166 0 0 3356 6453
11290 i
* 24.122.224.0/20 4.68.1.166 0 0 3356 6453
11290 i
* 24.122.240.0/20 4.68.1.166 0 0 3356 6453
11290 i
And it's unlikely to work here: for those standard size blocks, you
really don't want any per-user config: you want those to be assigned
automatically. But for the /48s you do need per-user config, if only
that this user gets a /48. So these two block sizes can't
realistically come from the same (sub-) range.
|
|
|