1. doc.: IEEE 802.11-09/1000r4 Submission Jan 2010 Hiroshi Mano Root, Inc.Slide 1 IEEE802.11 for High Speed Mobility Notice: This document has been prepared to assist IEEE 802.11. 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 grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE 802.11. Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures, including the statement "IEEE standards may include the known use of patent(s), including patent applications, provided the IEEE receives assurance from the patent holder or applicant with respect to patents essential for compliance with both mandatory and optional portions of the standard." Early disclosure to the Working Group of patent information that might be relevant to the standard is essential to reduce the possibility for delays in the development process and increase the likelihood that the draft publication will be approved for publication. Please notify the Chair as early as possible, in written or electronic form, if patented technology (or technology under patent application) might be incorporated into a draft standard being developed within the IEEE 802.11 Working Group. If you have questions, contact the IEEE Patent Committee Administrator at.http:// ieee802.org/guides/bylaws/sb-bylaws.pdfstuart.kerry@philips.compatcom@ieee.org Date: 2010-01-19 Authors: NameCompanyAddressPhoneemail Hiroshi MANOROOT Inc.8F TOC2 Bldg. 7-21-11 Nishi- Gotanda, Shinagawa-ku, Tokyo 141-0031 JAPAN +81-3-5719-7630hmano@root-hq.com Hitoshi MORIOKAROOT Inc.#33 Ito Bldg. 2-14-38 Tenjin, Chuo-ku, Fukuoka 810-0001 JAPAN +81-92-771-7630hmorioka@root-hq.com

2. doc.: IEEE 802.11-09/1000r4 Submission Jan 2010 Hiroshi Mano Root, Inc.Slide 2 Abstract We told about IEEE802.11 enhancement for high speed mobility support in the previous session in Atlanta. –Mobile vs. Nomadic –Limitation of Market –Connectivity Lost –How to solve the issue –Example implementation Today, we talk about our experimental protocol and another profit –Scalability for simultaneous access from large number of mobile devices. –Straw Polls for tutorial session

3. doc.: IEEE 802.11-09/1000r4 Submission Jan 2010 Hiroshi Mano Root, Inc.Slide 3 Mobile vs. Nomadic Let’s quote definitions from RECOMMENDATION ITU-R F.1399-1 “Vocabulary of terms for wireless access” Mobile wireless access (MWA) –Wireless access application in which the location of the end-user termination is mobile. Nomadic wireless access (NWA) –Wireless access application in which the location of the end-user termination may be in different places but it must be stationary while in use.

4. doc.: IEEE 802.11-09/1000r4 Submission Jan 2010 Hiroshi Mano Root, Inc.Slide 4 Limitation of market growth in the existing 802.11 Bandwidth? –No! We are getting wide bandwidth day by day 11b, g, a, n, ac, ad Securities? –No! 802.11 incorporates new security system too. WEP, 802.11i… Propagation range? –No! it is true, but it is not limit of technologies. –It’s depends on regulatory. –And it’s good for avoiding congestion. Service devices? –No! now we have several type of devices such as cell-phone, game and digital camera. Service model? –Yes! we are still in nomadic services.

5. doc.: IEEE 802.11-09/1000r4 Submission Jan 2010 Hiroshi Mano Root, Inc.Slide 5 Beyond “Nomadic” If we got actual mobility on 802.11 We will get Wi-Fi IP mobile phone (not only in-house phone) Wi-Fi on a car (high context navigation) Wi-Fi on a train (passenger services) Wi-Fi real-time audio (anywhere anytime) Wi-Fi real-time video (anywhere anytime) skype, etc.,

6. doc.: IEEE 802.11-09/1000r4 Submission Jan 2010 Hiroshi Mano Root, Inc.Slide 6 Existing Wi-Fi Service Area Huge number of APs were deployed by different owners. (autonomously deployment) –APs owned by one owner can be operated by 802.11r technology to provide fast roaming inside one ESS. An STA is always receiving at least one or more signals from someone's APs continuously. However, we have to spend a couple of seconds to connect to another ESS every time. –In other words, we lost connectivity at every border of ESS. This fact is not suitable for mobile communication.

7. doc.: IEEE 802.11-09/1000r4 Submission Jan 2010 Nomadic Vs Mobile ESS 1ESS 2 ESS 3 ESS 1ESS 2 ESS 3 Slide 7Hiroshi Mano Root, Inc.

