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

Unreferenced person/role objects
by Denis Walker 03 Jan '08

03 Jan '08

[Apologies for duplicates] Dear Colleagues, The RIPE Data Protection Task Force asked the RIPE NCC to look at why so many unreferenced person/role objects are being created. We found that one organisation was responsible for about 80% of all objects that became unreferenced over the course of 2007. At the time of investigation, this same organisation was responsible for about 30% of all existing unreferenced objects in the RIPE Database. We contacted them and they responded very quickly. They gave the RIPE NCC permission to delete all these unreferenced objects, and they have now adjusted their procedures. Over the New Year period, when we expected the load on the RIPE Database to be quite low, we deleted 161062 person/role objects. You can see the drop in the graph here: http://www.ripe.net/projects/dbconstat/cons-unrefpero.html This problem was caused by deleting inetnum objects, but not deleting the referenced person/role objects. We would like to ask you to please check your own assignment procedures. As customers come and go and you delete or re-assign address space, please delete any person/role objects that are no longer referenced. In the long term, the RIPE NCC will implement an automatic clean-up process, but this may take some time to develop. Regards Denis Walker Business Analyst, RIPE NCC

1 0

AAAA records to be added for root servers
by Barbara Roseman 31 Dec '07

31 Dec '07

apologies for cross-posting... On 4 February 2008, IANA will add AAAA records for the IPv6 addresses of the four root servers whose operators have requested it. A technical analysis of inserting IPv6 records into the root has been done by a joint working group of ICANN's Root Server System Advisory Committee and Security and Stability Advisory Committee, a report of which can be found at http://www.icann.org/committees/security/ sac018.pdf. Network operators should take whatever steps they feel appropriate to prepare for the inclusion of AAAA records in response to root queries. More information will be posted to the IANA web site during January. Regards, Barbara Roseman IANA General OperationsManager ICANN

1 0

New RIPE NCC PGP Key
by Alex Le Heux 17 Dec '07

17 Dec '07

[Apologies for duplicate e-mails] Dear Colleagues, We are approaching the new year and so we will start to use a new PGP key for signing e-mail sent from our ticketing system. On Wednesday 2nd January 2008 we will start using our 2008 key to sign e-mail. The new key has been signed by the old key as described in the key-management policy on our web site: https://www.ripe.net/rs/pgp/index.html The old key remains valid until 7th February 2008. If you have any questions, please contact <lir-help(a)ripe.net>. Kind Regards, Alex Le Heux RIPE NCC

1 0

Unscheduled LIR Portal outage
by Pedro da Silva Vaz 22 Nov '07

22 Nov '07

Dear Colleagues The LIR Portal and related services have experienced several short outages in recent days. This was due to an unsuccessful upgrade of our production servers. All LIR Portal services were down for approximately one hour from 16:00 (UTC) on Wednesday, 21 November, and from 10:00 - 15:00 (UTC) on Thursday, 22 November. The New LIR Registration Wizard remained unavailable until approximately 16:30 (UTC) on Thursday, due to some extra maintenance tasks. We apologise for any inconvenience this may have caused. If you have any questions regarding this event, please send an email to <sw-bugs(a)ripe.net>. -- Pedro Vaz Software Engineer Phone: +31 20 535 4490 ------------------ Business Applications Department RIPE NCC

1 0

New Document available: ripe-423
by RIPE NCC Document Announcement Service 15 Nov '07

15 Nov '07

Dear Colleagues We have published a new RIPE Document - ripe-423 'RIPE NCC Audit Activity'. It replaces ripe-170 'RIPE NCC Consistency & Auditing Activity'. We have also published ripe-424, as it contained references to ripe-170. The publication of these documents do not represent any change to policy in the RIPE NCC Service Region. The new documents are available at: http://www.ripe.net/ripe/docs/ripe-423.html http://www.ripe.net/ripe/docs/ripe-424.html Regards Adrian Bedford Web Services Team Leader RIPE NCC

1 0

Announcing new RIS de-bogon prefixes
by Ruben van Staveren 13 Nov '07

13 Nov '07

[Apologies for duplicate messages] Dear Colleagues As part of our effort to de-bogonise new address blocks, we are now announcing the following prefixes on RRC03: 114.0.0.0/24 114.50.0.0/21 114.200.0.0/19 114.255.0.0/16 115.0.0.0/24 115.50.0.0/21 115.200.0.0/19 115.255.0.0/16 More information regarding the RIS de-bogon project can be found at: http://www.ris.ripe.net/debogon/index.shtml Kind regards, Ruben van Staveren, RIPE NCC

