On Mon, 2020-01-06 at 11:26 +0200, Jouni Malinen wrote: > On Sat, Jan 04, 2020 at 11:10:09PM +0100, Alexander Wetzel wrote: > > Support Extended Key ID in hostapd according to IEEE 802.11-2016. > > > > Extended Key ID allows to rekey pairwise keys without the otherwise > > unavoidable MPDU losses on a busy link. The standard is fully backward > > compatible, allowing an AP to serve STAs with and without Extended Key > > ID support in the same BSS. > > The standard may claim to be fully backwards compatible, but that does > not mean there would be guarantee of no regressions or interop issues if > this were enabled.. I'd consider getting this in first with default > being the functionality being disabled. Once there is some more trust in > this actually working and not causing problems (e.g., an independent > implementation to test against), the default could be changed in the > future. You'll never find out if you don't enable it though? :) But are you thinking that clients might get confused by a new extended capability bit getting set? That's something that happens all the time. Or clients might erroneously set the extended capability bit for extended PTK IDs? johannes _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
