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

Deletion of Forward DOMAIN data from the RIPE Database
by Denis Walker 29 Mar '11

29 Mar '11

[Apologies for duplicate emails] Dear colleagues, The RIPE NCC is ready for the next stage of this clean-up process, as discussed at the last few RIPE Meetings. The RIPE Database still contains many forward DOMAIN objects, listed below. Only four TLD Registries are still actively using the RIPE Database for their whole provisioning or for a second-level dataset, .SM, .MC, .NO, .IL. These four Registries are working on alternative solutions and their data will remain in the RIPE Database until their arrangements are complete. Looking at the update logs for the last year, there has been very little activity on all the other DOMAIN data (summarised below). The occasional updates are End Users who maintain their own DOMAIN objects. Even though the activity logs show that these Registries were not actively using the RIPE Database, we still contacted them for confirmation. In some cases, we received no response. The RIPE NCC will delete all the forward DOMAIN data (except for the four active users) in the week beginning Monday, 4 April 2011. Regards, Denis Walker Business Analyst RIPE NCC Database Group List of registries with forward DOMAIN data in the RIPE Database 2 al 12 at 2 az 9 ba 2 by 2 cm 24 com 1 cx 1 dz 8 ee 2 es 56 fi 2 ga 668 gm 26 hu 8 ie 176 il 2 ir 1 jj 3 jo 1 ke 1 kg 1 kr 4 kz 1 lb 1 lc 1 lv 1 ly 1 ma 702 mc 1 mt 55 net 82 no 9 org 1 pk 99 pl 20 pt 4 ru 6 sa 2210 sm 33 tr 1 va Activity over last year 2010 1 Create Modify delete fo 34 29 12 il 0 2 0 sm 27 12 15 2010 2 Create Modify delete fo 26 21 41 md 0 2 0 pl 0 1 0 sm 18 44 12 2010 3 Create Modify delete TLD si 0 0 1 es 0 0 1 fo 34 48 24 ly 0 0 3 sm 24 23 15 2010 4 Create Modify delete fo 38 34 13 net 0 0 1 si 0 0 1 sm 26 9 13 2010 5 Create Modify delete TLD de 0 1 0 fo 32 27 13 gr 0 1 0 il 0 2 0 mc 0 1 0 org 0 1 0 sm 37 10 10 2010 6 Create Modify delete TLD dk 0 1 0 fo 3 10 2 mc 2 8 0 sm 9 5 12 2010 7 Create Modify delete TLD fo 0 1 0 fo 0 0 1 gr 0 2 0 mc 2 2 0 sm 18 8 16 2010 8 Create Modify delete TLD fo 0 3 0 fo 0 0 3109 sm 16 14 10 2010 9 Create Modify delete mc 2 0 0 sm 20 20 9 2010 10 Create Modify delete be 0 0 1 gr 0 1 0 mc 1 0 0 sm 25 16 119 2010 11 Create Modify delete be 0 0 30 bg 0 0 5 cz 0 0 3 de 0 0 1 fi 0 1 0 gl 0 0 22 gr 0 0 75 it 0 0 2 lv 0 0 62 md 0 0 15 ro 0 0 1 se 0 0 6 sm 29 15 11 tn 0 0 2 ug 0 0 1 uk 0 0 4 2010 12 Create Modify delete sm 11 272 7 2011 1 Create Modify delete mc 2 0 0 sm 22 9 23 2011 2 Create Modify delete TLD is 0 1 0 fi 0 2 0 sm 13 3 66

1 0

Statistics on Policy Implementation "Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region"
by Arne Kiessling 22 Mar '11

22 Mar '11

Dear Colleagues, The RIPE NCC will start Phase 3 of the policy implementation "Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region" this week. We gathered statistics on the progress of the policy implementation since it started in March 2009. The statistics are available at: http://www.ripe.net/internet-coordination/news/announcements/update-on-poli… -- Kind Regards Arne Kiessling IP Resource Analyst RIPE Network Coordination Centre

2 2

GRS updates for the RIPE Database
by Agoston Horvath 21 Mar '11

21 Mar '11

[Apologies for duplicate emails] Dear colleagues, We are pleased to announce that we've deployed a revamped Global Resource Service (GRS) in the RIPE Database today, 21 March 2011. Please take note of the following changes: - All foreign (non-RIPE) sources have '-GRS' added to their name. Old names without '-GRS' will work for one year for backwards compatibility. You are kindly asked to adjust your environment as necessary within that time-frame. - A short-hand format has been added to the '-s GRS' to make it easier to select all GRS sources. - Queries against GRS sources don't filter returned data, nor is any accounting in place. - 'RIPE-GRS' has been added as a GRS version of our own database and includes the changes noted above. For more information on GRS, see: http://labs.ripe.net/Members/Paul_P_/ripe-registry-global-resource-service Regards, Agoston Horvath Database Group RIPE NCC

1 0

Announcement: New E-Learning Module DNS Vulnerabilities
by Sandra Bras 15 Mar '11

15 Mar '11

