RE: [dhcwg] RFC3004 - User class question.

"McCullagh, Matthew (Matt)" <mm63@lucent.com> Tue, 05 February 2002 18:55 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 NAA13667 for <dhcwg-archive@odin.ietf.org>; Tue, 5 Feb 2002 13:55:36 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id NAA25042 for dhcwg-archive@odin.ietf.org; Tue, 5 Feb 2002 13:55:38 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA22641; Tue, 5 Feb 2002 13:12:35 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA22612 for <dhcwg@ns.ietf.org>; Tue, 5 Feb 2002 13:12:33 -0500 (EST)
Received: from auemail1.firewall.lucent.com (auemail1.lucent.com [192.11.223.161]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11649 for <dhcwg@ietf.org>; Tue, 5 Feb 2002 13:12:31 -0500 (EST)
Received: from sp0002exch001p.wins.lucent.com (h135-88-24-89.lucent.com [135.88.24.89]) by auemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g15ICUx11116 for <dhcwg@ietf.org>; Tue, 5 Feb 2002 13:12:31 -0500 (EST)
Received: by sp0002exch001p.es.lucent.com with Internet Mail Service (5.5.2650.21) id <CR49HVSV>; Tue, 5 Feb 2002 19:12:29 +0100
Message-ID: <C75D175831F6D411893200508BB3A020012C7DA2@sp2002exch001u.es.lucent.com>
From: "McCullagh, Matthew (Matt)" <mm63@lucent.com>
To: 'Ted Lemon' <mellon@nominum.com>
Cc: "'dhcwg@ietf.org'" <dhcwg@ietf.org>
Subject: RE: [dhcwg] RFC3004 - User class question.
Date: Tue, 05 Feb 2002 19:12:27 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain
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

Hi Ted, 

I guess I was reading into it what I wanted/needed to read into it !
I'll certainly look into the ISC option - any ideas how scalable it is. 

Am checking around to see if we have a copy of your book here ! 

Many thanks for quick response ! 

Matt


-----Original Message-----
From: Ted Lemon [mailto:mellon@nominum.com]
Sent: martes, 05 de febrero de 2002 18:42
To: McCullagh, Matthew (Matt)
Cc: 'dhcwg@ietf.org'
Subject: Re: [dhcwg] RFC3004 - User class question.


> If I am reading this correctly, any DHCP server which states that it is
> compliant with RFC 3004 "should" be able to have multiple pools defined
> using the same private address range - distinguished by user-class.

Yikes!   This is a lesson in careful wording of drafts.   I am sure that 
that was not the intention of the authors!   It certainly wasn't how I read 
it during the review.

The user class option is just intended to be available to the DHCP server 
as a way to differentiate between clients based on user-supplied 
information.   How the server uses this is up to the implementor and the 
server administrator.   There is no requirement that servers support the 
policy you're talking about.

Having said that, I'd say it's pretty likely that the server you're using 
does support address allocation based on user class.   The ISC server does,
  for sure.   There's an example of how to configure it in the DHCP
Handbook.
.. :')

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