Re: pmipv4 of WiMAX forum (Re: [Mip4]Questionaboutdraft-leung-mip4-proxy-mode)
Jun AWANO <j-awano@az.jp.nec.com> Sat, 28 July 2007 05:26 UTC
Return-path: <mip4-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IEep2-0004uj-6z; Sat, 28 Jul 2007 01:26:36 -0400
Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1IEeoz-0004ud-Vc for mip4-confirm+ok@megatron.ietf.org; Sat, 28 Jul 2007 01:26:33 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IEeoz-0004uT-2t for mip4@ietf.org; Sat, 28 Jul 2007 01:26:33 -0400
Received: from tyo201.gate.nec.co.jp ([202.32.8.193]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IEeox-0001F0-T7 for mip4@ietf.org; Sat, 28 Jul 2007 01:26:32 -0400
Received: from mailgate3.nec.co.jp (mailgate54.nec.co.jp [10.7.69.193]) by tyo201.gate.nec.co.jp (8.13.8/8.13.4) with ESMTP id l6S5QOgC014120; Sat, 28 Jul 2007 14:26:24 +0900 (JST)
Received: (from root@localhost) by mailgate3.nec.co.jp (8.11.7/3.7W-MAILGATE-NEC) id l6S5QOu14691; Sat, 28 Jul 2007 14:26:24 +0900 (JST)
Received: from kuichi.jp.nec.com (kuichi.jp.nec.com [10.26.220.17]) by mailsv4.nec.co.jp (8.11.7/3.7W-MAILSV4-NEC) with ESMTP id l6S5QNX27529; Sat, 28 Jul 2007 14:26:23 +0900 (JST)
Received: from [10.87.72.34] ([10.87.72.34] [10.87.72.34]) by mail.jp.nec.com with ESMTP; Sat, 28 Jul 2007 14:26:21 +0900
Message-Id: <46AAD381.2080401@az.jp.nec.com>
Date: Sat, 28 Jul 2007 00:26:25 -0500
From: Jun AWANO <j-awano@az.jp.nec.com>
User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
MIME-Version: 1.0
To: "Yoshi Tsuda (yotsuda)" <yotsuda@cisco.com>, mip4 <mip4@ietf.org>
Subject: Re: pmipv4 of WiMAX forum (Re: [Mip4]Questionaboutdraft-leung-mip4-proxy-mode)
References: <35912544FC930E49BF20EF16C3EF2765027A4819@xmb-hkg-416.apac.cisco.com> <46AA7C18.3040101@az.jp.nec.com>
In-Reply-To: <46AA7C18.3040101@az.jp.nec.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8c5db863102a3ada84e0cd52a81a79e
Cc: "Kent Leung (kleung)" <kleung@cisco.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>
Errors-To: mip4-bounces@ietf.org
Hi Tsuda-san and Kent, I forgot to say about supporting IPv6/DS host. Of cource, draft-leung-mip4-proxy-mode could include the feature to support IPv6/DS host although WiMAX spec PMIPv4 doesn't have such a feature (at least so far). But I think there are issues about this. The first issue: The draft refers to draft-navali-ip6-over-netmip4-00 (I found out -02 ver.) to achieve support for dual stack feature. You know, mip4 WG already have dsmipv4 draft. It's draft-ietf-mip4-dsmipv4. Although some modifications might be needed to adapt draft-ietf-mip4-dsmipv4 to proxy mode. (e.g. RRQ MUST include IPv6 Tunneling Mode Ext.) Extensions defined at draft-ietf-mip4-dsmipv4 can be reused. The draft defines IPv4 Prefix Ext and IPv6 Code Ext to request, bind and get IPv6 HoA. OTOH, draft-navali-ip6-over-netmip4 defines IPv6 Home Address Request Ext and IPv6 Home Address Extension for the same aims. IMO, I don't want to have different extension to achieve the same effect. I want to reuse extensions and procedures described in draft-navali-ip6-over-netmip4 as much as possible. The second issue: I think there might be an argument about necessity of PMIPv4 DS support. Because PMIPv6 draft + IPv4 support draft can cover almost the same scenario as PMIPv4 DS can. What do you think? Thanks, Jun Jun AWANO wrote: > Hi Tsuda-san, > > O.K. Tsuda-san. > I think I couldn't pick up all of differences. > But I try to enumerate them. > > The differences are as following. > > 1. Terminologies > draft-leung-mip4-proxy-mode says > LMA,MAG,PRRQ,PRRP. > But WiMAX spec doesn't use such terminologies. > Just, HA, FA & PMIP Client, RRQ, RRP,respectively. > > 2. New extensions > draft-leung-mip4-proxy-mode defines new MIPv4 extensions, > Proxy Mobile IPv4 Mode Extension and PMIPv4 Per-Node > Authentication Method Extension. And enfocing to use them. > But WiMAX spec doesn't support them. > > 3. New error codes > draft-leung-mip4-proxy-mode defines new error codes, > PMIP_UNSUPPORTED and PMIP_DISALLOWED. > But WiMAX spec doesn't use them. > > 4. How to use Registration Revocation > When a MN moves to a new MAG. > Registration Revocation message is sent to the > previous MAG according to draft-leung-mip4-proxy-mode. > I'm not sure it's different or not. > But at least WiMAX spec doesn't say explicitly that > a LMA(HA) uses Registration Revocation in this case. > > 5. Processing Proxy Registration Request > Whole sentence described at "8.1. Processing Proxy > Registration Requests" is different from WiMAX spec. > A HA specified in WiMAX performs as per RFC3344. > So the HA doesn't perform like described at "8.1.". > i.e. The HA doen't use Sequence Number and doesn't > send error RRP like described at "8.1.". > > 6. Moving to a New MAG > I think draft-leung-mip4-proxy-mode assumes that > the MAG which sends RRQ on behalf of a MN is relocated > when the MN has moved to a new MAG. > But In WiMAX spec, PMIP client which sends RRQ on behalf > of a MN is anchored even when the MN has moved to a new FA. > Are you following the proceeding of netlmm WG? > And do you know Ajoy's PMIPv6 draft? > http://tools.ietf.org/wg/netlmm/draft-singh-netlmm-protocol-03.txt > The MAG described in the draft is anchored while moving. > The PMIP client specified in WiMAX is similar to it. > So, WiMAX PMIP client isn't required to transfer any MN's > contexts(e.g. MN-HA key) when the MN has moved. > > Best Regard, > Jun > > > Yoshi Tsuda (yotsuda) wrote: >> Hi Awano-san, >> >> What do you think the major technical differences between current >> Kent's draft and the current WiMAX spec? >> You know, most people in this MIP4 mailinglist doesn't have enough >> time to check the specific WiMAX spec. So, we would appreciate, >> if you point out the MIPv4-related technical differences instead of >> just >> saying different. >> >> Thanks in advance. >> -Yoshi >> >>> -----Original Message----- >>> From: Kent Leung (kleung) Sent: Friday, July 27, 2007 9:31 AM >>> To: Jun AWANO; mip4 >>> Subject: RE: pmipv4 of WiMAX forum (Re: >>> [Mip4]Questionaboutdraft-leung-mip4-proxy-mode) >>> >>> Let me clarify that we will be updating our draft, >>> draft-leung-mip4-proxy-mode, accordingly to address the gaps. >>> >>> Kent >>> -----Original Message----- >>> From: Kent Leung (kleung) >>> Sent: Friday, July 27, 2007 9:29 AM >>> To: Jun AWANO; mip4 >>> Subject: RE: pmipv4 of WiMAX forum (Re: [Mip4] >>> Questionaboutdraft-leung-mip4-proxy-mode) >>> >>> Hi Jun. >>> >>> We are working with WiMAX Forum members to address the technical gaps >>> in the draft. Currently, we are collecting the review comments and >>> will update the draft accordingly. >>> >>> Kent >>> -----Original Message----- >>> From: Jun AWANO [mailto:j-awano@az.jp.nec.com] >>> Sent: Thursday, July 26, 2007 7:23 PM >>> To: mip4 >>> Subject: pmipv4 of WiMAX forum (Re: [Mip4] Question >>> aboutdraft-leung-mip4-proxy-mode) >>> >>> Hi, kent >>> >>> Please let me ask about your draft. >>> >>> Your draft says, >>> "This document describes WiMAX Forum and 3GPP2 solution for the base >>> Proxy Mobile IPv4 function which enables another entity to provide >>> mobility support on behalf of an unaltered and mobility-unaware IPv4 >>> device." >>> >>> But, I think that the PMIPv4 described in your draft seems different >>> from the one specified in WiMAX Forum spec (WiMAX Forum Network >>> Architechture stage2/3). >>> >>> Do you plan to change the PMIPv4 spec of WiMAX Forum to match your >>> draft? >>> >>> Best Regards, >>> Jun >>> >>> >>> -- >>> 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/ >>> >> >> > > -- ----------------------------------------------- Jun AWANO <j-awano@az.jp.nec.com> NEC System Platforms Research Laboratories Tel:+81 44 431 7638, FAX:+81 44 431 7609 -- 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] Question about draft-leung-mip4-proxy-mode Bruno Mongazon-Cazavet
- RE: [Mip4] Question about draft-leung-mip4-proxy-… Kent Leung (kleung)
- Re: [Mip4] Question about draft-leung-mip4-proxy-… Bruno Mongazon-Cazavet
- Re: [Mip4] Question about draft-leung-mip4-proxy-… John.zhao
- pmipv4 of WiMAX forum (Re: [Mip4] Question about … Jun AWANO
- RE: [Mip4] Question about draft-leung-mip4-proxy-… Kent Leung (kleung)
- RE: [Mip4] Question about draft-leung-mip4-proxy-… Kent Leung (kleung)
- RE: pmipv4 of WiMAX forum (Re: [Mip4] Question ab… Kent Leung (kleung)
- RE: pmipv4 of WiMAX forum (Re: [Mip4] Questionabo… Kent Leung (kleung)
- RE: pmipv4 of WiMAX forum (Re: [Mip4]Questionabou… Yoshi Tsuda (yotsuda)
- Re: pmipv4 of WiMAX forum (Re: [Mip4] Questionabo… Jun AWANO
- Re: pmipv4 of WiMAX forum (Re: [Mip4]Questionabou… Jun AWANO
- Re: pmipv4 of WiMAX forum (Re: [Mip4]Questionabou… Jun AWANO
- Re: [Mip4] Question about draft-leung-mip4-proxy-… Bruno Mongazon-Cazavet