I got the impression Extended Key IDs were added without updating all
sections which should get updates. But the pattern is suspect, even the igtk
numbers fit into the pattern:
PTK 0 & 1
GTK 1 & 2 & 3
iGTK 4 & 5
An AP is allowed to do this, but there is no requirement for doing so.
The pairwise key (TK, not PTK) is required to use Key ID 0 unless the > optional Extended Key ID for Individually Addressed Frames capability is
negotiated (and 0 or 1 if that capability is negotiated). Group keys
(GTK) are allowed to use Key IDs 0..4. IGTKs are allowed to use Key ID
values 4 and 5.
There is a long history behind this and some de facto constraints due to
that history and possible implementation constraints. However, as far as
the protocol itself is concerned, there would be no real need for having
IGTK use 4..5; it could have as well been 0..1 or 1..2 or whatever
combination the AP would like to use.
These three cases have completely independent namespaces for Key IDs as
far as RSN is concerned with one exception: "Use group cipher suite"
that was added as an option for some AP implementation that did not
support individual key mapping. That special case would end up using GTK
for both group-addressed and individually-addressed frames. That said,
I'm not aware of there having ever been an actually deployed device with
this constraint and even if there were, this mode is highly discouraged
and should not be used for anything today. Anyway, this exception and
similar implementation constraints are likely behind the expectations of
TK and GTK having to use different Key ID values.
Thanks for the clarifications!
If there really are drivers using "Use group cipher suite" it does not
sound like they would be able to support Extended Key ID with APs using
key ID 1+2 for GTKs. But sounds not likely anyone would need that...
My experimentation with hw accel and Extended Key ID for existing
drivers so far are also indicating that it will work using the keyid 1
for both PTK and GTK, so this should be a trivial change in hostapd only.
As far as the kernel changes are concerned, cfg80211 and mac80211 should
support everything that's allowed by the standard, i.e., use of Key IDs
0..3 for GTK. It is up to the user space implementation on the AP side
(e.g., hostapd) to select which Key IDs are actually taken into use.
I'm pretty sure that is already the case, but so far I only tested it
with GTK shifted to 2+3. I'll make sure to test the next revision with
GTK using 1+2 also. I'll test that once I get that working again from
end2end. The patch here is getting a bit dated and makes no sense to
invest time for that win it.
Alexander
