[inet-ops] Cidr report here?

Randy Bush randy at psg.com
Mon Dec 13 23:23:34 EST 2004


as folk are censored by an fool from another non-ops-run list,
having this as one place to discuss the cidr and ris reports
would be good.

the real question is what can effectively be done to get
clueless crap out of the routing tables.  the s/n in bgp
approaches that of a mailing list.  but it may easier to
apply technology to the bgp universe; e.g., see discussion
on c-nsp of auto-drop of covered prefixes.  to get actual
discussion moving, my opinion is appended.

randy

---

From: randy at psg.com (Randy Bush)
Date: Wed Dec  1 20:51:25 2004
Subject: [c-nsp] Growing BGP tables
References: <OF49CD5C93.07A11904-ON85256F5D.004AD609-85256F5D.004CD194 at census.gov>
	<0D6AB216-4403-11D9-8994-000D93282A96 at Hughes.com.au>
Message-ID: <16814.29973.27522.38883 at ran.psg.com>

i proposed to rodney today, there are three types of prefix
pollution.
  o pure crap, such as that we see on top of the weekly
    report
  o someone traffic engineering
  o legitimate holes (someone moving from at&t's 12/8)

a hardcore <bleep> such as i might just filter them all

a friendlier type might just dump longer prefixes if they
had the same origin asn (the new part of the suggestion)

a southern californian might only dump a longer prefix
if it has the same next hop as the covering prefix

randy



More information about the inet-ops mailing list