May 2006 - db-wg - mailman.ripe.net

<auto-dbm@ripe.net> is slow this afternoon.
by RIPE Database Administration 17 May '18

17 May '18

Dear Colleagues, Because of a very high level of use this afternoon, the response time of <auto-dbm(a)ripe.net> is longer than normal. I have made contact with those who are responsible and I expect the situation to improve as the machine works through the queue. Please be patient. Obviously we at the RIPE NCC Database Group are continuously working to make the performance of the database as good as possible. However, we cannot make improvements in zero time. We thank you for your co-operation up to now and we ask for your continued co-operation so that everyone receives the best possible service. If you have anymore questions, please contact <ripe-dbm(a)ripe.net>. Regards, Ambrose Magee ____________________________ RIPE Database Administration.

2 2

Proposal to change the syntax of "nserver:" attribute
by Katie Petrusha 11 Jul '06

11 Jul '06

[Apologies for duplicate mails] Motivation: We plan to automate management of DNS delegation in the e164.arpa zone (ENUM). The provisioning system, with the RIPE Database as a front end, must support IPv6 glue records. It must also implement complete and consistent IPv4 glue record support. This will mean making changes to the RIPE Database syntax so that it specifies the glue record and update the delegation checks. This proposal covers that syntax. Proposal: We suggest changing the syntax of the "nserver:" attribute in DOMAIN objects as follows: nserver: [domain_name] /or/ nserver: [domain_name] [ipv4_address] /or/ nserver: [domain_name] [ipv6_address] where [domain_name] is the fully qualified DNS name of the name server without a trailing "." [ipv4_address] is an IPv4 address of the name server [ipv6_address] is an IPv6 address of the name server If [domain_name] is followed by an IP address, it must be inside the zone that is being delegated. Any level of a glue name is supported within the valid domain name syntax. Multiple name server lines will need to be used to specify multiple IP addresses for the same hostname. Examples: The following values would be allowed: domain: example.com nserver: ns1.test.net 168.0.0.1 nserver: ns1.test.net 0::0 nserver: ns1.example.com nserver: ns1.d1.example.com All other variants of the values will be rejected. End-of-line comments starting with '#' will be still allowed. Consequences for existing objects: We will not automatically modify any existing objects. Instead we suggest notifying the maintainers of objects that do not comply with the proposed syntax. This will cover around 150 objects. Consequences for the delegation checks: DNS checks applicable to glue records will be added to the Zone Delegation Checker (http://www.ripe.net/rs/reverse/delcheck/delcheck_descr.html) -- Katie Petrusha RIPE NCC

10 16

Re: Deprecation of ip6.int scheduled for 1 June 2006
by Andrei Robachevsky 02 Jun '06

02 Jun '06

Dear Colleagues, This is a reminder that from 1 June 2006, reverse delegations in the ip6.int DNS tree corresponding to IPv6 address space allocated by the RIPE NCC will no longer be supported. On 1 June 2006, RIPE NCC delegations will be deleted from the ip6.int zone. Following this we will remove the zones from the authoritative servers and delete the corresponding DOMAIN objects in the RIPE Whois Database. The maintainers of the DOMAIN objects to be deleted will also receive individual notifications 1 week prior to the deletion. This is being coordinated with other RIRs and is based on an IETF Best Current Practice document (RFC 4159). Regards, Andrei Robachevsky Chief Technical Officer RIPE NCC On 14 March 2006 Andrei Robachevsky wrote: > Dear Colleagues > > In August 2005, the IETF published RFC 4159: 'Deprecation of "ip6.int"', > as a Best Current Practice document. The RFC noted that maintenance of > "ip6.int" is no longer needed and called on the Regional Internet > Registries (RIRs) to decide when to stop providing support for the > domain. The RIRs have jointly agreed to do this on 1 June 2006. > > There will be a short presentation on this at the RIPE 52 Meeting in > Istanbul. You can find more information about this meeting at: > > http://www.ripe.net/ripe/meetings/ripe-52/index.html > > Regards > > Andrei Robachevsky > Chief Technical Officer > RIPE NCC > > > > >

1 1

please help, can't start whoisserver
by Nicolae Ghimbovschi 29 May '06

29 May '06

Hi everybody ! I'm a newbie in working with a whoisserver, and I can't start it, i get errors I have compiled and installed whoisserve-3.3.0 ,from RIPE site, under Fedora Core 5. #./build.sh --prefix=/opt/whoisd --disable-xmltest --disable-xslttest everything worked fine. But when I run to make the sample database I get errors. In files rip.conf.sample and sources.config.sample I have configured the following lines: in rip.conf.smaple RIPADMIN xmachine.fedora,3306,root,hello,RIPADMIN and in sources.conf.sample DATABASE SAMPLEDB host: xmachine.fedora port: 3306 trx_support: n user: root password: hello /DATABASE [root@xmachine bin]# ./make_db -c /opt/whois/conf/rip.config.sample -s SAMPLE -1 sqlhost=xmachine.fedora sqlport=3306 sqluser=root sqlpswd=hello sqldbname=SAMPLEDB npasses=1 = 10:27:16 Loading database [SAMPLEDB] (source [SAMPLE]) started = 10:27:16 Loading the database [SAMPLEDB] [see list in /dev/tty] *******************Sun May 28 10:27:17 EEST 2006****************** Creating tables\n Creating tables\n creating main database ERROR 1060 (42S21) at line 246: Duplicate column name 'interface_v6_lsp' creating RIPADMIN database Sun May 28 10:27:17 EEST 2006\n Making indexes\n ERROR 1146 (42S02) at line 1: Table 'SAMPLEDB.person_role' doesn't exist Sun May 28 10:27:18 EEST 2006\n Loading tables - 1 of 1 pass\n Sun May 28 10:27:18 EEST 2006 Loading /opt/whois/var/tmp/load/SAMPLE/sample.db.gz D: Making SQL connection to SAMPLEDB(a)xmachine.fedora ...OK starting processing stream Table 'SAMPLEDB.mntner' doesn't exist[SELECT object_id FROM mntner WHERE mntner='TEST-DBM-MNT' ] died: +315 modules/ud/ud_core.c ./load_all.sh: line 15: 3464 Done ${UNZIP1} ${object_file} 3465 | eval ${FILTER} 3467 Segmentation fault | $LOADER -L $1 -p ${PROPERTIES} -s ${SOURCE} *** ERROR: Loader failure [139]. Exiting\n ************** ERROR *************** *** 10:27:18 Error loading database=SAMPLEDB for source=SAMPLE, ./make_db exiting ************************************ ######################################################## ##when making an empty database I get the following ######################################################## [root@xmachine bin]# ./make_db -c /opt/whois/conf/rip.config.sample -s SAMPLE -0 sqlhost=xmachine.fedora sqlport=3306 sqluser=root sqlpswd=hello sqldbname=SAMPLEDB npasses=0 = 10:30:27 Loading database [SAMPLEDB] (source [SAMPLE]) started = 10:30:27 Loading the database [SAMPLEDB] [see list in /dev/tty] *******************Sun May 28 10:30:28 EEST 2006****************** Creating tables\n Creating tables\n creating main database ERROR 1007 (HY000) at line 1: Can't create database 'SAMPLEDB'; database exists ERROR 1060 (42S21) at line 246: Duplicate column name 'interface_v6_lsp' creating RIPADMIN database ERROR 1007 (HY000) at line 2: Can't create database 'RIPADMIN'; database exists Sun May 28 10:30:28 EEST 2006\n Making indexes\n ERROR 1146 (42S02) at line 1: Table 'SAMPLEDB.person_role' doesn't exist Sun May 28 10:30:28 EEST 2006\n Making more indexes\n Sun May 28 10:30:28 EEST 2006 creating indexes for aux tables ERROR 1146 (42S02) at line 4: Table 'SAMPLEDB.tech_c' doesn't exist Sun May 28 10:30:28 EEST 2006 creating indexes for leaf tables ERROR 1146 (42S02) at line 1: Table 'SAMPLEDB.names' doesn't exist Sun May 28 10:30:28 EEST 2006 saving CURRENTSERIAL=22 ERROR 1146 (42S02) at line 1: Table 'SAMPLEDB.serials' doesn't exist Finished Sun May 28 10:30:28 EEST 2006 = 10:30:29 Loading database [SAMPLEDB] (source [SAMPLE]) finished without errors ######################################################## ##when checking the database ######################################################## [root@xmachine bin]# ./whois-server -c /opt/whois/conf/rip.config.sample -p test.pid Configuration [/opt/whois/conf/rip.config.sample]: /opt/whois/log/riperr/riperrlog Check the DB Checking the Database [SAMPLEDB]...died: +230 modules/ud/ud_recover.c Segmentation fault [root@xmachine bin]# ./whoisd_start Starting whois-server daemon with configuration /opt/whois/conf/rip.config.sample from /opt/whois/bin ./whoisd_start: line 174: 3639 Segmentation fault $NOHUP_NICENESS $WHOISRIP -p $pid_file -c ${CONFIG} >>$err_log 2>&1 mv: cannot stat `core': No such file or directory ######################################### #from Error log: ######################################### Warning: undefined configuration variable: SAWFILE Warning: undefined configuration variable: RIR Error: Incomplete configuration file. Was this intended ??? 2 configuration variables undefined. died: +168 modules/sq/mysql_driver.c 060528 10:39:45 whoisd crashed & restarted\n/opt/whois/bin/whois-server -c /opt/whois/conf/rip.config.sample.q\n 060528 10:39:46 /opt/whois/bin/whois-server -p /opt/whois/bin/whois- server.pid -c /opt/whois/conf/rip.config.sample.q Configuration [/opt/whois/conf/rip.config.sample.q]: Warning: undefined configuration variable: SAWFILE Warning: undefined configuration variable: RIR Error: Incomplete configuration file. Was this intended ??? 2 configuration variables undefined. Mandatory variable(s) undefined <<<<<<<<<<<<<<< >>>>>>>>>>> Best Regards, Nicolae

2 1

Mike Simkins is out of the office.
by Mike.Simkins＠sungard.com 28 May '06

28 May '06

I will be out of the office starting 26/05/2006 and will not return until 30/05/2006. I will respond to your message when I return. If you have an urgent issue - please call the IOC at 1-800-41-1181 where someone will be able to help you immediately

1 0

RIPE 52 Draft Minutes of the DB WG meeting posted to web site
by Nigel Titley 26 May '06

26 May '06

Folks, The final draft minutes have been sent to the RIPE NCC webmaster for posting to the RIPE website. You *all* failed to spot that I misnumbered the action points as 51.n rather than 52.n (actually, so did I until I extracted the actions ready for uploading to the web site). Enjoy Nigel

1 0

RIPE 52 Draft Minutes of the DB WG meeting (Final Call)
by Nigel Titley 24 May '06

24 May '06

Folks, Having posted the 2nd draft of the minutes on the 8th May and having received no comments I am assuming that these are now acceptable as a record of the RIPE 52 meeting. I'll give it until the end of the week and then post the minutes and actions to the DB-WG website. Thanks to all who commented Nigel

1 0

Database query tool for ip allocations
by Fuat Demir (Garanti Teknoloji) 24 May '06

24 May '06

Hi, I'm looking for a tool that sends a query to the database whether the source ip is in the db or not. The database which will be looked up for the query should contain the ip allocations and ISP ip blocks of the all RIR's (RIPE, ARIN, LACNIC, APNIC, AfriNIC) and it must be keep updated in a period of time, for example, daily. The tool will give permission or restriction to the packets by sending query to the updated database and new allocations will not be discarded. How could i achieve this ? Thank you. Fuat Demir Garanti Technology This message and attachments are confidential and intended solely for the individual(s) stated in this message. If you received this message although you are not the addressee, you are responsible to keep the message confidential. The sender has no responsibility for the accuracy or correctness of the information in the message and its attachments. Our company shall have no liability for any changes or late receiving, loss of integrity and confidentiality, viruses and any damages caused in anyway to your computer system. Bu mesaj ve ekleri, mesajda gonderildigi belirtilen kisi/kisilere ozeldir ve gizlidir. Bu mesajin muhatabi olmamaniza ragmen tarafiniza ulasmis olmasi halinde mesaj iceriginin gizliligi ve bu gizlilik yukumlulugune uyulmasi zorunlulugu tarafiniz icin de soz konusudur. Mesaj ve eklerinde yer alan bilgilerin dogrulugu ve guncelligi konusunda gonderenin ya da sirketimizin herhangi bir sorumlulugu bulunmamaktadir. Sirketimiz mesajin ve bilgilerinin size degisiklige ugrayarak veya gec ulasmasindan, butunlugunun ve gizliliginin korunamamasindan, virus icermesinden ve bilgisayar sisteminize verebilecegi herhangi bir zarardan sorumlu tutulamaz.

1 0

Proposal for returning IRT objects
by Denis Walker 16 May '06

16 May '06

[Apologies for duplicate mails] Proposal for returning IRT objects Motivation ---------- The original proposal for the IRT object (ripe-254) did not make adequate provision for presenting the irt information to the user. A new query flag ("-c") was introduced. Because of the way this flag was implemented and the objects it returned, it was not considered intuitive or helpful. It can also cause confusion. A discussion held at the RIPE 51 meeting decided that the original implementation was a misunderstanding of the requirements. For more information, see AOB in the Database Working Group minutes: http://www.ripe.net/ripe/wg/db/minutes/ripe-51.html There was further discussion at the RIPE 52 meeting, details of which can be found at: http://www.ripe.net/ripe/maillists/archives/db-wg/2006/msg00052.html Objectives ---------- - To increase the availability of the irt information to users. - To promote the use of the IRT object. - To make it easier for third party tool writers to find the correct contacts. Background ---------- There has been confusion in the past about the implementation of the IRT object. We have been studying the concept and looking deep into the whois query code. Our understanding of how this works now, and how the community wants it to work in the future, has changed. This proposal outlines the current behaviour and what we now understand to be the desired behaviour. Current behaviour ----------------- A standard query for address space returns the queried inetnum and related objects. This does not include an IRT object, even if it is directly referenced by the queried INETNUM object. By using the "-r" flag, the related personal objects are filtered out but ROUTE objects are still returned. By using the "-c" flag, an INETNUM object is returned with a referenced IRT object and objects related to this INETNUM. This may not be the INETNUM in the query. No ROUTE objects are returned. If no (less specific) INETNUM references an IRT object, nothing is returned. By using the "-rc" flags, the related personal objects are filtered out, including the IRT object. The only object returned is the referencing INETNUM object, which may not be the one in the query. So it is not possible to find IRT objects without returning personal objects related to the referencing INETNUM object. New behaviour ------------- A standard query for address space returns the queried INETNUM and related objects. This does not include an IRT object, even if it is directly referenced by the queried INETNUM object. This is the same as the current behaviour. We propose to change this default behaviour at the second stage of implementation (see Implementation below). By using the "-r" flag, the related personal objects are filtered out but ROUTE objects are still returned. A standard query for address space including the "-c" query flag returns the queried inetnum and related objects. This will also include an IRT object referenced by the queried INETNUM object or the closest less specific INETNUM object, if one exists. It will also still include any ROUTE objects. By using the "-rc" flags, the related personal objects are filtered out. The IRT object will still be returned along with any ROUTE objects. When using any other address space query flags (lLmMxb) or querying for other object types, query behaviour remains the same as the current behaviour. If the "-c" query flag is used, it will be ignored. Implementation -------------- We propose a two stage implementation. The majority of the address space queries are made without any specific flags. We therefore propose to change the behaviour to return an IRT object by default (if one exists) only at the second stage. For the first stage, we propose changing the behaviour of the "-c" flag and the "-rc" flag combination as described above. This should not make any fundamental changes to the way the queries work. Existing tools and scripts should not fail. The web query form on www.ripe.net will add the "-c" flag to address space queries, making it a default. This only occurs if no other address space query flags (lLmMxbc) are present. At the second stage, the query server will add the "-c" flag to any address space query that does not include any of the address space query flags (lLmMxbc). This will make standard queries return IRT objects by default. This second stage changes the current behaviour of queries. This may break some tools and scripts. We can mitigate this by providing new query flags or using existing ones in different ways so that the behaviour resulting from the first stage of implementation can be reproduced. Tool writers ------------ Currently any third party tools that use the "-c" flag to find IRT objects run the risk of being blocked for returning too many personal objects. With the new behaviour, the "-rc" flags can be used to return the IRT objects without the personal objects. If only the IRT object is needed, "-rc -T irt" can be used. Notes ----- Any references to INETNUM and ROUTE objects also imply INET6NUM and ROUTE6. A consequence of this change is the return of an object with no direct reference from the queried object. With grouping turned on (default without "-G"), we assume that the IRT object should be grouped with the queried INETNUM object. -- Denis Walker Software Engineering Department RIPE NCC

1 0

Draft Minutes of the RIPE 52 DB-WG meeting
by Nigel Titley 15 May '06

15 May '06

Please find enclosed the first rough draft of the minutes. Please check your action points and make corrections to me. Thanks Nigel <<DB-minutes.txt>>

10 17

Maintenance announcement
by Trudy Prins 15 May '06

15 May '06

[Apologies for duplicate mails] Dear Colleagues, On Thursday, 18 May 2006 the following services will be unavailable from 05:00 - 06:00 GMT: - RIPE Whois Test Database - Internet Registry Information Service (IRIS) Server - Routing Registry Consistency Check (RRCC) Database These services will be unavailable while we perform important server maintenance work. We apologise in advance for any inconvenience. If you have any questions or concerns about this, please e-mail: <ripe-dbm(a)ripe.net>. Regards, Trudy Prins User Support Coordinator Software Engineering Department

1 0

whois update service was paused
by Trudy Prins 11 May '06

11 May '06

[Apologies for duplicate mails] Dear Colleagues, Yesterday, we deployed several bug fixes for the whois server software. The fixes should improve ORGANISATION object name handling. During the work, the whois update service was paused for around two hours. We apologise for the inconvenience. If you have any questions or concerns about this, please e-mail <ripe-dbm(a)ripe.net>. Regards, Trudy Prins User Support Coordinator Software Engineering Department

1 0

clients statistics
by md＠Linux.IT 10 May '06

10 May '06

I'd like to see published on the RIPE web site statistics about the -V parameter used by whois clients to identify themselves to the server. Does this need a formal proposal or is something which NCC staff can just implement quickly? -- ciao, Marco

1 0

Announcement Routing Registry Training Courses
by RIPE NCC Training Services 09 May '06

09 May '06

Dear Colleagues The RIPE NCC Training Services Department invites you to register for one of our upcoming Routing Registry Training Courses: Date: Friday 4 August 2006 Time: 0900 - 1700 Location: Warsaw, Poland And Date: Friday 1 September 2006 Time: 0900 - 1700 Location: Reykjavik, Iceland 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

RE: [db-wg] Draft Minutes of the RIPE 52 DB-WG meeting
by Nigel Titley 04 May '06

04 May '06

> No, after Manchester the agreement was to return the irt > record relevant > to the queried ip/network. > This is subtly different from the behaviour of -c, which may return a > less specific inetnum object if the irt record is referenced by it. And this, if I recall correctly was, at the heart of the argument in Istanbul Nigel

1 0

RIPE 52 Draft Minutes of the DB WG meeting (2nd Draft)
by Nigel Titley 04 May '06

04 May '06

Dear All, Well, I'm quite gratified that people actually read the minutes. Usually I circulate them on the mailing list and get no response at all. I think I've folded in most of the corrections and attach a 2nd version. Thanks to those who have made factual corrections. I published the minutes as quickly as I could so we could get them correct while things were fresh in our minds, hence the somewhat unpolished look. Once we've got the content right I'll do a final polish. All the best Nigel <<DB-minutes.txt>>

1 0

updated RIPE Whois Database User Manual
by Trudy Prins 04 May '06

04 May '06

[Apologies for duplicate e-mails] Dear Colleagues, We are pleased to announce the publication of an updated RIPE Whois Database User Manual. ripe-375 RIPE Whois Database User Manual: Getting Started The content has been revised and updated and we have improved the wording to make it clearer. We have also added extra information about 'webupdates'. You can find the document at: http://www.ripe.net/ripe/docs/db-start.html Regards, Trudy Prins User Support Coordinator Software Engineering Department RIPE NCC

1 0