- db-wg - mailman.ripe.net

IPV6 Whois
by DB-News 27 Jan '03

27 Jan '03

[apologies for duplicate messages] Dear Colleagues, We are happy to announce the availability of RIPE Whois servers on IPv6 network. It is now possible to query whois.ripe.net and test-whois.ripe.net from an IPv6 host, using an IPv6 enabled whois client. If your system doesn't already have one, you can find the latest RIPE Whois client at: ftp://ftp.ripe.net/ripe/tools/ripe-whois-latest.tar.gz You can read the full anouncement at: http://www.ripe.net/ripencc/pub-services/db/whois-ipv6.html Best regards, -- Can Bican Database Group RIPE NCC

3 3

Organisation object proposal
by Shane Kerr 26 Jan '03

26 Jan '03

Colleagues, Attached please find a proposal for adding the organisation object type to the RIPE Database. As always, discussion about the document can be done on this mailing list. There will be a brief presentation at the RIPE meeting next week about organisation objects. -- Shane Kerr RIPE NCC

5 4

IPv6 Whois update
by Shane Kerr 23 Jan '03

23 Jan '03

Colleagues, As you may have seen on the list, there were a few reachability problems with the new IPv6 Whois service. We believe these are configuration related, and have a workaround allowing queries to WHOIS.RIPE.NET to work while we research it further. If you have network issues with this service please e-mail <ripe-dbm(a)ripe.net>. We also have heard some problems people are having with their Whois clients giving them errors querying the RIPE Whois server. These can occur in the case that: - The Whois client has IPv6 support. - The host computer does not have working IPv6 support. The client will: 1. Get the AAAA record for WHOIS.RIPE.NET. 2. Try to connect to the IPv6 address. 3. Fail because there is no IPv6 stack/address/router/etc. If you are experiencing this problem, you may be able to fix it by enabling IPv6 on your host (so that the IPv6 queries work), disabling IPv6 *completely* on your host (so that no AAAA records are returned), or by using another Whois client. The RIPE Whois client will work in this case, and is available from our FTP site: ftp://ftp.ripe.net/tools/ripe-whois-latest.tar.gz -- Shane Kerr RIPE NCC

3 2

RE: [ipv6-wg@ripe.net] IPV6 Whois
by matthew.ford＠bt.com 23 Jan '03

23 Jan '03

I'm getting Type 1 (Unreachable) Code 1 (Administratively Prohibited) messages back from 2001:7f8:1::a500:3333:1 - luckily the client falls back to IPv4 and that works just fine ;-) Mat. > -----Original Message----- > From: Pim van Pelt [mailto:pim@ipng.nl] > Sent: 23 January 2003 14:17 > To: ripe-dbm(a)ripe.net > Cc: db-wg(a)ripe.net; ipv6-wg(a)ripe.net > Subject: Re: [ipv6-wg(a)ripe.net] IPV6 Whois > > > | We are happy to announce the availability of RIPE Whois > servers on IPv6 > | network. It is now possible to query whois.ripe.net and > test-whois.ripe.net > | from an IPv6 host, using an IPv6 enabled whois client. If > your system doesn't > | already have one, you can find the latest RIPE Whois client at: > Hi Can, > > I cannot reach the server from AS12859, nor from AS8954. > > --- whois.ripe.net ping6 statistics --- > 2 packets transmitted, 0 packets received, 100% packet loss > > A traceroute from me (2001:7b8:3:17:202:b3ff:fe10:d926) to you gives: > 1 dapje-gw.ipv6.network.bit.nl 0.383 ms 0.286 ms 0.269 ms > 2 jun1.telecity.ipv6.network.bit.nl 1.537 ms 1.552 ms 1.505 ms > 3 nikipv6.ripe.net 3.378 ms 3.035 ms 3.111 ms > 4 nikipv6.ripe.net 4.432 ms !P 3.248 ms !P 3.288 ms !P > > And telnetting to port 43 of whois.ripe.net does not do much: > $ telnet 2001:610:240:0:193::135 whois > Trying 2001:610:240:0:193::135... > ^C > > Please advise. > -- > ---------- - - - - -+- - - - - ---------- > Pim van Pelt Email: pim(a)ipng.nl > http://www.ipng.nl/ IPv6 Deployment > ----------------------------------------------- > >

1 0

RRCC scripts beta release
by DB-News 23 Jan '03

23 Jan '03

