[dhcwg] dhcpv6-24: sending Information-request via multicast
Thomas Narten <narten@us.ibm.com> Wed, 08 May 2002 15:09 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11311 for <dhcwg-archive@odin.ietf.org>; Wed, 8 May 2002 11:09:53 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id LAA04502 for dhcwg-archive@odin.ietf.org; Wed, 8 May 2002 11:10:01 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA04114; Wed, 8 May 2002 11:07:46 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA04051 for <dhcwg@optimus.ietf.org>; Wed, 8 May 2002 11:07:42 -0400 (EDT)
Received: from e21.nc.us.ibm.com (e21.nc.us.ibm.com [32.97.136.227]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11014 for <dhcwg@ietf.org>; Wed, 8 May 2002 11:07:33 -0400 (EDT)
Received: from southrelay02.raleigh.ibm.com (southrelay02.raleigh.us.ibm.com [9.37.3.209]) by e21.nc.us.ibm.com (8.12.2/8.12.2) with ESMTP id g48F7f64058738 for <dhcwg@ietf.org>; Wed, 8 May 2002 11:07:42 -0400
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.9.21]) by southrelay02.raleigh.ibm.com (8.11.1m3/NCO/VER6.1) with ESMTP id g48F7fQ107180 for <dhcwg@ietf.org>; Wed, 8 May 2002 11:07:41 -0400
Received: from rotala.raleigh.ibm.com (narten@localhost) by rotala.raleigh.ibm.com (8.11.6/8.11.6) with ESMTP id g48F85N19250 for <dhcwg@ietf.org>; Wed, 8 May 2002 11:08:05 -0400
Message-Id: <200205081508.g48F85N19250@rotala.raleigh.ibm.com>
To: dhcwg@ietf.org
Date: Wed, 08 May 2002 11:08:05 -0400
From: Thomas Narten <narten@us.ibm.com>
Subject: [dhcwg] dhcpv6-24: sending Information-request via multicast
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: <dhcwg.ietf.org>
X-BeenThere: dhcwg@ietf.org
> If the client has an IPv6 address of sufficient scope, the > client MAY choose to send the Information-request message to the > All_DHCP_Servers multicast address. This MAY leaves things very ambiguous. When should they do this? When not? It would be much better to have a clear algorithm the client always follows. Otherwise, you'll get different implementations doing different things, which is probably not good for interoperability. Thomas _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] dhcpv6-24: sending Information-request vi… Thomas Narten
- RE: [dhcwg] dhcpv6-24: sending Information-reques… Bernie Volz (EUD)
- RE: [dhcwg] dhcpv6-24: sending Information-reques… Ralph Droms