IRRd-Discuss
Date Prev | Date Next |
Date Index |
Thread Index |
Author Index |
Historical
Implementation practices
- From: Jason Lixfeld
- Date: Tue Oct 08 15:59:22 2002
Greetings,
I'm wondering what the general concensus is with regards to IRR
implementation practices? I've done a little digging and have tried to
find practical examples of networks listing their detailed peering sets
and detailed aut-num objects to see how their import and export entries
look for things like community strings, MEDs, Local-Pref, etc. I
haven't had much luck in finding any detailed, practical examples.
I can come up with only two conclusions: 1) Security policies for most
networks networks likely mandate against disclosing routing policies by
means of mirroring your database with RADB. 2) People just don't use
the irrd, hence no detailed entries.
I'd like to think that the former is true, so if that's the case, what
are some of the best practices for maintaining both a public and a
private database? Is it just as simple as creating a database, in my
case FASTVIBE which has your general maintainer, as and route objects
which is mirrored with RADB then having a private,
un-mirrored/non-exported database FV-INTERNAL which contains all the
nuts and bolts?
|