RE: [dhcwg] DHCP_DECLINE question

"Burcak Beser" <burcak@juniper.net> Thu, 07 March 2002 17:43 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 MAA09907 for <dhcwg-archive@odin.ietf.org>; Thu, 7 Mar 2002 12:43:01 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id MAA16178 for dhcwg-archive@odin.ietf.org; Thu, 7 Mar 2002 12:43:06 -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 MAA15815; Thu, 7 Mar 2002 12:41:00 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA15782 for <dhcwg@optimus.ietf.org>; Thu, 7 Mar 2002 12:40:57 -0500 (EST)
Received: from beta.jnpr.net (natint.juniper.net [207.17.136.129]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09735 for <dhcwg@ietf.org>; Thu, 7 Mar 2002 12:40:49 -0500 (EST)
Received: from antiproton.jnpr.net ([172.24.18.101]) by beta.jnpr.net with Microsoft SMTPSVC(5.0.2195.3779); Thu, 7 Mar 2002 09:40:23 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Subject: RE: [dhcwg] DHCP_DECLINE question
Date: Thu, 07 Mar 2002 09:40:23 -0800
Message-ID: <5B671CEC7A3CDA40BA4A8B081D7B046CFD782B@antiproton.jnpr.net>
Thread-Topic: [dhcwg] DHCP_DECLINE question
Thread-Index: AcHFkxABSt/8p1vgTYSIS4Wan93JWwAas1aA
From: Burcak Beser <burcak@juniper.net>
To: Ted Lemon <Ted.Lemon@nominum.com>, Ralph Droms <rdroms@cisco.com>
Cc: dhcwg@ietf.org
X-OriginalArrivalTime: 07 Mar 2002 17:40:23.0951 (UTC) FILETIME=[2912B9F0:01C1C5FF]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id MAA15786
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
Content-Transfer-Encoding: 8bit

I believe that right now the DCHP protocol is growing to include more
than just the IP address but to fulfill the name 'Dynamic Host
Configuration'. As with time the distinction between configuration and
provisioning is getting blurred. If you look into the recent DHCP work
you can see this happening we have Relay Agent Options (and suboptions),
User Class Option, Lease Query. It is my impression is that even though
the IP addressing issues are central to the DHCP supplied information
the configuration extends beyond just IP. The real issue is that should
we start to think about correcting/adding to the RFC such that the
protocol would be extended to include more and more
configuration/provisioning syntax. 

In short, even though we do not see any problems today with the DHC
protocol, we need to think ahead.

-burcak

-----Original Message-----
From: Ted Lemon [mailto:Ted.Lemon@nominum.com]
Sent: Wednesday, March 06, 2002 8:41 PM
To: Ralph Droms
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] DHCP_DECLINE question


> In my opinion, a client is within the spec if it sends a DHCPRELEASE 
> immediately after receiving a DHCPACK (for whatever reason).  The 
> DHCPRELEASE will terminate the lease and make the address available
for 
> reassignment without causing the server to mark the address as "not to
be 
> assigned".

True.

> There is still the open question of whether we want to *recommend*
this 
> behavior...

Right.   I'd say we shouldn't, because in all likelihood it's going to 
result in the client looping behavior about which Barr is concerned.
I 
think that we are trying to fix a nonexistant problem here, and the fix 
seems much worse than the problem, particularly since I've never
observed 
the problem happening in real life.


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

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