Re: [Mip4] Question about draft-leung-mip4-proxy-mode
Bruno Mongazon-Cazavet <bruno.mongazon-cazavet@alcatel-lucent.fr> Mon, 30 July 2007 08:40 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 1IFQnb-0005gX-NI; Mon, 30 Jul 2007 04:40:19 -0400
Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1IFQna-0005gS-Ob for mip4-confirm+ok@megatron.ietf.org; Mon, 30 Jul 2007 04:40:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IFQna-0005gK-F8 for mip4@ietf.org; Mon, 30 Jul 2007 04:40:18 -0400
Received: from smail5.alcatel.fr ([62.23.212.27]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IFQnZ-000551-Jd for mip4@ietf.org; Mon, 30 Jul 2007 04:40:18 -0400
Received: from FRVELSBHS07.ad2.ad.alcatel.com (frvelsbhs07.ad2.ad.alcatel.com [155.132.6.79]) by smail5.alcatel.fr (8.13.4/8.13.4/ICT) with ESMTP id l6U8e7gZ004098; Mon, 30 Jul 2007 10:40:07 +0200
Received: from [172.27.205.222] ([172.27.205.222]) by FRVELSBHS07.ad2.ad.alcatel.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.2499); Mon, 30 Jul 2007 10:40:14 +0200
Message-ID: <46ADA3EE.5090306@alcatel-lucent.fr>
Date: Mon, 30 Jul 2007 10:40:14 +0200
From: Bruno Mongazon-Cazavet <bruno.mongazon-cazavet@alcatel-lucent.fr>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: "Kent Leung (kleung)" <kleung@cisco.com>
Subject: Re: [Mip4] Question about draft-leung-mip4-proxy-mode
References: <2979E38DD6FC6544B789C8DAD7BAFC520445EA5E@xmb-sjc-235.amer.cisco.com>
In-Reply-To: <2979E38DD6FC6544B789C8DAD7BAFC520445EA5E@xmb-sjc-235.amer.cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 30 Jul 2007 08:40:14.0606 (UTC) FILETIME=[3FCA62E0:01C7D285]
X-Scanned-By: MIMEDefang 2.51 on 155.132.188.13
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8
Cc: Mobile IPv4 Mailing List <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
Kent Leung (kleung) wrote: > The router which implements the MIP4 proxy mode may not be enabled with > FA service. In such case, collocated Care-of Address may be used for > Mobile IP registration/tunneling. > > I think your question is based on the need for the mobile terminal to > learn if the network supports PMIP and/or MIP. Is this in the context > of WiMAX or just generic MIP? > Generic MIP. > For generic MIP, a MIP-enabled terminal also supports simple IP. If the > terminal is using the MIP Home Address, then it must register with its > HA via FA CoA or CCoA to maintain its communications. If a CCoA address > is available, the terminal may use that IP address as well. Not clear > if the terminal needs to know if this IP address is provided mobility by > the network? For PMIP, this is suppose to be transparent to the mobile > terminal. Of course, the terminal can detect if the CCoA is still > usable after handover via DHCP, ARP, and/or ICMP mechanisms without > having to know what the network is doing. > Of course such mechanisms can be used. I am just wondering if a simple and common mechanism can be used to do so. Would be more simple and direct to send a RS and get back the answer in a RA. This does not impact existing simple IP terminals that would not send RS, but only MIP capable. Just to ease the job, not contradicting MIP philosophy i guess. > For WiMAX case, we should probably discuss this on the NWG alias. > > Kent > > -----Original Message----- > From: Bruno Mongazon-Cazavet > [mailto:bruno.mongazon-cazavet@alcatel-lucent.fr] > Sent: Thursday, July 26, 2007 6:17 AM > To: Kent Leung (kleung) > Cc: Mobile IPv4 Mailing List > Subject: Re: [Mip4] Question about draft-leung-mip4-proxy-mode > > Kent Leung (kleung) wrote: > >> Hi Bruno. Sorry, I missed this question. >> >> In this case, the Router Advertisement will not have the Mobility >> Agent Advertisement Extension. >> >> > Since a router implementing MIP4 proxy mode includes FA function, isn't > it logical and consistent to include a Mobility Agent Advertisment > extension in RA to indicate FA support? > I would suggest this behaviour can be added to your draft, possibly > extending the Mobility Agent Advertisment extension to indicate PMIP > support (i think some place is left for RFU in the format). > > What do you think? > > Such addition is not intended to be processed (understandable) by simple > IP terminals, but rather by terminals that might behave as simple IP or > MIP and need to choose which protocol to use. > > Thanks in advance for your reply. > Bruno. > >> Kent >> >> -----Original Message----- >> From: Bruno Mongazon-Cazavet >> [mailto:bruno.mongazon-cazavet@alcatel-lucent.fr] >> Sent: Thursday, July 19, 2007 8:48 AM >> To: Mobile IPv4 Mailing List >> Subject: [Mip4] Question about draft-leung-mip4-proxy-mode >> >> Hello, >> >> When a router implements this draft, how should it reacts to Router >> Solicitation? >> In particular: >> -should the router fill the Mobility Agent Advertisement extension in >> the reply? >> -should the FA capability be set if only PMIP is supported? >> >> Thanks, Bruno. >> >> >> -- >> 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] 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