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

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

[training] RIPE NCC Webinars - new dates
by Training Services 30 Mar '15

30 Mar '15

Dear colleagues, We are pleased to announce the launch of new dates for our Webinars. The RIPE NCC Webinars are live and take only one hour. You can interact with our trainers without leaving your desk. We focus on the topics and issues most important for LIRs. Register now at https://www.ripe.net/lir-services/training/e-learning/webinars Participation is limited to 20 people, so don't hesitate if you want to take part! If you have questions, please email <training(a)ripe.net>. We look forward to seeing you online. Kind regards, RIPE NCC Training Services

1 0

Update of RIPE NCC Procedural Document
by Athina Fragkouli 18 Mar '15

18 Mar '15

Dear Colleagues, The RIPE NCC Procedural document, “Closure of Members, Deregistration of Internet Resources, and Legacy Resources” has been recently reviewed and updated. The amendments made were mostly with regards to the actions the RIPE NCC undertakes during the Deregistration procedure of Internet Number Resources. These amendments are thought to be necessary in order to avoid any chance of inconsistency between the document and the actual procedure. Moreover, an overall review of the language and terminology of the document was performed in line with the RIPE Policies and the other RIPE NCC procedural documents. Please see here the relevant link: https://www.ripe.net/ripe/docs/ripe-640/ Kind regards, Athina Fragkouli Legal Counsel RIPE NCC

1 0

Call for Agenda Items RIPE70 - RIPE NCC Services WG
by Bijal Sanghani 18 Mar '15

18 Mar '15

Dear NCC-Services WG, RIPE70 is not far away and we are putting the agenda together for the NCC Services WG. This is your opportunity to let the RIPE NCC know what you want from them, if you would like to suggest a topic for discussion or have a presentation idea you have or would like to see presented please get in touch with the working group chairs at ncc-services-wg-chairs(a)ripe.net. We look forward to hearing from you. Best regards, Bijal Sanghani RIPE NCC Services WG Co-Chair

1 0

Update from the CIO on RIPE NCC technical services
by Kaveh Ranjbar 16 Mar '15

16 Mar '15

Dear colleagues, We were busy throughout 2014 developing our technical services, including RIPE Atlas, K-root, our DNS services, RIPEstat and our research and analysis activities. I wanted to give you an update on their current state, as well as an overview of the direction we’d like to head in 2015. And of course, I’d like to hear your feedback about our proposed plans. You can find all the details on RIPE Labs: https://labs.ripe.net/Members/kranjbar/ripe-ncc-technical-services-update <https://labs.ripe.net/Members/kranjbar/ripe-ncc-technical-services-update> I look forward to your comments and suggestions. Regards, Kaveh Ranjbar Chief Information Officer RIPE NCC

1 0

2014-06 Proposal Accepted (Publication of Sponsoring LIR for Legacy Internet Resource Holders)
by Marco Schmidt 16 Mar '15

16 Mar '15

Dear colleagues, Consensus has been reached, and the proposal for a change to RIPE Document ripe-605, "RIPE NCC Services to Legacy Internet Resource Holders", has been accepted by the RIPE community. This policy change requires the RIPE NCC to publish the link between legacy holders and their sponsoring LIR. The RIPE NCC already publishes the sponsoring LIR for Provider Independent (PI) addresses and ASNs. You can find the full proposal at: http://www.ripe.net/ripe/policies/proposals/2014-06 The new RIPE Document is called ripe-639 and is available at: https://www.ripe.net/ripe/docs/ripe-639 We estimate that this proposal will take about one month to fully implement. Details of the implementation status are available at: https://www.ripe.net/lir-services/resource-management/policy-implementation… We will send another announcement once the implementation is complete and the new procedures are in place. Thank you to everyone who provided their input. Regards, Marco Schmidt Policy Development Officer RIPE NCC

1 0

Consensus on 2014-06 (Publication of Sponsoring LIR for Legacy Internet Resource Holders)
by Bijal Sanghani 12 Mar '15

12 Mar '15

Greetings everyone, The “last call” phase for policy proposal 2014-16 has now ended. There were no comments in the last call phase which is fine as it’s not really needed - in Last Call “no comments at all” is good enough. Thus, the chairs hereby declare consensus on 2014-06. If you disagree with this decision please contact the working group chairs (preferably on this public mailing list and otherwise by sending mail to ncc-services-wg—chairs(a)ripe.net. Should that not resolve the problem then you can appeal to the WG chairs collective (as per section 4 of ripe-614). Marco will send the formal announcement from the NCC shortly. Best regards, Bijal and Kurtis NCC Services WG Chairs

1 0

New RIPE NCC Membership Application Form
by Laura Cobley 05 Mar '15

05 Mar '15

Dear colleagues, We are happy to announce the launch of the new RIPE NCC Membership Application Form. The new application process was created based on the feedback we received from newly-joined RIPE NCC members and from the RIPE NCC Survey 2013. Drawing on user experiences, we have been working to streamline the process of joining the RIPE NCC. The new application form offers a much more intuitive user experience. It also collects all information needed to apply for and subsequently manage RIPE NCC accounts, meaning that new members do not need to come back for assistance before requesting Internet number resources. If you or your contacts are interested in joining the RIPE NCC, the application form is available at: https://my.ripe.net/#/public/membership As always, we welcome your feedback on the new process and invite you to send comments to us at <new-account(a)ripe.net>. Kind regards, Laura Cobley RIPE NCC

1 0

RIPE request forms
by Havard Eidnes 04 Mar '15

04 Mar '15

Hi, it seems that all the textual request forms we earlier used to interact with the e-mail based request handling service at the RIPE NCC has now been made much harder to find at the RIPE NCC web site. The underlying assumption seems to be that since the e-mail interaction with the RIPE NCC is now obsoleted, the only use for these forms has ceased to exist, so the documents have been made obsolete and can now only be found by searching. Finding the newest version of each of the individual request forms requires even more tedious work. This overlooks the fact that these documents are also very convenient one-piece collections of "this is the information we as a LIR require from you as an applicant to complete the application process for some resource with the RIPE NCC". Instead, me acting as a LIR is left with the LIR portal piecemal doling out the individual questions it wants answers to in multiple interaction steps, where each of the steps potentially require another interaction with the applicant. Am I alone in finding this to be frustrating? Regards, - Håvard

2 1