[alto] Questions on ALTO elements identified in the ALTO problem statement
Linda Dunbar <ldunbar@huawei.com> Mon, 06 July 2009 23:07 UTC
Return-Path: <ldunbar@huawei.com>
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 2A7953A6A37 for <alto@core3.amsl.com>; Mon, 6 Jul 2009 16:07:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.134
X-Spam-Level:
X-Spam-Status: No, score=-2.134 tagged_above=-999 required=5 tests=[AWL=0.465, 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 29habvtnpM0P for <alto@core3.amsl.com>; Mon, 6 Jul 2009 16:07:43 -0700 (PDT)
Received: from usaga02-in.huawei.com (usaga02-in.huawei.com [206.16.17.70]) by core3.amsl.com (Postfix) with ESMTP id 549013A6842 for <alto@ietf.org>; Mon, 6 Jul 2009 16:07:43 -0700 (PDT)
Received: from huawei.com (localhost [127.0.0.1]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KMD00ARVUUM78@usaga02-in.huawei.com> for alto@ietf.org; Mon, 06 Jul 2009 16:06:23 -0700 (PDT)
Received: from L735042 ([10.124.12.92]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KMD00B3VUUMQU@usaga02-in.huawei.com> for alto@ietf.org; Mon, 06 Jul 2009 16:06:22 -0700 (PDT)
Date: Mon, 06 Jul 2009 18:06:21 -0500
From: Linda Dunbar <ldunbar@huawei.com>
In-reply-to: <20090703150002.027D53A6DBB@core3.amsl.com>
To: alto@ietf.org
Message-id: <010101c9fe8e$610776a0$5c0c7c0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset="us-ascii"
Content-transfer-encoding: 7bit
Thread-index: Acn774tTd8zZX/OaRruyodUoAF9nIwCmx1bQ
References: <20090703150002.027D53A6DBB@core3.amsl.com>
Subject: [alto] Questions on ALTO elements identified in 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/mail-archive/web/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>
X-List-Received-Date: Mon, 06 Jul 2009 23:07:44 -0000
ALTO problem statement depicted architecture of the ALTO server and ALTO client. I find this "ALTO Server" is not very practical. For public servers which provide contents (like video streaming), they already registered at DHCP which provides ways for individual users to find the optimal route to the nearest server. For pure P2P applications, the duration of the applications is short and chance of them re-appearing is not high. Therefore it will be difficult for ALTO server to maintain all the needed information to achieve the optimization. Besides, what motivate P2P software to provide a hook to ALTO server? Linda Dunbar -----Original Message----- From: alto-bounces@ietf.org [mailto:alto-bounces@ietf.org] On Behalf Of Internet-Drafts@ietf.org Sent: Friday, July 03, 2009 10:00 AM To: i-d-announce@ietf.org Cc: alto@ietf.org Subject: [alto] I-D Action:draft-ietf-alto-problem-statement-02.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization Working Group of the IETF. Title : Application-Layer Traffic Optimization (ALTO) Problem Statement Author(s) : J. Seedorf, E. Burger Filename : draft-ietf-alto-problem-statement-02.txt Pages : 14 Date : 2009-07-03 Peer-to-peer applications, such as file sharing, real-time communication, and live and on-demand media streaming use a significant amount of Internet resources. Such applications often transfer large amounts of data in peer-to-peer connections. However, they usually have little knowledge of the underlying network topology. As a result, they may choose their peers randomly with respect to the underlying network topology or they may choose their peers based on measurements and statistics that, in many situations, may lead to suboptimal choices. This document describes problems related to improving traffic generated by peer-to-peer applications. In particular, this document discusses issues which better-than- random peer selection based on network-layer information may raise. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-alto-problem-statement-02.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft.
- [alto] Questions on ALTO elements identified in t… Linda Dunbar
- [alto] I-D Action:draft-ietf-alto-problem-stateme… Internet-Drafts
- Re: [alto] Questions on ALTO elements identified … Eric Burger