Re: [netext] Consensus call: Adopt I-D draft-bernardos-netext-pmipv6-flowmob-03 as Netext WG doc?
<Dirk.von-Hugo@telekom.de> Thu, 11 August 2011 08:02 UTC
Return-Path: <Dirk.von-Hugo@telekom.de>
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 8A87521F858D for <netext@ietfa.amsl.com>;
Thu, 11 Aug 2011 01:02:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.149
X-Spam-Level:
X-Spam-Status: No, score=-3.149 tagged_above=-999 required=5 tests=[AWL=0.100,
BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1]
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 mWIvIWozoFRx for
<netext@ietfa.amsl.com>; Thu, 11 Aug 2011 01:02:15 -0700 (PDT)
Received: from tcmail53.telekom.de (tcmail53.telekom.de [217.5.214.110]) by
ietfa.amsl.com (Postfix) with ESMTP id BBB0A21F8586 for <netext@ietf.org>;
Thu, 11 Aug 2011 01:02:14 -0700 (PDT)
Received: from he111629.emea1.cds.t-internal.com ([10.134.93.21]) by
tcmail51.telekom.de with ESMTP/TLS/AES128-SHA; 11 Aug 2011 10:02:08 +0200
Received: from HE113484.emea1.cds.t-internal.com ([169.254.4.241]) by
HE111629.emea1.cds.t-internal.com ([::1]) with mapi;
Thu, 11 Aug 2011 10:02:08 +0200
From: <Dirk.von-Hugo@telekom.de>
To: <Basavaraj.Patil@nokia.com>, <netext@ietf.org>
Date: Thu, 11 Aug 2011 10:02:06 +0200
Thread-Topic: [netext] Consensus call: Adopt I-D
draft-bernardos-netext-pmipv6-flowmob-03 as Netext WG doc?
Thread-Index: AQHMV6MuHZ6NbgcL2k6ZQy/+0fAoQZUXSlLQ
Message-ID: <05C81A773E48DD49B181B04BA21A342A263F118328@HE113484.emea1.cds.t-internal.com>
References: <CA68600C.1CED7%basavaraj.patil@nokia.com>
In-Reply-To: <CA68600C.1CED7%basavaraj.patil@nokia.com>
Accept-Language: en-US, de-DE
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US, de-DE
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: Thu, 11 Aug 2011 08:02:15 -0000
Yes Regards Dirk 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] 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… 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… Basavaraj.Patil
- Re: [netext] Consensus call: Adopt I-D draft-bern… Julien Laganier
- Re: [netext] Consensus call: Adopt I-D draft-bern… Mohana Jeyatharan