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

<Basavaraj.Patil@nokia.com> Fri, 26 August 2011 19:00 UTC

Return-Path: <Basavaraj.Patil@nokia.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 7281221F8C56 for <mext@ietfa.amsl.com>; Fri, 26 Aug 2011 12:00:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.597
X-Spam-Level:
X-Spam-Status: No, score=-102.597 tagged_above=-999 required=5 tests=[AWL=0.002, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 yiQXJUJJRH+J for <mext@ietfa.amsl.com>; Fri, 26 Aug 2011 12:00:15 -0700 (PDT)
Received: from mgw-sa01.nokia.com (smtp.nokia.com [147.243.1.47]) by ietfa.amsl.com (Postfix) with ESMTP id 91D7A21F8C3A for <mext@ietf.org>; Fri, 26 Aug 2011 12:00:14 -0700 (PDT)
Received: from vaebh102.NOE.Nokia.com (vaebh102.europe.nokia.com [10.160.244.23]) by mgw-sa01.nokia.com (Switch-3.4.4/Switch-3.4.3) with ESMTP id p7QJ1Q02020350; Fri, 26 Aug 2011 22:01:27 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.8]) by vaebh102.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Fri, 26 Aug 2011 22:01:26 +0300
Received: from 008-AM1MMR1-005.mgdnok.nokia.com (65.54.30.60) by NOK-AM1MHUB-04.mgdnok.nokia.com (65.54.30.8) with Microsoft SMTP Server (TLS) id 8.2.255.0; Fri, 26 Aug 2011 21:01:26 +0200
Received: from 008-AM1MPN1-051.mgdnok.nokia.com ([169.254.1.86]) by 008-AM1MMR1-005.mgdnok.nokia.com ([65.54.30.60]) with mapi id 14.01.0323.007; Fri, 26 Aug 2011 21:01:25 +0200
From: <Basavaraj.Patil@nokia.com>
To: <charliep@computer.org>, <mccap@petoni.org>
Thread-Topic: [MEXT] Re: Well-known problem with authentication/etc. in wirelessnetworks
Thread-Index: AQHMZCKNFDj0Wzp3c0CY7C8n0YRSkA==
Date: Fri, 26 Aug 2011 19:01:24 +0000
Message-ID: <CA7D5704.FADF%basavaraj.patil@nokia.com>
In-Reply-To: <4E57E814.4020607@computer.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.10.0.110310
x-originating-ip: [172.19.59.18]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <888D2843564A00439E95F9FA6D931DE8@nokia.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 26 Aug 2011 19:01:26.0729 (UTC) FILETIME=[8E610390:01CC6422]
X-Nokia-AV: Clean
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
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:00:16 -0000

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