- db-wg - mailman.ripe.net

RIPE Whois Server version 3.3.0
by Can Bican 25 May '05

25 May '05

Dear Colleagues, We are pleased to announce the release of version 3.3.0 of the RIPE Whois server. Major changes to the software include the following: o People upgrading from 3.2.0 need to read the file UPDATE-DB-3.3.0. o The source tree has heavily been modified; build system now makes full use of autoconf/automake. o We have added new options to the configure script. You can choose RPSL variants during configure by using --with-rpslvariant. You can turn RDNS off or on by using the --with-rdns option. o The LIMERICK object type has been upgraded to more the general POEM and POETIC-FORM object types. You can find a complete description of this change at: http://www.ripe.net/ripe/maillists/archives/db-wg/2005/msg00073.html o We have added a Reverse DNS registry checking mechanism. Since this is a specialised requirement for the software, it is initially turned off by default. o We have included a Perl RPSL library in the distribution. o We have implemented abuse mailbox changes, by adding a few new query options and changes to the default output. You can see a full list of changes at: http://www.ripe.net/ripe/maillists/archives/db-wg/2005/msg00057.html o We have changed the name of the server binary: whois_rip is now whois-server. o We have included the ORGANISATION object type. o We have included RPSL-NG facilities in the main branch of the software. This conforms to the RFC at: ftp://ftp.ripe.net/rfc/rfc4012.txt o IRT and MNTNER object creation is now automatic. o dbupdate is now x-509 aware, along with the related KEY-CERT objects. You can find more information on the implementation at: http://www.ripe.net/ripe/maillists/archives/db-wg/2003/msg00144.html You can download this release by anonymous FTP from the following URL: ftp://ftp.ripe.net/ripe/dbase/software/whoisserver-3.3.0.tar.gz You can also check out the release from CVS, which includes test cases, using the following CVS commands: cvs -d :pserver:anonymous@cvs.ripe.net:/cvsroot login cvs -d :pserver:anonymous@cvs.ripe.net:/cvsroot co -r \ release_3_3_0 whoisserver If you have any questions, please contact <ripe-dbm(a)ripe.net>. Best regards, -- Can Bican RIPE NCC Software Engineering Department

1 0

abuse-mailbox
by Philippe Bourcier 25 May '05

25 May '05

Hi, I'm the author of the CyberAbuse whois, which is a tool that catches the "most suitable" abuse contact email for a specific IP/host by searching in the RIRs whois result. It's security and network abuse oriented... it's used in many CERTs or IRTs. I understand there's a new (and long waited for) abuse-mailbox field that my program should catch in the RIPE db. I'd like to know what would you recommend as the behavior for catching the "best possible" abuse-contact in the RIPE db. Here is how the cyberabuse whois used to work (for RIPE) : 1 - search for an IRT object (mnt-irt), if one exist, go catch the associated e-mail 2 - search for an email in all the remarks/trouble/descr fields with the abuse/security/cert/csirt string in it 3 - search for the admin-c's email, if any 4 - search for the tech-c's, if any 5 - search for the first email found I think I'm going to add a search for the abuse-mailbox field between (1) and (2). Is this how you would do it ? Any other comments/suggestions ? Sincerely, Philippe Bourcier

2 1

Re: [ipv6-wg@ripe.net] Re: [ncc-services-wg] RIPE 50 Report
by Shane Kerr 24 May '05

24 May '05

Daniel Roesen wrote: >On Tue, May 24, 2005 at 02:09:07PM +0200, Nick Hyrka wrote: > > >>IPV6 WORKING GROUP >> >>- It was decided that the RIPE Whois Database will continue to include more >>services that run in native IPv6. >> >> > >Hm? > > Right now the Whois server answers queries through a proxy. The server will answer IPv6 itself, and the proxy terminated. Also, there is no IPv6 mirroring facility. This will be added. -- Shane

2 1

Whois changes
by James A. T. Rice 13 May '05

13 May '05

I'm probably posting far too late about this, but: Much as I agree that the default removal of email addresses from the whois output is a good idea, the lack of a changed: field is very annoying. Its always good to know how out of date an object is - and one of the key parameters I've used to decide if the details in an object are likely to be correct (i.e. are they actively maintained). Any chance of having changed: with a date (not an email address) back in the default output? Regards James

4 4

Whois changes
by Erics 12 May '05

12 May '05

Hi, i think this is a good idea. The default output should show the last changed date. This could be very helpful for LIRs. Kind regards Eric

6 7

RE: [db-wg] Implementation of POEM object
by Titley, Nigel 12 May '05

12 May '05

