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]/

[Fwd: Re: [Fwd: [db-wg] RIPE51 DB-WG Draft Agenda V1]]

Previous message (by thread): [Fwd: Re: [Fwd: [db-wg] RIPE51 DB-WG Draft Agenda V1]]
Next message (by thread): [Fwd: Re: [Fwd: [db-wg] RIPE51 DB-WG Draft Agenda V1]]

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Havard Eidnes he at uninett.no
Wed Oct 12 12:06:53 CEST 2005

> > We have changed the behaviour of the database so that when
> > you do a "-c" lookup, we return the IRT object in the
> > reply. I thought this was the desired behaviour. You can see
> > it here:
>
> This is useful, but the desired behavious was to always return
> the relevant irt record for inetnum queries, along with the
> most specific inetnum object.

I guess the missing phrase both in the action point and in the
above reply is "by default".

(And, yes, I agree, that is needed for this action point to make
any sense.)

Regards,

- Håvard

Previous message (by thread): [Fwd: Re: [Fwd: [db-wg] RIPE51 DB-WG Draft Agenda V1]]
Next message (by thread): [Fwd: Re: [Fwd: [db-wg] RIPE51 DB-WG Draft Agenda V1]]

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ db-wg Archives ]