Re: [MEXT] the future of the MEXT working group

"Charles E. Perkins" <charles.perkins@earthlink.net> Thu, 03 November 2011 17:49 UTC

Return-Path: <charles.perkins@earthlink.net>
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 E25441F0C76 for <mext@ietfa.amsl.com>; Thu, 3 Nov 2011 10:49:32 -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=[AWL=0.000, 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 r995E+TYAcUJ for <mext@ietfa.amsl.com>; Thu, 3 Nov 2011 10:49:32 -0700 (PDT)
Received: from elasmtp-banded.atl.sa.earthlink.net (elasmtp-banded.atl.sa.earthlink.net [209.86.89.70]) by ietfa.amsl.com (Postfix) with ESMTP id 027B21F0C40 for <mext@ietf.org>; Thu, 3 Nov 2011 10:49:32 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=dlzif6kPJyz00BkNWvDz3/rvtQ/Ow1gzAVNK2mzyLQLiTodEBRmy/VnYQtv+6TrK; h=Received:Message-ID:Date:From:Organization:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [138.111.58.2] (helo=[172.17.96.136]) by elasmtp-banded.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <charles.perkins@earthlink.net>) id 1RM1Pr-00007L-Qa; Thu, 03 Nov 2011 13:49:28 -0400
Message-ID: <4EB2D421.4030905@earthlink.net>
Date: Thu, 03 Nov 2011 10:49:21 -0700
From: "Charles E. Perkins" <charles.perkins@earthlink.net>
Organization: Wichorus Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
References: <4EAA9B4A.3020208@piuha.net>
In-Reply-To: <4EAA9B4A.3020208@piuha.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956d5d4673fe7faad86cccb02f4a65ae22eec64eb2da3c95900350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 138.111.58.2
Cc: jouni.korhonen@nsn.com, mext@ietf.org
Subject: Re: [MEXT] the future of the MEXT working group
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, 03 Nov 2011 17:49:33 -0000

Hello folks,

For several years now, I have been studying 4G wireless
network architecture and wondering why there is such a
disconnect between, say, LTE mobility management and
IETF mobility management.  Mobile IP has a secondary
role, to say the least.  IETF approaches may be seen to
have several inadequacies, and 3GPP approaches also show
some major problems.  I think that it is important for
the IETF to devote some serious effort towards bringing
these two worlds together, because current directions
are leading towards an impossibly baroque, wasteful,
nearly impenetrable mess of complication.  The effects
overall is loss of performance and opportunity.

Taking a look at S101 and S103, we can immediately
recognize that they are drastically more complicated,
restrictive, and operationally more expensive than
Mobile IP.  Taking a look at S102, we immediately see
that 3GPP mobility management threatens to be different
for each class of application, with an unnecessary
per-application proliferation of servers, protocol,
permissions, traffic controls, configuration, and so on.
Taking a look at recent efforts towards WiFi offload,
we see the same trend of complication and software
hacks that could be avoided with proper IETF
approaches.

On the IETF side, we should specify:
- Integrated authentication for access control
   as well as IP address continuity
- Location-assisted handovers (think MIIS / ANDSF)
- Modular/alternative security
- Signaling on control plane, user traffic on
   data plane
- Alternative tunneling (GTP is simply not going
   to die a quick death, to say the least)
- geez, the list does go on, but no one reads
   long lists ...
...

I don't know if we already have 3GPP liaison, but
if we do the communication channels don't seem to
have had very much effect within the [mext] work
lately.

My fear is that if we don't take action, we are
choosing a future that is ever more complicated,
non-extendible, non-flexible, radio technology
specific, application specific, and bug-ridden.
In short, everything we don't want the Internet
to be.  And, I am sure no one here doubts that
the Internet of the future is all high-speed
wireless.  Where is the IETF going to be?

If the [mext] working group is shut down, there
is no natural place for this work to happen.
Therefore, I hope that [mext] would NOT shut
down, and instead recharter to tackle these
urgent problems.

Regards,
Charlie P.



On 10/28/2011 5:08 AM, Jari Arkko wrote:
> All,
>
> We are making some changes to the working group. While we have
> successfully published a large number of specifications in recent years,
> recently it has been difficult to make progress in the group. The chairs
> and ADs have looked at the situation and we believe we need a new focus
> and a bit of new organization as well. We are terminating the working
> group and moving the one remaining active work item to a new working
> group, the "DMM" working group. Here's what is going to happen:
>
> o Jouni Korhonen and Julien Laganier will become the chairs of the group.
>
> o The group will meet in Taipei (there is a MEXT slot in the agenda).
>
> o The charter of the group will be changed to focus only on the
> distributed mobility effort. We should discuss the details of this
> charter change both on the list and in the meeting. The meeting agenda
> should reserve some time both for technical discussions as well as the
> charter discussion.
>
> o Once the discussion on the list and in the meeting has finished, we
> will rename the group to "DMM" and put the new charter in effect.
>
> o If there are any other specifications that people would like to
> publish beyond the distributed mobility work, we can offer to AD sponsor
> them to RFCs outside the new working group. If there is some significant
> new activity, we can create new working groups for that.
>
> Comments and feedback and/or alternate suggestions on this plan are
> welcome.
>
> We would like to thank Marcelo for your many years of service in MEXT.
> We could not have completed all the work we did without your energy and
> push for high quality results. We would also like to thank Jouni for
> taking on this new challenge, and Julien for continuing the work in this
> space.
>
> Jari and Ralph
>
> _______________________________________________
> MEXT mailing list
> MEXT@ietf.org
> https://www.ietf.org/mailman/listinfo/mext
>