TG bh Identifiable Random MAC Address

Nov 2021
TG bh
Identifiable Random MAC Address
Date:
 2021-10
Authors:
Graham Smith, SR Technologies
Slide 1
This is a presentation on “Identifiable Random MAC Address”, IRMA
Rev 1,
Presented initial idea to TGbh 10/12/2021
Rev 2,
Added “No IRMK found” to cover case when the AP has deleted the “old” IRMKs.  AP can ask for
new IRMK (STA sends new or same)
Added “Private” to IRM element to allow IRM STA to use a private MAC address (eliminate need to
set I/G bit)
Rev 3
Added “IRMK Check” 
Used
 to down-select stored IRMKs in AP
Used to confirm back to STA that correct IRMK has been found
Rev 4 - Discussed Change to stop any possible brute force attack
Rev 5 - Delete Provide IRMK ? (can’t see a good use case for it)
Rev 6 - Worked on Advantages.  Corrected ANQP-element
Rev 7 - Added IRMK Check Request and Response.
Rev 8 – Added slides on security
Rev 9 – Added IRMK Check numbers and performance
Rev 10 – Edits, counter to “spoof”, delete Criteria slide
Rev 11 – Added time to find IRMK.
Intro
Nov 2021
Graham Smith, SR Technologies
Slide 2
MAC Address 48-bit
Two Types:
Fixed
Assigned MAC.
Random
Two types,
Non-identifiable
 - random, STA does not want to be known in any way
Identifiable 
– random, but STA wishes to be identified/remembered by
particular APs (networks)
MAC Addresses
Nov 2021
Graham Smith, SR Technologies
Slide 3
Identifiable Random MAC (IRM) 
: a scheme where a non-AP STA uses
identifiable random medium access control (MAC) addresses (IRMA) to
prevent third parties from tracking the non-AP STA while still allowing
trusted parties to identify the non-AP STA
.
Identifiable Random MAC Address (IRMA) – a r
andom MAC address used by
a STA using IRM
Identifiable Random MAC Key (IRMK) – 
a
 
Key used to resolve an IRMA
802.11 Definitions
Nov 2021
Graham Smith, SR Technologies
Slide 4
Purpose
Prevent third-parties from tracking the STA while still allowing trusted
parties to recognize the STA.
Identifiable
Uses a key shared with trusted AP/network – IRMK
IRMA is the random TA MAC address used by the STA
STA generates an “
IRM Hash
” using 
IRMK and IRMA
IRM Hash is sent in IRM element 
(in Association Request)
STA can use different IRMK for every network, and change at will.
Changing TA address
TA MAC Address (IRMA) changes every use.
Does NOT use same MAC address for each ESS
Identifiable Random MAC Address - IRMA
Nov 2021
Graham Smith, SR Technologies
Slide 5
Two basic random MAC address types:
Random private (changes randomly, non-identifiable))
Random identifiable  IRMA
MAC Address is 48 bits
Least significant bit of first octet (“I/G bit”)
0 = unicast, 1 = multicast
Second-least-significant bit of the first octet (“U/L bit”)
0 = globally unique, 1 = locally administered
Random MAC is described in Clause 12.2.10 (D0.0)
“The STA shall construct the randomized MAC address from the 
locally administered address
space
Note:  Also compatible with SLAP if the 4 bits are required.
IRMA
 looks like any other randomized MAC address
,
IF IRM element includes the IRM Hash, then the address is an IRMA, i.e.,
“identifiable”
IF IRM element indicates “Private”, the IRM Hash is NOT sent and the
address is a private randomized MAC, i.e., NOT an IRMA.
IRM Address (IRMA)
Nov 2021
Graham Smith, SR Technologies
Slide 6
An IRM Capability field is used in the STA and AP
The AP looks for the IRM Capability AND the IRM Hash in IRM
element
AP can use the IRM Capability bit to indicate to STAs that there
may be a reason to be identified, i.e., “I provide a service”
CAPABILITY BIT
Nov 2021
Graham Smith, SR Technologies
Slide 7
IRMK (Identifiable Random MAC Key)
1.
STA generates the IRMK
Could be constant; could vary for each SSID; could be preset.
2.
STA shares IRMK with AP when first associated
3.
STA provides IRM Hash in “IRM element”
4.
The IRMK is used to resolve the identity of the STA
verifies that the hash included in the IRM element matches the output of
the local hash computation
 
