<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;">Dear colleagues, The RIPE NCC has updated the implementation plan for ripe-605 "RIPE NCC Services to Legacy Internet Resource Holders" (accepted policy proposal 2012-07): <a href="https://www.ripe.net/lir-services/resource-management/policy-implementation-plans/2012-07-implementation">https://www.ripe.net/lir-services/resource-management/policy-implementation-plans/2012-07-implementation</a> The implementation that specifically relates to the RIPE Database has been updated in line with these revisions: <a href="https://www.ripe.net/lir-services/resource-management/policy-implementation-plans/2012-07-implementation-ripe-db">https://www.ripe.net/lir-services/resource-management/policy-implementation-plans/2012-07-implementation-ripe-db</a> We have revised this plan so that all AUT-NUM and parent legacy Internet resource holders will be notified of status changes in one batch. These notifications will be sent when the software is deployed to the Resource Candidate (RC) Test Environment. When the software is deployed to production, after RIPE 68, all status values will be generated or set on the same day. Notifying all resource holders in the same, single batch ensures consistency and accuracy across the entries in the RIPE Database. The process of contacting all resource holders in multiple batches would have been a more time-consuming and drawn out process. Please do not hesitate to contact us if you have any questions or feedback. Kind regards, Xavier Le Bris IP Resource Analyst <div apple-content-edited="true"><div> </div> </div> </body></html>