- db-wg - mailman.ripe.net

Concerning the authentication for route object creation
by Hendrik T Voelker 04 Apr '07

04 Apr '07

Dear RIPE, dear Colleagues. I'd like to discuss a topic which most likely has already been discussed several times - only I have not seen that so far. If so, please excuse the 100th time being asked about it and just point me to results of these discussions. Anyway, here we go: According to http://www.ripe.net/info/faq/db/route-creation-IP-space-check.html if it is found that there is no exact matching route object already in existence in the RIPE DB, the less specific route is examined. If one is found deciding for authentication are then contained mnt-routes, mnt-lower or mnt-by fields. What annoys me here is, that holes are completely disregarded, meaning so even if because of defined holes the route object is not authoritative for a network, nonetheless it's authentication data is used. As we have several larger aggregated routes and additional some routes for IP allocations that have a status of "ALLOCATED UNSPECIFIED" we have to update our route objects to include maintainers for other companies so that they become able to maintain PI allocations. If the authentication process would regard holes all we would have to do would be defining a hole once, and not have to change the mnt-routes for a network for every provider change. This might ease the daily business of us all slightly. Cheers Hendrik -- Hendrik T. Voelker HTV5-RIPE EMEA Registrar Team Verizon Deutschland GmbH Sebrathweg 20 D-44149 Dortmund GERMANY http://www.verizonbusiness.com/de/ tel +49-231-972-1565 fax +49-231-972-2587 PubKey 1024D/92479A5D EC1B 76F2 D69D 11C6 2611 5CD1 5269 9351 9247 9A5D Verizon Deutschland GmbH - Sebrathweg 20, 44149 Dortmund, Germany - Amtsgericht Dortmund, HRB 14952 - Gesch�ftsf�hrer: Donald Badoux - Vorsitzender des Aufsichtsrats: Mark Kearns

1 0

RIPE NCC Network Maintenance 1700 UTC (1900 CEST) Thurday 5 April 2007
by Mark Guz 03 Apr '07

03 Apr '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [apologies for duplicates] Dear Colleagues, On Thursday 05/04/2007, between 17:00 and 19:00 (UTC), the RIPE NCC will carry out planned maintenance work on our core network infrastructure. RIPE NCC services will be temporarily unavailable during this period. We apologise for any inconvenience that this may cause. This work is due to the deployment of a new section of dark fibre between two of our PoPs If you have any questions about this, please send an e-mail to: ops(a)ripe.net Regards Mark Guz Senior Engineer Operations Department RIPE NCC http://www.ripe.net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGEhqgl42z2L2N9gERAofHAKClFauaor8xhKENLD4dp5PSfN9MFQCfZhCh D1RBdhQbWlox3dtzLzLPvLE= =g9jU -----END PGP SIGNATURE-----

1 0

NOC / Lookinglass Information in the RIPE DB
by Jeroen Massar 29 Mar '07

29 Mar '07

Hi, I am probably approaching this from the wrong way, in that case point me at the right way so that I can do it in the correct way. It needs discussion first anyway, so here we go: RIPE currently has a couple of projects going on which help in solving network connectivity issues, amongst those of course the really nice RIS tool (I love BGPPlay btw :) and the debogon projects. The latter project can be used by a network admin to check if that, to be debogonized network, is reachable. This does not help with network problems that might occur at other places. Now what if we could have an object in the RIPE registry that would explain us where to find Looking Glasses that are applicable for a prefix? I am thinking of something in the area of the following: route: 192.0.2.0/24 descr: Documentation Network origin: AS23456 lookingglass: http://noc.as23456.net/lg/ reachable: icmp:192.0.2.1 reachable: http://192.0.2.1 mnt-by: RIR-MNT source: RIPE # Filtered One could debate that maybe putting the proposed 'lookingglass' and 'reachable' addresses might be better suited in the ASN object. Another option to store this data would be to create a new 'noc' object and to have the details in there. The above information, when available, could then easily allow operators who have a problem with a certain prefix to find the lookingglass which allows them to look at the problem from the remote angle, without having to contact that NOC. This will give people with network problems a better insight, which allows for better reporting of the issue, and thus hopefully faster resolution of issues. There are indeed resources (eg www.traceroute.org) which list these items, but it is much more scalable and reliable to have it in the RIPE registry. What do folks think about this? Useless? Useful? Nonsense? ??? :) Greets, Jeroen

4 4

whois-server friendly client programming
by Henning Brauer 02 Mar '07

