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

liu dapeng <maxpassion@gmail.com> Sun, 13 November 2011 09:56 UTC

Return-Path: <maxpassion@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 6348D21F8468 for <mext@ietfa.amsl.com>; Sun, 13 Nov 2011 01:56:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.56
X-Spam-Level:
X-Spam-Status: No, score=-3.56 tagged_above=-999 required=5 tests=[AWL=0.039, 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 XRyMqAzRIgw1 for <mext@ietfa.amsl.com>; Sun, 13 Nov 2011 01:56:50 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id CECFF21F8467 for <mext@ietf.org>; Sun, 13 Nov 2011 01:56:50 -0800 (PST)
Received: by iaeo4 with SMTP id o4so7775335iae.31 for <mext@ietf.org>; Sun, 13 Nov 2011 01:56:51 -0800 (PST)
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; bh=SK1EjnKmnrRbW62p1+50SUrt56kfhtMd+C4c41CtcRQ=; b=dRZ4RRVTj4UB8rCspDQpUFDld/jWnwWFc/bsbEA4cbd1ppSMgo6Wg6i5gJPBS6emuw YU/sTDvXQ+5hPtsfF2hBdfxb6JTyninYcMqArcKSpJ9aSD7zps1RwslyzLQBU9frc2fV Jyr80rd9E00W3Kg1bgNu1IHV1UQJjGb51ljWs=
MIME-Version: 1.0
Received: by 10.42.117.193 with SMTP id u1mr18981872icq.24.1321178210950; Sun, 13 Nov 2011 01:56:50 -0800 (PST)
Received: by 10.42.228.68 with HTTP; Sun, 13 Nov 2011 01:56:50 -0800 (PST)
In-Reply-To: <4EBC7681.8010203@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> <4EBC4537.7050501@earthlink.net> <4EBC7681.8010203@kddilabs.jp>
Date: Sun, 13 Nov 2011 17:56:50 +0800
Message-ID: <CAKcc6Adk+7oKW1Ljvtn4uVxALzteGFfdRwcauAuBLYJWQ+Bk+g@mail.gmail.com>
From: liu dapeng <maxpassion@gmail.com>
To: Hidetoshi Yokota <yokota@kddilabs.jp>
Content-Type: text/plain; charset="ISO-8859-1"
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: Sun, 13 Nov 2011 09:56:51 -0000

2011/11/11, Hidetoshi Yokota <yokota@kddilabs.jp>:
> Hi Charlie,
>
> (2011/11/11 6:42), Charles E. Perkins wrote:
>>
>> 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.
>
> I fully agree with your point and am glad you initiated this discussion.
> One of the reasons for its complicatedness is that the 3GPP architecture
> has been incrementally built considering all the backward compatibility
> and interoperability along with introducing new features and minimizing
> the unhappiness of all. I respect this effort and achievement we all
> enjoy today. On the other hand, the current mobile traffic is way too
> much for this architecture to be able to handle. If IETF can contribute
> to tackling this issue toward the future evolved design, it will be very
> valuable. I don't know if DMM is the start point or we need a new WG,
> but we still have a high mountain to climb.

I fully aggree with this point. The mobile operators faces the presure
of  rapidly traffic increasing. We should consider this point when we
try to optimize mobility protocols.

regards,
Dapeng

> Regards,
> --
> Hidetoshi
>
>> Regards,
>> Charlie P.
>>
>>
>>
>
>
> _______________________________________________
> MEXT mailing list
> MEXT@ietf.org
> https://www.ietf.org/mailman/listinfo/mext
>


-- 

------
Best Regards,
Dapeng Liu