Re: [MEXT] Mobile IPv6 label and Mobile IPv6 protocol changes

Julien Laganier <julien.ietf@gmail.com> Thu, 24 March 2011 17:13 UTC

Return-Path: <julien.ietf@gmail.com>
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 B48FA28C13D for <mext@core3.amsl.com>; Thu, 24 Mar 2011 10:13:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.307
X-Spam-Level:
X-Spam-Status: No, score=-3.307 tagged_above=-999 required=5 tests=[AWL=0.292, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 TKdNNCKUU7fh for <mext@core3.amsl.com>; Thu, 24 Mar 2011 10:13:31 -0700 (PDT)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by core3.amsl.com (Postfix) with ESMTP id 98D8628C13C for <mext@ietf.org>; Thu, 24 Mar 2011 10:13:31 -0700 (PDT)
Received: by eye13 with SMTP id 13so124625eye.31 for <mext@ietf.org>; Thu, 24 Mar 2011 10:15:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=SDv6G/oNsE+wMmMdSdWe+fQVmfRy/gzPxWKyIeqVAug=; b=WCSv7AdVt/TLHtcczsl+QkvZyBibDhlr80jbwbJyYBAsDiO+NFvzxqJlVoFFU/KrJE Cz0r04HCXMslkrz6SxNEYfBB8H/TGct+BXOzPoCUZOjNyMuFKRHOnOPtYKWrX4T1RW2n cVV6EIyUf8CuuBwNWqxMGzBwo83Iq+2NfrBss=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=KTTRlkxDcMrIkV9qHvJPPboEsevTGurIEUUnGNZEkwX4e4i+205D5TgQxw9wRmbw1u Czm1bE48ts6i2DK7/gjBUsD+D/3UbTAZxyddUcaChXjGfc3oU60R1jdsM2LJiADx7QyS 2423pz9xz8f5307xsKHiYYHjGEL05l5AGjVAw=
MIME-Version: 1.0
Received: by 10.216.160.129 with SMTP id u1mr911689wek.88.1300986905594; Thu, 24 Mar 2011 10:15:05 -0700 (PDT)
Received: by 10.216.89.205 with HTTP; Thu, 24 Mar 2011 10:15:05 -0700 (PDT)
In-Reply-To: <4D8B4E62.50903@inria.fr>
References: <E1829B60731D1740BB7A0626B4FAF0A65C69021B3A@XCH-NW-01V.nw.nos.boeing.com> <4D7E64EE.5030302@it.uc3m.es> <4D860B93.4030602@gmail.com> <4D88ACE6.6030207@it.uc3m.es> <4D88B3A5.7050302@gmail.com> <4D88B7B5.4020903@it.uc3m.es> <4D88C23B.4020709@gmail.com> <4D88D22D.300@it.uc3m.es> <4D88FC52.4090309@gmail.com> <AANLkTimP84zss62OuTddFGLgDd5GAw1M7ctZh+Nxbkmj@mail.gmail.com> <4D890BD4.8060502@gmail.com> <AANLkTim_wYf+=OsgzOTpm5wWz+sPi564Tpph0HpY57XW@mail.gmail.com> <7758DEF9-FD80-428B-95F1-782C9EB9373D@inria.fr> <AANLkTimuMPUaHSiFvxv9GBR_H8UxTet7R7wiRf+f4CPP@mail.gmail.com> <4D8B4E62.50903@inria.fr>
Date: Thu, 24 Mar 2011 10:15:05 -0700
Message-ID: <AANLkTin7NqPA-v8PXo1vanuw2gr0a5pqZ_m1EpxkUKAD@mail.gmail.com>
From: Julien Laganier <julien.ietf@gmail.com>
To: Thierry Ernst <thierry.ernst@inria.fr>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: mext <mext@ietf.org>
Subject: Re: [MEXT] Mobile IPv6 label and Mobile IPv6 protocol changes
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: Thu, 24 Mar 2011 17:13:32 -0000

Thierry,

If any, it would be whenever after Alex presented his draft, as I
originally wrote. That is anyway beside the point. The point was, and
remains, that my recollection of how things went were there was no or
little interest expressed by the WG in Alex's draft, and it was also
commented by some that the issue described in Alex's draft isn't
specific to MEXT, NEMO or MIPv6 but a generic routing issue and thus
is out-of-scope for MEXT.

Thus unless the situation changes from what it's been earlier on, I do
not see a reason to allocate airtime to present the same draft again
in our face-to-face meeting.

--julien

On Thu, Mar 24, 2011 at 7:00 AM, Thierry Ernst <thierry.ernst@inria.fr> wrote:
>
> Hi Julien,
>
> What is the timestamp associated with your question regarding interest from
> WG members ? I did say I have interest in this, but this was a while ago
> (and it stills holds).
>
> I'm not attending the IETF meeting this time but I would be happy to
> ear/read what are the conclusions of the MEXT WG regarding Alex's draft are.
>
> Regards,
> Thierry
>
>
>
>
> On 23/03/11 15:55, Julien Laganier wrote:
>>
>> Thierry,
>>
>> On Wed, Mar 23, 2011 at 1:05 AM, Thierry Ernst<thierry.ernst@inria.fr>
>>  wrote:
>>>
>>> Juiien,
>>>
>>> Please read below.
>>>
>>> Le 22 mars 2011 à 23:26, Julien Laganier a écrit :
>>>
>>>> 2. If I am not mistaken you were already given a chance to present
>>>> this draft in a MEXT session, at which point nobody in the WG
>>>> expressed interest in it.
>>>
>>> This is not what I would called a fair statement. There are people on
>>> this list that DO have interest in this work - including me -, though I
>>> agree it might not be the priority of the WG (which is quite different from
>>> what you wrote - please be careful with such a statement - of course I'm
>>> sure you didn't really mean it).
>>
>> Please read my statements carefully before calling on their fairness.
>> I did not write nobody in the WG was interested, I wrote that nobody
>> in the WG expressed interest. Did you expressed interest in this
>> specific draft when it was announced to the mailing list? If so, it
>> would seem I have missed your message and I would apologize...
>>
>> --julien
>
>