RE: [dhcwg] DHCP_DECLINE question

Richard Barr Hibbs <rbhibbs@pacbell.net> Wed, 06 March 2002 23:34 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 SAA15140 for <dhcwg-archive@odin.ietf.org>; Wed, 6 Mar 2002 18:34:41 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id SAA27781 for dhcwg-archive@odin.ietf.org; Wed, 6 Mar 2002 18:34:45 -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 SAA27713; Wed, 6 Mar 2002 18:32:26 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA27688 for <dhcwg@optimus.ietf.org>; Wed, 6 Mar 2002 18:32:24 -0500 (EST)
Received: from mta7.pltn13.pbi.net (mta7.pltn13.pbi.net [64.164.98.8]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15076 for <dhcwg@ietf.org>; Wed, 6 Mar 2002 18:32:19 -0500 (EST)
Received: from BarrH63p601 ([63.193.193.26]) by mta7.pltn13.pbi.net (iPlanet Messaging Server 5.1 (built May 7 2001)) with SMTP id <0GSK007RHS1ZCG@mta7.pltn13.pbi.net> for dhcwg@ietf.org; Wed, 06 Mar 2002 15:32:23 -0800 (PST)
Date: Wed, 06 Mar 2002 15:31:47 -0800
From: Richard Barr Hibbs <rbhibbs@pacbell.net>
Subject: RE: [dhcwg] DHCP_DECLINE question
In-reply-to: <4.3.2.7.2.20020305140546.00b82b20@funnel.cisco.com>
To: dhcwg@ietf.org
Reply-to: rbhibbs@pacbell.net
Message-id: <JCELKJCFMDGAKJCIGGPNKEAEDLAA.rbhibbs@pacbell.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Content-type: text/plain; charset="us-ascii"
Content-transfer-encoding: 7bit
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Content-Transfer-Encoding: 7bit
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: 7bit

I'll try to clarify the points.....

--Barr


> -----Original Message-----
> From: Ralph Droms
> Sent: Tuesday, March 05, 2002 11:36
>
> Barr - comments in line...
>
> At 10:09 AM 3/5/2002 -0800, Richard Barr Hibbs wrote:
>
> > > Good point re. potential for looping.  This behavior should only
> > > occur when the parameters change between the DHCPOFFER and the
> > > DHCPACK.  Presumably, on the retry after the RELEASE, the OFFER
> > > and the ACK will match and the client will accept the parameters
> > > in the ACK.
> > >
> >...while the parameters would likely match, it might be that the client
> >still doesn't like the values and that takes us back to the
> initial question
> >about the meaning of DHCPDECLINE.
>
> Barr - I'm with you here up to the last few words.  What do you mean by
> "...the initial question about the meaning of DHCPDECLINE"?
>
...assuming I understood the question properly, it could be restated as "Can
a client use DHCPDECLINE to reject an offered IP address after sending
DHCPREQUEST?"  Implied in that is what recourse is there for a client that
doesn't like some or all of a server's offer?


<*Snip!*>

> I agree that there is no explicit mechanism for rejecting a lease (as
> opposed to releasing it) once the server sends the REQUEST.  Is
> there much
> of a difference between the two cases?
>
...only that if a client releases the lease it is likely to get the same
lease the next time it starts the cycle....  I don't think we should be
making a change to the protocol at this point lacking sufficient evidedence
of harm caused by the current behavior, but it does seem a bit of an
oversight....

--Barr


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