Re: [hiprg] draft-ahrenholz-hiprg-dht-05

"Ahrenholz, Jeffrey M" <jeffrey.m.ahrenholz@boeing.com> Mon, 14 September 2009 19:53 UTC

Return-Path: <jeffrey.m.ahrenholz@boeing.com>
X-Original-To: hiprg@core3.amsl.com
Delivered-To: hiprg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CFD793A6A9B for <hiprg@core3.amsl.com>; Mon, 14 Sep 2009 12:53:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7ARNvw8d+ISA for <hiprg@core3.amsl.com>; Mon, 14 Sep 2009 12:53:06 -0700 (PDT)
Received: from blv-smtpout-01.boeing.com (blv-smtpout-01.boeing.com [130.76.32.69]) by core3.amsl.com (Postfix) with ESMTP id E9A5B3A6A76 for <hiprg@irtf.org>; Mon, 14 Sep 2009 12:53:05 -0700 (PDT)
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6]) by blv-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id n8EJraIt012142 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 14 Sep 2009 12:53:41 -0700 (PDT)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id n8EJraZg027969; Mon, 14 Sep 2009 14:53:36 -0500 (CDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com [130.247.55.84]) by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id n8EJrYEr027930; Mon, 14 Sep 2009 14:53:35 -0500 (CDT)
Received: from XCH-NW-6V1.nw.nos.boeing.com ([130.247.55.53]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 14 Sep 2009 12:53:35 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 14 Sep 2009 12:53:33 -0700
Message-ID: <0DF156EE7414494187B087A3C279BDB404AD7CA8@XCH-NW-6V1.nw.nos.boeing.com>
In-Reply-To: <4AA89413.3070003@hiit.fi>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [hiprg] draft-ahrenholz-hiprg-dht-05
Thread-Index: Acox2txfICWD4MXpRAag+pV/wPBoqgDlx0+g
References: <0DF156EE7414494187B087A3C279BDB404AD7C9D@XCH-NW-6V1.nw.nos.boeing.com> <4AA89413.3070003@hiit.fi>
From: "Ahrenholz, Jeffrey M" <jeffrey.m.ahrenholz@boeing.com>
To: miika.komu@hiit.fi
X-OriginalArrivalTime: 14 Sep 2009 19:53:35.0311 (UTC) FILETIME=[0B747DF0:01CA3575]
Cc: hiprg@irtf.org
Subject: Re: [hiprg] draft-ahrenholz-hiprg-dht-05
X-BeenThere: hiprg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Host Identity Protocol \(HIP\) Research Group" <hiprg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/hiprg>, <mailto:hiprg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/hiprg>
List-Post: <mailto:hiprg@irtf.org>
List-Help: <mailto:hiprg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/hiprg>, <mailto:hiprg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Sep 2009 19:53:06 -0000

> good. Why doesn't this document yet have individual label 
> instead of the 
> official research group label? Maybe I have forgotten the reason.

The first version had the name draft-irtf-hip-dht-00 (see
https://listserv.cybertrust.com/pipermail/hipsec-rg/2005-July/000190.htm
l) but at the time was not a research group item but an individual
submission, so it was renamed. The only official RG draft is the
experiment report. If there is interest I am willing to change this
draft's designation.

> > Even though the OpenDHT service has retired on PlanetLab, 
> we can still
> > use the same interface with OpenLookup
> > (http://code.google.com/p/openlookup/) for experimentation.
> 
> We are using it as well in HIIT/TKK.
> 
> There are now two implementations of the same DHT interface. Jeff, 
> should we try interoperability to take this to the next level?

Yes we should try interoperability at some point. We need to update the
OpenHIP software to support this latest draft.

-Jeff