April 2015 - ncc-services-wg - mailman.ripe.net

Policy Proposal Implemented: 2014-06, "Publication of Sponsoring LIR for Legacy Internet Resource Holders"
by Tim Bruijnzeels 30 Apr '15

30 Apr '15

Dear colleagues, We are pleased to announce that following the deployment of release 1.79.1 of the RIPE Database earlier this week, the accepted RIPE Policy Proposal 2014-06, "Publication of Sponsoring LIR for Legacy Internet Resource Holders", has now been implemented. The full policy proposal can be found at: http://www.ripe.net/ripe/policies/proposals/2014-06 <http://www.ripe.net/ripe/policies/proposals/2014-06> The new RIPE Document, ripe-639, "RIPE NCC Services to Legacy Internet Resource Holders ", is available at: https://www.ripe.net/publications/docs/ripe-639 <https://www.ripe.net/publications/docs/ripe-639> Kind regards, Tim Bruijnzeels Assistant Manager Software Engineering RIPE NCC

1 0

Draft minutes: RIPE 69 NCC Services WG
by Bijal Sanghani 28 Apr '15

28 Apr '15

Hi All, We just realised the minutes from the last services working group session in London were not posted to the list, please see minutes here and apologies for delivering them a little late. https://www.ripe.net/participate/ripe/wg/services/minutes/ripe-69-ripe-ncc-… Best regards, NCC Services WG Chairs

1 0

ARC DNS consistency checks
by Nick Hilliard 23 Apr '15

23 Apr '15

A couple of months ago, I did an assisted registry check for a LIR, and the info in the Reverse DNS Consistency widget was out of date - from what I remember, over a year. This caused some confusion, as several of the problems had actually been fixed in the interim. Would it be possible to get up-to-date checks scheduled in advance of future ARC checks? It should be straightforward for the dev people to write a tool to take a regid and schedule a batch check for all the things which are reviewed in the ARC. Nick

4 4

RIPE-NCC-LEGACY-MNT
by Hank Nussbacher 07 Apr '15

07 Apr '15

Not sure which list is appropriate so please reply only to the list that people point out as the one which should handle the following issue: I have modified a number of objects to be now LEGACY objects. inet-nums and aut-nums. When the object is processed and converted into a LEGACY object, RIPE auto-adds the following line to each object: mnt-by: RIPE-NCC-LEGACY-MNT This is documented here: https://www.ripe.net/data-tools/db/release-notes/ripe-database-release-1.77 Policy 2012-07: Legacy holder organisations cannot change their organisation name in their org object if it is referenced by an INETNUM or AUTNUM that is maintained by RIPE-NCC-LEGACY-MNT. I then noticed I needed to delete some import and export lines on my aut-num policy. No can do any more. I now get the error: Authorisation for [aut-num] AS378 failed using "mnt-by:" not authenticated by: RIPE-NCC-LEGACY-MNT, AS378-MNT So this now means *every* change to any legacy IP block or ASN has to go via RIPE. But I have been unable to find how to go about informing RIPE that I need to make an object modification. Any pointers would be helpful. Regards, Hank

2 2