14 Dec
2020
14 Dec
'20
11:26 a.m.
I assume since AMPR does not have a RSA with ARIN,
Chris cannot create
IRR records for those folks who BGP advertise AMPR resources?
The vast majority of folk advertising their subnet over BGP are using altdb with no issues
(currently).
IIRC, altdb is run by one person, so if you don’t already have a MNTNER object there, it
can sometimes take some time to get one.
Chris
v/r,
Caleb
On 12/13/2020 10:08, James Colderwood via 44Net wrote:
Hi Pierre,
Thank you for the heads up. I was aware of altdb but it hadn't crossed
my mind. Hopefully one of these solutions will work :-).
On 2020-12-13 17:32, Pierre Emeriaud wrote:
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net Le dim. 13 déc. 2020 à 12:04, G1FEF via 44Net
<44net(a)mailman.ampr.org> a écrit :
> On 13 Dec 2020, at 09:54, James Colderwood via 44Net
<44net(a)mailman.ampr.org> wrote:
>
> Hi All,
>
> May I wish you all happy holidays!
>
> Quick question, I'm working on establising my 3rd upstream but hit
a snag. The suppliers validation automation prohibits announcing
AMPR addresses as the system can't qualify validity.
Are you talking about automatically checking entries in an IRR, or
RPKI?
For service providers requesting an IRR route object to automate
filter creation I've been using altdb. While it has not a lot of value
in terms of authorization (anyone can create objects about any
resource - a proper LOA has more value here) it is usually enough for
provisioning tools to create appropriate filters / prefix-lists:
$ whois -h whois.altdb.net 44.151.210.0
route: 44.151.210.0/24
descr: F4INU
origin: AS206155
mnt-by: MAINT-AS206155
$ bgpq3 -4 -l F4INU as206155
no ip prefix-list F4INU
ip prefix-list F4INU permit 44.151.210.0/24
73 de F4INU
--
pierre