October 2008 - ncc-services-wg

The new charging sceme
by Max Tulyev 31 Oct '08

31 Oct '08

Hi all, I see http://www.ripe.net/ripe/docs/charging2009.html is adopted, and charging for ancient resources such as PI and AS for third-parties is resurrected. So it means I have to find these guys and say hey, RIPE billing scheme is changed, so I want some money and a permanent agreement. But! As I pass them their mntners, I can't enforce them to do anything. How can I enforce them to sign an agreement and pay money? -- WBR, Max Tulyev (MT6561-RIPE, 2:463/253@FIDO)

1 0

Planned maintenance for ns.ripe.net, 4 November 08
by Sjoerd Oostdijck 30 Oct '08

30 Oct '08

[Apologies for duplicate emails.] Dear Colleagues, This message concerns people who have ns.ripe.net listed as a secondary DNS server for their reverse DNS zones. In order to improve the quality of our service, we are adding additional servers to our infrastructure. The effect of this change will be that we will perform zone transfers from more then one IP address within the ranges 193.0.0.0/22 and 2001:610:240::/48 as documented at: http://www.ripe.net/rs/reverse/reverse_howto.html On 4 November 2008 at 11:00 UTC, ns.ripe.net will move to a load-balanced solution. No noticeable downtime is expected. If you would like to make sure that we can properly transfer the zone from your server after the change, we recommend that you follow the following steps: - Increase the serial number in your zone's Start of Authority (SOA) record. - Wait for a zone transfer to be initiated from the 193.0.0.0/22 or the IPv6 address range. - Now you can compare the zone serials on your master server and ns.ripe.net. To compare the serials you can use tools like "dig", "drill" or "host -C" to query the SOA record and compare the serials on both servers. If you have any further questions about this message, please contact us at dns-help(a)ripe.net Regards, Sjoerd Oostdijck DNS Services RIPE NCC

1 0

LIR Portal Outage
by Trudy Prins 28 Oct '08

28 Oct '08

[Apologies for duplicate emails] Dear Colleagues, On Monday, 27 October 2008 between 20:33 - 22:38 (UTC) and Tuesday, 28 October between 00:25 - 00:41 (UTC), the LIR Portal was unavailable due to a power outage. We apologise for any inconvenience that this may have caused. Regards, Trudy Prins Manager Business Applications Department RIPE NCC

1 0

Outage Report for RIPE Database Updates
by Agoston Horvath 28 Oct '08

28 Oct '08

[Apologies for duplicate mails] Dear Colleagues, Between approximately 20:05 - 23:14 (UTC) on Monday, 27 October 2008, we experienced an outage in our RIPE Database updates service. During this period, it was not possible to connect to the syncupdates or webupdates services. During the outage, all the messages received by auto-dbm(a)ripe.net were stored on our mail server. If you sent an email update to the RIPE Database during the outage, you will have already received an acknowledgment. There is no need to re-send any update messages. We apologise for any inconvenience that this may have caused. Regards, Agoston Horvath Database Group RIPE NCC

1 0

Deleting unreferenced PERSON objects
by Denis Walker 16 Oct '08

16 Oct '08

[Apologies for duplicate emails] Dear Colleagues, We announced at RIPE 56 that the RIPE NCC would soon start to delete unreferenced PERSON and ROLE objects. This will begin in late November 2008. There are some people involved in the Internet industry who do not directly manage Internet resources but who have PERSON objects in the RIPE Database. If you fall into this category and you believe your PERSON object should not be deleted, you have the option to join the RIPE Database White Pages. This will prevent your PERSON object from being deleted. For further details, please see this web page: http://www.ripe.net/db/support/white-pages-instructions.pdf Regards, Denis Walker Business Analyst RIPE NCC Database Group

1 0

Maintaining DOMAIN objects
by Denis Walker 16 Oct '08

16 Oct '08

[Apologies for duplicate emails] Dear Colleagues, The RIPE Data Protection Task Force advised the RIPE NCC that all objects in the RIPE Database should be maintained. Maintaining Routing Policy Specification Language (RPSL) objects in the RIPE Database was optional for PERSON, ROLE and DOMAIN objects. All the DOMAIN objects in the RIPE Database are now maintained and protected. As there may have been a possibility to exploit this data if any advance warning had been made, the RIPE NCC did not publicly announce that it was going to add maintainers to unmaintained DOMAIN objects before doing so. For further details of what was done, please see this web page: http://www.ripe.net/db/support/security/domain/syntax.html Regards, Denis Walker Business Analyst RIPE NCC Database Group

1 0

Outage report for updates to the RIPE Database
by Denis Walker 13 Oct '08

13 Oct '08

[ Apologies for duplicate mails ] Dear colleagues, >From approximately 19:41 (UTC) to 20:15 (UTC) on Friday, 10 October 2008, some e-mail update messages to the RIPE Database service, auto-dbm(a)ripe.net, were not processed due to a problem with our system. During the same period it was not possible to connect to the syncupdates or webupdates services. All the messages received by auto-dbm(a)ripe.net were stored on our mail server. The problem was resolved on Friday evening. All the saved update messages have been processed. If you sent an e-mail update to the RIPE Database service during this period, you will have already received an acknowledgement message. There is no need to re-send any update messages. We apologise for any inconvenience that this may have caused. Regards, Denis Walker Business Analyst RIPE NCC Database Group

1 0

Reverse DNS lameness alerts
by Anand Buddhdev 01 Oct '08

01 Oct '08

[Apologies for duplicate emails] Dear Colleagues, Some of you received email messages last month from the RIPE NCC with alerts about lame DNS servers. These messages were generated as part of the RIPE NCC's DNS lameness project. Unfortunately, the alerts were not entirely correct, and showed all the servers of some reverse zones as lame. This was caused by programming errors in the software that produced the messages. We have identified these errors, and we are correcting them. We are also introducing additional tests and safeguards to improve the quality of our DNS lameness measurements. For more information on the RIPE NCC's DNS lameness project, please see: http://www.ripe.net/info/stats/dns-lameness/ Regards, Anand Buddhdev DNS Services Manager, RIPE NCC

1 0