idnits 2.17.1 draft-ietf-radext-ieee802ext-05.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 : ---------------------------------------------------------------------------- -- The draft header indicates that this document updates RFC4072, but the abstract doesn't seem to directly say this. It does mention RFC4072 though, so this could be OK. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year (Using the creation date from RFC4072, updated by this document, for RFC5378 checks: 2002-06-24) -- The document seems to contain a disclaimer for pre-RFC5378 work, and may have content which was first submitted before 10 November 2008. The disclaimer is necessary when there are original authors that you have been unable to contact, or if some do not wish to grant the BCP78 rights to the IETF Trust. If you are able to get all authors (current and original) to grant those rights, you can and should remove the disclaimer; otherwise, the disclaimer is needed and you can ignore this comment. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (17 April 2013) is 4027 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) -- Looks like a reference, but probably isn't: '1' on line 226 -- Looks like a reference, but probably isn't: '2' on line 238 -- Looks like a reference, but probably isn't: '3' on line 246 -- Possible downref: Non-RFC (?) normative reference: ref. 'IEEE-802' -- Possible downref: Non-RFC (?) normative reference: ref. 'IEEE-802.11' -- Possible downref: Non-RFC (?) normative reference: ref. 'IEEE-802.11ad' -- Possible downref: Non-RFC (?) normative reference: ref. 'IEEE-802.1X' -- Possible downref: Non-RFC (?) normative reference: ref. 'ISO-639' -- Possible downref: Non-RFC (?) normative reference: ref. 'ISO-14962-1997' -- Obsolete informational reference (is this intentional?): RFC 4005 (Obsoleted by RFC 7155) Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 13 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 RADEXT Working Group Bernard Aboba 3 INTERNET-DRAFT Skype 4 Category: Proposed Standard Jouni Malinen 5 Expires: October 21, 2013 Devicescape Software 6 Updates: 4072 Paul Congdon 7 Hewlett Packard Company 8 Joseph Salowey 9 Cisco Systems 10 Mark Jones 11 Azuca Systems 12 17 April 2013 14 RADIUS Attributes for IEEE 802 Networks 15 draft-ietf-radext-ieee802ext-05.txt 17 Abstract 19 RFC 3580 provides guidelines for the use of the Remote Authentication 20 Dialin User Service (RADIUS) within IEEE 802 local area networks 21 (LANs). This document proposes additional attributes for use within 22 IEEE 802 networks, as well as clarifications on the usage of the EAP- 23 Key-Name attribute, updating RFC 4072. The attributes defined in 24 this document are usable both within RADIUS and Diameter. 26 Status of This Memo 28 This Internet-Draft is submitted in full conformance with the 29 provisions of BCP 78 and BCP 79. 31 Internet-Drafts are working documents of the Internet Engineering 32 Task Force (IETF), its areas, and its working groups. Note that 33 other groups may also distribute working documents as Internet- 34 Drafts. 36 Internet-Drafts are draft documents valid for a maximum of six months 37 and may be updated, replaced, or obsoleted by other documents at any 38 time. It is inappropriate to use Internet-Drafts as reference 39 material or to cite them other than as "work in progress." 41 The list of current Internet-Drafts can be accessed at 42 http://www.ietf.org/ietf/1id-abstracts.txt. 44 The list of Internet-Draft Shadow Directories can be accessed at 45 http://www.ietf.org/shadow.html. 47 This Internet-Draft will expire on October 21, 2013. 49 Copyright Notice 51 Copyright (c) 2013 IETF Trust and the persons identified as the 52 document authors. All rights reserved. 54 This document is subject to BCP 78 and the IETF Trust's Legal 55 Provisions Relating to IETF Documents 56 (http://trustee.ietf.org/license-info) in effect on the date of 57 publication of this document. Please review these documents 58 carefully, as they describe your rights and restrictions with respect 59 to this document. Code Components extracted from this document must 60 include Simplified BSD License text as described in Section 4.e of 61 the Trust Legal Provisions and are provided without warranty as 62 described in the Simplified BSD License. 64 This document may contain material from IETF Documents or IETF 65 Contributions published or made publicly available before November 66 10, 2008. The person(s) controlling the copyright in some of this 67 material may not have granted the IETF Trust the right to allow 68 modifications of such material outside the IETF Standards Process. 69 Without obtaining an adequate license from the person(s) controlling 70 the copyright in such materials, this document may not be modified 71 outside the IETF Standards Process, and derivative works of it may 72 not be created outside the IETF Standards Process, except to format 73 it for publication as an RFC or to translate it into languages other 74 than English. 76 Table of Contents 78 1. Introduction .......................................... 4 79 1.1 Terminology ..................................... 4 80 1.2 Requirements Language ........................... 5 81 2. RADIUS attributes ..................................... 5 82 2.1 Allowed-Called-Station-Id ....................... 5 83 2.2 EAP-Key-Name .................................... 7 84 2.3 EAP-Peer-Id ..................................... 8 85 2.4 EAP-Server-Id ................................... 9 86 2.5 Mobility-Domain-Id .............................. 10 87 2.6 Preauth-Timeout ................................. 10 88 2.7 Network-Id-Name ................................. 11 89 2.8 Access-Info ..................................... 13 90 2.9 WLAN-SSID ....................................... 13 91 2.10 WLAN-HESSID ..................................... 14 92 2.11 WLAN-Venue-Info ................................. 15 93 2.12 WLAN-Venue-Language ............................. 16 94 2.13 WLAN-Venue-Name ................................. 16 95 2.14 WLAN-Reason-Code ................................ 17 96 2.15 WLAN-Pairwise-Cipher ............................ 18 97 2.16 WLAN-Group-Cipher ............................... 19 98 2.17 WLAN-AKM-Suite .................................. 19 99 2.18 WLAN-Group-Mgmt-Cipher .......................... 20 100 2.19 WLAN-RF-Band .................................... 21 101 3. Table of attributes ................................... 22 102 4. Diameter Considerations ............................... 23 103 5. IANA Considerations ................................... 25 104 6. Security Considerations ............................... 26 105 7. References ............................................ 26 106 7.1 Normative References .................................. 26 107 7.2 Informative References ................................ 27 108 ACKNOWLEDGMENTS .............................................. 28 109 AUTHORS' ADDRESSES ........................................... 28 110 1. Introduction 112 In situations where it is desirable to centrally manage 113 authentication, authorization and accounting (AAA) for IEEE 802 114 [IEEE-802] networks, deployment of a backend authentication and 115 accounting server is desirable. In such situations, it is expected 116 that IEEE 802 authenticators will function as AAA clients. 118 "IEEE 802.1X Remote Authentication Dial In User Service (RADIUS) 119 Usage Guidelines" [RFC3580] defined guidelines for the use of the 120 Remote Authentication Dialin User Service (RADIUS) within networks 121 utilizing IEEE 802 local area networks. This document defines 122 additional attributes suitable for usage by IEEE 802 authenticators 123 acting as AAA clients. The attributes defined in this document are 124 usable both within RADIUS and Diameter. 126 1.1. Terminology 128 This document uses the following terms: 130 Access Point (AP) 131 A Station that provides access to the distribution 132 services via the wireless medium for associated Stations. 134 Association The service used to establish Access Point/Station 135 mapping and enable Station invocation of the distribution 136 system services. 138 authenticator An authenticator is an entity that require authentication 139 from the supplicant. The authenticator may be connected 140 to the supplicant at the other end of a point-to-point 141 LAN segment or wireless link. 143 authentication server 144 An authentication server is an entity that provides an 145 authentication service to an authenticator. This service 146 verifies from the credentials provided by the supplicant, 147 the claim of identity made by the supplicant. 149 Station (STA) Any device that contains an IEEE 802.11 conformant medium 150 access control (MAC) and physical layer (PHY) interface 151 to the wireless medium (WM). 153 Supplicant A supplicant is an entity that is being authenticated by 154 an authenticator. The supplicant may be connected to the 155 authenticator at one end of a point-to-point LAN segment 156 or 802.11 wireless link. 158 1.2. Requirements Language 160 In this document, several words are used to signify the requirements 161 of the specification. The key words "MUST", "MUST NOT", "REQUIRED", 162 "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", 163 and "OPTIONAL" in this document are to be interpreted as described in 164 [RFC2119]. 166 2. RADIUS attributes 168 2.1. Allowed-Called-Station-Id 170 Description 172 The Allowed-Called-Station-Id Attribute allows the RADIUS server 173 to specify the authenticator MAC addresses and/or networks to 174 which the user is allowed to connect. One or more Allowed-Called- 175 Station-Id attributes MAY be included in an Access-Accept or CoA- 176 Request packet. 178 A summary of the Allowed-Called-Station-Id Attribute format is 179 shown below. The fields are transmitted from left to right. 181 0 1 2 3 182 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 183 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 184 | Type | Length | String... 185 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 187 Code 189 TBD1 191 Length 193 >=3 195 String 197 The String field is one or more octets, containing the layer 2 198 endpoint that the user's call is allowed to be terminated on, as 199 specified in the definition of Called-Station-Id in [RFC2865] 200 Section 5.30 and [RFC3580] Section 3.20. In the case of IEEE 802, 201 the Allowed-Called-Station-Id Attribute is used to store the 202 Medium Access Control (MAC) address in ASCII format (upper case 203 only), with octet values separated by a "-". Example: 204 "00-10-A4-23-19-C0". Where restrictions on both the network and 205 authenticator MAC address usage are intended, the network name 206 MUST be appended to the authenticator MAC address, separated from 207 the MAC address with a ":". Example: "00-10-A4-23-19-C0:AP1". 208 Where no MAC address restriction is intended, the MAC address 209 field MUST be omitted, but ":" and the network name field MUST be 210 included. Example: ":AP1". Within IEEE 802.11 [IEEE-802.11], the 211 SSID constitutes the network name; within IEEE 802.1X 212 [IEEE-802.1X], the Network-Id Name (NID-Name) constitutes the 213 network name. Since a NID-Name can be up to 253 octets in length, 214 when used with [IEEE-802.1X], there may not be sufficient room 215 within the Allowed-Called-Station-Id Attribute to include a MAC 216 address. 218 If the user attempts to connect to the NAS from a Called-Station- 219 Id that does not match one of the Allowed-Called-Station-Id 220 attributes, then the user MUST NOT be permitted to access the 221 network. 223 The Allowed-Called-Station-Id Attribute can be useful in the 224 following situations: 226 [1] Where users can connect to a NAS without an Access-Request being 227 sent by the NAS to the RADIUS server (e.g. where key caching is 228 supported within IEEE 802.11 or IEEE 802.1X [IEEE-802.1X]). To 229 ensure that an attacker cannot gain entry to a network they have 230 not authenticated to, key cache entries are typically only 231 usable within the network to which the user originally 232 authenticated (e.g. the originally selected network name is 233 implicitly attached to the key cache entry). Also, if it is 234 desired that access to a network name not be available from a 235 particular authenticator MAC address, then the authenticator can 236 be set up not to advertise that particular network name. 238 [2] Where pre-authentication may be supported (e.g. IEEE 802.1X 239 pre-authentication). In this situation, the network name 240 typically will not be included in a Called-Station-Id Attribute 241 within the Access-Request, so that the RADIUS server will not 242 know the network that the user is attempting to access. As a 243 result, the RADIUS server may desire to restrict the networks to 244 which the user can subsequently connect. 246 [3] Where the network portion of the Called-Station-Id is present 247 within an Access-Request, the RADIUS server can desire to 248 authorize access to a network different from the one that the 249 user selected. 251 2.2. EAP-Key-Name 253 Description 255 The EAP-Key-Name Attribute, defined in "Diameter Extensible 256 Authentication Protocol (EAP) Application" [RFC4072], contains the 257 EAP Session-Id, as described in "Extensible Authentication 258 Protocol (EAP) Key Management Framework" [RFC5247]. Exactly how 259 this Attribute is used depends on the link layer in question. 261 It should be noted that not all link layers use this name. An 262 EAP-Key-Name Attribute MAY be included within Access-Request, 263 Access-Accept and CoA-Request packets. A summary of the EAP-Key- 264 Name Attribute format is shown below. The fields are transmitted 265 from left to right. 267 0 1 2 3 268 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 269 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 270 | Type | Length | String... 271 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 273 Code 275 102 [RFC4072] 277 Length 279 >=3 281 String 283 The String field is one or more octets, containing the EAP 284 Session-Id, as defined in "Extensible Authentication Protocol 285 (EAP) Key Management Framework" [RFC5247]. Since the NAS operates 286 as a pass-through in EAP, it cannot know the EAP Session-Id before 287 receiving it from the RADIUS server. As a result, an EAP-Key-Name 288 Attribute sent in an Access-Request MUST only contain a single NUL 289 character. A RADIUS server receiving an Access-Request with an 290 EAP-Key-Name Attribute containing anything other than a single NUL 291 character MUST silently discard the Attribute. In addition, the 292 RADIUS server SHOULD include this Attribute in an Access-Accept or 293 CoA-Request only if an EAP-Key-Name Attribute was present in the 294 Access-Request. Since a NAS will typically only include a EAP- 295 Key-Name Attribute in an Access-Request in situations where the 296 Attribute is required to provision service, if an EAP-Key-Name 297 Attribute is included in an Access-Request but is not present in 298 the Access-Accept, the NAS SHOULD treat the Access-Accept as 299 though it were an Access-Reject. If an EAP-Key-Name Attribute was 300 not present in the Access-Request but is included in the Access- 301 Accept, then the NAS SHOULD silently discard the EAP-Key-Name 302 Attribute. 304 2.3. EAP-Peer-Id 306 Description 308 The EAP-Peer-Id Attribute contains a Peer-Id generated by the EAP 309 method. Exactly how this name is used depends on the link layer 310 in question. See [RFC5247] for more discussion. The EAP-Peer-Id 311 Attribute MAY be included in Access-Request, Access-Accept and 312 Accounting-Request packets. More than one EAP-Peer-Id Attribute 313 MUST NOT be included in an Access-Request; one or more EAP-Peer-Id 314 attributes MAY be included in an Access-Accept. 316 It should be noted that not all link layers use this name, and 317 existing EAP method implementations do not generate it. Since the 318 NAS operates as a pass-through in EAP [RFC3748], it cannot know 319 the EAP-Peer-Id before receiving it from the RADIUS server. As a 320 result, an EAP-Peer-Id Attribute sent in an Access-Request MUST 321 only contain a single NUL character. A home RADIUS server 322 receiving an Access-Request an EAP-Peer-Id Attribute containing 323 anything other than a single NUL character MUST silently discard 324 the Attribute. In addition, the home RADIUS server SHOULD include 325 one or more EAP-Peer-Id attributes in an Access-Accept only if an 326 EAP-Peer-Id Attribute was present in the Access-Request. If a NAS 327 receives EAP-Peer-Id Attribute(s) in an Access-Accept without 328 having included one in an Access-Request, the NAS SHOULD silently 329 discard the Attribute(s). A summary of the EAP-Peer-Id Attribute 330 format is shown below. The fields are transmitted from left to 331 right. 333 0 1 2 3 334 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 335 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 336 | Type | Length | String... 337 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 339 Code 341 TBD2 343 Length 345 >=3 347 String 349 The String field is one or more octets containing a EAP Peer-Id 350 exported by the EAP method. For details, see [RFC5247] Appendix 351 A. A robust implementation SHOULD support the field as 352 undistinguished octets. Only a single EAP Peer-Id may be included 353 per Attribute. 355 2.4. EAP-Server-Id 357 Description 359 The EAP-Server-Id Attribute contains a Server-Id generated by the 360 EAP method. Exactly how this name is used depends on the link 361 layer in question. See [RFC5247] for more discussion. The EAP- 362 Server-Id Attribute is only allowed in Access-Request, Access- 363 Accept, and Accounting-Request packets. More than one EAP-Server- 364 Id Attribute MUST NOT be included in an Access-Request; one or 365 more EAP-Server-Id attributes MAY be included in an Access-Accept. 367 It should be noted that not all link layers use this name, and 368 existing EAP method implementations do not generate it. Since the 369 NAS operates as a pass-through in EAP [RFC3748], it cannot know 370 the EAP-Server-Id before receiving it from the RADIUS server. As 371 a result, an EAP-Server-Id Attribute sent in an Access-Request 372 MUST contain only a single NUL character. A home RADIUS server 373 receiving in an Access-Request an EAP-Server-Id Attribute 374 containing anything other than a single NUL character MUST 375 silently discard the Attribute. In addition, the home RADIUS 376 server SHOULD include this Attribute an Access-Accept only if an 377 EAP-Server-Id Attribute was present in the Access-Request. A 378 summary of the EAP-Server-Id Attribute format is shown below. The 379 fields are transmitted from left to right. 381 0 1 2 3 382 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 383 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 384 | Type | Length | String... 385 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 387 Code 389 TBD3 391 Length 393 >=3 395 String 397 The String field is one or more octets, containing a EAP Server-Id 398 exported by the EAP method. For details, see [RFC5247] Appendix 399 A. A robust implementation SHOULD support the field as 400 undistinguished octets. 402 2.5. Mobility-Domain-Id 404 Description 406 A single Mobility-Domain-Id Attribute MAY be included in an 407 Access-Request or Accounting-Request, in order to enable the NAS 408 to provide the RADIUS server with the Mobility Domain Identifier 409 (MDID), defined in IEEE 802.11 [IEEE-802.11]. A summary of the 410 Mobility-Domain-Id Attribute format is shown below. The fields 411 are transmitted from left to right. 413 0 1 2 3 414 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 415 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 416 | Type | Length | Value 417 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 418 Value | 419 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 421 Code 423 TBD4 425 Length 427 6 429 Value 431 The Value field is four octets, containing a 32-bit unsigned 432 integer. Since the Mobility Domain Identifier defined in IEEE 433 802.11 [IEEE-802.11] is only two octets in length, the two most 434 significant octets MUST be set to zero by the sender, and are 435 ignored by the receiver; the two least significant octets contain 436 the MDID value. 438 2.6. Preauth-Timeout 440 Description 442 This Attribute sets the maximum number of seconds which pre- 443 authentication state is required to be kept by the NAS, without 444 being utilized within a user session. For example, when 445 [IEEE-802.11] pre-authentication is used, if a user has not 446 attempted to utilize the Pairwise Master Key (PMK) derived as a 447 result of pre-authentication within the time specified by the 448 Preauth-Timeout Attribute, the PMK MAY be discarded by the Access 449 Point. However, once the session is underway, the Preauth-Timeout 450 Attribute has no bearing on the maximum session time for the user, 451 or the maximum time during which key state may be kept prior to 452 re-authentication. This is determined by the Session-Timeout 453 Attribute, if present. 455 This Attribute MAY be sent by the server to the NAS in an Access- 456 Accept. A summary of the Preauth-Timeout Attribute format is 457 shown below. The fields are transmitted from left to right. 459 0 1 2 3 460 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 461 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 462 | Type | Length | Value 463 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 464 Value (cont) | 465 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 467 Code 469 TBD5 471 Length 473 6 475 Value 477 The field is 4 octets, containing a 32-bit unsigned integer 478 encoding the maximum time in seconds that pre-authentication state 479 should be retained by the NAS. 481 2.7. Network-Id-Name 483 Description 485 The Network-Id-Name Attribute is utilized by implementations of 486 IEEE-802.1X [IEEE-802.1X] to specify the name of a Network-Id 487 (NID-Name). 489 Unlike the IEEE 802.11 SSID (which is a maximum of 32 octets in 490 length), the NID-Name may be up to 253 octets in length. 492 Consequently, if the MAC address is included within the Called- 493 Station-Id Attribute, it is possible that there will not be enough 494 remaining space to encode the NID-Name as well. Therefore when 495 used with IEEE 802.1X [IEEE-802.1X], the Called-Station-Id 496 Attribute SHOULD contain only the MAC address, with the Network- 497 Id-Name Attribute used to transmit the NID-Name. The Network-Id- 498 Name Attribute MUST NOT be used to encode the IEEE 802.11 SSID; as 499 noted in [RFC3580], the Called-Station-Id Attribute is used for 500 this purpose. 502 Zero or one Network-Id-Name Attribute is permitted within a RADIUS 503 Access-Request or Accounting-Request packet. When included within 504 an Access-Request packet, the Network-Id-Name Attribute represents 505 a hint of the NID-Name to which the Supplicant should be granted 506 access. In order to indicate which network names the Supplicant 507 is permitted to access, the Allowed-Called-Station-Id Attribute is 508 provided within an Access-Accept. When included within an 509 Accounting-Request packet, the Network-Id-Name Attribute 510 represents the NID-Name to which the Supplicant has been granted 511 access. 513 A summary of the Network-Id-Name Attribute format is shown below. 514 The fields are transmitted from left to right. 516 0 1 2 3 517 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 518 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 519 | Type | Length | String... 520 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 522 Code 524 TBD6 526 Length 528 >=3 530 String 532 The String field is one or more octets, containing a NID-Name. 533 For details, see [IEEE-802.1X]. A robust implementation SHOULD 534 support the field as undistinguished octets. 536 2.8. Access-Info 538 Description 540 The Access-Info Attribute is utilized by implementations of 541 IEEE-802.1X [IEEE-802.1X] to specify the Access status information 542 field within an Access Information Type Length Value Tuple (TLV) 543 to be sent to the user within MACsec Key Agreement (MKA) or EAPoL- 544 Announcement frames. 546 A single Access-Info Attribute is permitted within a RADIUS 547 Access-Accept, Access-Challenge, Access-Reject or Accounting- 548 Request packet. 550 A summary of the Access-Info Attribute format is shown below. The 551 fields are transmitted from left to right. 553 0 1 2 3 554 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 555 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 556 | Type | Length | Value 557 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 558 Value | 559 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 561 Code 563 TBD7 565 Length 567 6 569 Value 571 The Value field is four octets containing a 32-bit unsigned 572 integer. Since the Access status information field of the Access 573 Information TLV defined in [IEEE-802.1X] Section 11.12.2 is only 574 two octets in length, the two most significant octets of the Value 575 field MUST be set to zero by the sender and are ignored by the 576 receiver. 578 2.9. WLAN-SSID 580 Description 582 The WLAN-SSID attribute contains the Service Set Identifier (SSID) 583 which identifies a specific 802.11 extended service set (ESS). A 584 single WLAN-SSID Attribute is permitted within an Access-Accept or 585 Accounting-Request packet. 587 0 1 2 3 588 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 589 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 590 | Type | Length | String... 591 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 593 Code 595 TBD8 597 Length 599 3 to 34 601 String 603 The String field is between 1 and 32 octets in length. The actual 604 format of the information is site or application specific, and a 605 robust implementation MUST support the field as undistinguished 606 octets. 608 2.10. WLAN-HESSID 610 Description 612 The WLAN-HESSID attribute contains a MAC address that identifies 613 the Homogenous Extended Service Set. The HESSID is a globally 614 unique identifier that in conjunction with the WLAN-SSID, may be 615 used to provide network identification for a subscription service 616 provider network (SSPN), as described in [IEEE-802.11]. A single 617 WLAN-HESSID Attribute is permitted within an Access-Accept or 618 Accounting-Request packet. 620 0 1 2 3 621 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 622 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 623 | Type | Length | String... 624 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 626 Code 628 TBD9 630 Length 631 19 633 String 635 The String field is encoded in upper-case ASCII characters with 636 the octet values separated by dash characters, as described in 637 RFC3580 [RFC3580]. Example: "00-10-A4-23-19-C0". 639 2.11. WLAN-Venue-Info 641 Description 643 The WLAN-Venue-Info attribute identifies the category of venue 644 hosting the WLAN, as defined in Section 8.4.1.34 of [IEEE-802.11]. 646 0 1 2 3 647 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 648 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 649 | Type | Length | Value 650 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 651 Value | 652 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 654 Code 656 TBD10 658 Length 660 6 662 Value 664 The Value field is four octets, containing a 32-bit unsigned 665 integer. The two most significant octets MUST be set to zero by 666 the sender, and are ignored by the receiver; the two least 667 significant octets contain the Venue Group and Venue Type fields. 669 0 1 2 3 670 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 671 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 672 | Reserved | Venue Group | Venue Type | 673 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 675 Venue Group 677 The Venue Group field is a single octet and describes the broad 678 category of the venue, e.g. "Assembly". See Section 8.4.1.34 680 [IEEE-802.11] for Venue Group codes and descriptions. 682 Venue Type 684 The Venue Type field is a single octet and describes the venue in 685 a finer granularity within the Venue Group, e.g. "Library". See 686 Section 8.4.1.34 of [IEEE-802.11] for Venue Type codes and 687 descriptions. 689 2.12. WLAN-Venue-Language 691 Description 693 The WLAN-Venue-Language attribute is an ISO-14962-1997 694 [ISO-14962-1997] encoded string that defines the language used in 695 the WLAN-Venue-Name attribute. Zero or more WLAN-Venue-Language 696 attributes may be included in an Access-Request or Accounting- 697 Request and each one indicates the language of the WLAN-Venue-Name 698 attribute that follows it. 700 0 1 2 3 701 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 702 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 703 | Type | Length | String... 704 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 705 String (cont) | 706 +-+-+-+-+-+-+-+-+ 708 Code 710 TBD11 712 Length 714 5 716 String 718 The String field is a two or three character language code 719 selected from ISO-639 [ISO-639]. A two character language code 720 has a zero ("null" in ISO-14962-1997) appended to make it 3 octets 721 in length. 723 2.13. WLAN-Venue-Name 725 Description 727 The WLAN-Venue-Name attribute provides additional metadata on the 728 BSS. For example, this information may be used to assist a user 729 in selecting the appropriate BSS with which to associate. Zero or 730 more WLAN-Venue-Name attributes may be included in an Access- 731 Request or Accounting-Request in the same or different languages. 733 0 1 2 3 734 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 735 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 736 | Type | Length | String... 737 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 739 Code 741 TBD12 743 Length 745 >=3 747 String 749 The String field is a UTF-8 formatted field containing the venue's 750 name. The maximum length of this field is 252 octets. 752 2.14. WLAN-Reason-Code 754 Description 756 The WLAN-Reason-Code Attribute contains information on the reason 757 why a station has been refused network access and has been 758 disassociated or de-authenticated. This can occur due to policy 759 or for reasons related to the user's subscription. 761 A WLAN-Reason-Code Attribute MAY be included within an Access- 762 Reject or Disconnect-Request packet, as well as within an 763 Accounting-Request packet. Upon receipt of an Access-Reject or 764 Disconnect-Request packet containing a WLAN-Reason-Code Attribute, 765 the WLAN-Reason-Code value is copied by the Access Point into the 766 Reason Code field of a Disassociation or Deauthentication frame 767 (see clause 8.3.3.4 and 8.3.3.12 respectively in [IEEE- 802.11]), 768 which is subsequently transmitted to the station. 770 A summary of the WLAN-Reason-Code Attribute format is shown below. 771 The fields are transmitted from left to right. 773 0 1 2 3 774 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 775 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 776 | Type | Length | Value 777 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 778 Value | 779 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 781 Code 783 TBD13 785 Length 787 6 789 Value 791 The Value field is a 32-bit unsigned integer drawn from Table 8-36 792 (Reason Codes) in clause 8.4.1.7 of [IEEE-802.11]. 794 2.15. WLAN-Pairwise-Cipher 796 Description 798 The WLAN-Pairwise-Cipher Attribute contains information on the 799 pairwise cipher suite used to establish the robust security 800 network association (RSNA) between the AP and mobile device. 802 A WLAN-Pairwise-Cipher Attribute MAY be included within Access- 803 Request and Accounting-Request packets. A summary of the WLAN- 804 Pairwise-Cipher Attribute format is shown below. 806 The fields are transmitted from left to right. 808 0 1 2 3 809 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 810 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 811 | Type | Length | Value 812 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 813 Value | 814 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 816 Code 818 TBD14 820 Length 822 6 824 Value 826 The Value field is four octets formatted in accordance with Figure 827 8-187 with values drawn from Table 8-99 of [IEEE-802.11]. 829 2.16. WLAN-Group-Cipher 831 Description 833 The WLAN-Group-Cipher Attribute contains information on the group 834 cipher suite used to establish the robust security network 835 association (RSNA) between the AP and mobile device. 837 A WLAN-Group-Cipher Attribute MAY be included within Access- 838 Request and Accounting-Request packets. A summary of the WLAN- 839 Group-Cipher Attribute format is shown below. The fields are 840 transmitted from left to right. 842 0 1 2 3 843 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 844 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 845 | Type | Length | Value 846 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 847 Value | 848 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 850 Code 852 TBD15 854 Length 856 6 858 Value 860 The Value field is four octets formatted in accordance with Figure 861 8-187 with values drawn from Table 8-99 of [IEEE-802.11]. 863 2.17. WLAN-AKM-Suite 865 Description 867 The WLAN-AKM-Suite Attribute contains information on the 868 authentication and key management suite used to establish the 869 robust security network association (RSNA) between the AP and 870 mobile device. 872 A WLAN-AKM-Suite Attribute MAY be included within Access-Request 873 and Accounting-Request packets. A summary of the WLAN-AKM-Suite 874 Attribute format is shown below. The fields are transmitted from 875 left to right. 877 0 1 2 3 878 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 879 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 880 | Type | Length | Value 881 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 882 Value | 883 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 885 Code 887 TBD16 889 Length 891 6 893 Value 895 The Value field is four octets formatted in accordance with Figure 896 8-187 with values drawn from Table 8-101 of [IEEE-802.11]. 898 2.18. WLAN-Group-Mgmt-Cipher 900 Description 902 The WLAN-Group-Mgmt-Cipher Attribute contains information on group 903 management cipher used to establish the robust security network 904 association (RSNA) between the AP and mobile device. 906 A WLAN-Group-Mgmt-Cipher Attribute MAY be included within Access- 907 Request and Accounting-Request packets. Presence of the attribute 908 indicates that the station negotiated to use management frame 909 protection during association. 911 A summary of the WLAN-Group-Mgmt-Cipher Attribute format is shown 912 below. The fields are transmitted from left to right. 914 0 1 2 3 915 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 916 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 917 | Type | Length | Value 918 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 919 Value | 921 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 923 Code 925 TBD17 927 Length 929 6 931 Value 933 The Value field is four octets formatted in accordance with Figure 934 8-187 with values drawn from Table 8-99 of [IEEE-802.11]. 936 2.19. WLAN-RF-Band 938 Description 940 The WLAN-RF-Band Attribute contains information on the RF band 941 used by the Access Point for transmission and reception of 942 information to and from the mobile device. 944 A WLAN-RF-Band Attribute MAY be included within Access-Request and 945 Accounting-Request packets. A summary of the WLAN-RF-Band 946 Attribute format is shown below. The fields are transmitted from 947 left to right. 949 0 1 2 3 950 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 951 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 952 | Type | Length | Value 953 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 954 Value | 955 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 957 Code 959 TBD18 961 Length 963 6 965 Value 967 The Value field is four octets, containing a 32-bit unsigned 968 integer. The three most significant octets MUST be set to zero by 969 the sender, and are ignored by the receiver; the least significant 970 octet contains the RF Band field, whose values are defined in 971 Table 8-53a of [IEEE-802.11ad]. 973 0 1 2 3 974 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 975 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 976 | Reserved | RF Band | 977 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 979 3. Table of attributes 981 The following table provides a guide to which attributes may be found 982 in which kinds of packets, and in what quantity. 984 Access- Access- Access- Access- 985 Request Accept Reject Challenge # Attribute 986 0 0+ 0 0 TBD1 Allowed-Called-Station-Id 987 0-1 0-1 0 0 102 EAP-Key-Name 988 0-1 0+ 0 0 TBD2 EAP-Peer-Id 989 0-1 0+ 0 0 TBD3 EAP-Server-Id 990 0-1 0 0 0 TBD4 Mobility-Domain-Id 991 0-1 0-1 0 0 TBD5 Preauth-Timeout 992 0-1 0 0 0 TBD6 Network-Id-Name 993 0 0-1 0-1 0-1 TBD7 Access-Info 994 0-1 0 0 0 TBD8 WLAN-SSID 995 0-1 0 0 0 TBD9 WLAN-HESSID 996 0-1 0 0 0 TBD10 WLAN-Venue-Info 997 0+ 0 0 0 TBD11 WLAN-Venue-Language 998 0+ 0 0 0 TBD12 WLAN-Venue-Name 999 0 0 0-1 0 TBD13 WLAN-Reason-Code 1000 0-1 0 0 0 TBD14 WLAN-Pairwise-Cipher 1001 0-1 0 0 0 TBD15 WLAN-Group-Cipher 1002 0-1 0 0 0 TBD16 WLAN-AKM-Suite 1003 0-1 0 0 0 TBD17 WLAN-Group-Mgmt-Cipher 1004 0-1 0 0 0 TBD18 WLAN-RF-Band 1005 CoA- Dis- Acct- 1006 Req Req Req # Attribute 1007 0+ 0 0 TBD1 Allowed-Called-Station-Id 1008 0-1 0 0 102 EAP-Key-Name 1009 0 0 0+ TBD2 EAP-Peer-Id 1010 0 0 0+ TBD3 EAP-Server-Id 1011 0 0 0-1 TBD4 Mobility-Domain-Id 1012 0 0 0 TBD5 Preauth-Timeout 1013 0 0 0-1 TBD6 Network-Id-Name 1014 0-1 0 0-1 TBD7 Access-Info 1015 0 0 0-1 TBD8 WLAN-SSID 1016 0 0 0-1 TBD9 WLAN-HESSID 1017 0 0 0-1 TBD10 WLAN-Venue-Info 1018 0 0 0+ TBD11 WLAN-Venue-Language 1019 0 0 0+ TBD12 WLAN-Venue-Name 1020 0 0-1 0-1 TBD13 WLAN-Reason-Code 1021 0 0 0-1 TBD14 WLAN-Pairwise-Cipher 1022 0 0 0-1 TBD15 WLAN-Group-Cipher 1023 0 0 0-1 TBD16 WLAN-AKM-Suite 1024 0 0 0-1 TBD17 WLAN-Group-Mgmt-Cipher 1025 0 0 0-1 TBD18 WLAN-RF-Band 1027 The following table defines the meaning of the above table entries. 1029 0 This Attribute MUST NOT be present in packet. 1030 0+ Zero or more instances of this Attribute MAY be 1031 present in the packet. 1032 0-1 Zero or one instance of this Attribute MAY be 1033 present in the packet. 1035 4. Diameter Considerations 1037 The EAP-Key-Name Attribute is already defined as a RADIUS Attribute 1038 within Diameter EAP [RFC4072]. When used in Diameter, the other 1039 attributes defined in this specification can be used as Diameter AVPs 1040 from the Code space 1-255 (RADIUS Attribute compatibility space). No 1041 additional Diameter Code values are therefore allocated. The data 1042 types and flag rules for the attributes are as follows: 1044 +---------------------+ 1045 | AVP Flag rules | 1046 |----+-----+----+-----|----+ 1047 | | |SHLD| MUST| | 1048 Attribute Name Value Type |MUST| MAY | NOT| NOT|Encr| 1049 -----------------------------------------|----+-----+----+-----|----| 1050 Allowed-Called-Station-Id UTF8String | M | P | | V | Y | 1051 EAP-Peer-Id UTF8String | M | P | | V | Y | 1052 EAP-Server-Id UTF8String | M | P | | V | Y | 1053 Mobility-Domain-Id Unsigned32 | M | P | | V | Y | 1054 Preauth-Timeout Unsigned32 | M | P | | V | Y | 1055 Network-Id-Name UTF8String | M | P | | V | Y | 1056 Access-Info Unsigned32 | M | P | | V | Y | 1057 WLAN-SSID UTF8String | M | P | | V | Y | 1058 WLAN-HESSID UTF8String | M | P | | V | Y | 1059 WLAN-Venue-Info Unsigned32 | M | P | | V | Y | 1060 WLAN-Venue-Language UTF8String | M | P | | V | Y | 1061 WLAN-Venue-Name UTF8String | M | P | | V | Y | 1062 WLAN-Reason-Code Unsigned32 | M | P | | V | Y | 1063 WLAN-Pairwise-Cipher Unsigned32 | M | P | | V | Y | 1064 WLAN-Group-Cipher Unsigned32 | M | P | | V | Y | 1065 WLAN-AKM-Suite Unsigned32 | M | P | | V | Y | 1066 WLAN-Group-Mgmt-Cipher Unsigned32 | M | P | | V | Y | 1067 WLAN-RF-Band Unsigned32 | M | P | | V | Y | 1068 -----------------------------------------|----+-----+----+-----|----| 1070 The attributes in this specification have no special translation 1071 requirements for Diameter to RADIUS or RADIUS to Diameter gateways; 1072 they are copied as is, except for changes relating to headers, 1073 alignment, and padding. 1075 What this specification says about the applicability of the 1076 attributes for RADIUS Access-Request packets applies in Diameter to 1077 AA-Request [RFC4005] or Diameter-EAP-Request [RFC4072]. What is said 1078 about Access-Challenge applies in Diameter to AA-Answer [RFC4005] or 1079 Diameter-EAP-Answer [RFC4072] with Result-Code AVP set to 1080 DIAMETER_MULTI_ROUND_AUTH. 1082 What is said about Access-Accept applies in Diameter to AA-Answer or 1083 Diameter-EAP-Answer messages that indicate success. Similarly, what 1084 is said about RADIUS Access-Reject packets applies in Diameter to AA- 1085 Answer or Diameter-EAP-Answer messages that indicate failure. 1087 What is said about COA-Request applies in Diameter to Re-Auth-Request 1088 [RFC4005]. What is said about Accounting-Request applies to Diameter 1089 Accounting- Request [RFC4005] as well. 1091 5. IANA Considerations 1093 This document uses the RADIUS [RFC2865] namespace, see 1094 . This specification 1095 requires assignment of a RADIUS attribute types for the following 1096 attributes: 1098 Attribute Type 1099 ========= ==== 1100 Allowed-Called-Station-Id TBD1 1101 EAP-Peer-Id TBD2 1102 EAP-Server-Id TBD3 1103 Mobility-Domain-Id TBD4 1104 Preauth-Timeout TBD5 1105 Network-Id-Name TBD6 1106 Access-Info TBD7 1107 WLAN-SSID TBD8 1108 WLAN-HESSID TBD9 1109 WLAN-Venue-Info TBD10 1110 WLAN-Venue-Language TBD11 1111 WLAN-Venue-Name TBD12 1112 WLAN-Reason-Code TBD13 1113 WLAN-Pairwise-Cipher TBD14 1114 WLAN-Group-Cipher TBD15 1115 WLAN-AKM-Suite TBD16 1116 WLAN-Group-Mgmt-Cipher TBD17 1117 WLAN-RF-Band TBD18 1119 6. Security Considerations 1121 Since this document describes the use of RADIUS for purposes of 1122 authentication, authorization, and accounting in IEEE 802 networks, 1123 it is vulnerable to all of the threats that are present in other 1124 RADIUS applications. For a discussion of these threats, see 1125 [RFC2607], [RFC2865], [RFC3162], [RFC3579], [RFC3580] and [RFC5176]. 1127 While it is possible for a RADIUS server to make decisions on whether 1128 to Accept or Reject an Access-Request based on the values of the 1129 WLAN-Pairwise-Cipher, WLAN-Group-Cipher, WLAN-AKM-Suite, WLAN-Group- 1130 Mgmt-Cipher and WLAN-RF-Band Attributes the value of doing this is 1131 limited. In general, an Access-Reject should not be necessary, 1132 except where Access Points and Stations are misconfigured so as to 1133 enable connections to be made with unacceptable values. Rather than 1134 rejecting access on an ongoing basis, users would be better served by 1135 fixing the misconfiguration. 1137 Where access does need to be rejected, the user should be provided 1138 with an indication of why the problem has occurred, or else they are 1139 likely to become frustrated. For example, if the values of the WLAN- 1140 Pairwise-Cipher, WLAN-Group-Cipher, WLAN-AKM-Suite or WLAN-Group- 1141 Mgmt-Cipher Attributes included in the Access-Request are not 1142 acceptable to the RADIUS server, then a WLAN-Reason-Code Attribute 1143 with a value of 29 (Requested service rejected because of service 1144 provider cipher suite or AKM requirement) SHOULD be returned in the 1145 Access-Reject. Similarly, if the value of the WLAN-RF-Band Attribute 1146 included in the Access-Request is not acceptable to the RADIUS 1147 server, then a WLAN-Reason-Code Attribute with a value of 11 1148 (Disassociated because the information in the Supported Channels 1149 element is unacceptable) SHOULD be returned in the Access-Reject. 1151 7. References 1153 7.1. Normative references 1155 [IEEE-802] IEEE Standards for Local and Metropolitan Area Networks: 1156 Overview and Architecture, ANSI/IEEE Std 802, 1990. 1158 [IEEE-802.11] 1159 Information technology - Telecommunications and Information 1160 Exchange Between Systems - Local and Metropolitan Area 1161 Networks - Specific Requirements Part 11: Wireless LAN 1162 Medium Access Control (MAC) and Physical Layer (PHY) 1163 Specifications, IEEE Std. 802.11-2012, 2012. 1165 [IEEE-802.11ad] 1166 Information technology - Telecommunications and Information 1167 Exchange Between Systems - Local and Metropolitan Area 1168 Networks - Specific Requirements Part 11: Wireless LAN 1169 Medium Access Control (MAC) and Physical Layer (PHY) 1170 Specifications, Amendment 3: Enhancements for Very High 1171 Throughput in the 60 GHz Band, IEEE Std. 802.11ad-2012, 2012. 1173 [IEEE-802.1X] 1174 IEEE Standard for Local and Metropolitan Area Networks - 1175 Port-Based Network Access Control, IEEE 802.1X-2010, February 1176 2010. 1178 [ISO-639] ISO, "Codes for the Representation of Names of Languages". 1180 [ISO-14962-1997] 1181 ISO, "Space data and information transfer systems - ASCII 1182 encoded English", 1997. 1184 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1185 Requirement Levels", RFC 2119, March, 1997. 1187 [RFC2865] Rigney, C., Rubens, A., Simpson, W. and S. Willens, "Remote 1188 Authentication Dial In User Service (RADIUS)", RFC 2865, June 1189 2000. 1191 [RFC4072] Eronen, P., Hiller, T. and G. Zorn, "Diameter Extensible 1192 Authentication Protocol (EAP) Application", RFC 4072, August 1193 2005. 1195 [RFC5247] Aboba, B., Simon, D. and P. Eronen, "EAP Key Management 1196 Framework", RFC 5247, August 2008. 1198 7.2. Informative references 1200 [RFC2607] Aboba, B. and J. Vollbrecht, "Proxy Chaining and Policy 1201 Implementation in Roaming", RFC 2607, June 1999. 1203 [RFC3162] Aboba, B., Zorn, G. and D. Mitton, "RADIUS and IPv6", RFC 1204 3162, August 2001. 1206 [RFC3579] Aboba, B. and P. Calhoun, "RADIUS Support for Extensible 1207 Authentication Protocol (EAP)", RFC 3579, September 2003. 1209 [RFC3580] Congdon, P., Aboba, B., Smith, A., Zorn, G. and J. Roese, 1210 "IEEE 802.1X Remote Authentication Dial In User Service 1211 (RADIUS) Usage Guidelines", RFC 3580, September 2003. 1213 [RFC3748] Aboba, B., Blunk, L., Vollbrecht, J., Carlson, J. and H. 1214 Levkowetz, "Extensible Authentication Protocol (EAP)", RFC 1215 3748, June 2004. 1217 [RFC4005] Calhoun, P., Zorn, G., Spence, D., and D. Mitton, "Diameter 1218 Network Access Server Application", RFC 4005, August 2005. 1220 [RFC5176] Chiba, M., Dommety, G., Eklund, M., Mitton, D. and B. Aboba, 1221 "Dynamic Authorization Extensions to Remote Authentication 1222 Dial In User Service (RADIUS)", RFC 5176, January 2008. 1224 Acknowledgments 1226 The authors would like to acknowledge Maximilian Riegel, Dorothy 1227 Stanley, Yoshihiro Ohba, and the contributors to the IEEE 802.1 and 1228 IEEE 802.11 reviews of this document, for useful discussions. 1230 Authors' Addresses 1232 Bernard Aboba 1233 Skype 1234 EMail: bernard_aboba@hotmail.com 1236 Jouni Malinen 1237 EMail: j@w1.fi 1239 Paul Congdon 1240 Hewlett Packard Company 1241 HP ProCurve Networking 1242 8000 Foothills Blvd, M/S 5662 1243 Roseville, CA 95747 1245 Phone: +1 916 785 5753 1246 Fax: +1 916 785 8478 1247 EMail: paul_congdon@hp.com 1249 Joseph Salowey 1250 Cisco Systems 1251 EMail: jsalowey@cisco.com 1253 Mark Jones 1254 Azuca Systems 1255 EMail: mark@azu.ca