Privacy Address Requirements for Wireless Personal Area Networks
This document discusses the privacy address requirements for IEEE P802.15 Working Group's TG4ab standard for Wireless Personal Area Networks (WPANs). It covers the need for 48-bit addresses with collision resistance, the use of different privacy addresses for each frame, and the adequacy of 12-bit collision resistance. The document raises questions about the necessity of unique privacy addresses for every frame, the sufficiency of collision resistance, and the introduction of 48-bit addresses in the standard.
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. Download presentation by click this link. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
E N D
Presentation Transcript
Nov 2023 Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) doc.: 802-15-23-0579-00 Submission Title: Privacy address requirements for TG4ab Date Submitted: 14th November, 2023 Source: Tero Kivinen E-Mail: kivinen@iki.fi Re: Pre ballot TG4ab draft Company - Abstract: Provide a listof requiremets of privacy addressing in TG4ab Purpose: Trying to find out what are the requirements set .by TG4ab Notice: This document has been prepared to assist the IEEE P802.15. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. Release: The contributor acknowledges and accepts that this contribution becomes the property of IEEE and may be made publicly available by P802.15. Submission Page 1 Tero Kivinen
Nov 2023 doc.: 802-15-23-0579-00 Sources P802.15.4ab-pre-ballot-B.pdf contains section 10.35.9.2.1 Private addresses and this was used to find out what are the requirements for the TG4ab private addresses Submission Page 2 Tero Kivinen
Nov 2023 doc.: 802-15-23-0579-00 Address format 6-octet (48-bit) address with 12 bits of collision resistance. Meaning after few thousands of invocations of this functions there will be collisions where wrong device will be marked as resolved. Requres cryptographically strong pseudo random number generator, which is used for every single frame Every single frame has different source address. Submission Page 3 Tero Kivinen
Nov 2023 doc.: 802-15-23-0579-00 Question 1 Do we really need to use different privacy address for every single frame? The distance of the device to be measured does not really change that much, so most likely the timing of the frames will allow attacker to keep track who is who, even if the addresses are different every single time. Submission Page 4 Tero Kivinen
Nov 2023 doc.: 802-15-23-0579-00 Question 2 Is the 12-bit collision resistance really enough? This will mean that if you have two devices in the network then after only few thousands of frames they will generate same 24-bit RPA_hash that will match other devices RPA_hash and wrong source is assumed. Submission Page 5 Tero Kivinen
Nov 2023 doc.: 802-15-23-0579-00 Question 3 Why 48-bit addresses? We already have 16-bit and 64-bit addresses in the IEEE Std 802.15.4, so why we need to have new 48-bit addresses? Submission Page 6 Tero Kivinen
Nov 2023 doc.: 802-15-23-0579-00 Question 4 Is it really requirement to use CSPRNG when generating the addresses, especially how weak they are? When the addresses has so weak collision properties, using CSPRNG to generate them is overkill. Submission Page 7 Tero Kivinen
Nov 2023 doc.: 802-15-23-0579-00 Question 5 Is there a mechanism that will solve the issues caused by the collision in ranging addresses? Submission Page 8 Tero Kivinen
