Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: notesfiles Path: utzoo!linus!decvax!tektronix!hplabs!hp-pcd!hpfcla!jad From: jad@hpfcla.UUCP (jad) Newsgroups: net.mail Subject: Re: Will it ever work? Message-ID: <47300003@hpfclo.UUCP> Date: Mon, 5-Aug-85 20:26:00 EDT Article-I.D.: hpfclo.47300003 Posted: Mon Aug 5 20:26:00 1985 Date-Received: Mon, 12-Aug-85 20:56:05 EDT References: <47300002@hpfclo.UUCP> Organization: Hewlett-Packard - Fort Collins, CO Lines: 36 Nf-ID: #R:hpfclo:47300002:hpfclo:47300003:000:1484 Nf-From: hpfclo!jad Aug 5 16:26:00 1985 > /***** hpfclo:net.mail / hpcnof!dat / 12:57 am Aug 4, 1985*/ > > The alternative approach that I like is to take advantage of > the information that IS unique for each machine - the geographical > location! For example, consider if the machine I was posting on > was called 'hpcnof@FortCollinsColorado' rather than just 'hpcnof'... > this would eliminate all duplicate names without forcing a 'unique' > naming scheme on everyone ... > > Any thoughts? First off, I agree that it may be quite impossible to "force" conversion. Leading it may work a lot better -- if you have something which works better than what is currently out there, and are willing to give it away cheap (and it works and does not take too much time to bring up, and etc.), then it will get used. I am confident of this. Next, re: 'hpcnof@FortCollinsColorado' ... what's wrong with hpcnof.CNO.FC.HP.COM? Or even hpcnof.HP.COM? The hpcnof would not have to be unique within the entire network (agreed -- global uniqueness over the ENTIRE WORLD is a pretty awful thought, esp. in the chaotic world of UUCP); it would only have to be unique within its "local" domain (.CNO. or .HP. above). Now what about that silly 7 letter host name limit that some brain damaged software out there forces???? (for those without inside info) -- jad -- John A. Dilley, FSD Fort Collins, CO ARPA: terrapin@Purdue.EDU UUCP: {ihnp4}! hpfcla!jad PHONE: (303)226-3800 x4166