[netext] Consensus call on adopting I-D draft-liebsch-netext-pmip6-qos as WG document
<Basavaraj.Patil@nokia.com> Wed, 23 May 2012 19:02 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 5EAD521F8699 for <netext@ietfa.amsl.com>; Wed, 23 May 2012 12:02:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 Y0dBjaRLz8ha for <netext@ietfa.amsl.com>; Wed, 23 May 2012 12:02:02 -0700 (PDT)
Received: from mgw-sa01.nokia.com (smtp.nokia.com [147.243.1.47]) by ietfa.amsl.com (Postfix) with ESMTP id 2314321F864C for <netext@ietf.org>; Wed, 23 May 2012 12:02:01 -0700 (PDT)
Received: from vaebh104.NOE.Nokia.com (vaebh104.europe.nokia.com [10.160.244.30]) by mgw-sa01.nokia.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id q4NJ1a6u013175 for <netext@ietf.org>; Wed, 23 May 2012 22:01:56 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.57]) by vaebh104.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Wed, 23 May 2012 22:01:54 +0300
Received: from 008-AM1MPN1-071.mgdnok.nokia.com ([169.254.1.4]) by 008-AM1MMR1-002.mgdnok.nokia.com ([65.54.30.57]) with mapi id 14.02.0283.004; Wed, 23 May 2012 21:01:53 +0200
From: Basavaraj.Patil@nokia.com
To: netext@ietf.org
Thread-Topic: Consensus call on adopting I-D draft-liebsch-netext-pmip6-qos as WG document
Thread-Index: AQHNORaDzXXBLSQQaEiNUGHX4GFi7w==
Date: Wed, 23 May 2012 19:01:52 +0000
Message-ID: <CBE29E5E.1F386%basavaraj.patil@nokia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.2.1.120420
x-originating-ip: [172.19.40.102]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <CE3C1C4093B798468902715FA741635B@mgd.nokia.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 23 May 2012 19:01:54.0000 (UTC) FILETIME=[84947D00:01CD3916]
X-Nokia-AV: Clean
Subject: [netext] Consensus call on adopting I-D draft-liebsch-netext-pmip6-qos as WG document
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: Wed, 23 May 2012 19:02:03 -0000
Hello, The authors of the I-D: Quality of Service Option for Proxy Mobile IPv6 <draft-liebsch-netext-pmip6-qos> http://www.ietf.org/id/draft-liebsch-netext-pmip6-qos-01.txt have requested the adoption of this I-D as a WG document. The I-D itself has been presented at IETF83 and has also been reviewed by multiple WG members. The crux of the proposal is to extend PMIP6 signaling to enable support for QoS. Abstract This specification defines a new mobility option that can be used by the mobility entities in the Proxy Mobile IPv6 domain to exchange Quality of Service parameters associated with a subscriber's IP flows. Using the QoS option, the local mobility anchor and the mobile access gateway can exchange available QoS attributes and associated values. This enables QoS policing and labeling of packets to enforce QoS differentiation on the path between the local mobility anchor and the mobile access gateway. Furthermore, making QoS parameters available on the MAG enables mapping these parameters to QoS rules being specific to the access technology which operates below the mobile access gateway. After such mapping, QoS rules can be enforced on the access technology components, such as an IEEE 802.11e Wireless LAN controller. Please review the I-D and respond by June 6th with your opinion. Respond to the following question: Should the Netext WG adopt this I-D as a WG document? Yes [ ] No [ ] Thank you. -Chairs
- [netext] Consensus call on adopting I-D draft-lie… Basavaraj.Patil
- [netext] FW: Consensus call on adopting I-D draft… Ahmad Muhanna
- Re: [netext] Consensus call on adopting I-D draft… John Kaippallimalil
- Re: [netext] Consensus call on adopting I-D draft… Florin Baboescu
- Re: [netext] Consensus call on adopting I-D draft… Carlos Jesús Bernardos Cano
- Re: [netext] Consensus call on adopting I-D draft… Lee, Yiu
- Re: [netext] Consensus call on adopting I-D draft… Charles E. Perkins
- Re: [netext] Consensus call on adopting I-D draft… Hui Deng
- [netext] 答复: Consensus call on adopting I-D draft… zhou.xingyue
- Re: [netext] Consensus call on adopting I-D draft… Dirk.von-Hugo
- Re: [netext] Consensus call on adopting I-D draft… Marco Liebsch
- Re: [netext] Consensus call on adopting I-D draft… Mark Grayson (mgrayson)
- Re: [netext] Consensus call on adopting I-D draft… Marco Liebsch
- Re: [netext] Consensus call on adopting I-D draft… Carl Williams
- Re: [netext] Consensus call on adopting I-D draft… karagian
- Re: [netext] Consensus call on adopting I-D draft… Marco Liebsch
- Re: [netext] Consensus call on adopting I-D draft… Dirk.von-Hugo
- Re: [netext] Consensus call on adopting I-D draft… Marco Liebsch
- Re: [netext] Consensus call on adopting I-D draft… Dirk.von-Hugo