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

Pete McCann <mccap@petoni.org> Fri, 26 August 2011 02:22 UTC

Return-Path: <mccap@petoni.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 18E2321F8586 for <mext@ietfa.amsl.com>; Thu, 25 Aug 2011 19:22:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level:
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
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 FbsaABF4OWri for <mext@ietfa.amsl.com>; Thu, 25 Aug 2011 19:22:32 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id A8E0C21F8500 for <mext@ietf.org>; Thu, 25 Aug 2011 19:22:31 -0700 (PDT)
Received: by fxe6 with SMTP id 6so2416203fxe.31 for <mext@ietf.org>; Thu, 25 Aug 2011 19:23:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=petoni.org; s=google; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=MD/HVOdvSn6F53VSnQpY2kh38LbtWVvJhHuP8LsDvyA=; b=bpfGO8lxIgqPoIDEP349j1eZRfDijCEK/1ngZnYKISlOaYpOzyYvJ63fpfOgXGT92r UwWKFoeNcum3hhSlcmBE0Y1eVxjHBkn6xjpJl7/3ab4z/AXtbM9/No6pg2RJdeIJfTh4 EnGWswPPIloEuUNiF8c3lkP8mQnc8JyqWpu1E=
MIME-Version: 1.0
Received: by 10.223.22.150 with SMTP id n22mr725452fab.110.1314325425925; Thu, 25 Aug 2011 19:23:45 -0700 (PDT)
Received: by 10.223.144.143 with HTTP; Thu, 25 Aug 2011 19:23:45 -0700 (PDT)
X-Originating-IP: [68.45.157.93]
In-Reply-To: <CAE_dhju-brMYdhNx7Zf5uwsu_1hnhYcxj6Y0k2+A82WybTmGsg@mail.gmail.com>
References: <4E554BAA.9080409@computer.org> <CAE_dhjtz5ue1noQwzb5gcCFa1gq_4EY-hxMhQRL07JAQNZq3bg@mail.gmail.com> <CACvMsLEgYZ+z05x9O978OuRG+fn=EqspPxjiBfV5VB2UvS0wWg@mail.gmail.com> <CAE_dhjuvZeywp+pN+gRh4hhZg_azq1RPa3hT0FVb=HDMwvECNQ@mail.gmail.com> <CACvMsLHqx68uKn5q1jZMcehERatAUuMu1xJ8B5N2zOSDSY0qTA@mail.gmail.com> <CAE_dhju-brMYdhNx7Zf5uwsu_1hnhYcxj6Y0k2+A82WybTmGsg@mail.gmail.com>
Date: Thu, 25 Aug 2011 22:23:45 -0400
Message-ID: <CACvMsLFJEfrw71SbOMJvCCiaU7rHNMBDsdbAfxqORPraNDw64A@mail.gmail.com>
From: Pete McCann <mccap@petoni.org>
To: Julien Laganier <julien.ietf@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: charliep@computer.org, mext <mext@ietf.org>
Subject: Re: [MEXT] Well-known problem with authentication/etc. in wireless networks
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 02:22:33 -0000

Hi, Julien,

On Thu, Aug 25, 2011 at 6:39 PM, Julien Laganier <julien.ietf@gmail.com> wrote:
>
> In the context of this discussion, optimizing Mobile IPv6 handover
> speed seems to imply that slowness of those is the root cause of that
> lack of MIPv6 deployment, which I don' t think is the case. On the
> other hand, coupling network access authentication with mobility
> management would arguably reduces deployment flexibility and thus harm
> rather than help potential MIPv6 deployments.

You're right that performance is probably not why 3GPP went the
way they did.  I think there were a variety of motivations that boil
down to a desire on the part of operators to control the handling
of UE traffic, mainly by routing it back through policy enforcement
points.  They built a network-based mobility management scheme
that borrowed very little from Mobile IP.

There was also a legacy authentication infrastructure built around
AKA that they wanted to re-use.  They didn't build algorithm agility
into their UE authentication protocol.  One could argue that in an
LTE network the mobility is very much tied to the access authentication,
and it's one reason why MIPv6 has missed the boat here.

> Thus I am still not sure what the problem is.

There's probably very little impetus for change no matter what MEXT
does.

-Pete