Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!lll-crg!nike!ucbcad!ucbvax!hplabs!hpcea!hpfcdc!hpfclp!diamant
From: diamant@hpfclp.HP.COM (John Diamant)
Newsgroups: net.mail
Subject: Re: Change of address notification
Message-ID: <1660005@hpfclp.HP.COM>
Date: Thu, 18-Sep-86 23:37:11 EDT
Article-I.D.: hpfclp.1660005
Posted: Thu Sep 18 23:37:11 1986
Date-Received: Mon, 22-Sep-86 07:48:43 EDT
References: <15635@ucbvax.BERKELEY.EDU>
Organization: H-P Fort Collins
Lines: 22

> I don't see any conflict either.  When I talk about John to my mother, she
> knows whom I mean.  when I talk about John to my soccer team, they know whom
> I mean (at least until a) I'll get a baby brother also named John or b) we
> recruit another player named John).
> 
> And when I talk to my ARPA-host, I expect it to know which other host I mean
> when I try to send mail to rick@seismo .... I don't think that't so much to
> ask.

Actually, that type of context is exactly what you get.  However, the
appropriate context is not ARPA, it is COM  or GOV, etc.  If you are also
in the GOV domain, instead of typing rick@seismo.CSS.GOV, you can type in
rick@seismo.CSS, or if you are in the CSS.GOV domain, then you really can
address him as rick@seismo.  The reason the ARPA context is not sufficient
is that it is just too large.  Would you expect your soccer team to know which
John you are referring to if your team had 10,000 members!?


John Diamant
Systems Software Operation	UUCP:  {hplabs,hpfcla}!hpfclp!diamant
Hewlett Packard Co.		ARPA/CSNET: diamant%hpfclp@hplabs.HP.COM
Fort Collins, CO