[48446] in North American Network Operators' Group
Re: Bogon list
daemon@ATHENA.MIT.EDU (Sean M. Doran)
Tue Jun 4 19:58:24 2002
To: david_mcgaugh@eli.net, jabley@automagic.org
Cc: bgreene@cisco.com, nanog@merit.edu, ras@e-gerbil.net,
robt@cymru.com
Date: Tue, 4 Jun 2002 16:57:52 -0700 (PDT)
From: smd@clock.org (Sean M. Doran)
Errors-To: owner-nanog-outgoing@merit.edu
| While on the subject of IXP blocks, we also ended up redistributing the
| IXP blocks and sending them to our BGP customers (who do not receive a
| default) so that traceroutes and such from Looking Glasses do not break.
| They can then choose to filter them as they wish.
This is backwards. Do not break the architecture to fix a broken
looking glass (or to work around bad interpretations of real-world
traceroute results). Spend a few minutes scripting your looking
glass software so that if it sees a well-known target, or an expected
real-world result (1918 addresses that YOU are using, with expected
ttl-distance), it returns a "sanitized" result to a naive
looking glass user.
I wonder if there exists the possibility of a useful (perhaps open source)
generalized expert system to interpret traceroute data?
"configure; make; make install" is probably even easier than
breaking one's filter lists to leak prefixes all over the place.
Sean. (that was a hint. you know who you are.)
