Received-SPF: pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
References: <CAAooHFeLWrY_wmCp-HWqygh8gnKsfpoPCky7SykOBKZgXkb8OQ@mail.gmail.com>
 <20190403210200.GA93453@google.com> <211816ff03cf188d834a21b1fbc98b4f8c5b81f4.camel@sipsolutions.net>
 <CA+ASDXOyXb0dPGOrjQR7C-b6dyftiZhkta3cwG28B9sC5wxHxQ@mail.gmail.com>
 <7687225C-D965-479E-BAE8-769B0AEADD76@holtmann.org> <CA+ASDXNC0hwFzSTvZmUq-B7r_H+pZ3N=p_kjfMqKb1gftsmDKw@mail.gmail.com>
 <7CCE8D56-9E1A-4E04-9C28-E384C1B2E2EA@holtmann.org>
In-Reply-To: <7CCE8D56-9E1A-4E04-9C28-E384C1B2E2EA@holtmann.org>
From:   Brian Norris <briannorris@chromium.org>
Date:   Wed, 21 Aug 2019 09:54:57 -0700
Message-ID: <CA+ASDXPhX3Yet=dJn8Pet_inP1uyueFZqBmuNXvmTrjv1r497g@mail.gmail.com>
Subject: Re: Flag for detecting 802.11r Fast BSS Transition support
To:     Marcel Holtmann <marcel@holtmann.org>
Cc:     Johannes Berg <johannes@sipsolutions.net>,
        Matthew Wang <matthewmwang@google.com>,
        linux-wireless <linux-wireless@vger.kernel.org>,
        Kirtika Ruchandani <kirtika@google.com>,
        Jouni Malinen <j@w1.fi>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-wireless-owner@vger.kernel.org
Precedence: bulk

On Sat, Aug 17, 2019 at 6:40 AM Marcel Holtmann <marcel@holtmann.org> wrote:
> And if you have a distribution or an OEM that cares, then that is what is going to happen.

I can see where you might not be particularly sympathetic to this
concern, but where I re-started this thread, I added in Jouni, due to
his mention of:

"There are such drivers [supporting FT] especially in number of
Android devices and I'd
rather not break those use cases.." [1]

That doesn't exactly sound like a case where he's willing to break
compatibility with older kernels in new wpa_supplicant. But maybe I
shouldn't put words in his mouth. (On the other hand, Android systems
are likely to not ever get either kernel *or* wpa_supplicant version
upgrades, so maybe it's not really a problem at all!)

Anyway, I'll just cook a patch, and then figure out whether/how I can
teach wpa_supplicant to respect it. (Or, continue forking
wpa_supplicant as we have been wont to do...)

Brian

[1] http://lists.infradead.org/pipermail/hostap/2019-April/039951.html