idnits 2.17.1 draft-kaippallimalil-netext-pmip-qos-wifi-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 15 instances of lines with control characters in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (July 6, 2012) is 4312 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Missing Reference: 'RFC2119' is mentioned on line 107, but not defined == Missing Reference: 'GSMA-IR34' is mentioned on line 148, but not defined == Unused Reference: 'KEYWORDS' is defined on line 320, but no explicit reference was found in the text == Unused Reference: 'RFC1776' is defined on line 323, but no explicit reference was found in the text == Unused Reference: 'TRUTHS' is defined on line 326, but no explicit reference was found in the text == Unused Reference: 'EVILBIT' is defined on line 331, but no explicit reference was found in the text == Unused Reference: 'RFC5513' is defined on line 334, but no explicit reference was found in the text == Unused Reference: 'RFC5514' is defined on line 337, but no explicit reference was found in the text == Unused Reference: 'RFC 2211' is defined on line 343, but no explicit reference was found in the text == Unused Reference: 'RFC 2212' is defined on line 346, but no explicit reference was found in the text == Unused Reference: 'RFC 2216' is defined on line 350, but no explicit reference was found in the text == Unused Reference: 'RFC 3246' is defined on line 354, but no explicit reference was found in the text == Outdated reference: A later version (-12) exists of draft-ietf-netext-pmip6-qos-00 Summary: 1 error (**), 0 flaws (~~), 15 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET-DRAFT John Kaippallimalil 3 Intended Status: Informational Huawei 4 Expires: January 7, 2013 July 6, 2012 6 Mapping PMIP Quality of Service in WiFi Network 7 draft-kaippallimalil-netext-pmip-qos-wifi-00 9 Abstract 11 This document proposes a mapping for PMIP QoS parameters of each 12 mobility session that a WLC configures on a WiFi Access Point. In 13 particular there is a recommendation for consistent mapping between 14 DSCP and QCI to 802.11e parameters. The document also discusses that 15 these QoS parameters can be used by the WiFi Access Point to provide 16 priority based services based on contention in WiFi radio network or 17 reservation based services in contention free cycles in the WiFi 18 radio network. 20 Status of this Memo 22 This Internet-Draft is submitted to IETF in full conformance with the 23 provisions of BCP 78 and BCP 79. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF), its areas, and its working groups. Note that 27 other groups may also distribute working documents as 28 Internet-Drafts. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 The list of current Internet-Drafts can be accessed at 36 http://www.ietf.org/1id-abstracts.html 38 The list of Internet-Draft Shadow Directories can be accessed at 39 http://www.ietf.org/shadow.html 41 Copyright and License Notice 43 Copyright (c) 2012 IETF Trust and the persons identified as the 44 document authors. All rights reserved. 46 This document is subject to BCP 78 and the IETF Trust's Legal 47 Provisions Relating to IETF Documents 48 (http://trustee.ietf.org/license-info) in effect on the date of 49 publication of this document. Please review these documents 50 carefully, as they describe your rights and restrictions with respect 51 to this document. Code Components extracted from this document must 52 include Simplified BSD License text as described in Section 4.e of 53 the Trust Legal Provisions and are provided without warranty as 54 described in the Simplified BSD License. 56 Table of Contents 58 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 59 1.1 Terminology . . . . . . . . . . . . . . . . . . . . . . . . 3 60 1.2 Definitions . . . . . . . . . . . . . . . . . . . . . . . . 3 61 1.3 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . 3 62 2. QoS Mechanisms . . . . . . . . . . . . . . . . . . . . . . . . 4 63 2.1 QoS in 3GPP Networks . . . . . . . . . . . . . . . . . . . . 4 64 2.2 QoS in 802.11 Networks . . . . . . . . . . . . . . . . . . . 4 65 3. QoS Configuration . . . . . . . . . . . . . . . . . . . . . . . 5 66 3.1 Architecture Context . . . . . . . . . . . . . . . . . . . . 5 67 3.2 QoS Configuration on WiFi AP . . . . . . . . . . . . . . . . 6 68 4. Mapping Recommendations and Default Values . . . . . . . . . . 7 69 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 9 70 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 9 71 7 References . . . . . . . . . . . . . . . . . . . . . . . . . . 9 72 7.1 Normative References . . . . . . . . . . . . . . . . . . . 9 73 7.2 Informative References . . . . . . . . . . . . . . . . . . 9 74 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10 76 1 Introduction 78 This document provides information on how to map 3GPP QoS profile to 79 802.11e. When a user with subscription in the 3GPP network attaches 80 to a 3GPP EPC via a WiFi access, the 3GPP network can provides a QoS 81 profile for each mobility session over PMIP (S2a interface) and 82 during authorization over Diameter (STa interface). [PMIP-QoS] 83 proposes a mechanism by which QoS policy parameters in the 3GPP EPC 84 (Enhanced Packet Core) are obtained by the WLC (MAG). [PMIP-QoS] 85 further describes how DSCP obtained via PMIP is mapped to 802.1p and 86 used by WiFi APs to prioritize IP flows to/from a host (UE). 88 The QoS policy for the user should be applied in the WiFi radio 89 network and to upstream user flows in the IP backhaul network. DSCP 90 or 802.1D mapping can be used in the backhaul network. If per session 91 QoS policy is not available, the AP may be provisioned to apply QoS 92 based on the subscribed QoS values obtained during 3GPP user 93 authorization. 95 In order to provision QoS in the WiFi network, it is useful to have a 96 consistent mapping of QoS parameters and values between 3GPP and 97 802.11e. Recommendations to map a 3GPP QCI to DSCP for mobility 98 sessions are available in [PMIP-QoS]. This document adds the explicit 99 configuration of QoS per PMIP mobility session to a WiFi access 100 (radio access). 102 1.1 Terminology 104 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 105 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 106 document are to be interpreted as described in RFC 2119 [RFC2119]. 108 1.2 Definitions 110 1.3 Abbreviations 112 3GPP Third Generation Partnership Project 113 AAA Authentication Authorization Accounting 114 ARP Allocation and Retention Priority 115 AP Access Point 116 DSCP Differentiated Services Code Point 117 EPC Enhanced Packet Core 118 GBR Guaranteed Bit Rate 119 MAG Mobility Access Gateway 120 MBR Maximum Bit Rate 121 PDN-GW Packet Data Network Gateway 122 QCI QoS Class Indicator 123 QoS Quality of Service 124 Tspec Traffic Conditioning Spec 125 UE 3GPP User Equipment 126 WLC Wireless Controller 128 2. QoS Mechanisms 130 2.1 QoS in 3GPP Networks 132 3GPP has standardized QoS for EPC (Enhanced Packet Core) from Release 133 8 [TS 23.107]. 3GPP QoS policy configuration defines access agnostic 134 QoS parameters that can be used to provide service differentiation in 135 multi vendor and operator deployments. The concept of a bearer is 136 used as the basic construct for which the same QoS treatment is 137 applied for uplink and downlink packet flows between the UE (host) 138 and gateway [TS23.401]. A bearer may have more than one packet filter 139 associated and this is called a Traffic Flow Template (TFT). The IP 140 five tuple (IP source address, port, IP destination, port, protocol) 141 identifies a flow. 143 The access agnostic QoS parameters associated with each bearer are 144 QCI (QoS Class Identifier), ARP (Allocation and Retention Priority), 145 MBR (Maximum Bit Rate) and optionally GBR (Guaranteed Bit Rate). QCI 146 is a scalar that defines packet forwarding criteria in the network. 147 Mapping of QCI values to DSCP is well understood and GSMA has defined 148 standard means of mapping between these scalars [GSMA-IR34]. 150 A 3GPP UE may have more than one IP addresses associated with the 151 same hardware (MAC) address corresponding to each of the networks 152 than it is attached to. This corresponds to more than one PMIP 153 mobility session for which QoS is provisioned in the WLC. 155 2.2 QoS in 802.11 Networks 157 802.11e [802.11e] defined by IEEE provides an enhancement of the MAC 158 layer in WiFi networks to support QoS. Basic 802.11 WiFi uses CSMA 159 and collision avoidance to provide best effort access to the medium. 160 802.11e defines a Hybrid Coordination Function (HCF) that provides a 161 priority based access and also admission control based access. 163 HCF contention based channel access provides prioritized access to 164 the 802.11 medium. Four access categories (AC) are defined based on 165 traffic type. Each arriving frame is mapped into one of four FIFO 166 queues corresponding to different user priority (UP) values. The 167 highest priority frame is transmitted when access is obtained in a 168 contention window. Access categories and their mapping to 802.1D user 169 priorities is provided [802.11e]. 171 HCF controlled channel access uses a central coordinator to provide 172 contention free access to the medium based on admission control. The 173 HCCA (HCF Controlled Channel Access) based scheduling can use 174 configured policies to grant exclusive access to a QSTA (user) for 175 limited contention free slots. 177 3. QoS Configuration 179 3.1 Architecture Context 181 This section describes the context in which the 3GPP QoS 182 configuration is applied to traffic flows handled by a WiFi Access 183 Point. In this case, a 3GPP user attaches to the WiFi network and 184 accesses services in the 3GPP EPC. The 3GPP EPC provides QoS 185 parameters when the user is authorized (subscribed QoS) and for each 186 connection to EPC as described in [PMIP-QoS]. At this point, the WLC 187 has 3GPP QoS parameters for each user attached to the EPC. Access 188 Points can use DSCP values in downlink IP flows associated with a 189 user to provision 802.11e priority in WiFi network. 191 In [PMIP-QoS], the Access Point (AP) is not directly provisioned with 192 QoS for a user connection. As a result, the AP is only able to 193 prioritize flows based on observed DSCP values on downlink flows. 194 Additionally, the AP does not know the maximum bandwidth of a 195 subscriber or flow to be applied on the WiFi radio network. This can 196 result in sub-optimal utilization of scarce WiFi network resources. 197 This solution recommends provisioning the AP with QoS policy 198 associated to a user. 200 The paragraphs that follow outline the overall architecture and the 201 next sub-chapter provides details on QoS parameters provisioned in 202 the AP. 204 +-----+ 205 | AAA | 206 +--+--+ 207 | 208 | STa 209 | 210 WiFi AP WLC(MAG)| 211 +---------------+ +-------|-------+ 212 | +---------+ | 802.11 | +----v----+ | PMIP-QoS +--------+ 213 | |QoS-Ctrl <-----------------+QoS-Ctrl <--------------+ PDN-GW + 214 | +----+----+ | QoS | +----+----+ | (S2a) +---+----+ 215 | | | | | | | 216 | +----v----+ | _____ | +----V----+ | ________ | 217 | | PEP +-----/ IP )-----+ PEP +------/ IP ) | 218 | +---------+ | Network | +---------+ | | Network|--+ 219 +---------------+ ( / +---------------+ ( / 220 ----- -------- 221 Figure 1: Provisioning 802.11 QoS parameters on WiFi AP 223 Figure 1 provides a view of the architecture in which the 3GPP QoS is 224 provisioned on the AP. The end user (not shown in figure) attaches to 225 the 3GPP EPC (Enhanced Packet Core) via the WiFi AP and WLC. The two 226 QoS provisioning interfaces shown in the figure are STa for 227 delivering subscriber policy as part of user authorization, and S2a 228 PMIP for each connection to the EPC. QoS-Ctrl (logical entity) in WLC 229 provisions QoS to the WLC PEP as described in [PMIP-QoS]. In 230 addition, the WLC translates the 3GPP QoS policy to equivalent 231 parameters for 802.11e and IP flows and sends them to the WiFi AP. 232 The protocols used to exchange QoS parameters between the WLC and AP 233 are not discussed in this document. The AP maps the received QoS 234 policy configuration and applies them to upstream and downstream 235 forwarding of data packets on the WiFi radio network. The AP also 236 applies these QoS policies for upstream user IP flows to the WLC. 238 The WLC takes subscriber policy and policy per connection to EPC 239 network and translates it to equivalent 802.11e and DSCP parameters. 240 It should be noted that 3GPP users may have more than one connection 241 and policy associated with each of them. The WLC should provide the 242 AP with a policy that applies to each user (MAC address in WiFi 243 network) and parameters per IP flow. 245 3.2 QoS Configuration on WiFi AP 247 The WiFi Access Point (AP) gets QoS configuration per IP session from 248 the WLC. The QoS information per IP session provided to the AP 249 includes: 251 - Hardware (MAC) address of host for which PMIP session is 252 established. 253 - IP prefix or address of PMIP mobility session 254 - DSCP. Diffserv PHB value of PMIP QoS for the mobility session. 255 - QCI. The WLC may provide the 3GPP QCI value if available, for 256 example, from authorization profile of APN (i.e. subscribed values 257 per established PMIP mobility session). 258 - ARP (Allocation and Retention Priority). This value is obtained 259 from the PMIP QoS for the mobility session. It determines the 260 priority of a flow (1 has highest priority). 261 - MBR (Maximum Bit Rate) for mobility session uplink and downlink. 262 This should not exceed the AMBR (Aggregate MBR) of the 263 subscription. 264 - GBR (Guaranteed Bit Rate) for mobility session uplink and downlink, 265 if required. 267 The WiFi AP uses the above QoS configuration to implement 268 classification, admission control and forwarding of user flows. The 269 WiF AP maps DSCP (or QCI) to 802.11e AC (Access Categories) for each 270 IP session / hardware (MAC) address of the host (3GPP user). The 271 mapping from DSCP or QCI to 802.11e AC is shown in table in chapter 4 272 below. 274 In the WiFi radio network, the AP uses 802.11e AC values for 275 contention (HCF) based forwarding based on priority. The AP schedules 276 downstream flows in the WiFi radio network and for upstream backhaul 277 to the WLC. For contention free scheduling (based on HCCA), the WiFi 278 AP additionally uses the QoS configuration per user to admit flows 279 based on 802.11e ADDTS (ADD TSpec) requests from the host (3GPP 280 user). The WiFi AP may drops packet that fall outside the configured 281 MBR and GBR. In case of severe radio congestion, the WiFi AP can use 282 ARP in addition to DSCP drop precedence to determine the flows to be 283 dropped. 285 4. Mapping Recommendations and Default Values 287 The table below outlines a recommended mapping between 3GPP QCI, 288 and 802.11e Access Category (AC) priorities. QCI packet delay budget 289 and packet error loss rate may be used by the WiFi access point in 290 scheduling contention free access when HCCA scheduling is used. 292 QCI DSCP 802.11e AC Example 3GPP service 293 ------------------------------------------------------------- 294 1 EF 3 AC_VO conversational voice 295 2 EF 3 AC_VO conversational video 296 3 EF 3 AC_VO real-time gaming 297 4 AF41 2 AC_VI buffered streaming 298 5 AF31 2 AC_VI IMS signaling 299 6 AF31 2 AC_VI buffered streaming 300 7 AF21 0 AC_BE interactive gaming 301 8 AF11 0 AC_BE web access 302 9 BE 1 AC_BK e-mail 304 Table: QoS Mapping between QCI, WMM, 802.11e AC 306 5. Security Considerations 308 This document describes mapping of 3GPP QoS profile and parameters to 309 IEEE 802.11e parameters. No security concerns are expected as a 310 result of using this mapping. 312 6. IANA Considerations 314 No IANA assignment of parameters are required in this document. 316 7 References 318 7.1 Normative References 320 [KEYWORDS] Bradner, S., "Key words for use in RFCs to Indicate 321 Requirement Levels", BCP 14, RFC 2119, March 1997. 323 [RFC1776] Crocker, S., "The Address is the Message", RFC 1776, April 324 1 1995. 326 [TRUTHS] Callon, R., "The Twelve Networking Truths", RFC 1925, 327 April 1 1996. 329 7.2 Informative References 331 [EVILBIT] Bellovin, S., "The Security Flag in the IPv4 Header", 332 RFC 3514, April 1 2003. 334 [RFC5513] Farrel, A., "IANA Considerations for Three Letter 335 Acronyms", RFC 5513, April 1 2009. 337 [RFC5514] Vyncke, E., "IPv6 over Social Networks", RFC 5514, April 1 338 2009. 340 [PMIP-QoS] Liebsch, et al., "Quality of Service Option for Proxy 341 Mobile IPv6", draft-ietf-netext-pmip6-qos-00, June 2012. 343 [RFC 2211] Wroclawski, J., "Specification of the Controlled Load 344 Quality of Service", RFC 2211, September 1997. 346 [RFC 2212] Shenker, S., Partridge, C., and R. Guerin, "Specification 347 of Guaranteed Quality of Service", RFC 2212, September 348 1997. 350 [RFC 2216] Shenker, S., and J. Wroclawski, "Network Element QoS 351 Control Service Specification Template", RFC 2216, 352 September 1997. 354 [RFC 3246] 356 [TS23.107] Quality of Service (QoS) Concept and Architecture, Release 357 10, 3GPP TS 23.107, V10.2.0 (2011-12). 359 [TS23.207] End-to-End Quality of Service (QoS) Concept and 360 Architecture, Release 10, 3GPP TS 23.207, V10.0.0 (2011- 361 03). 363 [TS23.401] General Packet Radio Service (GPRS) enhancements for 364 Evolved Universal Terrestrial Radio Access Network (E- 365 UTRAN) access (Release 11), 3GPP TS 23.401, V11.2.0 (2012- 366 06). 368 [TS23.203] Policy and Charging Control Architecture, Release 11, 3GPP 369 TS 23.203, V11.2.0 (2011-06). 371 [TS29.212] Policy and Charging Control over Gx/Sd Reference Point, 372 Release 11, 3GPP TS 29.212, V11.1.0 (2011-06). 374 [802.11e] IEEE, "IEEE part 11: Wireless LAN Medium Access 375 Control(MAC) and Physical Layer (PHY) specifications. 376 Amendment 8: Medium Access Control (MAC) Quality of 377 Service Enhancements" 802.11e-2005, 22 September 2005. 379 [GSMA-IR34]Inter-Service Provider Backbone Guidelines 5.0, 22 380 December 2010 382 Authors' Addresses 384 John Kaippallimalil 385 5340 Legacy Drive, Suite 175 386 Plano Texas 75024 388 EMail: john.kaippallimalil@huawei.com