RE: [Mip4] Request to consider FMIPv4 as a working group document
Narayanan Vidya-CVN065 <vidya@motorola.com> Fri, 18 March 2005 23:10 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 SAA20862 for <mip4-web-archive@ietf.org>; Fri, 18 Mar 2005 18:10:05 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DCQg5-0008OV-OL for mip4-web-archive@ietf.org; Fri, 18 Mar 2005 18:14:49 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DCQaM-0003ao-St; Fri, 18 Mar 2005 18:08:54 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DCQaL-0003ag-Bc for mip4@megatron.ietf.org; Fri, 18 Mar 2005 18:08:53 -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 SAA20713 for <mip4@ietf.org>; Fri, 18 Mar 2005 18:08:50 -0500 (EST)
Received: from motgate.mot.com ([129.188.136.100]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DCQes-0008NC-AX for mip4@ietf.org; Fri, 18 Mar 2005 18:13:34 -0500
Received: from az33exr04.mot.com (az33exr04.mot.com [10.64.251.234]) by motgate.mot.com (Motorola/Motgate) with ESMTP id j2IN8p99010229 for <mip4@ietf.org>; Fri, 18 Mar 2005 16:08:51 -0700 (MST)
Received: from il02exm13.corp.mot.com (il02exm13.corp.mot.com [10.0.111.24]) by az33exr04.mot.com (8.13.1/8.13.0) with ESMTP id j2IN9a4s024331 for <mip4@ietf.org>; Fri, 18 Mar 2005 17:09:37 -0600 (CST)
Received: by il02exm13 with Internet Mail Service (5.5.2657.72) id <D3S2RV6V>; Fri, 18 Mar 2005 17:08:50 -0600
Message-ID: <1B631E11D496D711BB2800065BFCB6A10C977916@il02exm13>
From: Narayanan Vidya-CVN065 <vidya@motorola.com>
To: 'Mobile IPv4 Mailing List' <mip4@ietf.org>
Subject: RE: [Mip4] Request to consider FMIPv4 as a working group document
Date: Fri, 18 Mar 2005 17:08:48 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Cc: '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: 34d35111647d654d033d58d318c0d21a
All, Does anyone know what happened to the draft on post-MIT? A few years ago, I thought it was being considered to be part of the low latency handoff spec - but, obviously it has not made it. James' draft on Post-MIT was trying to solve the issue of L2 dependency. Essentially, I see this as a major deployment issue to have a fast handoff solution exclusively dependent on receiving an L2 trigger (e.g. the L2 Target Trigger at the nFA). I think an approach like FMIPv4 is essential in light of this. Ideally, I think post-MIT should have been a part of LLH - that way, we won't have the need to have 2 specifications that are somewhat close with only minor differences. Vidya -----Original Message----- From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf Of Espen Klovning Sent: Friday, March 18, 2005 4:30 PM To: 'Charles E.Perkins'; 'Mobile IPv4 Mailing List' Cc: 'Rajeev Koodli' Subject: RE: [Mip4] Request to consider FMIPv4 as a working group document Hi Charlie I support making this draft a WG item. I do have some concerns that more or less reflect what Kent Leung has voiced in previous mails on the list. - AR == FA - IP address management An additional issue is how the MN-PAR auth extension is handled. I take it this will reuse MN-FA auth extension. It will require key distribution of some kind that could jeopardize the performance benefits. What am I missing? regards espen Espen Klovning Birdstep Technology In addition, > -----Original Message----- > From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf > Of Charles E.Perkins > Sent: Thursday, March 17, 2005 10:53 PM > To: Mobile IPv4 Mailing List > Cc: Rajeev Koodli > Subject: [Mip4] Request to consider FMIPv4 as a working group document > > > > 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/ -- 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/ -- 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/
- [Mip4] Request to consider FMIPv4 as a working gr… Charles E.Perkins
- Re: [Mip4] Request to consider FMIPv4 as a workin… Kent Leung
- RE: [Mip4] Request to consider FMIPv4 as a workin… Narayanan Vidya-CVN065
- Re: [Mip4] Request to consider FMIPv4 as a workin… Charles E. Perkins
- RE: [Mip4] Request to consider FMIPv4 as a workin… Soliman, Hesham
- RE: [Mip4] Request to consider FMIPv4 as a workin… Kent Leung
- RE: [Mip4] Request to consider FMIPv4 as a workin… Kent Leung
- Re: [Mip4] Request to consider FMIPv4 as a workin… Kent Leung
- RE: [Mip4] Request to consider FMIPv4 as a workin… Espen Klovning
- RE: [Mip4] Request to consider FMIPv4 as a workin… Narayanan Vidya-CVN065
- Re: [Mip4] Request to consider FMIPv4 as a workin… Alexandru Petrescu
- Re: [Mip4] Request to consider FMIPv4 as a workin… Alexandru Petrescu
- Re: [Mip4] Request to consider FMIPv4 as a workin… James Kempf
- Re: [Mip4] Request to consider FMIPv4 as a workin… Alexandru Petrescu
- Re: [Mip4] Request to consider FMIPv4 as a workin… Rajeev Koodli
- Fwd: [Mip4] Request to consider FMIPv4 as a worki… Henrik Levkowetz