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

<pierrick.seite@orange-ftgroup.com> Tue, 22 March 2011 14:57 UTC

Return-Path: <pierrick.seite@orange-ftgroup.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 C57FE28C13D for <mext@core3.amsl.com>; Tue, 22 Mar 2011 07:57:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.051
X-Spam-Level:
X-Spam-Status: No, score=-2.051 tagged_above=-999 required=5 tests=[AWL=0.198, 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 T0R924Qcj3Np for <mext@core3.amsl.com>; Tue, 22 Mar 2011 07:57:39 -0700 (PDT)
Received: from r-mail1.rd.francetelecom.com (r-mail1.rd.francetelecom.com [217.108.152.41]) by core3.amsl.com (Postfix) with ESMTP id 6E7D128C137 for <mext@ietf.org>; Tue, 22 Mar 2011 07:57:39 -0700 (PDT)
Received: from r-mail1.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id C1E4C6F8001; Tue, 22 Mar 2011 15:59:44 +0100 (CET)
Received: from ftrdsmtp2.rd.francetelecom.fr (unknown [10.192.128.47]) by r-mail1.rd.francetelecom.com (Postfix) with ESMTP id B28816C0001; Tue, 22 Mar 2011 15:59:44 +0100 (CET)
Received: from ftrdmel0.rd.francetelecom.fr ([10.192.128.56]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675); Tue, 22 Mar 2011 15:59:11 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 22 Mar 2011 15:59:10 +0100
Message-ID: <843DA8228A1BA74CA31FB4E111A5C4620195491C@ftrdmel0.rd.francetelecom.fr>
In-Reply-To: <4D88B7B5.4020903@it.uc3m.es>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [MEXT] FW: Agenda requests for Prague meeting
Thread-Index: AcvooNg9hRpSVZEnQ4yLdUcidIcPBQAAEC6g
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>
From: <pierrick.seite@orange-ftgroup.com>
To: <marcelo@it.uc3m.es>, <mext@ietf.org>
X-OriginalArrivalTime: 22 Mar 2011 14:59:11.0700 (UTC) FILETIME=[B3F8D940:01CBE8A1]
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 14:57:47 -0000

Hi,

In Beijing, many questions was about motivation for distribution of mobility management. So, worth to be discussed in Prague.

Pierrick

> -----Message d'origine-----
> De : mext-bounces@ietf.org [mailto:mext-bounces@ietf.org] De la part de
> marcelo bagnulo braun
> Envoyé : mardi 22 mars 2011 15:53
> À : mext@ietf.org
> Objet : Re: [MEXT] FW: Agenda requests for Prague meeting
> 
> 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... 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
> 
> 
> 
> 
> 
> 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