Re: Interaction between ARs in lmm domain (was Re: [netlmm] Re: [Mipshop] comments on Mobile IPv6 Fast Handovers over IEEE 802.16eNetworks draft)

Rajeev Koodli <rajeev@iprg.nokia.com> Fri, 15 July 2005 22:35 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DtYmY-0005wG-7N; Fri, 15 Jul 2005 18:35:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DtYmV-0005wB-75 for mipshop@megatron.ietf.org; Fri, 15 Jul 2005 18:35:43 -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 SAA01768 for <mipshop@ietf.org>; Fri, 15 Jul 2005 18:35:39 -0400 (EDT)
Received: from darkstar.iprg.nokia.com ([205.226.5.69]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DtZFP-0000w1-12 for mipshop@ietf.org; Fri, 15 Jul 2005 19:05:35 -0400
Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j6FM3eo10204; Fri, 15 Jul 2005 15:03:40 -0700
X-mProtect: <200507152203> Nokia Silicon Valley Messaging Protection
Received: from mvdhcp14166.americas.nokia.com (172.18.141.66, claiming to be "[127.0.0.1]") by darkstar.iprg.nokia.com smtpdxhHcRj; Fri, 15 Jul 2005 15:03:39 PDT
Message-ID: <42D83A1C.2060803@iprg.nokia.com>
Date: Fri, 15 Jul 2005 15:35:08 -0700
From: Rajeev Koodli <rajeev@iprg.nokia.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: James Kempf <Kempf@docomolabs-usa.com>
Subject: Re: Interaction between ARs in lmm domain (was Re: [netlmm] Re: [Mipshop] comments on Mobile IPv6 Fast Handovers over IEEE 802.16eNetworks draft)
References: <DA62A6E0CDD1B34A84557FF1AC850C5769E638@EXC01B.cselt.it> <42D7F3BE.1050809@iprg.nokia.com> <116701c58966$ac3919e0$016115ac@dcml.docomolabsusa.com> <42D7FC9D.5000307@iprg.nokia.com> <118901c5896b$e3b1e640$016115ac@dcml.docomolabsusa.com> <42D82
In-Reply-To: <127901c58985$b3313790$016115ac@dcml.docomolabsusa.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Content-Transfer-Encoding: 7bit
Cc: Gerardo Giaretta <Gerardo.Giaretta@TILAB.COM>, mipshop@ietf.org, Heejin Jang <heejin.jang@samsung.com>, soohong.park@samsung.com, Phil.Roberts@motorola.com
X-BeenThere: mipshop@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mipshop.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mipshop>, <mailto:mipshop-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mipshop@ietf.org>
List-Help: <mailto:mipshop-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mipshop>, <mailto:mipshop-request@ietf.org?subject=subscribe>
Sender: mipshop-bounces@ietf.org
Errors-To: mipshop-bounces@ietf.org


James Kempf wrote:

> Even if DNA isn't used, the MN can use oDAD for the src addr and the pAR for
> the dest addr. In this case, the MN would have had to configure the new CoA
> using prehandover prefix information or prefix information derived from the
> specialized link support.
>

I think we are digressing from the main thread..

FYI: there is a draft specifying FMIP and DNA interaction that should
appear soon.

draft-koodli-dna-fmip-00.txt

A protocol (FMIP) should be able to work on its own, while also being 
able to work well when some other protocol is available.

The FBU can be constructed as above. But we still need a way to inform
NAR to flush the buffer.

> So, I wonder, is FNA really needed anymore for FMIP? Seems like it could
> really simplify the protocol to have it concentrate on FBU.

See above. In cases where we can assume that an announcement that makes
the NAR's ND state REACHABLE (for NCoA) is available, we can make do 
without it.


-Rajeev


> 
>             jak
> 
> 


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