idnits 2.17.1 draft-ietf-radext-ieee802ext-03.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 (21 October 2012) is 4176 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 == Missing Reference: 'Note' is mentioned on line 975, but not defined -- 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.1X' -- Possible downref: Non-RFC (?) normative reference: ref. 'ISO-639' -- Possible downref: Non-RFC (?) normative reference: ref. 'ISO-14962-1997' ** Obsolete normative reference: RFC 3588 (Obsoleted by RFC 6733) -- Obsolete informational reference (is this intentional?): RFC 4005 (Obsoleted by RFC 7155) Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 12 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 RADEXT Working Group Bernard Aboba 3 INTERNET-DRAFT Microsoft Corporation 4 Category: Proposed Standard Jouni Malinen 5 Expires: April 21, 2013 Devicescape Software 6 Updates: 4072 Paul Congdon 7 Hewlett Packard Company 8 Joseph Salowey 9 Cisco Systems 10 Mark Jones 11 Amdocs 12 21 October 2012 14 RADIUS Attributes for IEEE 802 Networks 15 draft-ietf-radext-ieee802ext-03.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 April 21, 2013. 49 Copyright Notice 51 Copyright (c) 2012 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 ..................................... 12 90 2.9 WLAN-SSID ....................................... 13 91 2.10 WLAN-HESSID ..................................... 14 92 2.11 WLAN-Venue-Info ................................. 14 93 2.12 WLAN-Venue-Language ............................. 15 94 2.13 WLAN-Venue-Name ................................. 16 95 2.14 WLAN-Reason-Codes ............................... 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 .............................................. 27 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 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 and 262 existing EAP method implementations do not generate it. An EAP- 263 Key-Name Attribute MAY be included within Access-Request, Access- 264 Accept and CoA-Request packets. A summary of the EAP-Key-Name 265 Attribute format is shown below. The fields are transmitted from 266 left to right. 268 0 1 2 3 269 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 270 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 271 | Type | Length | String... 272 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 274 Code 276 102 [RFC4072] 278 Length 280 >=3 282 String 284 The String field is one or more octets, containing the EAP 285 Session-Id, as defined in "Extensible Authentication Protocol 286 (EAP) Key Management Framework" [RFC5247]. Since the NAS operates 287 as a pass-through in EAP, it cannot know the EAP Session-Id before 288 receiving it from the RADIUS server. As a result, an EAP-Key-Name 289 Attribute sent in an Access-Request MUST only contain a single NUL 290 character. A RADIUS server receiving an Access-Request with an 291 EAP-Key-Name Attribute containing anything other than a single NUL 292 character MUST silently discard the Attribute. In addition, the 293 RADIUS server SHOULD include this Attribute in an Access-Accept or 294 CoA-Request only if an EAP-Key-Name Attribute was present in the 295 Access-Request. 297 2.3. EAP-Peer-Id 299 Description 301 The EAP-Peer-Id Attribute contains a Peer-Id generated by the EAP 302 method. Exactly how this name is used depends on the link layer 303 in question. See [RFC5247] for more discussion. The EAP-Peer-Id 304 Attribute MAY be included in Access-Request, Access-Accept and 305 Accounting-Request packets. More than one EAP-Peer-Id Attribute 306 MUST NOT be included in an Access-Request; one or more EAP-Peer-Id 307 attributes MAY be included in an Access-Accept. 309 It should be noted that not all link layers use this name, and 310 existing EAP method implementations do not generate it. Since the 311 NAS operates as a pass-through in EAP [RFC3748], it cannot know 312 the EAP-Peer-Id before receiving it from the RADIUS server. As a 313 result, an EAP-Peer-Id Attribute sent in an Access-Request MUST 314 only contain a single NUL character. A home RADIUS server 315 receiving an Access-Request an EAP-Peer-Id Attribute containing 316 anything other than a single NUL character MUST silently discard 317 the Attribute. In addition, the home RADIUS server SHOULD include 318 one or more EAP-Peer-Id attributes in an Access-Accept only if an 319 EAP-Peer-Id Attribute was present in the Access-Request. A 320 summary of the EAP-Peer-Id Attribute format is shown below. The 321 fields are transmitted from left to right. 323 0 1 2 3 324 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 325 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 326 | Type | Length | String... 327 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 329 Code 331 TBD2 333 Length 335 >=3 337 String 339 The String field is one or more octets containing a EAP Peer-Id 340 exported by the EAP method. For details, see [RFC5247] Appendix 341 A. A robust implementation SHOULD support the field as 342 undistinguished octets. 344 2.4. EAP-Server-Id 346 Description 348 The EAP-Server-Id Attribute contains a Server-Id generated by the 349 EAP method. Exactly how this name is used depends on the link 350 layer in question. See [RFC5247] for more discussion. The EAP- 351 Server-Id Attribute is only allowed in Access-Request, Access- 352 Accept, and Accounting-Request packets. More than one EAP-Server- 353 Id Attribute MUST NOT be included in an Access-Request; one or 354 more EAP-Server-Id attributes MAY be included in an Access-Accept. 356 It should be noted that not all link layers use this name, and 357 existing EAP method implementations do not generate it. Since the 358 NAS operates as a pass-through in EAP [RFC3748], it cannot know 359 the EAP-Server-Id before receiving it from the RADIUS server. As 360 a result, an EAP-Server-Id Attribute sent in an Access-Request 361 MUST contain only a single NUL character. A home RADIUS server 362 receiving in an Access-Request an EAP-Server-Id Attribute 363 containing anything other than a single NUL character MUST 364 silently discard the Attribute. In addition, the home RADIUS 365 server SHOULD include this Attribute an Access-Accept only if an 366 EAP-Server-Id Attribute was present in the Access-Request. A 367 summary of the EAP-Server-Id Attribute format is shown below. The 368 fields are transmitted from left to right. 370 0 1 2 3 371 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 372 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 373 | Type | Length | String... 374 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 376 Code 378 TBD3 380 Length 382 >=3 384 String 386 The String field is one or more octets, containing a EAP Server-Id 387 exported by the EAP method. For details, see [RFC5247] Appendix 388 A. A robust implementation SHOULD support the field as 389 undistinguished octets. 391 2.5. Mobility-Domain-Id 393 Description 395 A single Mobility-Domain-Id Attribute MAY be included in an 396 Access-Request or Accounting-Request, in order to enable the NAS 397 to provide the RADIUS server with the Mobility Domain Identifier 398 (MDID), defined in IEEE 802.11 [IEEE-802.11]. A summary of the 399 Mobility-Domain-Id Attribute format is shown below. The fields 400 are transmitted from left to right. 402 0 1 2 3 403 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 404 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 405 | Type | Length | Value 406 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 407 Value | 408 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 410 Code 412 TBD4 414 Length 416 6 418 Value 420 The Value field is four octets, containing a 32-bit unsigned 421 integer. Since the Mobility Domain Identifier defined in IEEE 422 802.11 [IEEE-802.11] is only two octets in length, the two most 423 significant octets MUST be set to zero by the sender, and are 424 ignored by the receiver; the two least significant octets contain 425 the MDID value. 427 2.6. Preauth-Timeout 429 Description 431 This Attribute sets the maximum number of seconds which pre- 432 authentication state is required to be kept by the NAS, without 433 being utilized within a user session. For example, when 434 [IEEE-802.11] pre-authentication is used, if a user has not 435 attempted to utilize the Pairwise Master Key (PMK) derived as a 436 result of pre-authentication within the time specified by the 437 Preauth-Timeout Attribute, the PMK MAY be discarded by the Access 438 Point. However, once the session is underway, the Preauth-Timeout 439 Attribute has no bearing on the maximum session time for the user, 440 or the maximum time during which key state may be kept prior to 441 re-authentication. This is determined by the Session-Timeout 442 Attribute, if present. 444 This Attribute MAY be sent by the server to the NAS in an Access- 445 Accept. A summary of the Preauth-Timeout Attribute format is 446 shown below. The fields are transmitted from left to right. 448 0 1 2 3 449 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 450 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 451 | Type | Length | Value 452 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 453 Value (cont) | 454 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 456 Code 458 TBD5 460 Length 462 6 464 Value 466 The field is 4 octets, containing a 32-bit unsigned integer 467 encoding the maximum time in seconds that pre-authentication state 468 should be retained by the NAS. 470 2.7. Network-Id-Name 472 Description 474 The Network-Id-Name Attribute is utilized by implementations of 475 IEEE-802.1X [IEEE-802.1X] to specify the name of a Network-Id 476 (NID-Name). 478 Unlike the IEEE 802.11 SSID (which is a maximum of 32 octets in 479 length), the NID-Name may be up to 253 octets in length. 480 Consequently, if the MAC address is included within the Called- 481 Station-Id Attribute, it is possible that there will not be enough 482 remaining space to encode the NID-Name as well. Therefore when 483 used with IEEE 802.1X [IEEE-802.1X], the Called-Station-Id 484 Attribute SHOULD contain only the MAC address, with the Network- 485 Id-Name Attribute used to transmit the NID-Name. The Network-Id- 486 Name Attribute MUST NOT be used to encode the IEEE 802.11 SSID; as 487 noted in [RFC3580], the Called-Station-Id Attribute is used for 488 this purpose. 490 Zero or one Network-Id-Name Attribute is permitted within a RADIUS 491 Access-Request or Accounting-Request packet. When included within 492 an Access-Request packet, the Network-Id-Name Attribute represents 493 a hint of the NID-Name to which the Supplicant should be granted 494 access. In order to indicate which network names the Supplicant 495 is permitted to access, the Allowed-Called-Station-Id Attribute is 496 provided within an Access-Accept. When included within an 497 Accounting-Request packet, the Network-Id-Name Attribute 498 represents the NID-Name to which the Supplicant has been granted 499 access. 501 A summary of the Network-Id-Name Attribute format is shown below. 502 The fields are transmitted from left to right. 504 0 1 2 3 505 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 506 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 507 | Type | Length | String... 508 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 510 Code 512 TBD6 514 Length 516 >=3 518 String 520 The String field is one or more octets, containing a NID-Name. 521 For details, see [IEEE-802.1X]. A robust implementation SHOULD 522 support the field as undistinguished octets. 524 2.8. Access-Info 526 Description 528 The Access-Info Attribute is utilized by implementations of 529 IEEE-802.1X [IEEE-802.1X] to specify the Access status information 530 field within an Access Information Type Length Value Tuple (TLV) 531 to be sent to the user within MACsec Key Agreement (MKA) or EAPoL- 532 Announcement frames. 534 A single Access-Info Attribute is permitted within a RADIUS 535 Access-Accept, Access-Challenge, Access-Reject or Accounting- 536 Request packet. 538 A summary of the Access-Info Attribute format is shown below. The 539 fields are transmitted from left to right. 541 0 1 2 3 542 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 543 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 544 | Type | Length | Value 545 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 546 Value | 547 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 549 Code 551 TBD7 553 Length 555 6 557 Value 559 The Value field is four octets containing a 32-bit unsigned 560 integer. Since the Access status information field of the Access 561 Information TLV defined in [IEEE-802.1X] Section 11.12.2 is only 562 two octets in length, the two most significant octets of the Value 563 field MUST be set to zero by the sender and are ignored by the 564 receiver. 566 2.9. WLAN-SSID 568 Description 570 The WLAN-SSID attribute contains the Service Set Identifier (SSID) 571 which identifies a specific 802.11 extended service set (ESS). 573 0 1 2 3 574 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 575 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 576 | Type | Length | String... 577 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 579 Code 581 TBD8 583 Length 585 3 to 34 587 String 589 The String field is between 1 and 32 octets in length. The actual 590 format of the information is site or application specific, and a 591 robust implementation SHOULD support the field as undistinguished 592 octets. 594 2.10. WLAN-HESSID 596 Description 598 The WLAN-HESSID attribute contains a 6-octet MAC address that 599 identifies the Homogenous Extended Service Set. The HESSID is a 600 globally unique identifier that in conjunction with the WLAN-SSID, 601 may be used to provide network identification for a subscription 602 service provider network (SSPN). 604 0 1 2 3 605 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 606 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 607 | Type | Length | String... 608 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 610 Code 612 TBD9 614 Length 616 19 618 String 620 The String field is encoded in upper-case ASCII characters with 621 the octet values separated by dash characters, as described in 622 RFC3580 [RFC3580]. Example: "00-10-A4-23-19-C0". 624 2.11. WLAN-Venue-Info 626 Description 628 The WLAN-Venue-Info attribute identifies the category of venue 629 hosting the WLANi. 631 0 1 2 3 632 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 633 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 634 | Type | Length | Value 635 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 636 Value | 637 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 639 Code 641 TBD10 643 Length 645 4 647 Value 649 The Value field is four octets, containing a 32-bit unsigned 650 integer. The two most significant octets MUST be set to zero by 651 the sender, and are ignored by the receiver; the two least 652 significant octets contain the Venue-Group and Venue-Type fields. 654 0 1 2 3 655 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 656 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 657 | Reserved | Venue-Group | Venue-Type | 658 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 660 Venue-Group 662 The Venue-Group field is a single octet and describes the broad 663 category of the venue, e.g. "Assembly". See IEEE 802.11 664 [IEEE-802.11] for Venue-Group codes and descriptions. 666 Venue-Type 668 The Venue-Type field is a single octet and describes the venue in 669 a finer granularity within the Venue-Group, e.g. "Library". See 670 IEEE 802.11 [IEEE-802.11] for Venue-Type codes and descriptions. 672 2.12. WLAN-Venue-Language 674 Description 676 The WLAN-Venue-Language attribute is an ISO-14962-1997 677 [ISO-14962-1997] encoded string that defines the language used in 678 the WLAN-Venue-Name attribute. Zero or more WLAN-Venue-Language 679 attributes may be included in an Access-Request and each one 680 indicates the language of the WLAN-Venue-Name attribute that 681 follows it. 683 0 1 2 3 684 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 685 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 686 | Type | Length | String... 687 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 688 String (cont) | 689 +-+-+-+-+-+-+-+-+ 691 Code 693 TBD11 695 Length 697 5 699 String 701 The String field is a two or three character language code 702 selected from ISO-639 [ISO-639]. A two character language code 703 has a zero ("null" in ISO-14962-1997) appended to make it 3 octets 704 in length. 706 2.13. WLAN-Venue-Name 708 Description 710 The WLAN-Venue-Name attribute provides additional metadata on the 711 BSS. For example, this information may be used to assist a user 712 in selecting the appropriate BSS with which to associate. Zero or 713 more WLAN-Venue-Name attributes may be included in an Access- 714 Request in the same or different languages. 716 0 1 2 3 717 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 718 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 719 | Type | Length | String... 720 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 722 Code 724 TBD12 726 Length 727 >=3 729 String 731 The String field is a UTF-8 formatted field containing the venue's 732 name. The maximum length of this field is 252 octets. 734 2.14. WLAN-Reason-Code 736 Description 738 The WLAN-Reason-Code Attribute contains information on the reason 739 why a station has been dissaciated or de-authenticated. This can 740 occur due to policy or for reasons related to the user's 741 subscription. 743 A WLAN-Reason-Code Attribute MAY be included within an Access- 744 Reject or Disconnect-Request packet. Upon receipt of an Access- 745 Reject or Disconnect-Request packet containing a WLAN-Reason-Code 746 Attribute, the WLAN-Reason-Code value is copied by the Access 747 Point into the Reason code field of a Disassociation or 748 Deauthentication frame (see clause 8.3.3.4 and 8.3.3.12 749 respectively in [IEEE- 802.11]), which is subsequently transmitted 750 to the station. In order to provide information within an 751 Accounting-Request on why a station has been disassociated or de- 752 authenticated, the Acct-Termination-Cause Attribute is used, 753 rather than the WLAN-Reason-Code Attribute. A summary of the 754 WLAN-Reason-Code Attribute format is shown below. The fields are 755 transmitted from left to right. 757 0 1 2 3 758 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 759 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 760 | Type | Length | Value 761 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 762 Value | 763 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 765 Code 767 TBD13 769 Length 771 4 773 Value 774 The Value field is a 32-bit unsigned integer drawn from Table 8-36 775 in clause 8.4.1.7 of [IEEE-802.11]. The following Reason codes 776 for public Wi-Fi access networks (and the corresponding additional 777 values of the Acct-Terminate-Cause Attribute) were added by the 778 IEEE 802.11u-2011 amendment: 780 Reason Acct- Description 781 Code Terminate- 782 Value Cause 784 27 24 Disassociated because session 785 terminated by service provider request 786 28 25 Disassociated because of lack 787 of service provider roaming agreement 788 29 26 Requested service rejected because 789 of service provider cipher suite or 790 AKM requirement 791 30 27 Requested service not authorized in 792 this location 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 821 4 823 Value 825 The Value field is four octets formatted in accordance with Figure 826 8-187 with values drawn from Table 8-99 of [IEEE-802.11]. 828 2.16. WLAN-Group-Cipher 830 Description 832 The WLAN-Group-Cipher Attribute contains information on the group 833 cipher suite used to establish the robust security network 834 association (RSNA) between the AP and mobile device. 836 A WLAN-Group-Cipher Attribute MAY be included within Access- 837 Request and Accounting-Request packets. A summary of the WLAN- 838 Group-Cipher Attribute format is shown below. The fields are 839 transmitted from left to right. 841 0 1 2 3 842 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 843 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 844 | Type | Length | Value 845 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 846 Value | 847 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 849 Code 851 TBD15 853 Length 855 4 857 Value 859 The Value field is four octets formatted in accordance with Figure 860 8-187 with values drawn from Table 8-99 of [IEEE-802.11]. 862 2.17. WLAN-AKM-Suite 864 Description 866 The WLAN-AKM-Suite Attribute contains information on the 867 authentication and key management suite used to establish the 868 robust security network association (RSNA) between the AP and 869 mobile device. 871 A WLAN-AKM-Suite Attribute MAY be included within Access-Request 872 and Accounting-Request packets. A summary of the WLAN-AKM-Suite 873 Attribute format is shown below. The fields are transmitted from 874 left to right. 876 0 1 2 3 877 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 878 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 879 | Type | Length | Value 880 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 881 Value | 882 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 884 Code 886 TBD16 888 Length 890 4 892 Value 894 The Value field is four octets formatted in accordance with Figure 895 8-187 with values drawn from Table 8-101 of [IEEE-802.11]. 897 2.18. WLAN-Group-Mgmt-Cipher 899 Description 901 The WLAN-Group-Mgmt-Cipher Attribute contains information on group 902 management cipher used to establish the robust security network 903 association (RSNA) between the AP and mobile device. 905 A WLAN-Group-Mgmt-Cipher Attribute MAY be included within Access- 906 Request and Accounting-Request packets. Presence of the attribute 907 indicates that the station negotiated to use management frame 908 protection during association. 910 A summary of the WLAN-Group-Mgmt-Cipher Attribute format is shown 911 below. The fields are transmitted from left to right. 913 0 1 2 3 914 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 915 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 916 | Type | Length | Value 917 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 918 Value | 919 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 921 Code 923 TBD17 925 Length 927 4 929 Value 931 The Value field is four octets formatted in accordance with values 932 drawn from Table ? of [IEEE-802.11]. 934 2.19. WLAN-RF-Band 936 Description 938 The WLAN-RF-Band Attribute contains information on the RF band 939 used by the Access Point for transmission and reception of 940 information to and from the mobile device. 942 A WLAN-RF-Band Attribute MAY be included within Access-Request and 943 Accounting-Request packets. A summary of the WLAN-RF-Band 944 Attribute format is shown below. The fields are transmitted from 945 left to right. 947 0 1 2 3 948 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 949 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 950 | Type | Length | Value 951 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 952 Value | 953 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 955 Code 957 TBD18 959 Length 960 4 962 Value 964 The Value field is 4 octets having a value chosen from the table 965 below: 967 Band ID value Meaning 968 0 TV white spaces 969 1 Sub-1 GHz (excluding TV white spaces) 970 2 2.4 GHz 971 3 3.6 GHz 972 4 4.9 and 5 GHz 973 5 60 GHz 975 [Note]: this table was copied from Table 8-53a in IEEE 802.11ad-d5. 976 I'm not sure of the relative publication dates of this internet draft 977 and IEEE 802.11ad-d5. Since it's generally not recommended to 978 reference a draft specification in an RFC, I've copied the table. If 979 we discover that the IEEE document will be published in time, then we 980 could deleted the table and instead reference Table 8-53a in IEEE 981 802.11ad. 983 3. Table of attributes 985 The following table provides a guide to which attributes may be found 986 in which kinds of packets, and in what quantity. 988 Access- Access- Access- Access- 989 Request Accept Reject Challenge # Attribute 990 0 0 0-1 0 49 Acct-Terminate-Cause 991 0 0+ 0 0 TBD1 Allowed-Called-Station-Id 992 0-1 0-1 0 0 102 EAP-Key-Name 993 0-1 0+ 0 0 TBD2 EAP-Peer-Id 994 0-1 0+ 0 0 TBD3 EAP-Server-Id 995 0-1 0 0 0 TBD4 Mobility-Domain-Id 996 0-1 0-1 0 0 TBD5 Preauth-Timeout 997 0-1 0 0 0 TBD6 Network-Id-Name 998 0 0-1 0-1 0-1 TBD7 Access-Info 999 0-1 0 0 0 TBD8 WLAN-SSID 1000 0-1 0 0 0 TBD9 WLAN-HESSID 1001 0-1 0 0 0 TBD10 WLAN-Venue-Info 1002 0-1 0 0 0 TBD11 WLAN-Venue-Language 1003 0-1 0 0 0 TBD12 WLAN-Venue-Name 1004 0 0 0-1 0 TBD13 WLAN-Reason-Code 1005 0-1 0 0 0 TBD14 WLAN-Pairwise-Cipher 1006 0-1 0 0 0 TBD15 WLAN-Group-Cipher 1007 0-1 0 0 0 TBD16 WLAN-AKM-Suite 1008 Access- Access- Access- Access- 1009 Request Accept Reject Challenge # Attribute 1010 0-1 0 0 0 TBD17 WLAN-Group-Mgmt-Cipher 1011 0-1 0 0 0 TBD18 WLAN-RF-Band 1013 CoA- Dis- Acct- 1014 Req Req Req # Attribute 1015 0 0-1 0-1 49 Acct-Terminate-Cause 1016 0+ 0 0 TBD1 Allowed-Called-Station-Id 1017 0-1 0 0 102 EAP-Key-Name 1018 0 0 0+ TBD2 EAP-Peer-Id 1019 0 0 0+ TBD3 EAP-Server-Id 1020 0 0 0-1 TBD4 Mobility-Domain-Id 1021 0 0 0 TBD5 Preauth-Timeout 1022 0 0 0-1 TBD6 Network-Id-Name 1023 0-1 0 0-1 TBD7 Access-Info 1024 0 0 0-1 TBD8 WLAN-SSID 1025 0 0 0-1 TBD9 WLAN-HESSID 1026 0 0 0-1 TBD10 WLAN-Venue-Info 1027 0 0 0-1 TBD11 WLAN-Venue-Language 1028 0 0 0-1 TBD12 WLAN-Venue-Name 1029 0 0-1 0 TBD13 WLAN-Reason-Code 1030 0 0 0-1 TBD14 WLAN-Pairwise-Cipher 1031 0 0 0-1 TBD15 WLAN-Group-Cipher 1032 0 0 0-1 TBD16 WLAN-AKM-Suite 1033 0 0 0-1 TBD17 WLAN-Group-Mgmt-Cipher 1034 0 0 0-1 TBD18 WLAN-RF-Band 1036 The following table defines the meaning of the above table entries. 1038 0 This Attribute MUST NOT be present in packet. 1039 0+ Zero or more instances of this Attribute MAY be 1040 present in the packet. 1041 0-1 Zero or one instance of this Attribute MAY be 1042 present in the packet. 1044 4. Diameter Considerations 1046 The EAP-Key-Name Attribute is already defined as a RADIUS Attribute 1047 within Diameter EAP [RFC4072]. When used in Diameter, the other 1048 attributes defined in this specification can be used as Diameter AVPs 1049 from the Code space 1-255 (RADIUS Attribute compatibility space). No 1050 additional Diameter Code values are therefore allocated. The data 1051 types and flag rules for the attributes are as follows: 1053 +---------------------+ 1054 | AVP Flag rules | 1055 |----+-----+----+-----|----+ 1056 | | |SHLD| MUST| | 1057 Attribute Name Value Type |MUST| MAY | NOT| NOT|Encr| 1058 -----------------------------------------|----+-----+----+-----|----| 1059 Allowed-Called-Station-Id UTF8String | M | P | | V | Y | 1060 EAP-Peer-Id UTF8String | M | P | | V | Y | 1061 EAP-Server-Id UTF8String | M | P | | V | Y | 1062 Mobility-Domain-Id Unsigned32 | M | P | | V | Y | 1063 Preauth-Timeout Unsigned32 | M | P | | V | Y | 1064 Network-Id-Name UTF8String | M | P | | V | Y | 1065 Access-Info Unsigned32 | M | P | | V | Y | 1066 WLAN-SSID UTF8String | M | P | | V | Y | 1067 WLAN-HESSID UTF8String | M | P | | V | Y | 1068 WLAN-Venue-Info Unsigned32 | M | P | | V | Y | 1069 WLAN-Venue-Language UTF8String | M | P | | V | Y | 1070 WLAN-Venue-Name UTF8String | M | P | | V | Y | 1071 WLAN-Reason-Code Unsigned32 | M | P | | V | Y | 1072 WLAN-Pairwise-Cipher Unsigned32 | M | P | | V | Y | 1073 WLAN-Group-Cipher Unsigned32 | M | P | | V | Y | 1074 WLAN-AKM-Suite Unsigned32 | M | P | | V | Y | 1075 WLAN-Group-Mgmt-Cipher Unsigned32 | M | P | | V | Y | 1076 WLAN-RF-Band Unsigned32 | M | P | | V | Y | 1077 -----------------------------------------|----+-----+----+-----|----| 1079 The attributes in this specification have no special translation 1080 requirements for Diameter to RADIUS or RADIUS to Diameter gateways; 1081 they are copied as is, except for changes relating to headers, 1082 alignment, and padding. See also [RFC3588] Section 4.1 and [RFC4005] 1083 Section 9. 1085 What this specification says about the applicability of the 1086 attributes for RADIUS Access-Request packets applies in Diameter to 1087 AA-Request [RFC4005] or Diameter-EAP-Request [RFC4072]. What is said 1088 about Access-Challenge applies in Diameter to AA-Answer [RFC4005] or 1089 Diameter-EAP-Answer [RFC4072] with Result-Code AVP set to 1090 DIAMETER_MULTI_ROUND_AUTH. 1092 What is said about Access-Accept applies in Diameter to AA-Answer or 1093 Diameter-EAP-Answer messages that indicate success. Similarly, what 1094 is said about RADIUS Access-Reject packets applies in Diameter to AA- 1095 Answer or Diameter-EAP-Answer messages that indicate failure. 1097 What is said about COA-Request applies in Diameter to Re-Auth-Request 1098 [RFC4005]. What is said about Accounting-Request applies to Diameter 1099 Accounting- Request [RFC4005] as well. 1101 5. IANA Considerations 1103 This document uses the RADIUS [RFC2865] namespace, see 1104 . This specification 1105 requires assignment of a RADIUS attribute types for the following 1106 attributes: 1108 Attribute Type 1109 ========= ==== 1110 Allowed-Called-Station-Id TBD1 1111 EAP-Peer-Id TBD2 1112 EAP-Server-Id TBD3 1113 Mobility-Domain-Id TBD4 1114 Preauth-Timeout TBD5 1115 Network-Id-Name TBD6 1116 Access-Info TBD7 1117 WLAN-SSID TBD8 1118 WLAN-HESSID TBD9 1119 WLAN-Venue-Info TBD10 1120 WLAN-Venue-Language TBD11 1121 WLAN-Venue-Name TBD12 1122 WLAN-Reason-Code TBD13 1123 WLAN-Pairwise-Cipher TBD14 1124 WLAN-Group-Cipher TBD15 1125 WLAN-AKM-Suite TBD16 1126 WLAN-Group-Mgmt-Cipher TBD17 1127 WLAN-RF-Band TBD18 1129 This document also assigns the following additional values of the 1130 Acct-Terminate-Cause attribute: 1132 Acct- Description 1133 Terminate- 1134 Cause 1135 ========== ============ 1136 24 Disassociated because session 1137 terminated by service provider request 1138 25 Disassociated because of lack 1139 of service provider roaming agreement 1140 26 Requested service rejected because 1141 of service provider cipher suite or 1142 AKM requirement 1143 27 Requested service not authorized in 1144 this location 1146 6. Security Considerations 1148 Since this document describes the use of RADIUS for purposes of 1149 authentication, authorization, and accounting in IEEE 802 networks, 1150 it is vulnerable to all of the threats that are present in other 1151 RADIUS applications. For a discussion of these threats, see 1152 [RFC2607], [RFC2865], [RFC3162], [RFC3579], [RFC3580] and [RFC5176]. 1154 7. References 1156 7.1. Normative references 1158 [IEEE-802] IEEE Standards for Local and Metropolitan Area Networks: 1159 Overview and Architecture, ANSI/IEEE Std 802, 1990. 1161 [IEEE-802.11] 1162 Information technology - Telecommunications and information 1163 exchange between systems - Local and metropolitan area 1164 networks - Specific Requirements Part 11: Wireless LAN 1165 Medium Access Control (MAC) and Physical Layer (PHY) 1166 Specifications, IEEE Std. 802.11-2012, 2012. 1168 [IEEE-802.1X] 1169 IEEE Standard for Local and Metropolitan Area Networks - 1170 Port-Based Network Access Control, IEEE 802.1X-2010, February 1171 2010. 1173 [ISO-639] ISO, "Codes for the Representation of Names of Languages". 1175 [ISO-14962-1997] 1176 ISO, "Space data and information transfer systems - ASCII 1177 encoded English", 1997. 1179 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1180 Requirement Levels", RFC 2119, March, 1997. 1182 [RFC2865] Rigney, C., Rubens, A., Simpson, W. and S. Willens, "Remote 1183 Authentication Dial In User Service (RADIUS)", RFC 2865, June 1184 2000. 1186 [RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. 1187 Arkko, "Diameter Base Protocol", RFC 3588, September 2003. 1189 [RFC4072] Eronen, P., Hiller, T. and G. Zorn, "Diameter Extensible 1190 Authentication Protocol (EAP) Application", RFC 4072, August 1191 2005. 1193 [RFC5247] Aboba, B., Simon, D. and P. Eronen, "EAP Key Management 1194 Framework", RFC 5247, August 2008. 1196 7.2. Informative references 1198 [RFC2607] Aboba, B. and J. Vollbrecht, "Proxy Chaining and Policy 1199 Implementation in Roaming", RFC 2607, June 1999. 1201 [RFC3162] Aboba, B., Zorn, G. and D. Mitton, "RADIUS and IPv6", RFC 1202 3162, August 2001. 1204 [RFC3579] Aboba, B. and P. Calhoun, "RADIUS Support for Extensible 1205 Authentication Protocol (EAP)", RFC 3579, September 2003. 1207 [RFC3580] Congdon, P., Aboba, B., Smith, A., Zorn, G. and J. Roese, 1208 "IEEE 802.1X Remote Authentication Dial In User Service 1209 (RADIUS) Usage Guidelines", RFC 3580, September 2003. 1211 [RFC3748] Aboba, B., Blunk, L., Vollbrecht, J., Carlson, J. and H. 1212 Levkowetz, "Extensible Authentication Protocol (EAP)", RFC 1213 3748, June 2004. 1215 [RFC4005] Calhoun, P., Zorn, G., Spence, D., and D. Mitton, "Diameter 1216 Network Access Server Application", RFC 4005, August 2005. 1218 [RFC5176] Chiba, M., Dommety, G., Eklund, M., Mitton, D. and B. Aboba, 1219 "Dynamic Authorization Extensions to Remote Authentication 1220 Dial In User Service (RADIUS)", RFC 5176, January 2008. 1222 Acknowledgments 1224 The authors would like to acknowledge Mick Seaman, Dorothy Stanley, 1225 Yoshihiro Ohba, and the contributors to the IEEE 802.1 and IEEE 1226 802.11 reviews of this document, for useful discussions. 1228 Authors' Addresses 1230 Bernard Aboba 1231 Microsoft Corporation 1232 One Microsoft Way 1233 Redmond, WA 98052 1235 EMail: bernard_aboba@hotmail.com 1237 Jouni Malinen 1238 EMail: j@w1.fi 1240 Paul Congdon 1241 Hewlett Packard Company 1242 HP ProCurve Networking 1243 8000 Foothills Blvd, M/S 5662 1244 Roseville, CA 95747 1246 Phone: +1 916 785 5753 1247 Fax: +1 916 785 8478 1248 EMail: paul_congdon@hp.com 1250 Joseph Salowey 1251 Cisco Systems 1253 EMail: jsalowey@cisco.com 1255 Mark Jones 1256 Amdocs 1258 EMail: mark@azu.ca