From: Scott Huddle <huddle@mci.net> Oarnet is an MCI customer as well. they have a T3 connection to our network at Washington and another to the Chicago area. I think you might be confusing traffic to them over their dedicated line at Washington as going over MAE-East.

Thanks, I checked again, and you are correct, it no longer seems to go via the same paths in the DC area that it did in February or March.... Every month, a different path! But then, this is all beside the point! The point was that another more direct path exists, via Chicago, that would stop swamping your DC routers, and reduce my recorded congestion. If only these regional providers would cooperate. However, this little public exchange has stimulated some local comment, and there may be some cooperation at hand. I am deeply gratified! ---- And I see that you are working on the links, even changing the inverse names for the same address: Recording Wed Feb 28 17:42:29 1996 10: 204.70.1.102 core1-hssi-3.WestOrange.mci.net. (226 ms) (273 ms) (214 ms) 11: 204.70.1.106 core2-hssi-2.Washington.mci.net. (229 ms) (238 ms) (231 ms) 12: 204.70.1.73 core1-aip-4.Washington.mci.net. (240 ms) *** (248 ms) 13: 204.70.2.3 border3-fddi-0.Washington.mci.net. (231 ms) (235 ms) (240 ms) 14: *** 204.70.58.10 ohio-state-u--oarnet.Washington.mci.net. (267 ms) (235 ms) 15: *** 206.21.252.2 oeb-fddi-gwoeb2.columbus.oar.net. (1298 ms) (376 ms) 16: 199.18.105.250 (266 ms) (254 ms) *** 17: *** *** 192.20.239.132 ds2.internic.net. (277 ms) Recording Mon Mar 18 22:25:27 1996 10: 204.70.1.102 core1-hssi-3.WestOrange.mci.net. (226 ms) (273 ms) (214 ms) 11: 204.70.1.106 core2-hssi-2.Washington.mci.net. (243 ms) (379 ms) (240 ms) 12: 204.70.74.52 borderx1-fddi-1.Washington.mci.net. (325 ms) (281 ms) (250 ms) 13: 204.70.74.102 mae-east-plusplus.Washington.mci.net. (251 ms) *** (284 ms) 14: *** *** *** 15: *** *** *** 16: *** *** *** Recording Tue Apr 16 20:29:01 1996 9: 204.70.1.102 core1-hssi-3.WestOrange.mci.net. (214 ms) (201 ms) (201 ms) 10: 204.70.4.129 core1.Washington.mci.net. (307 ms) (367 ms) (214 ms) 11: 204.70.2.3 border3-fddi-0.Washington.mci.net. (206 ms) (205 ms) (208 ms) 12: 204.70.58.10 ohio-state-university.Washington.mci.net. (223 ms) (218 ms) (217 ms) 13: 206.21.252.2 oeb-fddi-gwoeb2.columbus.oar.net. (227 ms) (219 ms) (218 ms) 14: 199.18.105.250 (442 ms) (245 ms) (226 ms) 15: *** *** *** 16: *** *** *** 17: *** *** *** Note that the last 2 times, I still couldn't reach my final destination, ds2.internic.net. Of course, I usually only record the trace when there is an ongoing problem.... WSimpson@UMich.edu Key fingerprint = 17 40 5E 67 15 6F 31 26 DD 0D B9 9B 6A 15 2C 32 BSimpson@MorningStar.com Key fingerprint = 2E 07 23 03 C5 62 70 D3 59 B1 4F 5E 1D C2 C1 A2