RE: [Mip4] Request to consider FMIPv4 as a working group document
"Espen Klovning" <espen@birdstep.com> Fri, 18 March 2005 22:32 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 RAA16294 for <mip4-web-archive@ietf.org>; Fri, 18 Mar 2005 17:32:50 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DCQ62-0006s7-Mx for mip4-web-archive@ietf.org; Fri, 18 Mar 2005 17:37:34 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DCPyv-0002cA-Oy; Fri, 18 Mar 2005 17:30:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DCPyt-0002bz-OT for mip4@megatron.ietf.org; Fri, 18 Mar 2005 17:30:11 -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 RAA15828 for <mip4@ietf.org>; Fri, 18 Mar 2005 17:30:08 -0500 (EST)
Received: from mail.birdstep.com ([80.239.52.35]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DCQ3P-0006lQ-8l for mip4@ietf.org; Fri, 18 Mar 2005 17:34:52 -0500
Received: from HPTRYBUY (ti211110a080-3144.bb.online.no [85.165.76.72]) (authenticated bits=0) by mail.birdstep.com (8.12.8/8.12.8) with ESMTP id j2IMTwGa007066 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Fri, 18 Mar 2005 23:29:59 +0100
Message-Id: <200503182229.j2IMTwGa007066@mail.birdstep.com>
From: Espen Klovning <espen@birdstep.com>
To: "'Charles E.Perkins'" <charliep@iprg.nokia.com>, 'Mobile IPv4 Mailing List' <mip4@ietf.org>
Subject: RE: [Mip4] Request to consider FMIPv4 as a working group document
Date: Fri, 18 Mar 2005 23:30:03 +0100
Organization: Birdstep Technology ASA
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
In-Reply-To: <4239FC52.33760051@iprg.nokia.com>
Thread-Index: AcUrPAmoSCVXOdaxSy2rer/dt/XmpAAyOFTw
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Content-Transfer-Encoding: 7bit
Cc: 'Rajeev Koodli' <rajeev.koodli@nokia.com>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: espen@birdstep.com
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: d8ae4fd88fcaf47c1a71c804d04f413d
Content-Transfer-Encoding: 7bit
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] 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