<div dir="ltr"><br>As far as I can see, our conversation transcended the scope of a mail-list dedicated to supporting the IXP-Manager community.<br><br>On the one hand, this is bad.<br>I apologize for having helped trigger this change of course.<br><br>On the other hand, this is good.<br>Well-meaning people having a tool in common talking about difficulties that transcend the tool.<br><br>But back to the topic:<br>I imagine this conversation will get to the point of talking about some kind of multibase referential integrity check.<br><br>And I believe that this is already being discussed by other colleagues.<br>I bring it here for your knowledge:<br><br><a href="https://github.com/mxsasha/nrtmv4">https://github.com/mxsasha/nrtmv4</a> <br><a href="https://htmlpreview.github.io/?https://github.com/mxsasha/nrtmv4/blob/main/draft-ietf-grow-nrtm-v4.html">https://htmlpreview.github.io/?https://github.com/mxsasha/nrtmv4/blob/main/draft-ietf-grow-nrtm-v4.html</a><br><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Em qua., 5 de jul. de 2023 às 16:56, Richard Laager via ixpmanager <<a href="mailto:ixpmanager@inex.ie">ixpmanager@inex.ie</a>> escreveu:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<div>On 2023-07-05 08:18, Nick Hilliard
wrote:<br>
</div>
<blockquote type="cite">
<div style="font-size:14px;font-family:Calibri">
<div>Richard Laager via ixpmanager wrote on 04/07/2023 22:11:
<br>
<blockquote type="cite" style="color:rgb(0,0,0)">This is
supported in bgpq4, which works fine with IXP Manager if you
have this trivial patch, which is in bgpq4 1.10 (and 1.11):
<a href="https://github.com/bgp/bgpq4/pull/90" target="_blank">https://github.com/bgp/bgpq4/pull/90</a>
<br>
</blockquote>
<br>
it's not supported in RPSL, which is where it needs to be
supported. The current implementation in peeringdb / bgpq4 is
convenient syntax but little more.</div>
</div>
</blockquote>
<p>It is genuinely useful if someone's as-set name exists in
multiple IRRs, especially if the right one is higher in the list.
This actually happened for us, where someone has AS-ABC in RADB,
but someone else has AS-ABC in RIPE (which, as an authenticated
IRR, we have listed before RADB). Them being able to specify
RADB::AS-ABC made it work.<br>
</p>
<p>But yes, I agree with your point generally.<br>
</p>
<p><br>
</p>
<blockquote type="cite">
<div style="font-size:14px;font-family:Calibri">
<div>RPSL support would allow us to
address some of the serious structural disambiguation
associated with RPSL syntax when dealing with multiple IRRDBs.
</div>
</div>
</blockquote>
Writing and RFC for this would be pretty straightforward. But for
this to go anywhere, there would have to be interest from other
players, e.g. irrd. Do you have any idea if this has been discussed
in those circles?<br>
<pre cols="72">--
Richard</pre>
</div>
_______________________________________________<br>
INEX IXP Manager mailing list<br>
<a href="mailto:ixpmanager@inex.ie" target="_blank">ixpmanager@inex.ie</a><br>
Unsubscribe or change options here: <a href="https://www.inex.ie/mailman/listinfo/ixpmanager" rel="noreferrer" target="_blank">https://www.inex.ie/mailman/listinfo/ixpmanager</a><br>
</blockquote></div><br clear="all"><div><br></div><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr">Douglas Fernando Fischer<br>Engº de Controle e Automação<br><div style="padding:0px;margin-left:0px;margin-top:0px;overflow:hidden;color:black;text-align:left;line-height:130%;font-family:"courier new",monospace"></div></div></div>