<br><div><span class="gmail_quote">On 6/19/06, <b class="gmail_sendername">Ross W</b> <<a href="mailto:email@example.com">firstname.lastname@example.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>For those not on the arin-announce mailing list, they just notified everyone (notice is copied below) about implimenting a new routing registry server recently. <br><br>In addition, I got followup confirmation from Jon
that their routing registry is now RFC4012 compliant, so now you can do route6/inet6num records with them (hence this post in ipv6-ops).</div></blockquote><div><br>As a followup to my own posting, after further communications with Jon, while the new rr server (
<a href="http://rr-eval.arin.net">rr-eval.arin.net</a>) is RFC4012 compliant, it doesn't support v6 objects currently. But since it's responding correctly to mirrored data from RIPE, so it's just a matter of time until us North Americans can submit new v6 objects.