Received-SPF: softfail (google.com: domain of transitioning linux-wireless-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19;
From:   Philip Prindeville <philipp_subx@redfish-solutions.com>
Content-Type: text/plain;
        charset=utf-8
Content-Transfer-Encoding: 8BIT
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.80.82.1.1\))
Subject: What's required for WiFi 6 Certified Location service?
Message-Id: <D6C016DA-086E-4CB1-80DA-A40839B714AE@redfish-solutions.com>
Date:   Tue, 12 Apr 2022 13:40:27 -0600
To:     linux-wireless@vger.kernel.org
Precedence: bulk

Hi all,

Not my wheelhouse...  and I've not read through the WiFi 6 Certified Location service specification, but does anyone have an idea of what would be required to support this in out-of-the-box Linux?

Per this news release:

https://www.wi-fi.org/news-events/newsroom/wi-fi-certified-location-brings-wi-fi-indoor-positioning-capabilities

> Wi-Fi Location™, based on the Fine Timing Measurement (FTM) protocol from IEEE 802.11-2016, delivers meter-level accuracy for indoor device location data.

Looking in include/linux/ieee80211.h I see:

include/linux/ieee80211.h:	WLAN_PUB_ACTION_FTM_REQUEST = 32,
include/linux/ieee80211.h:	WLAN_PUB_ACTION_FTM = 33,

But these don't appear anywhere else in the tree.

It also states:

> Each AP in a Wi-Fi Location network is configured with its exact location, including geospatial coordinates (latitude, longitude, and altitude), and civic address. This allows more precise location determination than with other solutions, even in multilevel structures.

But doesn't specify how that location is exchanged with the client.

Is anyone in the Linux kernel community working on an FTM implementation?

Thanks