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

Locally caching riswhois results
by Laurent Zimmerli 22 Jul '08

22 Jul '08

Hi list I'm making use of the riswhois service and would like to cache queries locally. However, I am not sure whether I can do it the way I want to. My idea is to store the ASN an the corresponding route of each query I execute. Before performing another query I would then check whether I already stored the ASN of a route which contains the IP for which I want to find the AS. Can I do that? Or is then the following case possible: I store an AS an its route -- say ASx, 123.0.0.0/8 -- whose IP range includes another one -- say ASy, 123.100.0.0/16. When I store ASx first and then query an IP of ASy, I will assign ASx to this IP instead of ASy. Is such a case possible? Or is there even another problem with my caching approach? Thanks for your time! Best, Laurent

2 1

IPv6 enabled for email to the RIPE NCC
by Henk Uijterwaal 18 Jul '08

18 Jul '08

Dear Colleagues, On Wednesday, 16 July, the RIPE NCC's new mail servers were enabled. As of this date, it is possible to send mail to the RIPE NCC with IPv6 as a transport medium. This setup has been extensively tested but if you see any problems, please send an e-mail to <ops(a)ripe.net> or phone +31 20 535 4444. Kind regards, The RIPE NCC -- ------------------------------------------------------------------------------ Henk Uijterwaal Email: henk.uijterwaal(at)ripe.net RIPE Network Coordination Centre http://www.amsterdamned.org/~henk P.O.Box 10096 Singel 258 Phone: +31.20.5354414 1001 EB Amsterdam 1016 AB Amsterdam Fax: +31.20.5354445 The Netherlands The Netherlands Mobile: +31.6.55861746 ------------------------------------------------------------------------------ Is one of the choices leaving the office open? Alan Greenspan on the next elections

1 0

Announcing new RIS de-bogon prefixes
by Ruben van Staveren 20 Jun '08

20 Jun '08

[Apologies for duplicate e-mails] Dear Colleagues, As part of our effort to de-bogonise new address blocks, we are now announcing the following prefixes on RRC03: 112.0.0.0/24 113.0.0.0/24 112.50.0.0/21 112.50.0.0/21 112.255.0.0/16 113.255.0.0/16 More information about the Routing Information Service (RIS) De- Bogonising New Address Blocks Project can be found at: http://www.ris.ripe.net/debogon/index.shtml Kind regards, Ruben van Staveren RIPE NCC, Engineer

2 1

Notification message change
by Denis Walker 18 Jun '08

18 Jun '08

[Apologies for duplicates] Dear Colleagues, With most updates to the RIPE Database, notification messages are sent out. Many of these notifications are hitting users' ticketing systems or arriving in mailboxes with auto-responders. The "Reply-to:" address in these notifications was <ripe-dbm(a)ripe.net>. Our help desk ticketing system was receiving hundreds of e-mails a month from these auto-responders. This was causing a serious operational problem for our Customer Services Department. To solve this problem, we have changed the e-mail header in the notification messages we send out. They now have the "From:" and "Reply-to:" addresses set to <unread(a)ripe.net>. As the name suggests, any replies to this address are not read by anyone and they are just dropped from our mail system. We have also made a small change to the introductory text to make it clear that these e-mails are auto-generated. We also clearly show users the e-mail reply address to use if they have an issue with the notification. This change was implemented today. It should not affect any users unless they parse the mail headers or the introductory text in the notification. Examples of the old and new notification messages are shown below. Regards, Denis Walker Business Analyst RIPE NCC Database Group Old notification message ____________________________________________________ To: user(a)somewhere.com From: RIPE Database Notifications <bitbucket(a)ripe.net> Subject: Notification of RIPE Database changes Reply-To: ripe-dbm(a)ripe.net Precedence: bulk Auto-Submitted: auto-generated Dear Colleague, This is to notify you that some object(s) in RIPE database which you either maintain or are listed as to-be-notified have been added, deleted or changed. The update causing these changes had the following mail headers: > From: user(a)somewhereelse.com > Subject: > Date: Tue, 17 Jun 2008 00:00:18 +0200 (CEST) > Reply-To: user(a)somewhereelse.com > MsgId: <2008061622> For assistance or clarification please contact: RIPE Database Administration <ripe-dbm(a)ripe.net> New notification message ____________________________________________________ To: user(a)somewhere.com From: RIPE Database Notifications <unread(a)ripe.net> Subject: Notification of RIPE Database changes Reply-To: unread(a)ripe.net Precedence: bulk Auto-Submitted: auto-generated Dear Colleague, This is to notify you that some object(s) in RIPE database which you either maintain or are listed as to-be-notified have been added, deleted or changed. This message is auto-generated. Please DO NOT reply to this message. If you do not understand why we sent you this message, or for assistance or clarification please contact: RIPE Database Administration <ripe-dbm(a)ripe.net> The update causing these changes had the following mail headers: > From: user(a)somewhereelse.com > Subject: > Date: Tue, 17 Jun 2008 00:00:18 +0200 (CEST) > Reply-To: user(a)somewhereelse.com > MsgId: <2008061622>

1 0

Emergency Maintenance Announcement
by Gerard Leurs 16 Jun '08

