[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [P2PSIP] Boot strap peers
Hi Cullen,
I think there are two ways to decide the bootstrap peers.
First, the bootstrap server is easy to determine which peer to be the bootstrap peer if it can get all online peers' information from a certain entity, e.g., from a server that keeps all peers' information (Enrollment server or else?).
Second, some reputation mechanism can be used to select the bootstrap peer by the overlay itself. I think in some scenarios this is practical.
There should be a status maintenance mechanism between a bootstrap peer and the bootstrap server. At least when a bootstrap server is going to leave the overlay, it must notify the bootstrap server for its leaving, so that the bootstrap server can keep a list of effect peers for bootstrapping.
I think we should keep in mind that if we want the bootstrapping progress to be effective, we should ensure the list of bootstrap peers alive and easy to access(not behind very restrict NAT or FW).
Best Regards,
Song Haibin
Email: melodysong at huawei.com
Skype: alexsonghw
___________________From p2psip-bounces at ietf.org Fri Jul 18 00:06:12 2008
Return-Path: <p2psip-bounces at ietf.org>
X-Original-To: p2psip-archive at optimus.ietf.org
Delivered-To: ietfarch-p2psip-archive at core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id 8CB263A688D;
Fri, 18 Jul 2008 00:06:12 -0700 (PDT)
X-Original-To: p2psip at core3.amsl.com
Delivered-To: p2psip at core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id F26623A688D
for <p2psip at core3.amsl.com>; Fri, 18 Jul 2008 00:06:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.224
X-Spam-Level:
X-Spam-Status: No, score=-2.224 tagged_above=-999 required=5
tests=[AWL=-0.225, BAYES_00=-2.599, J_CHICKENPOX_63=0.6]
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 oA12YXR1ltwJ for <p2psip at core3.amsl.com>;
Fri, 18 Jul 2008 00:06:10 -0700 (PDT)
Received: from usaga01-in.huawei.com (usaga01-in.huawei.com [206.16.17.211])
by core3.amsl.com (Postfix) with ESMTP id 3B9A43A67AC
for <p2psip at ietf.org>; Fri, 18 Jul 2008 00:06:10 -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 <0K4600CKKX36EK at usaga01-in.huawei.com> for
p2psip at ietf.org; Fri, 18 Jul 2008 00:06:43 -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 <0K4600MFNX353R at usaga01-in.huawei.com> for
p2psip at ietf.org; Fri, 18 Jul 2008 00:06:42 -0700 (PDT)
Received: from [172.24.1.12] (Forwarded-For: [10.164.9.76])
by szxmc03-in.huawei.com (mshttpd); Fri, 18 Jul 2008 15:06:28 +0800
Date: Fri, 18 Jul 2008 15:06:28 +0800
From: songhaibin 64081 <melodysong at huawei.com>
In-reply-to: <2D8D7D06-C04D-4ADB-963C-0461FF5E5B78 at cisco.com>
To: Cullen Jennings <fluffy at cisco.com>
Message-id: <fe8c82a77f.7ffe8c82a7 at huawei.com>
MIME-version: 1.0
X-Mailer: iPlanet Messenger Express 5.2 HotFix 2.14 (built Aug 8 2006)
Content-language: en
Content-disposition: inline
X-Accept-Language: en
Priority: normal
References: <2D8D7D06-C04D-4ADB-963C-0461FF5E5B78 at cisco.com>
Cc: P2PSIP WG <p2psip at ietf.org>
Subject: Re: [P2PSIP] Boot strap peers
X-BeenThere: p2psip at 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 at ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip at ietf.org>
List-Help: <mailto:p2psip-request at ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/p2psip>,
<mailto:p2psip-request at ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: p2psip-bounces at ietf.org
Errors-To: p2psip-bounces at ietf.org
Hi Cullen,
I think there are two ways to decide the bootstrap peers.
First, the bootstrap server is easy to determine which peer to be the bootstrap peer if it can get all online peers' information from a certain entity, e.g., from a server that keeps all peers' information (Enrollment server or else?).
Second, some reputation mechanism can be used to select the bootstrap peer by the overlay itself. I think in some scenarios this is practical.
There should be a status maintenance mechanism between a bootstrap peer and the bootstrap server. At least when a bootstrap server is going to leave the overlay, it must notify the bootstrap server for its leaving, so that the bootstrap server can keep a list of effect peers for bootstrapping.
I think we should keep in mind that if we want the bootstrapping progress to be effective, we should ensure the list of bootstrap peers alive and easy to access(not behind very restrict NAT or FW).
Best Regards,
Song Haibin
Email: melodysong at huawei.com
Skype: alexsonghw
_______________________________________________________
P2PSIP mailing list
P2PSIP at ietf.org
https://www.ietf.org/mailman/listinfo/p2psip
____________________
P2PSIP mailing list
P2PSIP at ietf.org
https://www.ietf.org/mailman/listinfo/p2psip