RE: [P2PSIP] Term for the peer who is responsible for a specific key

"Henry Sinnreich" <hsinnrei@adobe.com> Thu, 30 August 2007 16:37 UTC

Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IQn1Z-0006m5-0i; Thu, 30 Aug 2007 12:37:41 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IQn1X-0006lx-Af for p2psip@ietf.org; Thu, 30 Aug 2007 12:37:39 -0400
Received: from exprod6og55.obsmtp.com ([64.18.1.191]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IQn1W-0006kv-JX for p2psip@ietf.org; Thu, 30 Aug 2007 12:37:39 -0400
Received: from source ([192.150.11.134]) by exprod6ob55.postini.com ([64.18.5.12]) with SMTP; Thu, 30 Aug 2007 09:37:21 PDT
Received: from inner-relay-1.corp.adobe.com ([153.32.1.51]) by outbound-smtp-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id l7UGZmIQ006720; Thu, 30 Aug 2007 09:35:48 -0700 (PDT)
Received: from fe1.corp.adobe.com (fe1.corp.adobe.com [10.8.192.70]) by inner-relay-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id l7UGapRg005596; Thu, 30 Aug 2007 09:37:20 -0700 (PDT)
Received: from namail5.corp.adobe.com ([10.8.192.88]) by fe1.corp.adobe.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 30 Aug 2007 09:37:15 -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
Subject: RE: [P2PSIP] Term for the peer who is responsible for a specific key
Date: Thu, 30 Aug 2007 09:37:04 -0700
Message-ID: <24CCCC428EFEA2469BF046DB3C7A8D223AE026@namail5.corp.adobe.com>
In-Reply-To: <001801c7eb1e$ccb92360$030aa8c0@comcast.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [P2PSIP] Term for the peer who is responsible for a specific key
Thread-Index: AcfrHkORJfrFJSedTOO2QpnLA1qRcgAA3bIg
References: <011c01c7eaa4$87c9e480$5105a40a@china.huawei.com><0142F8A2-D96A-4956-9873-DE3454C2FB99@magma.ca> <001801c7eb1e$ccb92360$030aa8c0@comcast.net>
From: Henry Sinnreich <hsinnrei@adobe.com>
To: Peter Pan <huang-ming.pan@comcast.net>, Philip Matthews <philip_matthews@magma.ca>, Zheng Hewen <hwzheng@huawei.com>
X-OriginalArrivalTime: 30 Aug 2007 16:37:15.0036 (UTC) FILETIME=[05B3ADC0:01C7EB24]
X-Spam-Score: 1.8 (+)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Cc: Jan Seedorf <Jan.Seedorf@netlab.nec.de>, P2PSIP Mailing List <p2psip@ietf.org>
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>, <mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>, <mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

As Jan Seedorf has already indicated (see below), the root in a DHT is
well defined and documented. Here are three examples, including one from
the P2P SIP WG I-D :-)>

If anything, this trail shows the need for a DHT and P2PSIP glossary.

Henry

A. Chord vn. 0.6.3 released on May 3, 2007 features:
* The root node of routing creates and removes replicas on a DHT instead
of the requester if replication is enabled. 
* In case of DHT put, get and remove, a node requests spare root
candidates to be prepared for failure of the root node. 

See http://overlayweaver.sourceforge.net/news/ 

B. Chord and Bamboo

"The DHT assigns every key in the identifier space to
a node, which is called the root (or the successor) of the
key. The main primitive that DHTs support is lookup, in
which a node can efficiently discover a key's root. The
lookup protocol greedily traverses the nodes of the DHT,
progressing closer to the root of the key at each step."

See http://srhea.net/papers/ntr-worlds05.pdf 

C. In the IETF P2P SIP WG:

"Req 7-5: The peer protocol MUST accommodate a DHT for a fast routing 
 algorithm that minimizes hop count to the root node..."

See
http://tools.ietf.org/wg/p2psip/draft-bryan-p2psip-requirements-00.txt 

Henry

-----Original Message-----
From: Peter Pan [mailto:huang-ming.pan@comcast.net] 
Sent: Thursday, August 30, 2007 11:00 AM
To: Philip Matthews; Zheng Hewen
Cc: 'Jan Seedorf'; 'P2PSIP Mailing List'
Subject: Re: [P2PSIP] Term for the peer who is responsible for a
specific key

neither have i, though i did heard of "root beer".

peter


----- Original Message -----
From: "Philip Matthews" <philip_matthews@magma.ca>
To: "Zheng Hewen" <hwzheng@huawei.com>
Cc: "'Jan Seedorf'" <Jan.Seedorf@netlab.nec.de>; "'P2PSIP Mailing List'"
<p2psip@ietf.org>
Sent: Thursday, August 30, 2007 8:45 AM
Subject: Re: [P2PSIP] Term for the peer who is responsible for a
specific
key


> I personally have never heard of the term "root peer" before, and I
> would never guess that it mean the peer that stores the content
> associated with a key. Can someone explain where this term comes
> from? What is it the root of?
>
> - Philip
>
> On 29-Aug-07, at 21:24 , Zheng Hewen wrote:
>
> > Hi,
> >
> > I suggest that the concept draft would adopt those terms - "P2PSIP
> > root peer" and "P2PSIP replica root peer", they are clear
> > and useful for contributors to P2PSIP WG.
> >
> > --Hewen
> >
> > -----Original Message-----
> > From: Jan Seedorf [mailto:Jan.Seedorf@netlab.nec.de]
> > Sent: 2007?8?29? 23:53
> > To: P2PSIP Mailing List
> > Subject: RE: [P2PSIP] Term for the peer who is responsible for a
> > specific key
> >
> > Dear Henry and Spencer (I am replying to the last two mails on this
> > thread),
> >
> > In the DHT literature the node responsible for storing the content
> > belonging to some key is usually referred to as the
> > "root" node for that particular key. If content for a key is
> > additionally stored at several nodes in the DHT to provide
> > resilience on the DHT layer, these nodes are referred to as the
> > "replica roots" for that key.
> >
> > Hope this helps,
> >
> > - Jan Seedorf
> >

_______________________________________________
P2PSIP mailing list
P2PSIP@ietf.org
https://www1.ietf.org/mailman/listinfo/p2psip