Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt

Alexandru Petrescu <alexandru.petrescu@motorola.com> Tue, 25 October 2005 18:51 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EUTtP-0000Xm-4v; Tue, 25 Oct 2005 14:51:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EUTtN-0000Vj-MC for mip6@megatron.ietf.org; Tue, 25 Oct 2005 14:51:25 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12215 for <mip6@ietf.org>; Tue, 25 Oct 2005 14:51:11 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUU6M-000606-7x for mip6@ietf.org; Tue, 25 Oct 2005 15:04:52 -0400
Received: from il06exr01.mot.com (il06exr01.mot.com [129.188.137.131]) by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id j9PJ3C4k012988; Tue, 25 Oct 2005 12:03:12 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8]) by il06exr01.mot.com (8.13.1/8.13.0) with ESMTP id j9PJ1Bgb026492; Tue, 25 Oct 2005 14:01:12 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117]) by zfr01srv02.crm.mot.com (Postfix) with ESMTP id 9601E865980; Tue, 25 Oct 2005 20:51:16 +0200 (CEST)
Message-ID: <435E7EA4.2070202@motorola.com>
Date: Tue, 25 Oct 2005 20:51:16 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
References: <200510251824.j9PIO1CB008312@givry.rennes.enst-bretagne.fr>
In-Reply-To: <200510251824.j9PIO1CB008312@givry.rennes.enst-bretagne.fr>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Content-Transfer-Encoding: 7bit
Cc: James Kempf <Kempf@docomolabs-usa.com>, mip6@ietf.org, Kilian Weniger <Kilian.Weniger@eu.panasonic.com>, Alexandru Petrescu <alexandru.petrescu@motorola.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>, <mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>, <mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Francis, please allow me slight remarks, don't take as corrections.

Francis Dupont wrote:

>  In your previous mail you wrote:
> 
>    > => we agree: current DHAAD design is not stupid, it has only two real
>    > problems:
>    >  - the DHAAD idea itself is in danger because HA assignment is better
>    
>    By "HA assignment" you mean HA Switch message and draft?
> 
> => no, I mean a HA assignment mechanism in general, including
> (i.e., mainly :-) any still to be invented mechanism.
> HA switch message is fine but is clearly *re*-assignment.
> 
>    If yes, that
>    draft alone does not help for bootstrapping IMHO.  If DHAAD can be made
>    to work with non-anycast addresses then DHAAD+MPD is a good idea to do
>    bootstrapping simple (MPD is Mobile Prefix Discovery).
>    
> => I don't understand why MPD is for when you have HA discovery/assignment
> (the mobile prefix is simply the prefix of the HA address)... I should
> have missed something, for instance there is more than one MP?

"MP" could be misinterpreted as "Mobile Prefix" which isn't.

MPD is more like: Mobile       Prefix Discovery, a prefix discovery
performed by a mobile.

There's only one MPD.

DHAAD doesn't provide a prefix length field in DHAAD Reply, so the MN
can't know it.  MPD is the equivalent of local RS/RA for a MN that is
away from home.

For bootstrapping, MN could do DHAAD to get the HA's full address and
then interrogate that HA with MPD Sol and get Response, and then call
the stateless address autoconfiguration functions easily.

HA-Switch and DHAAD+MPD could also be used when the home link is
re-numbered.

>    >  - the current mechanism has some operational issues, mainly its lack
>    >    of reasonably easy security and the spurious but common ICMP filtering.
>    > My draft is about the second but the first is more critical and drastic...
>    
>    I don't see anything critical or drastic in HA assignment being proposed
>    as better than DHAAD.
> 
> => the question is drastic, i.e., if the answer is yes all discussions about
> the best DHAAD mechanism are lost bits...

I agree.

[... snip because I don't know]

Alex


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