Re: [dhcwg] Address selection for Information-request/Reply messages
Robert Elz <kre@munnari.OZ.AU> Thu, 01 May 2003 19:27 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 PAA02856 for <dhcwg-archive@odin.ietf.org>; Thu, 1 May 2003 15:27:09 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h41JXKF18870 for dhcwg-archive@odin.ietf.org; Thu, 1 May 2003 15:33:20 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h41JXK818867 for <dhcwg-web-archive@optimus.ietf.org>; Thu, 1 May 2003 15:33:20 -0400
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 PAA02821 for <dhcwg-web-archive@ietf.org>; Thu, 1 May 2003 15:26:38 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h41JVE818193; Thu, 1 May 2003 15:31:14 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h41JPW816652 for <dhcwg@optimus.ietf.org>; Thu, 1 May 2003 15:25:32 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01910 for <dhcwg@ietf.org>; Thu, 1 May 2003 15:18:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19BJc6-0005Yr-00 for dhcwg@ietf.org; Thu, 01 May 2003 15:21:02 -0400
Received: from ip26.coe.tnet.co.th ([203.146.155.26] helo=fuchsia.home) by ietf-mx with esmtp (Exim 4.12) id 19BJbz-0005Xz-00 for dhcwg@ietf.org; Thu, 01 May 2003 15:20:56 -0400
Received: from delta.cs.mu.OZ.AU (delta.ex0.home [192.168.192.22]) by fuchsia.home with ESMTP id h41JIohX003528; Fri, 2 May 2003 02:18:51 +0700 (ICT)
Received: from munnari.OZ.AU (localhost [127.0.0.1]) by delta.cs.mu.OZ.AU (8.11.6/8.11.6) with ESMTP id h41JH9J20091; Fri, 2 May 2003 02:17:11 +0700 (ICT)
From: Robert Elz <kre@munnari.OZ.AU>
To: Ralph Droms <rdroms@cisco.com>
cc: dhcwg@ietf.org
Subject: Re: [dhcwg] Address selection for Information-request/Reply messages
In-Reply-To: <4.3.2.7.2.20030501094136.00b8f828@funnel.cisco.com>
References: <4.3.2.7.2.20030501094136.00b8f828@funnel.cisco.com> <4.3.2.7.2.20030411113053.042c1cb0@funnel.cisco.com> <4.3.2.7.2.20030411113053.042c1cb0@funnel.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Fri, 02 May 2003 02:17:09 +0700
Message-ID: <20089.1051816629@munnari.OZ.AU>
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>
Date: Thu, 01 May 2003 09:52:19 -0400 From: Ralph Droms <rdroms@cisco.com> Message-ID: <4.3.2.7.2.20030501094136.00b8f828@funnel.cisco.com> | Infact, it would be important to note that a site MUST NOT both | implement multicast and configure relay agents to listen on | All_DHCP_Servers, as such a configuration would result in the | servers receiving multiple copies of client messages. Surely that happens with relay agents anyway? Any site with half a brain, or more, configures multiple relay agents for redundancy (assuming it also has multiple routers for redundancy of course). If the protocol can't handle multiple copies of messages being delivered to the servers, it badly needs fixing (but I actually doubt it has that defect). kre _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] WG last call on draft-ietf-dhc-dhcpv6-sta… Ralph Droms
- Re: [dhcwg] WG last call on draft-ietf-dhc-dhcpv6… JINMEI Tatuya / 神明達哉
- Re: [dhcwg] WG last call on draft-ietf-dhc-dhcpv6… SHIRASAKI Yasuhiro
- RE: [dhcwg] WG last call on draft-ietf-dhc-dhcpv6… juha.wiljakka
- RE: [dhcwg] WG last call on draft-ietf-dhc-dhcpv6… Bound, Jim
- [dhcwg] Address selection for Information-request… Ralph Droms
- [dhcwg] When to invoke the stateless DHCPv6 messa… Ralph Droms
- [dhcwg] Update of parameters supplied through sta… Ralph Droms
- [dhcwg] Stateless DHCPv6 == "Other stateful confi… Ralph Droms
- Re: [dhcwg] Address selection for Information-req… Robert Elz