]> Cisco Systems

10 New Square Park Feltham TW14 8HA UK mgrayson@cisco.com

CableLabs

858 Coal Creek Cr. Louisville 80027 US j.redmore@cablelabs.com

general RADEXT Working Group Internet-Draft Connect-Info RADIUS This document describes a syntax for the Connect-Info attribute used with the RADIUS protocol, enabling RADIUS clients to provide RADIUS servers information pertaining to a user's connection with an IEEE 802.11 wireless network.

Introduction The Connect-Info attribute is defined in to enable a Network Access Server (NAS) to indicate to a RADIUS server "the nature of the user's connection". includes the recommendation that:

• The connection speed SHOULD be included at the beginning of the first Connect-Info attribute in the packet. If the transmit and receive connection speeds differ, they MAY both be included in the first attribute with the transmit speed first (the speed the NAS modem transmits at), a slash (/), the receive speed, then optionally other information.

but where the definition of "speed" is not defined in . The Connect-Info attribute can be sent in both Access-Request and Accounting-Request messages, as shown in .

Many NAS implementations have implemented the Connect-Info attribute. Wi-Fi vendors supporting the Connect-Info attribute start the text field with "CONNECT" that is followed by a floating point value representing the maximum connection speed in Mbps. Implementations follow this with text information about the IEEE 802.11 amendment supported, as illustrated in .

Other implementations have extended this baseline to signal additional information to the RADIUS server using a slash (/) delimiter, as illustrated in . Note, these examples together with the recommendation in are illustrations of complex data types, as described in section 3.2.3 of .

There are use-cases that benefit from being able to share Wi-Fi network connection metrics between a NAS and a server, including where the NAS is operated by an Access Network Provider (ANP) and the server is operated by an Identity Provider (IDP). Reception of the Connect-Info attribute by a RADIUS server is intended to be used to assist the IDP in making authorization decisions. The rest of this document describes a syntax for the Connect-Info attribute that is simultaneously able to support existing, complex data type, vendor implementations as illustrated in and , while being enhanced with additional optional information to support new use-cases and requirements. Whereas discourages the introduction of new complex data types where viable alternatives exist, it is argued that the present document does not introduce a new complex data type, rather extends the syntax widely used in existing implementations of the Connect-Info attribute that currently encode a complex data type. Note, the techniques by which a server uses the information encoded in the Connect-Info attribute to assist in making authorization decisions are not defined in this document. Some servers MAY define the use a threshold for one or more parameters received in an access-request, other systems MAY use historical Connect-Info records from previously authenticated sessions, including those in the accounting-request messages received from the same NAS, still other systems MAY decide to algorithmically combine the parameters into a new metric used when making authorization decisions.

Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here.

Terminology Access Network Provider (ANP):

• A Wi-Fi operator that has configured its Wi-Fi equipment to support inbound roaming of users.

Identity Provider (IDP):

• An entity that authenticates end-user Wi-Fi devices onto ANP networks.

Received Signal Strength Indicator (RSSI):

• A measurement of the power level that is received by an antenna from a wireless device.

Types of Connect-Info Metrics The access network characteristics that can be shared between NAS and AAA include those that can be used to derive a quality metric of the performance of a Wi-Fi network. These include characteristics associated with the IEEE 802.11 connection: transmit and receive bit rates, received signal strength indicator (RSSI), frame loss rate, and frame retry rate. The inclusion of the above parameters in a Connect-Info attribute signalled in a RADIUS Access-Request message, or RADIUS Accounting-Request with Acct-Status-Type set to Start, is restricted by the number of IEEE 802.11 frames over which the calculation are based. In such cases, the transmit bit rates, receive bit rates and RSSI level MAY correspond to the instantaneous value of the specific parameter. In other cases, e.g., where the Connect-Info attribute is signalled in RADIUS Accounting-Request messages with Acct-Status-Type set to Interim-Update or Stop, the NAS SHOULD use multiple measurements when calculating the reported value: the reported transmit and receive bit rates SHOULD represent the maximum values experienced since the last time the connect-info was signalled. the received signal strength indicator (RSSI) SHOULD represent the average RSSI value, where the average value calculated MAY be either a linear average or an exponential weighted average. frame loss rate and frame retry rate SHOULD represent the average rates, where the average value calculated MAY be either a linear average or an exponential weighted average. While not uniquely associated with the IEEE 802.11 connection, describes legacy implementations which include generic parameters concerning the configuration of the Wi-Fi network in the Connect-Info attribute. These legacy parameters include: the Wi-Fi amendment , the Wi-Fi channel number, and the maximum Wi-Fi transmit rate.

