[34584] in North American Network Operators' Group

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

Re: BGP Question - how do work around pigheaded ISPs

daemon@ATHENA.MIT.EDU (Stephen Griffin)
Tue Feb 13 04:13:52 2001

Message-Id: <200102130910.EAA22543@elektra.ultra.net>
In-Reply-To: <Pine.BSF.4.21.0102130028450.20345-100000@courier.netrail.net> from "Daniel L. Golding" at "Feb 13, 2001 00:29:28 am"
To: dan@netrail.net (Daniel L. Golding)
Date: Tue, 13 Feb 2001 04:10:36 -0500 (EST)
From: Stephen Griffin <stephen.griffin@rcn.com>
Cc: nanog@merit.edu
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Errors-To: owner-nanog-outgoing@merit.edu


A really quick inspection shows:
91.16.23.0/24 AS11770, although is is a history entry only at the moment:
route-views.oregon-ix.net>sh ip bgp 91.16.23.0
BGP routing table entry for 91.16.23.0/24, version 6427742
Paths: (23 available, no best path)
  Not advertised to any peer
  8517 9000 2548 1239 11770 (history entry)
...

103.22.7.0/24 AS9768
route-views.oregon-ix.net>sh ip bgp 103.22.7.0
BGP routing table entry for 103.22.7.0/24, version 6099648
Paths: (25 available, best #10)
  Not advertised to any peer
  2551 1239 3608 3608 3608 9768
    163.179.232.37 from 163.179.232.37 (163.179.232.37)
      Origin incomplete, localpref 100, valid, external
...

Stolen is a lot harder to find.

In the referenced message, Daniel L. Golding said:
> 
> Information on stolen or squatted address space should be published, to
> ensure maximum shame for those involved.
> 
> Daniel Golding                           NetRail,Inc.
> "Better to light a candle than to curse the darkness"
> 
> On Mon, 12 Feb 2001, John Fraizer wrote:
> 
> > 
> > On Mon, 12 Feb 2001, Joe Provo wrote:
> > 
> > > 
> > > I have been aware of several times when squatted, stolen, or 
> > > misconfigured-into-others'-space has been caught by registry-minded
> > > filters.  Specifically regarding slices of classical B-space and
> > > not yet allocated A-space.
> > > 
> > > Cheers,
> > > 
> > > Joe
> > > 
> > 
> > Any time a network is caught announcing non-allocated address space, the
> > registry should bill them accordingly.  If they refuse to pay, the
> > registry should yank their ASN.  That would be strong encouragement to do
> > the right thing.
> > 
> > ---
> > John Fraizer
> > EnterZone, Inc




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