[50107] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

RE: verio arrogance

daemon@ATHENA.MIT.EDU (Daniel Golding)
Thu Jul 18 17:35:54 2002

From: "Daniel Golding" <dgolding@sockeye.com>
To: "Ralph Doncaster" <ralph@istop.com>, <up@3.am>
Cc: <nanog@merit.edu>
Date: Thu, 18 Jul 2002 17:35:27 -0400
In-Reply-To: <Pine.LNX.4.21.0207181624530.20232-100000@cpu1693.adsl.bellglobal.com>
Errors-To: owner-nanog-outgoing@merit.edu


RADB is largely meaningless, in terms of authorization or authority to
advertise. However, if you have a properly delegated SWIP entry for the
block, few providers will request LOA. Those who do, should probably be
avoided.

I still like the idea of using the DNS system for this, since there are
already authoritative reverse delegations. (i.e. AS to IP block mapping)

- Daniel Golding

> > On Thu, 18 Jul 2002, Ralph Doncaster wrote:
> >
> > > And your suggestion has technical deficiencies as well.  I
> have a leased
> > > line between Toronto and Ottawa, so I want to announce my
> Ottawa IPs to my
> > > Toronto transit provider as well as an Ottawa transit
> provider.  And the
> > > reverse for the Toronto IPs.  My understand is trying to
> punch holes in PA
> > > space is much more difficult than de-aggregating ARIN PI space.
> >
> > I can't really see why, as long as the provider has punched the
> > appropriate hole for your aggregate in their filters.  More specific
> > routes always win out.  Or am I missing your point?
>
> If the block isn't assigned to you by ARIN, I've encountered cases where
> network operators request an LOA before accepting the announcement, even
> if there is an RADB entry for it.  As well, if you have PA space and your
> upstream allocates you a 66.x for example, then you're back to square one.
>
> -Ralph
>
>


home help back first fref pref prev next nref lref last post