routing meltdown


Perhaps "policies, procedures & data" is a better word than "protocols" used
in the generic sense.

I want to route things differently based on the time of day, whether
or not a particular network is seeing heavy traffic, and what my
horoscope said today. I can implement this much more easily on a
workstation where I have source code than I can convince Cisco to
implement it.

I wonder how many ISP operations have a requirement to support
internet-wide routing based on such factors as traffic load or
your horoscope. Let me personally assure you that if there will be enough
demand, then there will be enough supply.