RE: [dhcwg] Address selection for Information-request/Reply messa ges

"Bernie Volz (EUD)" <Bernie.Volz@am1.ericsson.se> Thu, 01 May 2003 20:06 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 QAA06464 for <dhcwg-archive@odin.ietf.org>; Thu, 1 May 2003 16:06:04 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h41KCEd32275 for dhcwg-archive@odin.ietf.org; Thu, 1 May 2003 16:12: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 h41KCE832271 for <dhcwg-web-archive@optimus.ietf.org>; Thu, 1 May 2003 16:12:14 -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 QAA06394 for <dhcwg-web-archive@ietf.org>; Thu, 1 May 2003 16:05:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19BKLH-00062u-00 for dhcwg-web-archive@ietf.org; Thu, 01 May 2003 16:07:43 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19BKLG-00062p-00 for dhcwg-web-archive@ietf.org; Thu, 01 May 2003 16:07:42 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h41K6o829885; Thu, 1 May 2003 16:06:50 -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 h41K0Z828312 for <dhcwg@optimus.ietf.org>; Thu, 1 May 2003 16:00:35 -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 PAA05269 for <dhcwg@ietf.org>; Thu, 1 May 2003 15:53:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19BKA0-0005w4-00 for dhcwg@ietf.org; Thu, 01 May 2003 15:56:04 -0400
Received: from imr1.ericy.com ([208.237.135.240]) by ietf-mx with esmtp (Exim 4.12) id 19BK9u-0005u3-00 for dhcwg@ietf.org; Thu, 01 May 2003 15:55:59 -0400
Received: from mr5.exu.ericsson.se (mr5u3.ericy.com [208.237.135.124]) by imr1.ericy.com (8.12.9/8.12.9) with ESMTP id h41Jqrat005272; Thu, 1 May 2003 14:52:53 -0500 (CDT)
Received: from eamrcnt761.exu.ericsson.se (eamrcnt761.exu.ericsson.se [138.85.133.39]) by mr5.exu.ericsson.se (8.12.9/8.12.9) with ESMTP id h41JqrNe011136; Thu, 1 May 2003 14:52:53 -0500 (CDT)
Received: by eamrcnt761.exu.ericsson.se with Internet Mail Service (5.5.2656.59) id <W7YCATDF>; Thu, 1 May 2003 14:52:52 -0500
Message-ID: <A1DDC8E21094D511821C00805F6F706B067F5D25@eamrcnt715.exu.ericsson.se>
From: "Bernie Volz (EUD)" <Bernie.Volz@am1.ericsson.se>
To: 'Robert Elz' <kre@munnari.oz.au>, Ralph Droms <rdroms@cisco.com>
Cc: dhcwg@ietf.org
Subject: RE: [dhcwg] Address selection for Information-request/Reply messa ges
Date: Thu, 01 May 2003 14:50:51 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C3101A.65602620"
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>

The problem comes about if we change All_DHCP_Servers to include relays to
listen for messages on this address.

Because now both the relays and the routers would forward messages, and the
relays may forward messages forwarded by routers, you could (depending on
the number of relays and routers), get a fairly large packet storm.

The DHCPv6 protocol will work fine and doesn't break. Though the load placed
on the servers and network may not be desireable. That is the point.

Bottom line, IMHO, this is a bad idea. We shouldn't have relays listening
for All_DHCP_Servers traffic. And, if we don't do that, allowing Information-Request
sent directly to All_DHCP_Servers would require site multicast to work and if
it doesn't or is disabled, these clients would fail to receive the requested
information if the server isn't local.

- Bernie

-----Original Message-----
From: Robert Elz [mailto:kre@munnari.oz.au]
Sent: Thursday, May 01, 2003 3:17 PM
To: Ralph Droms
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] Address selection for Information-request/Reply
messages 


    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