idnits 2.17.00 (12 Aug 2021) /tmp/idnits55493/draft-adrangi-radius-location-information-attribut-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: ---------------------------------------------------------------------------- ** Bad filename characters: the document name given in the document, 'draft-adrangi-RadiusExt-location-information-00', contains other characters than digits, lowercase letters and dash. == Mismatching filename: the document gives the document name as 'draft-adrangi-RadiusExt-location-information-00', but the file name used is 'draft-adrangi-radius-location-information-attribut-00' == 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 32 has weird spacing: '... The list ...' == Line 197 has weird spacing: '...eration is i...' == Line 266 has weird spacing: '...rmation attri...' == Line 291 has weird spacing: '... found in wh...' == Line 301 has weird spacing: '... This docum...' == (2 more instances...) == Couldn't figure out when the document was first submitted -- there may comments or warnings related to the use of a disclaimer for pre-RFC5378 work that could not be issued because of this. Please check the Legal Provisions document at https://trustee.ietf.org/license-info to determine if you need the pre-RFC5378 disclaimer. -- 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 115 == Missing Reference: '6' is mentioned on line 138, but not defined == Missing Reference: '3' is mentioned on line 169, but not defined Summary: 3 errors (**), 0 flaws (~~), 15 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group F. Adrangi, Intel 3 INTERNET DRAFT C. Black, P. Congdon, Hewlett Packard 4 Category: Informational F. Bari, AT&T Wireless 5 Expires: June 2004 S. ala-luukko, J. Korhonen, Teliasonera 6 A. Lior, Bridgewater 7 E. Van Horne, Mark Grayson, Cisco 8 J. Tuomi, Nokia 9 January 6, 2004 11 Attributes for Access Network Location and Ownership 12 Information 14 draft-adrangi-RadiusExt-location-information-00.txt 16 Status of this Memo 18 This document is an Internet-Draft and is in full conformance 19 with all provisions of Section 10 of RFC2026. 21 Internet-Drafts are working documents of the Internet 22 Engineering Task Force (IETF), its areas, and its working 23 groups. Note that other groups may also distribute working 24 documents as Internet-Drafts. 26 Internet-Drafts are draft documents valid for a maximum of six 27 months and may be updated, replaced, or obsoleted by other 28 documents at any time. It is inappropriate to use Internet- 29 Drafts as reference material or to cite them other than as "work 30 in progress." 32 The list of current Internet-Drafts can be accessed at 33 http://www.ietf.org/ietf/1id-abstracts.txt 35 The list of Internet-Draft Shadow Directories can be accessed at 36 http://www.ietf.org/shadow.html. 38 Abstract 40 This document describes RADIUS Authentication, Authorization, 41 Accounting (AAA) attributes that are used to convey the Access 42 Network’s operational ownership and Location Information to a 43 Home Service Network. 45 Internet Draft Access Network Location Information 47 Table of Contents 49 1. Introduction....................................................2 50 1.2 Applicability..................................................3 51 1.3 Requirements language..........................................3 52 1.4 Terminology....................................................3 53 2. Overview........................................................3 54 2.1 Operator-Name Attribute........................................3 55 2.2 Location-Name Attribute........................................4 56 2.3 Location-Information Attribute.................................4 57 3. Operation.......................................................4 58 3.1 Attributes.....................................................4 59 3.1.1 Operator-Name Attribute......................................5 60 3.1.2 Location-Name Attribute......................................5 61 3.1.3 Location-Information Attribute...............................6 62 4. Table of Attributes............................................6 63 5. IANA Considerations.............................................6 64 5. Security Considerations.........................................7 65 6. Acknowledgements................................................7 66 7. References......................................................7 67 Authors’ Addresses.................................................7 69 1. Introduction 71 Wireless LAN (WLAN) Access Networks (AN) are being deployed in 72 public places such as airports, hotels, shopping malls, and coffee 73 shops by a diverse set of incumbent operators such as cellular 74 carriers (GSM and CDMA), Wireless Internet Service Providers 75 (WISP), and fixed broadband operators. 77 When a Public Wireless Local Area Network (PWLAN) client connects 78 to a PWLAN AN, the information pertaining to the PWLAN AN location 79 and operational ownership needs to be conveyed to the PWLAN 80 client’s Home Service Network (HSN). The intent of PWALN AN 81 location-related information is to enable use case scenarios for 82 location aware billing (e.g., determine the appropriate tariff and 83 taxation), location aware subscriber authentication / authorization 84 in roaming, and location aware services. 86 Standard bodies / forums (such as 3GPP, 3GPP2, GSMA) and WiFi 87 Alliance public access III have already defined Vendor Specific 88 Attributes (VSA) with different format/syntax and content for 89 indicating location-related information. However, common 90 understanding and Standardization of these attributes is essential 91 to enable improved interoperability and hence successful 92 deployments of PWLANs. 94 This document describes AAA attributes that are used by an AAA 95 client or a local AAA server/proxy in an AN for conveying location- 96 related information to the HSN AAA server. The attributes are 97 described for RADIUS [1]. 99 Internet Draft Access Network Location Information 101 1.2 Applicability 103 Although proposed attributes in this draft are intended for PWLAN 104 deployments, they can also be used in other networks (e.g., wired 105 networks) where location-aware services are required. 107 1.3 Requirements language 109 In this document, several words are used to signify the 110 requirements of the specification. These words are often 111 capitalized. The key words "MUST", "MUST NOT", "REQUIRED", 112 "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", 113 "MAY", and "OPTIONAL" in this document are to be interpreted as 114 described in [RFC2119]. 116 1.4 Terminology 118 Access Network (AN) 119 The PWLAN hotspot network that provides wireless connectivity 120 to the Internet for WLAN clients (or stations) present in the 121 local access area. This MAY be in a separate security and 122 routing domain with respect to the Home Service Network or a 123 Mediating Network. 125 Home Service Network (HSN) 126 The network providing the service and therefore maintaining 127 the direct relationship to the user/subscriber of the WLAN 128 service. All AAA functions are ultimately performed by the 129 HSN. 131 Access Point (AP) 132 A station that provides access to the distribution services 133 via the wireless medium for associated Stations. 135 RADIUS server 136 This is a server which provides for 137 authentication/authorization via the protocol described in 138 [1], and for accounting as described in [6]. It is deployed in 139 the PWLAN AN, MN, and HSN. 141 2. Overview 143 The AN location and operational ownership information is conveyed 144 in three AAA attributes which are: Operator-Name, Location-Name, 145 and Location-Information. The description of these attributes is 146 as follows. 148 2.1 Operator-Name Attribute 150 Internet Draft Access Network Location Information 152 This attribute contains an operator name which uniquely identifies 153 the ownership of an AN. The Attribute value is a non-NULL 154 terminated string whose Length MUST NOT exceed xxxx. The 155 attribute value is comprised of the prefix and the Identity, 156 separated by a colon. The prefix identifies the operator type; 157 example: GSM, CDMA. And, the Identity uniquely identifies the 158 operator name within the scope of the operator type. Examples: 159 GSM:TADIC where GSM is a prefix indicating an operator type and 160 TADIC is a unique globally known GSM operator ID. 162 This document defines three prefixes which are: GSM, CDMA, and 163 REALM. 165 2.2 Location-Name Attribute 167 This attribute contains country name, telephone area code, city 168 name where an AN is located, and location type of the AN such as 169 airport, hotel, coffee shop, bookstore, and etc. E.164 [3] format 170 is used for identifying country name and telephone area code. A 171 city name is a non-NULL terminated string whose length MUST NOT 172 exceed 64 octets. This document defines the following integer 173 codes for AN location type: 175 0 Reserved 176 1 Coffee Shop 177 2 Hotel 178 3 Airport 179 4 Shopping Mall 180 5 Restaurant 181 9 Library 182 10 Convention Center 183 11 School 184 12 Enterprise 185 13 Airplane 186 14 Train 188 2.3 Location-Information Attribute 190 This attribute contains a descriptive information in English 191 language about the AN’s Location that can be printed into 192 subscriber’s detailed bill. The information is presented as a non- 193 NULL terminated string whose length MUST NOT exceed 64 octets. 195 3. Operation 197 Operation is identical to that defined in RADIUS AAA 198 specifications [1][2]. 200 3.1 Attributes 202 Internet Draft Access Network Location Information 204 This section defines attributes for AN operational ownership and 205 location Information. 207 3.1.1 Operator-Name Attribute 209 Operator-Name Attribute SHOULD be sent in Access-Request, and 210 Accounting-Request records where the Acc-Status-Type is set to 211 Start, Interim, or Stop. 213 A summary of the Operator-Name Attribute is shown below. 215 0 1 2 216 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 217 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- 218 | Type | Length | Text... 219 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- 221 Type: 222 To Be Assigned by IANA - Operator-Name 224 Length: 225 >= 3 227 Text: 228 The text field contains an Access Network Operator Name in 229 prefix-based format as describe above. Example: 230 REALM:anyisp.com 232 3.1.2 Location-Name Attribute 234 Location-Name Attribute SHOULD be sent in Access-Request, and 235 Accounting-Request records where the Acc-Status-Type is set to 236 Start, Interim, or Stop if available. 238 A summary of the Location-Name Attribute is shown below. 240 0 1 2 3 241 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 242 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 243 | TYPE | LENGTH | text | 244 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 246 Type: 247 To Be Assigned by IANA - Location-Name 249 LENGTH: 250 >= 3 252 Text: 253 The text is a string which should be of the form: 255 Internet Draft Access Network Location Information 257 cc=,cn=,lt= 260 Example: 262 cc=1,ac=503,cn=Portland,lt=1 264 3.1.3 Location-Information Attribute 266 Location-Information attribute SHOULD be sent in Access- 267 Request, and Accounting-Request records where the Acc-Status- 268 Type is set to Start, Interim or Stop if available. 270 A summary of the Location Information Attribute is shown below. 272 0 1 2 273 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 274 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- 275 | Type | Length | Text ... 276 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- 278 Type : 279 To Be Assigned by IANA - Location-Information 281 Length: 282 >= 3 284 Text: 285 The text field contains descriptive information about PWLAN 286 AN Location. Its length MUST NOT exceed 64 octets. 288 4. Table of Attributes 290 The following table provides a guide to which attributes may be 291 found in which kinds of packets, and in what quantity. 293 Request Accept Reject Challenge Accounting # Attribute 294 Request 295 0-1 0 0 0 0-1 TBD Operator-Name 296 0-1 0 0 0 0-1 TBD Location-Name 297 0-1 0 0 0 0-1 TBD Location-Information 299 5. IANA Considerations 301 This document requires the assignment of three new RADIUS 302 attribute numbers for the following attributes: 304 Operator-Name 306 Internet Draft Access Network Location Information 308 Location-Name 309 Location-Information 311 See section 4 for the registered list of numbers. 313 6. Security Considerations 315 The attributes in this document have no additional security 316 considerations beyond those already identified in [1]. 318 7. Acknowledgements 320 The authors would like to thank Victor Lortz (of Intel), Jose 321 Puthenkulam (of Intel), Bernrad Aboba (of Microsoft), Jari Arkko 322 (of Ericson), Parviz Yegani (of Cisco), Serge Manning (of Sprint), 323 Kuntal Chowdury (of Nortel), Pasi Eronen (of Nokia), and Blair 324 Bullock (of iPass), Eugene Chang (of Funk) for their feedback and 325 guidance. 327 8. References 329 [1] Rigney, C., Rubens, A., Simpson, W. and S. Willens, "Remote 330 Authentication Dial In User Server (RADIUS)", RFC 2865, June 331 2000. 333 [2] Rigney, C., "RADIUS Accounting", RFC 2866, June 2000. 335 Authors’ Addresses 337 Farid Adrangi, Intel Corporatation farid.adrangi@intel.com 338 Chuck Black, Hewlett Packard Company chuck.black@hp.com 339 Paul Congdon, Hewlett Packard Company paul.congdon@hp.com 340 Jouni Korhonen, Teliasonera jouni.korhonen@teliasonera.com 341 Sami Ala-luukko, Teliasonera Sami.ala-luukko@teliasonera.com 342 Farooq Bari, AT&T Wireless farooq.bari@attws.com 343 Avi Lior, Bridgwater Systems Corporation avi@bridgewatersystems.com 344 Ed Van Horne, Cisco evh@cisco.com 345 Mark Grayson, Cisco mgrayson@cisco.com 346 Jukkat Tuomi, Nokia jukkat.tumoi@nokia.com 348 Full Copyright Statement 350 Copyright (C) The Internet Society (2002). All Rights 351 Reserved. 353 This document and translations of it may be copied and 354 furnished to others, and derivative works that comment on or 355 otherwise explain it or assist in its implementation may be 356 prepared, copied, published and distributed, in whole or in 358 Internet Draft Access Network Location Information 360 part, without restriction of any kind, provided that the above 361 copyright notice and this paragraph are included on all such 362 copies and derivative works. However, this document itself may 363 not be modified in any way, such as by removing the copyright 364 notice or references to the Internet Society or other Internet 365 organizations, except as needed for the purpose of developing 366 Internet standards in which case the procedures for copyrights 367 defined in the Internet Standards process must be followed, or 368 as required to translate it into languages other than English. 370 The limited permissions granted above are perpetual and will 371 not be revoked by the Internet Society or its successors or 372 assigns. 374 This document and the information contained herein is provided 375 on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET 376 ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR 377 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE 378 OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY 379 IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A 380 PARTICULAR PURPOSE. 382 Acknowledgement 384 Funding for the RFC Editor function is currently provided by 385 the Internet Society.