[dhcwg] Temporary addresses
"Vijayabhaskar A K" <vijayak@india.hp.com> Sat, 15 June 2002 14:05 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 KAA08179 for <dhcwg-archive@odin.ietf.org>; Sat, 15 Jun 2002 10:05:31 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id KAA19812 for dhcwg-archive@odin.ietf.org; Sat, 15 Jun 2002 10:06:07 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA19755; Sat, 15 Jun 2002 10:04:30 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA19732 for <dhcwg@optimus.ietf.org>; Sat, 15 Jun 2002 10:04:29 -0400 (EDT)
Received: from atlrel7.hp.com (atlrel7.hp.com [156.153.255.213]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08147 for <dhcwg@ietf.org>; Sat, 15 Jun 2002 10:03:52 -0400 (EDT)
Received: from dce.india.hp.com (dce.india.hp.com [15.10.45.122]) by atlrel7.hp.com (Postfix) with ESMTP id 5C9168055A2 for <dhcwg@ietf.org>; Sat, 15 Jun 2002 10:03:57 -0400 (EDT)
Received: from nt4147 (nt4147.india.hp.com [15.10.41.47]) by dce.india.hp.com with SMTP (8.8.6 (PHNE_17190)/8.8.6 SMKit7.02) id TAA22089 for <dhcwg@ietf.org>; Sat, 15 Jun 2002 19:39:15 +0530 (IST)
Reply-To: vijayak@india.hp.com
From: Vijayabhaskar A K <vijayak@india.hp.com>
To: dhcwg@ietf.org
Date: Sat, 15 Jun 2002 19:35:34 +0530
Message-ID: <000701c21475$b8875040$2f290a0f@india.hp.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Importance: Normal
Content-Transfer-Encoding: 7bit
Subject: [dhcwg] Temporary addresses
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
We dont have T1 and T2 values for IA having temporary addreses but the draft says that the temporary addresses can be renewed. So, if the client wishes to renew the adddresses, when should the client renew the addresses? Does it mean that the application has to trigger the renew in the case, if it need to use the address for some more time? RFC 3041 says the mechanism of generating random Interface IDs, for subsequent addresses for the same interface of the node. Does the DHCP server need to implement this mechanism for allocating temporary addresses to the client? Probabably, we can add some text to state that once a temporary address is released or lifetime expires, the server should forget the bindings, unlike the normal addresses. This will be helpful in allocating different addresses for the subsequent request from the same node. Vijayabhaskar A K Hewlett Packard ESDI 91-80-2051424,9624-371137 _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] Temporary addresses Vijayabhaskar A K
- RE: [dhcwg] Temporary addresses Bernie Volz (EUD)