<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">
<div class="moz-cite-prefix">On 2023-07-03 16:22, Paul Emmons via
ixpmanager wrote:<br>
</div>
<blockquote type="cite"
cite="mid:2d6186a9-8ec2-2c82-15d8-23f33cb574dd@ninja-ix.net">In
short RADB doesn't mirror any other datasets this member uses.</blockquote>
<p>That's not what's going on here. As you can see from your own
output, you're querying RADB in both cases. RADB is mirroring
those other sources. It's just that IXP Manager (for good
reasons) is passing a -S to limit the sources to those
configured in IXP Manager.<br>
</p>
<p>It looks like you need to add ARIN and ALTDB at a minimum. You
should order the authenticated IRR sources like ARIN above
unauthenticated sources. So set this one to something like:
ARIN,RADB,ALTDB<br>
</p>
<div class="moz-cite-prefix">At MICE, we ended up using one list
for everyone, rather than trying to customize per network based
on who they were using:<br>
ARIN,RIPE,LACNIC,APNIC,AFRINIC,RADB,ALTDB,NTTCOM,LEVEL3,BELL</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">I'm told all of the RIRs are
authenticated, so there's not really any harm in including all
of those (and listing them at the front). Then it's just a
question of what people are using. RADB is pretty popular, so
you're almost certainly going to need that one.<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">If I were you, I would also tell
AS14237 to fix their own missing IRR entries at ARIN. Here is
what I wrote and sent to people; this particular AS has already
done steps 3-6, so you could remove those when sending them the
advice. I found that with a little hand-holding like this, most
networks were able to fix their records.<br>
</div>
<div class="moz-cite-prefix">
<ol type="1" start="1">
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1
level1 lfo3"> Login to ARIN Online. (Go to <a
href="https://linkprotect.cudasvc.com/url?a=https%3a%2f%2farin.net&c=E,1,bishIqF6tagnpfV2E58sQ4CjI107UL_Da1_s1BI_WNE1gal7FtY4lqXaJyfOuozk0T4ronTJnWwNrniVqixSF9Sdv_xe3jaqCPJqGKvk2wA,&typo=1&ancr_add=1">
arin.net</a> and click Login in the top right.)</li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1
level1 lfo3"> On the left side, expand "Routing Security"
and click "IRR". </li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1
level1 lfo3"> Click "as-set" at the top. </li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1
level1 lfo3"> Click "Create an Object". </li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1
level1 lfo3"> Fill in the fields:<br>
The "AS Set Name" is what you will list in PeeringDB.<br>
"Description" is unparsed, but they suggest the location and
have a button to "Copy the Address from My Org ID".<br>
"Members" is where you list your ASN and downstream ASes (if
any). </li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1
level1 lfo3"> Click "Review". Once ready, click "Submit". </li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1
level1 lfo3"> Click "route/route6" at the top. </li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1
level1 lfo3"> Click "Create an Object". </li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1
level1 lfo3"> Fill in the fields:<br>
"Prefix" is the prefix, e.g. 192.0.2.0/24.<br>
"Origin" is your ASN. </li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1
level1 lfo3"> Click "Review". Once ready, click "Submit". </li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1
level1 lfo3"> Repeat to create additional route objects
until all of your announcements are covered. Don't forget
IPv6!</li>
</ol>
</div>
</div>
<div class="moz-cite-prefix"><br>
<p>
</p>
</div>
<div class="moz-cite-prefix">On 2023-07-03 16:56, Paul Emmons via
ixpmanager wrote:<br>
</div>
<blockquote type="cite"
cite="mid:8841aae9-c18b-0863-f42a-e247cbc7557a@ninja-ix.net">Member
uses ARIN as their IRR - very high quality IRR and that member
doesn't have any down streams.</blockquote>
<blockquote type="cite"
cite="mid:8841aae9-c18b-0863-f42a-e247cbc7557a@ninja-ix.net">Member
B provides downstream to A</blockquote>
<blockquote type="cite"
cite="mid:8841aae9-c18b-0863-f42a-e247cbc7557a@ninja-ix.net">Member
B has their AS-SET as RADB</blockquote>
<p><br>
</p>
In this case, you need to list (at a minimum) ARIN,RADB as the
sources for "B" in IXP Manager.
<p><br>
</p>
<p>
<blockquote type="cite"><span style="white-space: pre-wrap; display: block; width: 98vw;">It is probably more of an issue of training member B not to use AUTNUMs for down streams.</span></blockquote>
</p>
<p>Whether B uses an as-set or just an AS12345 is irrelevant, I'm
pretty sure. The issue is finding the route/route6 objects. AFAIK,
that's done by looking for route/route6 objects for a given ASN.<br>
</p>
<pre class="moz-signature" cols="72">--
Richard</pre>
</body>
</html>