Re: [MEXT] the future of the MEXT working group
jouni korhonen <jouni.nospam@gmail.com> Fri, 04 November 2011 12:38 UTC
Return-Path: <jouni.nospam@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 2A37221F8B8E for <mext@ietfa.amsl.com>; Fri, 4 Nov 2011 05:38:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.513
X-Spam-Level:
X-Spam-Status: No, score=-3.513 tagged_above=-999 required=5 tests=[AWL=0.086, 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 U-z06MlA1w82 for <mext@ietfa.amsl.com>; Fri, 4 Nov 2011 05:38:00 -0700 (PDT)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id 4762521F89BA for <mext@ietf.org>; Fri, 4 Nov 2011 05:38:00 -0700 (PDT)
Received: by eyg24 with SMTP id 24so2332671eyg.31 for <mext@ietf.org>; Fri, 04 Nov 2011 05:37:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=08XcnWi9q27l8/gjMJPpF+NqykB2YXTnLDNuYJ8lAA8=; b=GiRnYT1Xo9KQK2iAzOWfDpXEPj0tlFnzSEP6bTlo72MdcFTCX0SciiwVp9wQsxMlIb 0MUeEZuG+77jWiVGFdttcT8wQrSB1EMQrB7qxTZHt2eu6ZVCGw6+UW5c0jsO6pyCrqdh hDSgl7E2vBs/u7yX+Rk2Oe3gev7kiUpaVozqY=
Received: by 10.213.17.74 with SMTP id r10mr226473eba.125.1320410277887; Fri, 04 Nov 2011 05:37:57 -0700 (PDT)
Received: from dhcp-27-53.ripemtg.ripe.net (dhcp-27-53.ripemtg.ripe.net. [193.0.27.53]) by mx.google.com with ESMTPS id f41sm24848745eec.5.2011.11.04.05.37.54 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 04 Nov 2011 05:37:56 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: jouni korhonen <jouni.nospam@gmail.com>
In-Reply-To: <843DA8228A1BA74CA31FB4E111A5C4620203035E@ftrdmel0.rd.francetelecom.fr>
Date: Fri, 04 Nov 2011 14:37:47 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <2C16A256-DEA6-4690-B35B-D5A41FCD02A3@gmail.com>
References: <4EAA9B4A.3020208@piuha.net> <4EAA9E34.2080903@piuha.net> <1B31D76B-4C76-4351-B270-437D4560007C@gmail.com> <843DA8228A1BA74CA31FB4E111A5C4620203035E@ftrdmel0.rd.francetelecom.fr>
To: pierrick.seite@orange.com
X-Mailer: Apple Mail (2.1084)
Cc: jari.arkko@piuha.net, 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, 04 Nov 2011 12:38:01 -0000
Pierrick, On Nov 4, 2011, at 11:28 AM, <pierrick.seite@orange.com> <pierrick.seite@orange.com> wrote: >> Also, I think we ought not only consider just mobility enhancement. More >> efficient use of CoA(s) for direct/local/non-tunneled communication along >> with existing mobility solutions should be in scope as well. >> > > Actually, this is the idea behind dynamic mobility management described in the charter: use the CoA for IP flow which does not require mobility support. We are inline. > > Pierrick Nit picking and a bit of intentional teasing ;) Above is currently about a half.. one clear statement in the charter proposal is "the distribution of mobility anchors to achieve a more flat design". The other clear statement is "the dynamic activation/deactivation of mobility protocol support as an enabler". However to use CoA(s) or any address you get locally falls greatly into the source address selection issues, which is not really about mobility per se. You don't necessarily even need distributed mobility anchors to facilitate that. Of course, there are vast amount possible solution approaches in this space. - Jouni
- Re: [MEXT] the future of the MEXT working group Jari Arkko
- [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