<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8">
<style>
div.plaintext { white-space: normal; }
body { font-family: sans-serif; }
div.plaintext h1 { font-size: 1.4em; }
div.plaintext h2 { font-size: 1.2em; }
div.plaintext h3 { font-size: 1.1em; }
blockquote.embedded,div.plaintext blockquote { margin: 0 0 5px; padding-left: 5px; border-left: 2px solid #777777; color: #777777; }
blockquote.embedded blockquote.embedded,div.plaintext blockquote blockquote { border-left-color: #999999; color: #999999; }
blockquote.embedded blockquote.embedded blockquote.embedded,div.plaintext blockquote blockquote blockquote { border-left-color: #BBBBBB; color: #BBBBBB; }
div.plaintext a { color: #3983C4 }
blockquote.embedded,div.plaintext blockquote a { color: #777777; }
blockquote.embedded blockquote.embedded,div.plaintext blockquote blockquote a { color: #999999; }
blockquote.embedded blockquote.embedded blockquote.embedded,div.plaintext blockquote blockquote blockquote a { color: #BBBBBB; }
div.plaintext math[display="inline"] > mrow { padding:5px; }
div.plaintext div.footnotes li p { margin: 0.2em 0; }
</style>
</head>
<body>
<div class="plaintext"><p dir="auto">That’ll be the plan. Our WHOIS database does have an “origin-as” attribute but AFAIK it’s seldom used. We do have a wealth of origination data in RPKI though.</p>
<p dir="auto">thanks!</p>
<p dir="auto">/Carlos</p>
<p dir="auto">On 3 Jan 2018, at 8:36, Arturo Servin wrote:</p>
</div>
<blockquote class="embedded"><div dir="ltr"><div><br></div>Just to make sure that I got it correctly.<div><br></div><div>You could do the same using RPKI and importing the verified ROAs to the IRR database (instead of using whois), right?</div><div><br></div><div>-as<br><br><div class="gmail_quote"><div dir="ltr">On Tue, 2 Jan 2018 at 14:12 Job Snijders <<a href="mailto:job@ntt.net">job@ntt.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Tue, Jan 02, 2018 at 10:56:09AM -0200, Luis Balbinot wrote:<br>
> Thanks cool!<br>
><br>
> One could easily export this data and create a local IRR server and<br>
> benefit from all existing RPSL automation tools.<br>
<br>
That is exactly what NTT has done: the ARIN WHOIS routing data is<br>
imported into our local IRR server at <a href="http://rr.ntt.net" rel="noreferrer" target="_blank">rr.ntt.net</a><br>
<br>
We took this approach so we'd avoid having to update any of our prefix<br>
filter generation tools.<br>
<br>
Kind regards,<br>
<br>
Job<br>
_______________________________________________<br>
LACNOG mailing list<br>
<a href="mailto:LACNOG@lacnic.net" target="_blank">LACNOG@lacnic.net</a><br>
<a href="https://mail.lacnic.net/mailman/listinfo/lacnog" rel="noreferrer" target="_blank">https://mail.lacnic.net/mailman/listinfo/lacnog</a><br>
Cancelar suscripcion: <a href="https://mail.lacnic.net/mailman/options/lacnog" rel="noreferrer" target="_blank">https://mail.lacnic.net/mailman/options/lacnog</a><br>
</blockquote></div></div></div></blockquote>
<div class="plaintext"><blockquote>
</blockquote><blockquote><p dir="auto">_______________________________________________<br>
LACNOG mailing list<br>
LACNOG@lacnic.net<br>
<a href="https://mail.lacnic.net/mailman/listinfo/lacnog">https://mail.lacnic.net/mailman/listinfo/lacnog</a><br>
Cancelar suscripcion: <a href="https://mail.lacnic.net/mailman/options/lacnog">https://mail.lacnic.net/mailman/options/lacnog</a></p>
</blockquote></div>
</body>
</html>