Re: [MEXT] the future of the MEXT working group
"Charles E. Perkins" <charles.perkins@earthlink.net> Thu, 10 November 2011 21:42 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 908C521F8484 for <mext@ietfa.amsl.com>;
Thu, 10 Nov 2011 13:42:25 -0800 (PST)
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=[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 pTPb5l0U81oT for
<mext@ietfa.amsl.com>; Thu, 10 Nov 2011 13:42:25 -0800 (PST)
Received: from elasmtp-mealy.atl.sa.earthlink.net
(elasmtp-mealy.atl.sa.earthlink.net [209.86.89.69]) by ietfa.amsl.com
(Postfix) with ESMTP id 1FD4C21F8486 for <mext@ietf.org>;
Thu, 10 Nov 2011 13:42:25 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net;
b=hb1UmzZLr081F58NT8UXTN8OWTJI9prp0l+SB34AJl8diafH7mvvQ2Cjd8bGkV+0;
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 [123.124.244.146] by elasmtp-mealy.atl.sa.earthlink.net with
esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from
<charles.perkins@earthlink.net>) id 1ROcO5-0004Qe-Jn;
Thu, 10 Nov 2011 16:42:22 -0500
Message-ID: <4EBC4537.7050501@earthlink.net>
Date: Thu, 10 Nov 2011 13:42:15 -0800
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: Hidetoshi Yokota <yokota@kddilabs.jp>
References: <CAD9800F.1D0F9%hesham@elevatemobile.com><350CD199-C70E-491B-B81D-AFE1D3F95C05@nokia.com><4EB41DC5.1010409@earthlink.net><DF856C56-8BA2-4DCD-9CBB-BC02A3B9FCD0@nokia.com><CACvMsLE4fGeXdvRPkJvW2OZDXD8FKtjd58v0QjA39y4a7xo9Fw@mail.gmail.com>
<4EBBC682.7070101@kddilabs.jp>
In-Reply-To: <4EBBC682.7070101@kddilabs.jp>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956d5d4673fe7faad868c4c8bd301d7b413b56f14bab15e6d82350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 123.124.244.146
Cc: 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, 10 Nov 2011 21:42:25 -0000
Hello Hidetoshi, On 11/10/2011 4:41 AM, Hidetoshi Yokota wrote: > Hi, > > I think that the point is to give a choice to the network and user if > mobility is needed or not. Some applications benefit from seamless > mobility (e.g., VoIP), but others may not (e.g., Web access). The > network and user should be able to specify the capability of mobility > and appropriate access network for each application. In that sense, > Dynamic MM is an interesting feature. I pretty much agree with this; I expect that working out the details will be pretty tedious and perhaps even contentious. > I agree that the current 3GPP architecture is very complicated and may > not be optimal, but I don't think it is a good idea to change it in IETF... I agree we can't "change" 3GPP architecture in the IETF, but we can respond to the needs which are evident from considering the 3GPP architecture. It seems very few believe that LTE is really immune from further evolution and even significant change in the future. If IETF does NOT respond to the needs made evident in current 3GPP specifications, we have little hope of proper integration into their future evolved designs. Regards, Charlie P.
- [MEXT] the future of the MEXT working group Jari Arkko
- Re: [MEXT] the future of the MEXT working group Jari Arkko
- Re: [MEXT] the future of the MEXT working group Behcet Sarikaya
- Re: [MEXT] the future of the MEXT working group Hui Deng
- Re: [MEXT] the future of the MEXT working group Hesham Soliman
- Re: [MEXT] the future of the MEXT working group Basavaraj.Patil
- Re: [MEXT] the future of the MEXT working group Hui Deng
- Re: [MEXT] the future of the MEXT working group Ryuji Wakikawa
- Re: [MEXT] the future of the MEXT working group Basavaraj.Patil
- Re: [MEXT] the future of the MEXT working group Jari Arkko
- Re: [MEXT] the future of the MEXT working group Julien Laganier
- Re: [MEXT] the future of the MEXT working group Basavaraj.Patil
- Re: [MEXT] the future of the MEXT working group Jari Arkko
- Re: [MEXT] the future of the MEXT working group Basavaraj.Patil
- Re: [MEXT] the future of the MEXT working group Behcet Sarikaya
- Re: [MEXT] the future of the MEXT working group Ryuji Wakikawa
- Re: [MEXT] the future of the MEXT working group pierrick.seite
- Re: [MEXT] the future of the MEXT working group Charles E. Perkins
- Re: [MEXT] the future of the MEXT working group Thierry Ernst
- Re: [MEXT] the future of the MEXT working group jouni korhonen
- Re: [MEXT] the future of the MEXT working group Charles E. Perkins
- Re: [MEXT] the future of the MEXT working group Basavaraj.Patil
- Re: [MEXT] the future of the MEXT working group jouni korhonen
- Re: [MEXT] the future of the MEXT working group Hesham Soliman
- Re: [MEXT] the future of the MEXT working group Pete McCann
- Re: [MEXT] the future of the MEXT working group jouni korhonen
- Re: [MEXT] the future of the MEXT working group pierrick.seite
- Re: [MEXT] the future of the MEXT working group jouni korhonen
- Re: [MEXT] the future of the MEXT working group pierrick.seite
- Re: [MEXT] the future of the MEXT working group Basavaraj.Patil
- Re: [MEXT] the future of the MEXT working group Behcet Sarikaya
- Re: [MEXT] the future of the MEXT working group liu dapeng
- Re: [MEXT] the future of the MEXT working group Charles E. Perkins
- Re: [MEXT] the future of the MEXT working group Charles E. Perkins
- Re: [MEXT] the future of the MEXT working group Charles E. Perkins
- Re: [MEXT] the future of the MEXT working group Basavaraj.Patil
- Re: [MEXT] the future of the MEXT working group Hesham Soliman
- Re: [MEXT] the future of the MEXT working group Pete McCann
- Re: [MEXT] the future of the MEXT working group jouni korhonen
- Re: [MEXT] automotive reqs WG item (was: the futu… Alexandru Petrescu
- Re: [MEXT] automotive reqs WG item Thierry Ernst
- Re: [MEXT] automotive reqs WG item Alexandru Petrescu
- Re: [MEXT] the future of the MEXT working group pierrick.seite
- Re: [MEXT] automotive reqs WG item karagian
- Re: [MEXT] automotive reqs WG item Dirk.von-Hugo
- Re: [MEXT] automotive reqs WG item Basavaraj.Patil
- Re: [MEXT] automotive reqs WG item Charles E. Perkins
- Re: [MEXT] the future of the MEXT working group Hidetoshi Yokota
- Re: [MEXT] the future of the MEXT working group Charles E. Perkins
- Re: [MEXT] the future of the MEXT working group Hidetoshi Yokota
- Re: [MEXT] the future of the MEXT working group Hesham Soliman
- Re: [MEXT] the future of the MEXT working group liu dapeng
- Re: [MEXT] the future of the MEXT working group liu dapeng
- Re: [MEXT] the future of the MEXT working group jouni korhonen
- Re: [MEXT] the future of the MEXT working group h chan