ABNF syntax for Connect-Info The Augmented Backus-Naur form (ABNF) is a syntax for specifications defined in . The proposed ABNF syntax for the text of the Connect-Info attribute used with Wi-Fi networks is shown below. This syntax is intended to encompass current vendor implementations while supporting optional enhancements to support sharing of new parameters.

Example encoding in Access-Request The Connect-Info attribute value is limited to 253 bytes. Example encodings using the ABNF definition are illustrated in , indicating that the metrics can be signaled while keeping the attribute size below 253 bytes.

Implementations In July 2024, a proof of concept was built using modified hostapd code (https://w1.fi/) that is able to populate the connect-info attributes according to the syntax defined above. In December 2024, Helium Network (www.helium.com) upgraded their deployment of 17,000 OpenWi-Fi/OpenWRT Wi-Fi Access points to support the enhanced connect-info attribute.

Security Considerations This document describes a syntax that enables a RADIUS client to provide a RADIUS server information pertaining to the operation of an IEEE 802.11 wireless network. The terms agreed between the operator of the RADIUS client and the operator of the RADIUS server SHOULD include restrictions on the use of such non-personal information by the operator of the RADIUS server, for example limiting the use of such information to making RADIUS server authorization decisions and prohibiting a RADIUS server from disclosing information signalled in the Connect-Info attribute to any third-party.

IANA Considerations This document has no IANA Actions.

In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings. This document describes additional attributes for carrying authentication, authorization and accounting information between a Network Access Server (NAS) and a shared Accounting Server using the Remote Authentication Dial In User Service (RADIUS) protocol described in RFC 2865 and RFC 2866. This memo provides information for the Internet community. Internet technical specifications often need to define a formal syntax. Over the years, a modified version of Backus-Naur Form (BNF), called Augmented BNF (ABNF), has been popular among many Internet specifications. The current specification documents ABNF. It balances compactness and simplicity with reasonable representational power. The differences between standard BNF and ABNF involve naming rules, repetition, alternatives, order-independence, and value ranges. This specification also supplies additional rule definitions and encoding for a core lexical analyzer of the type common to several Internet specifications. [STANDARDS-TRACK] This document provides guidelines for the design of attributes used by the Remote Authentication Dial In User Service (RADIUS) protocol. It is expected that these guidelines will prove useful to authors and reviewers of future RADIUS attribute specifications, within the IETF as well as other Standards Development Organizations (SDOs). This memo documents an Internet Best Current Practice.

Changelog 01 - Added extensibility to ABNF and corrected syntax. Added security considerations section. Added note on TxBitRate/RxBitRate when included in Accounting-Request type Stop. 02 - Corrected ABNF syntax definition of RATE. 03 - Switched to independent submission. Updated ABNF to ease parsing of key/value pairs. 04 - Updated ABNF i) switching from band to global operating class, ii) added Wi-Fi Alliance generational name support as an alternative to 802.11 amendment designator, iii) permit legacy absolute and signed representations of signal strength, and iv) added WAN-RTT attribute 05 - Added clarifications that information is shared to enable a RADIUS server to make improved authorization decisions. Switched back to IETF submission. Added text about aligning with legacy implementations that do not adhere to RFC6158. 06 - Following RADEXT feedback at IETF 124, removed non-connection orientated key-value pairs from the syntax definition.

Acknowledgements The authors would like to thank all the members of the WBA's Access Network Metrics project team who have helped review and refine the Connect-Info syntax.

Contributors Cisco Systems

170 West Tasman Drive San Jose 95134 US sgundave@cisco.com

Wireless Broadband Alliance

5000 Executive Parkway, Suite 302 San Ramon 94583 US bruno@wballiance.com

Single Digits

4 Bedford Farms Drive, Suite 210 Bedford 1608 US msym@singledigits.com

Boldyn Networks

Pleasanton US blair.bullock@boldyn.com

Helium

Boulder US jpadden@helium.com