Re: [MEXT] [dmm?] Surprising assertion about make-before-break handover prevalance

Hesham Soliman <hesham@elevatemobile.com> Fri, 05 August 2011 03:32 UTC

Return-Path: <hesham@elevatemobile.com>
X-Original-To: mext@ietfa.amsl.com
Delivered-To: mext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81B9011E80B4 for <mext@ietfa.amsl.com>; Thu, 4 Aug 2011 20:32:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LrPxd+aB8BhD for <mext@ietfa.amsl.com>; Thu, 4 Aug 2011 20:32:30 -0700 (PDT)
Received: from smtp-1.servers.netregistry.net (smtp.netregistry.net [202.124.241.204]) by ietfa.amsl.com (Postfix) with ESMTP id E3CB211E809B for <mext@ietf.org>; Thu, 4 Aug 2011 20:32:29 -0700 (PDT)
Received: from [203.219.211.243] (helo=[192.168.0.11]) by smtp-1.servers.netregistry.net protocol: esmtpa (Exim 4.69 #1 (Debian)) id 1QpB8W-0008DA-WE; Fri, 05 Aug 2011 13:31:49 +1000
User-Agent: Microsoft-MacOutlook/14.12.0.110505
Date: Fri, 05 Aug 2011 13:31:44 +1000
From: Hesham Soliman <hesham@elevatemobile.com>
To: Sri Gundavelli <sgundave@cisco.com>, <Basavaraj.Patil@nokia.com>, <charles.perkins@earthlink.net>, <mext@ietf.org>
Message-ID: <CA61A089.18306%hesham@elevatemobile.com>
Thread-Topic: [MEXT] [dmm?] Surprising assertion about make-before-break handover prevalance
In-Reply-To: <CA60A942.238D2%sgundave@cisco.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Authenticated-User: hesham@elevatemobile.com
Subject: Re: [MEXT] [dmm?] Surprising assertion about make-before-break handover prevalance
X-BeenThere: mext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mobile IPv6 EXTensions WG <mext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mext>, <mailto:mext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mext>
List-Post: <mailto:mext@ietf.org>
List-Help: <mailto:mext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mext>, <mailto:mext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Aug 2011 03:32:30 -0000

From: Sri Gundavelli <sgundave@cisco.com>
>>Will devices keep multiple radios powered on simultaneously in the
>>future?
>> It depends.
>> Battery technology still lags the advances of radio, processors and
>> displays on devices. And hence it generally boils down to optimizing
>> battery in handheld devices which implies that you would not want to
>> always keep multiple radios switched "On" all the time. You could if you
>> were willing to carry around a battery backpack all the time :)
>
>
>After all the standardization around MCoA/IFOM, building all the
>hype/coolness around driving one flow on path and another the other path,
>its sad to note that we simply don't have the devices/or the battery
>technology that can keep multiple radios up at the same time for a
>reasonable length of time (except few exceptions).


=> This is not about MCoA or flow mobility. Of course we have the ability
to have multiple interfaces up and many of us use it everyday. I assumed
Charlie's question was not about this trivial case, which we all know
exists, but rather about a single technology doing make before break
handovers. I know of only one radio technology that did that in real
deployments (OFDM).

Hesham



>Most devices/operator
>configuration still try to keep only one radio active at a time, so they
>can
>claim better battery serving time. So, we are not there yet, but from
>what I
>believe with LTE radios, the power requirement is only going up.
>Hopefully,
>there will be a major breakthrough in the battery technology that will
>allow
>all the radios to be up for a day with a recharge ...
>
>
>Sri
>
>
>
>
>
>
>
>_______________________________________________
>MEXT mailing list
>MEXT@ietf.org
>https://www.ietf.org/mailman/listinfo/mext