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

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

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EUVhg-0008Eh-T8; Tue, 25 Oct 2005 16:47:28 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EUVha-0008Be-BU for mip6@megatron.ietf.org; Tue, 25 Oct 2005 16:47:27 -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 QAA08059 for <mip6@ietf.org>; Tue, 25 Oct 2005 16:47:06 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUVuZ-0007uo-Es for mip6@ietf.org; Tue, 25 Oct 2005 17:00:49 -0400
Received: from il06exr03.mot.com (il06exr03.mot.com [129.188.137.133]) by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id j9PKx5kO001961; Tue, 25 Oct 2005 13:59:05 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8]) by il06exr03.mot.com (8.13.1/8.13.0) with ESMTP id j9PKvCqp029918; Tue, 25 Oct 2005 15:57:13 -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 B5369865980; Tue, 25 Oct 2005 22:47:08 +0200 (CEST)
Message-ID: <435E99CC.3090309@motorola.com>
Date: Tue, 25 Oct 2005 22:47:08 +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: <200510251938.j9PJcspQ008946@givry.rennes.enst-bretagne.fr>
In-Reply-To: <200510251938.j9PJcspQ008946@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: cab78e1e39c4b328567edb48482b6a69
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 Dupont wrote:
>  In your previous mail you wrote:
> 
>    >    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?
>    
> => I mean Mobile Prefix for MP.
> 
>    "MP" could be misinterpreted as "Mobile Prefix" which isn't.
>    
> => it is.

Well, the Prefix is the prefix of a fixed home link, advertised in fixed
RAs sent by its routers.  A "Mobile Prefix" would be more like the
prefix of the Mobile Network Prefix which moves together with the moving
network, I think.

But ok, it's also like a "Mobile Network" moves or is fixed depending
who one talks to.

>    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.
>    
> => but in fact the prefix length is 64 bits so this is not enough
> to explain the necessity of MPD.

Well, ok.  When plens are shorter than 64bits please pad with 0s between
prefix and IID, and don't use these zeros as network identifier.

>    HA-Switch and DHAAD+MPD could also be used when the home link is
>    re-numbered.
> 
> => this is a very unlikely event.

Well, ok, a discussion could be held about what are the minimal parts of
MIP6 which are really necessary and in what contexts.

Alex

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