[dhcwg] renew/rebind can mean reconfigure?
Thamer Al-Harbash <tmh@whitefang.com> Fri, 11 July 2003 11:25 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 HAA25157; Fri, 11 Jul 2003 07:25:32 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aw1N-00006q-Oa; Fri, 11 Jul 2003 07:25:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19anWH-00086z-TQ for dhcwg@optimus.ietf.org; Thu, 10 Jul 2003 22:20:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA00637 for <dhcwg@ietf.org>; Thu, 10 Jul 2003 22:20:16 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19anWE-0001PO-00 for dhcwg@ietf.org; Thu, 10 Jul 2003 22:20:18 -0400
Received: from helena.whitefang.com ([216.254.175.50] ident=0xdeadbeef) by ietf-mx with smtp (Exim 4.12) id 19anWD-0001PL-00 for dhcwg@ietf.org; Thu, 10 Jul 2003 22:20:17 -0400
Received: (qmail 11166 invoked from network); 11 Jul 2003 02:20:33 -0000
Received: from helena.whitefang.com (216.254.175.50) by 0 with SMTP; 11 Jul 2003 02:20:33 -0000
Date: Thu, 10 Jul 2003 22:20:33 -0400
From: Thamer Al-Harbash <tmh@whitefang.com>
X-X-Sender: shadows@helena.whitefang.com
To: dhcwg@ietf.org
Message-ID: <Pine.BSF.4.51.0307102217530.9170@helena.whitefang.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Subject: [dhcwg] renew/rebind can mean reconfigure?
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>
RFC2131 mentions that the client should not use its old address if a new one is assigned via a rebind or renew. It also mentions that the user should be notified of the problem. There's no mention whether or not the client should configure a new address or any of the new leases. Most clients I have looked at will attempt to reconfigure values which have changed, but I cannot find a single piece of literature from the DHC IETF group that verifies that this is the correct behaviour. What is the correct thing to do as the client if a rebind/renew causes the server to change the client's IP address or any of the configuration values in the lease? -- Thamer Al-Harbash _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] renew/rebind can mean reconfigure? Thamer Al-Harbash
- Re: [dhcwg] renew/rebind can mean reconfigure? Thamer Al-Harbash
- Re: [dhcwg] renew/rebind can mean reconfigure? Ted Lemon