About RIPE | Contact  | Search | Sitemap    
Homepage RIPE  
RIPE Community Mail Archives
search  
     
RIPE Navigation Ends
About RIPE Maillists
Maillists Archive
Global Lists
Non Active Lists
RIPE NCC Navigation Ends
Next Section

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

  • From:
    (Marco d'Itri)
  • Date: Wed, 12 Oct 2005 14:37:51 +0200

On Oct 12, Denis Walker denis@localhost wrote:

> >From this discussion it looks like what you want is for the first query
> to return this irt object as the default, along with the inetnum object
> that would normally be returned with this query.
No, we are NOT asking for changes in which inetnums (and related) objects
are returned, but that the relevant IRT object is returned along with the
inetnum object which is currently returned.

> If we make this the default operation, then we have to have a way to
> turn it off. Not everyone wants yet more information returned with their
> query. This could be done with another flag. Or we could link it in with
> the recursive searching currently done with personal data.
I think it would be natural for -r to suppress IRT objects too.

> This would mean a query done for a range with no query flags would
> return the most specific inetnum object, route objects, organisation
> object, role/person objects and the irt object that would have been
> found with a -c query. The same query with the -r flag would only return
> the inetnum and route objects.
> 
> Is this the behavior that most people would prefer?
Yes.

-- 
ciao,
Marco

Attachment: signature.asc
Description: Digital signature


 

Next Section
     About RIPE | Site Map | LIR Portal | About the RIPE NCC | Contact | Copyright Statement
RIPE.NET Homepage LIR Portal RIPE Community