Applying a cryptographic namespace to applications

Authors:
Miika Komu;Sasu Tarkoma;Jaakko Kangasharju;Andrei Gurtov
Affiliations:
Helsinki Institute for Information Technology, HUT, Finland;Helsinki University of Technology, HUT, Finland;Helsinki Institute for Information Technology, HUT, Finland;Helsinki Institute for Information Technology, HUT, Finland
Venue:
DIN '05 Proceedings of the 1st ACM workshop on Dynamic interconnection of networks
Year:
2005

Citing 5
Cited 4

Internet indirection infrastructure

Proceedings of the 2002 conference on Applications, technologies, architectures, and protocols for computer communications
Host Mobility Using an Internet Indirection Infrastructure

Host Mobility Using an Internet Indirection Infrastructure
Unmanaged Internet Protocol: taming the edge network management crisis

ACM SIGCOMM Computer Communication Review
A layered naming architecture for the internet

Proceedings of the 2004 conference on Applications, technologies, architectures, and protocols for computer communications
BLIND: a complete identity protection framework for end-points

SP'04 Proceedings of the 12th international conference on Security Protocols

Hi3: An efficient and secure networking architecture for mobile hosts

Computer Communications
Black boxes: making ends meet in data driven networking

Proceedings of the 3rd international workshop on Mobility in the evolving internet architecture
Leap-of-faith security is enough for IP mobility

CCNC'09 Proceedings of the 6th IEEE Conference on Consumer Communications and Networking Conference
Adoption barriers of network layer protocols: The case of host identity protocol

Computer Networks: The International Journal of Computer and Telecommunications Networking

Quantified Score

Hi-index	0.00

Visualization

Abstract

The Host Identity Protocol (HIP) is a promising solution for dynamic network interconnection. HIP introduces a namespace based on cryptographically generated Host Identifiers. In this paper, two different API variants for accessing the namespace are described, namely the legacy and the native APIs. Furthermore, we present our implementation experience on applying the APIs to a number of applications, including FTP, telnet, and personal mobility. Well-known problems of callbacks and referrals, i.e., passing the IP address within application messages, are considered for FTP in the context of HIP. We show that the callback problem is solvable using the legacy API. The APIs are important for easy transition to HIP-enabled networks. Our experimentation with well-known network applications indicate that porting applications to use the APIs is realistic.