[alto] Problems with the Alto problem statement

Paul Hoffman <paul.hoffman@vpnc.org> Fri, 14 November 2008 21:48 UTC

Return-Path: <alto-bounces@ietf.org>
X-Original-To: alto-archive@ietf.org
Delivered-To: ietfarch-alto-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 112A928C103; Fri, 14 Nov 2008 13:48:16 -0800 (PST)
X-Original-To: alto@core3.amsl.com
Delivered-To: alto@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2E8EF28C103 for <alto@core3.amsl.com>; Fri, 14 Nov 2008 13:48:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 qhks2MZ36ZRH for <alto@core3.amsl.com>; Fri, 14 Nov 2008 13:48:14 -0800 (PST)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id 0A6B528C0D8 for <alto@ietf.org>; Fri, 14 Nov 2008 13:48:13 -0800 (PST)
Received: from [10.20.30.152] (dsl-63-249-108-169.cruzio.com [63.249.108.169]) (authenticated bits=0) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id mAELmBQn012213 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <alto@ietf.org>; Fri, 14 Nov 2008 14:48:12 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p0624080bc5439cab91b5@[10.20.30.152]>
Date: Fri, 14 Nov 2008 13:47:36 -0800
To: alto@ietf.org
From: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: [alto] Problems with the Alto problem statement
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: alto-bounces@ietf.org
Errors-To: alto-bounces@ietf.org

Greetings. draft-marocco-alto-problem-statement-03 mixes two types of problem statements in a way that might confuse some readers. It covers both:

A: the problem of the large amount of P2P traffic seen on the current Internet

B: the problem of how to provide useful network information to applications

The proposed solution space for Alto will probably do nearly nothing for Problem A. Most BitTorrent traffic, which is often said to account for nearly 50% of all ISP traffic, comes from communities that would get no advantage from any of the proposed Alto solutions.

Most of the large BitTorrent communities *want* more users who are further away topologically from well-connected users, or have slower connectivity, so that the community grows. In exchange for slightly lower speed, those communities get much more stability by having torrents seeded for a longer time and more people who are willing to seed "long tail" material.

Further, any Alto solution that involves an application telling a server specific files that it is interested in, or even asking which of a list of other users would be best to communicate with, will only be useful if the user of that application is willing to directly reveal to his/her ISP what they are asking for or who they want to share with. For legitimate content, that is probably not so much of an issue. For content whose legality is questionable, it is a huge issue.

In short, an Alto might work for some scenarios, but it is pretty much irrelevant for the scenario that concerns many people now, which is the huge and growing amount of BitTorrent traffic on the net today. Therefore, any discussion of current problems with this BitTorrent traffic should be removed from the problem statements draft. Otherwise, someone reading it as part of the suite of Alto specification might think that Alto will be useful for this problem. The problems Alto might be useful for are quite different than what we have today.

--Paul Hoffman, Director
--VPN Consortium
_______________________________________________
alto mailing list
alto@ietf.org
https://www.ietf.org/mailman/listinfo/alto