Le dim. 13 déc. 2020 à 12:04, G1FEF via 44Net 44net@mailman.ampr.org a écrit :
On 13 Dec 2020, at 09:54, James Colderwood via 44Net 44net@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?
Le dim. 13 déc. 2020 à 12:04, G1FEF via 44Net 44net@mailman.ampr.org a écrit :
On 13 Dec 2020, at 09:54, James Colderwood via 44Net 44net@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