1 0

RIPE NCC General Meeting October 2007 - Final Reminder to Register
by Axel Pawlik 23 Oct '07

23 Oct '07

[Apologies for duplicate e-mails] Dear RIPE NCC member, The RIPE NCC Executive Board is pleased to invite you to the RIPE NCC General Meeting (GM). The meeting will be held at 17:45 on Wednesday, 24 October 2007 during the RIPE 55 meeting in Amsterdam, the Netherlands. You can register online at: https://lirportal.ripe.net/lirportal/meeting/registration-general/meeting.h… You will also be able to register at the GM registration desk until 15:00 on Wednesday, 24 October 2006. After this time, registration for the GM will close. Please bring the appropriate identification to the GM registration desk. Once registered you will be given your meeting folder (containing your membership status and details of your voting rights) and your GM badge. More information on the GM can be found at: http://www.ripe.net/membership/gm/gm-october2007/ The GM agenda is available at: http://www.ripe.net/membership/gm/gm-october2007/agenda.html The GM supporting documents can be downloaded at: http://www.ripe.net/ripe/draft-documents/gm-october2007/ If you have any questions about the GM, please e-mail us at: agm(a)ripe.net Regards, Axel Pawlik Managing Director RIPE NCC

1 0

Re: Allow DNSMON services to monitor ENUM domains
by Jim Reid 18 Oct '07

18 Oct '07

Ondrej, I raised a number of issues about this proposal when you first presented this to the ENUM WG. To the best of my knowledge these have still not been resolved. Wearing no hats, my concerns are as follows: 1 DNS Monitoring is not a core NCC service. It should not be doing this IMO. It's OK for the NCC to monitor its own name servers, but that's all. 2 By offering a commercial DNS Monitoring service, the NCC is distorting the market. Its presence presents other organisations from offering similar services because the barrier to entry has been artificially increased. And on top of that the NCC has cherry-picked the best customers. 3 The costs of the NCC's DNS monitoring service are not clear. Which raises the prospect of complaints about monopoly membership fees cross-subsidising non-core commercial activities. This is a particular worry of mine given that the NCC's initial investment in name server monitoring was met from its membership fees. 4 If any monitoring of ENUM delegations was to be done by the NCC, it must only be at the request of the Administration concerned. This avoids issues about national sovereignty. I accept this is unlikely to be a concern for many countries. But that will not be the case in the parts of the world that are hostile to Internet governance in its broadest sense being outside an international treaty organisation. It would not be wise IMO to open another window for those sorts of complaints and attacks. Issues 1-3 have parallels with the historical situation of the NCC providing DNS service for ccTLDs. That situation is beginning to get untangled. And for the same reasons outlined above: non-core service, competition concerns, cross-subsidy, etc. It seems unwise to be opening up the same can of worms all over again just as an earlier one is starting to get cleared up.

14 39

New RIPE Database document
by Denis Walker 11 Oct '07

11 Oct '07

[Apologies for duplicates] Dear Colleagues, During the Database Working Group (DB WG) session at RIPE 54, it was decided to review the status of those RIPE Documents relating to the RIPE Database. Following discussion on the DB WG Mailing List, a proposal to address this issue was produced, which can be viewed at: http://ripe.net/ripe/maillists/archives/db-wg/2007/msg00162.html No concerns were raised and this proposal has now been implemented. This implementation has resulted in a new RIPE Document, ripe-419 "RIPE Database Reference Manual". This provides a brief introduction to the RIPE Database and references the new RIPE Database Document Library, which can be viewed at: http://www.ripe.net/db/docs.html This library references all the available documents concerning the RIPE Database and associated services. These documents will, in future, be kept up-to-date with all changes to database software and procedures. If you have any questions or concerns, please send an e-mail to <ripe-dbm(a)ripe.net>. Regards Denis Walker RIPE NCC

1 0

Announcing new RIS de-bogon prefixes
by Ruben van Staveren 11 Oct '07

11 Oct '07

[Apologies for duplicate messages] Dear Colleagues As part of our effort to de-bogonise new address blocks, we are now announcing prefixes from 186.127.248/21 and 186.128/16 on RRC03. Kind regards, Ruben van Staveren, RIPE NCC -- Ruben van Staveren RIPE Network Coordination Center Information Services Singel 258 Amsterdam NL http://www.ripe.net +31 20 535 4444 PGP finger print 6501 4389 A675 477E DCE5 53D8 9108 49E2 DAFC 271B

1 0