Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!purdue!tut.cis.ohio-state.edu!ucbvax!FORALIE.ICS.HAWAII.EDU!torben
From: torben@FORALIE.ICS.HAWAII.EDU (Torben Nielsen)
Newsgroups: comp.protocols.tcp-ip
Subject: (none)
Message-ID: <89Oct12.021232hst.30@foralie.ics.Hawaii.Edu>
Date: 12 Oct 89 12:12:30 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 27

Merton,

>Date:	Thu, 12 Oct 89 00:45:30 HST
>From:	mcc@WLV.IMSD.CONTEL.COM (Merton Campbell Crockett)
>Message-Id: <8910121045.AA23199@WLV.IMSD.CONTEL.COM>
>To:	GMILIEFS@MITVMA.MIT.EDU, kasten%interlan.interlan.com@RELAY.CS.NET,
>	tcp-ip@NIC.DDN.MIL, torben@foralie.ics.Hawaii.Edu
>Subject: Re:  Multihoming
>Status: RO
>

......
......

>Torben's workstation may be considered multihomed in its local environment
>but would not be from my perspective if there is only one route to his LAN.

There may be only one route from your perspective, but there're definitely
two paths. And you could reach the host via either path. One address is
128.171.1.2 and the other is 132.160.1.3. As it turns out,it's even the same
number of hops from you and a nameserver could return you either address.

What I was responding to was the comment abot systems not supporting
multiple addreses belonging to one name. That's clearly not the case
today.

						Torben