Here's a couple of operational questions for those who build
filters from IRRdb's.
Background:
* peval / rpsl.merit.edu *may* be incorrectly evaluating
RIPE database entries currently - but this isn't my main
thrust. The scary thing is suddenly what I'm 99% sure used
to work (expanding AS Macros) now silently fails if they
are in RIPE. [for details see the end]
* I'm not saying the server is broken (I guess it has something to
do with the 'server is running at low priority' line), but if I had
this in an automatic filter generating run, it would generate
the RADB stuff just fine, and silently filter out all RIPE based
peerings. Even if it's working perfectly correctly, the questions
are still interesting, at least to me.
Questions:
* Does anyone actually do build filters without running
their own complete database mirror, i.e. do they rely real
time on a database working. If so, which one?
* Does anyone let this config their routers automatically? To peers
customers, transits, or all three? Or do you rely on humans to
reinstall the lists once autogenerated?
* If it's just a fact of life that occasionally this thing turns up duff
data, and if people are in general doing automatic installation, what
data validation heuristics are used?
I'll summarize to the list any off-list replies that are interesting.