IRM hash = function (IRMK, IRMA)
Since the AP has the IRMK stored locally and has access to the IRMA included as the MAC
address and the IRM Hash in the association packet, it can perform this computation and verify the
IRMK
NOTE: Scheme is based on known proven technology – “key derivation functions”.
A typical usage is take a secret, such as a password or a shared key (IRMK), and a random number
(known as a ‘salt’) (IRMA) to produce a key (IRM Hash). Used in many applications.
IRMK and Hash function
Nov 2021
Graham Smith, SR Technologies
Slide 8
Proposed to use SHA-256 truncated to 128 bits*, i.e.:
IRM Hash = SHA-256/128 (IRMK, IRMA)
Where SHA-256/128 is the truncated SHA-256 where 
the leftmost 128
bits of the 256-bit hash generated by SHA-256 are selected as the truncated
128 bit IRM Hash
A 3
rd
 party chance of discovering the IRMK?
Pre-image resistance
1 in 2 
128  
(See slide 18)
Chance that AP finds wrong key or more than one key?
Hash collision
1 in 2 
64
Two STAs pick same key , 1 in 2
64
AP can ask for “New IRMK Request”
Note: AP can ask for new key if IRMK not found or duplicate, for example
* 
Could use other hash functions.  Want to select a function already known and used.
IRM Hash
Nov 2021
Graham Smith, SR Technologies
Slide 9
1.
STA and AP indicates IRM support in Extended Capability Field
2.
STA generates 48 bit IRMA
1.
Generates a random 46 bit number
2.
Appends I/G = 0, U/L = 1  (Compatible with 12.2.10)
3.
STA calculates IRM Hash value and includes it in the IRM element
1.
Element included in (re)association frame
2.
Element may be included pre-association ANQP frames
4.
STA also indicates other information for the AP, e.g.:
1.
First time association “Unknown”
2.
Been here before (you should have my key) “Known”
3.
Been here before but want to change key “Change”
5.
When 
first 
associated, “Unknown” STA provides IRMK to AP
1.
Action frame Request and Response exchange(s)
6.
AP uses IRMA and stored IRMKs to calculate hash and identify the STA IRMK.
It’s important to note that the 
IRMK is not used to reveal the STA’s MAC or “identity”
address 
but rather for verification purposes only, i.e., the hash matches
Basic Steps for IRM
Nov 2021
Graham Smith, SR Technologies
Slide 10
IRM element
Nov 2021
Graham Smith, SR Technologies
Slide 11
STA can use “private” address
IRM element sent in Association Request
AP then knows if STA IRMK already known (stored) or not
Change – Eliminates all chances of a
brute-force attack.
See next slide
IRMK Check field
Nov 2021
Graham Smith, SR Technologies
Slide 12
IRMK Offset takes a value N, from 0 to 112  (Note: IRMK is 128 bits)
The Check field contains the 8 bits representing the EX-OR of the 8 bits of the IRMK, b
N
 to
b
N+7 
with the following 8 bits (b
N+8
 to b
N+15
)
i.e.  For n = 0 to 7
Bits in Check field are
 
b
n
 = EX-OR (b
N+n
, b
N+n+8
)          where 
 
b
N
 is Nth bit in IRMK
     
