Can you help me explain trace route in a very detailed way?! Well of course I know the purpose and how to use it but I just need to grab or explain something to our operations group about its output. They're so used to identifying latencies based on traces. Like for example, there's a website that they need to access where all their tools or application resides. Then they claim that there's latency, what they do is they conduct trace route and if they see a very high number somewhere in the middle, they are already assuming that this hop is causing the overall latency. Like the trace has total of 15 hops but at the 8th hop, it displays 500ms average but from 9th to 15th hop is low. And if you do a ping, the RTT is very low. I know there are routers that doesn't prioritize ICMPs that's why they response time is quite high.
I just need to know how to explain these things to them. In a very simple term and in a technical term. Thanks guys. :)
:: I'm hoping that I can get something different from this URL, http://www.nanog.org/meetings/nanog45/abstracts.php?pt=MTE4NSZuYW5vZzQ1&nm=nanog45