19 May 2003 © The JNT Association Terena Technical Advisory Council Terena Mobility Task Force Mobility Issues James Sankar

19 May 2003 © The JNT Association Background Mobility workshops were arranged in Amsterdam in March, June & October 2002 to define and agree a charter. On January , the charter was approved, two chairman were appointed and the task force started. Key objectives –Evaluate AAA techniques in mobile environments (802.1X, VPN, Web). –Create an Inter-NREN WLAN roaming architecture and testbed. –Evaluate mobile equipment and technology. –Evaluate next generation mobile technology for handover and roaming (mobile IP v4 and v6). Participation: SURFnet, UKERNA, DFN, SWITCH, UNINETT, FUNET

19 May 2003 © The JNT Association Requirements definition 1) With minimal administrative overhead (per roaming user) Very little admin work to enable roaming per user Minimize the complexity of additional systems required No n2 work required when scaling system No regulatory entanglement 2) With g ood usability Available to most current WLAN (and wired) users. No additional software required to enable roaming. Enable all (work, guest, home networks, IPv4 and IPv6). 3) Maintaining required security for all partners Allow use only for approved NREN users. Provide accountability but also confidentiality of traffic. Guard against data manipulation and session hijacking. Allow real security (e2e) on top. Don’t aggravate security issues of visited networks. Enable NREN users to use Internet (WLAN and wired) everywhere in Europe

19 May 2003 © The JNT Association Inventory 1 - VPN

19 May 2003 © The JNT Association Inventory 2 – Cross-domain 802.1X with VLAN assignment AuthZ at home institution, 802.1X, TTLS (SecureW2), (proxy) RADIUS. Public hotspots within Freeband project RADIUS server Institution B RADIUS server Institution A Internet Central RADIUS Proxy server Authenticator (AP or switch) User DB Supplicant Guest Student VLAN Guest VLAN Employee VLAN data signalling

19 May 2003 © The JNT Association Inventory 3 – Web based Internet Public Access Network Public Access Controller AAA Server WWW-browser

19 May 2003 © The JNT Association Next steps 1.Finalise and publicise inventories for external review and comment. 2.Agree on an architecture to i) accommodate and support the requirements definition and ii) where possible ensure the interoperability of the 3 solutions 3.Monitor emerging wireless standards (802.11a & g etc) and if ratified, review the proposed architecture to determine whether it can support these new standards. 4.Continue to develop a knowledge base wireless device performance and interoperability issues.

19 May 2003 © The JNT Association Contact Details: James Sankar Telephone: Website: Thank you & Questions