1 / 4

HIP DHT Interface for Address Lookup Using OpenDHT

This document discusses the Hip DHT interface for address lookup leveraging OpenDHT. It outlines the process of using OpenDHT, including address and HIT lookup mechanisms, key structures, and value types. The document also provides guidelines on when to use DHT for connection setup and suggestions for publishing preferred locators. By following the guidelines presented, users can efficiently utilize the DHT for address management in HIP.

kiara-nieves
Download Presentation

HIP DHT Interface for Address Lookup Using OpenDHT

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. HIP-RG meeting, IETF-63 HIP DHT Interface (draft-ahrenholz-hiprg-dht-00.txt) August 5, 2004 Jeff Ahrenholz {jeffrey.m.ahrenholz@boeing.com}

  2. HIP using OpenDHT • OpenDHT is a deployment of the Bamboo DHT on PlanetLab • Provides generic PUT/GET interface • uses XML RPC • address lookup: addr = GET(HIT) • preferred locator is stored in the DHT • HIT lookup: HIT = GET(LSI) • this supports LSIs not based on HITs

  3. HIP DHT Interface Address publish +----------------+----------------------------+----------------+ | field | value | data type | +----------------+----------------------------+----------------+ | application | "hip-addr" | string | | | | | | client_library | (implementation dependent) | string | | | | | | key | 128-bit HIT | base64 encoded | | | | | | value | struct sockaddr | base64 encoded | | | | | | ttl_sec | current address lifetime | numeric string | +----------------+----------------------------+----------------+ HIT publish +----------------+-----------------------------------+----------------+ | field | value | data type | +----------------+-----------------------------------+----------------+ | application | "hip-hit" | string | | | | | | client_library | (implementation dependent) | string | | | | | | key | SHA1(struct sockaddr LSI|site id) | base64 encoded | | | | | | value | 128-bit HIT | base64 encoded | | | | | | ttl_sec | "604800" (maximum value) | numeric string | +----------------+-----------------------------------+----------------+

  4. When • DHT used here for connection setup (base exchange) • Suggested to lookup: • when a peer HIT is first configured, can lookup and cache address (latency for loading a list of peers) • before I1 if address unknown • after I1 retransmission timer fires (is address stale?) • Suggested to publish: • preferred locator upon startup • after change in preferred locator (maybe after UPDATEs are sent)

More Related