<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<font size="+1"><tt>Dear Job<br>
<br>
Looking again at this issue I think we already provide the !g
and !6 services. You gave two examples:<br>
<br>
Connected to whois.radb.net.<br>
Escape character is '^]'.<br>
!gas5580<br>
A1195<br>
50.7.160.0/20 50.7.184.0/24 50.7.185.0/24.....<br>
<br>
Connected to whois.radb.net.<br>
Escape character is '^]'.<br>
!6as5580<br>
A86<br>
2001:49f0:c000::/48 2a02:d28::/32 2a00:19c0:1000::/48
2001:67c:b0::/48 2a01:8640::/48<br>
<br>
These queries give you back the same info but in a slightly
different layout:<br>
<br>
$ whois -GBrK -Troute -i origin as5580<br>
<br>
route: 128.127.152.0/21<br>
origin: AS5580<br>
<br>
route: 164.138.248.0/21<br>
origin: AS5580<br>
....</tt></font><br>
<br>
<font size="+1"><tt>$ whois -GBrK -Troute6 -i origin as5580</tt></font><br>
<font size="+1"><tt>route</tt></font>6:
2001:67c:b0::/48<br>
<font size="+1"><tt>origin: AS5580</tt></font><br>
<br>
<font size="+1"><tt>route</tt></font>6:
2a00:19c0:1000::/48<br>
<font size="+1"><tt>origin: AS5580</tt></font><br>
<font size="+1"><tt>....</tt></font><br>
<br>
Regards<br>
Denis Walker<br>
Business Analyst<br>
RIPE NCC Database Team<br>
<br>
<font size="+1"><tt>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<br>
</tt></font>
<div class="moz-cite-prefix">On 20/10/2013 16:44, Job Snijders
wrote:<br>
</div>
<blockquote cite="mid:20131020144419.GC74206@Eleanor.local"
type="cite">
<pre wrap="">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:
<a class="moz-txt-link-freetext" href="https://github.com/RIPE-NCC/whois/issues/73">https://github.com/RIPE-NCC/whois/issues/73</a>
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
</pre>
</blockquote>
<br>
</body>
</html>