Re: [dhcwg] Client identification clarification

Ralph Droms <rdroms@cisco.com> Wed, 10 October 2001 14:44 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 KAA11478; Wed, 10 Oct 2001 10:44:37 -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 KAA17876; Wed, 10 Oct 2001 10:43:15 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA17832 for <dhcwg@optimus.ietf.org>; Wed, 10 Oct 2001 10:43:13 -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 KAA11448 for <dhcwg@ietf.org>; Wed, 10 Oct 2001 10:43:11 -0400 (EDT)
Received: from rdroms-w2k.cisco.com (dhcp-161-44-149-111.cisco.com [161.44.149.111]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id KAA24215; Wed, 10 Oct 2001 10:42:38 -0400 (EDT)
Message-Id: <4.3.2.7.2.20011010102201.00bbe400@funnel.cisco.com>
X-Sender: rdroms@funnel.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Wed, 10 Oct 2001 10:26:49 -0400
To: "Guja, ArturX" <ArturX.Guja@intel.com>
From: Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] Client identification clarification
Cc: "Dhcwg (E-mail)" <dhcwg@ietf.org>
In-Reply-To: <413FBB0BA5AED1119122000083234B1A0247B427@alpha.igk.intel.c om>
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

The DUID uniquely identifies a client, but gives no additional information 
about a client.

The DHCPv6 server can make decisions about how to assign addresses based on 
any other available information: what other options the client has 
requested, what link the client is attached to, etc.

DHCPv4 a "Vendor class identifier" option, through which a client can pass 
more information to the server.   We haven't defined a "Vendor class 
identifier" for DHCPv6.  If there is interest, we can consider adding it to 
the spec doc.

- Ralph

At 10:05 AM 9/20/2001 +0200, Guja, ArturX wrote:
>Ok, here comes another one :)))
>
>Questions:
>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
>dhcwg@ietf.org
>http://www1.ietf.org/mailman/listinfo/dhcwg


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