[168267] in North American Network Operators' Group
Re: Internet Routing Registries - RADb, etc
daemon@ATHENA.MIT.EDU (courtneysmith@comcast.net)
Thu Jan 16 13:27:22 2014
Date: Thu, 16 Jan 2014 18:26:11 +0000 (UTC)
From: courtneysmith@comcast.net
To: nanog@nanog.org
In-Reply-To: <mailman.12252.1389893409.40664.nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On 16/01/2014 14:32, Blake Hudson wrote:=20
> Thanks for the responses, these objects are all older. However, none of=
=20
> them are stale or from previous owners, allocations, etc. Each of these=
=20
> objects were posted to their respective IRR's after the IP space was=20
> allocated to us. This leads me to believe that the individual IRR's reall=
y=20
> do very little checking for accuracy and their usefulness is then=20
> questionable.=20
Oh yeah. I got hit by that sort of thing a week or two back. It wasn't=20
origin: AS14179 / mnt-by: MAINT-AS28071, by any chance? AS14179 have been=
=20
hijacking chunks of space from the various registries.=20
Nick=20
------------------------------=20
Another possible scenario.=20
a.b.c.d/24->small_isp->regional_isp->Level3=20
Imagine a regional ISP is a customer of Level3. Level3 filters the regional=
ISP based on Regional ISP's IRR objects. Small ISP buys access from Region=
al. Small ISP doesn't maintain their own objects. Regional ISP wants Small'=
s business so doesn't force the issue. Regional manually maintains the filt=
ers. Regional adds objects under Regional's maintainer whenever Small reque=
st a filter change. If they don=E2=80=99t, Level3 wont accept the announcem=
ent from them. Customer with a.b.c.d/24 has no idea about any of this.=20
Now we are years later. Customer has either moved to another small ISP or S=
mall ISP found a different regional ISP.=20
a.b.c.d/24->small_isp->new_regional_isp->Level3=20
or=20
a.b.c.d/24->new_small_isp->new_regional_isp->Level3=20
The original Regional ISP didnt remember to delete all the objects related =
to Small ISP's customers. The objects just sit there until one day customer=
has interest in registring their own object. Customer sees entries for the=
ir /24 under Regional ISP's objects. Customer knows they have never done bu=
siness with Regional. Also the objects are newer than the customer's alloca=
tion from their RIR. Customer comes to the conclusion that Regional ISP mus=
t have been hi-jacking their space or doing some other naughtiness.=20
Proxy registering objects isn't a good idea. However, the number of network=
s with allocations from ARIN registering objects in any IRR appears to be e=
xtremely low. ARIN doesn=E2=80=99t charge you more to use rr.arin.net. Folk=
s seem to not be aware of IRR or perceive it provides no benefit to them. W=
ill RPKI adoption suffer the same fate?=20
