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

Stig Venaas <Stig.Venaas@uninett.no> Mon, 02 August 2004 04:53 UTC

Received: from megatron.ietf.org (megatron.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA29438; Mon, 2 Aug 2004 00:53:54 -0400 (EDT)
Received: from localhost.localdomain ([] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BrUnQ-0007mc-9q; Mon, 02 Aug 2004 00:51:36 -0400
Received: from odin.ietf.org ([] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BrUkw-0006K1-GP for dhcwg@megatron.ietf.org; Mon, 02 Aug 2004 00:49:02 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA29295 for <dhcwg@ietf.org>; Mon, 2 Aug 2004 00:48:59 -0400 (EDT)
Received: from tyholt.uninett.no ([]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BrUni-0007H4-CP for dhcwg@ietf.org; Mon, 02 Aug 2004 00:51:56 -0400
Received: from sverresborg.uninett.no (sverresborg.uninett.no [IPv6:2001:700:e000:0:204:75ff:fee4:423b]) by tyholt.uninett.no (8.12.10/8.12.10) with ESMTP id i724mQV0019796; Mon, 2 Aug 2004 06:48:26 +0200
Received: (from venaas@localhost) by sverresborg.uninett.no (8.12.8/8.12.8/Submit) id i724mPGu016973; Mon, 2 Aug 2004 06:48:25 +0200
X-Authentication-Warning: sverresborg.uninett.no: venaas set sender to Stig.Venaas@uninett.no using -f
Date: Mon, 02 Aug 2004 06:48:25 +0200
From: Stig Venaas <Stig.Venaas@uninett.no>
To: Pekka Savola <pekkas@netcore.fi>
Message-ID: <20040802044825.GA16941@sverresborg.uninett.no>
References: <20040801174409.GB14995@sverresborg.uninett.no> <Pine.LNX.4.44.0408020051210.6499-100000@netcore.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0408020051210.6499-100000@netcore.fi>
User-Agent: Mutt/1.4.1i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
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 Mon, Aug 02, 2004 at 01:01:06AM +0300, Pekka Savola wrote:
> 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.)

The prefixes to use could also be announced by DHCP. You could easily
use stateless DHCP. In addition to this some form of DAD would be good.
I don't care that much how the client picks the last 32 bits, it could
be random, from interface id somehow, or specified by the user. The
main thing is making sure it's unique.

So, I think there are basically two issues that can be solved
independently. One is prefix to use, the other is link uniqueness.

The former might be done with RAs or stateless DHCP. The second
should probably be done using some link-local multicast ICMP, but I
need to think more about that. One issue is that one needs to allow
multiple sources for a group in some cases. So I think DAD should
just be offered as a service, whether an application should use the
group in case of duplicates should be up to the application.


dhcwg mailing list