IETF Logo Mail Archive

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

<pierrick.seite@orange.com> Mon, 07 November 2011 14:53 UTC

Return-Path: <pierrick.seite@orange.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 C8C8821F8B70 for <mext@ietfa.amsl.com>; Mon, 7 Nov 2011 06:53:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.091
X-Spam-Level:
X-Spam-Status: No, score=-2.091 tagged_above=-999 required=5 tests=[AWL=0.158, BAYES_00=-2.599, HELO_EQ_FR=0.35]
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 PsQYsOHRvzoh for <mext@ietfa.amsl.com>; Mon, 7 Nov 2011 06:53:24 -0800 (PST)
Received: from r-mail2.rd.francetelecom.com (r-mail2.rd.francetelecom.com [217.108.152.42]) by ietfa.amsl.com (Postfix) with ESMTP id 4D0D021F8B6F for <mext@ietf.org>; Mon, 7 Nov 2011 06:53:24 -0800 (PST)
Received: from r-mail2.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 59EAE40001; Mon, 7 Nov 2011 15:53:23 +0100 (CET)
Received: from ftrdsmtp1.rd.francetelecom.fr (unknown [10.192.128.46]) by r-mail2.rd.francetelecom.com (Postfix) with ESMTP id 4DE05FCC003; Mon, 7 Nov 2011 15:53:23 +0100 (CET)
Received: from ftrdmel0.rd.francetelecom.fr ([10.192.128.56]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675); Mon, 7 Nov 2011 15:53:23 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 07 Nov 2011 15:53:22 +0100
Message-ID: <843DA8228A1BA74CA31FB4E111A5C462020308E2@ftrdmel0.rd.francetelecom.fr>
In-Reply-To: <C90EE503-DF1D-4870-9768-4E7107872788@gmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [MEXT] the future of the MEXT working group
Thread-Index: AcycwzmMJXGjZWkmTf2zK4evFJc/xwAmTteQ
References: <4EB2D421.4030905@earthlink.net><CAD9800F.1D0F9%hesham@elevatemobile.com><CACvMsLG496pFVaVM0aJzt9W+=kwAwJjMNru4OO45aK66iDhhgw@mail.gmail.com><1672201A-C652-4204-99D9-3DE4D23D2BB2@gmail.com><CAC8QAcc85DKuerWsZC9S_C7bUzhdgSr9Z5yMFNngjtTcaoZv+g@mail.gmail.com> <C90EE503-DF1D-4870-9768-4E7107872788@gmail.com>
From: pierrick.seite@orange.com
To: jouni.nospam@gmail.com, mext@ietf.org
X-OriginalArrivalTime: 07 Nov 2011 14:53:23.0375 (UTC) FILETIME=[FF5D2BF0:01CC9D5C]
Cc: jouni.korhonen@nsn.com, jari.arkko@piuha.net
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: Mon, 07 Nov 2011 14:53:24 -0000

I agree with this scope.

Pierrick

> 
> IMHO I see no reason to focus only on client-based or network-based
> solutions. FWIW the DMM solution space:
> 
> o is incremental to an existing IETF mobility protocol, be that
client-,
>   network- or even transport-based.
> o or alternatively may not depend on a specific mobility protocol at
all
>   i.e. non-anchored solution is also in scope.
> o solution is backward compatible in a sense that if a host or a
network
>   does not support DMM, nothing breaks.
> o focuses on IPv6 because anything IPv4 is just NAT-games.
> 
> - Jouni
>

v2.23.0 | Report a Bug | By Email