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

Kent Leung <kleung@cisco.com> Fri, 18 March 2005 18:55 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 NAA10522 for <mip4-web-archive@ietf.org>; Fri, 18 Mar 2005 13:55:35 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DCMhm-0001v8-0i for mip4-web-archive@ietf.org; Fri, 18 Mar 2005 14:00:18 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DCMZt-0006nM-Cx; Fri, 18 Mar 2005 13:52:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DCMZr-0006nE-PR for mip4@megatron.ietf.org; Fri, 18 Mar 2005 13:52:08 -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 NAA09914 for <mip4@ietf.org>; Fri, 18 Mar 2005 13:52:04 -0500 (EST)
Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DCMeM-0001lS-Hu for mip4@ietf.org; Fri, 18 Mar 2005 13:56:47 -0500
Received: from sj-core-5.cisco.com (171.71.177.238) by sj-iport-4.cisco.com with ESMTP; 18 Mar 2005 10:53:15 -0800
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id j2IIptZV000658; Fri, 18 Mar 2005 10:51:56 -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 BDA93744; Fri, 18 Mar 2005 10:51:54 -0800 (PST)
Message-Id: <4.3.2.7.2.20050318083546.0305f100@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 10:44:44 -0800
To: "Charles E.Perkins" <charliep@iprg.nokia.com>
From: Kent Leung <kleung@cisco.com>
Subject: Re: [Mip4] Request to consider FMIPv4 as a working group document
In-Reply-To: <4239FC52.33760051@iprg.nokia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>, 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: 00e94c813bef7832af255170dca19e36

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/