02 Mar '07

Hi, I am writing a tool to generate OpenBGPD filters from the policy specification in aut-num objects. Naturally, this involves sending a lot of queries to the whois servers: -one for the aut-num in question -one for every as-set given in the policy -one for every member of these as-sets, and recursively for their members, until we're down to an all-aut-num list -for each aut-num, a query for the routes it exports (-i origin <AS>) I do have extensive caching in place, all responses are beeing cached (or rather, the parse result), so no query is ever sent twice. nontheless, a lot of queries remain. right now, I have whois.ripe.net hardwired, of course this is going to change before the tool is released. I am using "-r -a -T <objtype> <object>" for aut-num and as-set, and "-r -a -T <objtype> -i origin <as>" for route objects. Questions: can I make life easier for the whois servers by using another set of query options? what is a good default whois server? whois.ripe.net? whois.radb.net? of course, I run into the penalty delays the whois server imposes because of the amount of queries I send. How do I deal with that? do nothing, just accept the delay (that's how it is now)? is it possible (and feasable!) to mirror the entire IRR? is this documented somewhere? I'd happily point to that documentation and recommend running a local mirror in the manpage if that is feasable. the forced delays also make development pretty painful ;( Thanks & Greetz Henning Brauer -- Henning Brauer, hb(a)bsws.de, henning(a)openbsd.org BS Web Services, http://bsws.de Full-Service ISP - Secure Hosting, Mail and DNS Services Dedicated Servers, Rootservers, Application Hosting - Hamburg & Amsterdam

4 4

Deprecation of CRYPT-PW authentication method from the RIPE Database
by Agoston Horvath 21 Feb '07

21 Feb '07

[Apologies for duplicate mails] Dear Colleagues, The CRYPT-PW deprecation project ends today, Wednesday, 21 February 2007. From today, the following changes will apply: * CRYPT-PW passwords will be disabled in the syntax * CRYPT-PW passwords will be disabled in authorisation * CRYPT-PW passwords will be removed from existing maintainer objects If a maintainer object contained CRYPT-PW passwords only, the passwords were replaced with a randomly generated MD5-PW password. If a maintainer object used an authentication method that was not CRYPT-PW, the CRYPT-PW auth: lines have been removed. To retrieve the removed CRYPT-PW passwords, please visit: https://www.ripe.net/cgi-bin/crypt2md5.cgi The RIPE NCC has recently upgraded its mail servers to support TLS/SSL. If you are updating the RIPE Database by email, please use an SMTP server that supports TLS/SSL. This will protect your data where possible. The use of an SMTP server that supports TLS/SSL is particularly important if you use cleartext password (MD5-PW) for authentication instead of PGP or X509. More information is available at: http://ripe.net/news/tls.html Notification e-mails will be sent today to over 5100 e-mail addresses. A total of 2337 objects had CRYPT-PW authentication only. Another 179 objects had other authentication methods in addition to CRYPT-PW. More information about the project is available at: http://www.ripe.net/db/support/security/crypt-pw_deprecation/ If you have any questions, contact: ripe-dbm(a)ripe.net. Regards, Agoston Horvath Database Group RIPE NCC

1 0

RIPE NCC Planned Maintenance, February/March 2007
by RIPE NCC 19 Feb '07

19 Feb '07

[Apologies for duplicate e-mails] Dear Colleagues, The RIPE NCC will perform maintenance work that will affect a number of servers. The maintenance work will take place on: Tuesday, 20 February 2007 between 18:00 and 20:00 UTC Thursday, 22 February 2007 between 18:00 and 20:00 UTC Tuesday, 27 February 2007 between 18:00 and 20:00 UTC During this maintenance, individual servers may experience short outages. We apologise for any inconvenience that this may cause. If you have any questions about this, please send an e-mail to ops(a)ripe.net. Regards, James -- James Aldridge, Senior Systems & Network Engineer, RIPE NCC

1 0

Announcement Routing Registry Training Courses
by RIPE NCC Training Services 12 Feb '07

12 Feb '07

