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

"Roy, Radhika R Dr CTR USA USAMC" <radhika.r.roy@us.army.mil> Wed, 06 February 2008 14:04 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 4BBC53A6E08; Wed, 6 Feb 2008 06:04:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.999
X-Spam-Level:
X-Spam-Status: No, score=-4.999 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 Rmm8fseRknlc; Wed, 6 Feb 2008 06:04:09 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 289B83A6D00; Wed, 6 Feb 2008 06:04:09 -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 AA8F13A6D00 for <p2psip@core3.amsl.com>; Wed, 6 Feb 2008 06:04:07 -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 PbY7oc2qyCAU for <p2psip@core3.amsl.com>; Wed, 6 Feb 2008 06:04:06 -0800 (PST)
Received: from mxoutps1.us.army.mil (mxoutps1.us.army.mil [143.69.250.38]) by core3.amsl.com (Postfix) with ESMTP id 42FD33A6C26 for <p2psip@ietf.org>; Wed, 6 Feb 2008 06:04:04 -0800 (PST)
From: "Roy, Radhika R Dr CTR USA USAMC" <radhika.r.roy@us.army.mil>
X-AKO: 113008873:10.224.36.65:06 Feb 2008 14:05:25 +0000:$Webmail:None
X-IronPort-AV: E=Sophos;i="4.25,312,1199664000"; d="scan'208";a="113008873"
Received: from mail5.int.ps1.us.army.mil (HELO us.army.mil) ([10.224.36.65]) by mxoutps1.us.army.mil with ESMTP; 06 Feb 2008 14:05:20 +0000
Received: from [10.240.32.176] (Forwarded-For: 134.80.13.193, [10.240.32.176]) by mail5.int.ps1.us.army.mil (mshttpd); Wed, 06 Feb 2008 09:05:20 -0500
To: =?iso-8859-1?Q?Victor_Pascual_=C1vila?= <victor.pascual.avila@gmail.com>
Message-ID: <e15eaafa4165b.47a97850@us.army.mil>
Date: Wed, 06 Feb 2008 09:05:20 -0500
X-Mailer: Sun Java(tm) System Messenger Express 6.2-9.04 (built Jun 11 2007)
MIME-Version: 1.0
Content-Language: en
X-Accept-Language: en
Priority: normal
In-Reply-To: <618e24240802060359l6e19e92em5f3e46733180225c@mail.gmail.com>
References: <000501c867da$64e46400$2d09a40a@china.huawei.com> <618e24240802060359l6e19e92em5f3e46733180225c@mail.gmail.com>
Content-Disposition: inline
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: p2psip-bounces@ietf.org
Errors-To: p2psip-bounces@ietf.org

Inline [RRR]

----- Original Message -----
From: Victor Pascual Ávila 
Date: Wednesday, February 6, 2008 7:06
Subject: Re: [P2PSIP] How to discover which peers provide which type of services
To: JiangXingFeng 
Cc: P2PSIP Mailing List 

> Hi,
> 
> On Feb 5, 2008 10:35 AM, JiangXingFeng 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 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.
> 
[RRR] I would not say P2PSIP is completely service agostic per se. The use of the term - SIP, does it not make it almost servcie-specific (i.e. it has a limited view of service as opposed to 'generic')?

[RRR] Are you indicating something like UDDI of web services for discovery? If so, how far do we like to go in developing the P2PSIP protocol as we are NOT chartered for development of the generic P2P protocol?

> discovery could be a issue to discuss during the
> upcoming meeting in Philadelphia.

[RRR] In any event, we would like to have the experiences of this meeting and let us apply those findings as a part of the P2PSIP protocol development that has more limited objectives. So, your comments in this WG will really be valuable.

> 
> 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
> 
_______________________________________________
P2PSIP mailing list
P2PSIP@ietf.org
http://www.ietf.org/mailman/listinfo/p2psip