Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!apple!bbn.com!kwe
From: kwe@bbn.com (Kent W. England)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: Map of Internet
Message-ID: <6822@archive.BBN.COM>
Date: 3 Jun 91 21:34:06 GMT
References: <552.283ced35@vax87.aud.auc.dk> <1991May27.173507.20501@watson.ibm.com> <1991May28.161202.14155@salt.acc.com> <1991May28.212310.23424@Spies.COM>
Sender: news@bbn.com
Organization: BBN/STD
Lines: 24

In article <1991May28.212310.23424@Spies.COM> joshua@Spies.COM (Joshua 
Geller) writes:
> In article <1991May28.161202.14155@salt.acc.com> art@opal.acc.com (Art 
> Berggreen) writes:
> 
> |>But a map showing just the backbones and regionals (and their 
interconnection
> |>points) might be doable and useful. 
> 
> Hey, I'd settle for one of the backbones. Backbones and regionals would 
cause
> me to literally faint in ecstatsy. 

Even that is not so simple as it would seem.  For example, only a few 
people have actually seen a topology map of the new NSFnet T3 backbone.  
The public maps I see are a little "cloudy".   I'm not complaining, mind 
you, just noting that maps are hard for a number of reasons.

I think there is a IETF mapping working group underway or soon to happen 
that will be addressing some of the technical issues related to maps of 
the Internet.  But topology mapping is never going to be easy and topology 
maps are not routing maps, which is what most people really need to see.

--Kent