Dear Colleagues The RIPE NCC Training Services Department invites you to register for one of our upcoming Routing Registry Training Courses: Date: Thursday 5 April 2007 Time: 09:00 - 17:00 Location: Manama, Bahrain Hosted by: 2Connect:http://www.2connectbahrain.com/ AND Date: Thursday 26 April 2007 Time: 09:00 - 17:00 Location: Budapest, Hungary AND Date: Friday 4 May 2007 Time: 09:00 - 17:00 Location: Amsterdam, Netherlands AND Date: Friday 25 May 2007 Time: 09:00 - 17:00 Location: Moscow, Russian Federation AND Date: Thursday 7 June 2007 Time: 09:00 - 17:00 Location: London, United Kingdom ND Date: Friday 29 June 2007 Time: 09:00 - 17:00 Location: Rome, Italy The main objective of the "Routing Registry Training Course" is to familiarise the LIRs with the features of the Routing Registry, while introducing the relevant tools and services of the RIPE NCC. The course also offers practical exercises. OVERVIEW OF TOPICS COVERED IN THE COURSE: - Routing Registry as a part of the RIPE Whois Database and the Internet Routing Registry (IRR) - Specifying routing policies using (RPSL) Routing Policy Specification Language and the RtConfig tool - IRRToolSet - Routing Information Service (RIS) - Routing Registry Consistency Check Project Please note that this is an advanced course. It will: - NOT teach the basics of routing - NOT teach the basics of RIPE Database operations - NOT describe how to receive Internet resources from the RIPE NCC - NOT describe how to operate a Local Internet Registry (LIR) The target audience of the course are technical staff of LIRs: e.g. network operators, engineers etc. This course is not intended for administrative or management staff (e.g. Hostmasters) . It is assumed that all attendees will be familiar with Border Gateway Protocol routing and with the RIPE Database (i.e. creating/modifying objects). This course is based on interactive exercises in a local network set-up. Please bring your laptops equipped with the following: - A working Ethernet card, - Three meters of Ethernet cable, - A secure connection client, - A web browser. Please be prepared to share your laptop (or at least allow another attendee to "look over your shoulder") if necessary. The course is free of charge. We provide lunch and printed training materials. We do not cover any of your travel expenses or accommodation. We give all of our training courses in English. You can find more information about the course at: http://www.ripe.net/training/rr/ How to register: --------------------- You can register up to two people from your LIR for each course. (If there are places left nearer the time of the course, you can register more people). To register for this course, you can either use the LIR Portal at: https://lirportal.ripe.net/lirportal/training/course-list.html Or the online registration form on our website: http://www.ripe.net/cgi-bin/trainingform.pl.cgi If you have any questions, send an e-mail to <training(a)ripe.net>. Kind regards, Rumy Kanis Training Services Manager RIPE NCC

1 0

Transfer of ERX resources from RIPE NCC to AfriNIC
by Andrei Robachevsky 12 Feb '07

12 Feb '07

[Apologies for duplicate e-mails] Dear colleagues, On Wednesday 14 February 2007, the RIPE NCC will transfer management of several Early Registration PI address blocks and Autonomous System Numbers to AfriNIC. A list of the resources being transferred is available at: http://www.ripe.net/projects/erx/transferred.html You can find more information about AfriNIC at: http://www.afrinic.net For more information on the ERX project, see: http://www.ripe.net/projects/erx/index.html Regards, Andrei Robachevsky, Chief Technical Officer RIPE NCC

1 0

New mirrored database: ARIN Routing Registry
by Katie Petrusha 12 Feb '07

12 Feb '07

[Apologies for duplicate mails] Dear Colleagues, We have added the ARIN-RR database to our list of mirrored databases. The ARIN-RR database contains Routing Registry (RR) data from rr.arin.net. A list of all mirrored databases is available at: http://www.ripe.net/db/mirrored.html If you have any questions about this, please contact: ripe-dbm(a)ripe.net. Regards, -- Katie Petrusha Database Group RIPE NCC

1 0

Multiple export statements per peer-as in aut-num objects
by Jan Wagner 12 Feb '07

12 Feb '07

Hi there, is the following supported? export: to AS54321 announce AS12345 export: to AS54321 action aspath.prepend (AS12345, AS12345); announce AS12345:AS-BACKUPDOWN We try to use rtconfig to generate filter lists, but only the first export line is used. Is this a bug or are multiple export lines not supported by rpsl? Thank and with kind regards, Jan. -- Never write mail to <waja(a)spamfalle.info>, you have been warned! -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GIT d-- s+: a- C+++ UL++++ P+ L+++ E- W+++ N+++ o++ K++ w--- O M V- PS PE Y++ PGP++ t-- 5 X R tv- b+ DI- D++ G++ e++ h-- r+++ y+++ ------END GEEK CODE BLOCK------

1 0