Re: [Mip4] Problem of using layer 2 triggers alone for the Low latency Handoff for MIPv4
Sebastian Thalanany <comscape@gmail.com> Wed, 17 January 2007 19:20 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H7GL8-00008R-02; Wed, 17 Jan 2007 14:20:54 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H7GL7-00008I-0V for mip4@ietf.org; Wed, 17 Jan 2007 14:20:53 -0500
Received: from py-out-1112.google.com ([64.233.166.183]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H7GL5-0006Rb-GI for mip4@ietf.org; Wed, 17 Jan 2007 14:20:52 -0500
Received: by py-out-1112.google.com with SMTP id f31so1140103pyh for <mip4@ietf.org>; Wed, 17 Jan 2007 11:20:51 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:x-accept-language:mime-version:to:cc:subject:references:in-reply-to:content-type; b=GDWDhGkDUszwn07pY57oEvGg2KXfHz3FF1KwSj1R5vB0hmxmfvsfpQPDRz5075pUK9U3RUSVn5C9lHDVW0UbG7s93PNA54LZzYw9SKd2lPpJQ61KHQ9GK8857BWw9Vd6x78OEDiLH0W7RQqbEkEW9lXDTTlwItfKU4nDvUaYC4o=
Received: by 10.35.9.15 with SMTP id m15mr13235183pyi.1169061650786; Wed, 17 Jan 2007 11:20:50 -0800 (PST)
Received: from ?10.105.16.28? ( [12.192.138.117]) by mx.google.com with ESMTP id f78sm9848711pyh.2007.01.17.11.20.48; Wed, 17 Jan 2007 11:20:49 -0800 (PST)
Message-ID: <45AE7709.5020005@gmail.com>
Date: Wed, 17 Jan 2007 13:20:41 -0600
From: Sebastian Thalanany <comscape@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ANTOINE Stephane RD-ILAB-LON <stephane.antoine@orange-ftgroup.com>
Subject: Re: [Mip4] Problem of using layer 2 triggers alone for the Low latency Handoff for MIPv4
References: <14FD20369E52DE478BD9612D63BE21B4070F841F@ftrdmel3.rd.francetelecom.fr>
In-Reply-To: <14FD20369E52DE478BD9612D63BE21B4070F841F@ftrdmel3.rd.francetelecom.fr>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 8068004c042dabd7f1301bcc80e039df
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>
Content-Type: multipart/mixed; boundary="===============1210201007=="
Errors-To: mip4-bounces@ietf.org
Hello, Stephane, Thanks for your query. Please note my responses in-line. Regards, Sebastian ANTOINE Stephane RD-ILAB-LON wrote: > Hello, > > I would like to get some feedback about the problem, as described > below, of using layer 2 triggers alone to initiate the Low latency > Handoff for MIPv4: > > > > The Low Latency Handoff for MIPv4 as described in > > http://www.ietf.org/internet-drafts/draft-ietf-mobileip-lowlatency-handoffs-v4-11.txt > > assumes availability of the L2 triggers which contain Layer 3 > information such as the IP address of the new Foreign Agent. > Availability of the Layer 3 information is assumed in the Layer 2 > trigger. However the method by which the Layer 3 information is made > available in the Layer 2 trigger has not been specified. > st> The specific procedure used to acquire the L3 information, such as the IP address of the appropriate access gateway is dependent on the access technology over which the low-latency handoff scheme is applied. For instance, the radio access point or base station identifier could be used to determine the L3 information associated with the radio access point or the base station (L2 entities). The L3 information could be statically or dynamically configured at the L2 entity based on the connectivity to an L3 entity (access gateway). > Moreover, Layer 2 trigger will actually occur in response or in > prevision to certain link events such as the fading of the relative > signal noise ratio below a certain level. > st> Yes. > Relying only on link information to initiate a handoff does not > generally gather enough information for the Mobile Node to handoff to > the most suitable available access network at the most suitable time. > st> See the previous response on L3 information acquisition. > > > Information from layers higher than Layer 2 (that may come from > various protocols) can be used as triggers to compensate the > insufficiency of using Layer 2 triggers alone for the Low latency > Handoff for MIPv4. > st> The L2 trigger information is used to assist the upper layer protocols, in the case of wireless mobility with minimum latency, and not vice-versa. Using access technology specific schemes, the required L3 information, such as the serving access gateway IP address can be obtained from the L2 trigger information. > > > I would also appreciate receiving some feedback upon the work > presenting scenarios describing how the low latency Handoff for MIPv4 > is initiated by higher layer triggers. > > http://www.ietf.org/internet-drafts/draft-antoine-mip4-lowlatency-handoff-triggers-00.txt > > > > Cheers > > > > Stephane > > >
-- 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] Problem of using layer 2 triggers alone fo… ANTOINE Stephane RD-ILAB-LON
- Re: [Mip4] Problem of using layer 2 triggers alon… Sebastian Thalanany