Hi, need some advise here. Do I still need to maintain my objects (and pay) RADB? I use ARIN as source and all my route objects can be verified with a whois.
Thanks,
Zaid
If your objects are all maintained via another routing registry (ARIN's, altdb, etc.) and you don't care to maintain objects with radb.ra.net, then you do not need to pay RADB maintenance fees.
Is there a good source to explain the whole RADB "system", and
tools/processes people use to maintain routing policies/filters based on it?
I'd like to both review and make sure my current understanding is accurate,
and have a doc to send people to.
Thanks for any pointers!
--D
Is the ARIN registry free, then?
Jon Lewis wrote:
No. Use of a routing registry is not required.. ARIN's, RADB's or otherwise. You might want to check out this presentation:
http://nanog.org/meetings/nanog44/abstracts.php?pt=ODg4Jm5hbm9nNDQ=&nm=nanog44
This is an entirely different statement from "Your globally unique IP's should to be allocated to you in an RIR's database before someone routes them for you" For example 207.76.0.0/14 is allocated to us, you can see it in ARIN's whois, but it is not registered in ARIN's IRRD, or any other.
As further proof - note that people publicly route resources that aren't registered in a "routing registry database" or even registered to them by an RIR at all:
http://www.cidr-report.org/as2.0/#Bogons
I'm not saying this is a good thing.. I would like to see the system drastically improved and secured.. I'm just pointing out how things actually work today.
Check w/ your provider, but in most cases you will find that they don't use a route registry.
--Heather
No. Use of a routing registry is not required.
^ always
some wise upstreams require it.
and it is a good idea to be in the irr.
and there are free/open irr servers.
randy
If you are happy using a RR which appears to only rely on a MAIL-FROM auth
scheme then the ARIN RR is fine. If you'd like to have a stronger auth
scheme available you might want to look at RADB.
Leo
It is the IRR system. You want to read up on http://www.irr.net/ and
the various RPSL docs (RFC2622, RFC2650, and related). Choice of a
registry to use will dictate your toolset; someone already noted auth
method limitations, but some will support more elements of the language
or extend with local needs. If you are large ehough that the time
investment makes sense, you can just run your own routing registry
and be free of those limitations.
Local-use tools of interest would include ease-of-driving your updates
with your selected registry [irrpt (http://sourceforge.net/projects/irrpt/)]
and the recent updates to IRRToolset (http://irrtoolset.isc.org/ -
see http://www.uknof.org.uk/uknof12/Kerr-IRRtoolset.pdf).
Cheers!
Joe
No. Use of a routing registry is not required.. ARIN's, RADB's or
otherwise.
It's not required, however it's a good operational best-practice, and
it helps with automating prefix-list generation/management.
Check w/ your provider, but in most cases you will find that they don't use
a route registry.
Most is a very strong word. A number of large providers do,
Level3/Savvis/GX to name a few. Verizon might not, but they're
becoming increasingly less relevant in the transit marketplace with
every passing day... 
Drive Slow,
Paul Wall