[apologies for duplicate messages] Dear Colleagues, We are happy to announce the beta release of RRCC scripts. Routing Registry Consistency Check, or RRCC project had already its web interface, where you can check the accuracy of your data in the RIPE Routing Registry and Whois Database. Per-maintainer reports are also available as in an e-mail interface. For more information, please visit http://www.ripe.net/rrcc/ . Now you can build you own RRCC database yourself, using RRCC scripts, which you can find at ftp://ftp.ripe.net/ripe/dbase/software/RRCC-0.2.tar.gz Using these scripts, you can check the consistency of other routing registries as well. Please contact rrcc(a)ripe.net for any comments. Best regards, Engin Gunduz RIPE NCC Database Group

1 0

draft agenda (v1), for DB-WG meeting, RIPE 44, Amsterdam, NL
by Wilfried Woeber, UniVie/ACOnet 22 Jan '03

22 Jan '03

Dear WG list members, dear "Meeting Role" @ the NCC, dear WG-Chairs! Attached please find the 1st, very preliminary, draft: Proposed Agenda for the DB-WG Meeting at RIPE 44 in Amsterdam, NL. For the moment this is pretty much "work in progress", but something has to be printed on paper. I'll add the usual "syntactic sugar" later... As usual, if you have any comments, corrections or additions please get back to me directly. Looking forward to see many of you in Amsterdam, Wilfried. ______________________________________________________________________ Proposed Agenda for the Database Working Group Meeting 1. Draft A. Administrative stuff (WW, chair) 10 min B. Action Items 15 min C. DB update (RIPE NCC, Shane K.) 20 min D ERX (Status report and future plans) (RIPE NCC) 15 min E. Organisation object proposal (RIPE NCC, Shane K.) 10 min F. status: SUB-ALLOCATED PA (Space.Net, Gert D.) 10(?) min G. reclaim: - Attribut (Space.Net, Gert D.) 10(?) min H. allowing "generated" attributes in updates (WW et.al.) 10 min I. Key Certificates to person: role: ? 10 min Y. Input from other WGs . Z. AOB: . ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ WW, 22-JAN-2003 09:53:47 UTC _________________________________:_____________________________________ Wilfried Woeber : e-mail: Woeber(a)CC.UniVie.ac.at UniVie Computer Center - ACOnet : Tel: +43 1 4277 - 140 33 Universitaetsstrasse 7 : Fax: +43 1 4277 - 9 140 A-1010 Vienna, Austria, Europe : RIPE-DB: WW144, PGP keyID 0xF0ACB369 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ "Only one thing in life is certain: init is Process #1"

2 1

Re: contacts
by leo vegoda 20 Jan '03

20 Jan '03

Dear Mouse, You are correct in stating that the RIPE NCC does not manage the contact information stored in the RIPE Database. Contact information is currently published in "person:" or "role:" objects managed by database users. The RIPE NCC and other database users reference contact information from various objects describing networks. The current design allows the people publishing the contact data to update it independently from the people publishing the network objects that reference it. It should also be noted that the "e-mail" attribute is optional for the "person:" object in the current database specification. The RIPE NCC takes direction from consensus reached within the RIPE community. If you would like to bring about a change then please bring a proposal to the mailing list of the appropriate working group. Information about RIPE working groups may be found at: <http://www.ripe.net/ripe/wg/index.html> It may also be possible to raise a proposal during a working group session at RIPE 44 next week. RIPE 44 meeting details are available from our web site at: <http://www.ripe.net/ripe/meetings/current/ripe-44/> Kind regards, -- leo vegoda RIPE NCC Registration Services

2 1

Contacts
by der Mouse 18 Jan '03

18 Jan '03

