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

Marshall Eubanks <tme@multicasttech.com> Fri, 10 October 2008 10:12 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 B89B428C197; Fri, 10 Oct 2008 03:12:22 -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 1025728C18B for <p2pi@core3.amsl.com>; Fri, 10 Oct 2008 03:12:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.195
X-Spam-Level:
X-Spam-Status: No, score=-103.195 tagged_above=-999 required=5 tests=[AWL=0.404, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 h+RTVjIyyhXP for <p2pi@core3.amsl.com>; Fri, 10 Oct 2008 03:12:21 -0700 (PDT)
Received: from multicasttech.com (lennon.multicasttech.com [63.105.122.7]) by core3.amsl.com (Postfix) with ESMTP id 416DB28C110 for <p2pi@ietf.org>; Fri, 10 Oct 2008 03:12:21 -0700 (PDT)
Received: from [63.105.122.7] (account marshall_eubanks HELO [IPv6:::1]) by multicasttech.com (CommuniGate Pro SMTP 3.4.8) with ESMTP-TLS id 13322670; Fri, 10 Oct 2008 06:12:47 -0400
Message-Id: <44965FC0-69E9-4DED-8925-45DB6B7429F7@multicasttech.com>
From: Marshall Eubanks <tme@multicasttech.com>
To: Philip Levis <pal@cs.stanford.edu>
In-Reply-To: <E60AE53B-64BE-4ECE-94BE-B70164A3F0AD@cs.stanford.edu>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 10 Oct 2008 06:12:46 -0400
References: <20081006203532.B1D673A68AF@core3.amsl.com> <BE82361A0E26874DBC2ED1BA244866B9276373BA@NALASEXMB08.na.qualcomm.com> <48EEB19C.4000303@bbn.com> <E60AE53B-64BE-4ECE-94BE-B70164A3F0AD@cs.stanford.edu>
X-Mailer: Apple Mail (2.929.2)
Cc: Richard Barnes <rbarnes@bbn.com>, 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 10, 2008, at 12:45 AM, Philip Levis wrote:

>
> 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.
>

I agree with this interpretation and also support moving this forward  
into a WG.

Regards
Marshall



> Phil
> _______________________________________________
> 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