1 / 9

Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: IEEE802.15.3: SSID an

Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: IEEE802.15.3: SSID and PNID proposal Date Submitted: 12 March, 2002 Source: Dr. William Shvodian Company: XtremeSpectrum, Inc. Address: 8133 Leesburg Pike, Suite 700, Vienna, VA 22182

ayita
Download Presentation

Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: IEEE802.15.3: SSID an

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: IEEE802.15.3: SSID and PNID proposal Date Submitted: 12 March, 2002 Source: Dr. William Shvodian Company: XtremeSpectrum, Inc. Address: 8133 Leesburg Pike, Suite 700, Vienna, VA 22182 Voice: 703-269-3047 , FAX: 703-269-3092 , E-Mail: bshvodian@xtremespectrum.com Re: [ ] Abstract: Proposal for SSIDs and modified PNID usage, LB 12 comment 1524, 1467 Purpose: To provide information for comment resolution of , LB 12 comment 1524, 1467 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 Dr. William Shvodian

  2. Overview • Piconet Identification • Secure Communication of MAC addresses Dr. William Shvodian

  3. 802.15.3 D09 Baseline • PNID is random and sent in every frame in the piconet. PNID specified as a random number, but there is an issue of whether it is dynamic or whether it is a lasting value. • 48 bit MAC address (device identifier) is sent in every Beacon • DEVs send their 48 bit address in the association command Dr. William Shvodian

  4. Problems with the baseline • It is not clear what the lifetime of a PNID is. Does the PNC change PNID every time the piconet starts, or does it stay the same? This is currently undefined. • If PNID is random, DEV won’t know if it is the right piconet to join. It could use MAC address, but PNC can change • MAC address in beacon and in association commands limit anonymity • Snoopers can listen and monitor where DEVs go or what vendor equipment someone has in their home • Adjacent piconets may have the same PNID (1 in 65535 chance of choosing same PNID) – Can lead to DEVs receiving frame from the wrong piconet Dr. William Shvodian

  5. Proposal 1: Replace MAC address in the Beacon with a SSID identical to 802.11 • SSID is 6-32 octets information element • SSID is used to allow a DEV to quickly identify the piconet, not for security • User creates it’s own SSID, like “shvodian_home_piconet” • If no GUI in the PNC, it may choose a random SSID • 16 bit PNID is still used in headers of every frame (chosen by PNC – maybe random, maybe 16 bit hash on the SSID?) • SSID is used in 802.11 Dr. William Shvodian

  6. How do DEVs get the SSID? • If there is a sophisticated GUI, SSID can be manually entered • If there is not a sophisticated GUI, the DEV will find the proper PNC the first time using some unspecified means like button pushing, range detection or other. Then, the DEV stores the SSID for future use for quickly finding the correct piconet for fast association. • SSID is persistent once programmed in, regardless of which DEV is the PNC. Dr. William Shvodian

  7. Proposal 2: Remove MAC address from Beacon and Association frames • Use SSID in beacon instead of 48 bit MAC address of PNC • Use random 48 bit number in the association command instead of MAC address • MAC addresses are only sent encrypted when security is on. This prevents an eavesdropper from identifying people or manufacturers of equipment. Dr. William Shvodian

  8. Proposal 3: • Add a new command to allow a DEV to tell the PNC “I heard another beacon with the same PNID.” This will inform the PNC that it should choose a new PNID. • Add a new command from the PNC to tell DEVs that the PNID will be changing. Dr. William Shvodian

  9. Summary • Use SSID instead of PNC MAC address in the beacons • Remove MAC address from the association command, so that MAC addresses are only transmitted while encrypted when command protection is used. • Add 2 new commands, One to allow a DEV to tell the PNC that there is another piconet in range with the same PNID and another to Dr. William Shvodian

More Related