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:
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
Hello,
Your upstream providers may be able to put a proxy obj into the ARIN db for you. Unfortunately ARIN changed their IRR db in June of this year. They added a web based IRR service. According to ARIN, the web based service only allows you to add object for resources you own (your upstream ISP could not create those proxy objects since they do not own the 44net resources). If they still use the ARIN email IRR system, they can add proxy objects, they will just appear as ARIN-NOAUTH in the IRR db. I don't think NOAUTH is a problem for most providers now, but could be down the road if they start filtering/ignoring NOAUTH entries.
Of course altdb, radb and others are options (full list at: http://www.irr.net/docs/list.html). Not sure how other RIR's outside the US are handling NOAUTH entries.
I assume since AMPR does not have a RSA with ARIN, Chris cannot create IRR records for those folks who BGP advertise AMPR resources?
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:
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
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:
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
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
-
Caleb Pal -
G1FEF -
James Colderwood