Re: [MEXT] FW: Agenda requests for Prague meeting

Alexandru Petrescu <alexandru.petrescu@gmail.com> Tue, 22 March 2011 15:36 UTC

Return-Path: <alexandru.petrescu@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 A238A28C12E for <mext@core3.amsl.com>; Tue, 22 Mar 2011 08:36:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level:
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35]
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 56-UEUG2nKjl for <mext@core3.amsl.com>; Tue, 22 Mar 2011 08:36:00 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.144]) by core3.amsl.com (Postfix) with ESMTP id 56B5D28C0D6 for <mext@ietf.org>; Tue, 22 Mar 2011 08:36:00 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.2) with ESMTP id p2MFbV8G005843 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 22 Mar 2011 16:37:31 +0100
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id p2MFbVan013218; Tue, 22 Mar 2011 16:37:31 +0100 (envelope-from alexandru.petrescu@gmail.com)
Received: from [132.166.133.178] ([132.166.133.178]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.1) with ESMTP id p2MFbV2p020938; Tue, 22 Mar 2011 16:37:31 +0100
Message-ID: <4D88C23B.4020709@gmail.com>
Date: Tue, 22 Mar 2011 16:37:31 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: mext@ietf.org
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>
In-Reply-To: <4D88B7B5.4020903@it.uc3m.es>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [MEXT] FW: Agenda requests for Prague meeting
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: Tue, 22 Mar 2011 15:36:07 -0000

Le 22/03/2011 15:52, marcelo bagnulo braun a écrit :
> so, you ave downgraded you statement of several itemS being non MIP
> related and all the DMM discussion being non MIP related to just one
> single agenda item...

You asked one, I told one.

Another is the 3rd item (HAC is not a Mobile IPv6 entity, TLS is not a
MIP6 Type Code, etc.)

> great, it seems we are making good progress here.
>
> about the particular item you mention: i understand this is the
> motivation for the dmm work and understanding the perceived probelms
> is needed to figure out how we can use MIP to deal with the
> perceived problem.
>
>
> However, if people think this is out of scope for MEXT, i am fine to
> discuss whether we should keep it in the agenda or not

I think it is worth discussing how much relationship do the current
agenda items have to the Mobile IPv6 protocol, and whether that
relationship is as much as other agenda requests.

Alex

>
>
>
>
>
> El 22/03/11 15:35, Alexandru Petrescu escribió:
>> Le 22/03/2011 15:06, marcelo bagnulo braun a écrit :
>>> Please point exactly what item in the agenda is NOT about the
>>> Mobile IP protocol.
>>
>> The 6th.
>>
>> Alex
>>
>>>
>>>
>>> El 20/03/11 15:13, Alexandru Petrescu escribió:
>>>> Marcelo, Hi,
>>>>
>>>> I have a doubt about the reasoning behind declining Fred's
>>>> request of agenda item.
>>>>
>>>> The current agenda
>>>> http://www.ietf.org/proceedings/80/agenda/mext.txt
>>>>
>>>> contains items IMHO only remotely or very vaguely related to
>>>> the Mobile IPv6 protocol per se. Additionally, agenda's DMM
>>>> core item has a discussion which does not seem to converge on
>>>> the use of Mobile IPv6.
>>>>
>>>> In this sense, I am not sure the typical statements of MEXT
>>>> doing _only_ Mobile IPv6 stuff holds any longer, as I see it
>>>> today.
>>>>
>>>> Fred's "IRON and MOBIKE" draft-templin-ironmike-00.txt is
>>>> related to IKE which is related to Mobile IPv6 security.
>>>>
>>>> I am not trying to advertise Fred's draft particularly. I am
>>>> saying this because...
>>>>
>>>> I have the same agenda problem with similar work I do
>>>> (RA-based routing) for mobility, i.e. boxes which may run
>>>> Mobile IPv6 but need something else than Mobile IPv6 Type
>>>> Codes.
>>>>
>>>> That is my doubt about MEXT activity and agenda planning,
>>>> thanks.
>>>>
>>>> Alex
>>>>
>>>> Le 14/03/2011 19:56, marcelo bagnulo braun a écrit :
>>>>> Hi Fred,
>>>>>
>>>>> This is outside the scope of the MEXT wg, which is limited
>>>>> to the the Mobile IPv6 protocol. Hence, we decline your
>>>>> request.
>>>>>
>>>>> Regards, marcelo
>>>>>
>>>>>
>>>>> El 14/03/11 18:57, Templin, Fred L escribió:
>>>>>> Hi Marcelo (and Julien),
>>>>>>
>>>>>> In January, I posted several messages on a new approach to
>>>>>> mobility management known as IRON:
>>>>>>
>>>>>> http://www.ietf.org/mail-archive/web/mext/current/msg04529.html
>>>>>>
>>>>>>
>>>>>>
http://www.ietf.org/mail-archive/web/mext/current/msg04535.html
>>>>>> http://www.ietf.org/mail-archive/web/mext/current/msg04543.html
>>>>>>
>>>>>>
>>>>>>
http://www.ietf.org/mail-archive/web/mext/current/msg04546.html
>>>>>>
>>>>>> The base IRON architecture document has now been published
>>>>>> as an experimental RFC of the IRTF Routing Research Group:
>>>>>>
>>>>>> http://www.rfc-editor.org/rfc/rfc6179.txt
>>>>>>
>>>>>> and the mechanisms and operational practices are
>>>>>> documented in the following active Internet drafts:
>>>>>>
>>>>>> http://tools.ietf.org/html/draft-templin-intarea-vet
>>>>>> http://tools.ietf.org/html/draft-templin-intarea-seal
>>>>>> http://tools.ietf.org/html/draft-templin-ironmike-00
>>>>>> http://tools.ietf.org/html/draft-templin-iron-pm-00
>>>>>>
>>>>>> I'd like to get a 20min MEXT slot at IETF80 to present the
>>>>>>  approach. Please let me know if that works for you.
>>>>>>
>>>>>> Fred fred.l.templin@boeing.com
>>>>>>
>>>>>>> -----Original Message----- From: mext-bounces@ietf.org
>>>>>>> [mailto:mext-bounces@ietf.org] On Behalf Of marcelo
>>>>>>> bagnulo braun Sent: Wednesday, March 09, 2011 8:32 AM
>>>>>>> To: mext Subject: [MEXT] Agenda requests for Prague
>>>>>>> meeting
>>>>>>>
>>>>>>> Please send slot requests for the prague meeting to the
>>>>>>> chairs. please note that we are meeting on friday.
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________ 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
>>>>>
>>>>
>>>> _______________________________________________ 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
>>>
>>
>> _______________________________________________ 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
>