IETF Logo Mail Archive

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

Hesham Soliman <hesham@elevatemobile.com> Fri, 11 November 2011 02:29 UTC

Return-Path: <hesham@elevatemobile.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 D26B411E808F for <mext@ietfa.amsl.com>; Thu, 10 Nov 2011 18:29:38 -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 Xhyp+UWnA72o for <mext@ietfa.amsl.com>; Thu, 10 Nov 2011 18:29:38 -0800 (PST)
Received: from smtp-1.servers.netregistry.net (smtp.netregistry.net [202.124.241.204]) by ietfa.amsl.com (Postfix) with ESMTP id 50B7B11E8080 for <mext@ietf.org>; Thu, 10 Nov 2011 18:29:37 -0800 (PST)
Received: from [120.146.201.23] (helo=[10.0.0.24]) by smtp-1.servers.netregistry.net protocol: esmtpa (Exim 4.69 #1 (Debian)) id 1ROgrf-00056x-0s; Fri, 11 Nov 2011 13:29:11 +1100
User-Agent: Microsoft-MacOutlook/14.13.0.110805
Date: Fri, 11 Nov 2011 13:28:55 +1100
From: Hesham Soliman <hesham@elevatemobile.com>
To: "Charles E. Perkins" <charles.perkins@earthlink.net>, Hidetoshi Yokota <yokota@kddilabs.jp>
Message-ID: <CAE2D2B7.1D6CE%hesham@elevatemobile.com>
Thread-Topic: [MEXT] the future of the MEXT working group
In-Reply-To: <4EBC4537.7050501@earthlink.net>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Authenticated-User: hesham@elevatemobile.com
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: Fri, 11 Nov 2011 02:29:38 -0000

Hi Charlie, 

>>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 think we should all learn from the RFC 3314 experience where IETF
(IPv6 WG at the time) made clear recommendations to 3GPP about address
configuration and all the recommendations were adopted in the same
release. I know these are smaller recommendations but this happens all the
time and we shouldn't worry about achieving things before trying to get a
unified view and presenting it. RFC 3316 is another example, although it
was more of a consensus-based approach between the two organisations

Hesham

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

v2.23.0 | Report a Bug | By Email