Re: [netext] Alvaro Retana's No Objection on draft-ietf-netext-pmip-qos-wifi-07: (with COMMENT)

John Kaippallimalil <John.Kaippallimalil@huawei.com> Fri, 10 April 2015 15:15 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 DBA5D1A1ABB; Fri, 10 Apr 2015 08:15:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 Kf5PBlj_NtHW; Fri, 10 Apr 2015 08:15:25 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 908F91A1A8C; Fri, 10 Apr 2015 08:15:24 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml405-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BRG41979; Fri, 10 Apr 2015 15:15:23 +0000 (GMT)
Received: from DFWEML706-CHM.china.huawei.com (10.193.5.225) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 10 Apr 2015 16:15:22 +0100
Received: from DFWEML703-CHM.china.huawei.com ([10.193.5.130]) by dfweml706-chm ([10.193.5.225]) with mapi id 14.03.0158.001; Fri, 10 Apr 2015 08:15:13 -0700
From: John Kaippallimalil <John.Kaippallimalil@huawei.com>
To: "aretana@cisco.com" <aretana@cisco.com>, "iesg@ietf.org" <iesg@ietf.org>
Thread-Topic: Alvaro Retana's No Objection on draft-ietf-netext-pmip-qos-wifi-07: (with COMMENT)
Thread-Index: AQHQc57+alqAQXkALk+Xxk2sD3svx51GWOuw
Date: Fri, 10 Apr 2015 15:15:13 +0000
Message-ID: <6561EABF52675C45BCDACA1B4D7AA1171DA90866@dfweml703-chm>
References: <20150408171741.1230.60763.idtracker@ietfa.amsl.com> <5527E554.8030706@innovationslab.net>
In-Reply-To: <5527E554.8030706@innovationslab.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.192.11.163]
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/3RQqcH1d12eCoW27oZS2ikVtapU>
Cc: "netext@ietf.org" <netext@ietf.org>, "netext-chairs@ietf.org" <netext-chairs@ietf.org>
Subject: Re: [netext] Alvaro Retana's No Objection on draft-ietf-netext-pmip-qos-wifi-07: (with COMMENT)
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: Fri, 10 Apr 2015 15:15:30 -0000

Hi Alvaro,

> Just a small question/comment:
> 
> Given that rfc7222 considers an access network independent way of
> negotiating QoS, and that this document describes the negotiation when
> the access is WiFi, it seems to me that this document updates rfc7222
> for this specific case and it should be marked as such.  Am I missing
> something?

I don't see this draft updating RFC 7222 because that is about access independent QoS mechanisms between the mobility anchor and access gateway. 
How they are mapped to specific access technologies is not defined in RFC 7222. This draft supplements with parameter and procedure information for just the WiFi access. The Introduction chapter explains this as follows:

"   The recommendations in this document use IEEE 802.11 QoS and PMIPv6
   QoS [1] mechanisms.  State machines for QoS policy setup in IEEE
   802.11 and PMIPv6 operate differently.  Guidelines for installing QoS
   in the MN using 802.11 and PMIPv6 segments, and for mapping
   parameters between them are outlined below."

[followed by the two paragraphs on parameter mapping and procedure mapping]

Best Regards,
John

 


> -------- Forwarded Message --------
> Subject: Alvaro Retana's No Objection on
> draft-ietf-netext-pmip-qos-wifi-07: (with COMMENT)
> Date: Wed, 08 Apr 2015 10:17:41 -0700
> From: Alvaro Retana <aretana@cisco.com>;
> To: The IESG <iesg@ietf.org>;
> CC: netext@ietf.org, netext-chairs@ietf.org, bpatil1+ietf@gmail.com
> 
> Alvaro Retana has entered the following ballot position for
> draft-ietf-netext-pmip-qos-wifi-07: No Objection
> 
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
> 
> 
> Please refer to http://www.ietf.org/iesg/statement/discuss-
> criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
> 
> 
> The document, along with other ballot positions, can be found here:
> http://datatracker.ietf.org/doc/draft-ietf-netext-pmip-qos-wifi/
> 
> 
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> Just a small question/comment:
> 
> Given that rfc7222 considers an access network independent way of
> negotiating QoS, and that this document describes the negotiation when
> the access is WiFi, it seems to me that this document updates rfc7222
> for this specific case and it should be marked as such.  Am I missing
> something?
> 
>