Re: [p2pi] Information in an ALTO protocol

Laird Popkin <laird@pando.com> Tue, 12 August 2008 14:46 UTC

Return-Path: <p2pi-bounces@ietf.org>
X-Original-To: p2pi-archive@ietf.org
Delivered-To: ietfarch-p2pi-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0E3993A6B48; Tue, 12 Aug 2008 07:46:01 -0700 (PDT)
X-Original-To: p2pi@core3.amsl.com
Delivered-To: p2pi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 11CCC28C101 for <p2pi@core3.amsl.com>; Tue, 12 Aug 2008 07:46:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.145
X-Spam-Level:
X-Spam-Status: No, score=-10.145 tagged_above=-999 required=5 tests=[AWL=0.120, BAYES_00=-2.599, HABEAS_ACCREDITED_COI=-8, IP_NOT_FRIENDLY=0.334]
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 w3nn3FXJWlCR for <p2pi@core3.amsl.com>; Tue, 12 Aug 2008 07:45:58 -0700 (PDT)
Received: from dkny.pando.com (dkny.pando.com [67.99.55.163]) by core3.amsl.com (Postfix) with ESMTP id 603F93A6A5F for <p2pi@ietf.org>; Tue, 12 Aug 2008 07:45:58 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by dkny.pando.com (Postfix) with ESMTP id 6A7E9E10BFC; Tue, 12 Aug 2008 10:45:38 -0400 (EDT)
X-Virus-Scanned: amavisd-new at
Received: from dkny.pando.com ([127.0.0.1]) by localhost (dkny.pando.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qvfwjx+O6zKj; Tue, 12 Aug 2008 10:45:32 -0400 (EDT)
Received: from dkny.pando.com (dkny.pando.com [10.10.60.11]) by dkny.pando.com (Postfix) with ESMTP id 3CD34E10BFB; Tue, 12 Aug 2008 10:45:32 -0400 (EDT)
Date: Tue, 12 Aug 2008 10:45:32 -0400
From: Laird Popkin <laird@pando.com>
To: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
Message-ID: <842019533.143161218552332226.JavaMail.root@dkny.pando.com>
In-Reply-To: <1068782360.143081218551863052.JavaMail.root@dkny.pando.com>
MIME-Version: 1.0
X-Originating-IP: [10.10.20.79]
Cc: p2pi@ietf.org, Richard Woundy <Richard_Woundy@cable.comcast.com>, Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
Subject: Re: [p2pi] Information in an ALTO protocol
X-BeenThere: p2pi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: P2P Infrastructure Discussion <p2pi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/p2pi>, <mailto:p2pi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/p2pi>
List-Post: <mailto:p2pi@ietf.org>
List-Help: <mailto:p2pi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/p2pi>, <mailto:p2pi-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: p2pi-bounces@ietf.org
Errors-To: p2pi-bounces@ietf.org

Many p2p networks already do this sort of thing, and I can't think of any way that the ISP could prevent it - any p2p app can measure throughput and report it. For example, see http://www.speedtest.net/global.php. Of course, this is only based on users that installed the agent, which may not be representative, and doesn't different between classes of users (since the agent can't tell whether they're on a DOCSIS 1/2/3 cable modem, etc.).

The advantage of getting link capacity info from the ISP rather than by measurement is that it's a bit faster and more consistent, and saves a little bandwidth by not doing the test.

The other alternative is to use commercial IP mapping databases (e.g. MaxMind's netspeed database), which is fast and cheap, but these databases not as accurate or precise as an ISP could be. For example, MaxMind differentiates between dial, broadband and corporate, but not between classes of broadband.

- Laird Popkin, CTO, Pando Networks
  mobile: 646/465-0570

----- Original Message -----
From: "Nicholas Weaver" <nweaver@ICSI.Berkeley.EDU>
To: "Laird Popkin" <laird@pando.com>
Cc: "Nicholas Weaver" <nweaver@ICSI.Berkeley.EDU>, "Richard Woundy" <Richard_Woundy@cable.comcast.com>, p2pi@ietf.org
Sent: Tuesday, August 12, 2008 10:28:03 AM (GMT-0500) America/New_York
Subject: Re: [p2pi] Information in an ALTO protocol


On Aug 12, 2008, at 7:12 AM, Laird Popkin wrote:

> Interesting points. I'm not paranoid enough. :-)

No, you're not.  Its not paranoia when they are out to get you.

> How about if this is exposed only to the ISP's customers?

My company-X P2P business model includes an agent I control on the  
user's computer, no?

So if its valuable, Company-X can use company-X's customers to mine  
the data.  This would especially be useful because you could do a  
direct increase in performance by feeding back the data to the  
tracking infrastructure.


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