Re: [dhcwg] dhcpv6 source address selection policy option
(Tomohiro -INSTALLER- Fujisaki/藤崎 智宏 ) <fujisaki@syce.net> Thu, 11 November 2004 01:53 UTC
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA00499; Wed, 10 Nov 2004 20:53:10 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CS45r-0004R3-5a; Wed, 10 Nov 2004 20:49:47 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CS42h-0003m0-4X for dhcwg@megatron.ietf.org; Wed, 10 Nov 2004 20:46:31 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA29828 for <dhcwg@ietf.org>; Wed, 10 Nov 2004 20:46:28 -0500 (EST)
Received: from mail.syce.net ([192.16.178.14]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CS43j-00050W-V0 for dhcwg@ietf.org; Wed, 10 Nov 2004 20:47:36 -0500
Received: from localhost (mail.syce.net [IPv6:2001:218:4fd::25]) by mail.syce.net (8.12.11/8.12.11) with ESMTP/inet6 id iAB1kH76040198; Thu, 11 Nov 2004 10:46:17 +0900 (JST) (envelope-from fujisaki@syce.net)
Date: Thu, 11 Nov 2004 10:46:28 +0900
Message-Id: <20041111.104628.846933399.fujisaki@syce.net>
To: matthew.ford@bt.com
Subject: Re: [dhcwg] dhcpv6 source address selection policy option
From: fujisaki@syce.net
In-Reply-To: <0AAF93247C75E3408638B965DEE11A700B164379@i2km41-ukdy.domain1.systemhost.net>
References: <0AAF93247C75E3408638B965DEE11A700B164379@i2km41-ukdy.domain1.systemhost.net>
X-Mailer: Mew version 3.3 on XEmacs 21.4.14 (Reasonable Discussion)
Mime-Version: 1.0
Content-Type: Text/Plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Content-Transfer-Encoding: 7bit
Cc: dhcwg@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
Content-Transfer-Encoding: 7bit
| > Source Address Selection Policy option for DHCPv6 | > <draft-hirotaka-dhc-source-address-selection-opt> | | > When one upstream link goes down, dynamic changes to the user network | > will occur. The changes could be revoking address prefix assigned from | > the failed link, and at that case, the policy bound to that assigned | > prefix would be also revoked. This change is caused by the revocation | > of that address prefix, and not caused by other trigger. | | I wasn't at the dhc meeting so apologies in advance if this was already | discussed there. But doesn't the above statement regarding the need to | revoke address assignments based upon dynamic changes in the upstream | connectivity suggest that RA is more appropriate than DHCP as a | mechanism substrate here? I wrote an example behavior, and did not say the preference of RA nor DHCP. I'm sorry for ambiguous statement. -- Tomohiro Fujisaki, Nippon Telegraph and Telephone Corporation _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- RE: [dhcwg] dhcpv6 source address selection polic… matthew.ford
- Re: [dhcwg] dhcpv6 source address selection polic… (Tomohiro -INSTALLER- Fujisaki/藤崎 智宏 )