Paul Wilson wrote: > Arife, > > i'm finding this discussion rather anglo-centric. was any > consideration given to a "language" descriptor in discussion of this > object. > > of course the official language of ripe ncc is english, but it's a bit > harsh to expect non-english speakers to contribute good verse in > other than their native language... > > :-) The poem object itself is language independent, although the naming of the poetry-form object is strongly anglo-centric. It was noted during the WG discussion that followed the original presentation that without multibyte character support in the RIPE database (and RPSL in general), the provision of a haiku type was something of an insult to Japanese literature. However, it was felt that the effort involved in making RPSL and the RIPE database fully multibyte compliant, solely to allow the storage of japanese language haikus, could be deferred to a later date. A subgroup of the Secret Cabal(TM), if such a thing were to exist, could of course, be set to work on this, if there were a means to contact them to give them the commission. -- Nigel Titley Peering Coordinator, FLAG Telecom +44 20 8564 5812 ********************************************************************** This e-mail message is confidential and is intended only for the use of the individual or entity named above and contains information which is or may be confidential, non-public or legally privileged. Any dissemination or distribution of this message other than to its intended recipient is strictly prohibited. You should not copy it or use it for any purpose nor disclose the contents to any other person. If you have received this message in error, please notify us by email to postmaster(a)flagtelecom.com immediately and delete the original message and all copies from all locations in your computer systems. This e-mail has been swept by Mailsweeper TM for viruses. However, FLAG Telecom cannot accept liability for any damage which you may sustain as a result of software viruses. ********************************************************************** This message has been scanned for viruses by MailControl - www.mailcontrol.com

1 0

RE: [db-wg] Implementation of POEM object
by Titley, Nigel 12 May '05

12 May '05

Arife Vural wrote: >>> poetic-form: FORM-LIMERICK >>> descr: Poem type for Limerick >>> admin-c: AMR68-RIPE >>> mnt-by: RIPE-DBM-MNT >>> changed: ripe-dbm(a)ripe.net 20050429 >>> source: RIPE >> >> Slight problem with this example. I beleive we agreed that the >> description of the poetic form should be in the form of the poetic >> form itself. I gave a number of examples: limerick, haiku, prose, >> and english sonnet in my original presentation. This example does >> not comply with the requirement. > > You mean like that, right? > > descr: FORM-LIMERICK > > I got the requirements from DB-WG mailling list thread. From there it > was not so clear. If there would not be any objections, I could > replace those entries as you proposed. > > Arife No, not quite that. The requirements (which came at the end of the thread) suggested that the description of a limerick (for example) should be in the form of a limerick. The description of a haiku should be in the form of a haiku etc. An example for limerick was poetic-form: VERSE-LIMERICK descr: The object consists of a verse descr: in a format approaching the terse descr: The rhymes, very strict descr: Must be carefully picked descr: and it's funny and often perverse admin-c: LIM1-RIPE tech-c: LIM1-RIPE mnt-by: RIPE-DBM-MNT changed: ripe-dbm(a)ripe.net 20040401 source: RIPE Note the hierachical naming convention for poetic-form objects, all verse type forms should start "VERSE". Remember that not all poetry is verse. So another example would be poetic-form: PROSE descr: Don't let the structure tie your tongue; descr: if you hate the masochism of verse, Descr: remember that you can feel free to use prose, descr: and feel free because you are. admin-c: LIM1-RIPE tech-c: LIM1-RIPE mnt-by: RIPE-DBM-MNT changed: ripe-dbm(a)ripe.net 20040401 source: RIPE The poetic form names are hierachical so for example the English sonnet form could be Poetic-form: VERSE-SONNET-ENGLISH descr: The English sonnet poem's perfect peak descr: Doth sooth the senses with its gracious line descr: Full fourteen lines, five doubles stressed we seek descr: The first octet a single concept fine descr: Must introduce in argument aright descr: And when is unconcealed its notion hid descr: A pause, a breath must make a junction slight descr: Before the latter part its thought must bid. descr: The sextet takes us further in this scheme descr: Its rhymes EFEFGG march on descr: Alike yet different in their simple theme descr: To those that went before and build upon descr: Them, rearing up the mused-on lambent dream descr: To climax in a final couplet bare descr: That ends this form of verse which flows so fair. admin-c: LIM1-RIPE tech-c: LIM1-RIPE mnt-by: RIPE-DBM-MNT changed: ripe-dbm(a)ripe.net 20040401 source: RIPE Again, see my presentation for a number of examples. -- Nigel Titley Peering Coordinator, FLAG Telecom +44 20 8564 5812 ********************************************************************** This e-mail message is confidential and is intended only for the use of the individual or entity named above and contains information which is or may be confidential, non-public or legally privileged. Any dissemination or distribution of this message other than to its intended recipient is strictly prohibited. You should not copy it or use it for any purpose nor disclose the contents to any other person. If you have received this message in error, please notify us by email to postmaster(a)flagtelecom.com immediately and delete the original message and all copies from all locations in your computer systems. This e-mail has been swept by Mailsweeper TM for viruses. However, FLAG Telecom cannot accept liability for any damage which you may sustain as a result of software viruses. ********************************************************************** This message has been scanned for viruses by MailControl - www.mailcontrol.com

6 5

abuse stuff implemented in the DB, and thanks
by Wilfried Woeber, UniVie/ACOnet 11 May '05

11 May '05

