WiFi Privacy network experiment at IETF91 Date: [2015-01-13] Authors: NameAffiliationPhone Carlos Jesús Fabio

Slides:



Advertisements
Similar presentations
Omniran Network Detection and Selection Date: Authors: NameAffiliationPhone Max RiegelNSN
Advertisements

Omniran GPP Trusted WLAN Access to EPC Use Case Analysis Date: Authors: NameAffiliationPhone Max RiegelNSN
Omniran IEEE 802 Enhanced Network Detection and Selection Date: Authors: NameAffiliationPhone Max RiegelNSN
Omniran OmniRAN Wi-Fi Hotspot Roaming Use Case Date: Authors: NameAffiliationPhone Max RiegelNSN
SDN-based OmniRAN Use Cases Date: [ ] Authors: NameAffiliationPhone Antonio de la OlivaUC3M+34 Juan Carlos ZúñigaInterDigital+1.
Privecsg Bluetooth LE/Smart/v4 Privacy Aspects Date: [ ] Authors: NameAffiliationPhone Piers O’HanlonOxford Internet
Privecsg Tracking of Link Layer Identifiers Date: [ ] Authors: NameAffiliationPhone Juan Carlos ZúñigaInterDigital
Omniran OmniRAN Proximity Service use case Date: [ ] Authors: NameAffiliationPhone Hyunho ParkETRI
WiFi Privacy network experiment at IEEE Berlin Date: [ ] Authors: NameAffiliationPhone Carlos Jesús
Omniran IEEE 802 Scope of OmniRAN Date: Authors: NameAffiliationPhone Max RiegelNSN
OmniRAN ecsg SDN-based Control Plane and Data Plane Separation in OmniRAN Network Reference Model Date: Authors: NameAffiliationPhone .
Omniran ZigBee SEP2 Smart Grid Use Case Analysis Date: Authors: NameAffiliationPhone Max RiegelNSN
Omniran OmniRAN Wi-Fi Hotspot Roaming Use Case Date: Authors: NameAffiliationPhone Max RiegelNSN
Omniran PtP Links across IEEE 802 Bridged Infrastructure Date: Authors: NameAffiliationPhone Max
Omniran ZigBee SEP2 Smart Grid Use Case Analysis Date: Authors: NameAffiliationPhone Max RiegelNSN
OmniRAN SoA and Gap Analysis Date: [ ] Authors: NameAffiliationPhone Antonio de la Juan Carlos
OmniRAN-15-00xx WLAN as a Component (WaaC) Date: xx Authors: NameAffiliationPhone Yonggang FangZTETX Bo SunZTE He HuangZTE Notice:
OmniRAN – 3GPP SaMOG Document Number: IEEE Shet
Discussion on IEEE metrics guidelines Document Number: IEEE R0 Date Submitted: Source: Antonio BovoVoice:
Discussion on NRM Control Reference Points Information and Parameters Date: Authors: NameAffiliationPhone Antonio de la Oliva University.
Logical Interface Overview Date: [ ] Authors: NameAffiliationPhone Juan Carlos ZúñigaInterDigital Notice:
Privecsg ecsg 1 IEEE 802 EC Privacy Recommendation Study Group February 4 th, 2015, Conference Call Juan Carlos Zuniga, InterDigital Labs (EC.
Privecsg ‹#› IEEE 802 Privacy concerns about 802c PAR Date: [ ] Authors: NameAffiliationPhone Juan Carlos ZunigaInterDigital.
OmniRAN SDN-based OmniRAN Use Cases Summary Date: Authors: NameAffiliationPhone Antonio de la OlivaUC3M+34
An SDN-based approach for OmniRAN Reference Point mapping Date: [ ] Authors: NameAffiliationPhone Antonio de la
Privecsg Privacy Recommendation PAR Proposal Date: [ ] Authors: NameAffiliationPhone Juan Carlos ZúñigaInterDigital
MAC Address Randomization Tests Date: [ ] Authors: NameAffiliationPhone Fabio Carlos Jesús
Omniran CF00 1 OmniRAN R3 Considerations Date: Authors: NameAffiliationPhone Max RiegelNSN
Omniran CF00 1 P802.1CF NRM Mapping to real networks Date: Authors: NameAffiliationPhone Max RiegelNokia Networks
Omniran CF CF Network Reference Model Introduction Date: Authors: NameAffiliationPhone Max RiegelNokia Networks+49.
WiFi Privacy network experiment at IEEE 802 Berlin Plenary and IETF92 Date: [ ] Authors: NameAffiliationPhone Carlos Jesús
Omniran Thoughts about the tenets in IEEE 802.1CF Date: Authors: NameAffiliationPhone Max RiegelNSN
Privecsg Tracking of Link Layer Identifiers Date: [ ] Authors: NameAffiliationPhone Juan Carlos ZúñigaInterDigital
WiFi Privacy network experiment at IETF91 Date: [ ] Authors: NameAffiliationPhone Carlos Jesús Fabio
Omniran IEEE 802 Scope of OmniRAN Date: Authors: NameAffiliationPhone Max RiegelNSN
Omniran CF00 1 VLANs in relation to P802.1CF NRM Date: Authors: NameAffiliationPhone Max RiegelNokia Networks
Privecsg Bluetooth LE/Smart/v4 Privacy Date: [ ] Authors: NameAffiliationPhone Piers O’HanlonOxford Internet
1 privecsg Privacy EC SG Update to NGP SG Date: [ ] Authors: NameAffiliationPhone Juan Carlos ZúñigaInterDigital
Omniran CF00 1 CF ToC Refinements Date: Authors: NameAffiliationPhone Max RiegelNSN
Omniran CF00 1 Content and outline considerations for Annex: Applicability to non-IEEE 802 PHY layer technologies Date: Authors:
Privecsg Privacy Recommendation PAR Proposal Date: [ ] Authors: NameAffiliationPhone Juan Carlos ZúñigaInterDigital
Omniran CF00 1 Key Concepts of Authentication and Trust Establishment Date: Authors: NameAffiliationPhone Max RiegelNokia Networks+49.
Omniran CF00 1 Key Concepts of Network Selection and Detection Date: Authors: NameAffiliationPhone Max RiegelNokia Networks+49.
Privecsg Overview of Privacy in Date: Authors: NameAffiliationPhone Phillip BarberBroadband Mobile Tech
Outline of Proposed Revision PARs [IEEE Presentation Submission Template (Rev. 9.2)] Document Number: IEEE Date Submitted:
Omniran OmniRAN SaMOG Use Case Date: Authors: NameAffiliationPhone Max RiegelNSN
Omniran CF00 1 P802.1CF NRM Backhaul Considerations Date: Authors: NameAffiliationPhone Max RiegelNokia Networks
Doc.: IEEE /0667r0 Submission July 2005 Mike Moreton, STMicroelectronicsSlide 1 Multiple Networks Notice: This document has been prepared to assist.
and LMAP liaison Document Number: IEEE R0 Date Submitted: Source: Antonio BovoVoice:
OmniRAN IEEE 802 OmniRAN Architecture Proposal Date: Authors: NameAffiliationPhone Yonggang Bo.
3GPP SA2 SaMOG Status Document Number: Omniran Date Submitted: Source: Antonio de la Oliva UC3M *
Omniran IEEE 802 Scope of OmniRAN Date: Authors: NameAffiliationPhone Max RiegelNSN
Privecsg Privacy Recommendation PAR Proposal Date: [ ] Authors: NameAffiliationPhone Juan Carlos ZúñigaInterDigital
OmniRAN omniRAN Network Function Virtualization Date: Authors: NameAffiliationPhone Yonggang FangZTETX Zhendong.
Omniran Backhaul representation in OmniRAN SDN model Date: Authors: NameAffiliationPhone Max RiegelNSN
Network reference model for access network virtualization
WLAN as a Component (WaaC)
An SDN-based approach for OmniRAN
SDN Functional Decomposition
R0KH-R1KH protocol requirements
[place document title here]
IEEE 802 Scope of OmniRAN Abstract
Privacy Recommendation PAR Proposal
Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [MAC address assignment in IEEE
An SDN-based approach for OmniRAN Reference Point mapping
[place document title here]
OmniRAN SDN Use Case ToC
SDN-based OmniRAN Use Cases Summary
OmniRAN SDN Use Case ToC
EAP Method Requirements for Emergency Services
Presentation transcript:

WiFi Privacy network experiment at IETF91 Date: [ ] Authors: NameAffiliationPhone Carlos Jesús Fabio Antonio de la Juan Carlos Notice: This document does not represent the agreed view of the IEEE 802 EC Privacy Recommendation SG. It represents only the views of the participants listed in the ‘Authors:’ field above. It is offered as a basis for discussion. It is not binding on the contributor, who reserve the right to add, amend or withdraw material contained herein. Copyright policy: The contributor is familiar with the IEEE-SA Copyright Policy. Patent policy: The contributor is familiar with the IEEE-SA Patent Policy and Procedures: and. Abstract The present document reports on the trial performed at IETF91 and presents some results

2  Carry out a Wi-Fi MAC randomization trial/experiment at IETF91  Evaluating support of different OSes (Windows, Mac OS X and Linux)  Analyzing the impact of L2 address randomization on the user experience and the network infrastructure Specially in case of L2 address collision  Learn from this initial experience so we can gather further information in subsequent trials

3  A specific SSID ( ietf-PrivRandMAC ) was deployed on the wireless IETF Internet infrastructure  Deployed on all IETF physical APs, as an additional virtual AP  WPA PSK security, to avoid non participants to accidentally connect to our trial WLAN  Connected via a different VLAN to the DHCP server and Internet gateway Provides certain isolation to the rest of the infrastructure Isolated pool of IPv4 addresses

4  Participants were asked to notify their participation to a mailing list (ietf91-mac-  WLAN address randomization scripts developed and provided for 3 different OSes:  Microsoft Windows (tested on Windows 7)  Apple Mac OS X (tested on Version 10.10, alias Yosemite)  GNU Linux (tested on Debian testing/unstable, Ubuntu 13.10, and Fedora 20)  Use of DHCP client identifier for debugging

5  Participation increased significantly throughout the week  Around 3x at the end of the week (Mon-Thu)  OS distribution

6  685 Local MACs seen during the week  631 Local MACs were seen on the trial’s WLAN network  125 Local MACs were also seen on regular IETF WLAN networks  Based on the number of non-Local MAC seen on the trial’s WLAN and other metrics (e.g., # different IP addresses allocated and DHCP hostnames provided) we estimate that between 50 and 100 people participated in the trial  Method for better keeping track the number of participants should be provided in the future (e.g., use of IEEE 802.1X access setup)

7  542 IP addresses were assigned to Local MAC addresses  530 IP addresses assigned to a single Local MAC address E.g., because no DHCP client ID was used by the client  12 IP addresses assigned to multiple Local MAC addresses

8  Hard to estimate based on available logs  Most of the Local MACs (575) never tried to renew the DHCP lease  Only 56 Local MACs tried to renew the lease/obtain a new IP  This might have been caused by a change of AP/WLAN network, or a suspend/wake-up, etc Impact of the OS and user behavior  Max between first and last DHCP exchanges: 41 hours 51 min 41 sec  Average: 4 min 46 sec

9  Prepare a “wish list” for network administrators of future trial experiments  Logged information: we are working on potential additional logs that would help us getting more precise information  Access setup: use IEEE 802.1X to easily track the participation  Increased frequency poll of logs at the routers (netdisco)  Decrease DHCP lease time Pros: better estimation of the lifetime of a Local MAC address Cons: harder to evaluate the number of participants (though this could be improved with a different access setup) Does a 1h lease time provide a granularity good enough?  Prepare address randomization tools for more platforms/OSes, including mobile ones (e.g. Android)  Make a more detailed study of collision effects under different scenarios