Bogon list

Messy traceroutes make the helpdesk phone ring.

Messy architecture is worse!

There's two ways to deal with the "messy traceroute problem":

  1. looking glasses - use them to compare traceroutes,
     point people at them, couple them with ample notes
     on how to interpret the results of multiple traceroutes
     launched from a variety of sources

     utility & education leads to wisdom, and away from
     "nuisance" phonecalls. everyone wins.

  2. if you'd rather stem the tide of calls without
     helping your users much, break traceroute.

     a/ make it not work in practically all cases
        on the grounds that the catharsis of its spurious
        reputation as a powerful diagnostic tool is LONG overdue

     b/ intercept low-ttl packets and return them with "better"
        information
    
        some MPLS people have documented ways to do this, even

        it works, although if you do it some ways, you generate
        media attention. check your nanog records

Basically, arguing that the routing system should carry around
even more information is backwards. It should carry less.
If IXes need numbers at all (why???) then use RFC 1918 addresses
and choose one of the approaches above to deal with questions
about why 1918 addresses result in "messy traceroutes."

Fewer routes, less address consumption, tastes great, less filling.

  Sean.

> Messy traceroutes make the helpdesk phone ring.

Messy architecture is worse!

Agreed. An inconsistent architecture is a messy one. Why treat exchange subnets differently to any other bit of backbone infrastructure? Why number point-to-point links with even locally-unique addresses?

Slashdot readers wielding traceroute can make an annoying pain in the side of your head, but traceroute and ping are not without their uses. Ask people who are cursed with running poorly-documented X.25 networks (surely there must be some left) how nice it would be to be able to map the network in-band. Ask them why they don't have any hair left, while you're at it.

There's two ways to deal with the "messy traceroute problem":

[messier 1]

[messier 2]

You don't need to deal with the messy traceroute problem if your consistent and clean architecture doesn't happen to make traceroute mess :slight_smile:

Joe