[dhcwg] Update of parameters supplied through stateless DHCPv6
Ralph Droms <rdroms@cisco.com> Thu, 01 May 2003 14:50 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 KAA14979 for <dhcwg-archive@odin.ietf.org>; Thu, 1 May 2003 10:50:38 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h41Eugd16098 for dhcwg-archive@odin.ietf.org; Thu, 1 May 2003 10:56:42 -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 h41Eug816095 for <dhcwg-web-archive@optimus.ietf.org>; Thu, 1 May 2003 10:56:42 -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 KAA14927 for <dhcwg-web-archive@ietf.org>; Thu, 1 May 2003 10:49:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19BFPs-0002Fs-00 for dhcwg-web-archive@ietf.org; Thu, 01 May 2003 10:52:08 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19BFPr-0002Fp-00 for dhcwg-web-archive@ietf.org; Thu, 01 May 2003 10:52:07 -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 h41Epd815415; Thu, 1 May 2003 10:51:39 -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 h41EfE812616 for <dhcwg@optimus.ietf.org>; Thu, 1 May 2003 10:41:14 -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 KAA13916 for <dhcwg@ietf.org>; Thu, 1 May 2003 10:34:40 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19BFB4-00020j-00 for dhcwg@ietf.org; Thu, 01 May 2003 10:36:50 -0400
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by ietf-mx with esmtp (Exim 4.12) id 19BFAy-00020P-00 for dhcwg@ietf.org; Thu, 01 May 2003 10:36:44 -0400
Received: from funnel.cisco.com (funnel.cisco.com [161.44.168.79]) by rtp-core-1.cisco.com (8.12.6/8.12.6) with ESMTP id h41EaiWS018374 for <dhcwg@ietf.org>; Thu, 1 May 2003 10:36:44 -0400 (EDT)
Received: from rdroms-w2k.cisco.com (rtp-vpn2-797.cisco.com [10.82.243.29]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id KAA01102 for <dhcwg@ietf.org>; Thu, 1 May 2003 10:36:43 -0400 (EDT)
Message-Id: <4.3.2.7.2.20030501095224.00b99538@funnel.cisco.com>
X-Sender: rdroms@funnel.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 01 May 2003 09:55:35 -0400
To: dhcwg@ietf.org
From: Ralph Droms <rdroms@cisco.com>
In-Reply-To: <y7vptnpktc9.wl@ocean.jinmei.org>
References: <4.3.2.7.2.20030411113053.042c1cb0@funnel.cisco.com> <4.3.2.7.2.20030411113053.042c1cb0@funnel.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Subject: [dhcwg] Update of parameters supplied through stateless DHCPv6
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>
At 12:10 AM 4/15/2003 +0900, JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= wrote: >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. Bernie responded to this issue: >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. - Ralph _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] WG last call on draft-ietf-dhc-dhcpv6-sta… Ralph Droms
- Re: [dhcwg] WG last call on draft-ietf-dhc-dhcpv6… JINMEI Tatuya / 神明達哉
- Re: [dhcwg] WG last call on draft-ietf-dhc-dhcpv6… SHIRASAKI Yasuhiro
- RE: [dhcwg] WG last call on draft-ietf-dhc-dhcpv6… juha.wiljakka
- RE: [dhcwg] WG last call on draft-ietf-dhc-dhcpv6… Bound, Jim
- [dhcwg] Address selection for Information-request… Ralph Droms
- [dhcwg] When to invoke the stateless DHCPv6 messa… Ralph Droms
- [dhcwg] Update of parameters supplied through sta… Ralph Droms
- [dhcwg] Stateless DHCPv6 == "Other stateful confi… Ralph Droms
- Re: [dhcwg] Address selection for Information-req… Robert Elz