nanog mailing list archives
Re: IRR AS-SET best practices - AS-SET Clash
From: Baldur Norddahl <baldur.norddahl () gmail com>
Date: Sun, 28 Jan 2018 04:02:44 +0100
The hierarchical as-set strategy has the problem that many fails to parse it correctly. We use it at NL-IX with the result that their portal believe we have no peers. Den 24. jan. 2018 15.50 skrev "Job Snijders" <job () ntt net>: On Wed, Jan 24, 2018 at 02:23:48PM +0000, Nick Hilliard wrote:
Alain Hebert wrote:Any feedback on best practices and "other avenue" about IRR naming?Known problem - you're asking for trouble unless you filter IRRDB queries by source: There isn't a global namespace for as-set names, unless you use source: as a database key element.
In addition to the above, one could use "hierarchical" AS-SET names, in some databases (from the top of my head: APNIC, AfriNIC, RIPE) only the owner of the ASN can create AS-SETs under that ASN's namespace. But more importantly: using the ASN in the AS-SET name chances of collision are reduced. Example: I defined "AS15562:AS-SNIJDERS" in the RIPE database, instead of "AS-SNIJDERS". Same for "AS2914:AS-GLOBAL" in NTTCOM. --- thread hijack --- Coincidentally, I'm working to define something like "AS-SETs in RPKI". There are a number of downsides to "AS-SETs in IRR": collisions between databases can exist, it is hard to figure out what AS-SET to use for what ASN (we rely on service order forms, peeringdb or guessing for that), and the way the recursion was done can too easily result in gigantic sets. I'd be interested to know what others think about improving feature parity between IRR and RPKI, and while doing that make the bad aspects of AS-SETs go away and keep the good parts. Thoughts? Kind regards, Job ps. raised the question here too https://mail.lacnic.net/ pipermail/lacnog/2018-January/005845.html
Current thread:
- Re: BGP Community Support WAS: Re: Cogent vs. HE ;-) WAS: Anyone using Cogent Ethernet, (continued)
- Re: BGP Community Support WAS: Re: Cogent vs. HE ;-) WAS: Anyone using Cogent Ethernet Christopher Morrow (Jan 23)
- Re: BGP Community Support WAS: Re: Cogent vs. HE ;-) WAS: Anyone using Cogent Ethernet James Breeden (Jan 23)
- Re: BGP Community Support WAS: Re: Cogent vs. HE ; -) WAS: Anyone using Cogent Ethernet Clinton Work (Jan 23)
- Re: BGP Community Support WAS: Re: Cogent vs. HE ;-) WAS: Anyone using Cogent Ethernet Dan White (Jan 23)
- Re: BGP Community Support WAS: Re: Cogent vs. HE ;-) WAS: Anyone using Cogent Ethernet Bryan Holloway (Jan 23)
- IRR AS-SET best practices - AS-SET Clash Alain Hebert (Jan 24)
- Re: IRR AS-SET best practices - AS-SET Clash Nick Hilliard (Jan 24)
- Re: IRR AS-SET best practices - AS-SET Clash Job Snijders (Jan 24)
- Re: IRR AS-SET best practices - AS-SET Clash Jared Mauch (Jan 27)
- Re: IRR AS-SET best practices - AS-SET Clash Job Snijders (Jan 27)
- Re: IRR AS-SET best practices - AS-SET Clash Baldur Norddahl (Jan 27)
- Re: IRR AS-SET best practices - AS-SET Clash Job Snijders (Jan 27)
- Re: IRR AS-SET best practices - AS-SET Clash Jared Mauch (Jan 27)
- Re: BGP Community Support WAS: Re: Cogent vs. HE ;-) WAS: Anyone using Cogent Ethernet Mike Hammett (Jan 23)