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

Julien Laganier <julien.ietf@gmail.com> Thu, 25 August 2011 22:38 UTC

Return-Path: <julien.ietf@gmail.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 3A0AC21F8B84 for <mext@ietfa.amsl.com>; Thu, 25 Aug 2011 15:38:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.455
X-Spam-Level:
X-Spam-Status: No, score=-3.455 tagged_above=-999 required=5 tests=[AWL=0.144, BAYES_00=-2.599, 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 MrWJbYC28UAN for <mext@ietfa.amsl.com>; Thu, 25 Aug 2011 15:38:19 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 8102E21F8B82 for <mext@ietf.org>; Thu, 25 Aug 2011 15:38:19 -0700 (PDT)
Received: by wwf5 with SMTP id 5so1953880wwf.13 for <mext@ietf.org>; Thu, 25 Aug 2011 15:39:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=UYNFo/VnNUtfyor/+gDESrM6djY0tVyqQ3fAknj4eKg=; b=Iick9edyOFHcutGZzIml5cbtf6g9j6gGcYMarxGRQIZfxztl49ddd2IYl98qDrvi0A Ym3TCimkYCmqjSO3TFPHe/SIx/+u3zalaLiSpREPBN/foaYlcLS9A1iQQrM2kvkknHFV 4pEYbdydxZ/VyqYRQSS2Zge10RLD2ycdd/kCQ=
MIME-Version: 1.0
Received: by 10.227.11.141 with SMTP id t13mr260506wbt.36.1314311973361; Thu, 25 Aug 2011 15:39:33 -0700 (PDT)
Received: by 10.227.141.79 with HTTP; Thu, 25 Aug 2011 15:39:33 -0700 (PDT)
In-Reply-To: <CACvMsLHqx68uKn5q1jZMcehERatAUuMu1xJ8B5N2zOSDSY0qTA@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>
Date: Thu, 25 Aug 2011 15:39:33 -0700
Message-ID: <CAE_dhju-brMYdhNx7Zf5uwsu_1hnhYcxj6Y0k2+A82WybTmGsg@mail.gmail.com>
From: Julien Laganier <julien.ietf@gmail.com>
To: Pete McCann <mccap@petoni.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
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: Thu, 25 Aug 2011 22:38:20 -0000

Hi Pete,

On Thu, Aug 25, 2011 at 3:12 PM, Pete McCann <mccap@petoni.org> wrote:
> Hi, Julien,
>
> On Thu, Aug 25, 2011 at 5:02 PM, Julien Laganier <julien.ietf@gmail.com> wrote:
>> Yes, EAP authentication for IKEv2. Yes the MN needs to attach to the
>> network first, as hosts currently do today already.
>
> Right.  I think Charlie was asking whether MIP could be the network access
> authentication protocol.
>
>>> It may be interesting to look at whether access authentication and mobility
>>> management can be combined.
>>
>> I don' t know what problem we would be solving by combining the two.
>
> Making initial establishment of the SA with the HA (upon network attachment)
> more efficient. Making handovers faster and more efficient by reducing the
> number of round-trip messages required.

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.

Thus I am still not sure what the problem is.

--julien