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

RIPE NCC publishes case study of youtube.com hijack
by Daniel Karrenberg 28 Feb '08

28 Feb '08

[Apologies for duplicate e-mails] Dear Colleagues, As you may be aware from recent news reports, traffic to the youtube.com website was 'hijacked' on a global scale on Sunday, 24 February 2008. The incident was a result of the unauthorised announcement of the prefix 208.65.153.0/24 and caused the popular video sharing website to become unreachable from most, if not all, of the Internet. The RIPE NCC conducted an analysis into how this incident was seen and tracked by the RIPE NCC's Routing Information Service (RIS) and has published a case study at: http://www.ripe.net/news/study-youtube-hijacking.html The RIPE NCC RIS is a service that collects Border Gateway Protocol (BGP) routing information from roughly 600 peers at 16 Internet Exchange Points (IXPs) across the world. Data is stored in near real- time and can be instantly queried by anyone to provide multiple views of routing activity for any point in time. The RIS forms part of the RIPE NCC's suite of Information Services, which together provide a deeper insight into the workings of the Internet. The RIPE NCC is a neutral and impartial organisation, and commercial interests therefore do not influence the data collected. The RIPE NCC Information Services suite also includes the Test Traffic Measurement (TTM) service, the DNS Monitoring (DNSMON) service and Hostcount. All of these services are available to anyone, and most of them are offered free of charge. More information about RIPE NCC Information Services can be found at: http://is-portal.ripe.net Regards, Daniel Karrenberg Chief Scientist, RIPE NCC

1 0

RIPE NCC Maintenance - Saturday, 1 March 2008
by Brian Riddle 27 Feb '08

27 Feb '08

[Apologies for duplicate e-mails] Dear Colleagues, >From 10:00-18:00 (UTC) on Saturday, 1 March 2008, we will perform scheduled maintenance work on our core storage infrastructure. During this period, the following will be unavailable at times: - www.ripe.net - ftp.ripe.net - lirportal.ripe.net - e-learning.ripe.net The performance of dnsmon.ripe.net will be degraded during this period, and the website for k.root-servers.org will also be unavailable at times. We apologise for any inconvenience that this may cause. If you have any questions about this, please send an e-mail to <ops(a)ripe.net>. Regards, Brian Riddle IT Manager RIPE NCC

1 0

Announcement: Maintenance 16 February
by Brian Riddle 13 Feb '08

13 Feb '08

[Apologies for duplicate e-mails] Dear Colleagues, From 10:00-18:00 (UTC) on Saturday, 16 February 2008, we will perform scheduled maintenance work on our core storage infrastructure. During this period, the following will be unavailable at times: - www.ripe.net - ftp.ripe.net - lirportal.ripe.net - e-learning.ripe.net. The performance of dnsmon.ripe.net will also be degraded during this time. We apologise for any inconvenience that this may cause. If you have any questions about this, please e-mail ops(a)ripe.net. Regards, Brian Riddle IT Manager RIPE NCC

1 0

Important change to RIPE NCC services
by RIPE Database Manager 13 Feb '08

13 Feb '08

[Apologies for duplicate e-mails] Dear Colleagues, On Wednesday, 27 February 2008, between 17:00 and 19:00 (UTC), RIPE NCC staff will replace the web server www.ripe.net. This change means there are some possible issues that you need to be aware of. The IP address of www.ripe.net will change on Wednesday, 27 February. If you have any software that connects to this website, you should ensure that the IP address is not hard coded. The change will also result in a new URL for the syncupdates service. Most of the client software that uses syncupdates should be able to handle HTTP redirects, return code 301. If your software does this, then it will continue to work, though it is still advisable that you configure your software to use the new URL. If your software cannot handle HTTP redirects, you will need to update the URL in your software before Wednesday, February 27, to continue using this service. We would also advise that you fully implement HTTP handling in your software to avoid any future problems. The current syncupdates URLs are: http://www.ripe.net/syncupdates http://www.ripe.net/syncupdates-test These will change to: http://syncupdates.db.ripe.net http://syncupdates-test.db.ripe.net There will be a period between Wednesday, 13 February, and Wednesday, 27 February, when both the new and old syncupdates URLs will be available. We apologise for any inconvenience this may cause. If you have any questions or concerns about this, please send an e-mail to <ripe-dbm(a)ripe.net>. Regards, Agoston Horvath Software Engineer, RIPE NCC

1 0

Announcement: Maintenance 9 February 2008
by Brian Riddle 06 Feb '08

06 Feb '08

[Apologies for duplicate e-mails] Dear Colleagues, From 10:00-18:00 (UTC) on Saturday, 9 February 2008, we will perform scheduled maintenance work on our core storage infrastructure. During this period, the following will be unavailable at times: - www.ripe.net - ftp.ripe.net - lirportal.ripe.net - e-learning.ripe.net. The performance of dnsmon.ripe.net will also be degraded during this time. We apologise for any inconvenience that this may cause. If you have any questions about this, please send an e-mail ops(a)ripe.net. Regards, Brian Riddle IT Manager RIPE NCC

1 0

Maintenance Announcement
by Brian Riddle 30 Jan '08

30 Jan '08

[Apologies for duplicate e-mails.] Dear Colleagues, From 10:00 - 17:00 (UTC) on Saturday, 2 February 2008, we will perform maintenance on our central file server. During this period, the following will be unavailable at times: - www.ripe.net - ftp.ripe.net The following services will be unavailable for the entire maintenance period: - e-learning.ripe.net - lirportal.ripe.net We apologise for any inconvenience this may cause. If you have any questions or concerns about this, please e-mail ops(a)ripe.net Regards, Brian Riddle IT Manager RIPE NCC

1 0

LIR Portal Upgrade
by Trudy Prins 07 Jan '08

07 Jan '08

Dear Colleagues, A software upgrade for the LIR Portal is planned during the service's maintenance window on Wednesday, 9 January from 17:00-18:00 (UTC). During this time the LIR Portal may not be available. We apologise for any inconvenience this may cause. If you have any questions, please contact <sw-bugs(a)ripe.net>. Regards, Trudy Prins Manager Business Applications Department

1 0

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