Re: [P2PSIP] draft-maenpaa-p2psip-self-tuning-01

Jouni Mäenpää <jouni.maenpaa@ericsson.com> Sun, 08 November 2009 01:11 UTC

Return-Path: <jouni.maenpaa@ericsson.com>
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 D61573A68EC for <p2psip@core3.amsl.com>; Sat, 7 Nov 2009 17:11:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.949
X-Spam-Level:
X-Spam-Status: No, score=-5.949 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 Gh-TQhpMnCV4 for <p2psip@core3.amsl.com>; Sat, 7 Nov 2009 17:11:53 -0800 (PST)
Received: from mailgw5.ericsson.se (mailgw5.ericsson.se [193.180.251.36]) by core3.amsl.com (Postfix) with ESMTP id 27E463A68DD for <p2psip@ietf.org>; Sat, 7 Nov 2009 17:11:52 -0800 (PST)
X-AuditID: c1b4fb24-b7b12ae000007bda-b0-4af61af0d8c1
Received: from esealmw127.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw5.ericsson.se (Symantec Mail Security) with SMTP id 82.2D.31706.0FA16FA4; Sun, 8 Nov 2009 02:12:16 +0100 (CET)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.175]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959); Sun, 8 Nov 2009 02:12:16 +0100
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959); Sun, 8 Nov 2009 02:12:15 +0100
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se [131.160.33.3]) by mail.lmf.ericsson.se (Postfix) with ESMTP id BC4B824F7; Sun, 8 Nov 2009 03:12:15 +0200 (EET)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1]) by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 876E021A2A; Sun, 8 Nov 2009 03:12:15 +0200 (EET)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 5D8A7219B8; Sun, 8 Nov 2009 03:12:14 +0200 (EET)
Message-ID: <4AF61AED.50606@ericsson.com>
Date: Sun, 08 Nov 2009 10:12:13 +0900
From: Jouni Mäenpää <jouni.maenpaa@ericsson.com>
User-Agent: Thunderbird 2.0.0.17 (X11/20080925)
MIME-Version: 1.0
To: Cullen Jennings <fluffy@cisco.com>
References: <268D74B9-DE7A-4F55-9874-5B276B1FEE22@cisco.com>
In-Reply-To: <268D74B9-DE7A-4F55-9874-5B276B1FEE22@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-OriginalArrivalTime: 08 Nov 2009 01:12:16.0034 (UTC) FILETIME=[8299C820:01CA6010]
X-Brightmail-Tracker: AAAAAA==
Cc: P2PSIP WG <p2psip@ietf.org>
Subject: Re: [P2PSIP] draft-maenpaa-p2psip-self-tuning-01
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/mail-archive/web/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>
X-List-Received-Date: Sun, 08 Nov 2009 01:11:55 -0000

Hi Cullen,

Thanks for your comments. See inline for my answers.

Regards,
Jouni

Cullen Jennings wrote:

> I'm not sure what anyone else things, but I think it would be worth
> considering moving just one small part of to the base draft - namely
> Section 5.6.1.

I see no problem with doing that.

> On the Pro side for doing this:  It's really easy to implement and it
> would provide some interesting options for future things such as this
> self tuning draft.

The nice thing about self-tuning is that it automatically determines
appropriate values for the DHT parameters that are otherwise very
difficult to configure manually. An example is the stabilization rate.

> On the Con side for doing this: in many DHT, a large percentage of nodes
> leave without sending nay signaling that they are going to Leave so
> specifying what goes in a Leave message might be a little optimistic

I agree that many nodes may leave without sending any Leave messages
(i.e., crash). The mechanism works even without the data included in
Leave messages; including data in them is just an optimization that
speeds up recovery from peer departures in those cases in which peers
send explicit leave signaling. Section 6.3.1 of the draft deals with
failure detection (e.g., how for instance crashed peers are detected).