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: [db-wg] irt object useless

  • To: Gert Doering <
    >
  • From: Andre Koopal <
    >
  • Date: Fri, 27 May 2005 23:32:49 +0200

On Fri, May 27, 2005 at 10:05:34PM +0200, Gert Doering wrote:
> Hi,
> 
> On Fri, May 27, 2005 at 07:51:31PM +0200, Marco d'Itri wrote:
> > > As I don't see any more comments on this, have we already reached consensus?
> > Hiding more-specific objects by default is such a major change that I
> > do not think it can be deployed after a discussion among just three or
> > four people.
> 
> Nobody wants to hide more-specifics.
> 
> The goal is to show the inetnum: object (as before) and, in addition to that,
> the most-specific available irt: object.  *In the default response*.
> 
> So if the inetnum: has its own mnt-irt: then show it, but if there is only
> one for the encompassing /16 (or whatever), then show the "parent" irt: -
> otherweise irt: is pretty useless.
> 
That is exactly what I mean.

And I don't see this as a discussion between 3 or 4 people, everybody can
read this and participate. So the rest either doesn't care or agrees :-)

Regards,

Andre Koopal




 

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