irt object being returned by default [was: Re: [db-wg] ASN32 deployment]

Jeroen Massar wrote:

>Wilfried Woeber, UniVie/ACOnet wrote:
>  
>
>>Marco d'Itri wrote:
>>    
>>
>>>On Jan 02, Denis Walker <denis at ripe.net> wrote:
>>>      
>>>
>>>>This morning, between 07:00 and 09:00 (UTC), we deployed new
>>>>software for the RIPE Database. Three changes were made:
>>>>        
>>>>
>>>What happened to the planned changes about when irt objects are returned?
>>>
>>>      
>>>
>>it is - as a 1st step - already being returned by default for web-queries.
>>    
>>
>
>Which just does a local "whois -- <quote-escaped options>" and formats
>it in a pretty way.
>
>  
>
>>Just go to www.ripe.net and do a database lookup for e.g. 131.130/16 in the
>>Database Search box, top right corner.
>>    
>>
>
>That trick works at the moment only when the object has a direct IRT
>object related to it. Take for instance 2001:7b8:300::/48 and it won't
>return it, unless you add the -c option. Which is prolly why you said
>'1st step' as that will be the 2nd step. But the 1st step has already
>been in place for quite some time afaik...
>  
>
Yes the first step has been implemented some time ago. But I think you
have highlighted a bug here with irt in inet6num objects. The web
interface is still not finding them without adding the -c flag. We will
look into this.

regards
Denis Walker
Database Group
RIPE NCC

>  
>
>>Btw, to everyone just reading along :-)
>>This lookup interface is pretty cool as it does support including your
>>favourity whois flags like -T, -r and friends in the lookup key entry-box!
>>    
>>
>
>IMHO the cool part is the "Advanced" box so that one can select the
>flags and construct a query, allowing me to forget all those options ;)
>
>Greets,
> Jeroen
>
>  
>