Re: [Seamoby] Deadline Approaching: WG Last Call for Paging Assessment Draft

Behcet Sarikaya <behcet.sarikaya@alcatel.com> Tue, 26 February 2002 00:03 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04589 for <seamoby-archive@odin.ietf.org>; Mon, 25 Feb 2002 19:03:38 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA25694; Mon, 25 Feb 2002 18:52:15 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA25625 for <seamoby@optimus.ietf.org>; Mon, 25 Feb 2002 18:52:12 -0500 (EST)
Received: from auds951.usa.alcatel.com (auds951.usa.alcatel.com [143.209.238.80] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04401 for <seamoby@ietf.org>; Mon, 25 Feb 2002 18:52:07 -0500 (EST)
Received: from alcatel.com (localhost [127.0.0.1]) by auds951.usa.alcatel.com (8.10.2/8.10.2) with ESMTP id g1PNpdq07967; Mon, 25 Feb 2002 17:51:39 -0600 (CST)
Message-ID: <3C7ACE0B.4040104@alcatel.com>
Date: Mon, 25 Feb 2002 17:51:39 -0600
From: Behcet Sarikaya <behcet.sarikaya@alcatel.com>
Organization: Alcatel USA
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2
X-Accept-Language: en-us
MIME-Version: 1.0
To: Srinivas.Sreemanthula@nokia.com
CC: seamoby@ietf.org
Subject: Re: [Seamoby] Deadline Approaching: WG Last Call for Paging Assessment Draft
References: <07EE0E021034014F99A57B032BC9C0E50FF672@daebe001.NOE.Nokia.com>
Content-Type: multipart/alternative; boundary="------------010900040701060305070400"
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org

A solution with no LMM means HA based paging, HA based paging is not 
scalable and it is inefficient. As you admit it has to be used only when 
no LMM agents available.

   LMM for Mipv4 seems to be done-deal, the only problem is right now at 
MIP WG is LMM for Mipv6 and I am sure it will be resolved very 
fast..There is no point and I do not think MIP WG would allow trying to 
develop an alternative.
 
  Alternative 2 is a win-win for all. If agreed, it enables both MIP 
based and Simple IP based solutions to be developed. Alternative 2 
requires harmonization within each and with MIP WG. This is the right 
approach, I think.

Srinivas.Sreemanthula@nokia.com wrote:

>>May I disagree on this? LMM is not Seamoby protocol. Alternative 2 is 
>>stating clearly that we follow the developments in Mobile IP WG and 
>>align Seamoby paging protocol with the LMM of choice in MIP WG. This 
>>creates a dependency. We already have a dependency by using MIP. What is 
>>wrong with another one?
>>
>
>I disagree. The fate of the paging protocol usability must not depend on whether (or when) a particular LMM is accepted in MIP WG or not. Instead, let's accept the dependency on mobility and limit it right there, without extending it to a particular LMM (or trying to align it to that of MIP WG). Let's develop a common solution - non-LMM based and a generalised LMM based or one that fits both.
>
>
>
>
>_______________________________________________
>Seamoby mailing list
>Seamoby@ietf.org
>https://www1.ietf.org/mailman/listinfo/seamoby
>

-- 
Behcet Sarikaya
Network Strategy Group, Mobile Networking Team
Alcatel USA M/S 026
1000 Coit Road  PB7
Plano, TX 75075 USA
Email: behcet.sarikaya@alcatel.com
Phone: (972) 477 2794 Fax: (972) 519 2460