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

RIPE NCC Services Working Group - Draft Agenda
by Sanghani, Bijal 25 Sep '09

25 Sep '09

Dear All, Please see below Draft Agenda for the NCC Services Working Group - A. Administrative Matters * Welcome * Select a scribe * Jabber Monitor * Microphone Etiquette * Approve Minutes from RIPE 58 * Finalise agenda B. RIPE NCC Update - Axel Pawlik, RIPE NCC (30 minutes) C. Contractual Relationship Requirement for End Users - Andrea Cima, RIPE NCC (15 minutes) D. Certification Update, Alex Band, RIPE NCC E. Discussion about inet(6)num and aut-num objects to reference sponsoring LIR - Piotr Strzyzewski (10 mins) F. Open Microphone Session Z. A.O.B. Regards, Bijal The information contained in this e-mail message is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you should return it to the sender immediately. Please note that while we scan all e-mails for viruses we cannot guarantee that any e-mail is virus-free and accept no liability for any damage caused by any virus transmitted by this email.

1 0

LIR Portal PI doesn't work
by Max Tulyev 16 Sep '09

16 Sep '09

Hello! I am experiencing troubles with Independent Resources part of the LIR portal. It hangs continuously, goes slow - each page opens more than 1 minute, some time shows 500 error of Java subsystem. At last, when I tried to save changes about my PI/ASN clients, it cleared all marks I did before, cancel all my work for months. Am I only such unlucky guy, or there is really something happens there?

3 6

Agenda Items for RIPE 59 - NCC Services WG
by Sanghani, Bijal 16 Sep '09

16 Sep '09

Dear All, The count down has started to RIPE 59 in Lisbon, we are starting to put together a draft agenda for the NCC Services Working Group. If anyone would like to suggest a presentation or raise a topic for discussion please let either Kurtis or me know and we'll arrange a spot on the agenda for you. Regards, Bijal Sanghani The information contained in this e-mail message is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you should return it to the sender immediately. Please note that while we scan all e-mails for viruses we cannot guarantee that any e-mail is virus-free and accept no liability for any damage caused by any virus transmitted by this email.

1 0

Change to NIC handle usage in the RIPE Database
by Denis Walker 14 Sep '09

14 Sep '09

Dear Colleagues, On Thursday, 10 September the RIPE NCC implemented a change to NIC handle usage. It is no longer possible to re-use an old NIC handle. Additional checks are made when an update is sent to the RIPE Database to create a ROLE or PERSON object. If the NIC handle is in use, or has previously been used and deleted, the update will fail and a new error message will be returned in the acknowledgement: ***Error: The nic-hdl 'name' is not available. This change was requested by the Data Protection Task Force and discussed by the Database Working Group at RIPE 58: http://www.ripe.net/ripe/wg/db/minutes/ripe-58.html In the new implementation, users can select any NIC handle they wish in the same formats as before. The choice of characters and numbers is at the discretion of the user, within the same limits as before. The only difference is that when a NIC handle is chosen that has already been used, the update will fail. The main consequence of this is that if you delete a PERSON or ROLE object you cannot re-create it with the same NIC handle you had previously. Under the old system there was always a chance someone else could have taken your old NIC handle by the time you wanted to re-create it; this was the main reason for the change. The new system ensures that NIC handles map to people or roles uniquely over time. This change does not affect automatically generated organisation names. But we would like to hear feedback on whether it makes sense to also have these map to organisations uniquely over time. Regards, Denis Walker Business Analyst RIPE NCC

2 1

Deprecation of "rev-srv:" attribute completed
by Denis Walker 14 Sep '09

14 Sep '09

Dear Colleagues, On Wednesday, 2 September the RIPE NCC implemented the final stage of the "rev-srv:" deprecation. Information on this project can be found at: http://www.ripe.net/ripe/maillists/archives/db-wg/2009/msg00032.html There were approximately 100,000 remaining "rev-srv:" attributes. All but a small handful have been converted to "remarks:". The few remaining objects have very old syntax, mostly concerning the "status:" value and "country:" code. These old objects will be checked manually to determine the correct values. Regards, Denis Walker Business Analyst RIPE NCC

1 0

Country index gone?
by Hank Nussbacher 14 Sep '09

14 Sep '09

On: http://www.ripe.net/membership/ there is a link to list of members: http://www.ripe.net/membership/indices/ but I am getting: Not Found The requested URL /membership/indices/ was not found on this server. Thanks, Hank

2 1

LIR Portal Downtime: Incident Report
by Tim Bruijnzeels 09 Sep '09

09 Sep '09

Dear Colleagues, LIR Portal service has now been restored. The LIR Portal, along with several other RIPE NCC online services, was unavailable from 06:30 - 08:30 (UTC), 9 September 2009. The outage was caused by a faulty switch. We have performed emergency patching to fix the problem for now. A replacement switch will be installed this afternoon between 15:00 - 16:00 (UTC). A five-minute interruption to service is expected when we make this change. We apologise for the inconvience this may have caused for you. We are currently working on a project to migrate the LIR Portal to a new architecture, with improved redundancy, which, when implemented, will reduce the likelihood of such events. Regards, Tim Bruijnzeels LIR Portal Service Manager RIPE NCC

1 0

Unplanned LIR Portal Downtime
by Tim Bruijnzeels 09 Sep '09

09 Sep '09

Dear Colleagues, We regret to inform you that the LIR Portal service has been unavailable since this morning, 06:30 (UTC), 9 September 2009. We are currently working to fix the problem. The cause of the outage is not yet known, though it is not related to service outage that occurred yesterday. We will provide further details once the issue has been resolved. Regards, Tim Bruijnzeels Service Manager LIR Portal RIPE NCC

1 0

Unplanned LIR Portal Downtime: Incident Report
by Tim Bruijnzeels 08 Sep '09

08 Sep '09

Dear Colleagues, This is an incident report regarding an LIR Portal service outage that occurred last night and earlier today. The outage started at 21:15 (UTC), Monday, 7 September, and services were restored at 08:15 (UTC) this morning. The outage was caused by a configuration error of the Apache web server. The RIPE NCC has strict upgrade procedures that our staff follow to prevent this, but they do leave some room for human error, and this outage was the result of such an error. To minimise the chance of this happening again, we plan to include automated monitoring of our Apache configuration syntax to our monitoring system. A separate issue was responsible for the longer than usual time it took to recognise and fix the problem. Our monitoring system is set up to send text messages to a 24/7 engineer in case of outages such as this. From our logs, we can see that the system did indeed try to send an SMS about the outage yesterday at 21:15 (UTC), but was unable to connect to our mobile service provider. To minimise the chance of this happening again, we will reconfigure our monitoring system to fall back to another provider in case a message can not be sent out. I hope that you find this explanation of the cause of the outage and the steps we are taking to prevent it from happening again useful. Regards, Tim Bruijnzeels Service Manager LIR Portal RIPE NCC

1 0

LIR portal unreachable
by Daniel Suchy 08 Sep '09

08 Sep '09

Hello, since yesterday night I'm observing problems with LIR portal connection. Planned maintenance or unplanned outage was not announced on obvious places. Connection to TCP port 443 (https) is closed by server immediately, browser reports that the network link was interrupted while negotiating a connection. Connection to TCP port 80 works (there's redirect to https). I verified this from several networks (AS) / browses. Someone could check on this problem. In addition, monitoring should be improoved I think, checks should be extended not only to monitor state of TCP port (open/closed), but also check application status (for example, nagios is able to monitor this). With regards, Daniel

1 0