do I need to maintain with RADB?

Heather Schiller heather.schiller at verizonbusiness.com
Thu Feb 19 17:21:13 CST 2009


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

====================================================
  Heather Schiller    Verizon Business
  Customer Security    1.800.900.0241
  IP Address Management    help4u at verizonbusiness.com
=====================================================

Jon Lewis wrote:
> On Thu, 19 Feb 2009, Zaid Ali wrote:
> 
>> 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.
> 
> 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.
> 
> ----------------------------------------------------------------------
>  Jon Lewis                   |  I route
>  Senior Network Engineer     |  therefore you are
>  Atlantic Net                |
> _________ http://www.lewis.org/~jlewis/pgp for PGP public key_________
> 
> 





More information about the NANOG mailing list