Re: [P2PSIP] How to discover which peers provide which type of services

" Victor Pascual Ávila " <victor.pascual.avila@gmail.com> Wed, 06 February 2008 12:01 UTC

Return-Path: <p2psip-bounces@ietf.org>
X-Original-To: ietfarch-p2psip-archive@core3.amsl.com
Delivered-To: ietfarch-p2psip-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E6E383A6BDC; Wed, 6 Feb 2008 04:01:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level:
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from core3.amsl.com ([127.0.0.1]) by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U6521B0dP00h; Wed, 6 Feb 2008 04:01:37 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C60213A6D11; Wed, 6 Feb 2008 04:00:50 -0800 (PST)
X-Original-To: p2psip@core3.amsl.com
Delivered-To: p2psip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8AC603A6CF0 for <p2psip@core3.amsl.com>; Wed, 6 Feb 2008 04:00:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1]) by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jg+hxTIrvL6z for <p2psip@core3.amsl.com>; Wed, 6 Feb 2008 04:00:47 -0800 (PST)
Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.174]) by core3.amsl.com (Postfix) with ESMTP id 009713A6D01 for <p2psip@ietf.org>; Wed, 6 Feb 2008 03:57:46 -0800 (PST)
Received: by ug-out-1314.google.com with SMTP id u2so1390272uge.46 for <p2psip@ietf.org>; Wed, 06 Feb 2008 03:59:18 -0800 (PST)
Received: by 10.67.22.2 with SMTP id z2mr2564213ugi.1.1202299157853; Wed, 06 Feb 2008 03:59:17 -0800 (PST)
Received: by 10.66.252.5 with HTTP; Wed, 6 Feb 2008 03:59:17 -0800 (PST)
Message-ID: <618e24240802060359l6e19e92em5f3e46733180225c@mail.gmail.com>
Date: Wed, 6 Feb 2008 12:59:17 +0100
From: "=?UTF-8?Q?Victor_Pascual_=C3=81vila?=" <victor.pascual.avila@gmail.com>
To: JiangXingFeng <jiang.x.f@huawei.com>
In-Reply-To: <000501c867da$64e46400$2d09a40a@china.huawei.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <000501c867da$64e46400$2d09a40a@china.huawei.com>
Cc: P2PSIP Mailing List <p2psip@ietf.org>
Subject: Re: [P2PSIP] How to discover which peers provide which type of services
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/p2psip>, <mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/p2psip>, <mailto:p2psip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: p2psip-bounces@ietf.org
Errors-To: p2psip-bounces@ietf.org

Hi,

On Feb 5, 2008 10:35 AM, JiangXingFeng <jiang.x.f@huawei.com> wrote:
> So I think, we could classify the service discovery method into two
> categories:
> The first one is based on the common PUT/GET operations; the other one is
> trying to relying on the most of peer's knowledge to find the suited peer.
>
> The first three methods in P2PP and the method in RELOAD-2 belong to the
> first category; The random work in P2PP and method proposed in SEP belong to
> the second one.
>
> For the second category, since it relies on each peer the request will
> traverse to find the service peer, we could make the intermediate peer not
> only check the routing states of each peer, but also tries to find them in
> the following data source:
> 1. The Peer's client service capability;
> 2. Using Standard Service Name to lookup <resource ID, value> pair.
> 3. Other data source which emerges in the future.
>
> By doing this extension, it will improve the success rate of the lookup
> operation.
>
> How about your opinions? Comments are appreciated.

A service agnostic technique would use a SOA-like approach for
discovering and providing services using the P2PSIP overlay network.
Our concept uses Service Consumer, Service Broker and Service
Providers entities where each one is a peer or even a group of peers
in the P2PSIP overlay network. Abstract Service is requested by
Service Consumer and Service Broker returns implementation of a
service as a reference to Service Provider. Mapping between abstract
service name and implementation is kept within P2PSIP overlay.

<Peer,Service> discovery could be a issue to discuss during the
upcoming meeting in Philadelphia.

Thank you,
-- 
Victor Pascual Ávila
Research Engineer
Tel.  +34 93 542 2906
Fax. +34 93 542 2517

Research Group on Network Technologies and Strategies (NeTS)
Universitat Pompeu Fabra (UPF)
Pg. de Circumval·lació, 8
Office 358
08003 Barcelona (Spain)
http://nets.upf.edu/
_______________________________________________
P2PSIP mailing list
P2PSIP@ietf.org
http://www.ietf.org/mailman/listinfo/p2psip