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 ]
Gert Doering
gert at space.net
Wed Jul 17 21:39:29 CEST 2019
Hi, On Wed, Jul 17, 2019 at 03:30:08PM -0400, Mike Burns wrote: > What is the principled objection to the community trading the new service > (of booked transfers) in exchange for the change of legacy status after the > blocks are in the hands of new owners? What imposition is it on legacy > holders, who are after all selling their blocks through the agency of the > RIR? 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. 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. We already see this effect when trying to get people to comment on other proposals that *do* have a clear problem statement and a tight timeline. Gert Doering -- APWG chair -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: </ripe/mail/archives/address-policy-wg/attachments/20190717/39103fd1/attachment.sig>
- 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 ]