40 likes | 132 Views
HIP-RG meeting, IETF-63. HIP DHT Interface (draft-ahrenholz-hiprg-dht-00.txt) August 5, 2004. Jeff Ahrenholz {jeffrey.m.ahrenholz@boeing.com}. HIP using OpenDHT. OpenDHT is a deployment of the Bamboo DHT on PlanetLab Provides generic PUT/GET interface uses XML RPC
E N D
HIP-RG meeting, IETF-63 HIP DHT Interface (draft-ahrenholz-hiprg-dht-00.txt) August 5, 2004 Jeff Ahrenholz {jeffrey.m.ahrenholz@boeing.com}
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
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 | +----------------+-----------------------------------+----------------+
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)