[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
IRR AS-SET best practices - AS-SET Clash
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.
I've found best practice to be use AS23456 to identify the owner.
(assuming you are 23456). Using something else like AS-CLOUD is likely
to cause conflicts as there are many clouds out there.
Much of the problem here is the limited namespace/concept space
and people get stuck saying IRR sucks when IRR/whois is often a method
to access a database. We have advanced quite far in the past 20 years
in how to build databases, realtime query methods, etc.. but it's not
made it to the routing ecosystem.
Jared Mauch | pgp key available via finger from jared at puck.nether.net
clue++; | http://puck.nether.net/~jared/ My statements are only mine.