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

Hesham Soliman <hesham@elevatemobile.com> Fri, 05 August 2011 10:16 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 94A7721F8ACE for <mext@ietfa.amsl.com>; Fri, 5 Aug 2011 03:16:44 -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=[AWL=0.000, 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 mqFiI7Tu8qUv for <mext@ietfa.amsl.com>; Fri, 5 Aug 2011 03:16:40 -0700 (PDT)
Received: from smtp-1.servers.netregistry.net (smtp.netregistry.net [202.124.241.204]) by ietfa.amsl.com (Postfix) with ESMTP id AE40421F89B8 for <mext@ietf.org>; Fri, 5 Aug 2011 03:16:36 -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 1QpHRk-0006lE-DR; Fri, 05 Aug 2011 20:16:04 +1000
User-Agent: Microsoft-MacOutlook/14.12.0.110505
Date: Fri, 05 Aug 2011 20:16:00 +1000
From: Hesham Soliman <hesham@elevatemobile.com>
To: "Charles E. Perkins" <charles.perkins@earthlink.net>
Message-ID: <CA61FCD6.1842B%hesham@elevatemobile.com>
Thread-Topic: [MEXT] [dmm?] Surprising assertion about make-before-break ...
In-Reply-To: <4E3B99E4.2050603@earthlink.net>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Authenticated-User: hesham@elevatemobile.com
Cc: mext@ietf.org
Subject: Re: [MEXT] [dmm?] Surprising assertion about make-before-break ...
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 10:16:44 -0000

Hi Charlie,


>
>Hello Hesham,
>
>Long time no see...

=> Likewise! 

>To your point:
>
>On 8/4/2011 10:11 PM, Hesham Soliman wrote:
>
>> On the battery issue, yes of course but a few years ago those smart
>>phones
>> needed to be charged every few hours, now they improved. My laptop
>>battery
>> lasts 5-6 hours, which is an improvement. So these things change over
>> time.
>
>Assume, just for a moment, there were a handover method requiring
>only a single radio interface to be powered up at any one time, that
>had roughly equal performance as handover algorithms which relied on
>multiple radio interfaces being powered up.
>
>In that case, I think it would be considerably preferable to
>make use of the single-radio algorithm.

=> Sure. I think we got two topics wrapped up in the same thread, I was
referring to multiple radio interfaces using different technologies. But I
agree with you that you can get good performance without make before break
handover. 

>
>Excellent performance with single-radio devices is quite possible,
>and we would practically already be there except for politics or,
>(less likely but plausible) simply a matter of inertia.  Certainly
>possible for good VoIP, almost certainly for interactive video on
>4G networks <--> WLAN.  We were showing smooth VoIP handovers
>almost ten years ago with 802.11b, and with SFF-based preregistration
>in 4G networks we could do far better than that now (I recently
>submitted a draft about this).

=> Absolutely, I've done similar experiments on WLAN and still do in fact
and I agree. And did the same with 3G and you're right, it's all politics
that's stopping this. Luckily for me I'm not in the middle of these
politics anymore :)

>
>How to get it standardized in LTE seems to be a puzzle of monumental
>proportions.  Perhaps if the end users realized how much better
>their service could be, and started demanding it, things would
>progress.  In the meantime, they'll get slow, battery-wasting
>handovers to WLAN that do not even preserve IP addresses, much
>less offer session continuity.  And the operators will have to
>purchase unbelievably complicated equipment to even enable that
>level of service.

=> Forget about average users demanding proper IP networks, some operators
tried that and failed. Unfortunately the "getting it into LTE" part is not
fun. The fun part is making it work and the rest is...well you know. But
it might be worth giving LTE a unified IETF solution for mobility instead
of re-dressing GTP in IP (PMIP) and then getting it rejected anyway. I
didn't like that approach, but that was a long time ago.


>
>I'd like to see the IETF start offering solutions that
>have an easier evolutionary path towards deployment.
>http://www.psg.com/~charliep/txt/ietf81/alt_mext/MIPv6_for_4G.pptx

=> Nice plug :), but I don't see the relation to the single Vs multiple
radio discussion.

Hesham

>
>[note I renamed that file, there was a typo in the previous name]
>
>Regards,
>Charlie P.