Re: [P2PSIP] :Re: Random resource probe

jiangxingfeng 36340 <jiang.x.f@huawei.com> Thu, 13 March 2008 14:08 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 014D528C8CE; Thu, 13 Mar 2008 07:08:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.088
X-Spam-Level:
X-Spam-Status: No, score=-100.088 tagged_above=-999 required=5 tests=[AWL=0.349, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 eAnuG6XdiscD; Thu, 13 Mar 2008 07:08:51 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2947128C8BD; Thu, 13 Mar 2008 07:07:42 -0700 (PDT)
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 C8B2C28C9B3 for <p2psip@core3.amsl.com>; Thu, 13 Mar 2008 07:07:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 LWDVvZPMSQgd for <p2psip@core3.amsl.com>; Thu, 13 Mar 2008 07:07:34 -0700 (PDT)
Received: from usaga01-in.huawei.com (usaga01-in.huawei.com [206.16.17.211]) by core3.amsl.com (Postfix) with ESMTP id E511B28C9FE for <p2psip@ietf.org>; Thu, 13 Mar 2008 07:05:26 -0700 (PDT)
Received: from huawei.com (usaga01-in [172.18.4.6]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0JXO00K8Q9P8RW@usaga01-in.huawei.com> for p2psip@ietf.org; Thu, 13 Mar 2008 07:03:08 -0700 (PDT)
Received: from huawei.com ([172.17.1.31]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0JXO00D0D9P6FV@usaga01-in.huawei.com> for p2psip@ietf.org; Thu, 13 Mar 2008 07:03:08 -0700 (PDT)
Received: from [172.24.1.6] (Forwarded-For: [130.129.19.1]) by szxmc03-in.huawei.com (mshttpd); Thu, 13 Mar 2008 09:03:00 -0500
Date: Thu, 13 Mar 2008 09:03:00 -0500
From: jiangxingfeng 36340 <jiang.x.f@huawei.com>
In-reply-to: <24CCCC428EFEA2469BF046DB3C7A8D22019E089D@namail5.corp.adobe.com>
To: Henry Sinnreich <hsinnrei@adobe.com>
Message-id: <f9778f92630f4.630f4f9778f92@huawei.com>
MIME-version: 1.0
X-Mailer: iPlanet Messenger Express 5.2 HotFix 2.14 (built Aug 8 2006)
Content-language: zh-CN
Content-disposition: inline
X-Accept-Language: zh-CN
Priority: normal
References: <47D568B6.2030102@joelhalpern.com> <DFBCE5CE-9083-4265-8018-3AC18EC60B4C@sipeerior.com> <618e24240803101044s4e0d4ff7l24bf34c695fe9887@mail.gmail.com> <DAA54A3C-B96C-4AD2-9522-FED6FE47F0A6@sipeerior.com> <fa02fc4a6448b.6448bfa02fc4a@huawei.com> <24CCCC428EFEA2469BF046DB3C7A8D22019E089D@namail5.corp.adobe.com>
Cc: Victor Pascual ?vila <victor.pascuala@upf.edu>, p2psip@ietf.org
Subject: Re: [P2PSIP] :Re: Random resource probe
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: <https://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: <https://www.ietf.org/mailman/listinfo/p2psip>, <mailto:p2psip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: p2psip-bounces@ietf.org
Errors-To: p2psip-bounces@ietf.org

> Discussing <draft-jiang-p2psip-sep-01> is a welcome opportunity to 
> freshen up on DHT and application layer (SIP) techniques such as:
> 

Some feautres from SEP are independent from application layer and could work with other proposals than SEP, I think.

> 1. Routing around congested or invisible nodes. This happens in 
> the DHT layer and is amply documented. Please remember we want to 
> keep the SIP and DHT layers neatly separated.

SEP tries to use keepalive message to communicate status of downstream peers and do some more intelligent routing decisions. It may not be supported by all DHT algorithms. But I think it is a interesting issue which will influence the transactions' success rate. 

> 2. Advertising and retrieval of classes of data such as 
> resources/services: SIP proxies, NAT traversal helpers that can do 
> STUN and maybe some flavors of ICE, NICE, D-ICE :-), plus some 
> relaying or (perish the thought) tunneling. There may be other 
> such as buddy lists and voice mail. 
> We would do well in the WG to define data types and classes to 
> facilitate faster retrieval (how?; range searches for coded data 
> types?).
> These topics have also been treated fairly well in: <draft-baset-
> p2psip-p2pp-01> and earlier in <draft-singh-p2p-sip-01>.
> 

Data model is a core structure in P2PSIP system. It is very important. Earlier RELOAD and P2PP also give descriptions on this topic. The service discovery method in SEP could be used to find a general service and could work with the core data model. 

> Questions: 
> 
> - Is storage and retrieval of data classes relevant to SIP 
> _generic and independent of the various P2PSIP proposals_?

I think, we need a independent service discovery method. You know, the essentienc of the P2P system is to make peers serve each other. So the important task for a peer in the overlay is to find peers where he could get help. So I think it is a important topic which should be considered in a base protocol. 

> 
> - What are the common concepts in the three I-Ds that can be 
> adopted by the WG, irrespective of the P2PSIP protocol choice?
> 
_______________________________________________
P2PSIP mailing list
P2PSIP@ietf.org
https://www.ietf.org/mailman/listinfo/p2psip