RE: [Mip4] Request to consider FMIPv4 as a working group document

Kent Leung <kleung@cisco.com> Fri, 18 March 2005 20:34 UTC

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 PAA23021 for <mip4-web-archive@ietf.org>; Fri, 18 Mar 2005 15:34:40 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DCOFe-00066w-Jl for mip4-web-archive@ietf.org; Fri, 18 Mar 2005 15:39:22 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DCO7K-00006U-0u; Fri, 18 Mar 2005 15:30:46 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DCO7F-00005z-SE for mip4@megatron.ietf.org; Fri, 18 Mar 2005 15:30:42 -0500
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 PAA22542 for <mip4@ietf.org>; Fri, 18 Mar 2005 15:30:39 -0500 (EST)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DCOBk-0005xL-A1 for mip4@ietf.org; Fri, 18 Mar 2005 15:35:21 -0500
Received: from sj-core-2.cisco.com (171.71.177.254) by sj-iport-3.cisco.com with ESMTP; 18 Mar 2005 12:29:25 -0800
X-IronPort-AV: i="3.91,102,1110182400"; d="scan'208"; a="237443662:sNHT583229852"
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j2IKTDgE028914; Fri, 18 Mar 2005 12:29:14 -0800 (PST)
Received: from kleung-w2k01.cisco.com (sjc-vpn4-961.cisco.com [10.21.83.192]) by mira-sjc5-b.cisco.com (MOS 3.4.5-GR) with ESMTP id BDB08411; Fri, 18 Mar 2005 12:29:12 -0800 (PST)
Message-Id: <4.3.2.7.2.20050318120448.03014980@mira-sjcm-2.cisco.com>
X-Sender: kleung@mira-sjcm-2.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 18 Mar 2005 12:29:12 -0800
To: Narayanan Vidya-CVN065 <vidya@motorola.com>
From: Kent Leung <kleung@cisco.com>
Subject: RE: [Mip4] Request to consider FMIPv4 as a working group document
In-Reply-To: <1B631E11D496D711BB2800065BFCB6A10C97790C@il02exm13>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 36c793b20164cfe75332aa66ddb21196
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>, "Charles E.Perkins" <charliep@iprg.nokia.com>, Rajeev Koodli <rajeev.koodli@nokia.com>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>, <mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>, <mailto:mip4-request@ietf.org?subject=subscribe>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b132cb3ed2d4be2017585bf6859e1ede

Hi Vidya.  I wouldn't put it that way.

My logic is that a Mobile IP based fast handover solution will involve 
Mobile IP
operation and messaging on the access router.  If the access router is to
be enabled with Mobile IP to support fast handover, then it might as well
be a Foreign Agent.  I don't see a practical rationale to upgrade the AR part
way in a sense.

Kent

At 01:41 PM 3/18/2005 -0600, Narayanan Vidya-CVN065 wrote:
>Hi Kent,
>What you are implying here seems to be that in order to have a fast 
>handoff solution, the MN must be using an FA CoA - did I get that right?
>
>If so, that seems a little restrictive to me. There are scenarios where 
>the MN may be using a CCoA and registering through an FA. Also, in 
>general, it seems that a solution that will work with or without FAs will 
>be a preferable one.
>
>Vidya
>
>-----Original Message-----
>From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf Of 
>Kent Leung
>Sent: Friday, March 18, 2005 12:45 PM
>To: Charles E.Perkins
>Cc: Mobile IPv4 Mailing List; Rajeev Koodli
>Subject: Re: [Mip4] Request to consider FMIPv4 as a working group document
>
>
>Hi Charlie.
>
>Generally, I support having a WG solution for fast handover using MIPv4.
>
>Some of the areas that is debatable in the draft:
>
>   - Key difference between MIPv4 and MIPv6 is FA existence.
>   - FMIPv4 enabled ARs not being FAs is unlikely, IMHO.  So
>     we can simplify by specifying only FA mode operation, no CCoA
>     support needed since ARs would have to be MIPv4 enabled.
>     This would fit the deployment model and clean up most of
>     draft dealing with IP address management.
>   - Support for fast handover in WiFi already exists today w/o
>     MIPv4 involvement.  Therefore, realizing deployments using
>     this type of scheme will be difficult.
>
>Haven't read the draft in detail for specifics to MIPv4.  Will comment on 
>them later.
>
>Kent
>
>At 01:53 PM 3/17/2005 -0800, Charles E.Perkins wrote:
>
>
> >Hello folks,
> >
> >We made a presentation at IETF 61 about a way to do
> >fast handovers with Mobile IPv4.  Our method is adapted
> >from the protocol for Mobile IPv6,
> >      draft-ietf-mipshop-fast-mipv6-03.txt
> >
> >The Mobile IPv6 protocol has been approved for
> >publication and is currently in the RFC editor's
> >queue.
> >
> >The discussion at IETF 61 can be reviewed from the
> >minutes, located at:
> >http://www1.ietf.org/proceedings_new/04nov/toc.html#int
> >
> >As part of this discussion, I showed some results which indicate very
> >good performance for FMIPv4, suitable for handling interactive voice
> >applications.  I probably have the PowerPoint presentation around
> >somewhere if needed.
> >
> >The protocol specification for the Mobile IPv4 fast
> >handovers is documented in the Internet Draft:
> >      draft-koodli-fmipv4-00.txt
> >which is available in the standard IETF draft
> >directories.
> >
> >Thanks in advance for your consideration of our
> >request.
> >
> >Regards,
> >Charlie P.
> >
> >--
> >Mip4 mailing list: Mip4@ietf.org
> >     Web interface: https://www1.ietf.org/mailman/listinfo/mip4
> >      Charter page: http://www.ietf.org/html.charters/mip4-charter.html
> >Supplemental site: http://www.mip4.org/
>
>--
>       |           |                   Kent Leung
>      :|:         :|:                  IP Mobility Development
>     :|||:       :|||:                 Internet Technologies Division
>    :|||||||:   :|||||||:              Voice: 408.526.5030
>.:|||||||||:.:|||||||||:.             Fax:   408.525.1653
>   c i s c o S y s t e m s             Email: kleung@cisco.com
>
>--
>Mip4 mailing list: Mip4@ietf.org
>     Web interface: https://www1.ietf.org/mailman/listinfo/mip4
>      Charter page: http://www.ietf.org/html.charters/mip4-charter.html
>Supplemental site: http://www.mip4.org/

--
      |           |                   Kent Leung
     :|:         :|:                  IP Mobility Development
    :|||:       :|||:                 Internet Technologies Division
   :|||||||:   :|||||||:              Voice: 408.526.5030
.:|||||||||:.:|||||||||:.             Fax:   408.525.1653
  c i s c o S y s t e m s             Email: kleung@cisco.com

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/