Re: [MEXT] doubting a 3GPP MIP, because requires SIM, BS, spectrum, code (was: Well-known problem with authentication/etc. in wireless networks)
Alexandru Petrescu <alexandru.petrescu@gmail.com> Sat, 27 August 2011 17:16 UTC
Return-Path: <alexandru.petrescu@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 0112521F86AA for <mext@ietfa.amsl.com>;
Sat, 27 Aug 2011 10:16:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.121
X-Spam-Level:
X-Spam-Status: No, score=-0.121 tagged_above=-999 required=5 tests=[AWL=0.050,
BAYES_00=-2.599, FH_RELAY_NODNS=1.451, RCVD_IN_SORBS_DUL=0.877, RDNS_NONE=0.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 dODF6LF-zJE8 for
<mext@ietfa.amsl.com>; Sat, 27 Aug 2011 10:16:20 -0700 (PDT)
Received: from smtp1-g21.free.fr (unknown [IPv6:2a01:e0c:1:1599::10]) by
ietfa.amsl.com (Postfix) with ESMTP id 480D421F85C6 for <mext@ietf.org>;
Sat, 27 Aug 2011 10:16:18 -0700 (PDT)
Received: from [127.0.0.1] (unknown [82.239.213.32]) by smtp1-g21.free.fr
(Postfix) with ESMTP id C796994011A for <mext@ietf.org>;
Sat, 27 Aug 2011 19:17:32 +0200 (CEST)
Message-ID: <4E5926A4.4030709@gmail.com>
Date: Sat, 27 Aug 2011 19:17:24 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: mext@ietf.org
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>
In-Reply-To: <CACvMsLHqx68uKn5q1jZMcehERatAUuMu1xJ8B5N2zOSDSY0qTA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Antivirus: avast! (VPS 110827-0, 27/08/2011), Outbound message
X-Antivirus-Status: Clean
Subject: Re: [MEXT] doubting a 3GPP MIP, because requires SIM, BS, spectrum,
code (was: 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: Sat, 27 Aug 2011 17:16:21 -0000
Le 26/08/2011 00:12, Pete McCann a écrit : > 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. I read that so too. I have a side note. I have a big doubt about making Mobile IP at IETF more attractive to 3GPP, be that in the security domain (EAP, access control) or any other. Specifying IETF protocol is often backed by significant implementation effort. And it is hard to do implementation effort when prerequisite tools are: (0) licensed spectrum, (1) a SIM card paid subscription, (2) a real 3GPP Base Station and (3) operator's source code, compared to implementation effort using cheap WiFi equipment, cheap-free open source code and unlicensed spectrum. I fail to see how a better MIP could be designed for 3GPP if a large number of implementers don't have access to these tools. Or maybe speculating, logically extending, behaviour on WiFi to 3GPP - once again. That is why I doubt an effort to make Mobile IP more attractive to 3GPP could happen at IETF. (this is not to say MIP is not good for mobility - it is very good when handing over from 3GPP link to e.g. WiFi, from one operator to another). (also, at various points in time I personally did have access to these tools but no intention could there be to talk at IETF about the inner workings of these tools, nor to modify them). Alex > >>> 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. > > -Pete _______________________________________________ MEXT mailing > list MEXT@ietf.org https://www.ietf.org/mailman/listinfo/mext >
- [MEXT] Well-known problem with authentication/etc… Charles E. Perkins
- Re: [MEXT] Well-known problem with authentication… Alper Yegin
- Re: [MEXT] Well-known problem with authentication… Charles E. Perkins
- Re: [MEXT] Well-known problem with authentication… Julien Laganier
- Re: [MEXT] Well-known problem with authentication… Pete McCann
- Re: [MEXT] [!! SPAM] Re: Well-known problem with … Charles E. Perkins
- Re: [MEXT] [!! SPAM] Re: Well-known problem with … Alper Yegin
- Re: [MEXT] [!! SPAM] Re: Well-known problem with … Pete McCann
- Re: [MEXT] [!! SPAM] Re: Well-known problem with … Basavaraj.Patil
- Re: [MEXT] [!! SPAM] Re: Well-known problem with … Pete McCann
- Re: [MEXT] [!! SPAM] Re: Well-known problem with … Charles E. Perkins
- Re: [MEXT] [!! SPAM] Re: Well-known problem with … Jong-Hyouk Lee
- Re: [MEXT] Well-known problem with authentication… Basavaraj.Patil
- Re: [MEXT] Well-known problem with authentication… Basavaraj.Patil
- Re: [MEXT] [!! SPAM] Re: Well-known problem with … Basavaraj.Patil
- Re: [MEXT] [!! SPAM] Re: Well-known problem with … Pete McCann
- Re: [MEXT] Well-known problem with authentication… Julien Laganier
- Re: [MEXT] Well-known problem with authentication… Pete McCann
- Re: [MEXT] Well-known problem with authentication… Julien Laganier
- Re: [MEXT] Well-known problem with authentication… Pete McCann
- Re: [MEXT] [!! SPAM] Re: Well-known problem with … Charles E. Perkins
- Re: [MEXT] Well-known problem with authentication… Basavaraj.Patil
- Re: [MEXT] Well-known problem with authentication… Charles E. Perkins
- Re: [MEXT] Well-known problem with authentication… Julien Laganier
- Re: [MEXT] Well-known problem with authentication… Basavaraj.Patil
- Re: [MEXT] Well-known problem with authentication… Julien Laganier
- Re: [MEXT] Well-known problem with authentication… Charles E. Perkins
- Re: [MEXT] Well-known problem with authentication… Basavaraj.Patil
- Re: [MEXT] Well-known problem with authentication… Julien Laganier
- Re: [MEXT] Well-known problem with authentication… Hesham Soliman
- Re: [MEXT] doubting a 3GPP MIP, because requires … Alexandru Petrescu
- Re: [MEXT] [!! SPAM] Re: Well-known problem with … Charles E. Perkins
- Re: [MEXT] [!! SPAM] Re: Well-known problem with … Charles E. Perkins
- Re: [MEXT] [!! SPAM] Re: Well-known problem with … Behcet Sarikaya
- Re: [MEXT] [!! SPAM] Re: Well-known problem witha… Charles E. Perkins
- Re: [MEXT] [!! SPAM] Re: Well-known problem with … Julien Laganier
- Re: [MEXT] [!! SPAM] Re: Well-known problem with … Pete McCann