idnits 2.17.1 draft-gundavelli-netext-access-network-option-01.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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (July 3, 2011) is 4679 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Obsolete informational reference (is this intentional?): RFC 3775 (Obsoleted by RFC 6275) Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 NETEXT WG S. Gundavelli 3 Internet-Draft Cisco 4 Intended status: Standards Track J. Korhonen 5 Expires: January 4, 2012 Nokia Siemens Networks 6 M. Grayson 7 K. Leung 8 Cisco 9 July 3, 2011 11 Access Network Information Option for Proxy Mobile IPv6 12 draft-gundavelli-netext-access-network-option-01.txt 14 Abstract 16 This specification defines a mechanism and a related mobility option 17 for carrying the access network identifier and the access operator 18 identification information from the mobile access gateway to the 19 local mobility anchor over Proxy Mobile IPv6. Based on the received 20 information, the local mobility anchor is able to provide access 21 network and access operator specific handling or policing for the 22 mobile node traffic. 24 Status of this Memo 26 This Internet-Draft is submitted in full conformance with the 27 provisions of BCP 78 and BCP 79. 29 Internet-Drafts are working documents of the Internet Engineering 30 Task Force (IETF). Note that other groups may also distribute 31 working documents as Internet-Drafts. The list of current Internet- 32 Drafts is at http://datatracker.ietf.org/drafts/current/. 34 Internet-Drafts are draft documents valid for a maximum of six months 35 and may be updated, replaced, or obsoleted by other documents at any 36 time. It is inappropriate to use Internet-Drafts as reference 37 material or to cite them other than as "work in progress." 39 This Internet-Draft will expire on January 4, 2012. 41 Copyright Notice 43 Copyright (c) 2011 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 2. Conventions and Terminology . . . . . . . . . . . . . . . . . . 4 60 2.1. Conventions . . . . . . . . . . . . . . . . . . . . . . . . 4 61 2.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 4 62 3. Protocol Considerations . . . . . . . . . . . . . . . . . . . . 4 63 4. Access Network Identifier Option . . . . . . . . . . . . . . . 5 64 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7 65 6. Security Considerations . . . . . . . . . . . . . . . . . . . . 7 66 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 8 67 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8 68 8.1. Normative References . . . . . . . . . . . . . . . . . . . 8 69 8.2. Informative References . . . . . . . . . . . . . . . . . . 8 70 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 8 72 1. Introduction 74 In many deployments there is a need for the local mobility anchor to 75 provide differentiated services and policing to the mobile nodes 76 based on the access network to which they are attached. Policy 77 systems in mobility architectures such as PCC [TS23203] and ANDSF 78 [TS23402] in 3GPP system allow configuration of policy rules with 79 conditions based on the access network information. For example, the 80 service treatment for the mobile node's traffic may be different when 81 they are attached to a access network owned by the home operator than 82 when owned by a roaming partner. The service treatment can also be 83 different based on the configured SSID in case of IEEE 802.11 based 84 access networks. 86 The Proxy Mobile IPv6 specification [RFC5213] allows carrying of the 87 Access Technology Type (ATT) information from the mobile access 88 gateway to the local mobility anchor. However, the Access Technology 89 Type alone is not sufficient for correct policy to be applied at the 90 LMA and there is a need to ensure additional information related to 91 the access network is available. Learning the access network 92 operator identity may not be possible for an LMA without a support of 93 an additional policy framework that is able to provide required 94 information out of band to the LMA. Such a policy framework may not 95 be required for all Proxy Mobile IPv6 deployments and hence an 96 alternative approach for carrying such information is required to 97 ensure that additional information related to the access network is 98 available. 100 This document defines a new mobility option, Access Network 101 Identifier (ANI) option for Proxy Mobile IPv6 (PMIPv6), that can be 102 used by mobile access gateway (MAG) for carrying the access network 103 information to the local mobility anchor. The specific details on 104 how the local mobility anchor uses this information is out-of-scope 105 for this document. 107 +--+ Access-Net-1 108 |AP|-------. {Access Specific 109 +--+ | _-----_ Policies based on ANI} 110 +-----+ _( )_ +-----+ 111 | MAG |-=====( PMIPv6 )======-| LMA |- 112 +-----+ (_ Tunnel_) +-----+ 113 +--+ | '-----' 114 |AP|-------' 115 +--+ Access-Net-2 117 Figure 1: Access Networks attached to MAG 119 Figure 1, illustrates the scenario where the IEEE 802.11 Access 120 Points are configured to the mobile access gateway. 122 2. Conventions and Terminology 124 2.1. Conventions 126 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 127 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 128 document are to be interpreted as described in RFC 2119 [RFC2119]. 130 2.2. Terminology 132 All the mobility related terms used in this document are to be 133 interpreted as defined in the Proxy Mobile IPv6 specifications 134 [RFC5213] and [RFC5844]. Additionally, this document uses the 135 following abbreviations: 137 ANDSF 139 Access Network Discovery and Selection Framework 141 PCC 143 Policy and Charging Control Framework 145 Service Set Identifier 147 Service Set Identifier (SSID) identifies the name of the IEEE 148 802.11 network. SSID differentiates from one network to the 149 other. 151 Vendor ID 153 The Vendor ID is the SMI Network Management Private Enterprise 154 Code of the IANA-maintained Private Enterprise Numbers registry 155 [SMI]. 157 3. Protocol Considerations 159 The following considerations apply to the local mobility anchor and 160 the mobile access gateway. 162 o The conceptual Binding Cache entry data structure maintained by 163 the local mobility anchor, described in Section 5.1 of [RFC5213], 164 MUST be extended to store the access network information 165 associated with the current session. Specifically, the following 166 parameters must be defined. 168 Network Identifier 170 Operator Identifier 172 o The conceptual Binding Update List entry data structure maintained 173 by the mobile access gateway, described in Section 6.1 of 174 [RFC5213], MUST be extended to store the access network 175 information associated with the current session. Specifically, 176 the following parameters must be defined. 178 Network Identifier 180 Operator Identifier 182 o The mobile access gateway may be statically configured with the 183 access network information related to the access links its 184 attached to. In access systems where the mobile access gateway is 185 attached to a micro-mobility domain such as IEEE 802.11 WLAN 186 domain, the DHCP relay agent function in that micro-mobility 187 domain may be configured to add the access network information in 188 DHCP option (82), which is the DHCP Relay Agent Information option 189 [RFC3046]. The mobile access gateway may learn the access network 190 information from this option. 192 o On receiving a Proxy Binding Update message [RFC5213] from a 193 mobile access gateway with the Access Network Information option, 194 the local mobility anchor must process the option and update the 195 corresponding fields in the Binding Cache entry. 197 o The local mobility anchor MAY choose to use the access network 198 information options for applying any access operator specific 199 handling or policing of the mobile node traffic. 201 4. Access Network Identifier Option 203 A new option, Access Network Information option, is defined for using 204 it in Proxy Binding Update (PBU) and Proxy Binding Acknowledgement 205 (PBA) messages exchanged between a local mobility anchor and a mobile 206 access gateway. This option is used for carrying the information 207 related to the access network to which the mobile node is attached. 209 The alignment requirement for this option is 4n. 211 0 1 2 3 212 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 213 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 214 | Type | Length | Op-ID Type | Op-ID Length | 215 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 216 | Operator Identifier ~ 217 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 218 | Nw-ID Type | Nw-ID Length | Network Identifier ~ 219 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 221 Figure 2: Access Network Identifier Option 223 Type 225 TBD by IANA 227 Length 229 8-bit unsigned integer indicating the length in octets of the 230 option, excluding the type and length fields. 232 Op-ID Type 234 8-bit unsigned integer indicating the type of the Operator 235 Identifier. Currently the following types are defined: 237 1. reserved. 239 2. Vendor ID as a Private Enterprise Number [SMI]. 241 3. Realm of the operator. Realm names are required to be unique, 242 and are piggybacked on the administration of the DNS 243 namespace. 245 Op-ID Length 247 8-bit unsigned integer indicating the number of octets-1 needed to 248 encode the Operator Identifier. 250 Operator Identifier 252 Up to 256 octets of the operator identifier. The encoding of the 253 identifier depends on the used OP-ID Type. 255 Nw-ID Type 257 8-bit unsigned integer indicating the type of the Network 258 Identifier. Currently the following types are defined: 260 1. reserved. 262 2. SSID of the IEEE 802.11 network. 264 3. Geolocation of the Access Point 266 Nw-ID Length 268 8-bit unsigned integer indicating the number of octets-1 needed to 269 encode the Network Identifier. 271 Network Identifier 273 Up to 256 octets of the network identifier. The encoding of the 274 identifier depends on the used Nw-ID Type. 276 5. IANA Considerations 278 This specification defines a new Mobility Header option, the Access 279 Network Information. This option is described in Section 4. The 280 Type value for this option needs to be assigned from the same 281 numbering space as allocated for the other mobility options, as 282 defined in [RFC3775]. 284 Furthermore, this specification creates a two new name spaces: Op-ID 285 Type ND NW-ID Type. Both are described with their initial 286 allocations in Section 4. These two name spaces are placed under the 287 Mobile IPv6 parameters registry for [RFC3775]. 289 6. Security Considerations 291 The Access Network Information option defined in this specification 292 is for use in Proxy Binding Update and Proxy Binding Acknowledgement 293 messages. This option is carried like any other mobility header 294 option as specified in [RFC3775] and does not require any special 295 security considerations. 297 The Access Technology Type option [RFC5213] is always present in the 298 Proxy Binding Update and Proxy Binding Acknowledgement messages. 299 Carrying additional details related to the access network to which 300 the mobile node is attached does not introduce any new security 301 vulnerabilities. 303 7. Acknowledgements 305 The authors would also like to acknowledge all the discussions 306 related to carrying Access Network Information option in Proxy Mobile 307 IPv6 protocol signaling. Additionally, the authors would like to 308 thank Stefano Faccin, Gerardo Gieratta, Rajesh Pazhyannur, and Eric 309 Voit for all the discussions around this topic. 311 8. References 313 8.1. Normative References 315 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 316 Requirement Levels", BCP 14, RFC 2119, March 1997. 318 [RFC5213] Gundavelli, S., Leung, K., Devarapalli, V., Chowdhury, K., 319 and B. Patil, "Proxy Mobile IPv6", RFC 5213, August 2008. 321 [RFC5844] Wakikawa, R. and S. Gundavelli, "IPv4 Support for Proxy 322 Mobile IPv6", RFC 5844, May 2010. 324 8.2. Informative References 326 [RFC3046] Patrick, M., "DHCP Relay Agent Information Option", 327 RFC 3046, January 2001. 329 [RFC3775] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support 330 in IPv6", RFC 3775, June 2004. 332 [SMI] IANA, "PRIVATE ENTERPRISE NUMBERS", SMI Network Management 333 Private Enterprise Codes, February 2011. 335 [TS23203] 3GPP, "Policy and Charging Control Architecture", 2010. 337 [TS23402] 3GPP, "Architecture enhancements for non-3GPP accesses", 338 2010. 340 Authors' Addresses 342 Sri Gundavelli 343 Cisco 344 170 West Tasman Drive 345 San Jose, CA 95134 346 USA 348 Email: sgundave@cisco.com 350 Jouni Korhonen 351 Nokia Siemens Networks 352 Linnoitustie 6 353 Espoo FIN-02600 354 Finland 356 Email: jouni.nospam@gmail.com 358 Mark Grayson 359 Cisco 360 11 New Square Park 361 Bedfont Lakes, FELTHAM TW14 8HA 362 ENGLAND 364 Email: mgrayson@cisco.com 366 Kent Leung 367 Cisco 368 170 West Tasman Drive 369 San Jose, CA 95134 370 USA 372 Email: kleung@cisco.com