Selected Research Projects on Mobile Internet

1. Selected Research Projects on Mobile Internet Klaas Wierenga <kwiereng@cisco.com> Mobile Internet Summit San Jose, 15 July 2008

2. Agenda • Intro • Examples: • Clean slate: POMI 2020 • Access: China Mobile • Routing: Lancaster University • Middleware: Geant2 Roaming and Authorisation • Mobile Applications: Waterloo University • Conclusions and next steps • References to other groups/projects

3. What is Mobile Internet • Mobility is a vision of providing access to whatever service, wherever, and whenever (CE mobility brief) • device portability • service portability • session persistence across devices and networks • Service driven, network enabled • It is about the user experience! • Mobile Internet =/= Wireless Internet

4. Cuts through the whole protocol stack • Access, routing, middleware, applications, politics • A lot of research in different cross-sections of the problem space as well as clean slate approaches • Now some examples • But there is much, much more…

5. Clean slate • The current Internet has deficiencies that are too structural to be solved in a manner that would allow for a truly Mobile Internet • How would we design the global communications infrastructure if we were to start with a clean slate? • What should the Internet look like in 15 years? • Tomorrow: POMI2020, Stanford

6. Access layer • Radio technology • Software defined radio • Spectrum policy • Sensors • Mesh Networks • Location

7. Example access layer: China Mobile • Who: China Mobile • What: WiiSE - (Wireless IP/Internet Service Environment) • Contact: Xiaodong Duan <duanxiaodong@chinamobile.com>, Monique Morrow <mmorrow@cisco.com>

8. Company Vision to 2015 ”WiiSE-- Wireless IP/Internet Service Environment, CMCC want to be push and integrate the whole industry ECO-Systems including network and service, be more stronger in domination and voice, like Vodafone and NTT DoCoMo”

9. Company Overview • China Mobile Limited provides mobile Telecommunications and related services in 31 provinces, autonomous regions and directly administered municipalities in Mainland China and Hong Kong through 32 subsidiaries. • Subscriber base is approximately ~376 million (Jan 31th 2008), with an ~ market share of 68% • China Mobile generated US$ 41,053.3 million Revenues (21.5% YoY Growth) and US$ 9,177 million Net Income (23.3 YoY Growth) in 2006. • Voice: GSM global roaming services cover 228 countries and regions with 285 SP. • Data: GPRS roaming services covers 152 countries and regions with 126 SP Source: from cmcc company website

10. SS7 PSTN V V AAA DNS Current Network Enterprise IPBB WiMX GMSC VLR/HLR TD-SCDMA Node B MGW RNC WiMX MGX TD-SCDMA Node B IPRAN Access Metro MGX N*E1/FE GE/25G/10G Internet Billing E3/STM-1 SGSN New CMnet GGSN RNC GSM/BTS DCN RNC MMS WLAN N*E1/FE BOSS TD-SCDMA Node B

11. Main considerations for the Mobile Internet

12. WiiSE Conceptual Design

13. Transition

14. IP mobility Management is key

15. Summary • Now 3GPP • Later all-IP • Need for standardisation in a number of areas: • GIAP initiative • GMP • RAI related areas:P2P SIP • new BGP/IP IP VPN:IPVPN Solution • MESH/AdHoc • SIGTRAN: M3UA Ext • TICTOC Requirements in RAN • IPsec secured GRE tunnel • Service Option update for DHCPv6 • Cisco recognized as the partner for innovation

16. Routing for the Mobile Internet • Is there light at the end of the 3GPP/MIP tunnel? • Underlying Problem • Overloading of the IP address • identity, location, even security context (IAB raw report rfc4984) • Approaches: LISP, Shim6, HIP, 8+8/GSE

17. Example routing: Lancaster University, UK • Who: Computing Department, Lancaster University, UK • What: Mobile and ubiquitous computing, Routing for the Mobile Internet (with Cisco) • Info: http://www.comp.lancs.ac.uk/research/mobileubiqcomp.html • Contact: Chris Edwards <ce@comp.lancs.ac.uk> or Brian McLaughlin brmclaug@cisco.com

18. Location Identifier Splitting • Idea behind Locator/Identifier - End-point Identifier : used to identify host - Routing Locators : used for packets routing across transit domain - One identity can be associated with one or more locations - Possible applications to mobility and multihoming - Necessitates some mapping function or agent, somewhere

19. GSE and EIP Alternative • GSE (Global, Site, Endpoint) or 8+8 addressing - 64-bit Internet Locator • Global Locator + Provider Locator • 64-bit Internet Identifier •   |            64 bits           |            64 bits             |    +------------------------------+--------------------------------+    |   Internet Locator     |   Internet Identifier    |    +------------------------------+--------------------------------+ •   | 32 bits | 28 bits | 4 bits   | 64 bits       |    +------------------------------+--------------------------------+    | Global | Local |Identifier|  Identifier    |    | Locator | Locator |  Type | Value    |    +------------------------------+--------------------------------+ • EIP - Endpoint Identity Protocol - New stack element - Allows changing of identity and locator bindings

20. Additional Components • Some Mapping Agent (Dynamic DNS) • holds bindings between identifier and location • Mobility Forwarding Function (MFF) • Discover and then re-write local locators when not known • Radio Routers • Handle network association and authentication for mobile devices • Paging Agents • Used to find location when devices have been sleeping

21. GSE and EIP Operation • The Mobile Host is responsible for updating a Mapping Function (DNS) entry whenever it is authenticated by a new provider’s network - implies authentication of DNS entry updates • A Correspondent Host retrieves the AAAA record and uses the Global Locator (top 32 bits) to construct the destination address. • But not local portion (all zeros) • MFF responsible for resolving local portion • Prefix discovery, configure new address, DAD, update DNS

22. Flow

23. Flow Auth Exchange

24. Flow Auth Exchange

25. Flow Prefix Discovery

26. Flow DAD

27. Flow Accounting start

28. Flow DNS Update

29. Flow Query/Response

30. Flow Global Locator in dest_addr

31. Flow Downlink Packet

32. Flow Query/ Response

33. Flow Local Locator Re-write

34. Flow Downlink Packet

35. Flow Uplink Packet

36. Flow EIP Updates Local Locator

37. Flow Downlink Packet

38. Project • Objectives • Implement and analyse GSE + EIP for mobility • Implementation • Linux based • hosts, radio routers, paging agents, MFF • Analysis • What are the (if any) improvements over Mobile IP? • path lengths, packet loss, handover latencies • Can using the DNS for mapping scale? • How does this compare to other approaches • Based on analysis more fundamental approach • Which layer? • Transport Layer mobility support? • Multi-layer interactions?

39. Demo Lancaster University

40. What is Mobile Internet • Mobility is a vision of providing access to whatever service, wherever, and whenever (CE mobility brief) • device portability • service portability • session persistence across devices and networks • Service driven, network enabled • It is about the user experience! • Mobile Internet =/= Wireless Internet

41. Middleware Layer • Roaming • AAA • Security • Federations • Provisioning

42. Example roaming and AAA: Geant2 project EU • Who: Dante, TERENA, SURFnet, RedIRIS, DFN, Janet, most other European NRENs and some universities • What: Roaming and authorisation activity • Info: http://www.geant2.net/server/show/nav.758 • Contact: Diego Lopez <diego.lopez@rediris.es> or Klaas Wierenga <kwiereng@cisco.com>

43. Disclaimer

44. Activities • Building on work done in TERENA taskforces Mobility and EMC2 on eduroam and federated applications • Create a pan-European roaming infrastructure for network access for HigherEd (eduroam) • Create a pan-European authentication and authorisation infrastructure by connecting the existing federations in HigherEd (eduGAIN) • Create universal single sign on by integrating the former two (DAMe)

45. eduroam Supplicant Authenticator (AP or switch) RADIUS server University A RADIUS server University B User DB User DB Guest piet@university_b.nl SURFnet Commercial VLAN Employee VLAN Central RADIUS Proxy server Student VLAN • Trust based on RADIUS plus policy documents • Routing based on realm • 802.1X (spin-off: SecureW2) • Home chooses EAP-method • RADIUS infra considered unsafe • (VLAN assignment) signalling data Source: SURFnet

46. eduroam status New trial with Internet2 Isolated trials in Latin-America • US experiment with I2 (failed) • Canada member since June 2008

47. Spin-off: RadSec • Eduroam problems: • Dead peer discovery • Fragmentation • Managing shared secret/IP-address based trust • Static hierarchy • DIAMETER not available • RADIUS with: • TLS • TCP • draft-ietf-radext-radsec-00.txt, draft-dekok-radext-tcp-transport-00.txt • implementations in Radiator, FreeRADIUS (in progress), RadSecProxy and OpenWRT and Lancom AP’s

48. eduGAIN • Bridging existing federations in HigherEd • Existing federations based on: • Shibboleth 1.3 • A-select • PAPI • Sun Access manager • WS-federations • SAML 2.0 (Shibboleth and Liberty Alliance) • Lingua franca for interconnect: SAML

49. Federated SSO

50. Attr. johnd Pa$$wD Attr. Attr. 1 2 9 3 6 7 8 5 4 WebSSO in PracticeCurrent Inter-Federation Usage Source: RedIRIS