[Apologies for duplicate emails] Dear colleagues, The RIPE NCC is pleased to announce the launch of "DNS vulnerabilities", the second module of our DNSSEC E-Learning course. This module explains two common DNS security problems: "Man in the Middle" and "Kaminsky Attack". It can be viewed at: http://www.ripe.net/lir-services/training/e-learning/dnssec/dns-vulnerabili… We will be releasing more modules in the coming months, including: Module 3 DNSSEC and RIPE Database Modules. The RIPE NCC E-Learning is a free service that is available to everyone. If you have any questions, please feel free to contact us at e-learning(a)ripe.net. Happy learning, Sandra Brás Trainer/E-Learning Coordinator RIPE NCC

1 0

Updated RIPE NCC Procedural Document Available
by Arne Kiessling 15 Mar '11

15 Mar '11

Dear Colleagues, The RIPE NCC has published an updated procedural document, ripe-518, "Implementation of RIPE Policy 'Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region' - Phase 3". This document replaces ripe-511, which was published recently. The updated document is available at: http://www.ripe.net/ripe/docs/ripe-518 -- Kind Regards Arne Kiessling IP Resource Analyst RIPE Network Coordination Centre

2 2

New RIPE NCC Procedural Document Available
by Arne Kiessling 10 Mar '11

10 Mar '11

Dear Colleagues, The RIPE NCC has published the new procedural document ripe-511, "Implementation of RIPE Policy 'Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region' - Phase 3". This document describes the RIPE NCC procedure when contacting End Users of independent Internet number resources who have not yet entered into a contractual relationship with sponsoring Local Internet Registry (LIR) or the RIPE NCC. It also describes the possible consequences if End Users of independent Internet number resources fail to respond when approached by the RIPE NCC or are not compliant with the policies of the RIPE community. The new document is available at: http://www.ripe.net/ripe/docs/ripe-511 -- Kind Regards Arne Kiessling IP Resource Analyst RIPE Network Coordination Centre

2 1

Closure of LIR and Deregistration of Internet Number Resources
by Axel Pawlik 10 Mar '11

10 Mar '11

[Apologies for duplicate emails] Dear colleagues, The RIPE NCC, after receiving feedback from the RIPE community on the draft version, has published the procedural RIPE Document ripe-517, "Closure of LIR and Deregistration of Internet Number Resources". The document is available at: https://www.ripe.net/ripe/docs/ripe-517 This document replaces sections in two RIPE Documents that deal with the closure of LIRs and the deregistration of resources: - Sections 3.0 and 4.0 of ripe-301, "Mergers, Acquisitions, Takeovers and Closures of Organisations Operating an LIR". These sections are entitled "Closing an LIR" and "When an LIR is Closed by the RIPE NCC", respectively. The updated version of this RIPE Document is available at: https://www.ripe.net/ripe/docs/ripe-515 - Sections 4.0, 4.1 and 4.2 of ripe-475, "Independent Internet Number Resources - Contractual Relationship Changes between sponsoring LIR and End User". These sections are entitled “De-registering of Independent Internet Number Resources”, “Closure of Sponsoring LIR” and "Violation of RIPE Policy, Law or Contract", respectively. The updated version of this RIPE Document is available at: https://www.ripe.net/ripe/docs/ripe-516 The RIPE NCC would like to thank the RIPE community for its feedback. An interactive chart that helps to explain the process of closure of LIRs and deregistration of Internet number resources will be available shortly. Best regards, Axel Pawlik Managing Director RIPE NCC

1 0

documentation about the minimum allocation/assignment sizes for v4 and v6 across the RIRs
by Wilfried Woeber, UniVie/ACOnet 10 Mar '11

10 Mar '11

I got a request from one of our customers, regarding documentation of the minimum allocation and assignment sizes of the various IPv4 and IPv6 address blocks. The initial cause of the research was creating filters that reasonably allow IPv6 PI prefices (which are longer than /35 or /32). I found the relevant info for the RIPE NCC's Service Region in http://www.ripe.net/ripe/docs/ripe-510 Now I am wondering - does anyone have a list of URLs or pointers to docs for the other 4 RIRs, which would provide similar information? As an aside, it would be nice to have such information accessible in one place, maybe by way of the NRO's website :-) TIA, Wilfried.

1 0

Results of Registry Quality Data project on RIPE Labs
by Mirjam Kuehne 08 Mar '11

08 Mar '11

Dear colleagues, In 2009 the RIPE NCC started the Registry Data Quality project. A new article on RIPE Labs describes this activity, the problems we found and how we fixed them: http://labs.ripe.net/Members/xavier/ensuring_registry_data_quality Kind Regards, Mirjam Kuehne RIPE NCC

1 0

Outage Report for RIPE Database Updates
by Agoston Horvath 07 Mar '11

07 Mar '11

[Apologies for duplicate emails] Dear colleagues, Between approximately 13:25 and 13:48 (UTC) on 7 March 2011, we experienced an outage of the RIPE Database update service. During this period, no updates were processed. It was not possible to access the update service via any of the web-based or synchronous interfaces. Updates sent via email are queued and will be executed later. However, we recommend that users check their acknowledgement reports. We apologise for any inconvenience this may have caused. Regards, Paul Palse Database Group RIPE NCC

1 0