[dhcwg] Re: mboned: draft-jdurand-assign-addr-ipv6-multicast-dhcpv6-00 comments

Pekka Savola <pekkas@netcore.fi> Sun, 01 August 2004 22:12 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 SAA27681; Sun, 1 Aug 2004 18:12:58 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BrOUB-0000tI-SL; Sun, 01 Aug 2004 18:07:19 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BrOOj-0002eg-Np for dhcwg@megatron.ietf.org; Sun, 01 Aug 2004 18:01:42 -0400
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 SAA26455 for <dhcwg@ietf.org>; Sun, 1 Aug 2004 18:01:38 -0400 (EDT)
Received: from netcore.fi ([193.94.160.1]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BrORR-0001YX-Tw for dhcwg@ietf.org; Sun, 01 Aug 2004 18:04:31 -0400
Received: from localhost (pekkas@localhost) by netcore.fi (8.11.6/8.11.6) with ESMTP id i71M17V06867; Mon, 2 Aug 2004 01:01:07 +0300
Date: Mon, 2 Aug 2004 01:01:06 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Stig Venaas <Stig.Venaas@uninett.no>
In-Reply-To: <20040801174409.GB14995@sverresborg.uninett.no>
Message-ID: <Pine.LNX.4.44.0408020051210.6499-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: dhcwg@ietf.org, mboned@lists.uoregon.edu
Subject: [dhcwg] Re: mboned: draft-jdurand-assign-addr-ipv6-multicast-dhcpv6-00 comments
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

On Sun, 1 Aug 2004, Stig Venaas wrote:
[...]
> I see some possible issues. There might be a need for giving hosts
> different prefixes for different scopes (you could imagine having
> one prefix where simply the scope bits are set to whatever scope
> is needed). I think there are cases where you might use say
> Embedded-RP internally (with small scope) and prefix-based addressing
> externally (with larger scope) or vice versa. Or where you may want
> different RPs for different scopes.

Well, one obvious way to achieve all of this is to add a Multicast
Prefix Information option (a tailed down version of PI option), to
RFC2461/RFC2462 Route Advertisements, and specification of multicast
DAD (possibly with a flag in the MPI whether it's needed or not).

With that, multiple prefixes could be advertised, but typically one
would be enough.

(The "good news" here is that a good implementation would not need to 
require the router admin to specify the prefix to be advertised on all 
the links, but it could be calculated & advertised automatically as 
well.)

Additionally, individual addresses could also be dealt with DHCPv6 or
something, but I personally don't see that as equally attractive.. but
in cases where this is attractive IMHO manual addressing, as it's done
today, is probably typically more lucrative..

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings



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