Re: [netext] Consensus call: Adopt I-D draft-bernardos-netext-pmipv6-flowmob-03 as Netext WG doc?
<Basavaraj.Patil@nokia.com> Fri, 12 August 2011 16:25 UTC
Return-Path: <Basavaraj.Patil@nokia.com>
X-Original-To: netext@ietfa.amsl.com
Delivered-To: netext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0642D21F8888 for <netext@ietfa.amsl.com>; Fri, 12 Aug 2011 09:25:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.387
X-Spam-Level:
X-Spam-Status: No, score=-102.387 tagged_above=-999 required=5 tests=[AWL=-0.388, BAYES_00=-2.599, J_CHICKENPOX_21=0.6, USER_IN_WHITELIST=-100]
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 I1Jw93PqFlcm for <netext@ietfa.amsl.com>; Fri, 12 Aug 2011 09:25:44 -0700 (PDT)
Received: from mgw-da02.nokia.com (smtp.nokia.com [147.243.128.26]) by ietfa.amsl.com (Postfix) with ESMTP id 4038621F8786 for <netext@ietf.org>; Fri, 12 Aug 2011 09:25:44 -0700 (PDT)
Received: from vaebh105.NOE.Nokia.com (vaebh105.europe.nokia.com [10.160.244.31]) by mgw-da02.nokia.com (Switch-3.4.4/Switch-3.4.3) with ESMTP id p7CGQJK1026465; Fri, 12 Aug 2011 19:26:20 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.7]) by vaebh105.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Fri, 12 Aug 2011 19:26:19 +0300
Received: from 008-AM1MMR1-006.mgdnok.nokia.com (65.54.30.61) by NOK-AM1MHUB-03.mgdnok.nokia.com (65.54.30.7) with Microsoft SMTP Server (TLS) id 8.2.255.0; Fri, 12 Aug 2011 18:26:18 +0200
Received: from 008-AM1MPN1-024.mgdnok.nokia.com ([169.254.4.61]) by 008-AM1MMR1-006.mgdnok.nokia.com ([65.54.30.61]) with mapi id 14.01.0323.002; Fri, 12 Aug 2011 18:26:18 +0200
From: Basavaraj.Patil@nokia.com
To: cjbc@it.uc3m.es, pierrick.seite@orange-ftgroup.com
Thread-Topic: [netext] Consensus call: Adopt I-D draft-bernardos-netext-pmipv6-flowmob-03 as Netext WG doc?
Thread-Index: AQHMV6MuHZ6NbgcL2k6ZQy/+0fAoQZUXSlLQgAAH7lCAASHYAIAAgGWA
Date: Fri, 12 Aug 2011 16:26:17 +0000
Message-ID: <CA6ABE18.1D11E%basavaraj.patil@nokia.com>
In-Reply-To: <1313120802.14232.19.camel@acorde.it.uc3m.es>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.2.0.101115
x-originating-ip: [172.19.59.137]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <4E76245F8B2375489A8BFD36CA6CDF64@nokia.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 12 Aug 2011 16:26:19.0030 (UTC) FILETIME=[90C65B60:01CC590C]
X-Nokia-AV: Clean
Cc: netext@ietf.org
Subject: Re: [netext] Consensus call: Adopt I-D draft-bernardos-netext-pmipv6-flowmob-03 as Netext WG doc?
X-BeenThere: netext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Mailing list for discusion of extensions to network mobility protocol, i.e PMIP6. " <netext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netext>, <mailto:netext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/netext>
List-Post: <mailto:netext@ietf.org>
List-Help: <mailto:netext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netext>, <mailto:netext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Aug 2011 16:25:45 -0000
The charter is quite explicit about not venturing into any extensions that require MN changes. Hence I would say that MN initiated flow mobility is OUT OF SCOPE for this work item. -Raj On 8/11/11 10:46 PM, "ext Carlos Jesús Bernardos Cano" <cjbc@it.uc3m.es> wrote: >Hi Pierrick, > >I think that once the draft becomes WG document, as long as it fits in >the charter, it's up to the WG to decide if MN initiated mobility should >be also considered. > >Thanks, > >Carlos > >On Thu, 2011-08-11 at 10:42 +0200, pierrick.seite@orange-ftgroup.com >wrote: >> Hi, >> >> I'm in favor of this document but I've one question: >> >> In the current version, the LMA makes decision to move flows and the MN >> follows that decision to forward packets on the right interface. >> However, during IETf80, we had good arguments in favour of the MN making >> decision to move flows. >> >> So, the question is: do you plan, in this I-D, to consider also MN >> initiated mobility management or shall we consider only network >> initiated mobility ? >> >> Pierrick >> >> > >> > Betreff: [netext] Consensus call: Adopt I-D >> draft-bernardos-netext-pmipv6- >> > flowmob-03 as Netext WG doc? >> > >> > Hello, >> > >> > At IETF81 the chairs made a proposal to adopt as WG I-D: Proxy Mobile >> IPv6 >> > Extensions to Support Flow Mobility >> > <draft-bernardos-netext-pmipv6-flowmob-03> As the starting point for >> > the specification defining flow mobility for Proxy Mobile IPv6. >> > We gauged support for and against adopting this I-D at the IETF81 WG >> > meeting with the following result: >> > >> > In favor: 18 >> > Opposed: None >> > >> > As per process we are following up on the mailing list with the same >> > question. Please respond by Aug 18th, 2011 to the question below: >> > >> > Q: Should we adopt as Netext WG I-D the document: >> > draft-bernardos-netext-pmipv6-flowmob-03 which will be used as the >> > starting point in specifying the flow mobility feature for Proxy >> > Mobile IPv6? >> > >> > Yes [ ] >> > No [ ] >> > >> > >> > -Chairs >> > >> > IETF81 WG minutes are posted at: >> > http://www.ietf.org/proceedings/81/minutes/netext.txt >> > >> > _______________________________________________ >> > netext mailing list >> > netext@ietf.org >> > https://www.ietf.org/mailman/listinfo/netext >> > _______________________________________________ >> > netext mailing list >> > netext@ietf.org >> > https://www.ietf.org/mailman/listinfo/netext >> _______________________________________________ >> netext mailing list >> netext@ietf.org >> https://www.ietf.org/mailman/listinfo/netext > >-- >Carlos Jesús Bernardos Cano http://www.netcom.it.uc3m.es/ >GPG FP: D29B 0A6A 639A A561 93CA 4D55 35DC BA4D D170 4F67
- [netext] Consensus call: Adopt I-D draft-bernardo… Basavaraj.Patil
- Re: [netext] Consensus call: Adopt I-D draft-bern… Carl Williams
- Re: [netext] Consensus call: Adopt I-D draft-bern… Behcet Sarikaya
- Re: [netext] Consensus call: Adopt I-D draft-bern… Basavaraj.Patil
- Re: [netext] Consensus call: Adopt I-D draft-bern… Dirk.von-Hugo
- Re: [netext] Consensus call: Adopt I-D draft-bern… pierrick.seite
- Re: [netext] Consensus call: Adopt I-D draft-bern… Hidetoshi Yokota
- Re: [netext] Consensus call: Adopt I-D draft-bern… Carlos Jesús Bernardos Cano
- Re: [netext] Consensus call: Adopt I-D draft-bern… Jinho Kim
- Re: [netext] Consensus call: Adopt I-D draft-bern… Behcet Sarikaya
- Re: [netext] Consensus call: Adopt I-D draft-bern… Basavaraj.Patil
- Re: [netext] Consensus call: Adopt I-D draft-bern… Julien Laganier
- Re: [netext] Consensus call: Adopt I-D draft-bern… Stefano Faccin
- Re: [netext] Consensus call: Adopt I-D draft-bern… Basavaraj.Patil
- Re: [netext] Consensus call: Adopt I-D draft-bern… Basavaraj.Patil
- Re: [netext] Consensus call: Adopt I-D draft-bern… Stefano Faccin
- Re: [netext] Consensus call: Adopt I-D draft-bern… Basavaraj.Patil
- Re: [netext] Consensus call: Adopt I-D draft-bern… Stefano Faccin
- Re: [netext] Consensus call: Adopt I-D draft-bern… Basavaraj.Patil
- Re: [netext] Consensus call: Adopt I-D draft-bern… Stefano Faccin
- Re: [netext] Consensus call: Adopt I-D draft-bern… Julien Laganier
- Re: [netext] Consensus call: Adopt I-D draft-bern… Basavaraj.Patil
- Re: [netext] Consensus call: Adopt I-D draft-bern… Julien Laganier
- Re: [netext] Consensus call: Adopt I-D draft-bern… Mohana Jeyatharan