[Apologies for duplicate emails] Dear colleagues, At the RIPE 62 Meeting, in both the RIPE NCC Services and Database Working Groups, there was an update on the progress of RIPE Policy Proposal 2007-01, "Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region". The presentations can be viewed on the RIPE NCC website at: http://ripe62.ripe.net/presentations/117-RIPE_62_Arne_Kiessling.pptx http://ripe62.ripe.net/presentations/143-DB_Update-62-final.pptx Part of the process requires the RIPE NCC to monitor changes to independent Internet number resources assigned by the RIPE NCC. The objects included in this are PI assignment INETNUM/INET6NUM and Autonomous System Number AUT-NUM objects. This is done by adding a reference to an additional maintainer to all these objects. This will not affect your authorisation or control of this data in the RIPE Database. For a number of years, the RIPE NCC has been using the MNTNER object RIPE-NCC-HM-PI-MNT for this monitoring. A new MNTNER is now being used, RIPE-NCC-END-MNT. The new MNTNER will replace the old one, or be added, where necessary. This change will be performed on all appropriate data in the RIPE Database by the RIPE NCC Database Group today, 28 June 2011. Because the update will involve more than 20,000 objects, no individual notifications will be sent. After this change takes place, please do not remove this new maintainer reference. It is required by the policy referenced above. This change is administrative and has no operational impact on users. If you have any questions, please contact Customer Services at ripe-dbm@ripe.net. Regards, Ingrid Wijte Registration Services Assistant Manager RIPE NCC