This file was created by the TYPO3 extension bib --- Timezone: CEST Creation date: 2024-05-03 Creation time: 08-36-24 --- Number of references 5 inproceedings Varj1112:Secure 2011 12 5 Many efforts of the network research community focus on the introduction ofa new identifier to relieve the IP address from its dual role of end-hostidentifier and routable locator. This identifier-locator split introduces anew identifier between human readable domain names and routable IPaddresses. Mapping between identifiers and locators requires additionalname mapping mechanisms because their relation is not trivial. Despite itspopularity and efficiency, the DNS system is not a perfect choice forperforming this mapping because identifiers are not hierarchicallystructured and mappings are frequently updated by users. In this paper wediscuss the features needed to resolve flat identifiers to locators in asecure manner. In particular, we focus on the features and the performancethat identifier-locator split protocols require from a mapping system. Tothis end, we consider a mapping system for an identifier-locator splitbased mobility solution and evaluate its performance. IndexTerms—Identifier-locator split, Name resolution, Host Identity Protocol,Security, DNS, DHT, OpenDHT DHT; DNS; Host Identity Protocol; Security; Identifier-locator split; Nameresolution fileadmin/papers/2011/2011-varjonen-secure.pdf Online IEEE

Piscataway, NJ, USA

IEEE GLOBECOM 2011 - Next Generation Networking Symposium (GC'11 - NGN), Awarded the NGN Best Paper Award accepted en 978-1-4244-9268-8 1930-529X 1 SamuVarjonen TobiasHeer KennethRimey AndreiGurtov techreport rfc6253 2011 5 rfc6253 The Certificate (CERT) parameter is a container for digital certificates. It is used for carrying these certificates in Host Identity Protocol (HIP) control packets. This document specifies the CERT parameter and the error signaling in case of a failed verification. Additionally, this document specifies the representations of Host Identity Tags in X.509 version 3 (v3) and Simple Public Key Infrastructure (SPKI) certificates. The concrete use of certificates, including how certificates are obtained, requested, and which actions are taken upon successful or failed verification, is specific to the scenario in which the certificates are used. Hence, the definition of these scenario- specific aspects is left to the documents that use the CERT parameter. mobile_access http://www.ietf.org/rfc/rfc6253.txt IETF RFC 6253 (Experimental) Request for Comments Internet Engineering Task Force Internet Engineering Task Force Request For Commments (Experimental Standard) 1 TobiasHeer SamuVarjonen techreport draft-ietf-hip-cert-08 2011 1 1 draft-ietf-hip-cert-08.txt <prt>expires: July 22, 2011 (work in progress)</prt> http://tools.ietf.org/html/draft-ietf-hip-cert-08 Online <prt>IETF Trust</prt> An online version is available at: http://tools.ietf.org/html/draft-ietf-hip-cert-08 Internet Drafts <prt>Internet Engineering Task Force</prt> Internet Engineering Task Force en 1 TobiasHeer SamuVarjonen techreport draft-ietf-hip-cert-07 2011 1 1 draft-ietf-hip-cert-07.txt <prt>expires: July 16, 2011 (work in progress)</prt> http://tools.ietf.org/html/draft-ietf-hip-cert-07 Online <prt>IETF Trust</prt> An online version is available at: http://tools.ietf.org/html/draft-ietf-hip-cert-07 Internet Drafts <prt>Internet Engineering Task Force</prt> Internet Engineering Task Force en 1 TobiasHeer SamuVarjonen techreport draft-ietf-hip-cert-09 2011 1 1 draft-ietf-hip-cert-09.txt 1 <prt>expires: July 22, 2011 (work in progress)</prt> http://tools.ietf.org/html/draft-ietf-hip-cert-09 Online <prt>IETF Trust</prt> An online version is available at: http://tools.ietf.org/html/draft-ietf-hip-cert-09 Internet Drafts <prt>Internet Engineering Task Force</prt> Internet Engineering Task Force en 1 TobiasHeer SamuVarjonen