|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |
To: Ellen.Hoffman@ub.cc.umich.edu Cc: com-priv@psi.com In-Reply-To: Your message of Wed, 17 Jul 91 12:47:00 -0400. Date: Wed, 17 Jul 91 14:59:53 EDT From: "Manavendra K. Thakur" <thakur@zerkalo.harvard.edu> >>>>> On Wed, 17 Jul 91 12:47:00 EDT, Ellen.Hoffman@ub.cc.umich.edu said: > Long ago Merit began using city rather than mid-level names because > more than one regional may be connected at a single location. For > example, here in Ann Arbor there is a site physically located at the > University of Michigan which connects both MichNet (Merit's > statewide network in Michigan) and CICnet to the backbone. > Ellen Hoffman > Merit Can you explain the policy that governs the naming of T3 nodes? Why, for example, are T3 nodes called things like: t3-2.cnss49.t3.nsf.net t3-0.cnss105.t3.nsf.net t3-0.aa-enss.t3.nsf.net Why not use city or other geographically-descriptive names (as is done at T1 nodes, per your explanation above) instead of these inscrutable names? Manavendra K. Thakur Internet: thakur@zerkalo.harvard.edu Systems Programmer, High Energy Division BITNET: thakur@cfa.BITNET Harvard-Smithsonian Center for DECNET: CFA::thakur Astrophysics UUCP: ...!uunet!mit-eddie!thakur
|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |