[dhcwg] rfc2131 and releasing leases

Thamer Al-Harbash <tmh@whitefang.com> Sat, 07 December 2002 18:43 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04109 for <dhcwg-archive@odin.ietf.org>; Sat, 7 Dec 2002 13:43:22 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gB7Ijn927199 for dhcwg-archive@odin.ietf.org; Sat, 7 Dec 2002 13:45:49 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB7Ijnv27196 for <dhcwg-web-archive@optimus.ietf.org>; Sat, 7 Dec 2002 13:45:49 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04099 for <dhcwg-web-archive@ietf.org>; Sat, 7 Dec 2002 13:42:51 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB7Ihav27150; Sat, 7 Dec 2002 13:43:36 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB7GtVv21902 for <dhcwg@optimus.ietf.org>; Sat, 7 Dec 2002 11:55:31 -0500
Received: from gw.xargs.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA01630 for <dhcwg@ietf.org>; Sat, 7 Dec 2002 11:52:34 -0500 (EST)
Received: (qmail 3265 invoked from network); 7 Dec 2002 16:55:26 -0000
Received: from gw.xargs.com (democracy@192.168.11.1) by gw.xargs.com with SMTP; 7 Dec 2002 16:55:26 -0000
Date: Sat, 07 Dec 2002 08:55:26 -0800
From: Thamer Al-Harbash <tmh@whitefang.com>
X-X-Sender: shadows@gw.xargs.com
To: dhcwg@ietf.org
Message-ID: <Pine.LNX.4.44.0212070850520.2945-100000@gw.xargs.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Subject: [dhcwg] rfc2131 and releasing leases
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Id: <dhcwg.ietf.org>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>

Hi,

I understand under rfc2131 that there is no way to acknowledge a
release from a DHCP client. Are there any extensions, or any plans
on incorporating a release acknowledgement?

Problem:

Client sends DHCP release. Client shuts down.

Server doesn't get the release datagram because it was dropped
before it reached the Server. The server holds onto the lease.

How is this scenario avoided by the server if no acknowledgement is
ever sent to the client? The problem becomes worse when the client
machine reboots to another OS and tries to acquire the same lease
with a different client-id.

-- 
Thamer Al-Harbash            http://www.whitefang.com/
          team dresch made me do it

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