Re: [MEXT] [dmm?] Surprising assertion about make-before-break handover prevalance
Sri Gundavelli <sgundave@cisco.com> Fri, 05 August 2011 04:24 UTC
Return-Path: <sgundave@cisco.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 4453311E80C4 for <mext@ietfa.amsl.com>;
Thu, 4 Aug 2011 21:24:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.086
X-Spam-Level:
X-Spam-Status: No, score=-3.086 tagged_above=-999 required=5 tests=[AWL=-0.487,
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 GVNqJm+-WsAz for
<mext@ietfa.amsl.com>; Thu, 4 Aug 2011 21:24:25 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78])
by ietfa.amsl.com (Postfix) with ESMTP id AD9EA11E8073 for <mext@ietf.org>;
Thu, 4 Aug 2011 21:24:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com;
i=sgundave@cisco.com; l=1507; q=dns/txt; s=iport; t=1312518281; x=1313727881;
h=date:subject:from:to:message-id:in-reply-to:mime-version: content-transfer-encoding;
bh=HKsrWDq6iX/3YOHvCmpUNUWCpjxeBW6DmlpQ9X8ce+s=;
b=FkORW5mIoIoN1tfm5GRhKdtXMORQNgHlHgCm8JPxOJaE4fH3NSMNAOXl
s6oBJmqE8eIFW6HxijlHxKHcPO8fnXIogPtYMDVDxlt6+gY6NfeqGzMfc
dXH5YBDqkroaR9zQnxqwjNqayhgzUaNttCOTgjMsyyl3nJ32iisdzvGAI U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAI5vO06rRDoI/2dsb2JhbABDp293gUABAQEBAxIBJwIBMR0BCIEdAQEEARIZCaosAZ5mhkYEh1uLJIURi3Y
X-IronPort-AV: E=Sophos;i="4.67,320,1309737600"; d="scan'208";a="9899414"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by rcdn-iport-7.cisco.com
with ESMTP; 05 Aug 2011 04:24:40 +0000
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
[128.107.191.63]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id
p754OeHZ025953; Fri, 5 Aug 2011 04:24:40 GMT
Received: from xmb-sjc-214.amer.cisco.com ([171.70.151.145]) by
xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);
Thu, 4 Aug 2011 21:24:40 -0700
Received: from 10.32.246.212 ([10.32.246.212]) by xmb-sjc-214.amer.cisco.com
([171.70.151.145]) with Microsoft Exchange Server HTTP-DAV ;
Fri, 5 Aug 2011 04:24:39 +0000
User-Agent: Microsoft-Entourage/12.30.0.110427
Date: Thu, 04 Aug 2011 21:24:39 -0700
From: Sri Gundavelli <sgundave@cisco.com>
To: Hesham Soliman <hesham@elevatemobile.com>, <Basavaraj.Patil@nokia.com>,
<charles.perkins@earthlink.net>, <mext@ietf.org>
Message-ID: <CA60BE97.238EB%sgundave@cisco.com>
Thread-Topic: [MEXT] [dmm?] Surprising assertion about make-before-break
handover prevalance
Thread-Index: AcxTJ5cNBbFZPpZ6I0OHtk4LjtJNyw==
In-Reply-To: <CA61A089.18306%hesham@elevatemobile.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 05 Aug 2011 04:24:40.0412 (UTC)
FILETIME=[97E551C0:01CC5327]
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 04:24:26 -0000
On 8/4/11 8:31 PM, "Hesham Soliman" <hesham@elevatemobile.com> wrote: > > >> >> 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 Yes, we slightly digressed from Charlie's original point. But, on keeping multiple radios up, the point that Raj touched on, sure, we can keep all the radios up, but with the charger wired on, in practical terms. All I know is, if I keep my WLAN interface up on my Droid X, I need a much sooner recharge. I also know, most terminals are configured to USE only one radio up for whatever reasons. But, I Ack, there may be some terminals which may be using both the interfaces, ignoring their SAS awareness ..etc... Any case, glad to hear your comments/disagreements. We need some life into these all dead IETF mailing lists :) ... Sri
- [MEXT] [dmm?] Surprising assertion about make-bef… Charles E. Perkins
- Re: [MEXT] [dmm?] Surprising assertion about make… Basavaraj.Patil
- Re: [MEXT] [dmm?] Surprising assertion about make… Stuart W. Card
- Re: [MEXT] [dmm?] Surprising assertion about make… Hesham Soliman
- Re: [MEXT] [dmm?] Surprising assertion about make… Sri Gundavelli
- Re: [MEXT] [dmm?] Surprising assertion about make… Hesham Soliman
- Re: [MEXT] [dmm?] Surprising assertion about make… Sri Gundavelli
- Re: [MEXT] [dmm?] Surprising assertion about make… Hesham Soliman
- Re: [MEXT] [dmm?] Surprising assertion about make… Charles E. Perkins
- Re: [MEXT] [dmm?] Surprising assertion about make… Hesham Soliman