As an example, IRKM Offset = 72
Check field b0 is EX_OR of bits 72 and 80, and b7 is EX-OR of bits 79 and 87
Acts as a “Hint” to the AP so AP can quickly find a stored IRMK.
Reduces the list of IRMKs by 1/256
e.g. correct key in a list of 1000 IRMKs found in just 2 calculations
Note that 256 combinations of the 16 bits satisfy the 8 bit Check field.
Reduces the integrity of key from 128 bits to 120 bits (see slide 18
)
Action Frames to get IRMK
Nov 2021
Graham Smith, SR Technologies
Slide 13
STA sends “Unknown”
AP sends IRMK Request, STA sends IRMK Response with IRMK
STA sends “Known” or “Change”
AP sends IRMK Confirm optionally with “IRMK check”
AP can request New IRMK (with reasons)
STA can change IRMK whenever it wants (prevents any possible brute-force
attack
AP can request “IRMK Check” (If many IRMKs stored for example).
IRMK Confirm
Nov 2021
Graham Smith, SR Technologies
Slide 14
The IRMK Confirm Action frame is transmitted from an AP to a non-AP
STA to confirm that an IRMK has been recognized
The Check field 
allows the STA to check that it is the right IRMK without having to
send 128 bits.
To provide extra security, AP confirms IRMK and STA can check it
without having to declare the full IRMK
If AP has many IRMKs and STA did not include the IRMK Check field in
IRM element, then AP can request it.
Also, AP can send Check Request, to confirm that the STA is who it says
it is.  NOTE: STA MUST respond with 
different IRMK Offset 
than that
used in IRM element used in Association.
Possibly make this mandatory every association so as to prevent any “spoofing” of the MAC
address and Hash??
Is this spoof a real problem?  Spoof would have to have Password to the network for this to be
of use. Then why pretend to be someone else?  If AP asks for IRMK Check, then spoof is
exposed.
Notes:
We could consider STA always includes Check in IRM element
IF STA recognizes AP as a “busy AP” then STA should include IRMK Check.
AP could always challenge STA to provide the Check (different Offset)
IRMK Check Request/Response
Nov 2021
Graham Smith, SR Technologies
Slide 15
AP requests new IRMK
Nov 2021
Graham Smith, SR Technologies
Slide 16
AP can request a new IRMK (provides reason)
REASON
AP might delete stored IRMKs
Old
Capacity
If STA associates as “Known” and IRMK not found, then AP can
request a new IRMA
Pre-Association
Nov 2021
Graham Smith, SR Technologies
Slide 17
STA can send IRM ANQP-element
AP can use the IRM Hash and the IRMA (TA) to find the IRMK
(Can only be used if AP already has the IRMK)
The “IRMK Check” field allows the AP to down-select list
Reduces APs stored list by 1/256
Only reduces security from 128 bits to 120 bits.
3
rd
 party must perform average of 2
119
 (6.4 x 10
35
) hash calculations to find the IRMK.
To find IRMK in 1 month requires 2.56 x 10
20
 calculations per nanosecond)
(note: Has to check IRMK for every STA that associates as TA and HASH change
every association, and if STA changes IRMK then impossible.  STAs might choose to
change IRMKs at regular intervals, say each week.)
Down-Select at AP with IRMK Check
2
16
 combinations for 16 bits, 2
8
 combinations for 8 bit EXOR
Down Select is 2
16
/2
8
 = 256 i.e. 1000 IRMKs down selected to 4.
1000 IRMKs in store, AP, on average, needs to check 
2
 to find correct IRMK