I'm not sure this is the right place for this, but if not, perhaps someone can point me at the right place. I previously raised the issue with ncc(a)ripe.net and the person dealing with it there pointed me here, among other places. When dealing with net-abuse, I have occasion to look up addresses in RIPE's database, to contact people responsible for the relevant netblock. Mostly this is unremarkable, but sometimes the contact address bounces. In this case, I normally write to the contact for the next larger containing netblock, but when that's the RIPE, that doesn't work (the contact address for RIPE's netblocks is one which doesn't accept mail from the world at large - or at least is documented as such; I don't recall trying it recently). So I was reporting such broken contact addresses to ncc@. But the person there (signing with the name Yvette Vermeer) tells me that ncc@ is not the correct place to send them. She (I assume "Yvette" is "she") referred me to two lists, of which this is one. Presumably _somewhere_ at RIPE there is _someone_ to whom such things should be addressed; like any assigning authority, RIPE has responsibility concomitant with its authority, in particular to make sure its assignees behave themselves - such as by maintaining correct contact info. But it seems to be difficult to find whom to report such outdated contacts to. I've been lurking here for a little while, and this doesn't look like the right place to send such notifications; this appears to be more operational than policy. But perhaps I'm wrong, or perhaps someone here can tell me where I *should* send such notifications; I'm going to exhaust all the leads I can find at RIPE before going upstairs about this. I don't like to kick it even far up as RIPE (I wouldn't except that the invalid contact addresses in question are direct RIPE assignees) and I really don't want to have to go even further. /~\ The ASCII der Mouse \ / Ribbon Campaign X Against HTML mouse(a)rodents.montreal.qc.ca / \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B

1 0

Ref: Agenda points for the db-wg session (call for...)
by Wilfried Woeber, UniVie/ACOnet 17 Jan '03

17 Jan '03

Dear DB-WG! The RIPE NCC has already submitted items for the Jan 2003 DB-WG meeting's draft agenda. If anyone wants to propose issues/topics/items to be included, please sumbit them _asap_. I'll review the list of open actions and the minutes to complement the set of items from my end during the weekend. Regards, Wilfried. _________________________________:_____________________________________ Wilfried Woeber : e-mail: Woeber(a)CC.UniVie.ac.at UniVie Computer Center - ACOnet : Tel: +43 1 4277 - 140 33 Universitaetsstrasse 7 : Fax: +43 1 4277 - 9 140 A-1010 Vienna, Austria, Europe : RIPE-DB: WW144, PGP keyID 0xF0ACB369 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

1 0

Updated proposal for clean-up of references by name
by Engin Gunduz 16 Jan '03

16 Jan '03

[Apologies for duplicate messages] Dear Colleagues, I'm attaching the updated proposal for automatically cleaning up the references by name in RIPE Whois Database. We have incorporated Janos's suggestions to the proposal. If no more comments come, we plan to apply the procedure described in the proposal in the first half of January, 2003. The operation should not take more than a day. We will notify the community about the actual date of the operation. Regards, Engin Gunduz ____________________________ RIPE NCC Database Group -------------- Proposed solution for cleaning up references by name and other invalid references in RIPE Whois Database Motivation: References by name and invalid references cause two main problems: 1. One reference by name in a single object locks all person and role objects with that name, that is, they cannot be deleted, because of referential integrity checks. 2. Having anything other than a NIC handle as a reference makes the implementation of whois database software considerably more complex, since the software needs to deal with these exceptions. This increases the coding time, maintenance time and testing time of the software. Classification of the inconsistencies we need to solve and proposed solutions: 1. Objects that refer to a person or role object by name. a. There is only one object with this name. 1. The referring inconsistent object is not maintained, or the maintainers of referring inconsistent object and the person/role object with this name are the same. Solution: Update the referring inconsistent object so that it will contain the NIC handle instead of the name. Add appropriate remarks and changed attributes to the object to explain the reason for update. 2. The referring object is maintained, and the maintainers are different from the maintainers of the object with the referred name (If the latter object is not maintained, then the maintainers are by definition different.) Solution: Create a role object with this name. It will list the role or person object with this name in its admin-c and tech-c attributes. Update the inconsistent object to refer to the NIC handle of this new role object. Add appropriate remarks and changed attributes to the object to explain the reason for update. b. There is no person or role object with this name: Solution: Create a person object with this name. Clearly mark this new object putting appropriate remarks attributes so that users will see it is actually a dummy object. Update the inconsistent object to refer to the NIC handle of this new person object. Add appropriate remarks and changed attributes to the object to explain the reason for update. Protect it with the inconsistent object's maintainer(s). c. There are multiple person and role objects with this name. Solution: Create a role object with this name. It will list all the other role and person objects with the same name in its admin-c and tech-c attributes. Update the inconsistent object to refer to the NIC handle of this new role object. Add appropriate remarks and changed attributes to the object to explain the reason for update. 2. Objects that refer to a non-existent NIC handle. Solution: Create a person object with that NIC handle. Clearly mark this new object so that users will see it is actually a dummy object. Name it "person: Place Holder Object". Protect it with the inconsistent object's maintainer(s). Note that there is no need to update the inconsistent object itself. 3. Objects that refer to a string which is neither a name, nor a NIC handle. For example, it might be a phone number in admin-c attribute, or it might be 'Gunduz', a string that can't be a NIC handle, as it's longer than 4 letters, nor can it be a name as it has only one word. Another example could be "Mr. Gunduz", which enters this category because "Mr" can't appear in a name of person/role object. Solution: Create a person object for each such reference. Name the object "person: Place Holder Object" and list the object that refers to it in its remarks attribute. Protect it with inconsistent object's maintainer(s). Then update the inconsistent object to refer to the NIC handle of this new place holder person object. In each case an object is updated, or created, send appropriate notifications (determined by "mnt-by" and "notify" attributes, as with all other updates). Please note that this proposal does not actually solve the problem of invalid contact information-- rather, it makes the data set more uniform, thus decreases the administration and development time of the whois database.

1 2