RE: [dhcwg] draft-chown-dhc-dual-stack-00

Changming Liu <cliu@netscreen.com> Wed, 03 March 2004 23:01 UTC

Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03283 for <dhcwg-archive@odin.ietf.org>; Wed, 3 Mar 2004 18:01:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AyfMR-00046S-Ic for dhcwg-archive@odin.ietf.org; Wed, 03 Mar 2004 18:01:07 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i23N1604015734 for dhcwg-archive@odin.ietf.org; Wed, 3 Mar 2004 18:01:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AyfMM-00045A-OD for dhcwg-web-archive@optimus.ietf.org; Wed, 03 Mar 2004 18:01:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03239 for <dhcwg-web-archive@ietf.org>; Wed, 3 Mar 2004 18:00:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AyfMJ-00030f-00 for dhcwg-web-archive@ietf.org; Wed, 03 Mar 2004 18:00:59 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AyfLU-0002pb-00 for dhcwg-web-archive@ietf.org; Wed, 03 Mar 2004 18:00:09 -0500
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1AyfKW-0002er-00 for dhcwg-web-archive@ietf.org; Wed, 03 Mar 2004 17:59:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AyfKP-0003mS-3d; Wed, 03 Mar 2004 17:59:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AyfKG-0003ly-S2 for dhcwg@optimus.ietf.org; Wed, 03 Mar 2004 17:58:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03068 for <dhcwg@ietf.org>; Wed, 3 Mar 2004 17:58:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AyfKE-0002ck-00 for dhcwg@ietf.org; Wed, 03 Mar 2004 17:58:50 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AyfJK-0002Tu-00 for dhcwg@ietf.org; Wed, 03 Mar 2004 17:57:54 -0500
Received: from [63.126.135.18] (helo=mail2.netscreen.com) by ietf-mx with esmtp (Exim 4.12) id 1AyfIe-0002Bb-00 for dhcwg@ietf.org; Wed, 03 Mar 2004 17:57:12 -0500
Received: from ns-ca.netscreen.com (ns-ca-local [10.100.3.35]) by mail2.netscreen.com (Switch-3.1.3/Switch-3.1.0) with ESMTP id i23MuZ9u012635; Wed, 3 Mar 2004 14:56:39 -0800 (PST)
Received: by NS-CA with Internet Mail Service (5.5.2653.19) id <FV1JSW6N>; Wed, 3 Mar 2004 14:56:35 -0800
Message-ID: <1B6D4CAFB8CA554EB1A0925685A07DFC0342C6A6@MONTEREY.netscreen.com>
From: Changming Liu <cliu@netscreen.com>
To: 'Ted Lemon ' <mellon@fugue.com>, Changming Liu <cliu@netscreen.com>
Cc: "'''dhcwg@ietf.org' ' '" <dhcwg@ietf.org>
Subject: RE: [dhcwg] draft-chown-dhc-dual-stack-00
Date: Wed, 03 Mar 2004 14:56:34 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

This is done on the client. No table is required execpt one additional
attribute is difined in client data structure. Once the client learns any
configuration info, its preference is checked to see if it is better or
equal than currentlly installed. If so, install it and the system start to
use it. Otherwise, ignore it (actually installed in the client table). There
are some minor details which can be easy to be figured out.  


For devices with multiple DHCP client enabled, I guess usually some kind of
config may be needed anyway. Otherwise the latest one will always be used
based on the above rule as they will have the same preference by default.
But you do have a point.

As I said earlier, this can be done on the server side as well but some
co-ordination is required among these server, which may not be possible in
some environment.

CHangming.

-----Original Message-----
From: Ted Lemon
To: Changming Liu
Cc: ''dhcwg@ietf.org' '
Sent: 3/3/2004 2:35 PM
Subject: Re: [dhcwg] draft-chown-dhc-dual-stack-00

On Mar 3, 2004, at 5:18 PM, Changming Liu wrote:
> It is a very simple solution: when enabling a DHCP client on an
> interface, allow the end user to define a preference value from 0 to 
> 255 and
> default to 128.

So this is done on the client?   Is preference assigned to different 
classes of DHCP server (e.g., v4 vs. v6) or different server 
identification information, or what?   I can envision a table on the 
client that contains a list of server ids and preferences, although 
this seems not so helpful in the sense that the client now has to be 
configured before it can use the network.

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