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

Behcet Sarikaya <sarikaya2012@gmail.com> Fri, 04 November 2011 16:18 UTC

Return-Path: <sarikaya2012@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 1BB4821F8C34 for <mext@ietfa.amsl.com>; Fri, 4 Nov 2011 09:18:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.431
X-Spam-Level:
X-Spam-Status: No, score=-3.431 tagged_above=-999 required=5 tests=[AWL=0.167, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 Yy9B1gutwCLF for <mext@ietfa.amsl.com>; Fri, 4 Nov 2011 09:18:09 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 1694621F8C1E for <mext@ietf.org>; Fri, 4 Nov 2011 09:18:09 -0700 (PDT)
Received: by ggnv1 with SMTP id v1so3042265ggn.31 for <mext@ietf.org>; Fri, 04 Nov 2011 09:18:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=A1DMUbOxyuDo9ivVUrpPpNPx+NlIBSsqP3GSHaKtyJs=; b=YInjJvuRtArAqD93Y9TRlq0mAYzi7MQnq7ITbxyTc334NAMINkNqE7tSd6CdIG8vu4 g3R//DkR0ucaxWnbScfUEC0KOefVlq20Gz58P4hkgfh5Bx1Khu1UliV4Kn/eBy9OfwfE u1og6O2OkCygI0HGnvqaxIIjgGGdqw+U+ynNo=
MIME-Version: 1.0
Received: by 10.236.192.233 with SMTP id i69mr21705751yhn.60.1320423488551; Fri, 04 Nov 2011 09:18:08 -0700 (PDT)
Received: by 10.236.108.135 with HTTP; Fri, 4 Nov 2011 09:18:08 -0700 (PDT)
In-Reply-To: <1672201A-C652-4204-99D9-3DE4D23D2BB2@gmail.com>
References: <4EB2D421.4030905@earthlink.net> <CAD9800F.1D0F9%hesham@elevatemobile.com> <CACvMsLG496pFVaVM0aJzt9W+=kwAwJjMNru4OO45aK66iDhhgw@mail.gmail.com> <1672201A-C652-4204-99D9-3DE4D23D2BB2@gmail.com>
Date: Fri, 04 Nov 2011 11:18:08 -0500
Message-ID: <CAC8QAcc85DKuerWsZC9S_C7bUzhdgSr9Z5yMFNngjtTcaoZv+g@mail.gmail.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: jouni korhonen <jouni.nospam@gmail.com>
Content-Type: multipart/alternative; boundary="20cf3056431ffcfb2604b0eb0c9f"
Cc: Pete McCann <mccap@petoni.org>, mext@ietf.org, Jari Arkko <jari.arkko@piuha.net>, jouni.korhonen@nsn.com
Subject: Re: [MEXT] the future of the MEXT working group
X-BeenThere: mext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: sarikaya@ieee.org
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, 04 Nov 2011 16:18:10 -0000

Hi all,

I am confused about all these very high level, intelligent looking
comments, and I must say I am fed up with them :-).

Non-tunneled communications is already there in DMM. You connect to the
nearest HA and all new communications is non-tunneled.

Do we agree that we should differentiate client-based and network based
protocols and discuss them in different places? or even there is no issue
for one.

I think this is what we should decide now.

Regards,

Behcet

On Fri, Nov 4, 2011 at 3:19 AM, jouni korhonen <jouni.nospam@gmail.com>wrote:

> Pete,
>
> On Nov 4, 2011, at 3:16 AM, Pete McCann wrote:
>
> > A good architecture is made not only from deciding what to standardize
> but
> > also from what not to standardize.
>
> Exactly.
>
> [snip]
>
> >
> > Perhaps IETF could take LIPA as a starting point to design a cleaner
> > mobility management solution.
>
> What came out from a certain SDO as a "Local IP Access" did not turn out
> as the most elegant solution :) But I do agree that from the idea & initial
> use case point of view, it definitely is something to look at.. even as a
> basis for a cleaner design.
>
> > It isn't clear to me that we should even start with tunnels as a basic
> building
> > block.
>
> I am along the same lines. See my earlier mail on the charter
> http://www.ietf.org/mail-archive/web/mext/current/msg04905.html
>
> - Jouni
>
>
>
> >
> > -Pete
> >
> > On Thu, Nov 3, 2011 at 8:43 PM, Hesham Soliman <hesham@elevatemobile.com>
> wrote:
> >> Hi Charlie,
> >>
> >> I agree completely with you on the problems with the current interfaces
> in
> >> LTE, and in 3G before that.
> >> I don't know what the best way to go about it would be. I say this
> because
> >> many people on this list are aware of what's happening in LTE and
> >> presumably have similar opinions about the complexity of their
> solutions,
> >> but it's still there.
> >>
> >> Hesham
> >>
> >> -----Original Message-----
> >> From: "Charles E. Perkins" <charles.perkins@earthlink.net>
> >> Organization: Wichorus Inc.
> >> Date: Thu, 03 Nov 2011 10:49:21 -0700
> >> To: Jari Arkko <jari.arkko@piuha.net>
> >> Cc: <jouni.korhonen@nsn.com>, <mext@ietf.org>
> >> Subject: Re: [MEXT] the future of the MEXT working group
> >>
> >>> Hello folks,
> >>>
> >>> For several years now, I have been studying 4G wireless
>
> [snap]
>
>
>
> _______________________________________________
> MEXT mailing list
> MEXT@ietf.org
> https://www.ietf.org/mailman/listinfo/mext
>