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] 2007-01 Last Call for Comments (Direct Internet Resource Assignments to End Users from the RIPE NCC)
- Previous message (by thread): [address-policy-wg] 2007-01 Last Call for Comments (Direct Internet Resource Assignments to End Users from the RIPE NCC)
- Next message (by thread): [address-policy-wg] 2007-01 Last Call for Comments (Direct Internet Resource Assignments to End Users from the RIPE NCC)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Shane Kerr
shane at time-travellers.org
Mon Apr 7 20:22:29 CEST 2008
Max, I agree with you. I don't care so much about how to revoke space in the IPv6 context, but it would be nice to know who is responsible for originating traffic. Or at least if someone, somewhere knew who is responsible for originating traffic. On Mon, Apr 07, 2008 at 06:01:49PM +0300, Max Tulyev wrote: > > current system is NOT working well. > > Just because we can't trace dead companies and dead assignments and > reuse it. In 1-2 years all unused space will be assigned. > > But if even that policy will be implemented - how we can enforce it? > How can we revoke that space if need? -- Shane
- Previous message (by thread): [address-policy-wg] 2007-01 Last Call for Comments (Direct Internet Resource Assignments to End Users from the RIPE NCC)
- Next message (by thread): [address-policy-wg] 2007-01 Last Call for Comments (Direct Internet Resource Assignments to End Users from the RIPE NCC)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]