idnits 2.17.1 draft-adrangi-radius-extension-for-pwlan-00.txt: -(61): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding -(320): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == There are 11 instances of lines with non-ascii characters in the document. == The page length should not exceed 58 lines per page, but there was 18 longer pages, the longest (page 2) being 66 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 19 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Authors' Addresses Section. ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** The abstract seems to contain references ([1]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 26 has weird spacing: '... The list ...' == Line 150 has weird spacing: '...summary of t...' == Line 236 has weird spacing: '... There is a...' == Line 249 has weird spacing: '...ilities is e...' == Line 292 has weird spacing: '... Note that ...' == (11 more instances...) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (October 14, 2003) is 7494 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- -- Looks like a reference, but probably isn't: 'RFC2119' on line 99 == Unused Reference: '4' is defined on line 807, but no explicit reference was found in the text ** Obsolete normative reference: RFC 3576 (ref. '4') (Obsoleted by RFC 5176) ** Obsolete normative reference: RFC 2234 (ref. '5') (Obsoleted by RFC 4234) ** Obsolete normative reference: RFC 2434 (ref. '6') (Obsoleted by RFC 5226) ** Obsolete normative reference: RFC 3344 (ref. '7') (Obsoleted by RFC 5944) Summary: 8 errors (**), 0 flaws (~~), 11 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Farid Adrangi (Ed.) 3 INTERNET DRAFT Intel Corporation 4 Category: Informational October 14, 2003 5 Expires: April 13, 2004 7 RADIUS Extension for Public Wireless LAN 8 draft-adrangi-radius-extension-for-pwlan-00.txt 10 Status of this Memo 12 This document is an Internet-Draft and is in full conformance 13 with all provisions of Section 10 of RFC2026. 15 Internet-Drafts are working documents of the Internet 16 Engineering Task Force (IETF), its areas, and its working 17 groups. Note that other groups may also distribute working 18 documents as Internet-Drafts. 20 Internet-Drafts are draft documents valid for a maximum of six 21 months and may be updated, replaced, or obsoleted by other 22 documents at any time. It is inappropriate to use Internet- 23 Drafts as reference material or to cite them other than as "work 24 in progress." 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/ietf/1id-abstracts.txt 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html. 32 Abstract 34 This document describes additional Remote Authentication Dial In 35 User Service (RADIUS) [1] attributes for use of RADIUS AAA 36 (Authentication, Authorization, Accounting) in Public Wireless 37 Local Area Network (PWLAN) deployments. Some of these attributes 38 are already implemented as Vendor Specific Attributes (VSA) in 39 networks today, but are core to PWLAN interoperability and 40 roaming. 42 Table of Contents 44 1. Introduction....................................................2 45 1.2 Applicability..................................................2 46 1.3 Requirements language..........................................3 47 1.4 Terminology....................................................3 48 2. Operation.......................................................3 49 2.1 RADIUS Support for PWLAN Location Information..................3 50 2.2 RADIUS Support for Advertising Application-based capabilities..5 51 2.3 RADIUS Support for Specifying a Mobile IP Home Agent...........7 52 2.4 RADIUS Support for Specifying DNS Server.......................9 53 2.5 RADIUS Support for Specifying Remote IP Addresses.............10 54 2.6 RADIUS Support for Specifying IP Address Type Options.........11 55 2.7 RADIUS Support for Specifying Network Capabilities............13 56 4. IANA Considerations............................................16 57 5. Security Considerations........................................16 58 6. Contributors...................................................17 59 7. Acknowledgements...............................................17 60 8. References.....................................................17 61 Authors� Addresses................................................18 63 1. Introduction 65 Wireless LAN (WLAN) Access Networks (AN) are being deployed in 66 public places such as airports, hotels, shopping malls, and coffee 67 shops by a diverse set of incumbent operators like cellular 68 carriers (GSM and CDMA), Wireless Internet Service Providers 69 (WISP), and fixed broadband operators. 71 Remote Access Dial In User Service (RADIUS) [1],[2],[3] is the 72 dominant Authentication, Authorization, and Accounting (AAA) 73 protocol in use across broadband networks globally and consequently 74 will be heavily reused in Public WLAN (PWLAN) deployments. 76 This document describes a number of additional attributes that are 77 needed to enable use of RADIUS AAA in PWLANs in an interoperable 78 manner. Attributes described in this document includes some of 79 Vendor Specific Attributes (VSA) that are recommended by various 80 standard bodies (such as 3GPP, 3GPP2, GSMA) for PWLAN interworking. 81 Common understanding and Standardization of these attributes is 82 essential to enable improved interoperability and hence successful 83 deployments of PWLANs. 85 1.2 Applicability 87 Although proposed attributes in this draft are intended for PWLAN 88 deployments, they can also be used in other networks (e.g., wired 89 networks). 91 1.3 Requirements language 93 In this document, several words are used to signify the 94 requirements of the specification. These words are often 95 capitalized. The key words "MUST", "MUST NOT", "REQUIRED", 96 "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", 97 "MAY", and "OPTIONAL" in this document are to be interpreted as 98 described in [RFC2119]. 100 1.4 Terminology 102 Access Network (AN) 103 The PWLAN hotspot network that provides wireless connectivity 104 to the Internet for WLAN clients (or stations) present in the 105 local access area. This MAY be in a separate security and 106 routing domain with respect to the Home Service Network or a 107 Mediating Network. 109 Home Service Network (HSN) 110 The network providing the service and therefore maintaining 111 the direct relationship to the user/subscriber of the WLAN 112 service. All AAA functions are ultimately performed by the 113 HSN. 115 Access Point (AP) 116 �A station that provides access to the distribution services 117 via the wireless medium for associated Stations.� 119 RADIUS server 120 �This is a server which provides for 121 authentication/authorization via the protocol described in 122 [1], and for accounting as described in [6].� It is deployed 123 in the PWLAN AN, MN, and HSN. 125 2. Operation 127 Operation is identical to that defined in [1] and [2]. 129 2.1 RADIUS Support for PWLAN Location Information 131 Rationale 133 When a PWLAN client connects to a PWLAN AN, the information 134 pertaining to the PWLAN AN location and operational ownership 135 needs to be conveyed to the HSN for accounting and services 136 management purposes. This information contains the AN operator 137 name and the AN location information such as Location Name, 138 Location Type, City, State, and Country. This information 139 enables use case scenarios for location aware billing, location 140 aware subscriber authentication / authorization in roaming, and 141 location aware services. 143 Attribute 145 This attribute describes information pertaining to a PWLAN AN 146 location and operational ownership. It MUST be sent in Access- 147 Request, and Accounting-Request records where the Acc-Status- 148 Type is set to Start or Stop if available. 150 A summary of the AN Location and Operational-Ownership 151 Information Attribute is shown below. 153 0 1 2 154 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 155 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- 156 | Type | Length | String ... 157 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- 159 Name 161 Access Network Location Information 163 Type 165 To be assigned by IANA 167 Length 169 >= 3 171 String 173 The string field is one or more octets, and it is structured as a 174 set of comma-separated field names and values according to the 175 following ABNF [5]. 177 Attribute Value = string [ %d0 location-info ] 178 string = *CHAR 180 location-info = item ["," item ] 181 item = field-name "=" value 183 field-name = 1*( ALPHA / "-" / "_" / �:� / DIGIT) 185 value = 0*( 0x01-2B / 0x2D-FF ) ; any non-null UTF-8 char 186 except "," 188 Defined Fields and their Descriptions 189 Here is a list of field name and description of their values 190 defined in this document. The field names are not case 191 sensitive. 193 Operator-Name : It contains a PWLAN AN operator name which MUST 194 be a globally known and registered name. One proposal is to 195 structure the content of the field into two parts separated by 196 a colon. The first (also referred to as a prefix) identifies 197 the operator type; example: GSM, WISP. And, the second part 198 identifies a globally known operator defined within the domain 199 of the operator type � for example, GSM:xxxx where xxxx is a 200 unique globally known GSM operator ID. Prefixes describing 201 various operator types MUST be registered with IANA [6]. The 202 other proposal is to have a prefixed field name where the 203 prefix identifies the operator type (e.g., GSM:Operator-Name, 204 WISP:Operator-Name). 206 Location-ID : It contains a PWLAN AN location ID defined within 207 the scope of the AN operator name. 209 Location-name : It contains a PWLAN AN location name defined 210 within the scope of the AN operator name (e.g., starbucks_2) 212 Location-type : It contains a PWLAN AN location type defined 213 within the scope of the AN operator (e.g., coffee-shop, 214 airport) 216 City : It contains a city name where an PWLAN AN is located 217 (e.g., Portland) 219 State : It contains a state name where an PWLAN AN is located 220 (e.g., Oregon) 222 Country : It contains an ISO (International Organization for 223 Standardization) defined country name where an PWLAN AN is 224 located (e.g., USA). 226 Example: 228 Operator-name=GSM:T-Mobile, location-ID=44,location- 229 name=starbucks-4,location-type=coffee shop, city= seattle, 230 state=Washington,country=us 232 2.2 RADIUS Support for Advertising Application-based capabilities 234 Rationale 236 There is a need for a HSN RADIUS server to discover 237 capabilities of a RADIUS client that has initiated a connection 238 to it. The capabilities indicate standard-based applications 239 (e.g., existing dynamic authorization Extension to Remote [5], 240 future prepaid accounting model, etc.) that a PWLAN AN RADIUS 241 Client supports. This enables the HSN RADIUS server to decide 242 which application services it can use for the connection, or 243 whether or not it should accept the connection. For example, 244 if the subscriber is a prepaid subscriber, and the RADIUS 245 client does not support the prepaid capability, the RADIUS 246 server may want to reject the connection. 248 Having a standard method for advertising application-based 249 capabilities is essential for interoperability and proper 250 operation of RADIUS for PWLAN in roaming situations. 252 Attribute 254 This attribute describes standard-based Applications (also 255 referred to as capabilities) that a PWLAN AN AP supports. 256 These capabilities MUST be identified by their identity numbers 257 assigned by the appropriate standard bodies (e.g., RFC number 258 for IETF). This attribute MUST be sent in Access-Request if 259 available. 261 A summary of the capability Attribute is shown below. 263 0 1 2 264 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 265 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- 266 | Type | Length | String ... 267 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- 269 Name 271 Generic Capability 273 Type 275 To be assigned by IANA 277 Length 279 >= 3 281 String 283 The string field is one or more octets. This string 284 consists of a comma-delimited list of URIs. These URIs may 285 but do not necessarily correspond to the actual locations of 286 files. However, they must include a FQDN corresponding to 287 the organization responsible for the document or standard to 288 which compliance is claimed. For example: 290 www.ietf.org/rfc/3580;2548;2607, www.3GPP.org/Release6. 292 Note that conformance to one specification may imply 293 conformance to others as well. Thus, it is not necessary or 294 even possible to list all standards that the PWLAN AN 295 supports. In many cases, the referenced URIs will 296 correspond to best practices documents that reference 297 standards and also indicate which optional elements of those 298 standards must be implemented. 300 2.3 RADIUS Support for Specifying a Mobile IP Home Agent 302 Rationale 304 In Mobile IP [7], a Mobile-IP enabled client registers with its 305 home agent when it attaches to the network for the first time, 306 or when it changes its network point of attachment. In typical 307 service provider deployments, networks are geographically 308 dispersed within a single large administrative domain. In such 309 networks, it is possible to deploy the home agents in each 310 geographical area. When a PWLAN client authenticates to its 311 HSN RADIUS server through a PWLAN AN, the HSN RADIUS server may 312 want to specify the optimal home agent for that PWLAN client 313 based on the PWLAN AN location information. 315 There is a need for an interoperable method by which the home 316 RADIUS server can indicate the Mobile IP home agent that should 317 used by the PWLAN client to the RADIUS client. Note that the 318 home agent can later be indicated to the PWLAN client through a 319 specific means � for example, it can be relayed in the �home 320 agent address� field of a DHCP reply if the client acquires its 321 IP address through DHCP [8]. 323 Attribute (IPv4 version) 325 This attribute indicates the home agent IPv4 Address that can 326 be used by a Mobile-IP enabled PWLAN client. This attribute 327 SHOULD be sent in Access-Accept if available. 329 A summary of the Mobile IPv4 home agent Attribute is shown 330 below. 332 0 1 2 3 333 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 334 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 335 | Type | Length | Address 336 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 337 Address (cont) | 338 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 339 Name 341 Mobile IPv4 Home Agent 343 Type 345 To be assigned by IANA 347 Length 349 6 351 Address 353 The Address filed is four octets. It contains a Mobile IP 354 home agent address. 356 Attribute (IPv6 version) 358 This attribute indicates the home agent IPv6 Address that can 359 be used by a Mobile-IP enabled PWLAN client. This attribute 360 SHOULD be sent in Access-Accept if available. 362 A summary of the Mobile IPv6 home-agent Attribute is shown 363 below. 365 0 1 2 3 366 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 367 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 368 | Type | Length | Address 369 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 370 Address (Cont.) 371 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 372 Address (Cont.) 373 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 374 Address (Cont.) 375 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 376 Address (cont.) | 377 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 379 Name 381 Mobile IPv6 Home Agent 383 Type 385 To be assigned by IANA 387 Length 389 18 391 Address 393 The Address filed is four octets. It contains a Mobile IP 394 home agent address. 396 2.4 RADIUS Support for Specifying DNS Server 398 Rationale 400 Once a PWLAN client authenticated, it will most likely acquire 401 an IP address by sending a Request to a DHCP [8] server in the 402 PWLAN AN. The DHCP server allocates an IP address and sends it 403 to the PWLAN client in a DHCP reply. The DHCP server also has 404 an option of sending a DNS update to the DNS server specified 405 by the HSN. 407 There is a need for an interoperable method by which a HSN 408 RADIUS server can indicate the DNS server to the RADIUS client 409 for a given PWLAN client. 411 Attribute (IPv4 Version) 413 This attribute indicates IPv4 address of a DNS server that 414 should be used for a PWLAN client, most likely by a DHCP 415 server. This attribute SHOULD be sent in Access-Accept if 416 available. 418 A summary of the DNS Server IPv4 Address Attribute is shown 419 below. 421 0 1 2 3 422 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 423 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 424 | Type | Length | Address 425 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 426 Address (cont) | 427 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 429 Name 431 DNS Server IPv4 Address 433 Type 435 To be assigned by IANA 437 Length 439 6 441 Address 443 The Address field is four octets 445 Attribute (IPv6 Version) 447 To Be Defined 449 2.5 RADIUS Support for Specifying Remote IP Addresses 451 Rationale 453 A HSN RADIUS server may want to restrict its subscribers 454 accessing to certain remote IP addresses for different types of 455 servers (such as, web servers, multimedia servers, mail 456 servers, etc.) based on their subscription profiles. Or, a HSN 457 RADIUS server may want to monitor a range of remote IP address 458 that its subscribers may connect to for accounting purposes. 459 There is a need for an interoperable method by which one or 460 more remote IP address associated with various services can be 461 indicated to the RADIUS client for a given PWLAN Client for 462 access authorization and/or accounting purposes. 464 Attribute (IPv4 Version) 466 This attribute indicates an IPv4 address and address mask which 467 together identify one or more IPv4 address. It SHOULD be sent 468 in Access-Accept, and Accounting-Request records where the Acc- 469 Status-Type is set to Start or Stop. 471 A summary of the Remote IP Address(s) Attribute is shown below. 473 0 1 2 3 474 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 475 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 476 | Type | Length | FLAG | Address 477 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 478 Address (cont) | Address Mask 479 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 480 Address Mask | 481 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 483 Name 485 Remote IPv4 Address(s) 487 Type 488 To be assigned by IANA 490 Length 492 10 494 Flag 496 1 : The address is used in conjunction with the Address 497 Mask, to identify the range of address that a PWLAN client 498 MAY establish an IP connection with. 500 2 : The address is used in conjunction with the Address 501 Mask, to identify the range of address to be monitored for 502 accounting purposes. 504 3: Both (1) and (2) 506 Address 508 The Address field is four octets 510 The address field is four octets. It contains an IPv4 511 address. 513 Address Mask 515 The Address Mask is four octets. It contains an IPv4 516 address mask that in conjunction with the Address define the 517 range of address. 519 Attribute (IPv6 Version) 521 To Be Defined 523 2.6 RADIUS Support for Specifying IP Address Type Options 525 Rationale 527 A PWLAN AN may have an option of assigning a layer 3 public 528 (i.e., routable) or private (i.e., non-routable) address to a 529 PWLAN client. If the option is available, a HSN may also want 530 to influence which address type (i.e., public or private) 531 should be assigned to the PWLAN client depending on the 532 client�s subscription profile. 534 There is a need for an interoperable method by which 1) a PWLAN 535 AN can indicate the IP address type options to a HSN. 2) A HSN 536 can specify the desired IP address type. 538 Attribute 540 This attribute indicates IPv4 address type options. It can be 541 present in Access-Request, Access-Accept, and Accounting- 542 Request records where the Acc-Status-Type is set to Start or 543 Stop if available. When it is used in an Access-Accept and 544 Accounting-Request packets, the Address Type value MUST be 1 or 545 2. 547 A PWLAN AN includes this attribute to advertise its IP address 548 type options for a given PWLAN client. A RADIUS server includes 549 this attribute in the Access-Accept to specify an IP address 550 type option for the PWLAN client. 552 A RADIUS server MUST NOT include this attribute in the Access- 553 Accept if the IP Address Type options were not advertised in 554 the Access-Request. If an invalid IP Address Type option is 555 received in the Access-Accept, then the PWLAN AN MUST use its 556 default IP Address Type option for the PWLAN client. 557 Otherwise, the PWLAN AN MUST assign an IP address according to 558 the specified type option, and it MUST include this attribute 559 in Accounting-Request packets to indicate the used IP address 560 type option. If an IP address type option is not specified in 561 the Access-Accept, the PWLAN AN MUST NOT include this attribute 562 in Accounting-Request packets. 564 A summary of the home-agent Attribute is shown below. 566 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 567 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 568 | Type | Length |IP Address Type| 569 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 571 Name 573 IP Address Type Options 575 Type 577 To be assigned by IANA 579 Length 581 1 583 Address Type 585 1 : Public Address Type 586 2 : Private Address Type 587 3 : Public and Private Type 589 2.7 RADIUS Support for Specifying Network Capabilities 591 Rationale 593 When a PWLAN client connects to a PWLAN AN, it may use certain 594 services (e.g., real-time or multimedia services) that require 595 a minimum network resources for the desired Quality of Service 596 (QoS) and user experience. A PWLAN AN may be able to allocate 597 network resources (e.g., radio and wired network bandwidth, 598 radio network delays) for a PWLAN client within the AN, or 599 influence the routing of its packets to outside (i.e., 600 determining the next external hop). 602 The intent is to provide a generic and simple framework within 603 which a PWLAN AN can advertise its network capabilities for a 604 given PWLAN client to the HSN RADIUS server. And, the HSN 605 RADIUS server then can specify the Network capability settings 606 that it wants for that PWLAN client. The specified network 607 capability settings also need to be indicated in the accounting 608 packets. 610 Attribute (Network Capability Advertisement) 612 This attribute indicates network capabilities that a PWLAN AN 613 can provide for a given PWLAN client. It SHOULD be sent in 614 Access-Request if available. 616 A summary of the Network Capability Advertisement Attribute is 617 shown below. 619 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 620 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 621 | Type | Length |Minimum Outbound Bandwidth (MOB) 622 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 623 MOB (Cont.) |Minimum Inbound Bandwidth (MIB) 624 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 625 MIB (Cont.) |Maximum Outbound Bandwidth (XOB) 626 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 627 XOB (Cont.) |Maximum Inbound Bandwidth (XIB) 628 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 629 XIB (Cont.) | 630 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 632 Name 634 Network Capability Advertisement 636 Type 638 To be assigned by IANA 640 Length 642 16 644 Minimum Outbound Bandwidth 646 The minimum bandwidth (bits per second) that can be 647 guaranteed by the PWLAN AN for outbound packets. 649 Minimum Inbound Bandwidth 651 The minimum bandwidth (bits per second) that can be 652 guaranteed by PWLAN AN for inbound packets. 654 Maximum Outbound Bandwidth 656 The maximum bandwidth (bits per second) that can be 657 guaranteed by the PWLAN AN for outbound packets. 659 Maximum Inbound Bandwidth 661 The maximum bandwidth (bits per second) that can be 662 guaranteed by the PWLAN AN for inbound packets. 664 Attribute (Specifying Network capabilities) 666 This attribute indicates network capability settings that MUST 667 be used for a PWLAN client. It is allowed only in Access-Accept 668 packets. However, it MUST NOT be present in Access-Accept if 669 network capabilities were not advertised in the Access-Request. 671 A summary of the Specifying Network Capabilities Attribute is 672 shown below. 674 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 675 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 676 | Type | Length | Capability Identifier | 677 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 678 | Minimum Outbound Bandwidth | 679 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 680 | Minimum Inbound Bandwidth | 681 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 682 | Maximum Outbound Bandwidth | 683 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 684 | Maximum Inbound Bandwidth | 685 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 687 Name 689 Specifying Network Capability Settings 691 Type 693 To be assigned by IANA 695 Length 697 18 699 Capability Identifier 701 A unique identifier used by the HSN RADIUS AAA to identify 702 a specific network capability settings. 704 Minimum Outbound Bandwidth 706 The minimum bandwidth (bits per second) specified by the 707 HSN RADIUS AAA. It MUST be equal or greater than the 708 advertised Minimum Outbound Bandwidth. 710 Minimum Inbound Bandwidth 712 The minimum bandwidth (bits per second) specified by the HSN 713 RADIUS AAA. It MUST be equal or greater than the advertised 714 Minimum Inbound Bandwidth. 716 Maximum Outbound Bandwidth 718 The maximum bandwidth (bits per second) specified by the HSN 719 RADIUS AAA. It MUST be equal or less than the advertised 720 Maximum Outbound Bandwidth. 722 Maximum Inbound Bandwidth 724 The maximum bandwidth (bits per second) specified by the HSN 725 RADIUS AAA. It MUST be equal or less than the advertised 726 Maximum Inbound Bandwidth. 728 Attribute (Network Capability Settings for Accounting) 730 This attribute indicates Network capability settings in use for 731 a PWLAN client for accounting purposes. It SHOULD be sent in 732 Accounting-Request records where the Acc-Status-Type is set to 733 Start or Stop. 735 A summary of the Network Capability for Accounting is shown 736 below. 738 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 739 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 740 | Type | Length | Capability Identifier | 741 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 743 Name 745 Network Capability Settings for Accounting 747 Type 749 To be assigned by IANA 751 Length 753 2 755 Capability Identifier 757 A unique ID known by the HSN RADIUS AAA that indicates 758 specific capability settings. 760 4. IANA Considerations 762 To be completed 764 This draft introduces new RADIUS Attributes. Therefore, there is 765 a need for obtaining new attribute TYPE numbers from IANA. 767 5. Security Considerations 769 The attributes in this document have no additional security 770 considerations beyond those already identified in [?]. 772 6. Contributors 774 This document is a joint work of the contributing authors (in 775 alphabetical order): 777 - Farid Adrangi (Intel) 778 - Farooq Bari (AT&T Wireless) 779 - Blair Bullock (iPass) 780 - Kountal Chowdury (Nortel) 781 - Pasi Eronen (Nokia) 782 - Mark Grayson (Cisco) 783 - Ed Van Horne (Cisco) 784 - Jouni Korhonen (teliasonera) 785 - Victor Lortz (Intel) 786 - Avi Lior (Bridgewater) 787 - Serge Manning (Sprint) 788 - Jose Puthenkulam (Intel) 790 7. Acknowledgements 792 The authors would like to thank Bernrad Aboba (of Microsoft), 793 Parviz Yeganeh (of Cisco), Gopal Dommety (of Cisco) for their 794 feedback and guidance. 796 8. References 798 [1] Rigney, C., Rubens, A., Simpson, W. and S. Willens, "Remote 799 Authentication Dial In User Server (RADIUS)", RFC 2865, June 800 2000. 802 [2] Rigney, C., "RADIUS Accounting", RFC 2866, June 2000. 804 [3] Rigney, C., Willats, W., Calhoun, P., "RADIUS Extensions", RFC 805 2869, June 2000. 807 [4] Chiba, M., Dommety, G., Eklund, M., Mitton, D., Aboba, B., 808 "Dynamic Authorization Extensions to Remote Authentication 809 Dial-In User Service (RADIUS)", Internet Draft (work in 810 progress), RFC 3576, July 2003. 811 [5] Crocker, D. and P. Overell, "Augmented BNF for Syntax 812 Specifications: ABNF", RFC 2234, November 1997. 814 [6] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA 815 Considerations Section in RFCs", BCP 26, RFC 2434, October 816 1998. 818 [7] C. Perkins, "IP Mobility Support for IPv4", RFC 3344, August 819 2002. 821 [8] Droms, R., "Dynamic Host Configuration Protocol", RFC 2131, 822 March 1997. 824 Authors� Addresses 826 Farid Adrangi 827 Email: farid.adrangi@intel.com Phone:+1 503-712-1791 828 Farooq Bari 829 Email : Farooq.bari@attws.com Phone: 830 Blair Bullock 831 Email: bbullock@ipass.com Phone: 832 Pasi Eronen 833 Email: pasi.eronen@nokia.com 834 Mark Grayson 835 Email: mgrayson@cisco.com Phone: 836 Victor Lortz 837 Email: victor.lortz@intel.com Phone:+1 503-264-3253 838 Jose Puthenkulam 840 Full Copyright Statement 842 Copyright (C) The Internet Society (2002). All Rights 843 Reserved. 845 This document and translations of it may be copied and 846 furnished to others, and derivative works that comment on or 847 otherwise explain it or assist in its implementation may be 848 prepared, copied, published and distributed, in whole or in 849 part, without restriction of any kind, provided that the above 850 copyright notice and this paragraph are included on all such 851 copies and derivative works. However, this document itself may 852 not be modified in any way, such as by removing the copyright 853 notice or references to the Internet Society or other Internet 854 organizations, except as needed for the purpose of developing 855 Internet standards in which case the procedures for copyrights 856 defined in the Internet Standards process must be followed, or 857 as required to translate it into languages other than English. 859 The limited permissions granted above are perpetual and will 860 not be revoked by the Internet Society or its successors or 861 assigns. 863 This document and the information contained herein is provided 864 on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET 865 ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR 866 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE 867 OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY 868 IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A 869 PARTICULAR PURPOSE. 871 Acknowledgement 872 Funding for the RFC Editor function is currently provided by 873 the Internet Society.