8. doc.: IEEE 802.11-09/1000r4 Submission Jan 2010 Hiroshi Mano Root, Inc.Slide 8 Reasons of Connectivity Loss Waste much time to … 1.Discover a new AP. Latency can be reduced by 11k or background scan. 2.Make association with a new AP. (includes authentication/key exchange…) 11i authentication is not so fast. –It needs many packet exchanges. 3.Upper layer setup. (Out of Scope) 4.Upper layer handover. (Out of Scope) Fast authentication and key management (AKM) can reduce connectivity loss.

9. doc.: IEEE 802.11-09/1000r4 Submission Jan 2010 Time for handover IEEE802.16e -- 35-50ms IEEE802.16m -- 30ms? IEEE802.11i +.1X -- >100ms while G.711 sends a packet every 20ms. Another VoIP implementation sends every 50ms. Hiroshi Mano Root, Inc.Slide 9

10. doc.: IEEE 802.11-09/1000r4 Submission Jan 2010 Hiroshi Mano Root, Inc.Slide 10 Protocol Sequence of IEEE802.11i (EAP-TLS) STA AP RADIUS Server Beacon Probe Request Probe Response Authentication Request Authentication Reply Association Request Association Accept EAPOL-Start EAP-Request/Identity EAP-Response/Identity EAP-Request/TLS-Start RADIUS-Access-Request/Identity RADIUS-Access-Challenge/TLS-Start EAP-Response/TLS-client Hello EAP-Success RADIUS-Access-Request/Pass Through RADIUS-Access-Challenge/ Server Certificate EAP-Key EAP-Request/Pass Through EAP-Response/Client Certificate RADIUS-Access-Request/Pass Through RADIUS-Access-Challenge/Encryption Type EAP-Request/Pass Through EAP-Response RADIUS-Access-Request RADIUS-Access-Accept Roundtrip: 2ms to 5ms Roundtrip: 1ms to 20ms

11. doc.: IEEE 802.11-09/1000r4 Submission Jan 2010 Hiroshi Mano Root, Inc.Slide 11 An Example of Faster AKM Utilize Pre-RSNA Security Framework –Authentication and PTK exchange can be done in pre-RSNA security framework. –After PTK setup, GTK can be securely delivered. STA AP Authentication Server Beacon (Probe Request) (Probe Response) Authentication Request Authentication Reply Access Request Access Response (Association Request) (Association Accept) Roundtrip: 2ms to 5msRoundtrip: 1ms to 20ms

12. doc.: IEEE 802.11-09/1000r4 Submission Jan 2010 Time for handover (review) IEEE802.16e -- 35-50ms IEEE802.16m -- 30ms? IEEE802.11i +.1X -- >100ms New Fast AKM -- 25-30ms (target) Hiroshi Mano Root, Inc.Slide 12

13. doc.: IEEE 802.11-09/1000r4 Submission Jan 2010 Hiroshi Mano Root, Inc.Slide 13 An Example: Pre-shared Secret Key Access Point (AP) Authentication Server (AS) Station (non-AP STA) No pre-shared information between mobile STA and AP –AP and AS function can be equipped in a box for a small system. Share an identifier and a secret key (MN-key) Each mobile STA has a different key Identified by NAI (account name) Share a secret key (AP-key) Each AP has a different key Identified by IP/MAC address

14. doc.: IEEE 802.11-09/1000r4 Submission Jan 2010 Hiroshi Mano Root, Inc.Slide 14 An Example: PTK delivery Access Point (AP) Authentication Server (AS) Station (non-AP STA) AP-key shared STA-key shared PTK is delivered via AS between mobile STA and AP PTK delivery without STA-AP mutual secrets

15. doc.: IEEE 802.11-09/1000r4 Submission Jan 2010 An Example: Authentication Procedure Access Point (AP) Authentication Server (AS) Station (Non-AP STA) Authentication Request Frame Authentication Data (16byte) ICV (16byte) MD5 HMAC-MD5 (STA-key) Authentication Request Frame Authentication Data (16byte) Access Request Message ICV (16byte) Extract Authenticator (16byte) MD5 HMAC-MD5 (AP-key) Access Request Message Authenticator (16byte) Authentication Data (16byte) ICV (16byte) Authenticator (16byte) ICV (16byte) Extract HMAC-MD5 (AP-key) HMAC-MD5 (STA-key) Compare Beacon/ Probe resp Beacon/ Probe resp Nonce NAI… Check Timestamp Transmit Broadcast Slide 15Hiroshi Mano Root, Inc.

