Path: utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!pasteur!ucbvax!CLASH.CISCO.COM!cire
From: cire@CLASH.CISCO.COM
Newsgroups: comp.protocols.tcp-ip
Subject: Re: a proposed modification to ARP
Message-ID: <8807200551.AA21211@ucbvax.Berkeley.EDU>
Date: 19 Jul 88 19:33:09 GMT
References: <8807181502.AA20987@monk.proteon.com>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 27

>> Date: Mon, 18 Jul 88 11:02:26 EDT
>> From: jas@proteon.com (John A. Shriver)
>> To: DCP@quabbin.scrc.symbolics.com
>> Cc: tcp-ip@sri-nic.arpa
>> Subject: a proposed modification to ARP
>> Status: O
>> 
>> ARP is one of the quintessentially elegant protocols.  An enormous
>> amount of power is provided for a very simple implmentation.  Let's
>> keep it that way.

Here here.  I also have a question.  If ARP was built to use
multicasts wouldn't that just replace one problem with another
one?  The hosts on the network would have to be properly configured
to use an appropriate multicast or group of multicasts.  How well
will this interoperate with other vendor's implementations?  Is
all this worth it?

-c
cire|eric

Eric B. Decker
cisco Systems
Menlo Park, California

email:	cire@cisco.com
uSnail: 1360 Willow Rd.,  Menlo Park, CA  94025
Phone : (415) 326-1941