Short Bio : Dr. Pekka Nikander is an internationally recognised expert in the Internet architecture, with special attention to mobility, security, and privacy aspects. He has strong background in operating systems, communications protocols, all levels of programming from microcontrollers and system programming to graphical user interfaces, and computer and communications security. In early 1990s he spend a few years focusing on user interface aspects, creating a user centric perspective that has remained active since then. During the last half a dozen years he has become active in Internet standardisation, and served at the Internet Architecture Board (IAB) from March 2005 to February 2006. Most recently, his work has focused on the future of the Internet architecture, with special attention to economic, end- user centric, and privacy aspects.

Abstract: Networking, as a piece of technology, seems to be on the brink of its second fundamental revolution. The first revolution was the move from wires to packets; a phenomenon that started in late 1950's, gained speed in the 1980's and 1990's, and seems to be coming to its conclusion right now. The second revolution, moving from packets to information, is only starting. Like the first revolution, the second revolution will bring forth a number of new types security problems, many of which we will even notice only later on.

In this talk, we use the revolutions framework to discuss current and anticipated networking-related problems, both architectural and security related. Currently, the primary reasons behind the most pressing problems include loss of trust, surge of unwanted traffic, choking of the routing system, poor support for mobility and multi- homing, and lack of privacy and accountability. The attempts to alleviate these problems, including middle-boxes, moving connectivity to overlay networks, and virtualisation, are at best temporary. More fundamental chances are needed to bring forth long-lasting solutions. Hence, we conclude with a brief look at a few of the most interesting research directions going on at the time, illustrating some aspects of the envisioned information-centric networking paradigm.

Abstract: The Host Identity Protocol (HIP) is an experimental architecture and protocol, being developed at the IETF since 1999 and reaching its first stable version in 2007. It enhances the original Internet architecture by injecting a new thin layer between the IP layer and the transport protocols. This new layer introduces a new name space consisting of cryptographic identifiers, thereby implementing the so-called identifier / locator split. In the new architecture, the new identifiers are used for naming application level end-points, thereby taking the prior identification role of IP addresses in applications, sockets, TCP connections, and UDP send and receive system calls. IPv4 and IPv6 addresses are still used, but only as names for topological locations in the network. At the same time, due to the backwards compatibility mode, no changes are needed in applications. The architectural enhancement implemented by HIP has profound consequences. A number of the previously hard problems become suddenly much easier. Mobility, multi-homing, and baseline end-to-end security integrate neatly into the architecture. The use of cryptographic identifiers allows enhanced accountability, thereby providing a base for easier build up of trust. With some privacy enhancements, HIP allows good location anonymity, assuring strong identity only towards relevant trusted parties. Finally, the HIP protocol has been carefully designed to take middle boxes into account, providing for overlay networks and thereby helping to reduce the currently prevalent problems with bad traffic and routing scalability. This tutorial provides an in-depth look at HIP, discussing its architecture, design, benefits, and potential drawbacks. In the first part of the tutorial, the architecture and design of HIP is discussed in an interactive but lecture-like manner. In the second part of the tutorial the protocol will be demonstrated in practise. The audience is assumed to have good knowledge about the current Internet architecture and the structure of the TCP/IP stack. However, no knowledge of HIP or the related problems are assumed.