16 Jun '08

[Apologies for duplicates] Dear Colleagues, Today, Monday, 16 June, the RIPE NCC will carry out emergency maintenance work on some of our servers. As a result, the following services will be temporarily unavailable at times over the course of the day: - www.ripe.net - lirportal.ripe.net Delayed response times can also be expected for RIPE NCC Registration Services and Customer Services. We apologise for any inconvenience that this may cause. If you have any questions, please send an e-mail to <ops(a)ripe.net>. Regards, Gerard Leurs Operations Coordinator, RIPE NCC

1 0

Announcement on prefix size change for k.root-servers.net (AS25152)
by Wolfgang Nagele 12 Jun '08

12 Jun '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [Apologies for duplicates] Dear Colleagues, The RIPE NCC, as operator of k.root-servers.net, will announce the less-specific prefix 193.0.14.0/23 within the next few days. This is due to a change in our traffic engineering policies. Affected locations: *) AMS-IX (NL) *) LINX (UK) *) JP-NAP, DIX-IE (JP) *) NAP (US/FL) *) NIXI (IN) We advise you to check whether you are peering with AS25152 and, if so, to ensure that you are allowing the prefix mentioned above. These are the recommended filter settings for our peerings: Cisco: - ---cut--- ip prefix-list as25152-policy seq 10 permit 193.0.14.0/23 le 24 ip prefix-list as25152-policy seq 20 deny 0.0.0.0/0 le 32 - ---cut--- Juniper: - ---cut--- policy-statement as25152-policy { term accept { from { route-filter 193.0.14.0/23 prefix-length-range /23-/24 accept; } } term reject { then reject; } } - ---cut--- If you have any questions, please contact us at <kroot-ops(a)ripe.net>. Regards, - -- Wolfgang Nagele DNS System Engineer RIPE NCC Singel 258 1016 AB Amsterdam Tel: +31 20 535 4444 Fax: +31 20 535 4445 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIUPLEjO7G63Byy8cRAkUZAJ9/g2kKieUn54sLofkChlPug8+8ZQCeP1P8 HWnbQjvj/g17fOE5MAIXW+c= =Y/z1 -----END PGP SIGNATURE-----

1 0

Emergency maintenance announcement
by Razvan Oprea 10 Jun '08

10 Jun '08

[Apologies for duplicates] Dear Colleagues, Due to unforeseen circumstances, the RIPE NCC had to carry out emergency maintenance work on our core storage infrastructure today, 10 June, between 15:00 and 17:30 (UTC). RIPE NCC services affected during this period include: www.ripe.net ftp.ripe.net e-learning.ripe.net lirportal.ripe.net DNSMON We apologise for any inconvenience that this may have caused. If you have any questions about this, please send an e-mail to <ops(a)ripe.net>. Regards, Razvan Oprea Senior Systems Engineer, RIPE NCC

1 0

RIPE NCC Maintenance Announcement
by Chris Buckridge 22 May '08

22 May '08

[Apologies for duplicate e-mails] Dear Colleagues, From 10:00-18:00 (UTC) on Saturday, 24 May 2008, RIPE NCC staff will perform scheduled maintenance work on our core storage infrastructure. The following items will be unavailable at times during this maintenance period: - www.ripe.net - ftp.ripe.net - lirportal.ripe.net - e-learning.ripe.net The performance of dnsmon.ripe.net will be degraded during this period, and the website for k.root-servers.org will also be unavailable at times. We apologise for any inconvenience that this may cause. If you have any questions about this, please send an e-mail to <ops@localhost>. Regards, Brian Riddle IT Manager RIPE NCC

1 0

Outage report for mail updates to the RIPE Database
by Katie Petrusha 18 Apr '08

18 Apr '08

[ Apologies for duplicate mails ] Dear colleagues, From approximately 14:15 (UTC) on Thursday, 17 April 2008 to 09:00 (UTC) on Friday, 18 April 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. All the messages received by <auto-dbm(a)ripe.net> were stored on our mail server and the problem has now been resolved. All the saved update messages are currently being processed. If you sent an e-mail update to the RIPE Database service during this period, you will receive an acknowledgement message shortly. There is no need to re-send any update messages. We apologise for any inconvenience that this may have caused. Regards, Katie Petrusha Senior Software Engineer RIPE NCC

1 0

DNSMON document, ripe-429, available online
by Mark Dranse 17 Apr '08

17 Apr '08

[Apologies for duplicate e-mails] Dear Colleagues, At the RIPE 55 Meeting, Ondr(ej Surý (CZ.NIC) made a proposal to the RIPE NCC Services Working Group suggesting that the scope of the RIPE NCC's DNS Monitoring (DNSMON) service be extended to permit the monitoring of ENUM domains. During the meeting, the working group reached consensus and approved the proposal. The RIPE NCC has now implemented the requested changes. The DNSMON document has also been simplified and republished as a new RIPE Document. This document, ripe-429, "DNS Monitoring Service for Infrastructure Domains", can be found online at: http://www.ripe.net/ripe/docs/ripe-429.html Regards, Mark Dranse Information Services Manager RIPE NCC

1 0