Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: notesfiles Path: utzoo!linus!philabs!cmcl2!seismo!harvard!talcott!panda!genrad!decvax!tektronix!hplabs!hp-pcd!hpcnoa!dat From: dat@hpcnoa.UUCP (dat) Newsgroups: net.mail Subject: Re: Will it ever work? Message-ID: <49800002@hpcnof.UUCP> Date: Sun, 4-Aug-85 04:57:00 EDT Article-I.D.: hpcnof.49800002 Posted: Sun Aug 4 04:57:00 1985 Date-Received: Mon, 12-Aug-85 00:35:23 EDT References: <47300002@hpfclo.UUCP> Organization: Hewlett-Packard - Fort Collins, CO Lines: 44 Nf-ID: #R:hpfclo:47300002:hpcnof:49800002:000:1995 Nf-From: hpcnof!dat Aug 4 00:57:00 1985 John, (jad = John A. Dilley) (inside information :-) ) It seems to me that what you are proposing is a 'standardized' (NBS-type) uucp system including an internet path standard. This could be done...but given the anarchy of the UNIX community, I think that the better solution is to 'lead rather than force': If a worthwhile standard for mail addresses was generated and it was GOOD, then let a few choice sites get it up and running...then the others will gradually come into the fold as they find it is a better program than what they currently run. For a historical example of this, consider the gradual rise to fame of 'sendmail'... Another nickel: I am against assigning unique machine names because this implies that machines will have a central database of all the other available nodes in the system and will be able to 'figure out' how to get from 'a' to 'b' in the (hopefully) least expensive way. From experience trying to maintain a SMALL database of just the machines available in HP, I don't think that this approach is feasable. It is more often than not that the database doesn't have the address of a machine (like hpfclo) or can't suggest a reasonable way to get there! 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 (and I for one do NOT relish the thought of sending mail to joe@XdcE34w or some other forcibly unique identifier!) Failing geographical area, how about 'zipcode' coupled with an international code for country?? That is, 'hpcnof@80525/USA' or something. Any thoughts? --- Dave Taylor HP Colorado Networks ..ihnp4 \ ..decvax!hplabs \ !hpfcla!d_taylor ..ucbvax!hplabs / ..hpbbn /