IRM Check field also used by AP to Confirm IRMK back to STA.
This provides  double security that the AP is who it says it is, i.e. the same AP that
was originally used to share the Key
Security
Nov 2021
Graham Smith, SR Technologies
Slide 18
Every time STA associates, the address IRMA AND IRM Hash
values change.
Impossible to know if same STA associating.
Third party would need to brute strength all keys, IRMK (128
bits, or 120 bits if using IRMK Check), to find the IRMK.  BUT,
next time STA associates 
third party must again check IRMKs as no
correlation between the IRMK and the TA (IRMA) and Hash.
IF STA changes IRMK (once associated) then IMPOSSIBLE to
know the STA.
STA can use a different IRMK for every AP, AND change it
whenever
IRM is very Secure
Nov 2021
Graham Smith, SR Technologies
Slide 19
IRM enables the AP to identify the STA,
i.e. STA “123”
AP can exchange frames or higher layer APP can then
associate STA 123 with some other specific details/IDs
Membership ID , customer ID, guest ID, family member,
employee ID, etc.
STA details
Nov 2021
Graham Smith, SR Technologies
Slide 20
A different Random MAC can be used even when returning to same ESS – more privacy!
Even though STA indicates “Known”, No way a 3
rd
 party can know if same STA (unlike “same MAC address for same
AP”)
 MAC address and IRM Hash field values change every time.  The last associated IRMK stays constant at the AP.
An IRM STA can still choose to use “private” random MAC
If no IRM Hash field, then private MAC address in use.
STA can change IRMK at any time
Changed when associated.  Hence even if brute force were practical to find IRMK, if changed, impossible to know if same
STA reassociates
AP still knows that it is STA X even though IRMK has changed
AP can restrict its stored list if necessary and request a new IRMK if “No IRMK found”
STA can provide old or new
However, “IRMK Check” allows AP to keep a large store. 1/256 reduction in list
STA can be identified pre-association
AP can check stored IRMKs as soon as Association Request received OR wait for association
 STA can send IRMK-ANQP element
No reference to any ‘real’ address or real ID
Spoof attacks can be countered
Very flexible, easy to add Action frames
NOTE:  Compatible with the ID Action frames
.
Provides an ID that solves many Use Case problems created by RCM
Advantages
Nov 2021
Graham Smith, SR Technologies
Slide 21
Document 21/1673 is the working document for the
accompanying text
IRM Text
Nov 2021
Graham Smith, SR Technologies
Slide 22
Nov 2021
Graham Smith, SR Technologies
Slide 23
QUESTIONS??
Do you agree that an Identifiable Random MAC
scheme, along the lines as described in <this
document>,  should be included in the TGbh
Amendment?
Straw Poll
Nov 2021
Graham Smith, SR Technologies
Slide 24
Slide Note

doc.: IEEE 802.11-

April 2013

Graham Smith, DSP Group

Page

Embed
Share

This document discusses the concept of Identifiable Random MAC Addresses (IRMA) within IEEE 802.11-21/1585r11 standard. It covers the purpose of IRMA in preventing tracking by third parties while allowing recognition by trusted entities. Topics include IRMA definitions, IRM Key (IRMK), and practical implementations. The presentation outlines the advantages, security aspects, and performance considerations related to using IRMAs.

  • IEEE 802.11
  • Identifiable Random MAC Address
  • IRMA
  • IRMK
  • Security

Uploaded on Feb 15, 2025 | 0 Views


Download Presentation

Please find below an Image/Link to download the presentation.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.

You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.

E N D

