[dhcwg] Client identification clarification

"Guja, ArturX" <ArturX.Guja@intel.com> Thu, 20 September 2001 08:07 UTC

Received: from optimus.ietf.org (ietf.org [] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03447; Thu, 20 Sep 2001 04:07:14 -0400 (EDT)
Received: from optimus.ietf.org (localhost []) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA14884; Thu, 20 Sep 2001 04:06:17 -0400 (EDT)
Received: from ietf.org (odin []) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA14864 for <dhcwg@optimus.ietf.org>; Thu, 20 Sep 2001 04:06:16 -0400 (EDT)
Received: from calliope1.fm.intel.com (fmfdns01.fm.intel.com []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03425 for <dhcwg@ietf.org>; Thu, 20 Sep 2001 04:06:12 -0400 (EDT)
Received: from fmsmsxvs042.fm.intel.com (fmsmsxv042-1.fm.intel.com []) by calliope1.fm.intel.com (8.9.1a+p1/8.9.1/d: relay.m4, v 1.42 2001/09/04 16:24:19 root Exp $) with SMTP id IAA05290 for <dhcwg@ietf.org>; Thu, 20 Sep 2001 08:05:34 GMT
Received: from fmsmsx29.FM.INTEL.COM ([]) by fmsmsxvs042.fm.intel.com (NAVGW with SMTP id M2001092001050229760 for <dhcwg@ietf.org>; Thu, 20 Sep 2001 01:05:02 -0700
Received: from alpha.igk.intel.com ([]) by fmsmsx29.FM.INTEL.COM with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id T2TNQQFZ; Thu, 20 Sep 2001 01:05:38 -0700
Received: by alpha.igk.intel.com with Internet Mail Service (5.5.2653.19) id <NMB58BRM>; Thu, 20 Sep 2001 10:05:32 +0200
Message-ID: <413FBB0BA5AED1119122000083234B1A0247B427@alpha.igk.intel.com>
From: "Guja, ArturX" <ArturX.Guja@intel.com>
To: "Dhcwg (E-mail)" <dhcwg@ietf.org>
Date: Thu, 20 Sep 2001 10:05:28 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-2"
Subject: [dhcwg] Client identification clarification
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

Ok, here comes another one :)))

How does the server identify the client? How does it choose 
what address to assign to the client?

How I understood the answers:
The clients sends a DUID option, that's clear (although the 
nature of the DUID is still unspecified, let's assume I've got
random numbers or ethernet addresses as DUIDs). Fine.

A client binding is a <DUID, IAID> tuple. Fine.

So does it suffice, if a server has an address range, eg:
from 2000:: to 2000::ffff and assigns hose addresses to
all clients requesting them.

Or should there be some other distinction? What I'm looking
here for is some way to let the administrator manage the 
addresses in a better way.

One thing, though: The server does not know anything else
about the client, apart from the DUID and IAID. Or does it???

Thank you all for your help here :)))

Artur G.

dhcwg mailing list