Re: [dhcwg] ARP reply vs. ARP request to announce address acquired from DHCP
Ted Lemon <Ted.Lemon@nominum.com> Tue, 14 January 2003 06:01 UTC
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA06219; Tue, 14 Jan 2003 01:01:55 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0E6FKJ22884; Tue, 14 Jan 2003 01:15:20 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0E6EUJ22839 for <dhcwg@optimus.ietf.org>; Tue, 14 Jan 2003 01:14:30 -0500
Received: from toccata.fugue.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA06146 for <dhcwg@ietf.org>; Tue, 14 Jan 2003 01:00:00 -0500 (EST)
Received: from nominum.com (dsl-64-193-175-153.telocity.com [64.193.175.153]) by toccata.fugue.com (8.11.6/8.6.11) with ESMTP id h0E60OP25224; Tue, 14 Jan 2003 00:00:24 -0600 (CST)
Date: Tue, 14 Jan 2003 00:03:18 -0600
Subject: Re: [dhcwg] ARP reply vs. ARP request to announce address acquired from DHCP
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Mime-Version: 1.0 (Apple Message framework v551)
Cc: dhcwg@ietf.org, Stuart Cheshire <cheshire@apple.com>, zeroconf@merit.edu, Thomas Narten <narten@us.ibm.com>, Erik Nordmark <Erik.Nordmark@sun.com>
To: Thamer Al-Harbash <tmh@whitefang.com>
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <Pine.BSF.4.51.0301140028120.92289@helena.whitefang.com>
Message-Id: <E0D8157E-2785-11D7-A7EA-00039367340A@nominum.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.551)
Content-Transfer-Encoding: 7bit
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Id: <dhcwg.ietf.org>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
> No need to update the RFC for this. Just send an ARP reply from > the client and let the OS send all the requests it wants :-) That's a fine engineering solution, but it's a lousy protocol solution - we can't specify two broadcasts. A better way to phrase my question would be, "are you objecting to what is specified in Stuart's draft?" _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] ARP reply vs. ARP request to announce add… Ted Lemon
- [dhcwg] Re: ARP reply vs. ARP request to announce… Brad Hards
- Re: [dhcwg] ARP reply vs. ARP request to announce… Thamer Al-Harbash
- Re: [dhcwg] ARP reply vs. ARP request to announce… Ted Lemon
- Re: [dhcwg] ARP reply vs. ARP request to announce… Thamer Al-Harbash
- Re: [dhcwg] ARP reply vs. ARP request to announce… Ted Lemon
- Re: [dhcwg] ARP reply vs. ARP request to announce… Ted Lemon
- Re: [dhcwg] ARP reply vs. ARP request to announce… Thamer Al-Harbash
- Re: [dhcwg] ARP reply vs. ARP request to announce… Thamer Al-Harbash
- [dhcwg] Re: ARP reply vs. ARP request to announce… John Schnizlein
- [dhcwg] Re: ARP reply vs. ARP request to announce… Ted Lemon