[e2e] Question about propagation and queuing delays

[Randy Bush]

> The traceroute from here to Cisco is:
> 
> traceroute to irp-view7.cisco.com (171.70.65.144), 64 hops max, 40  
> byte packets
> 1  ip-242-001 (140.109.242.1)  8.177 ms  10.311 ms  16.018 ms

one can not measure to you as there is blockage

traceroute to 140.109.242.1 (140.109.242.1), 64 hops max, 40 byte packets
 1  psg2 (147.28.0.5)  0.268 ms  0.283 ms  0.355 ms
 2  ...
10  s4-4-3-0.br0.tpe.tw.rt.ascc.net (140.109.251.106)  167.259 ms  166.778 ms  166.749 ms
11  * * *

but one can measure up to the block and

pathchar to 140.109.251.106 (140.109.251.106)
 mtu limited to 1500 bytes at local host
 doing 32 probes at each of 45 sizes (64 to 1500 by 32)
 0 rip (147.28.0.39)
 |    33 Mb/s,   133 us (631 us)
 1 psg2 (147.28.0.5)
 |    42 Mb/s,   103 us (1.12 ms)
 2 e2.psg1.psg.com (147.28.1.5)
 |   ?? b/s,   -93 us (0.91 ms)
 3 sl-gw11-sea-0-1.sprintlink.net (144.232.9.61)
 |   182 Mb/s,   16 us (1.01 ms)
 4 sl-bb20-sea-9-2.sprintlink.net (144.232.6.125)
 |   337 Mb/s,   135 us (1.31 ms)
 5 so-3-0-0.gar1.Seattle1.Level3.net (209.0.227.133)
 |   1138 Mb/s,   28 us (1.38 ms)
 6 so-7-0-0.mp1.Seattle1.Level3.net (64.159.1.81)
 |   ?? b/s,   8.61 ms (18.5 ms)
 7 as-0-0.bbr2.SanJose1.Level3.net (64.159.0.218)
 |   1873497444986126 Mb/s,   77 us (18.7 ms)
 8 so-14-0.hsa4.SanJose1.Level3.net (4.68.114.158)
 |   256 Mb/s,   69 us (18.9 ms)
 9 REACH-SERVIC.hsa4.Level3.net (64.152.81.10)
 |    32 Mb/s,   63.7 ms (147 ms),  +q 21.3 ms (84.9 KB)
10 s4-4-3-0.br0.tpe.tw.rt.ascc.net (140.109.251.106)
10 hops, rtt 145 ms (147 ms), bottleneck  32 Mb/s, pipe 583768 bytes

observe the queue on the 9/10 hop

randy