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] [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 ]
Sander Steffann
sander at steffann.nl
Sun Oct 14 14:23:24 CEST 2012
Hi, > > > Permanenent transfer cost [...] > > > Please remember that the current transfer policy explicitly states "This > > re-allocation may be on either a permanent or non-permanent basis." so you can > > already use the current transfer policy for temporary transfers. > > After temporary transfer you can receive back IPs which listed in Spamhouse. I don't know any company which will temporary transfers IPs. But exactly the same can happen with sub-allocated address space. Why would transfers be any different? At least with a transfer you can show that the responsibility for those addresses was (temporarily) transferred to another organisation. With sub-allocated addresses the responsibility remains with the original holder, who would then probably even have a bigger problem explaining everything and getting off the spam lists. This seems to be an argument *in favour* of using temporary transfers... Sander
- 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 ]