[dhcwg] dhcpv6 source address selection policy option

(Tomohiro -INSTALLER- Fujisaki/藤崎 智宏 ) <fujisaki@syce.net> Wed, 10 November 2004 16:32 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 LAA27864; Wed, 10 Nov 2004 11:32:01 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRvEe-0001t7-6P; Wed, 10 Nov 2004 11:22:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRv9y-0000m9-Ao for dhcwg@megatron.ietf.org; Wed, 10 Nov 2004 11:17:26 -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 LAA26136 for <dhcwg@ietf.org>; Wed, 10 Nov 2004 11:17:23 -0500 (EST)
Received: from mail.syce.net ([192.16.178.14]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRvAw-0006IV-Rh for dhcwg@ietf.org; Wed, 10 Nov 2004 11:18:27 -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 iAAGH8fm096628; Thu, 11 Nov 2004 01:17:09 +0900 (JST) (envelope-from fujisaki@syce.net)
Date: Thu, 11 Nov 2004 01:17:10 +0900
Message-Id: <20041111.011710.350532059.fujisaki@syce.net>
To: dhcwg@ietf.org
From: fujisaki@syce.net
In-Reply-To: <901AB2B0-3325-11D9-AA52-000A95D6A618@nominum.com>
References: <002d01c4c6b0$e63ae660$be878182@amer.cisco.com> <901AB2B0-3325-11D9-AA52-000A95D6A618@nominum.com>
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: 9466e0365fc95844abaf7c3f15a05c7d
Content-Transfer-Encoding: 7bit
Subject: [dhcwg] dhcpv6 source address selection policy option
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>

We got some comments and questions at the meeting. (thanks a lot!)

One big question was why we use DHCP where dynamic changes could be
occurred.

Our proposal in this draft is to distribute the source address
selection policy mainly at the node set up stage, and not changing the
policy dynamically.  And as Ted kindly pointed out in the meeting, we
assume the policy is static and the lifetime of the distributed policy
is bound to the address assigned to the node.

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.

So, we do not assume the dynamic changes such as routing affect to the
policy directly.

I hope this could be an answer to the question John asked.

Yours sincerely,
--
Tomohiro Fujisaki, Nippon Telegraph and Telephone Corporation

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg