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]/
[address-policy-wg] [Ticket#2012092701011684] FW: Sub-allocations - fast and simple re-using IP-addresses
- Previous message (by thread): [address-policy-wg] [Ticket#2012092701011684] FW: Sub-allocations - fast and simple re-using IP-addresses
- Next message (by thread): [address-policy-wg] [Ticket#2012092701011684] FW: Sub-allocations - fast and simple re-using IP-addresses
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Garry Glendown
garry at nethinks.com
Sun Oct 14 16:54:07 CEST 2012
On 14.10.2012 14:53, Sander Steffann wrote: > Hi, > >> It is very difficult discuss with black lists delisting. Some of black lists can ignore requests. > IMHO blacklist operators should keep an eye on address transfers and adjust their lists accordingly. Seeing that some RBL providers seem to be more of an extortion business than spam prevention, I doubt you will have a hard time getting out of the lists quickly if required ... though, I don't see why this should be a problem preventing sub-allocations, as long as the original holder of the address space is aware of the risks, and is not so short in addresses that they need to be re-used right away once they are returned ... -garry
- Previous message (by thread): [address-policy-wg] [Ticket#2012092701011684] FW: Sub-allocations - fast and simple re-using IP-addresses
- Next message (by thread): [address-policy-wg] [Ticket#2012092701011684] FW: Sub-allocations - fast and simple re-using IP-addresses
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]