Re: [p2pi] WG Review: Application-Layer Traffic Optimization (alto)

Philip Levis <pal@cs.stanford.edu> Fri, 10 October 2008 04:44 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 6CB7F3A6AA4; Thu, 9 Oct 2008 21:44:49 -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 C518C3A6843 for <p2pi@core3.amsl.com>; Thu, 9 Oct 2008 21:44:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 jU3-XXYfsSbY for <p2pi@core3.amsl.com>; Thu, 9 Oct 2008 21:44:48 -0700 (PDT)
Received: from cs-smtp-1.Stanford.EDU (cs-smtp-1.Stanford.EDU [171.64.64.25]) by core3.amsl.com (Postfix) with ESMTP id 0F51D3A69CD for <p2pi@ietf.org>; Thu, 9 Oct 2008 21:44:48 -0700 (PDT)
Received: from [76.14.71.180] (helo=[192.168.2.102]) by cs-smtp-1.Stanford.EDU with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.60) (envelope-from <pal@cs.stanford.edu>) id 1Ko9sP-00049s-VE; Thu, 09 Oct 2008 21:45:22 -0700
Message-Id: <E60AE53B-64BE-4ECE-94BE-B70164A3F0AD@cs.stanford.edu>
From: Philip Levis <pal@cs.stanford.edu>
To: Richard Barnes <rbarnes@bbn.com>
In-Reply-To: <48EEB19C.4000303@bbn.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 9 Oct 2008 21:45:21 -0700
References: <20081006203532.B1D673A68AF@core3.amsl.com> <BE82361A0E26874DBC2ED1BA244866B9276373BA@NALASEXMB08.na.qualcomm.com> <48EEB19C.4000303@bbn.com>
X-Mailer: Apple Mail (2.929.2)
X-Scan-Signature: 980022258218d8e0da9e8fd80fb6777b
Cc: p2pi@ietf.org
Subject: Re: [p2pi] WG Review: Application-Layer Traffic Optimization (alto)
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 Oct 9, 2008, at 6:36 PM, Richard Barnes wrote:

> On the contrary, I perceived pretty strong agreement at the BoF that  
> the ALTO problem, as expressed in the documents and presentations,  
> as an important one to solve.  There was some disagreement about  
> solutions, but there seemed to be agreement about the general idea  
> that it would be useful to create an ALTO service that could help  
> peers optimize their peer selection.
>
> The question of "service" versus "server" in the text is a complete  
> non-issue, purely a matter of wording.  In all of the "ALTO service"  
> scenarios Vidya describes, there is ultimately a single host that  
> provides ALTO information, which you might as well call an "ALTO  
> server".
>
> Since it addresses an important problem, and a problem that many  
> people agree is important, I support moving forward with this work.

I agree. This is such a pressing problem that blocking on terminology  
disputes which can be easily reconciled seems ill-advised. There was  
an excellent technical discussion on the list after the last IETF, and  
I think we reached at least rough consensus on the important points. I  
support moving forward.

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