Re: [MEXT] Well-known problem with authentication/etc. in wirelessnetworks

"Charles E. Perkins" <charliep@computer.org> Fri, 26 August 2011 19:24 UTC

Return-Path: <charliep@computer.org>
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 4FF4421F8C9E for <mext@ietfa.amsl.com>; Fri, 26 Aug 2011 12:24:02 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rh3SXYKXqKyr for <mext@ietfa.amsl.com>; Fri, 26 Aug 2011 12:24:01 -0700 (PDT)
Received: from elasmtp-mealy.atl.sa.earthlink.net (elasmtp-mealy.atl.sa.earthlink.net [209.86.89.69]) by ietfa.amsl.com (Postfix) with ESMTP id 69FF021F8C8E for <mext@ietf.org>; Fri, 26 Aug 2011 12:24:01 -0700 (PDT)
Received: from [64.105.168.146] (helo=[10.1.100.70]) by elasmtp-mealy.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <charliep@computer.org>) id 1Qx21l-0007Cy-8k; Fri, 26 Aug 2011 15:25:17 -0400
Message-ID: <4E57F317.8080900@computer.org>
Date: Fri, 26 Aug 2011 12:25:11 -0700
From: "Charles E. Perkins" <charliep@computer.org>
Organization: Wichorus Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: Basavaraj.Patil@nokia.com
References: <CA7D5704.FADF%basavaraj.patil@nokia.com>
In-Reply-To: <CA7D5704.FADF%basavaraj.patil@nokia.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956d5d4673fe7faad86239f482120826744fb4bc95835ecae31350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 64.105.168.146
Cc: mext@ietf.org
Subject: Re: [MEXT] Well-known problem with authentication/etc. in wirelessnetworks
X-BeenThere: mext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: charliep@computer.org
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, 26 Aug 2011 19:24:02 -0000

Hello Basavaraj,

Thanks for your correction/clarification.

Yes, I agree that in certain cases LTE can
do very fast handovers, of course, given the
installation of sufficiently high-performance
hardware to handle the additional signaling
requirement as designed for the special cases,
or homogeneous physical media.  And,
eventually, they could do fast handovers
for all physical media, with perhaps m*n^^2
hardware solutions for m applications and
n physical media.

I think that we could reasonably expect to
do better handovers in almost all cases
with a more flexible design based on Mobile IP,
FMIP, and PMIP.

I also agree that handovers are hampered by
authentication requirements serialized after
link establishment.  Pre-registration techniques
have been shown to ameliorate this problem
quite well even with "single-radio" handset
operation.  This "should" have been integrated
with FMIP, in my opinion.

Regards,
Charlie P.



On 8/26/2011 12:01 PM, Basavaraj.Patil@nokia.com wrote:
>
> Hi Charlie,
>
> On 8/26/11 1:38 PM, "ext Charles E. Perkins"<charliep@computer.org>  wrote:
>>
>>>> Thus I am still not sure what the problem is.
>>
>>
>> The problem is that they can't do very effective handovers.
>> Worse, they are designing _per-application_ handover systems.
>> This is wrong by most reasonable engineering standards,
>> regardless on the positive effect it might have for
>> standards junkies and permanent employment for engineers.
>
> Effective handovers between what networks? Handovers within the scope of
> an HSPA or LTE access for example work fine.
> If you are referring to handovers between 3G accesses and wifi (non-3GPP
> access) then yes.
> But the handover performance in such a scenario is hampered by other
> factors such as latency in connectivity and authentication etc.
>
> -Basavaraj
>
>
>>
>>
>>> There's probably very little impetus for change no matter what MEXT
>>> does.
>>
>>
>> I agree that, if [mext] does nothing,
>> there won't be much impetus for change.
>> But if we do something that is (a) secure,
>> (b) deployable, (c) easier to administer,
>> and (d) considerably better performance,
>> then I reckon they'd have to be purposefully
>> resistant to insist on ignoring it.
>>
>> Regards,
>> Charlie P.
>>
>> _______________________________________________
>> MEXT mailing list
>> MEXT@ietf.org
>> https://www.ietf.org/mailman/listinfo/mext
>
> _______________________________________________
> MEXT mailing list
> MEXT@ietf.org
> https://www.ietf.org/mailman/listinfo/mext
>