RE: [dhcwg] WG last call on draft-ietf-dhc-dhcpv6-stateless-00.tx t
"Bernie Volz (EUD)" <Bernie.Volz@am1.ericsson.se> Tue, 15 April 2003 12:32 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 IAA25636 for <dhcwg-archive@odin.ietf.org>; Tue, 15 Apr 2003 08:32:49 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h3FCevx00361 for dhcwg-archive@odin.ietf.org; Tue, 15 Apr 2003 08:40:57 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3FCev800358 for <dhcwg-web-archive@optimus.ietf.org>; Tue, 15 Apr 2003 08:40:57 -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 IAA25622 for <dhcwg-web-archive@ietf.org>; Tue, 15 Apr 2003 08:32:17 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.12) id 195PeD-0002Lh-00 for dhcwg-web-archive@ietf.org; Tue, 15 Apr 2003 08:34:49 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 195PeD-0002Le-00 for dhcwg-web-archive@ietf.org; Tue, 15 Apr 2003 08:34:49 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3FCWG831544; Tue, 15 Apr 2003 08:32:16 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3FCTW831442 for <dhcwg@optimus.ietf.org>; Tue, 15 Apr 2003 08:29:32 -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 IAA25200 for <dhcwg@ietf.org>; Tue, 15 Apr 2003 08:20:54 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.12) id 195PTC-0002Hw-00 for dhcwg@ietf.org; Tue, 15 Apr 2003 08:23:26 -0400
Received: from imr2.ericy.com ([198.24.6.3]) by ietf-mx with esmtp (Exim 4.12) id 195PTB-0002Hp-00 for dhcwg@ietf.org; Tue, 15 Apr 2003 08:23:25 -0400
Received: from mr5.exu.ericsson.se (mr5att.ericy.com [138.85.224.141]) by imr2.ericy.com (8.12.9/8.12.9) with ESMTP id h3FCMotP003143; Tue, 15 Apr 2003 07:22:50 -0500 (CDT)
Received: from eamrcnt761.exu.ericsson.se (eamrcnt761.exu.ericsson.se [138.85.133.39]) by mr5.exu.ericsson.se (8.12.9/8.12.9) with ESMTP id h3FCMoKG026532; Tue, 15 Apr 2003 07:22:50 -0500 (CDT)
Received: by eamrcnt761.exu.ericsson.se with Internet Mail Service (5.5.2656.59) id <W7YBJF14>; Tue, 15 Apr 2003 07:22:51 -0500
Message-ID: <A1DDC8E21094D511821C00805F6F706B067F5C85@eamrcnt715.exu.ericsson.se>
From: "Bernie Volz (EUD)" <Bernie.Volz@am1.ericsson.se>
To: 'SHIRASAKI Yasuhiro' <yasuhiro@nttv6.jp>, jinmei@isl.rdc.toshiba.co.jp
Cc: rdroms@cisco.com, dhcwg@ietf.org
Subject: RE: [dhcwg] WG last call on draft-ietf-dhc-dhcpv6-stateless-00.tx t
Date: Tue, 15 Apr 2003 07:20:53 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C30349.758E1E90"
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>
There are three mechanisms available: a. Whenever the client would normally determine that its stateless addresses are suspect, after confirming them or obtaining new addresses, it can use Information-Request to obtain new parameters. Note that a client may also use triggers such as existing address lifetimes expiring (if a prefix is has expired, it likely means some changes to the networks configuration and hence doing an Information-Request to obtain updated parameters may be in order). b. The server can send a Reconfigure provided the client has communicated it is able/willing to support this in the Information-Request. c. The client is free to do Information-Requests at times of its choosing (there is no prohibition against doing this). Of course, the client should not do this too frequently. If someone feels these mechanisms are insufficient, they could always write a draft that specifies an "Information Lifetime" or "Information Renewal Time" at which point the client could refresh the information. This option could specify T1 and T2 times - at T1 the client renews by including the server identifier option of the server that gave it the configuration parameters, at T2 it removes this option and any server may respond to the Information-Request. - Bernie -----Original Message----- From: SHIRASAKI Yasuhiro [mailto:yasuhiro@nttv6.jp] Sent: Tuesday, April 15, 2003 1:53 AM To: jinmei@isl.rdc.toshiba.co.jp Cc: rdroms@cisco.com; dhcwg@ietf.org Subject: Re: [dhcwg] WG last call on draft-ietf-dhc-dhcpv6-stateless-00.txt > 2. how to invalidate stale configuration parameters > > The stateless usage does not have the notion of Renew or Rebind. So, > how the client can purge configuration parameters (e.g. DNS addresses) > when they become invalidated? I guess we need a some kind of > "timeout" parameter, which suggests to the client that it refresh the > parameters in a certain period. or the server "advertises" when the parameters change? -- SHIRASAKI Yasuhiro @ NTT Communications _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- RE: [dhcwg] WG last call on draft-ietf-dhc-dhcpv6… Bernie Volz (EUD)