[ipv6-wg at ripe.net] New IPv6 Address Block Allocated to RIPE NCC
- Previous message (by thread): [ipv6-wg at ripe.net] New IPv6 Address Block Allocated to RIPE NCC
- Next message (by thread): [ipv6-wg at ripe.net] New IPv6 Address Block Allocated to RIPE NCC
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
william(at)elan.net
william at elan.net
Mon Jun 14 14:56:19 CEST 2004
On Mon, 14 Jun 2004, Gert Doering wrote: > Hi, > > On Mon, Jun 14, 2004 at 05:33:41AM -0700, william(at)elan.net wrote: > > > On Mon, Jun 14, 2004 at 02:18:01PM +0200, leo vegoda wrote: > > > > The RIPE NCC received the IPv6 address range 2001:4000::/23 > > > > from the IANA in June 2004. > > > Unbelievable. Morons. > > Why? > > Because man-months of argueing that "/23 allocations are needlessly > fragmenting the RIR address blocks, please allocate a decent size > (like a /8)" are just plainly ignored by the ICANN folks. I'll try to scan through archives when I get a chance, but I've been on this list for some time and have not seen much activity... Personally I don't see anything wrong with IANA reserving /8 for RIPE and specifying so on its page, but I really don't see why it should immedialy allocate that much space, as /8 would be what RIPE needs if half of its current membership requested ipv6 and somehow i dont think this is what is happening, you dont even have 10% of your membership doing it yet... -- William Leibzon Elan Networks william at elan.net
- Previous message (by thread): [ipv6-wg at ripe.net] New IPv6 Address Block Allocated to RIPE NCC
- Next message (by thread): [ipv6-wg at ripe.net] New IPv6 Address Block Allocated to RIPE NCC
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]