From andrei at ripe.net Fri Jun 2 07:47:48 2006 From: andrei at ripe.net (Andrei Robachevsky) Date: Fri, 02 Jun 2006 07:47:48 +0200 Subject: [ncc-services-wg] Re: Deprecation of ip6.int scheduled for 1 June 2006 In-Reply-To: <4471D95A.7010300@ripe.net> References: <4416BA2F.8080809@ripe.net> <4471D95A.7010300@ripe.net> Message-ID: <447FD104.1010204@ripe.net> Dear Colleagues, On 1 June 2006, the reverse delegations in the ip6.int DNS tree corresponding to IPv6 address space allocated by the RIPE NCC were deleted as planned. This means that these reverse delegations will no longer be supported. The corresponding DOMAIN objects were also deleted from the RIPE Whois Database. This has been coordinated with other Regional Internet Registries and is based on an IETF Best Current Practice document (RFC 4159). Regards, Andrei Robachevsky Chief Technical Officer RIPE NCC From trudy at ripe.net Mon Jun 12 14:06:53 2006 From: trudy at ripe.net (Trudy Prins) Date: Mon, 12 Jun 2006 14:06:53 +0200 Subject: [ncc-services-wg] Outage of Syncupdate and Webupdate Message-ID: <448D58DD.2030306@ripe.net> [Apologies for duplicate e-mails] Dear Colleagues, The Syncupdate service and the Webupdate service were unavailable from Sunday, 11 June 15:08:19 GMT until Monday, 12 June 23:53:54 GMT. The services are now available again. We apologise for any inconvenience. If you have any questions or concerns about this, please e-mail: ripe-dbm at ripe.net. Regards, Trudy Prins User Support Coordinator Software Engineering Department From briddle at ripe.net Wed Jun 14 13:14:52 2006 From: briddle at ripe.net (Brian Riddle) Date: Wed, 14 Jun 2006 13:14:52 +0200 Subject: [ncc-services-wg] Network maintenance tonight Message-ID: <448FEFAC.80804@ripe.net> [Apologies for Duplicates] Dear Colleagues, The RIPE NCC will carry out planned network maintenance Wednesday 14 June between 16:00 and 19:00 GMT. During this work, there may be periodic interruptions to our services. We apologise for any inconvenience that this may cause. This work is part of a programme of ongoing network upgrades. If you have any questions about this, please send an e-mail to ops at ripe.net Regards, Brian Riddle IT Manager RIPE NCC From markguz at ripe.net Thu Jun 15 12:45:13 2006 From: markguz at ripe.net (Mark Guz) Date: Thu, 15 Jun 2006 12:45:13 +0200 Subject: [ncc-services-wg] Re: Network maintenance tonight In-Reply-To: <448FEFAC.80804@ripe.net> References: <448FEFAC.80804@ripe.net> Message-ID: <1150368313.7110.46.camel@localhost.localdomain> [apologies for duplicates] Dear colleagues, The network upgrades we performed last night between 1600 and 1900 GMT were unfortunately unsuccessful. We experienced quite some problems between 1600 and 1800 GMT and decided to roll back to the original configuration at 1800 GMT. Normal network function returned at approximately 1830GMT. We plan to perform this upgrade work again on Monday 19 June between 1600 and 1900 GMT. Once again, if you have any questions please direct them to ops at ripe.net. Thank you again for your co-operation. Kind Regards Mark Guz Senior System/Network Engineer RIPE NCC Singel 258 Amsterdam 1016 AB Tel: +31 (0) 20 535 4444 Fax: +31 (0) 20 535 4445 http://www.ripe.net On Wed, 2006-06-14 at 13:14 +0200, Brian Riddle wrote: > [Apologies for Duplicates] > > Dear Colleagues, > > The RIPE NCC will carry out planned network maintenance Wednesday 14 > June between 16:00 and 19:00 GMT. During this work, there may be > periodic interruptions to our services. We apologise for any > inconvenience that this may cause. > > This work is part of a programme of ongoing network upgrades. > > If you have any questions about this, please send an e-mail to ops at ripe.net > > Regards, > > Brian Riddle > IT Manager RIPE NCC -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 191 bytes Desc: This is a digitally signed message part URL: From agoston at ripe.net Fri Jun 16 15:35:58 2006 From: agoston at ripe.net (Agoston Horvath) Date: Fri, 16 Jun 2006 15:35:58 +0200 Subject: [ncc-services-wg] Maintenance of whois-test.ripe.net Message-ID: <4492B3BE.5070005@ripe.net> [Apologies for duplicate e-mails.] Dear Colleagues, We will carry out maintenance work on flute.ripe.net (also known as whois-test.ripe.net) on Monday, 19 June at 11:00-13:00 (GMT). During this period, you may experience outages when trying to use the following services: - whois-test (queries and updates) - whois queries over ipv6 (including the web interface) - rrcc - dbconstat - surfme We apologise for any inconvenience. If you have any questions please contact: . Regards, Agoston Horvath Software Engineering Department RIPE NCC From james at ripe.net Wed Jun 21 16:58:57 2006 From: james at ripe.net (James Aldridge) Date: Wed, 21 Jun 2006 16:58:57 +0200 Subject: [ncc-services-wg] RIPE NCC (AS3333) Maintenance 18:00 - 21:00 (CEST) Today, June 21. Message-ID: <20060621145857.5E7B46007D@x34.ripe.net> [Apologies for duplicate e-mails.] Dear Colleagues, The RIPE NCC will carry out emergency network maintenance today, June 21, between 18:00 and 21:00 (CEST). During this time, there will be some interruption to our peerings. This work is part of a programme of ongoing network upgrades. We apologise for any inconvenience that this may cause. If you have any questions, please contact: Regards, James -- James Aldridge, Systems & Network Engineer, RIPE NCC Operations Group Tel: +31 20 535 4444 / Fax: +31 20 535 4445 From james at ripe.net Wed Jun 21 16:58:57 2006 From: james at ripe.net (James Aldridge) Date: Wed, 21 Jun 2006 16:58:57 +0200 Subject: [ncc-services-wg] RIPE NCC (AS3333) Maintenance 18:00 - 21:00 (CEST) Today, June 21. Message-ID: <20060621145857.5E7B46007D@x34.ripe.net> [Apologies for duplicate e-mails.] Dear Colleagues, The RIPE NCC will carry out emergency network maintenance today, June 21, between 18:00 and 21:00 (CEST). During this time, there will be some interruption to our peerings. This work is part of a programme of ongoing network upgrades. We apologise for any inconvenience that this may cause. If you have any questions, please contact: Regards, James -- James Aldridge, Systems & Network Engineer, RIPE NCC Operations Group Tel: +31 20 535 4444 / Fax: +31 20 535 4445 From ncc at ripe.net Thu Jun 22 10:17:43 2006 From: ncc at ripe.net (Paul Rendek) Date: Thu, 22 Jun 2006 10:17:43 +0200 Subject: [ncc-services-wg] New RIPE NCC Announcement List Message-ID: <20060622081743.6FD682F5C2@herring.ripe.net> [apologies for duplicate e-mails] Dear Colleagues, On Monday, 26 June 2006, we will replace the existing local-ir at ripe.net and the ncc-co at ripe.net membership announcement lists with one new list: ncc-announce at ripe.net. The new list will carry RIPE NCC announcements intended for our membership. The purpose of this change is to reduce duplicate e-mails and streamline the flow of communication with our members. All Local Internet Registries (LIRs) are currently subscribed to local-ir at ripe.net and ncc-co at ripe.net. All subscriptions to these lists will be moved to the new ncc-announce at ripe.net list. Many LIRs use a local mail exploder or similar method for internally distributing e-mails from the RIPE NCC. Please make sure e-mails from ncc-announce at ripe.net will be delivered to the LIR contacts within your company. The local-ir at ripe.net and ncc-co at ripe.net lists will be closed down on Monday, 26 June 2006. More information about the current membership announcement lists can be found at: http://www.ripe.net/membership/lists.html If you have any questions, please e-mail us at: contact at ripe.net Kind Regards, Paul Rendek Head of Member Services and Communications RIPE NCC From ncc at ripe.net Thu Jun 22 10:17:43 2006 From: ncc at ripe.net (Paul Rendek) Date: Thu, 22 Jun 2006 10:17:43 +0200 Subject: [ncc-services-wg] [local-ir]New RIPE NCC Announcement List Message-ID: <20060622081743.6FD682F5C2@herring.ripe.net> [apologies for duplicate e-mails] Dear Colleagues, On Monday, 26 June 2006, we will replace the existing local-ir at ripe.net and the ncc-co at ripe.net membership announcement lists with one new list: ncc-announce at ripe.net. The new list will carry RIPE NCC announcements intended for our membership. The purpose of this change is to reduce duplicate e-mails and streamline the flow of communication with our members. All Local Internet Registries (LIRs) are currently subscribed to local-ir at ripe.net and ncc-co at ripe.net. All subscriptions to these lists will be moved to the new ncc-announce at ripe.net list. Many LIRs use a local mail exploder or similar method for internally distributing e-mails from the RIPE NCC. Please make sure e-mails from ncc-announce at ripe.net will be delivered to the LIR contacts within your company. The local-ir at ripe.net and ncc-co at ripe.net lists will be closed down on Monday, 26 June 2006. More information about the current membership announcement lists can be found at: http://www.ripe.net/membership/lists.html If you have any questions, please e-mail us at: contact at ripe.net Kind Regards, Paul Rendek Head of Member Services and Communications RIPE NCC From ncc at ripe.net Thu Jun 22 10:17:43 2006 From: ncc at ripe.net (Paul Rendek) Date: Thu, 22 Jun 2006 10:17:43 +0200 Subject: [ncc-services-wg] [ncc-co@ripe.net] New RIPE NCC Announcement List Message-ID: <20060622081743.6FD682F5C2@herring.ripe.net> [apologies for duplicate e-mails] Dear Colleagues, On Monday, 26 June 2006, we will replace the existing local-ir at ripe.net and the ncc-co at ripe.net membership announcement lists with one new list: ncc-announce at ripe.net. The new list will carry RIPE NCC announcements intended for our membership. The purpose of this change is to reduce duplicate e-mails and streamline the flow of communication with our members. All Local Internet Registries (LIRs) are currently subscribed to local-ir at ripe.net and ncc-co at ripe.net. All subscriptions to these lists will be moved to the new ncc-announce at ripe.net list. Many LIRs use a local mail exploder or similar method for internally distributing e-mails from the RIPE NCC. Please make sure e-mails from ncc-announce at ripe.net will be delivered to the LIR contacts within your company. The local-ir at ripe.net and ncc-co at ripe.net lists will be closed down on Monday, 26 June 2006. More information about the current membership announcement lists can be found at: http://www.ripe.net/membership/lists.html If you have any questions, please e-mail us at: contact at ripe.net Kind Regards, Paul Rendek Head of Member Services and Communications RIPE NCC From ncc at ripe.net Thu Jun 22 10:17:43 2006 From: ncc at ripe.net (Paul Rendek) Date: Thu, 22 Jun 2006 10:17:43 +0200 Subject: [ncc-services-wg] [ncc-co@ripe.net] New RIPE NCC Announcement List Message-ID: <20060622081743.6FD682F5C2@herring.ripe.net> [apologies for duplicate e-mails] Dear Colleagues, On Monday, 26 June 2006, we will replace the existing local-ir at ripe.net and the ncc-co at ripe.net membership announcement lists with one new list: ncc-announce at ripe.net. The new list will carry RIPE NCC announcements intended for our membership. The purpose of this change is to reduce duplicate e-mails and streamline the flow of communication with our members. All Local Internet Registries (LIRs) are currently subscribed to local-ir at ripe.net and ncc-co at ripe.net. All subscriptions to these lists will be moved to the new ncc-announce at ripe.net list. Many LIRs use a local mail exploder or similar method for internally distributing e-mails from the RIPE NCC. Please make sure e-mails from ncc-announce at ripe.net will be delivered to the LIR contacts within your company. The local-ir at ripe.net and ncc-co at ripe.net lists will be closed down on Monday, 26 June 2006. More information about the current membership announcement lists can be found at: http://www.ripe.net/membership/lists.html If you have any questions, please e-mail us at: contact at ripe.net Kind Regards, Paul Rendek Head of Member Services and Communications RIPE NCC From briddle at ripe.net Thu Jun 22 13:26:36 2006 From: briddle at ripe.net (Brian Riddle) Date: Thu, 22 Jun 2006 13:26:36 +0200 Subject: [ncc-services-wg] Yesterday, 21 June, from 12:54 - 13:29 (CET), the RIPE NCC experienced a,network outage. Message-ID: <449A7E6C.9020600@ripe.net> [Apologies for duplicate e-mails.] Dear Colleagues, Yesterday, 21 June, from 12:54 - 13:29 (CET), the RIPE NCC experienced a network outage. The outage was caused by a firewall failure during the implementation of our new network infrastructure. We are currently working with Juniper to investigate the problem. We have scheduled maintenance today, 22 June, from 18:00 - 21:00 (CET) to resolve this. During this time, there will be some interruption to services. We apologise for any inconvenience caused by yesterday's outages and today's scheduled maintenance. If you have any questions, please e-mail: Regards, Brian Riddle IT Manager RIPE NCC -- Brian Riddle RIPE Network Coordination Center IT Manager Singel 258 Amsterdam NL http://www.ripe.net +31 20 535 4444 GPG Key fingerprint = 0EBA E8BA 236A D4CD B7A8 C679 A353 054D 2D35 9BE9 From briddle at ripe.net Thu Jun 22 13:26:36 2006 From: briddle at ripe.net (Brian Riddle) Date: Thu, 22 Jun 2006 13:26:36 +0200 Subject: [ncc-services-wg] Yesterday, 21 June, from 12:54 - 13:29 (CET), the RIPE NCC experienced a,network outage. Message-ID: <449A7E6C.9020600@ripe.net> [Apologies for duplicate e-mails.] Dear Colleagues, Yesterday, 21 June, from 12:54 - 13:29 (CET), the RIPE NCC experienced a network outage. The outage was caused by a firewall failure during the implementation of our new network infrastructure. We are currently working with Juniper to investigate the problem. We have scheduled maintenance today, 22 June, from 18:00 - 21:00 (CET) to resolve this. During this time, there will be some interruption to services. We apologise for any inconvenience caused by yesterday's outages and today's scheduled maintenance. If you have any questions, please e-mail: Regards, Brian Riddle IT Manager RIPE NCC -- Brian Riddle RIPE Network Coordination Center IT Manager Singel 258 Amsterdam NL http://www.ripe.net +31 20 535 4444 GPG Key fingerprint = 0EBA E8BA 236A D4CD B7A8 C679 A353 054D 2D35 9BE9 From briddle at ripe.net Tue Jun 27 16:44:50 2006 From: briddle at ripe.net (Brian Riddle) Date: Tue, 27 Jun 2006 16:44:50 +0200 Subject: [ncc-services-wg] Network Upgrade Message-ID: <44A14462.4000107@ripe.net> [Apologies for duplicate e-mails] Dear Colleagues, I am pleased to announce that the network is now stable following the recent problems we experienced during last week's network upgrade. We have identified two key issues responsible for the instability. 1. Our current firewalls have been chosen to generously accommodate all previously experienced traffic levels. This is an IPv6 related issue which does not affect the stability of the network. 2. We have agreed with Juniper that this high CPU utilisation is an abnormal state which must be addressed. We have open tickets with our suppliers concerning these issues. The network upgrade has been a long-term project with many carefully planned and implemented steps. It is great to see the end of the tunnel appearing and we thank you for your patience and support in this matter. Regards, Brian Riddle IT Manager RIPE NCC From briddle at ripe.net Tue Jun 27 16:44:50 2006 From: briddle at ripe.net (Brian Riddle) Date: Tue, 27 Jun 2006 16:44:50 +0200 Subject: [ncc-services-wg] Network Upgrade Message-ID: <44A14462.4000107@ripe.net> [Apologies for duplicate e-mails] Dear Colleagues, I am pleased to announce that the network is now stable following the recent problems we experienced during last week's network upgrade. We have identified two key issues responsible for the instability. 1. Our current firewalls have been chosen to generously accommodate all previously experienced traffic levels. This is an IPv6 related issue which does not affect the stability of the network. 2. We have agreed with Juniper that this high CPU utilisation is an abnormal state which must be addressed. We have open tickets with our suppliers concerning these issues. The network upgrade has been a long-term project with many carefully planned and implemented steps. It is great to see the end of the tunnel appearing and we thank you for your patience and support in this matter. Regards, Brian Riddle IT Manager RIPE NCC From james at ripe.net Wed Jun 28 14:35:23 2006 From: james at ripe.net (James Aldridge) Date: Wed, 28 Jun 2006 14:35:23 +0200 Subject: [ncc-services-wg] IPv6 access to ftp.ripe.net Message-ID: <20060628123523.BDC402F592@herring.ripe.net> [Apologies for duplicate e-mails] Dear Colleagues, IPv6 access to ftp.ripe.net is currently not possible. IPv4 access is unaffected. The current ScreenOS firewall software is unable to support extended passive-mode FTP. We have therefore temporarily removed the AAAA record for ftp.ripe.net from the DNS. We hope to restore IPv6 access as quickly as possible and will inform you when this occurs. We apologise for any inconvenience. Regards, James Aldridge Systems & Network Engineer RIPE NCC Operations Group