I believe we do peer with ANS. However, I am not familiar with the specifics of concurrent PSI/SURAnet T3 and the current state of the ANS routing database. I've forwarded your message on to ground troops in the vicinity to see if they can give you a hand. Thanks, mf P.S. I've edit'ed Cc: to cut down on multiple messages to individuals. (they weren't swallowed by a mailer) ----------
At 11:17 AM 4/8/96, Mark S. Fedor wrote:
Perhaps you can tell me where PSI connects, good sir... By my count it's MAE-East and CIX and nowhere else. There are a few major backbones not at the Chicago NAP. And none of the majors are at MAE-Chicago or any of the MAEs other than East and West.
PSINet connects to MAE-west, MAE-East, MAE-East+, CIX, and the SWAB (little known SMDS Washington (DC) Area Bypass).
mf
But, d#*(^&-it, they don't peer with ANS, and therefore we at NSF cannot get to hosts like fnc.gov. We, denizens of the NSF who have the good fortune to have been caught in the institution's un-debated switchover to PSInet. Arghhh!
This is the way some hosts that are not yet forced through PSI *can* get to fnc.gov:
traceroute to web1.hpc.org (192.187.8.59), 30 hops max, 40 byte packets 1 gw.cise.nsf.gov (128.150.55.1) 4 ms 4 ms 4 ms 2 wtn-6.bbnplanet.net (192.221.39.13) 6 ms 7 ms 6 ms 3 wtn-9.bbnplanet.net (128.167.26.9) 6 ms 9 ms 6 ms 4 wtn-8.bbnplanet.net (128.167.7.8) 22 ms 17 ms 30 ms 5 cpk-9.bbnplanet.net (128.167.212.1) 7 ms 37 ms 46 ms 6 cpk-5.bbnplanet.net (128.167.252.5) 9 ms 7 ms 9 ms 7 mae-east.bbnplanet.net (4.0.1.18) 22 ms 15 ms 14 ms 8 mae-east.ans.net (192.41.177.140) 9 ms 11 ms 10 ms 9 ft3.cnss56.Washington-DC.t3.ans.net (140.222.56.4) 10 ms 10 ms 11 ms 10 mf0.cnss58.Washington-DC.t3.ans.net (140.222.56.194) 14 ms 13 ms 12 ms 11 ft0.enss146.t3.ans.net (140.222.146.1) 13 ms 12 ms 11 ms 12 web1.hpc.org (192.187.8.59) 10 ms 15 ms 14 ms
--SG
____________________________________________ Steve Goldstein, National Science Foundation +1(703)306-1949 Ext. 1119 "Let's not procrastinate until next week!"