Re: [MEXT] [WGLC] draft-ietf-mext-flow-binding-03

marcelo bagnulo braun <marcelo@it.uc3m.es> Wed, 21 October 2009 08:42 UTC

Return-Path: <marcelo@it.uc3m.es>
X-Original-To: mext@core3.amsl.com
Delivered-To: mext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 931E43A6767 for <mext@core3.amsl.com>; Wed, 21 Oct 2009 01:42:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.367
X-Spam-Level:
X-Spam-Status: No, score=-6.367 tagged_above=-999 required=5 tests=[AWL=0.232, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TqQstdMP+N57 for <mext@core3.amsl.com>; Wed, 21 Oct 2009 01:42:40 -0700 (PDT)
Received: from smtp02.uc3m.es (smtp02.uc3m.es [163.117.176.132]) by core3.amsl.com (Postfix) with ESMTP id D0CFE3A6782 for <mext@ietf.org>; Wed, 21 Oct 2009 01:42:39 -0700 (PDT)
Received: from marcelo-bagnulos-macbook-pro.local (wlap005.it.uc3m.es [163.117.139.108]) by smtp02.uc3m.es (Postfix) with ESMTP id 428866C25A9; Wed, 21 Oct 2009 10:24:01 +0200 (CEST)
Message-ID: <4ADEC521.60708@it.uc3m.es>
Date: Wed, 21 Oct 2009 10:24:01 +0200
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Yuri Ismailov <yuri.ismailov@ericsson.com>
References: <C703464A.FCC4%hesham@elevatemobile.com> <346103.90889.qm@web111407.mail.gq1.yahoo.com> <C24C03AE7348E44FB76B34B5D4ED44F503EDA7B1@esealmw106.eemea.ericsson.se>
In-Reply-To: <C24C03AE7348E44FB76B34B5D4ED44F503EDA7B1@esealmw106.eemea.ericsson.se>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
X-TM-AS-Product-Ver: IMSS-7.0.0.3116-5.6.0.1016-16960.003
Cc: "Laganier, Julien" <julienl@qualcomm.com>, mext@ietf.org
Subject: Re: [MEXT] [WGLC] draft-ietf-mext-flow-binding-03
X-BeenThere: mext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobile IPv6 EXTensions WG <mext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 21 Oct 2009 08:42:41 -0000

Hi Yuri,

about the rechartering:

the main challenge that MEXT has is how manage the energy.

In order to work on something, we not only need to decide that this is 
not broken, but also that we want to invest the limited amount of energy 
of the WG in this topic _instead_ than investing in another topic.

and this is why we need a rechartering, so we can pick this topic and 
not pick another one or viveversa.

Makes sense?

Regards, marcelo


Yuri Ismailov escribió:
> Hi,
> Sorry for jumping in, but did not understand the point with re-chartering.
> As I can see it is in the charter.
>
> /yuri
>  
>
> -----Original Message-----
> From: mext-bounces@ietf.org [mailto:mext-bounces@ietf.org] On Behalf Of Behcet Sarikaya
> Sent: Tuesday, October 20, 2009 5:11 PM
> To: Hesham Soliman; Conny Larsson; Laganier, Julien
> Cc: mext@ietf.org
> Subject: Re: [MEXT] [WGLC] draft-ietf-mext-flow-binding-03
>
> Hi Conny, Hesham,
>
>
>
> ----- Original Message ----
>   
>> From: Hesham Soliman <hesham@elevatemobile.com>
>> To: Conny Larsson <conny.larsson@ericsson.com>; "Laganier, Julien" 
>> <julienl@qualcomm.com>
>> Cc: "mext@ietf.org" <mext@ietf.org>
>> Sent: Mon, October 19, 2009 6:49:46 PM
>> Subject: Re: [MEXT] [WGLC] draft-ietf-mext-flow-binding-03
>>
>> Hi Conny,
>>
>> We need the comments now, not after the document is updated :). This 
>> is WGLC and we're updating the document as a result of reviews.
>>
>> The bidirectionality issue was discussed and it was decided that there 
>> is no case for it.
>>     
>
> I don't think this reflects the situation.
>
> The right answer is that flow revocation and possibly other flow binding operations initiated by HA will be taken up as part of MEXT rechartering.
>
> BTW we revised our draft, here is the link to the revised draft:
>
> http://tools.ietf.org/id/draft-xia-mext-ha-init-flow-binding-01.txt
>
>
> Regards,
>
> Behcet
>
>
>       
> _______________________________________________
> MEXT mailing list
> MEXT@ietf.org
> https://www.ietf.org/mailman/listinfo/mext
> _______________________________________________
> MEXT mailing list
> MEXT@ietf.org
> https://www.ietf.org/mailman/listinfo/mext
>
>