Re: [ppsp] I-D Action: draft-ietf-ppsp-base-tracker-protocol-00.txt

Arno Bakker <arno@cs.vu.nl> Wed, 20 February 2013 07:10 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 EF56621F8942 for <ppsp@ietfa.amsl.com>; Tue, 19 Feb 2013 23:10:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.504
X-Spam-Level:
X-Spam-Status: No, score=-3.504 tagged_above=-999 required=5 tests=[AWL=1.000, BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, RCVD_IN_DNSWL_MED=-4]
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 qOL1AW73+lsj for <ppsp@ietfa.amsl.com>; Tue, 19 Feb 2013 23:10:28 -0800 (PST)
Received: from mailin.vu.nl (mailin.vu.nl [130.37.164.17]) by ietfa.amsl.com (Postfix) with ESMTP id D39D621F8A3F for <ppsp@ietf.org>; Tue, 19 Feb 2013 23:10:27 -0800 (PST)
Received: from PEXHB012B.vu.local (130.37.236.67) by mailin.vu.nl (130.37.164.17) with Microsoft SMTP Server (TLS) id 14.2.298.4; Wed, 20 Feb 2013 08:10:23 +0100
Received: from [192.168.0.103] (130.37.238.20) by mails.vu.nl (130.37.236.67) with Microsoft SMTP Server (TLS) id 14.2.298.4; Wed, 20 Feb 2013 08:10:25 +0100
Message-ID: <512476F5.6040305@cs.vu.nl>
Date: Wed, 20 Feb 2013 08:10:45 +0100
From: Arno Bakker <arno@cs.vu.nl>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: ppsp@ietf.org
References: <20130214163150.29515.33443.idtracker@ietfa.amsl.com> <51235B1E.4070608@cs.vu.nl> <2ADFC759-ADF4-40D9-B08F-441AA08DF6E4@ieee.org>
In-Reply-To: <2ADFC759-ADF4-40D9-B08F-441AA08DF6E4@ieee.org>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Originating-IP: [130.37.238.20]
Subject: Re: [ppsp] I-D Action: draft-ietf-ppsp-base-tracker-protocol-00.txt
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, 20 Feb 2013 07:10:29 -0000

On 19/02/2013 18:22, Rui Cruz wrote:
>
> What I mean is: the tracker protocol semantics already conveys the
> "criteria" to be respected by the Tracker service in the corresponding
> responses regarding the peer list, and the "normal" behavior of the
> Tracker Service should be of taking a random sample of the peer
> population in a swarm (subject or not to more fine-grained criteria
> expressed in the PeerNum attributes or by Operators’ policy preferences,
> e.g., peer location).
> As such, the peer protocol requirement 13.2.3 was already considered,
> but not conveniently expressed in the text.
>

Hi Rui

if you could update the text to make this clearer that would be great.

Regards,
      Arno