Re: [P2PSIP] Merge of P2PP and RELOAD

Eric Rescorla <ekr@networkresonance.com> Thu, 28 February 2008 19:38 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 9AAB23A6EFF; Thu, 28 Feb 2008 11:38:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.36
X-Spam-Level:
X-Spam-Status: No, score=-0.36 tagged_above=-999 required=5 tests=[AWL=0.077, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1]
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 MwjjD3Mhv-wy; Thu, 28 Feb 2008 11:38:44 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 49FF928C5CF; Thu, 28 Feb 2008 11:38:42 -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 AB5DA28C5CF for <p2psip@core3.amsl.com>; Thu, 28 Feb 2008 11:38:41 -0800 (PST)
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 z6YMamRrvBGU for <p2psip@core3.amsl.com>; Thu, 28 Feb 2008 11:38:38 -0800 (PST)
Received: from romeo.rtfm.com (unknown [74.95.2.173]) by core3.amsl.com (Postfix) with ESMTP id 62B7A28C941 for <p2psip@ietf.org>; Thu, 28 Feb 2008 11:38:08 -0800 (PST)
Received: from romeo.rtfm.com (localhost.rtfm.com [127.0.0.1]) by romeo.rtfm.com (Postfix) with ESMTP id 2BDA85081A; Thu, 28 Feb 2008 11:39:53 -0800 (PST)
Date: Thu, 28 Feb 2008 11:39:53 -0800
From: Eric Rescorla <ekr@networkresonance.com>
To: Michael Chen <michaelc@idssoftware.com>
In-Reply-To: <47C6C74D.5000902@idssoftware.com>
References: <20080224201501.7A0983A6C7A@core3.amsl.com> <51849779-F812-47A0-A3EB-0FE5B5A3AB6B@cisco.com> <47C6C74D.5000902@idssoftware.com>
User-Agent: Wanderlust/2.14.0 (Africa) Emacs/21.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Message-Id: <20080228193953.2BDA85081A@romeo.rtfm.com>
Cc: P2PSIP WG <p2psip@ietf.org>
Subject: Re: [P2PSIP] Merge of P2PP and RELOAD
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

Michael writes:
> It's great to see progress!
> 
> Could the authors of P2PP highlight what parts of p2pp were adopted in 
> RELOAD-03?

I'm not a P2PP author, but I hope you won't mind if I respond.

As you know, architecturally P2PP and RELOAD were actually very
similar, with quite similar feature sets. Even so, it's pretty hard to
merge all the words piecewise so we ended up starting with the RELOAD
text and trying to make sure that all the functionality in P2PP that
wasn't in RELOAD (unstructured DHTs, hop-by-hop reliability,
diagnostics, etc.)  got merged in. So, I think the more important
question here is whether we lost important P2PP functionality in the
merge. I think the answer to that is "no".

Best,
-Ekr



_______________________________________________
P2PSIP mailing list
P2PSIP@ietf.org
https://www.ietf.org/mailman/listinfo/p2psip