Re: [ppsp] Request: draft-cruz-ppsp-base-tracker-protocol as WG item
Arno Bakker <arno@cs.vu.nl> Wed, 21 November 2012 12:56 UTC
Return-Path: <a.bakker@vu.nl>
X-Original-To: ppsp@ietfa.amsl.com
Delivered-To: ppsp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E54121F8695 for <ppsp@ietfa.amsl.com>; Wed, 21 Nov 2012 04:56:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.814
X-Spam-Level:
X-Spam-Status: No, score=-1.814 tagged_above=-999 required=5 tests=[AWL=-0.310, BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wFu3RiujLH5Z for <ppsp@ietfa.amsl.com>; Wed, 21 Nov 2012 04:56:20 -0800 (PST)
Received: from mailin.vu.nl (mailin.vu.nl [130.37.164.18]) by ietfa.amsl.com (Postfix) with ESMTP id 8396A21F866F for <ppsp@ietf.org>; Wed, 21 Nov 2012 04:56:19 -0800 (PST)
Received: from PEXHB012B.vu.local (130.37.236.67) by mailin.vu.nl (130.37.164.18) with Microsoft SMTP Server (TLS) id 14.2.298.4; Wed, 21 Nov 2012 13:56:17 +0100
Received: from [192.168.0.102] (130.37.238.20) by mails.vu.nl (130.37.236.67) with Microsoft SMTP Server (TLS) id 14.2.298.4; Wed, 21 Nov 2012 13:56:18 +0100
Message-ID: <50ACCF90.6080308@cs.vu.nl>
Date: Wed, 21 Nov 2012 13:56:48 +0100
From: Arno Bakker <arno@cs.vu.nl>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20120312 Thunderbird/11.0
MIME-Version: 1.0
To: Rui Cruz <rui.cruz@ieee.org>
References: <1388AC0A-2E2E-4EE5-8868-688E7BE6E252@cisco.com> <EC14A918-B208-411A-902C-994297E0035C@cisco.com> <50A21BF4.9010102@cs.vu.nl> <52529918-0790-47C2-84D0-A1D11FE14129@ieee.org> <50A344CA.6060307@cs.vu.nl> <35D4DB2A-7468-490C-8147-FA9E5FF69B50@ieee.org>
In-Reply-To: <35D4DB2A-7468-490C-8147-FA9E5FF69B50@ieee.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [130.37.238.20]
Cc: ppsp@ietf.org
Subject: Re: [ppsp] Request: draft-cruz-ppsp-base-tracker-protocol as WG item
X-BeenThere: ppsp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: arno@cs.vu.nl
List-Id: discussing to draw up peer to peer streaming protocol <ppsp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ppsp>, <mailto:ppsp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ppsp>
List-Post: <mailto:ppsp@ietf.org>
List-Help: <mailto:ppsp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ppsp>, <mailto:ppsp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Nov 2012 12:56:20 -0000
Hi Rui et al, please see inline. On 14/11/2012 13:36, Rui Cruz wrote: >> >> At the moment when peerMode is SEED the tracker appears not to send a >> peer list (p. 27 at bottom). Please clarify how a seed obtains a peer >> list, e.g. does PeerNum take priority over peerMode? > Using only the base protocol (the extended protocol provides extra > control in this area) the condition you mention might be turned implicit > if peerNum is supplied when peerMode is SEED. > I personally have no objection with that condition. > If WG agrees a paragraph can be added to describe it. > Please do. > The CONNECT message in the base protocol is restricted to certain > conditions. IMHO, these restrictions on CONNECT could be lifted to allow it to be used for refreshing registrations, yielding a very simple 1 message protocol. >> But if it is currently not possible to implement a tracker service >> that offers this functionality and is secure in a malicious >> environment, the support for it should not be in the tracker protocol, >> IMHO. > I do not agree with your position stating that a (global) trust > functionality is "not possible" to be offered. > An implementation of a tracker service can perfectly offer a trust > functionality. It might not be "global" but can be offered. > In EU Project SARACEN we have an implementation of a trust/reputation > functionality. Let me phrase it differently: Can you build a PPSP-based YouTube that securely uses this property-based peer selection? If not, the draft should make it clear that property-based selections can only be safely used under specific conditions. CU, Arno
- [ppsp] Request: draft-cruz-ppsp-base-tracker-prot… stefano previdi
- [ppsp] 答复: Request: draft-cruz-ppsp-base-tracker-… Guyingjie (Yingjie)
- Re: [ppsp] 答复: Request: draft-cruz-ppsp-base-trac… Rui Cruz
- [ppsp] 答复: Request: draft-cruz-ppsp-base-tracker-… Xiajinwei
- Re: [ppsp] 答复: Request: draft-cruz-ppsp-base-trac… João Pedro Taveira
- Re: [ppsp] Request: draft-cruz-ppsp-base-tracker-… zhangyunfei
- Re: [ppsp] Request: draft-cruz-ppsp-base-tracker-… Arno Bakker
- Re: [ppsp] Request: draft-cruz-ppsp-base-tracker-… Rui Cruz
- Re: [ppsp] Request: draft-cruz-ppsp-base-tracker-… Arno Bakker
- Re: [ppsp] Request: draft-cruz-ppsp-base-tracker-… Rui Cruz
- Re: [ppsp] Request: draft-cruz-ppsp-base-tracker-… Arno Bakker
- Re: [ppsp] Request: draft-cruz-ppsp-base-tracker-… Zongning
- Re: [ppsp] Request: draft-cruz-ppsp-base-tracker-… Rui Cruz
- Re: [ppsp] Request: draft-cruz-ppsp-base-tracker-… Arno Bakker
- Re: [ppsp] Request: draft-cruz-ppsp-base-tracker-… zhangyunfei