IETF Logo Mail Archive

Re: [dhcwg] Revised Drafts on Source Address Selection Posted

Stig Venaas <Stig.Venaas@uninett.no> Thu, 10 March 2005 13:56 UTC

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 IAA16250 for <dhcwg-web-archive@ietf.org>; Thu, 10 Mar 2005 08:56:00 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D9OBk-00014K-Hv for dhcwg-web-archive@ietf.org; Thu, 10 Mar 2005 08:58:56 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D9O69-0007lU-VV; Thu, 10 Mar 2005 08:53:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D9O60-0007lI-1V for dhcwg@megatron.ietf.org; Thu, 10 Mar 2005 08:53:03 -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 IAA15941 for <dhcwg@ietf.org>; Thu, 10 Mar 2005 08:52:57 -0500 (EST)
Received: from tyholt.uninett.no ([158.38.60.10]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D9O8m-0000rz-Hu for dhcwg@ietf.org; Thu, 10 Mar 2005 08:55:54 -0500
Received: from storhaugen.uninett.no (storhaugen.uninett.no [IPv6:2001:700:e000:0:290:27ff:fe22:7186]) by tyholt.uninett.no (8.12.10/8.12.10) with ESMTP id j2ADqs3s022152; Thu, 10 Mar 2005 14:52:54 +0100
Received: from storhaugen.uninett.no (localhost.localdomain [127.0.0.1]) by storhaugen.uninett.no (8.12.11/8.12.9) with ESMTP id j2ADqr2V025911; Thu, 10 Mar 2005 14:52:53 +0100
Received: (from venaas@localhost) by storhaugen.uninett.no (8.12.11/8.12.11/Submit) id j2ADqnOI025910; Thu, 10 Mar 2005 14:52:49 +0100
X-Authentication-Warning: storhaugen.uninett.no: venaas set sender to Stig.Venaas@uninett.no using -f
Date: Thu, 10 Mar 2005 14:52:49 +0100
From: Stig Venaas <Stig.Venaas@uninett.no>
To: "JINMEI Tatuya / ?$B?@L@C#:H" <jinmei@isl.rdc.toshiba.co.jp>
Subject: Re: [dhcwg] Revised Drafts on Source Address Selection Posted
Message-ID: <20050310135249.GA25724@storhaugen.uninett.no>
References: <20050309164020.GL18857@storhaugen.uninett.no> <20050310.033634.137809416.fujisaki@syce.net> <20050309185017.GA20106@storhaugen.uninett.no> <20050310.065216.846934042.fujisaki@syce.net> <y7vwtsgz7kp.wl@ocean.jinmei.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <y7vwtsgz7kp.wl@ocean.jinmei.org>
User-Agent: Mutt/1.4.1i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab

On Thu, Mar 10, 2005 at 09:08:06AM +0900, JINMEI Tatuya / ?$B?@L@C#:H wrote:
[...]
> > As you say, there may be some cases to use zone index in scoped multicast
> > environment. The 'zone index' should be included to deliver RFC 3484 policy
> > table. I'll add this parameter to the option.
> 
> I don't think this works, since specific values of scope zone indices
> are only meaningful within a single node.

I mentioned it because it's in 3484, but you're right, this is
problematic. There might be cases where the DHCP administrator knows
which clients are on the network and wants specific interfaces to be
used though. Whether it should be there or not would be something the
ipv6 wg could help us with perhaps.

Stig


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

v2.23.0 | Report a Bug | By Email