Re: [p2pi] After-BoF charter
Laird Popkin <laird@pando.com> Thu, 14 August 2008 18:07 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 B7FDF3A6886; Thu, 14 Aug 2008 11:07:55 -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 608FD3A6886 for <p2pi@core3.amsl.com>; Thu, 14 Aug 2008 11:07:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.165
X-Spam-Level:
X-Spam-Status: No, score=-10.165 tagged_above=-999 required=5 tests=[AWL=0.100, 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 QGoAEyiyX4iZ for <p2pi@core3.amsl.com>; Thu, 14 Aug 2008 11:07:54 -0700 (PDT)
Received: from dkny.pando.com (dkny.pando.com [67.99.55.163]) by core3.amsl.com (Postfix) with ESMTP id 315703A684E for <p2pi@ietf.org>; Thu, 14 Aug 2008 11:07:54 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by dkny.pando.com (Postfix) with ESMTP id 69751E10B92; Thu, 14 Aug 2008 14:07:22 -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 aA-EWk5FbDpz; Thu, 14 Aug 2008 14:07:11 -0400 (EDT)
Received: from [10.10.20.61] (unknown [10.10.20.61]) by dkny.pando.com (Postfix) with ESMTP id 129FDE10B88; Thu, 14 Aug 2008 14:07:11 -0400 (EDT)
Message-Id: <90CC235D-FB1F-4F59-B57B-A2E378B559DC@pando.com>
From: Laird Popkin <laird@pando.com>
To: Enrico Marocco <enrico.marocco@telecomitalia.it>
In-Reply-To: <48A46A5F.4080606@telecomitalia.it>
Mime-Version: 1.0 (Apple Message framework v928.1)
Date: Thu, 14 Aug 2008 14:07:10 -0400
References: <489B47A0.1050507@telecomitalia.it> <EAFFEDBC-D318-4A37-A307-31C2F134DBD6@nokia.com> <20080808161710.GA25453@verdi> <48A46A5F.4080606@telecomitalia.it>
X-Mailer: Apple Mail (2.928.1)
Cc: Lisa Dusseault <lisa@osafoundation.org>, "p2pi@ietf.org" <p2pi@ietf.org>
Subject: Re: [p2pi] After-BoF charter
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: p2pi-bounces@ietf.org
Errors-To: p2pi-bounces@ietf.org
On Aug 14, 2008, at 1:24 PM, Enrico Marocco wrote: > John Leslie wrote: >> The speed of convergence to optimal is the critical issue: we want >> a "better-than-random" initial set of peers to try (and possibly an >> ordered list to try if they prove unsatisfactory. >> >> I think adding the word "inital" would help: >> " >> " information to perform better-than-random initial peer selection. > > Yes, that's better. I strongly agree - this clarifies the relationship between ALTO and P2P networks quite nicely. >>>> Protocols used for peer selection optimization will carry >>>> information >>>> related to the topology and the policies of the querying peer's >>>> network (i.e. queries on behalf of other peers are not allowed). >> >> We should perhaps be careful about this last prohibition. I'm not >> sure the obvious mechanism (matching the source IP address of a >> query) >> is wise (though I certainly wouldn't prohibit implementations from >> trying it). >> >> There are obvious potential benefits from letting particular >> trackers read an ISP's policies (by prior arrangement, usually). A >> blanket prohibition of this seems unnecessary. > > That's true, but, on the other hand, allowing uncontrolled third-party > queries would be a privacy nightmare, for both users and ISPs. I've > personally had a discussion with Stanislav, who said that having peers > doing the ALTO query and passing the response back to a BitTorrent > tracker would not be too much of a hassle, so, probably, given the > costs > that controlling third-party queries in a reasonable way would > imply, it > could be wise to just forbid them. However, I would really like to > hear > what other people think about this, especially on the P2P side. A p2p network can query ALTO information through clients, of course. If ALTO is used by Trackers to decide which peers to connect, then it's a matter of getting the right info to the Tracker. IMO ALTO should allow the expression of an ISP policy that applies more broadly than a single client. For example, if a client can get the ALTO guidance that "for all of my customers (defined by an IP prefix list), please do p2p transfers with the FTTH users (defined by an IP prefix list) before other users.") then the p2p service can apply that policy to all peers without them all having to individually ask the ALTO server. If ALTO were limited to telling each client what policy to apply to its p2p connections, then every p2p client would have to make an ALTO query, then pass the response back to the Tracker to analyze and apply. This seems like more work all around, so I hope that we don't restrict ALTO to this case. >>>> It is reasonable to expect that applications will use such >>>> protocols >>>> to discover Autonomous System (AS) numbers and approximate >>>> geographic >>>> location of peers hosting the needed resources, >> >> I don't even _understand_ this. >> >> Current trackers _do_ try to find these pieces of information, but >> IMHO they're suboptimal substitutes for information ISPs could >> provide. >> I see no reason to include such text in a charter. > > Right, we have let them in exactly because that's the kind of > information a third-party non-ISP ALTO service provider could provide > (ip2location and "looking glass" web services already do, just in a > non-standard way). We could get rid of those pieces of information, > but > that would probably reduce the suitability of ALTO for non-ISPs. The IP to ASN lookup services are proprietary and somewhat inaccurate. If ISPs can provide a standard, precise mechanism for determining which users are within their network, that would probably be better. Of course, for other ISPs p2p networks would continue to use the existing mechanisms, so this isn't a matter of doing something impossible, but more a matter of introducing a more precise, efficient mechanism to do what is done now. > > -- > Ciao, > Enrico > _______________________________________________ > p2pi mailing list > p2pi@ietf.org > https://www.ietf.org/mailman/listinfo/p2pi _______________________________________________ p2pi mailing list p2pi@ietf.org https://www.ietf.org/mailman/listinfo/p2pi
- [p2pi] After-BoF charter Enrico Marocco
- Re: [p2pi] After-BoF charter Lars Eggert
- Re: [p2pi] After-BoF charter John Leslie
- Re: [p2pi] After-BoF charter Laird Popkin
- Re: [p2pi] After-BoF charter David R Oran
- Re: [p2pi] After-BoF charter John Leslie
- Re: [p2pi] After-BoF charter David R Oran
- Re: [p2pi] After-BoF charter Bob Briscoe
- Re: [p2pi] After-BoF charter Bob Briscoe
- Re: [p2pi] After-BoF charter Bruce Davie
- Re: [p2pi] After-BoF charter Laird Popkin
- Re: [p2pi] After-BoF charter Woundy, Richard
- Re: [p2pi] After-BoF charter Stanislav Shalunov
- Re: [p2pi] After-BoF charter Bob Briscoe
- Re: [p2pi] After-BoF charter Laird Popkin
- Re: [p2pi] After-BoF charter Enrico Marocco
- Re: [p2pi] After-BoF charter Enrico Marocco
- Re: [p2pi] After-BoF charter Laird Popkin
- Re: [p2pi] Information in an ALTO protocol Vijay K. Gurbani
- Re: [p2pi] Information in an ALTO protocol John Leslie
- Re: [p2pi] Information in an ALTO protocol Laird Popkin
- Re: [p2pi] Information in an ALTO protocol Vijay K. Gurbani
- Re: [p2pi] Information in an ALTO protocol Yu-Shun Wang
- Re: [p2pi] Information in an ALTO protocol John Leslie
- Re: [p2pi] Information in an ALTO protocol Woundy, Richard
- Re: [p2pi] Information in an ALTO protocol John Leslie
- Re: [p2pi] After-BoF charter Bob Briscoe
- Re: [p2pi] After-BoF charter Bob Briscoe
- Re: [p2pi] After-BoF charter Vijay K. Gurbani
- Re: [p2pi] After-BoF charter Stanislav Shalunov
- Re: [p2pi] After-BoF charter Laird Popkin
- Re: [p2pi] Information in an ALTO protocol Woundy, Richard
- Re: [p2pi] Information in an ALTO protocol Woundy, Richard
- Re: [p2pi] Information in an ALTO protocol Reinaldo Penno
- Re: [p2pi] Information in an ALTO protocol Woundy, Richard