IETF Logo Mail Archive

[netext] [request for feedback] FW: New Version Notification for draft-kaippallimalil-netext-pmip-qos-wifi-04.txt

John Kaippallimalil <John.Kaippallimalil@huawei.com> Mon, 24 February 2014 17:43 UTC

Return-Path: <John.Kaippallimalil@huawei.com>
X-Original-To: netext@ietfa.amsl.com
Delivered-To: netext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F2531A026D for <netext@ietfa.amsl.com>; Mon, 24 Feb 2014 09:43:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.849
X-Spam-Level:
X-Spam-Status: No, score=-2.849 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lIP1qnzsCojk for <netext@ietfa.amsl.com>; Mon, 24 Feb 2014 09:43:12 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 88DBC1A0293 for <netext@ietf.org>; Mon, 24 Feb 2014 09:43:11 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BDX74333; Mon, 24 Feb 2014 17:43:10 +0000 (GMT)
Received: from LHREML406-HUB.china.huawei.com (10.201.5.243) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 24 Feb 2014 17:43:04 +0000
Received: from DFWEML705-CHM.china.huawei.com (10.193.5.142) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 24 Feb 2014 17:43:09 +0000
Received: from DFWEML703-CHM.china.huawei.com ([169.254.5.106]) by dfweml705-chm.china.huawei.com ([169.254.7.50]) with mapi id 14.03.0158.001; Mon, 24 Feb 2014 09:42:59 -0800
From: John Kaippallimalil <John.Kaippallimalil@huawei.com>
To: "netext@ietf.org" <netext@ietf.org>
Thread-Topic: [request for feedback] FW: New Version Notification for draft-kaippallimalil-netext-pmip-qos-wifi-04.txt
Thread-Index: AQHPMYfbXs489yxZt0m9q+SV2+JAbw==
Date: Mon, 24 Feb 2014 17:42:58 +0000
Message-ID: <6561EABF52675C45BCDACA1B4D7AA1171D9BC3CA@dfweml703-chm.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.192.11.65]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/netext/t_OucLZ21YGhuPBuYDEu_lw_G5c
Subject: [netext] [request for feedback] FW: New Version Notification for draft-kaippallimalil-netext-pmip-qos-wifi-04.txt
X-BeenThere: netext@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 24 Feb 2014 17:43:15 -0000

Hello,
We have a new draft on Mapping 802.11 QoS in PMIPv6 Mobility domain (http://www.ietf.org/internet-drafts/draft-kaippallimalil-netext-pmip-qos-wifi-04.txt) with comments from the group addressed. 

The main comments from last meeting:
- Why do we need per-user QoS and what is missing    ( -- new text in Introduction)
- default connection/admission control, etc.         ( -- revised/added use cases)
- Don't understand justification for DSCP map set    ( -- removed from draft)
- mapping of connection parameters between WiFi/PMIP ( -- added tables for the mapping)

We would like to get feedback on this draft/revision and would like to have it adopted as a working group item. 

Regards,
John



-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: Tuesday, February 11, 2014 11:09 AM
To: John Kaippallimalil; John Kaippallimalil; Rajesh Pazhyannur; Parviz Yegani; Rajesh Pazhyannur; Parviz Yegani
Subject: New Version Notification for draft-kaippallimalil-netext-pmip-qos-wifi-04.txt


A new version of I-D, draft-kaippallimalil-netext-pmip-qos-wifi-04.txt
has been successfully submitted by John Kaippallimalil and posted to the IETF repository.

Name:		draft-kaippallimalil-netext-pmip-qos-wifi
Revision:	04
Title:		Mapping 802.11 QoS in a PMIPv6 Mobility Domain
Document date:	2014-02-10
Group:		Individual Submission
Pages:		24
URL:            http://www.ietf.org/internet-drafts/draft-kaippallimalil-netext-pmip-qos-wifi-04.txt 
Status:         https://datatracker.ietf.org/doc/draft-kaippallimalil-netext-pmip-qos-wifi/ 
Htmlized:       http://tools.ietf.org/html/draft-kaippallimalil-netext-pmip-qos-wifi-04
Diff:           http://www.ietf.org/rfcdiff?url2=draft-kaippallimalil-netext-pmip-qos-wifi-04

Abstract:
   This document provides recommendations on procedures and mapping of
   QoS parameters between 802.11 and PMIPv6. QoS parameters in 802.11
   that reserve resources for 802.11 streams should be mapped to PMIP
   QoS resources for IP sessions and flows. QoS reservation sequences in
   802.11 should allow cases where MN initiate resource reservation, as
   well as cases where the network initiates resource reservation.
   Additionally, it should be possible for QoS parameters for PMIPv6
   flows and mobility sessions to be mapped to 802.11 traffic stream
   reservations. The sequences and parameters to be mapped to provide a
   consistent behavior across 802.11 and PMIPv6 QoS are described here.



                                                                                  


Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

v2.23.0 | Report a Bug | By Email