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] question about IPv4 legacy and transfers - should we convert legacy to non-legacy with transfers?
- Previous message (by thread): [address-policy-wg] question about IPv4 legacy and transfers - should we convert legacy to non-legacy with transfers?
- Next message (by thread): [address-policy-wg] question about IPv4 legacy and transfers - should we convert legacy to non-legacy with transfers?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Mike Burns
mike at iptrading.com
Wed Jul 17 22:05:05 CEST 2019
Hi Gert, Thanks for your reply, inline answers below. This is the wrong question to ask. "Why is changing the current system this way an improvement compared to what we have now? Improvement in which way, exactly, and who benefits?" We do not change policy just to change it, or because someone else did so, but to fix a problem, improve a process, shift unfairness some other way (these are never straightforward), etc. >Jordi has already expressed the problem and supported his depiction of unfairness that can be shifted. He buttressed his expression by pointing to relevant policies at every other RIR as evidence that he is not alone in his view. I would say he established his problem statement as a desire to shift the unfairness of retaining special address status after the provision of services that never existed for legacy owners before the RIR system. (At least I am unaware of booked transfers being possible to legacy holders prior to the RIR system.) Policy proposals do not come cheap. Bottom-up policy making requires that people spend their time looking at policy proposals, make up their mind, voice their opinion and discuss to come to an agreement. If we flood the system with changes "for the sake of change" that neither have enough support to properly take off, nor have a clearly defined problem statement (that has some amount of support behind it), we are wearing out the system, and people will stop engaging. >If we flood the system with comments from outside the region, issuing problem statement objections and irrelevancies about RIPE's contractual leverage over legacy holders and legacy holders' ability to voluntarily change status, we could also wear out the system. 😉 Regards, Mike
- Previous message (by thread): [address-policy-wg] question about IPv4 legacy and transfers - should we convert legacy to non-legacy with transfers?
- Next message (by thread): [address-policy-wg] question about IPv4 legacy and transfers - should we convert legacy to non-legacy with transfers?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]