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] returning v4 resources in a post v4 world
- Previous message (by thread): [address-policy-wg] returning v4 resources in a post v4 world
- Next message (by thread): [address-policy-wg] returning v4 resources in a post v4 world
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jim Reid
jim at rfc1035.com
Fri Apr 13 14:36:05 CEST 2012
On 13 Apr 2012, at 13:19, Chris wrote: > transfers between lirs are subject to the same prerequisites as > allocations. Yes. I have read the policy. However there are transfers and there are transfers. A formal transfer according to the policy is of course bound by those needs-based prerequisites. Address blocks sometimes need to be moved between LIRs without invoking that: no back-room deals or cheating either. You just don't call those moves a transfer, even though that's the end result. Suppose a hypothetical IXP sells off its web hosting business. It keeps some IP addresses for itself and the rest go with the web hosting. The web customers can't be renumbered but they move to another company which might or might not be an existing LIR in the same service region. What sort of "needs-based address transfer" is that? This is a rhetorical question BTW.
- Previous message (by thread): [address-policy-wg] returning v4 resources in a post v4 world
- Next message (by thread): [address-policy-wg] returning v4 resources in a post v4 world
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]