Hi, On Wed, Oct 15, 2014 at 12:05:56PM +0200, Daniel Baeza (Red y Sistemas TVT) wrote:
Allocations will only be made to LIRs if the have already received and IPv6 PI or PA from another LIR, RIPE NCC or other RIR. (Please, dont just read literally as my english is not very good. Try to read what I want to transmit)
But that's basically back to "window dressing" - acquiring an IPv6 network is trivial, but if someone does not want to deploy IPv6, it will not make him.
Sorry, cant understand what you mean.
Let me try to explain again. Such a policy would make the applicant request an IPv6 network block, yes. But will it make a difference for their IPv6 *deployment*? If they already plan to deploy, there's no extra incentive - and if they are not deploying IPv6, requesting an address and putting it into a drawer won't make a difference for their IPv6 deployment either. As Jim said upthread: this is window dressing, as in "it looks nice" - but it will not actually achieve what we want ("further IPv6 deployment"). [..]
If we have a clause in the policy that is there to achieve something, but doesn't do so, and the policy without the clause is easier to understand and implement, this is definitely preferred.
If the clause in the policy dont change the way the policy is, and make easier to understand and implement, for sure is preferred. If the clause is "core" and without it the policy completely changes, only to make is easier I do not agree with that.
The "core" of this policy is "define IPv4 /22 distribution", not "IPv6". The IPv6 clause was put there to give an incentive for IPv6 deployment, but it turns out that it is not effective in most cases, and harmful in others, so that clause has not met its purpose. Gert Doering -- APWG chair -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279