This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[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 ]
Carlos Morgado
chbm at cprm.net
Mon Jun 14 15:17:01 CEST 2004
On Mon, Jun 14, 2004 at 05:56:19AM -0700, william(at)elan.net wrote: > > > 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... > I wouldn't see anything wrong with it either except IANA is allocating sequential /23s, not reserving larger blocks for each RIR. (http://www.iana.org/assignments/ipv6-tla-assignments) Now, consider one of the reasons IPv6 hasn't take off yet is there's a bunch of problems created by the geographical aggregation goals. Regards -- Carlos Morgado <chbm at cprm.net> - Internet Engineering - Phone +351 214146594 GPG key: 0x75E451E2 FP: B98B 222B F276 18C0 266B 599D 93A1 A3FB 75E4 51E2 The views expressed above do not bind my employer.
- 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 ]