Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!usc!dianne.usc.edu!blarson
From: blarson@dianne.usc.edu (bob larson)
Newsgroups: comp.mail.misc
Subject: By address nameservers (was Re: Internet and Bitnet Directories?)
Message-ID: <21380@usc.edu>
Date: 23 Nov 89 23:59:14 GMT
References: <1360@sagepub.UUCP> <1810004@hpiag0.IAG.HP.COM> <1989Nov17.014854.23205@terminator.cc.umich.edu> <5266@yunexus.UUCP> <2172@prune.bbn.com> <5299@yunexus.UUCP> <6920@portia.Stanford.EDU> <1989Nov22.184823.28878@gpu.utcs.utoronto.ca>
Sender: news@usc.edu
Reply-To: blarson@dianne.usc.edu (bob larson)
Organization: USC AIS, Los Angeles
Lines: 22

In article <1989Nov22.184823.28878@gpu.utcs.utoronto.ca> dennis@gpu.utcs.utoronto.ca (Dennis Ferguson) writes:
>"UTORVM1" is an NJE network level
>address, it is used by the networking software on bitnet machines for
>routing purposes.  Its nearest functional analogue (and a pretty good
>match in terms of function, at that) for hosts on an IP network would
>be something like 128.100.63.2.INTERNET.  I think the reason the NIC
>won't register .BITNET (and shouldn't register CREN.ORG or CREN.NET to
>be used for the same purpose) is about the same reason they don't register
>a .INTERNET domain with the usage above.

But they DO register such things!  Actuallty, it would be
2.63.100.128.IN-ADDR.ARPA, and they are registered so that IP numbers
can be translated into domain names.  The numbers are backwards so
domian registration can be deligatedin the proper manner.  (Queries
about the 125.128.IN-ADDR.ARPA domain will be handled by USC's
nameservers.)  If there was such a need for bitnet addresses, I don't
think the NIC would object to having it set up.  The facts that many
internet users don't know such things exist is a credit to the
designers and implimentors.
Bob Larson	blarson@dianne.usc.edu		usc!dianne!blarson
--**		To join Prime computer mailing list		**---
info-prime-request@ais1.usc.edu		usc!ais1!info-prime-request