From andrei at ripe.net Tue Mar 14 13:42:23 2006 From: andrei at ripe.net (Andrei Robachevsky) Date: Tue, 14 Mar 2006 13:42:23 +0100 Subject: [ncc-services-wg] Deprecation of ip6.int scheduled for 1 June 2006 Message-ID: <4416BA2F.8080809@ripe.net> Dear Colleagues In August 2005, the IETF published RFC 4159: 'Deprecation of "ip6.int"', as a Best Current Practice document. The RFC noted that maintenance of "ip6.int" is no longer needed and called on the Regional Internet Registries (RIRs) to decide when to stop providing support for the domain. The RIRs have jointly agreed to do this on 1 June 2006. There will be a short presentation on this at the RIPE 52 Meeting in Istanbul. You can find more information about this meeting at: http://www.ripe.net/ripe/meetings/ripe-52/index.html Regards Andrei Robachevsky Chief Technical Officer RIPE NCC From andrei at ripe.net Tue Mar 14 13:42:23 2006 From: andrei at ripe.net (Andrei Robachevsky) Date: Tue, 14 Mar 2006 13:42:23 +0100 Subject: [ncc-services-wg] [local-ir]Deprecation of ip6.int scheduled for 1 June 2006 Message-ID: <4416BA2F.8080809@ripe.net> Dear Colleagues In August 2005, the IETF published RFC 4159: 'Deprecation of "ip6.int"', as a Best Current Practice document. The RFC noted that maintenance of "ip6.int" is no longer needed and called on the Regional Internet Registries (RIRs) to decide when to stop providing support for the domain. The RIRs have jointly agreed to do this on 1 June 2006. There will be a short presentation on this at the RIPE 52 Meeting in Istanbul. You can find more information about this meeting at: http://www.ripe.net/ripe/meetings/ripe-52/index.html Regards Andrei Robachevsky Chief Technical Officer RIPE NCC From trudy at ripe.net Mon Mar 27 13:27:19 2006 From: trudy at ripe.net (Trudy Prins) Date: Mon, 27 Mar 2006 13:27:19 +0200 Subject: [ncc-services-wg] Whois Updates down Message-ID: <4427CC17.6040106@ripe.net> [apologies for duplicate mails] Dear Colleagues, >From 11:30 this morning our Whois Update service has been unavailable. Currently, we are investigating what caused this problem. We expect Whois Updates to be available again in approximately 1 hour. We apologise for the inconvenience. If you have any questions or concerns regarding this issue, please contact . Regards, -- Trudy Prins RIPE Database Administration From trudy at ripe.net Mon Mar 27 16:01:44 2006 From: trudy at ripe.net (Trudy Prins) Date: Mon, 27 Mar 2006 16:01:44 +0200 Subject: [ncc-services-wg] Whois Updates up again In-Reply-To: <4427CC17.6040106@ripe.net> References: <4427CC17.6040106@ripe.net> Message-ID: <4427F048.50706@ripe.net> Dear Colleagues Whois updates are operational again. The problem was caused by one of our real time mirrors. We will investigate to find out which mirroring connection caused the issue, in the meantime, we have disabled the mirroring process for all of our external sources: RIPE:2:Y:2278327-7509807 RADB:1:Y:299843-303044 APNIC:2:Y:1710606-1949350 ARIN:1:Y:2-3603020 VERIO:1:Y:20896-59002 JPIRR:1:Y:755-27263 We apologise for the inconvenience. If you have any questions or concerns regarding this issue, please contact . Regards, Trudy Prins RIPE Database Administration From feedback at ripe.net Mon Mar 27 17:42:42 2006 From: feedback at ripe.net (Paul Rendek) Date: Mon, 27 Mar 2006 17:42:42 +0200 Subject: [ncc-services-wg] RIPE NCC Member Update 9: Now Online Message-ID: <442807F2.4050804@ripe.net> [Apologies for duplicate e-mails] Dear Colleagues, The RIPE NCC is pleased to announce that the latest edition of the RIPE NCC Member Update is now online. You can find the RIPE NCC Member Update 9 at: http://www.ripe.net/membership/newsletter/2006/newsletter9.pdf This edition includes information on: - The RIPE NCC?s secondary DNS service to top-level domains (TLDs) - World Summit on Information Society (WSIS) 2005: response and future plans - The RIPE NCC E-Learning Centre, Training Courses and conference calendar - RIPE NCC Regional and Roundtable Meetings - The RIPE Policy Development Process (PDP) - Previous and upcoming RIPE Meetings If you have any questions, suggestions or comments about the RIPE NCC Member Update, please contact us at: Regards, Paul Rendek Head of Member Services & Communications RIPE NCC From BSanghani at flagtelecom.com Tue Mar 28 13:02:05 2006 From: BSanghani at flagtelecom.com (Sanghani, Bijal) Date: Tue, 28 Mar 2006 12:02:05 +0100 Subject: [ncc-services-wg] RIPE 52 - NCC Services WG - Agenda Items Message-ID: <147955311569D511AD0D00508B66753001EE446A@lon-emailcl.flagtelecom.com> Dear Colleagues, We are currently compiling the draft agenda for the RIPE NCC Services Working Group for RIPE 52. If anyone would like to suggest a presentation or raise a topic for discussion please let me know and we'll arrange a spot on the agenda. Thanks, Bijal ********************************************************************** This e-mail message is confidential and is intended only for the use of the individual or entity named above and contains information which is or may be confidential, non-public or legally privileged. Any dissemination or distribution of this message other than to its intended recipient is strictly prohibited. You should not copy it or use it for any purpose nor disclose the contents to any other person. If you have received this message in error, please notify us by email to postmaster at flagtelecom.com immediately and delete the original message and all copies from all locations in your computer systems. This e-mail has been swept by Mailsweeper TM for viruses. However, FLAG Telecom cannot accept liability for any damage which you may sustain as a result of software viruses. ********************************************************************** This message has been scanned for viruses by MailControl - www.mailcontrol.com From trudy at ripe.net Thu Mar 30 14:27:54 2006 From: trudy at ripe.net (Trudy Prins) Date: Thu, 30 Mar 2006 14:27:54 +0200 Subject: [ncc-services-wg] mirroring connections with Whois Database enabled In-Reply-To: <4427F048.50706@ripe.net> References: <4427CC17.6040106@ripe.net> <4427F048.50706@ripe.net> Message-ID: <442BCECA.4050607@ripe.net> Dear Colleagues, We have enabled the mirroring process for all of our external sources, except for: APNIC:2:Y:1710606-1949350 This mirroring connection was causing our update server to crash, and so we temporarily disabled it. We intend to enable this mirroring connection as soon as it is safe to do so. We apologise for the inconvenience. If you have any questions or concerns regarding this issue, please contact ripe-dbm at ripe.net. Regards, Trudy Prins RIPE Database Administration