On 21/02/2013 15:12, Gert Doering wrote:
On Thu, Feb 21, 2013 at 08:52:18AM -0600, David Farmer wrote:
"Re-allocated blocks may be certified to establish the current allocation holder if the receiving party so chooses, and any previous related certificates will be revoked."
Works for me :-) - but now we need someone to volunteer to formally drive this through the policy development process (PDP)...
This is a bad idea for two reasons: 1. I don't think it's a good idea to have non-atomic policy. I.e. if there's RPKI policy statements here where they don't really need to be, then this creates unnecessary confusion. If there is no statement about RPKI policy in here, then I expect the default action by the RIPE NCC will be to treat these allocations as regular allocation 2. by explicitly mentioning RPKI and certification, the proposal will be to create a RIPE policy which will permit certification for reallocated blocks only. This will do two things: 2.1. create a RIPE policy discrepancy between how RPKI is handled for reallocated resources and resources which are still assigned to their original holders. 2.2. re-open the discussion about resource certification at half-cock, which will lead to a re-run of the same arguments put forward for 2008-08. The intention of the policy change here is to fix a policy bug, and it would be a shame to have it ending up as an unnecessary re-hash of 2008-08. The easiest and simplest thing would be to drop the sentence completely, at which point the de-facto RIPE NCC procedures concerning certification will apply. If this seems like a sensible and pragmatic approach to others, I can oblige from the policy proposal point of view. Or someone else can, if they want. Nick