Dear Job Looking again at this issue I think we already provide the !g and !6 services. You gave two examples: Connected to whois.radb.net. Escape character is '^]'. !gas5580 A1195 50.7.160.0/20 50.7.184.0/24 50.7.185.0/24..... Connected to whois.radb.net. Escape character is '^]'. !6as5580 A86 2001:49f0:c000::/48 2a02:d28::/32 2a00:19c0:1000::/48 2001:67c:b0::/48 2a01:8640::/48 These queries give you back the same info but in a slightly different layout: $ whois -GBrK -Troute -i origin as5580 route: 128.127.152.0/21 origin: AS5580 route: 164.138.248.0/21 origin: AS5580 .... $ whois -GBrK -Troute6 -i origin as5580 route6: 2001:67c:b0::/48 origin: AS5580 route6: 2a00:19c0:1000::/48 origin: AS5580 .... Regards Denis Walker Business Analyst RIPE NCC Database Team On 20/10/2013 16:44, Job Snijders wrote:

Dear RIPE DB-WG,

Much like my previous request regarding server side expansion of objects, I'd very much like the RIPE Database team to implement two flags which IRRd currently supports: !g & !6

I've filed an enhancement request on github:

https://github.com/RIPE-NCC/whois/issues/73

The !g and !6 flags signficantly reduce the amount of RPSL interpretation a client has to perform, as the server provides the clients with a straight answer (abeit simplified).

If the DB team implements such a feature, I'd also very much like an implementation in context or RDAP so I can query for lists of prefixes through HTTP rather than WHOIS.

Kind regards,

Job