From laura at ripe.net Tue Apr 4 15:53:22 2006 From: laura at ripe.net (Laura Cobley) Date: Tue, 4 Apr 2006 15:53:22 +0200 Subject: [ncc-services-wg] Improved wording for request forms Message-ID: <20060404155322.58fad925.laura@ripe.net> [Apologies for duplicate e-mails] Dear Colleagues, We are pleased to announce the publication of six updated RIPE Documents. ripe-369 IPv6 First Allocation Request Form http://www.ripe.net/docs/ipv6-first-alloc.html ripe-370 Supporting Notes for the IPv6 First Allocation Request Form http://www.ripe.net/docs/ipv6-first-alloc-support.html ripe-371 IPv6 Internet Exchange Points Assignment Request Form http://www.ripe.net/docs/ipv6-for-ixp.html ripe-372 Supporting Notes for the IPv6 Internet Exchange Points Assignment Request Form http://www.ripe.net/docs/ipv6-for-ixp-support.html ripe-373 IPv6 End User Site Assignment Request Form http://www.ripe.net/docs/ipv6-enduser-assignment.html ripe-374 Supporting Notes for the IPv6 End User Site Assignment Request Form http://www.ripe.net/docs/ipv6-enduser-assignment-support.html We have improved the wording of these documents to make the request forms easier to use. You can still complete the request forms using the previous layout as the content of the forms has not changed. These changes are part of a project to improve the wording of all request forms and supporting notes. Best Regards, Laura Cobley Registration Services RIPE NCC From markguz at ripe.net Tue Apr 4 16:00:05 2006 From: markguz at ripe.net (Mark Guz) Date: Tue, 04 Apr 2006 16:00:05 +0200 Subject: [ncc-services-wg] RIPE NCC(AS3333) Maintenance Message-ID: <1144159205.9653.9.camel@localhost.localdomain> [Apologies for Duplicates] Dear Colleagues, The RIPE NCC will carry out planned network maintenance tonight between 17:30 and 19:30 GMT and tomorrow between 16:00 and 18:00 GMT. During the work, there may be some interruption 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 . 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 -------------- 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 trudy at ripe.net Tue Apr 11 13:17:17 2006 From: trudy at ripe.net (Trudy Prins) Date: Tue, 11 Apr 2006 13:17:17 +0200 Subject: [ncc-services-wg] mirroring connection with APNIC enabled In-Reply-To: <442BCECA.4050607@ripe.net> References: <4427CC17.6040106@ripe.net> <4427F048.50706@ripe.net> <442BCECA.4050607@ripe.net> Message-ID: <443B903D.9080900@ripe.net> [Apologies for duplicate e-mails] Dear Colleagues, We recently informed you about problems with whois updates. These appeared to be caused by our mirroring connection with APNIC. Our connection caused our update server to crash, and so we temporarily disabled it. We have now reconfigured our mirroring process, and it is now stable. We have reloaded the APNIC Database to reflect recent changes. If you have any questions or concerns about this issue, please e-mail. Regards, Trudy Prins RIPE Database Administration From ncc at ripe.net Wed Apr 12 13:40:14 2006 From: ncc at ripe.net (Axel Pawlik) Date: Wed, 12 Apr 2006 13:40:14 +0200 Subject: [ncc-services-wg] Now online: RIPE NCC Annual Report 2005 Message-ID: <443CE71E.7010204@ripe.net> [Apologies for duplicate e-mails] Dear colleague, The RIPE NCC Annual Report 2005 is now available online at: http://www.ripe.net/ripe/draft-documents/gm-april2006/annual-report-2005.pdf The Annual Report details the RIPE NCC's performance during the fiscal year ending 31 December 2005. It also offers an overview of the activities carried out by the RIPE NCC and the services offered to its membership and the RIPE community. Kind regards, Axel Pawlik Managing Director RIPE NCC From markguz at ripe.net Wed Apr 12 17:07:20 2006 From: markguz at ripe.net (Mark Guz) Date: Wed, 12 Apr 2006 17:07:20 +0200 Subject: [ncc-services-wg] Emergency Maintenance Message-ID: <1144854440.6408.45.camel@localhost.localdomain> Dear Colleagues, During our maintenance window last night at NikHef we experienced connectivity problems with one of our core layer2 switches. This meant that the maintenance window was extended for an hour beyond the scheduled 19:30 - 21:30 period. The connectivity problems may have caused unreliable access to our external services, including www.ripe.net, whois.ripe.net and lirportal.ripe.net. We will perform remedial work this evening between 18:00 and 20:00 CET to replace a faulty fibre link.Unfortunately, this may cause some temporary connectivity problems. Once again, we apologise for any inconvenience this may cause and thank you for your patience. 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 -------------- 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 BSanghani at flagtelecom.com Thu Apr 13 17:20:23 2006 From: BSanghani at flagtelecom.com (Sanghani, Bijal) Date: Thu, 13 Apr 2006 16:20:23 +0100 Subject: [ncc-services-wg] RIPE 52 - NCC Services WG - Proposed Agenda Message-ID: <147955311569D511AD0D00508B66753004017AEB@lon-emailcl.flagtelecom.com> Dear All, Please see below proposed agenda for the NCC Services WG- A. Administrative Matters (5 min) Welcome Select a scribe Distribute participants list Finalise agenda Approve Minutes: RIPE 51 B. Report from the RIPE NCC, Axel Pawlik, RIPE NCC (20 min) C. Update on RIPE NCC Public Affairs, Roland Perry, RIPE NCC (10 min) D. Reassigning AS Numbers, Leo Vegoda, RIPE NCC (10 min) E. Hostcount++ Beta, Can Bican , RIPE NCC (10 min) F. Open Mic. (5 min) Z. AOB Regards, Bijal -----Original Message----- From: ncc-services-wg-admin at ripe.net [mailto:ncc-services-wg-admin at ripe.net] On Behalf Of Sanghani, Bijal Sent: 28 March 2006 12:02 To: 'ncc-services-wg at ripe.net' Subject: [ncc-services-wg] RIPE 52 - NCC Services WG - Agenda Items 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 andrei at ripe.net Thu Apr 13 17:49:24 2006 From: andrei at ripe.net (Andrei Robachevsky) Date: Thu, 13 Apr 2006 17:49:24 +0200 Subject: [ncc-services-wg] Problems with ipv6 router Message-ID: <443E7304.7000906@ripe.net> Dear Colleagues, [We are sorry for any duplicate mails you might receive] This afternoon we experienced a problem with our IPv6 router. Problems started at 13:50, and we are still facing problem. None of our IPv4 services are affected, as these are dealt with by other routers. Affected services, which we offer on IPv6 are: - FTP: ftp.ripe.net - WWW: www.ripe.net - DNS: ns*.ripe.net - Whois: whois.ripe.net We suspect that an interfacecard of our dedicated IPv6 router is faulty, and at the moment an engineer is working on it. The long term solution is that we will replace this router. We apologise for any disruption or delay this may have caused. If you have any further questions about this matter, please send an e-mail to ops at ripe.net. Kind regards Andrei Robachevsky CTO, RIPE NCC From briddle at ripe.net Thu Apr 13 20:22:03 2006 From: briddle at ripe.net (briddle at ripe.net) Date: Thu, 13 Apr 2006 20:22:03 +0200 Subject: [ncc-services-wg] Problems with ipv6 router In-Reply-To: <443E7304.7000906@ripe.net> References: <443E7304.7000906@ripe.net> Message-ID: <443E96CB.1040101@ripe.net> Dear Colleagues, With reference to the email from Andrei Robachevsky below the affected services are now up again. The uptime was 20:00. The outage was caused by a router hardware failure. We apologise for any inconvenience this may have caused. Regards, Brian Riddle. IT Manager, RIPE NCC Andrei Robachevsky wrote: > Dear Colleagues, > > [We are sorry for any duplicate mails you might receive] > > This afternoon we experienced a problem with our IPv6 router. Problems > started at 13:50, and we are still facing problem. > > None of our IPv4 services are affected, as these are dealt with by other > routers. > > Affected services, which we offer on IPv6 are: > - FTP: ftp.ripe.net > - WWW: www.ripe.net > - DNS: ns*.ripe.net > - Whois: whois.ripe.net > > We suspect that an interfacecard of our dedicated IPv6 router is faulty, > and at the moment an engineer is working on it. > > The long term solution is that we will replace this router. > > We apologise for any disruption or delay this may have caused. If you > have any further questions about this matter, please send an e-mail to > ops at ripe.net. > > > Kind regards > > Andrei Robachevsky > CTO, RIPE NCC From Niall.oReilly at ucd.ie Wed Apr 19 23:45:05 2006 From: Niall.oReilly at ucd.ie (Niall O'Reilly) Date: Wed, 19 Apr 2006 22:45:05 +0100 Subject: [ncc-services-wg] Re: RIPE52 DB-WG Draft Agenda V3 In-Reply-To: <4446444B.4020603@CC.UniVie.ac.at> References: <4446444B.4020603@CC.UniVie.ac.at> Message-ID: <4B8951C3-8772-4E07-A109-8C9FC72C73A2@ucd.ie> On 19 Apr 2006, at 15:08, Wilfried Woeber, UniVie/ACOnet wrote: > Z. AOB I'm not sure whether this is within scope, or better mentioned in the NCC-services WG, or just simply discussed over coffee with an NCC person. A colleague in a sister organization here in Ireland has recently had an experience which leads me to think that it would be useful to have some consistency checking between address assignments and the corresponding IN-ADDR.ARPA domains, at least at the /16 level. See you all next week. /Niall From Woeber at CC.UniVie.ac.at Thu Apr 20 07:09:35 2006 From: Woeber at CC.UniVie.ac.at (Wilfried Woeber, UniVie/ACOnet) Date: Thu, 20 Apr 2006 05:09:35 +0000 Subject: [ncc-services-wg] Re: RIPE52 DB-WG Draft Agenda V3 In-Reply-To: <4B8951C3-8772-4E07-A109-8C9FC72C73A2@ucd.ie> References: <4446444B.4020603@CC.UniVie.ac.at> <4B8951C3-8772-4E07-A109-8C9FC72C73A2@ucd.ie> Message-ID: <4447178F.7090400@CC.UniVie.ac.at> hi Niall, Niall O'Reilly wrote: > > On 19 Apr 2006, at 15:08, Wilfried Woeber, UniVie/ACOnet wrote: Option 3 >> Z. AOB > > > I'm not sure whether this is within scope, or Option 1 > better mentioned in the NCC-services WG, Option 2 > or just simply discussed over coffee with an NCC person. > > A colleague in a sister organization here in Ireland has recently had > an experience which leads me to think that it would be useful to have > some consistency checking between address assignments and the > corresponding IN-ADDR.ARPA domains, at least at the /16 level. > > See you all next week. > > /Niall Let us try to do (2) first, then maybe (1), both before Friday morning. Then we can still do (3) and try to bring it up in DB under AOB. Wilfried. From Woeber at CC.UniVie.ac.at Thu Apr 20 07:09:35 2006 From: Woeber at CC.UniVie.ac.at (Wilfried Woeber, UniVie/ACOnet) Date: Thu, 20 Apr 2006 05:09:35 +0000 Subject: [ncc-services-wg] [db-wg] Re: RIPE52 DB-WG Draft Agenda V3 In-Reply-To: <4B8951C3-8772-4E07-A109-8C9FC72C73A2@ucd.ie> References: <4446444B.4020603@CC.UniVie.ac.at> <4B8951C3-8772-4E07-A109-8C9FC72C73A2@ucd.ie> Message-ID: <4447178F.7090400@CC.UniVie.ac.at> hi Niall, Niall O'Reilly wrote: > > On 19 Apr 2006, at 15:08, Wilfried Woeber, UniVie/ACOnet wrote: Option 3 >> Z. AOB > > > I'm not sure whether this is within scope, or Option 1 > better mentioned in the NCC-services WG, Option 2 > or just simply discussed over coffee with an NCC person. > > A colleague in a sister organization here in Ireland has recently had > an experience which leads me to think that it would be useful to have > some consistency checking between address assignments and the > corresponding IN-ADDR.ARPA domains, at least at the /16 level. > > See you all next week. > > /Niall Let us try to do (2) first, then maybe (1), both before Friday morning. Then we can still do (3) and try to bring it up in DB under AOB. Wilfried. From Niall.oReilly at ucd.ie Wed Apr 19 23:45:05 2006 From: Niall.oReilly at ucd.ie (Niall O'Reilly) Date: Wed, 19 Apr 2006 22:45:05 +0100 Subject: [ncc-services-wg] [db-wg] Re: RIPE52 DB-WG Draft Agenda V3 In-Reply-To: <4446444B.4020603@CC.UniVie.ac.at> References: <4446444B.4020603@CC.UniVie.ac.at> Message-ID: <4B8951C3-8772-4E07-A109-8C9FC72C73A2@ucd.ie> On 19 Apr 2006, at 15:08, Wilfried Woeber, UniVie/ACOnet wrote: > Z. AOB I'm not sure whether this is within scope, or better mentioned in the NCC-services WG, or just simply discussed over coffee with an NCC person. A colleague in a sister organization here in Ireland has recently had an experience which leads me to think that it would be useful to have some consistency checking between address assignments and the corresponding IN-ADDR.ARPA domains, at least at the /16 level. See you all next week. /Niall From Niall.oReilly at ucd.ie Thu Apr 20 19:43:05 2006 From: Niall.oReilly at ucd.ie (Niall O'Reilly) Date: Thu, 20 Apr 2006 18:43:05 +0100 Subject: [ncc-services-wg] [db-wg] Re: RIPE52 DB-WG Draft Agenda V3 In-Reply-To: <4447178F.7090400@CC.UniVie.ac.at> References: <4446444B.4020603@CC.UniVie.ac.at> <4B8951C3-8772-4E07-A109-8C9FC72C73A2@ucd.ie> <4447178F.7090400@CC.UniVie.ac.at> Message-ID: <253AF332-A9E6-429A-8650-5B9DB104C233@ucd.ie> On 20 Apr 2006, at 06:09, Wilfried Woeber, UniVie/ACOnet wrote: > Niall O'Reilly wrote: >> On 19 Apr 2006, at 15:08, Wilfried Woeber, UniVie/ACOnet wrote: > Option 3 >>> Z. AOB >> I'm not sure whether this is within scope, or > Option 1 >> better mentioned in the NCC-services WG, > Option 2 >> or just simply discussed over coffee with an NCC person. >> >> A colleague in a sister organization here in Ireland has recently had >> an experience which leads me to think that it would be useful to have >> some consistency checking between address assignments and the >> corresponding IN-ADDR.ARPA domains, at least at the /16 level. >> See you all next week. >> /Niall > Let us try to do (2) first, then maybe (1), both before Friday > morning. > Then we can still do (3) and try to bring it up in DB under AOB. > Wilfried. Thanks, Wilfried. That sounds like a plan. Operationally, RIPE NCC are already on the case (2). Timothy decided he should ask me about it earlier today. Good for him! I'll follow (2) up over coffee next week and see whether NCC feel they need WG input for this for their database consistency effort. Depending on the outcome, I may approach you or Kurtis to pursue (1) or (3). If there's no WG input needed, it may be worth mentioning that very fact under AOB in DB-WG on Friday morning, just before I rush off to the airport. CU soon. /Niall From andrei at ripe.net Sun Apr 23 09:34:17 2006 From: andrei at ripe.net (Andrei Robachevsky) Date: Sun, 23 Apr 2006 09:34:17 +0200 Subject: [ncc-services-wg] Problems with the RIPE Database query server Message-ID: <444B2DF9.1070406@ripe.net> Dear Colleagues, At the moment the RIPE whois server is not responding to queries. We are aware of this and working on bringing it back into service. We will keep informing you. Sorry for the inconvenience. Regards, Andrei Robachevsky RIPE NCC From katie at ripe.net Sun Apr 23 10:16:30 2006 From: katie at ripe.net (Katie Petrusha) Date: Sun, 23 Apr 2006 10:16:30 +0200 Subject: [ncc-services-wg] RIPE Database query server is up Message-ID: <20060423081630.GA27925@ripe.net> [Apologies for duplicate mails] Dear colleagues, RIPE Whois Database query server is up. The outage was caused by a flaw in the failover setup of whois servers which we are working on. Sorry for any inconvenience. -- Katie Petrusha RIPE NCC From Niall.oReilly at ucd.ie Tue Apr 25 08:15:36 2006 From: Niall.oReilly at ucd.ie (Niall O'Reilly) Date: Tue, 25 Apr 2006 09:15:36 +0300 Subject: [ncc-services-wg] [db-wg] Re: RIPE52 DB-WG Draft Agenda V3 In-Reply-To: <253AF332-A9E6-429A-8650-5B9DB104C233@ucd.ie> References: <4446444B.4020603@CC.UniVie.ac.at> <4B8951C3-8772-4E07-A109-8C9FC72C73A2@ucd.ie> <4447178F.7090400@CC.UniVie.ac.at> <253AF332-A9E6-429A-8650-5B9DB104C233@ucd.ie> Message-ID: Change of plan: see below. On 20 Apr 2006, at 20:43, Niall O'Reilly wrote: > On 20 Apr 2006, at 06:09, Wilfried Woeber, UniVie/ACOnet wrote: > >> Niall O'Reilly wrote: >>> On 19 Apr 2006, at 15:08, Wilfried Woeber, UniVie/ACOnet wrote: >> Option 3 >>>> Z. AOB >>> I'm not sure whether this is within scope, or >> Option 1 >>> better mentioned in the NCC-services WG, >> Option 2 >>> or just simply discussed over coffee with an NCC person. >>> >>> A colleague in a sister organization here in Ireland has recently >>> had >>> an experience which leads me to think that it would be useful to >>> have >>> some consistency checking between address assignments and the >>> corresponding IN-ADDR.ARPA domains, at least at the /16 level. >>> See you all next week. >>> /Niall >> Let us try to do (2) first, then maybe (1), both before Friday >> morning. >> Then we can still do (3) and try to bring it up in DB under AOB. >> Wilfried. > > Thanks, Wilfried. That sounds like a plan. Conversations with a number of people here at RIPE 52, including some WG-co-chairs and some NCC experts, lead me to believe that this episode doesn't, on its own, indicate a sufficiently broad class of problems to warrant action. We should probably review the position if similar problems arise in the future. We don't need to take meeting time for this. /Niall