Presentation Transcript


  1. Nov 2021 doc.: IEEE 802.11-21/1585r11 TG bh Identifiable Random MAC Address Date: 2021-10 Authors: Name Company Address Phone email Olivia Fernandez SRT Group Sunrise , FL ofernandez@srtrl.com Graham Smith SRT Group Sunrise , FL gsmith@srtrl.com Submission Slide 1 Graham Smith, SR Technologies

  2. Nov 2021 doc.: IEEE 802.11-21/1585r11 Intro Rev 1, Rev 2, This is a presentation on Identifiable Random MAC Address , IRMA Presented initial idea to TGbh 10/12/2021 Added No IRMK found to cover case when the AP has deleted the old IRMKs. AP can ask for new IRMK (STA sends new or same) Added Private to IRM element to allow IRM STA to use a private MAC address (eliminate need to set I/G bit) Rev 3 Added IRMK Check Used to down-select stored IRMKs in AP Used to confirm back to STA that correct IRMK has been found Rev 4 - Discussed Change to stop any possible brute force attack Rev 5 - Delete Provide IRMK ? (can t see a good use case for it) Rev 6 - Worked on Advantages. Corrected ANQP-element Rev 7 - Added IRMK Check Request and Response. Rev 8 Added slides on security Rev 9 Added IRMK Check numbers and performance Rev 10 Edits, counter to spoof , delete Criteria slide Rev 11 Added time to find IRMK. Submission Slide 2 Graham Smith, SR Technologies

  3. Nov 2021 doc.: IEEE 802.11-21/1585r11 MAC Addresses MAC Address 48-bit Two Types: Fixed Assigned MAC. Random Two types, Non-identifiable - random, STA does not want to be known in any way Identifiable random, but STA wishes to be identified/remembered by particular APs (networks) Submission Slide 3 Graham Smith, SR Technologies

  4. Nov 2021 doc.: IEEE 802.11-21/1585r11 802.11 Definitions Identifiable Random MAC (IRM) : a scheme where a non-AP STA uses identifiable random medium access control (MAC) addresses (IRMA) to prevent third parties from tracking the non-AP STA while still allowing trusted parties to identify the non-AP STA. Identifiable Random MAC Address (IRMA) a random MAC address used by a STA using IRM Identifiable Random MAC Key (IRMK) aKey used to resolve an IRMA Submission Slide 4 Graham Smith, SR Technologies

  5. Nov 2021 doc.: IEEE 802.11-21/1585r11 Identifiable Random MAC Address - IRMA Purpose Prevent third-parties from tracking the STA while still allowing trusted parties to recognize the STA. Identifiable Uses a key shared with trusted AP/network IRMK IRMA is the random TA MAC address used by the STA STA generates an IRM Hash using IRMK and IRMA IRM Hash is sent in IRM element (in Association Request) STA can use different IRMK for every network, and change at will. Changing TA address TA MAC Address (IRMA) changes every use. Does NOT use same MAC address for each ESS Submission Slide 5 Graham Smith, SR Technologies

  6. Nov 2021 doc.: IEEE 802.11-21/1585r11 IRM Address (IRMA) Two basic random MAC address types: Random private (changes randomly, non-identifiable)) Random identifiable IRMA MAC Address is 48 bits Least significant bit of first octet ( I/G bit ) 0 = unicast, 1 = multicast Second-least-significant bit of the first octet ( U/L bit ) 0 = globally unique, 1 = locally administered Random MAC is described in Clause 12.2.10 (D0.0) The STA shall construct the randomized MAC address from the locally administered address space Note: Also compatible with SLAP if the 4 bits are required. IRMA looks like any other randomized MAC address, IF IRM element includes the IRM Hash, then the address is an IRMA, i.e., identifiable IF IRM element indicates Private , the IRM Hash is NOT sent and the address is a private randomized MAC, i.e., NOT an IRMA. Submission Slide 6 Graham Smith, SR Technologies

  7. Nov 2021 doc.: IEEE 802.11-21/1585r11 CAPABILITY BIT An IRM Capability field is used in the STA and AP The AP looks for the IRM Capability AND the IRM Hash in IRM element AP can use the IRM Capability bit to indicate to STAs that there may be a reason to be identified, i.e., I provide a service Bit Information Notes <ANA> IRM Capability The STA sets IRM Capability subfield to 1 to indicate support for IRM and sets to 0 if IRM Capability is not supported. Submission Slide 7 Graham Smith, SR Technologies

  8. Nov 2021 doc.: IEEE 802.11-21/1585r11 IRMK and Hash function IRMK (Identifiable Random MAC Key) 1. STA generates the IRMK Could be constant; could vary for each SSID; could be preset. 2. STA shares IRMK with AP when first associated 3. STA provides IRM Hash in IRM element 4. The IRMK is used to resolve the identity of the STA verifies that the hash included in the IRM element matches the output of the local hash computation IRM hash = function (IRMK, IRMA) Since the AP has the IRMK stored locally and has access to the IRMA included as the MAC address and the IRM Hash in the association packet, it can perform this computation and verify the IRMK NOTE: Scheme is based on known proven technology key derivation functions . A typical usage is take a secret, such as a password or a shared key (IRMK), and a random number (known as a salt ) (IRMA) to produce a key (IRM Hash). Used in many applications. Submission Slide 8 Graham Smith, SR Technologies

  9. Nov 2021 doc.: IEEE 802.11-21/1585r11 IRM Hash Proposed to use SHA-256 truncated to 128 bits*, i.e.: IRM Hash = SHA-256/128 (IRMK, IRMA) Where SHA-256/128 is the truncated SHA-256 where the leftmost 128 bits of the 256-bit hash generated by SHA-256 are selected as the truncated 128 bit IRM Hash A 3rd party chance of discovering the IRMK? Pre-image resistance 1 in 2 128 (See slide 18) Chance that AP finds wrong key or more than one key? Hash collision 1 in 2 64 Two STAs pick same key , 1 in 264 AP can ask for New IRMK Request Note: AP can ask for new key if IRMK not found or duplicate, for example * Could use other hash functions. Want to select a function already known and used. Submission Slide 9 Graham Smith, SR Technologies

  10. Nov 2021 doc.: IEEE 802.11-21/1585r11 Basic Steps for IRM 1. 2. STA and AP indicates IRM support in Extended Capability Field STA generates 48 bit IRMA 1. Generates a random 46 bit number 2. Appends I/G = 0, U/L = 1 (Compatible with 12.2.10) STA calculates IRM Hash value and includes it in the IRM element 1. Element included in (re)association frame 2. Element may be included pre-association ANQP frames STA also indicates other information for the AP, e.g.: 1. First time association Unknown 2. Been here before (you should have my key) Known 3. Been here before but want to change key Change When first associated, Unknown STA provides IRMK to AP 1. Action frame Request and Response exchange(s) AP uses IRMA and stored IRMKs to calculate hash and identify the STA IRMK. 3. 4. 5. 6. It s important to note that the IRMK is not used to reveal the STA s MAC or identity address but rather for verification purposes only, i.e., the hash matches Submission Slide 10 Graham Smith, SR Technologies

  11. Nov 2021 doc.: IEEE 802.11-21/1585r11 IRM element STA can use private address IRM element sent in Association Request AP then knows if STA IRMK already known (stored) or not Element ID Length Element ID Extension 1 Figure 9-yyy IRM element format IRM Indicator IRM Hash (Not present if IRM Indicator set to 0) (16) IRMK Check (Optional) Octets: 1 1 1 (2) Table 9 zzz IRM indicator IRMK Offset Check 1 IRM Indicator field value 0 Field name Notes Octets: 1 Figure 9-jjj IRMK Check field format See next slide Private A non-AP STA sets the IRM Indicator field value to 0 to indicate that the non-AP STA is using a private random MAC address, i.e., is not using an IRMA A non-AP STA sets the IRM Indicator field value to 1 to indicate that the non-AP STA has not previously provided an IRMK to the AP A non-AP STA sets the IRM Indicator field value to 2 to indicate that the non-AP STA has previously provided an IRMK to the AP A non-AP STA sets the the IRM Indicator field value to 3 to indicate that the non-AP STA has previously provided an IRMK to the AP but will change the IRMK once associated 1 Unknown 2 Known 3 Change Change Eliminates all chances of a brute-force attack. 3-255 Reserved Submission Slide 11 Graham Smith, SR Technologies

  12. Nov 2021 doc.: IEEE 802.11-21/1585r11 IRMK Check field IRMK Offset Check 1 Octets: 1 Figure 9-jjj IRMK Check field format IRMK Offset takes a value N, from 0 to 112 (Note: IRMK is 128 bits) The Check field contains the 8 bits representing the EX-OR of the 8 bits of the IRMK, bN to bN+7 with the following 8 bits (bN+8 to bN+15) i.e. For n = 0 to 7 Bits in Check field are bn = EX-OR (bN+n, bN+n+8) where As an example, IRKM Offset = 72 Check field b0 is EX_OR of bits 72 and 80, and b7 is EX-OR of bits 79 and 87 bN is Nth bit in IRMK Acts as a Hint to the AP so AP can quickly find a stored IRMK. Reduces the list of IRMKs by 1/256 e.g. correct key in a list of 1000 IRMKs found in just 2 calculations Note that 256 combinations of the 16 bits satisfy the 8 bit Check field. Reduces the integrity of key from 128 bits to 120 bits (see slide 18) Submission Slide 12 Graham Smith, SR Technologies

  13. Nov 2021 doc.: IEEE 802.11-21/1585r11 Action Frames to get IRMK Table 9-bbb IRM Action field Action field value 0 1 2 3 4 5 6-255 Meaning IRMK Request IRMK Response IRMK Confirm New IRMK Request IRMK Check Request IRMK Check Response Reserved STA sends Unknown AP sends IRMK Request, STA sends IRMK Response with IRMK STA sends Known or Change AP sends IRMK Confirm optionally with IRMK check AP can request New IRMK (with reasons) STA can change IRMK whenever it wants (prevents any possible brute-force attack AP can request IRMK Check (If many IRMKs stored for example). Submission Slide 13 Graham Smith, SR Technologies

  14. Nov 2021 doc.: IEEE 802.11-21/1585r11 IRMK Confirm To provide extra security, AP confirms IRMK and STA can check it without having to declare the full IRMK Category IRM Action 1 IRMK Check 2 Octets: 1 Figure 9-eee IRMK Confirm Action field format The IRMK Confirm Action frame is transmitted from an AP to a non-AP STA to confirm that an IRMK has been recognized IRMK Offset Check 1 Octets: 1 Figure 9-jjj IRMK Check field format The Check field allows the STA to check that it is the right IRMK without having to send 128 bits. Submission Slide 14 Graham Smith, SR Technologies

  15. Nov 2021 doc.: IEEE 802.11-21/1585r11 IRMK Check Request/Response If AP has many IRMKs and STA did not include the IRMK Check field in IRM element, then AP can request it. Also, AP can send Check Request, to confirm that the STA is who it says it is. NOTE: STA MUST respond with different IRMK Offset than that used in IRM element used in Association. Possibly make this mandatory every association so as to prevent any spoofing of the MAC address and Hash?? Is this spoof a real problem? Spoof would have to have Password to the network for this to be of use. Then why pretend to be someone else? If AP asks for IRMK Check, then spoof is exposed. Notes: We could consider STA always includes Check in IRM element IF STA recognizes AP as a busy AP then STA should include IRMK Check. AP could always challenge STA to provide the Check (different Offset) Submission Slide 15 Graham Smith, SR Technologies

  16. Nov 2021 doc.: IEEE 802.11-21/1585r11 AP requests new IRMK AP can request a new IRMK (provides reason) Table 9-ddd IRMK Reason field values IRMK Reason field value 0 No reason provided 1 Non-AP STA requested change 2 No IRMK found 3 Duplicate Key exists 4 Key not random 5-255 Reserved Meaning REASON AP might delete stored IRMKs Old Capacity If STA associates as Known and IRMK not found, then AP can request a new IRMA Submission Slide 16 Graham Smith, SR Technologies

  17. Nov 2021 doc.: IEEE 802.11-21/1585r11 Pre-Association STA can send IRM ANQP-element AP can use the IRM Hash and the IRMA (TA) to find the IRMK (Can only be used if AP already has the IRMK) Info ID Length IRM Hash IRM Check (optional) Octets: 1 1 16 Figure 9-xyz IRM ANQP-element format Submission Slide 17 Graham Smith, SR Technologies

  18. Nov 2021 doc.: IEEE 802.11-21/1585r11 Security The IRMK Check field allows the AP to down-select list Reduces APs stored list by 1/256 Only reduces security from 128 bits to 120 bits. 3rd party must perform average of 2119 (6.4 x 1035) hash calculations to find the IRMK. To find IRMK in 1 month requires 2.56 x 1020 calculations per nanosecond) (note: Has to check IRMK for every STA that associates as TA and HASH change every association, and if STA changes IRMK then impossible. STAs might choose to change IRMKs at regular intervals, say each week.) Down-Select at AP with IRMK Check 216 combinations for 16 bits, 28 combinations for 8 bit EXOR Down Select is 216/28 = 256 i.e. 1000 IRMKs down selected to 4. 1000 IRMKs in store, AP, on average, needs to check 2 to find correct IRMK IRM Check field also used by AP to Confirm IRMK back to STA. This provides double security that the AP is who it says it is, i.e. the same AP that was originally used to share the Key Submission Slide 18 Graham Smith, SR Technologies

  19. Nov 2021 doc.: IEEE 802.11-21/1585r11 IRM is very Secure Every time STA associates, the address IRMA AND IRM Hash values change. Impossible to know if same STA associating. Third party would need to brute strength all keys, IRMK (128 bits, or 120 bits if using IRMK Check), to find the IRMK. BUT, next time STA associates third party must again check IRMKs as no correlation between the IRMK and the TA (IRMA) and Hash. IF STA changes IRMK (once associated) then IMPOSSIBLE to know the STA. STA can use a different IRMK for every AP, AND change it whenever Submission Slide 19 Graham Smith, SR Technologies

  20. Nov 2021 doc.: IEEE 802.11-21/1585r11 STA details IRM enables the AP to identify the STA, i.e. STA 123 AP can exchange frames or higher layer APP can then associate STA 123 with some other specific details/IDs Membership ID , customer ID, guest ID, family member, employee ID, etc. Submission Slide 20 Graham Smith, SR Technologies

  21. Nov 2021 doc.: IEEE 802.11-21/1585r11 Advantages A different Random MAC can be used even when returning to same ESS more privacy! Even though STA indicates Known , No way a 3rdparty can know if same STA (unlike same MAC address for same AP ) MAC address and IRM Hash field values change every time. The last associated IRMK stays constant at the AP. An IRM STA can still choose to use private random MAC If no IRM Hash field, then private MAC address in use. STA can change IRMK at any time Changed when associated. Hence even if brute force were practical to find IRMK, if changed, impossible to know if same STA reassociates AP still knows that it is STA X even though IRMK has changed AP can restrict its stored list if necessary and request a new IRMK if No IRMK found STA can provide old or new However, IRMK Check allows AP to keep a large store. 1/256 reduction in list STA can be identified pre-association AP can check stored IRMKs as soon as Association Request received OR wait for association STA can send IRMK-ANQP element No reference to any real address or real ID Spoof attacks can be countered Very flexible, easy to add Action frames NOTE: Compatible with the ID Action frames. Provides an ID that solves many Use Case problems created by RCM Submission Slide 21 Graham Smith, SR Technologies

  22. Nov 2021 doc.: IEEE 802.11-21/1585r11 IRM Text Document 21/1673 is the working document for the accompanying text Submission Slide 22 Graham Smith, SR Technologies

  23. Nov 2021 doc.: IEEE 802.11-21/1585r11 QUESTIONS?? Submission Slide 23 Graham Smith, SR Technologies

  24. Nov 2021 doc.: IEEE 802.11-21/1585r11 Straw Poll Do you agree that an Identifiable Random MAC scheme, along the lines as described in <this document>, should be included in the TGbh Amendment? Submission Slide 24 Graham Smith, SR Technologies

Related


More Related Content

giItT1WQy@!-/#giItT1WQy@!-/#giItT1WQy@!-/#giItT1WQy@!-/#giItT1WQy@!-/#