[dhcwg] Edit #4 of DHCPv6 spec

Ralph Droms <rdroms@cisco.com> Tue, 14 May 2002 21:01 UTC

Received: from optimus.ietf.org (ietf.org [] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06773 for <dhcwg-archive@odin.ietf.org>; Tue, 14 May 2002 17:01:02 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id RAA24248 for dhcwg-archive@odin.ietf.org; Tue, 14 May 2002 17:01:13 -0400 (EDT)
Received: from optimus.ietf.org (localhost []) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA23297; Tue, 14 May 2002 16:57:25 -0400 (EDT)
Received: from ietf.org (odin []) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA23277 for <dhcwg@ns.ietf.org>; Tue, 14 May 2002 16:57:23 -0400 (EDT)
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06562 for <dhcwg@ietf.org>; Tue, 14 May 2002 16:57:09 -0400 (EDT)
Received: from funnel.cisco.com (funnel.cisco.com []) by sj-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g4EKupHt000624 for <dhcwg@ietf.org>; Tue, 14 May 2002 13:56:52 -0700 (PDT)
Date: Tue, 14 May 2002 16:56:51 -0400
From: Ralph Droms <rdroms@cisco.com>
To: dhcwg@ietf.org
Message-ID: <Pine.GSO.4.44.0205141644260.28862-100000@funnel.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Subject: [dhcwg] Edit #4 of DHCPv6 spec
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.

Response: Remove All_DHCP_Servers as destination for Information-request
message; deleted cited text from section 18.1.5.

dhcwg mailing list