16. doc.: IEEE 802.11-09/1000r4 Submission Jan 2010 An Example: Authentication Procedure (Cont.) Access Point (AP) Authentication Server (AS) Station (Non-AP STA) Authentication Success Frame Authentication Data (16byte) ICV (16byte) MD5 HMAC-MD5 Authenticator (16byte) Access Request Message Nonce (16byte) PTK (16byte) ICV (16byte) Extract HMAC-MD5 (STA-key) Extract HMAC-MD5 (AP-key) Hashed ICV (16byte) Session Key DD (16byte) XOR Access Approval Message Authenticator (16byte) HMAC-MD5 (AP-key) Access Approval Message Authenticator (16byte) Compare Extract HMAC-MD5 (AP-key) ICV (16byte) Hashed ICV (16byte) Extract HMAC-MD5 (AP-key) Session Key DD (16byte) PTK (16byte) Extract XOR Authentication Success Frame Authentication Data (16byte) ICV (16byte) MD5 HMAC-MD5 ICV (16byte) Nonce (16byte) PTK (16byte) HMAC-MD5 (STA-key) Compare Extract Network Info (IP address…) Transmit Slide 16Hiroshi Mano Root, Inc.

17. doc.: IEEE 802.11-09/1000r4 Submission Jan 2010 Slide 17 Protocol Sequence between AP and STA on IEEE802.11i ( PEAP/EAP-MSCHAPv2) STA AP EAPOL-Start EAP-Success PEAP EAP-MSCHAPv2 (4 round trip) Establishing TLS tunnel for PEAP (3 round trip) EAP-Identity (1 round trip) Association (1 round trip) Authentication (1 round trip) EAPOL-Key (2 round trip) Total: 14 round trip Probe (1 round trip) Slide 17Hiroshi Mano Root, Inc.

18. doc.: IEEE 802.11-09/1000r4 Submission Jan 2010 Airtime consumption for every single authentication process We observed an STA connecting to an AP with PEAP/MS-CHAPv2 by IEEE802.11g. All management frames were transmitted in 1Mbps mode. Required airtime for one unicast frame is defined as described below. Frame Occupied Time DIFSCW ACK aSlotTime:20us aSIFSTime:10us aPreambleLength:144us aPLCPHeaderLength:48bits aCWmin:31 aCWmax:1023 DIFS:50us CW:620us ACKRate:1Mbps ACKLength:14Bytes TXTIME SIFS TXTIME PEAP/EAP-MSCHAPv2 needs 14 round trip frame exchanges. From our observation result, total frame length without PLCP header is 4390 byte. An STA needs 48.4ms airtime connecting to an AP.

19. doc.: IEEE 802.11-09/1000r4 Submission Jan 2010 Simulation Assumption –Place: Train Station –Time: Rush Hour –Walking Speed: 4.8km/h=80m/min –AP cover area: 80m*80m square –Occupied Space by 1 Person: 2m*2m square –All persons have a cellular phone which supports WLAN. –All persons are walking same direction. 1,600 STAs are passing through the AP’s cover area in 1 minutes. this means 1,600 authentication process should be proceeded during every 1 minutes. Every authentication process needs 48.4ms airtime to connect to the AP. Only 1,238 authentication process can be proceeded. There is no time space to data communication. Furthermore, AP transmits beacons, STA needs DHCP… AKM should be shortened. Slide 19Hiroshi Mano Root, Inc.

20. doc.: IEEE 802.11-09/1000r4 Submission Jan 2010 Hiroshi Mano Root, Inc.Slide 20 Conclusion Limitation of IEEE802.11 is “NOMADIC” use only. Mobile communication will expand IEEE802.11 market. Long AKM time is not suitable for mobile use. We have to reduce AKM time toward mobile. We show an example of new fast AKM method. AKM should be shortened to support simultaneous access from large number of portable devices. Further study in SG/WG is required for better AKM method.

21. doc.: IEEE 802.11-09/1000r4 Submission Jan 2010 Hiroshi Mano Root, Inc.Slide 21 Questions & Comments

22. doc.: IEEE 802.11-09/1000r4 Submission Jan 2010 Hiroshi Mano Root, Inc.Slide 22 Straw Poll “Does WNG think that we need tutorial session exploring the need for support for mobile communication ?” Yes: No: 0 Don’t Care: