I think maybe it would be good to deal with the certification issue in a separate policy, because it's difficult. definitely! we need more corner-case policies :) If there isn't a policy to deal with this, de-facto due diligence policies will need be created by the registration services department to handle certification requirements for ERX users.
well, to me, it's not a policy per se, but a requirement and a process. and it applies both to bringing legacy and pi in from the cold. i am more concerned with the requirements, what makes us comfortable in establishing that a claimant indeed is the legitimate holder of some resource(s). you seem to be more focused on making sure the process of meeting those requirements is not onerous. i think both are quite legitimate concerns. Andrea's statement on this is interesting: We have however built some experience reviewing proof of holdership of legacy resources over time. 84 organisations have asked the RIPE NCC to add their legacy resources to an LIR. As mentioned in this email thread, some cases have been straightforward while other cases have required in-depth research and review of documentation. one has to wonder what criteria and methods the ncc uses. randy