idnits 2.17.00 (12 Aug 2021) /tmp/idnits56017/draft-adrangi-radiusext-location-information-00.txt: 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 6 instances of lines with non-ascii characters in the document. == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 7) being 59 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 8 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == The "Author's Address" (or "Authors' Addresses") section title is misspelled. == Line 31 has weird spacing: '... The list ...' == Line 196 has weird spacing: '...eration is i...' == Line 265 has weird spacing: '...rmation attri...' == Line 290 has weird spacing: '... found in wh...' == Line 300 has weird spacing: '... This docum...' == (2 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 (January 6, 2004) is 6710 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- -- Looks like a reference, but probably isn't: 'RFC2119' on line 114 == Missing Reference: '6' is mentioned on line 137, but not defined == Missing Reference: '3' is mentioned on line 168, but not defined Summary: 2 errors (**), 0 flaws (~~), 13 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group F. Adrangi, Intel 2 INTERNET DRAFT C. Black, P. Congdon, Hewlett Packard 3 Category: Informational F. Bari, AT&T Wireless 4 Expires: June 2004 S. ala-luukko, J. Korhonen, Teliasonera 5 A. Lior, Bridgewater 6 E. Van Horne, Mark Grayson, Cisco 7 J. Tuomi, Nokia 8 January 6, 2004 10 Attributes for Access Network Location and Ownership 11 Information 13 draft-adrangi-radiusext-location-information-00.txt 15 Status of this Memo 17 This document is an Internet-Draft and is in full conformance 18 with all provisions of Section 10 of RFC2026. 20 Internet-Drafts are working documents of the Internet 21 Engineering Task Force (IETF), its areas, and its working 22 groups. Note that other groups may also distribute working 23 documents as Internet-Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six 26 months and may be updated, replaced, or obsoleted by other 27 documents at any time. It is inappropriate to use Internet- 28 Drafts as reference material or to cite them other than as "work 29 in progress." 31 The list of current Internet-Drafts can be accessed at 32 http://www.ietf.org/ietf/1id-abstracts.txt 34 The list of Internet-Draft Shadow Directories can be accessed at 35 http://www.ietf.org/shadow.html. 37 Abstract 39 This document describes RADIUS Authentication, Authorization, 40 Accounting (AAA) attributes that are used to convey the Access 41 NetworkÆs operational ownership and Location Information to a 42 Home Service Network. 44 Internet Draft Access Network Location Information 46 Table of Contents 48 1. Introduction....................................................2 49 1.2 Applicability..................................................3 50 1.3 Requirements language..........................................3 51 1.4 Terminology....................................................3 52 2. Overview........................................................3 53 2.1 Operator-Name Attribute........................................3 54 2.2 Location-Name Attribute........................................4 55 2.3 Location-Information Attribute.................................4 56 3. Operation.......................................................4 57 3.1 Attributes.....................................................4 58 3.1.1 Operator-Name Attribute......................................5 59 3.1.2 Location-Name Attribute......................................5 60 3.1.3 Location-Information Attribute...............................6 61 4. Table of Attributes............................................6 62 5. IANA Considerations.............................................6 63 5. Security Considerations.........................................7 64 6. Acknowledgements................................................7 65 7. References......................................................7 66 AuthorsÆ Addresses.................................................7 68 1. Introduction 70 Wireless LAN (WLAN) Access Networks (AN) are being deployed in 71 public places such as airports, hotels, shopping malls, and coffee 72 shops by a diverse set of incumbent operators such as cellular 73 carriers (GSM and CDMA), Wireless Internet Service Providers 74 (WISP), and fixed broadband operators. 76 When a Public Wireless Local Area Network (PWLAN) client connects 77 to a PWLAN AN, the information pertaining to the PWLAN AN location 78 and operational ownership needs to be conveyed to the PWLAN 79 clientÆs Home Service Network (HSN). The intent of PWALN AN 80 location-related information is to enable use case scenarios for 81 location aware billing (e.g., determine the appropriate tariff and 82 taxation), location aware subscriber authentication / authorization 83 in roaming, and location aware services. 85 Standard bodies / forums (such as 3GPP, 3GPP2, GSMA) and WiFi 86 Alliance public access III have already defined Vendor Specific 87 Attributes (VSA) with different format/syntax and content for 88 indicating location-related information. However, common 89 understanding and Standardization of these attributes is essential 90 to enable improved interoperability and hence successful 91 deployments of PWLANs. 93 This document describes AAA attributes that are used by an AAA 94 client or a local AAA server/proxy in an AN for conveying location- 95 related information to the HSN AAA server. The attributes are 96 described for RADIUS [1]. 98 Internet Draft Access Network Location Information 100 1.2 Applicability 102 Although proposed attributes in this draft are intended for PWLAN 103 deployments, they can also be used in other networks (e.g., wired 104 networks) where location-aware services are required. 106 1.3 Requirements language 108 In this document, several words are used to signify the 109 requirements of the specification. These words are often 110 capitalized. The key words "MUST", "MUST NOT", "REQUIRED", 111 "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", 112 "MAY", and "OPTIONAL" in this document are to be interpreted as 113 described in [RFC2119]. 115 1.4 Terminology 117 Access Network (AN) 118 The PWLAN hotspot network that provides wireless connectivity 119 to the Internet for WLAN clients (or stations) present in the 120 local access area. This MAY be in a separate security and 121 routing domain with respect to the Home Service Network or a 122 Mediating Network. 124 Home Service Network (HSN) 125 The network providing the service and therefore maintaining 126 the direct relationship to the user/subscriber of the WLAN 127 service. All AAA functions are ultimately performed by the 128 HSN. 130 Access Point (AP) 131 A station that provides access to the distribution services 132 via the wireless medium for associated Stations. 134 RADIUS server 135 This is a server which provides for 136 authentication/authorization via the protocol described in 137 [1], and for accounting as described in [6]. It is deployed in 138 the PWLAN AN, MN, and HSN. 140 2. Overview 142 The AN location and operational ownership information is conveyed 143 in three AAA attributes which are: Operator-Name, Location-Name, 144 and Location-Information. The description of these attributes is 145 as follows. 147 2.1 Operator-Name Attribute 149 Internet Draft Access Network Location Information 151 This attribute contains an operator name which uniquely identifies 152 the ownership of an AN. The Attribute value is a non-NULL 153 terminated string whose Length MUST NOT exceed xxxx. The 154 attribute value is comprised of the prefix and the Identity, 155 separated by a colon. The prefix identifies the operator type; 156 example: GSM, CDMA. And, the Identity uniquely identifies the 157 operator name within the scope of the operator type. Examples: 158 GSM:TADIC where GSM is a prefix indicating an operator type and 159 TADIC is a unique globally known GSM operator ID. 161 This document defines three prefixes which are: GSM, CDMA, and 162 REALM. 164 2.2 Location-Name Attribute 166 This attribute contains country name, telephone area code, city 167 name where an AN is located, and location type of the AN such as 168 airport, hotel, coffee shop, bookstore, and etc. E.164 [3] format 169 is used for identifying country name and telephone area code. A 170 city name is a non-NULL terminated string whose length MUST NOT 171 exceed 64 octets. This document defines the following integer 172 codes for AN location type: 174 0 Reserved 175 1 Coffee Shop 176 2 Hotel 177 3 Airport 178 4 Shopping Mall 179 5 Restaurant 180 9 Library 181 10 Convention Center 182 11 School 183 12 Enterprise 184 13 Airplane 185 14 Train 187 2.3 Location-Information Attribute 189 This attribute contains a descriptive information in English 190 language about the ANÆs Location that can be printed into 191 subscriberÆs detailed bill. The information is presented as a non- 192 NULL terminated string whose length MUST NOT exceed 64 octets. 194 3. Operation 196 Operation is identical to that defined in RADIUS AAA 197 specifications [1][2]. 199 3.1 Attributes 201 Internet Draft Access Network Location Information 203 This section defines attributes for AN operational ownership and 204 location Information. 206 3.1.1 Operator-Name Attribute 208 Operator-Name Attribute SHOULD be sent in Access-Request, and 209 Accounting-Request records where the Acc-Status-Type is set to 210 Start, Interim, or Stop. 212 A summary of the Operator-Name Attribute is shown below. 214 0 1 2 215 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 216 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- 217 | Type | Length | Text... 218 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- 220 Type: 221 To Be Assigned by IANA - Operator-Name 223 Length: 224 >= 3 226 Text: 227 The text field contains an Access Network Operator Name in 228 prefix-based format as describe above. Example: 229 REALM:anyisp.com 231 3.1.2 Location-Name Attribute 233 Location-Name Attribute SHOULD be sent in Access-Request, and 234 Accounting-Request records where the Acc-Status-Type is set to 235 Start, Interim, or Stop if available. 237 A summary of the Location-Name Attribute is shown below. 239 0 1 2 3 240 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 241 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 242 | TYPE | LENGTH | text | 243 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 245 Type: 246 To Be Assigned by IANA - Location-Name 248 LENGTH: 249 >= 3 251 Text: 252 The text is a string which should be of the form: 254 Internet Draft Access Network Location Information 256 cc=,cn=,lt= 259 Example: 261 cc=1,ac=503,cn=Portland,lt=1 263 3.1.3 Location-Information Attribute 265 Location-Information attribute SHOULD be sent in Access- 266 Request, and Accounting-Request records where the Acc-Status- 267 Type is set to Start, Interim or Stop if available. 269 A summary of the Location Information Attribute is shown below. 271 0 1 2 272 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 273 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- 274 | Type | Length | Text ... 275 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- 277 Type : 278 To Be Assigned by IANA - Location-Information 280 Length: 281 >= 3 283 Text: 284 The text field contains descriptive information about PWLAN 285 AN Location. Its length MUST NOT exceed 64 octets. 287 4. Table of Attributes 289 The following table provides a guide to which attributes may be 290 found in which kinds of packets, and in what quantity. 292 Request Accept Reject Challenge Accounting # Attribute 293 Request 294 0-1 0 0 0 0-1 TBD Operator-Name 295 0-1 0 0 0 0-1 TBD Location-Name 296 0-1 0 0 0 0-1 TBD Location-Information 298 5. IANA Considerations 300 This document requires the assignment of three new RADIUS 301 attribute numbers for the following attributes: 303 Operator-Name 305 Internet Draft Access Network Location Information 307 Location-Name 308 Location-Information 310 See section 4 for the registered list of numbers. 312 6. Security Considerations 314 The attributes in this document have no additional security 315 considerations beyond those already identified in [1]. 317 7. Acknowledgements 319 The authors would like to thank Victor Lortz (of Intel), Jose 320 Puthenkulam (of Intel), Bernrad Aboba (of Microsoft), Jari Arkko 321 (of Ericson), Parviz Yegani (of Cisco), Serge Manning (of Sprint), 322 Kuntal Chowdury (of Nortel), Pasi Eronen (of Nokia), and Blair 323 Bullock (of iPass), Eugene Chang (of Funk) for their feedback and 324 guidance. 326 8. References 328 [1] Rigney, C., Rubens, A., Simpson, W. and S. Willens, "Remote 329 Authentication Dial In User Server (RADIUS)", RFC 2865, June 330 2000. 332 [2] Rigney, C., "RADIUS Accounting", RFC 2866, June 2000. 334 AuthorsÆ Addresses 336 Farid Adrangi, Intel Corporatation farid.adrangi@intel.com 337 Chuck Black, Hewlett Packard Company chuck.black@hp.com 338 Paul Congdon, Hewlett Packard Company paul.congdon@hp.com 339 Jouni Korhonen, Teliasonera jouni.korhonen@teliasonera.com 340 Sami Ala-luukko, Teliasonera Sami.ala-luukko@teliasonera.com 341 Farooq Bari, AT&T Wireless farooq.bari@attws.com 342 Avi Lior, Bridgwater Systems Corporation avi@bridgewatersystems.com 343 Ed Van Horne, Cisco evh@cisco.com 344 Mark Grayson, Cisco mgrayson@cisco.com 345 Jukkat Tuomi, Nokia jukkat.tumoi@nokia.com 347 Full Copyright Statement 349 Copyright (C) The Internet Society (2002). All Rights 350 Reserved. 352 This document and translations of it may be copied and 353 furnished to others, and derivative works that comment on or 354 otherwise explain it or assist in its implementation may be 355 prepared, copied, published and distributed, in whole or in 357 Internet Draft Access Network Location Information 359 part, without restriction of any kind, provided that the above 360 copyright notice and this paragraph are included on all such 361 copies and derivative works. However, this document itself may 362 not be modified in any way, such as by removing the copyright 363 notice or references to the Internet Society or other Internet 364 organizations, except as needed for the purpose of developing 365 Internet standards in which case the procedures for copyrights 366 defined in the Internet Standards process must be followed, or 367 as required to translate it into languages other than English. 369 The limited permissions granted above are perpetual and will 370 not be revoked by the Internet Society or its successors or 371 assigns. 373 This document and the information contained herein is provided 374 on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET 375 ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR 376 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE 377 OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY 378 IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A 379 PARTICULAR PURPOSE. 381 Acknowledgement 383 Funding for the RFC Editor function is currently provided by 384 the Internet Society.