Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!seismo!husc6!necntc!ames!ucbcad!ucbvax!CCV.BBN.COM!brescia From: brescia@CCV.BBN.COM (Mike Brescia) Newsgroups: comp.protocols.tcp-ip Subject: Name of NIC (was: twg, and nic not knowing its domain name..) Message-ID: <8707181004.AA09360@ucbvax.Berkeley.EDU> Date: Sat, 18-Jul-87 06:41:51 EDT Article-I.D.: ucbvax.8707181004.AA09360 Posted: Sat Jul 18 06:41:51 1987 Date-Received: Sat, 18-Jul-87 21:04:56 EDT References: <12318755656.17.MKL@SRI-NIC.ARPA> Sender: daemon@ucbvax.BERKELEY.EDU Distribution: world Organization: The ARPA Internet Lines: 11 NIC.SRI.COM is not and was never the official name of any host. SRI-NIC.ARPA is equally hard to remember. I suggest that NIC be a name at the top level of the domain tree, and be the obvious place. The reason is that the Net.Info.Ctr is a top level resource, not actually some branch of SRI.COM. Suppose SRI changes its corporate name? Suppose ARPA removes its support of the internet, and the ARPA domain goes away? The (THE) NIC service should still be available by name. Mike.