IETF Logo Mail Archive

RE: [dhcwg] dhcpv6-24: randomization delay before invoking DHC

Ralph Droms <rdroms@cisco.com> Thu, 09 May 2002 05:47 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 BAA03813 for <dhcwg-archive@odin.ietf.org>; Thu, 9 May 2002 01:47:41 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id BAA01910 for dhcwg-archive@odin.ietf.org; Thu, 9 May 2002 01:47:50 -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 BAA01869; Thu, 9 May 2002 01:46:10 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA01843 for <dhcwg@optimus.ietf.org>; Thu, 9 May 2002 01:46:08 -0400 (EDT)
Received: from funnel.cisco.com (funnel.cisco.com [161.44.168.79]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA03749 for <dhcwg@ietf.org>; Thu, 9 May 2002 01:45:59 -0400 (EDT)
Received: from rdroms-w2k.cisco.com (sjc-vpn3-221.cisco.com [10.21.64.221]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id BAA13342; Thu, 9 May 2002 01:45:33 -0400 (EDT)
Message-Id: <4.3.2.7.2.20020509013910.03139e20@funnel.cisco.com>
X-Sender: rdroms@funnel.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 09 May 2002 01:42:06 -0400
To: dhcwg@ietf.org
From: Ralph Droms <rdroms@cisco.com>
Subject: RE: [dhcwg] dhcpv6-24: randomization delay before invoking DHC
Cc: rdroms@cisco.com
In-Reply-To: <66F66129A77AD411B76200508B65AC69B4D3D0@EAMBUNT705>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
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

This text from section 5.2 of RFC2462 would seem to preclude a host policy 
that allows ManagedFlag to be always true:

       ManagedFlag      Copied from the M flag field (i.e., the
                        "managed address configuration" flag) of the most
                        recently received Router Advertisement message.
                        The flag indicates whether or not addresses are
                        to be configured using the stateful
                        autoconfiguration mechanism. It starts out in a
                        FALSE state.

- Ralph

At 08:44 PM 5/8/2002 -0500, Bernie Volz (EUD) wrote:

>There always is the possibility that a host's policy could force the 
>ManagedFlag to be TRUE always? Though why you'd want to do this is not 
>clear to me.





_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg

v2.23.0 | Report a Bug | By Email