idnits 2.17.00 (12 Aug 2021) /tmp/idnits2081/draft-cao-dhc-anqp-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 (October 22, 2012) is 3498 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: 'IEEE-ELEVENU' is defined on line 270, but no explicit reference was found in the text -- Obsolete informational reference (is this intentional?): RFC 3315 (Obsoleted by RFC 8415) Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force Z. Cao 3 Internet-Draft T. Sun 4 Intended status: Informational China Mobile 5 Expires: April 25, 2013 S. McCann 6 Research in Motion 7 October 22, 2012 9 DHCPv4 and DHCPv6 Options for Access Network Query Protocol Servers 10 draft-cao-dhc-anqp-option-01 12 Abstract 14 This document defines a DHCPv4 option and DHCPv6 option of the Access 15 Network Query Protocol (ANQP) server address. These options are used 16 to configure the ANQP server addresses on the Access Point of WLAN 17 system. 19 Status of this Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at http://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on April 25, 2013. 36 Copyright Notice 38 Copyright (c) 2012 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (http://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 54 1.1. Requirements Language . . . . . . . . . . . . . . . . . . . 3 55 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 56 3. DHCPv4 Option of ANQP Server Address . . . . . . . . . . . . . 4 57 4. DHCPv6 Option of ANQP Server Address . . . . . . . . . . . . . 5 58 5. Advertisement Server Type . . . . . . . . . . . . . . . . . . . 6 59 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 60 7. Security Considerations . . . . . . . . . . . . . . . . . . . . 7 61 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7 62 8.1. Normative References . . . . . . . . . . . . . . . . . . . 7 63 8.2. Informative References . . . . . . . . . . . . . . . . . . 7 64 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 8 66 1. Introduction 68 Access Network Query Protocol (ANQP) was defined by IEEE 802.11u Task 69 Group [IEEE-ELEVENU]and is now integrated into the 802.11-2012 70 specification suite. And ANQP has been further extended by the 71 Hotspot 2.0 Technical Group of Wi-Fi Alliance (WFA), and it has been 72 included in the representative certification program called 73 "Passpoint" [PASSPOINT]. 75 ANQP is an example of the query protocol for access network 76 information retrieval, and it is transported by the IEEE 802.11 77 defined Generic Advertisement Service (GAS) Public Action frames. 78 GAS enables a WLAN client (e.g., a STA) to exchange messages with an 79 advertisement server (e.g., an ANQP server) in the pre-association 80 state, i.e., prior to association. With the information retrieved 81 via this server, the WLAN client connection manager can make informed 82 selection among multiple access networks. One example of using ANQP 83 is that the WLAN client in a roaming environment can select the 84 correct visited access network that has roaming relationship with its 85 home service provider without user intervention. 87 In a scalable deployment environment, the ANQP server will not be 88 placed on the Access Point (AP), rather it should be placed on a 89 centralized device that serves different APs. The AP will forward 90 the ANQP message on the IP network between AP and ANQP Server. Then 91 the problem of configuring the ANQP server address on the AP arises. 93 This document defines a DHCPv4 option and DHCPv6 option of the ANQP 94 server addresses. As introduced above, these options are used to 95 configure the ANQP server addresses on the APs. This document also 96 defines the "Advertisement Protocol Type" field in the DHCPv4/v6 97 options which can be extended to configure other types of 98 advertisement protocols servers. 100 1.1. Requirements Language 102 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 103 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 104 document are to be interpreted as described in RFC 2119 [RFC2119]. 106 2. Terminology 108 ANQP: Access Network Query Protocol. ANQP is an example of a query 109 protocol for access network information retrieval transported by 110 Generic Advertisement Service (GAS) Public Action frames defined in 111 IEEE 802.11. ANQP message exchanges happen before network 112 association. ANQP is defined in the IEEE 802.11 specification and 113 has been further extended by the Wi-Fi Alliance. 115 ANQP Server: ANQP Server is the network entity that terminates and 116 responds to ANQP enquiries. In a scalable deployment, the ANQP 117 Server is placed in centralized device and administrated by the Wi-Fi 118 server provider. 120 IEEE 802.11u: IEEE 802.11u-2011 is an amendment to the IEEE 802.11- 121 2007 standard that added features that improve interworking with 122 external networks. It is now incorporated within IEEE 802.11-2012. 123 A key amendment to IEEE 802.11-2012 is the capability of WLAN client 124 network discovery and selection. 126 Passpoint: Wi-Fi Alliance Certified Program Name. The technical 127 specification of Passpoint is based on the output of the WFA Hotspot 128 2.0 (HS2.0) Technical Task Group. HS2.0 defines further vendor 129 specific ANQP options and has developed a test plan for Passpoint 130 certification. 132 RLQP: Registered Location Query Protocol. This is an additional 133 advertisement protocol defined by IEEE 802.11af [RLQP] (TV White 134 Spaces), which assists with location information, but operates as a 135 separate RLQP Server. The RLQP Server and ANQP Server may be co- 136 located. 138 3. DHCPv4 Option of ANQP Server Address 140 This section describes the ANQP Server Address Option for DHCPv4. 141 The option layout is depicted below Figure 1: 143 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 144 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 145 | Option Code | Length_1 | 146 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 147 | Type | Length_2 | IPv4 Address (0-15) | 148 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 149 | IPv4 Address (16-31) | | 150 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 151 . | 152 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 154 Figure 1: ANQP Server Address Option for DHCPv4 156 Option Code: OPTION-IPv4_Address-Adv-Server 158 Length_1 Length (in bytes) of the option excluding the 'Option Code' 159 and the 'Length_1' fields; 161 Type (Advertisement Server Type): Indicates the type of the 162 advertisement server. There are different advertisement servers 163 defined in 802.11, including ANQP and RLQP. The values of those 164 server types are discussed in Section 5. 166 Length_2: Length (in bytes) of the IPv4 addresses of the 167 advertisement server; its value equals four times of the number of 168 IPv4 addresses (4*N); 170 IP Address: IPv4 address(es) of ANQP server(s) 172 Note: Length_2 is necessary because there are multiple types of 173 advertisement servers and each has different number of IPv4 addresses 174 configured. 176 4. DHCPv6 Option of ANQP Server Address 178 This section describes the ANQP Server Address Option for DHCPv6. 179 The option layout is depicted below Figure 2: 181 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 182 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 183 | Option Code | Length_1 | 184 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 185 | Type | Length_2 | IPv6 Address (0-15) | 186 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 187 | | 188 | IPv6 Address(16-127) | 189 | _______________________________| 190 | | 191 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 193 Figure 2: ANQP Server Address Option for DHCPv6 195 Option Code: OPTION-IPv6_Address-Adv-Server 197 Length_1: Length (in bytes) of the option excluding the 'Option 198 Code' and the 'Length_1' fields; 200 Type (Advertisement Server Type): Indicates the type of the 201 advertisement server. There are different advertisement servers 202 defined in 802.11, including ANQP and RLQP. The values of those 203 server types are discussed in Section 5. 205 Length_2: Length (in bytes) of the IPv6 addresses of the 206 advertisement server; its value equals 16 times of the number of 207 IPv6 addresses (16*N); 209 IP address: IPv6 address(es) of ANQP server(s) 211 Note: Length_2 is necessary because there are multiple types of 212 advertisement servers and each has different number of IPv6 addresses 213 configured. 215 5. Advertisement Server Type 217 There are different types of advertisement servers defined in 802.11, 218 including ANQP Server and RLQP Server. IEEE may define other 219 advertisement servers in future. To make options defined in this 220 document scalable to further extensions, and also avoid the need of 221 an individual option code for each of such advertisement servers, 222 this document defines the Avertisement Server Type field in both the 223 DHCPv4 and DHCPv6 options. 225 The Advertisement Server Type value of ANQP is suggested in this 226 document as below. 227 +-----------+---------------+ 228 | Type | Value | 229 +-----------+---------------+ 230 | Reserved | 0 | 231 +-----------+---------------+ 232 | ANQP | 1 | 233 +-----------+---------------+ 234 | Reserved | 2-255 | 235 +-----------+---------------+ 237 In addition to ANQP, other advertisement protocols have been defined 238 within IEEE 802.11 (e.g. RLQP). These operate in a similar manner 239 to ANQP, but allow information exchange with different servers than 240 that of the ANQP Server. The Advertisement Server Type value of 241 other protocols including RLQP will be extended by future work. 243 6. IANA Considerations 245 This document has the following requests to the IANA. 247 Option Code for OPTION-IPv4_Address-Adv-Server in DHCPv4, as defined 248 in Section. 3 of this document. 250 Option Code for OPTION-IPv6_Address-Adv-Server in DHCPv6, as defined 251 in Section. 4 of this document. 253 Advertisement Server Type for ANQP, as defined in Section. 5 or this 254 document. 256 7. Security Considerations 258 If adversaries are able forge rogue ANQP Server options, the ANQP 259 messages will be directed to wrong servers and bogus information 260 about the queried access network would be injected. The DHCP 261 authentication option described in [RFC3315] and [RFC3118] MAY be 262 used to mitigate the above attacks. Lower layer security such as L2 263 traffic filtering and firewall SHOULD be configured prevent such 264 attacks. 266 8. References 268 8.1. Normative References 270 [IEEE-ELEVENU] 271 IEEE, "IEEE 802.11u Specification", 2011, . 274 [PASSPOINT] 275 Wi-Fi Alliance, "Wi-Fi CERTIFIED Passpoint", 2012, . 279 [RLQP] "Wireless LAN in the TV White Space", 2012, 280 . 282 8.2. Informative References 284 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 285 Requirement Levels", BCP 14, RFC 2119, March 1997. 287 [RFC3118] Droms, R. and W. Arbaugh, "Authentication for DHCP 288 Messages", RFC 3118, June 2001. 290 [RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., 291 and M. Carney, "Dynamic Host Configuration Protocol for 292 IPv6 (DHCPv6)", RFC 3315, July 2003. 294 Authors' Addresses 296 Zhen Cao 297 China Mobile 298 Xuanwumenxi Ave. No. 32 299 Beijing, 100871 300 China 302 Phone: +86-10-52686688 303 Email: zehn.cao@gmail.com, caozhen@chinamobile.com 305 Tao Sun 306 China Mobile 307 Xuanwumenxi Ave. No. 32 308 Beijing, 100871 309 China 311 Phone: +86-10-52686688 312 Email: suntao@chinamobile.com 314 Stephen McCann 315 Research in Motion 316 200 Bath Road 317 Slough, SL1 3XE, 318 United Kingdom 320 Phone: +44 1754 66700 321 Fax: 322 Email: smccann@rim.com 323 URI: