Peer-to-Peer Wireless Network Confederation (P2PWNC) Mobile Multimedia Laboratory Athens University of Economics and Business Athens MMAPPS Meeting, September 8 - 12, 2003
Download ReportTranscript Peer-to-Peer Wireless Network Confederation (P2PWNC) Mobile Multimedia Laboratory Athens University of Economics and Business Athens MMAPPS Meeting, September 8 - 12, 2003
Peer-to-Peer Wireless Network Confederation (P2PWNC) Mobile Multimedia Laboratory Athens University of Economics and Business Athens MMAPPS Meeting, September 8 - 12, 2003 Overview Introduction Usage Internals Demo Issues 10/09/2003 MMAPPS P2PWNC 2 of 40 Introduction 10/09/2003 MMAPPS P2PWNC 3 of 40 Background P2PWNC: A P2P approach to WISP roaming Easy for networks to participate: less administrative overhead Substantial autonomy for the roaming partners Provisions for identity and location privacy 10/09/2003 MMAPPS P2PWNC 4 of 40 Terminology Consuming bt.com Peer Providing Peer aueb.gr [email protected] Peer Names Domain Names Registered Users: Unique P2PWNC ID ( username@domain_name ) Home Domain Consuming Peer Visited Domain Providing Peer User Devices: Unique Hardware (MAC) Address 10/09/2003 MMAPPS P2PWNC 5 of 40 Service Fundamentals Ubiquitous wireless Internet access Lightweight devices ( WLAN interface, TCP/IP and a web-browser ) Device mobility Rules and accounting QoS 10/09/2003 MMAPPS P2PWNC 6 of 40 Usage 10/09/2003 MMAPPS P2PWNC 7 of 40 Usage Scenario 1. User visits a peer domain 2. Activates device 3. Uses P2PWNC ID to login 4. Accesses the Internet 5. Leaves or turns off device 10/09/2003 MMAPPS P2PWNC 8 of 40 Before Authentication 10/09/2003 MMAPPS P2PWNC 9 of 40 Before Authentication 10/09/2003 MMAPPS P2PWNC 10 of 40 Login 10/09/2003 MMAPPS P2PWNC 11 of 40 Successful Visitor Login 10/09/2003 MMAPPS P2PWNC 12 of 40 Internals 10/09/2003 MMAPPS P2PWNC 13 of 40 Session Types Two session types: local and roaming Only roaming sessions require a P2P negotiation Rules have no meaning for users when at home Peers keep track of: 1. visiting users 2. their own roaming users 3. their own registered users when at home 10/09/2003 MMAPPS P2PWNC 14 of 40 Layered Peer Architecture P2PWNC Application WLAN listener WLAN object calls WLAN Service Network Services Visitor Negotiation Firewall Wireless tools DHCP Routing / NAT Rate control Authentication Packet sniffer 10/09/2003 MMAPPS P2PWNC 15 of 40 Initial Events P2PWNC Application 3. New device event 6. New login event WLAN Service 2. MAC address is new 5. Authentication succeeded Network Services 1. IP address leased 4. CGI receives user credentials DHCP Authentication 10/09/2003 MMAPPS P2PWNC 16 of 40 Local Events GUI 10/09/2003 MMAPPS P2PWNC 17 of 40 Local Sessions GUI 10/09/2003 MMAPPS P2PWNC 18 of 40 Local Sessions getUsers() getTrafficDetails() getDuration() getRate() WLAN Service Local Sessions User User User 10/09/2003 Traffic Traffic Traffic Details Roaming Sessions Duration Duration Duration MMAPPS P2PWNC Rate Rate Rate 19 of 40 Roaming Sessions GUI 10/09/2003 MMAPPS P2PWNC 20 of 40 Roaming Sessions getUser() getTrafficDetails() getDuration() getRate() WLAN Service Local Sessions WLAN Service Consumer Consumer Stub Consumer Stub Consumer Consumer Consumer Stub Stub Stub Visited domain 10/09/2003 Roaming Sessions Home domain MMAPPS P2PWNC 21 of 40 Visitor Negotiation 1. Visitor credentials check WLAN 6. Balance OK: Proceed Visitor Negotiation Visitor Session 2. Negotiate Visitor Negotiation 5. Start MMAPPS Negotiation WLAN Negotiation Listener 3. Request service 4a. MMAPPS negotiation MMAPPS Negotiation 4b. Balance check Home domain - Consumer Visited domain - Provider 10/09/2003 MMAPPS P2PWNC 22 of 40 Visitor Logout Timeout-based logout Provider and consumer declare session terminated Balances updated Provider and consumer GUIs updated 10/09/2003 MMAPPS P2PWNC 23 of 40 Rules and Policies GUI 10/09/2003 MMAPPS P2PWNC 24 of 40 Breaking the Rules Provider can configure rule with one parameter ( benevolence ) If rule is broken, consuming peer receives a negotiation abort Even then, provider can provide some connection time “for free” 10/09/2003 MMAPPS P2PWNC 25 of 40 QoS GUI 10/09/2003 MMAPPS P2PWNC 26 of 40 QoS Scheme Split link bandwidth into two parts: home and visitors Allocate guaranteed bandwidth for specific locally registered users Allocate guaranteed percentage of visitor bandwidth for specific domains Current scheme is inflexible 10/09/2003 MMAPPS P2PWNC 27 of 40 Demo 10/09/2003 MMAPPS P2PWNC 28 of 40 Demo Setup 195.251.234.26 aueb.gr bt.com 192.168.0.1 192.168.0.1 Channel 01 SSID aueb.gr Mode Ad hoc 10/09/2003 195.251.234.27 switch Channel 11 SSID bt.com Mode Ad hoc MMAPPS P2PWNC 29 of 40 Network Settings GUI 10/09/2003 MMAPPS P2PWNC 30 of 40 User Accounts GUI 10/09/2003 MMAPPS P2PWNC 31 of 40 Issues 10/09/2003 MMAPPS P2PWNC 32 of 40 Accounting Events Volume-based events Time-based events QoS-based events A rule, similar to the current one, taking these under consideration 10/09/2003 MMAPPS P2PWNC 33 of 40 Lightweight Clients Consuming peer is not aware of the actual service We assumed no special software on the client device May be required, however, to verify received service authoritatively Who else can independently observe the provider? 10/09/2003 MMAPPS P2PWNC 34 of 40 Offline Peers A user’s home domain may be offline Password-based authentication cannot work No consumer peer available to negotiate on the user’s behalf Could the user device act as a peer? Could another peer act as the user’s home? 10/09/2003 MMAPPS P2PWNC 35 of 40 DNS Substitute Need to support unique, logical, location-independent peer names not just ‘aueb.gr’ or ‘bt.com’ but also ‘Elias_Athens_ADSL_Peer’ Resolve this to the peer’s current IP address ( which may change ) Enhanced MMAPPS Search? Based on a DHT? 10/09/2003 MMAPPS P2PWNC 36 of 40 More General Issues Distributed accounting Secure, fault-tolerant Efficient rules That take peer heterogeneity into account? 10/09/2003 MMAPPS P2PWNC 37 of 40 Privacy Identity privacy ( anonymity ) Hide real P2PWNC ID from visited peer Location privacy ( untraceability ) Hide current location from home peer 10/09/2003 MMAPPS P2PWNC 38 of 40 Privacy Architecture Peer ‘A’ (mix 1) Alias_X@B { MIX, C, { STOP, X }C }B Alias_X@A { MIX, B, { MIX, C, { STOP, X }C }B }A Peer ‘B’ (mix 2) Alias_X@C { STOP, X }C Peer ‘P’ Peer ‘C’ “My P2PWNC ID is Alias_X@A” (Credentials include real ID and a mix chain -encrypted using nested public-key encryptions) X@C 10/09/2003 MMAPPS P2PWNC 39 of 40 Thank You 10/09/2003 MMAPPS P2PWNC 40 of 40