<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>[Apologies for duplicate emails]</div><div><br></div>Dear colleagues,<br><br>Based on recent discussions on the RIPE Address Policy WG mailing list,<br>the RIPE NCC is now seeking policy related action from the RIPE<br>community with regards to clear guidelines on how it should proceed with<br>certifying transferred IPv4 allocations.<br><br>It has recently come to our notice, via two of the policy authors, that<br>the original intention (in 2007) of the sentence "Re-allocated blocks<br>will be signed to establish the current allocation owner" was that the<br>transferred block *must* be signed *after* the transfer in order to<br>completely establish holdership.<br><br>This sentence can be found under section 5.5 of "IPv4 Address Allocation<br>and Assignment Policies for the RIPE NCC Service Region" here:<br><a href="http://www.ripe.net/ripe/docs/ripe-582#Transfers-of-Allocations">http://www.ripe.net/ripe/docs/ripe-582#Transfers-of-Allocations</a><br><br>Because the RIPE community provided guidance saying that certification<br>should be an opt-in system, the RIPE NCC built an RPKI Certification<br>system based on this opt-in notion, therefore it is not currently<br>possible for the RIPE NCC to issue certificates without the resource<br>holder initiating the process.<br><br>Therefore, the RIPE NCC's interpretation and implementation of this<br>specific sentence has been:<br><br>Registration Services verifies and reflects the change in holdership of<br>the re-allocated blocks by updating the database objects and internal<br>records following the transfer. Any certificates that had been attached<br>to these number resources before the transfer automatically become<br>invalid/revoked due to the holdership change. The transfer recipient can<br>then request a new certificate for the address space and the RIPE NCC<br>will proceed to sign these resources to establish the current allocation<br>holder.<br><br>Therefore, the RIPE NCC does not make certification of any resources<br>mandatory.<br><br>As the sentence in section 5.5 of "IPv4 Address Allocation and<br>Assignment Policies for the RIPE NCC Service Region" is open to<br>interpretation, the RIPE NCC is seeking representative(s) from the RIPE<br>community to submit an update to ripe-582 that will replace this<br>sentence with more accurate and appropriate wording or perhaps remove it<br>completely.<div><br></div><div>Kind regards, </div><div><br></div><div>Andrew de la Haye</div><div>Chief Operations Officer</div><div>RIPE NCC </div></body></html>