This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[db-wg] Draft Minutes of the RIPE 52 DB-WG meeting
- Previous message (by thread): [db-wg] Draft Minutes of the RIPE 52 DB-WG meeting
- Next message (by thread): [db-wg] Draft Minutes of the RIPE 52 DB-WG meeting
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Andre Koopal
andre.koopal at nld.mci.com
Mon May 15 13:14:31 CEST 2006
On Fri, Apr 28, 2006 at 06:58:06PM +0200, Denis Walker wrote: > Hi > > I think Marco is right that there seemed to be a consensus on the > mailing lists for making the whois server return the irt object by > default. I was not at the RIPE meeting, but reading the minutes several > times it looks like the members at the meeting no longer want that to be > the case. There were some quite strong arguments about this in the > previous discussion on the mailing list. The general view seemed to be > that if this is not implemented in the right way it makes the whole > concept of the irt useless. If we get this wrong again, I feel that > either the discussions on the mailing list will never end or the irt > object will be abandoned. > It is still unclear to me what now has been decided on the RIPE meeting. Having abuse information in the RIPE database is useless if it is not returned in the default query, and you can't depend on the client to have some option by default as all kind of clients/webpages and whatever are used, so it must be be solved on server side. I was really under the impression we agreed that if you lookup an ip-number the correct inetnum would be displayed together with the relevant irt object that might be from a level up. It has been remarked that in that way a not referenced block would be returned, but that was taken for granted. I still think the above solution must be implemented to make the irt object usefull, and if the code can't easily handle it, the code must be changed. Whatever options will be implemented to finetune the output for experienced users/coders I don't care, but the average user should see the relevant information. Regards, Andre Koopal -- Andre Koopal EMEA Server & Service Management - Int ITSD Verizon Business H.J.E. Wenckebachweg 123 1096 AM Amsterdam Netherlands tel : +31 (0)20 711 1000 fax : +31 (0)20 711 2519 Verizon and MCI are now operating as Verizon Business ! This e-mail is strictly confidential and intended only for use by the addressee unless otherwise indicated.
- Previous message (by thread): [db-wg] Draft Minutes of the RIPE 52 DB-WG meeting
- Next message (by thread): [db-wg] Draft Minutes of the RIPE 52 DB-WG meeting
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]