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/address-policy-wg@ripe.net/
[address-policy-wg] Just say *NO* to PI space -- or how to make it lessdestructive
- Previous message (by thread): [address-policy-wg] Just say *NO* to PI space -- or how to make it lessdestructive
- Next message (by thread): [address-policy-wg] Just say *NO* to PI space -- or how to make it lessdestructive
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Gert Doering
gert at space.net
Mon Apr 24 13:07:03 CEST 2006
Hi,
On Mon, Apr 24, 2006 at 02:56:59PM +0400, Max Tulyev wrote:
> What about conserving of address space?
When talking about IPv6, and /32 or /48 allocations/assignments, routing
table slots are more valuable than /48 blocks (because routers will explode
long before the address space is done).
IPv4 is legacy anyway, and the sooner it goes away, the better.
Gert Doering
-- NetMaster
--
Total number of prefixes smaller than registry allocations: 92315
SpaceNet AG Mail: netmaster at Space.Net
Joseph-Dollinger-Bogen 14 Tel : +49-89-32356-0
D- 80807 Muenchen Fax : +49-89-32356-234
- Previous message (by thread): [address-policy-wg] Just say *NO* to PI space -- or how to make it lessdestructive
- Next message (by thread): [address-policy-wg] Just say *NO* to PI space -- or how to make it lessdestructive
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]