Dear WG Members, earlier today we had a very interesting presentation by Shane, summarizing the various changes in the DB machinery related to implementing the abuse-mailbox facilities. I'd like to take this opportunity to remind you about the availability of the presentation slides from the RIPE50 meeting pages on the web, AND to say "thank you" to everyone at the NCC involved in the implemenation. Looks like a job well done, and in time for review during this meeting! Wilfried.

2 1

RE: [db-wg] Implementation of POEM object
by Titley, Nigel 11 May '05

11 May '05

Olaf M. Kolkman wrote: >> Note the hierarchical naming convention for poetic-form objects, all >> verse > > I have a few maintenance questions. > > Although my colleagues are technically competent, they have > not been hired for their literary skills(*). So although the RIPE DB > staff will technically maintain the poetic-form: we still need a > mechanism to ensure the quality of the "poetic-form" objects. Agreed and it was always noted that this was a highly skilled job. > Will RIPE NCC staff need to contact a secret cabal for quality > control? Alternatively, will we skip quality control and act on first > come first served (serious security considerations: culprits might > specify a Haiku in the form of a Dada poem)? Or should a poetic-form > first be discussed by the db-wg? I would suggest that quality control should be managed by a secret cabal as at present with the limerick object. Secret cabals have a long and illustrous history on the internet and have usually resulted in fast, effective decision making albeit at the slight expense of annoying and upsetting large numbers of people (since my email is always bounced by Randy's "no legal disclaimer" filters, I feel perfectly safe in making this remark). > > I'd settle for the first option, a secret cabal... I may just know an > institution that could perform this task. I'm sure that they will prove themselves adequate to the task, even though I have no idea who they might be, or even if they exist. > > The classification scheme may also need some work. How do we classify > the different forms? Would the Aphorism have its own class or is it a > subclass of PROSE? > > In absence of the review process. Hereby a new proposal > > poetic-form: PROSE-APHORISM > descr: A database entry to be remembered by > admin-c: OK65-RIPE > tech-c: OK65-RIPE > mnt-by: RIPE-DBM-MNT As far as the name is concerned this would be perfectly correct, although ending a sentence with a preposition is perhaps to be regarded as slightly suspect style. (One must, though, remember Winston Churchill's comments on the matter). poetic-form: PROSE-APHORISM descr: A database entry by which to be remembered admin-c: OK65-RIPE tech-c: OK65-RIPE mnt-by: RIPE-DBM-MNT Might be slightly better stylistically. > > and > > poetic-form: VERSE-HAIKU > descr: The haiku object > descr: only seven syllables > descr: in its density > admin-c: OK65-RIPE > tech-c: OK65-RIPE > mnt-by: RIPE-DBM-MNT This is correct in all respects. > -- Olaf > > (*) I am sure I lost credit with my colleagues with this remark but > these are matters of high public interest. Of course. Perhaps we should include an examination of literary skill when engaging RIPE NCC staff. -- Nigel Titley Peering Coordinator, FLAG Telecom +44 20 8564 5812 ********************************************************************** This e-mail message is confidential and is intended only for the use of the individual or entity named above and contains information which is or may be confidential, non-public or legally privileged. Any dissemination or distribution of this message other than to its intended recipient is strictly prohibited. You should not copy it or use it for any purpose nor disclose the contents to any other person. If you have received this message in error, please notify us by email to postmaster(a)flagtelecom.com immediately and delete the original message and all copies from all locations in your computer systems. This e-mail has been swept by Mailsweeper TM for viruses. However, FLAG Telecom cannot accept liability for any damage which you may sustain as a result of software viruses. ********************************************************************** This message has been scanned for viruses by MailControl - www.mailcontrol.com

3 2

RE: [db-wg] Implementation of POEM object
by Titley, Nigel 11 May '05

11 May '05

Niall O'Reilly wrote: > On 11 May 2005, at 11:43, Titley, Nigel wrote: > >> ending a sentence with a preposition is perhaps to be regarded as >> slightly suspect style. > > Not really. > > From the Oxford Dictionary of English, 2nd edition (ISBN > 0-19-8613474): > >> The superstition that a preposition should always precede the word >> it governs and should not end a sentence [...] is not based on a >> real appreciation of the structure of English [...]. I did say "perhaps". -- Nigel Titley Peering Coordinator, FLAG Telecom +44 20 8564 5812 ********************************************************************** This e-mail message is confidential and is intended only for the use of the individual or entity named above and contains information which is or may be confidential, non-public or legally privileged. Any dissemination or distribution of this message other than to its intended recipient is strictly prohibited. You should not copy it or use it for any purpose nor disclose the contents to any other person. If you have received this message in error, please notify us by email to postmaster(a)flagtelecom.com immediately and delete the original message and all copies from all locations in your computer systems. This e-mail has been swept by Mailsweeper TM for viruses. However, FLAG Telecom cannot accept liability for any damage which you may sustain as a result of software viruses. ********************************************************************** This message has been scanned for viruses by MailControl - www.mailcontrol.com

1 0