RE: [Mip4] FMIPv4
<rajeev.koodli@nokia.com> Tue, 23 January 2007 20:05 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H9Rtw-0001dD-Hl; Tue, 23 Jan 2007 15:05:52 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H9Rtv-0001cx-3c for mip4@ietf.org; Tue, 23 Jan 2007 15:05:51 -0500
Received: from smtp.nokia.com ([131.228.20.170] helo=mgw-ext11.nokia.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H9Rts-00077D-JI for mip4@ietf.org; Tue, 23 Jan 2007 15:05:51 -0500
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213]) by mgw-ext11.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id l0NK2n60001216; Tue, 23 Jan 2007 22:03:16 +0200
Received: from daebh102.NOE.Nokia.com ([10.241.35.112]) by esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 23 Jan 2007 22:05:23 +0200
Received: from daebe103.NOE.Nokia.com ([10.241.35.24]) by daebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 23 Jan 2007 14:05:44 -0600
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip4] FMIPv4
Date: Tue, 23 Jan 2007 14:05:45 -0600
Message-ID: <3C33B44F3E969F4D8DE8D578078410C86F8E3B@daebe103.NOE.Nokia.com>
In-Reply-To: <45B4F94B.7080309@motorola.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Mip4] FMIPv4
Thread-Index: Acc+TgMwzGRyT+OCSam6l4eu+AtWHQA2yTvw
From: rajeev.koodli@nokia.com
To: alexandru.petrescu@motorola.com, pete.mccann@motorola.com
X-OriginalArrivalTime: 23 Jan 2007 20:05:44.0631 (UTC) FILETIME=[DD892470:01C73F29]
X-Nokia-AV: Clean
X-Spam-Score: 0.2 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Cc: mip4@ietf.org
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>
Errors-To: mip4-bounces@ietf.org
Hi Alex, thank you for your review. >BAsically I'm fine with it, here's a few minor editorial. > >> Optimizations have been proposed and are being standardized in IEEE >> however. > >... for example IEEE 802.11r (Fast Roaming, Fast BSS >Transition) and to a certain extent 802.21; probably worth mentioning. > Ok. >> The design of the protocol is the same as for Mobile IPv6 [2]. >> Readers should consult [2] for details, and here we provide >a summary. >[...] >> [2] R. Koodli (Editor). Fast Handovers for Mobile IPv6 (work in >> progress). Internet Draft, Internet Engineering Task Force. >> draft-ietf-mipshop-fast-mipv6-03.txt, October 2005. > >Editing nit. The draft referred as [2] no longer exists I >believe. I think there may be plans in the mipshop WG to take >RFC4068 on a Stds Track. So maybe RFC4068 and RFC3775 should >be referred for the moment, or any other update more up to >date. This '[2]' is cited several times in the draft. > That should be RFC 4068. Thanks for catching it! >> 5.3. Router Solicitation for Proxy Advertisement (RtSolPr) > >Is this an RS carried as ICMP (RFC1256) or as ICMPv6. >Encoding is different. Remark that existing implementations >of ICMPv4 RS could be re-used for minimal modifications, or >otherwise ICMPv6 could be re-used. > It's a choice. But in a FMIPv4 deployment one wouldn't >assume availability of ICMPv6... or maybe yes (?). Also it's >strange to use Checksum field as computed from rfc1256 but the >format from ICMPv6. > >Same for Proxy Router Advertisement. > It _should_ be ICMPv4, with the allowance for ICMPv6 I guess. Will revise. Regards, -Rajeev >Alex > > > >-- >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] FMIPv4 McCann Peter-A001034
- Re: [Mip4] FMIPv4 Alexandru Petrescu
- RE: [Mip4] FMIPv4 rajeev.koodli
- Re: [Mip4] FMIPv4 Rajeev Koodli
- Re: [Mip4] FMIPv4 Alexandru Petrescu
- Re: [Mip4] FMIPv4 Rajeev Koodli
- Re: [Mip4] FMIPv4 Alexandru Petrescu