RE: [dhcwg] dhcpv6 source address selection policy option
matthew.ford@bt.com Wed, 10 November 2004 22:17 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 RAA11142; Wed, 10 Nov 2004 17:17:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CS0dI-0007Rs-JB; Wed, 10 Nov 2004 17:08:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CS0Qv-00044q-3F for dhcwg@megatron.ietf.org; Wed, 10 Nov 2004 16:55:19 -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 QAA09034 for <dhcwg@ietf.org>; Wed, 10 Nov 2004 16:55:14 -0500 (EST)
From: matthew.ford@bt.com
Received: from smtp2.smtp.bt.com ([217.32.164.150]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CS0Rw-00006o-8w for dhcwg@ietf.org; Wed, 10 Nov 2004 16:56:21 -0500
Received: from i2km96-ukbr.domain1.systemhost.net ([193.113.197.84]) by smtp2.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.80); Wed, 10 Nov 2004 21:55:50 +0000
Received: from i2km41-ukdy.domain1.systemhost.net ([193.113.30.29]) by i2km96-ukbr.domain1.systemhost.net with Microsoft SMTPSVC(5.0.2195.6713); Wed, 10 Nov 2004 21:55:50 +0000
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [dhcwg] dhcpv6 source address selection policy option
Date: Wed, 10 Nov 2004 21:55:49 -0000
Message-ID: <0AAF93247C75E3408638B965DEE11A700B164379@i2km41-ukdy.domain1.systemhost.net>
Thread-Topic: [dhcwg] dhcpv6 source address selection policy option
Thread-Index: AcTHQuw34cAPu7YOSHWOGSZ9VPad0wAK9f9w
To: fujisaki@syce.net, dhcwg@ietf.org
X-OriginalArrivalTime: 10 Nov 2004 21:55:50.0288 (UTC) FILETIME=[0AB16900:01C4C770]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Content-Transfer-Encoding: quoted-printable
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: quoted-printable
On 10 November 2004 11:17, dhcwg-bounces@ietf.org (mailto:dhcwg-bounces@ietf.org) wrote: > 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? -- Mat _______________________________________________ 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/藤崎 智宏 )