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

Lakshminath Dondeti <ldondeti@qualcomm.com> Sat, 11 October 2008 04:58 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 839EF28C15F; Fri, 10 Oct 2008 21:58:28 -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 2664D3A6834; Fri, 10 Oct 2008 21:58:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.214
X-Spam-Level:
X-Spam-Status: No, score=-105.214 tagged_above=-999 required=5 tests=[AWL=1.385, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 oDcvAFjBrOJz; Fri, 10 Oct 2008 21:58:19 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by core3.amsl.com (Postfix) with ESMTP id CAF5A3A67F8; Fri, 10 Oct 2008 21:58:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=ldondeti@qualcomm.com; q=dns/txt; s=qcdkim; t=1223701147; x=1255237147; h=message-id:date:from:user-agent:mime-version:to:cc: subject:references:in-reply-to:content-type: content-transfer-encoding:x-ironport-av; z=Message-ID:=20<48F03281.2030900@qualcomm.com>|Date:=20Fr i,=2010=20Oct=202008=2021:58:41=20-0700|From:=20Lakshmina th=20Dondeti=20<ldondeti@qualcomm.com>|User-Agent:=20Thun derbird=202.0.0.17=20(Windows/20080914)|MIME-Version:=201 .0|To:=20Enrico=20Marocco=20<enrico.marocco@telecomitalia .it>|CC:=20Lisa=20Dusseault=20<lisa.dusseault@gmail.com>, =20"p2pi@ietf.org"=20<p2pi@ietf.org>,=0D=0A=20=20=20=20 =20=20=20=20IESG=20IESG=20<iesg@ietf.org>,=20"ietf@ietf.o rg"=20<ietf@ietf.org>|Subject:=20Re:=20[p2pi]=20WG=20Revi ew:=20Application-Layer=20Traffic=20Optimization=20(alto) |References:=20<20081006203532.B1D673A68AF@core3.amsl.com >=09=09<BE82361A0E26874DBC2ED1BA244866B9276373BA@NALASEXM B08.na.qualcomm.com>=09=09<48EEB19C.4000303@bbn.com>=20<4 8EEE549.1080208@qualcomm.com>=09=09<48EF477E.4080708@tele comitalia.it>=09<48EF706C.9050508@qualcomm.com>=09=09<48E FA0BE.1040809@alcatel-lucent.com>=09<ca722a9e0810101221yb 84ac3ar8ff0f267718c88c9@mail.gmail.com>=20<48EFD2BC.80507 06@qualcomm.com>=20<48F000FD.5000302@telecomitalia.it> |In-Reply-To:=20<48F000FD.5000302@telecomitalia.it> |Content-Type:=20text/plain=3B=20charset=3DISO-8859-15=3B =20format=3Dflowed|Content-Transfer-Encoding:=207bit |X-IronPort-AV:=20E=3DMcAfee=3Bi=3D"5300,2777,5403"=3B=20 a=3D"10664391"; bh=WcRQAHLK7Et0KPrpczIVje3bJ8uT1Q56olBtoru816c=; b=rgiu0euxLS1fsn1WDO2ph4kSpcG1nLjQiH9W9SiZ/0x41WFarBeiG+Og uUKajI/g7SljFNHKWgqeO0ctgFI3I2mdGahFAZSh0kKhNywMtLYguFT0d llCh12BX2Trpke/R9C4Mzk8+KkGkHiht6Z7b6d3sPw1bJ+7tXYcr4UUPy c=;
X-IronPort-AV: E=McAfee;i="5300,2777,5403"; a="10664391"
Received: from pdmz-ns-mip.qualcomm.com (HELO ithilien.qualcomm.com) ([199.106.114.10]) by wolverine01.qualcomm.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 10 Oct 2008 21:58:53 -0700
Received: from totoro.qualcomm.com (totoro.qualcomm.com [129.46.61.158]) by ithilien.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id m9B4wqKq019410 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 10 Oct 2008 21:58:52 -0700
Received: from [10.50.69.64] (qconnect-10-50-69-64.qualcomm.com [10.50.69.64]) by totoro.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id m9B4wodc003938 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 10 Oct 2008 21:58:51 -0700 (PDT)
Message-ID: <48F03281.2030900@qualcomm.com>
Date: Fri, 10 Oct 2008 21:58:41 -0700
From: Lakshminath Dondeti <ldondeti@qualcomm.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Enrico Marocco <enrico.marocco@telecomitalia.it>
References: <20081006203532.B1D673A68AF@core3.amsl.com> <BE82361A0E26874DBC2ED1BA244866B9276373BA@NALASEXMB08.na.qualcomm.com> <48EEB19C.4000303@bbn.com> <48EEE549.1080208@qualcomm.com> <48EF477E.4080708@telecomitalia.it> <48EF706C.9050508@qualcomm.com> <48EFA0BE.1040809@alcatel-lucent.com> <ca722a9e0810101221yb84ac3ar8ff0f267718c88c9@mail.gmail.com> <48EFD2BC.8050706@qualcomm.com> <48F000FD.5000302@telecomitalia.it>
In-Reply-To: <48F000FD.5000302@telecomitalia.it>
Cc: "p2pi@ietf.org" <p2pi@ietf.org>, IESG IESG <iesg@ietf.org>, "ietf@ietf.org" <ietf@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"
Sender: p2pi-bounces@ietf.org
Errors-To: p2pi-bounces@ietf.org

Thanks for the clarification Enrico :).

best,
Lakshminath

On 10/10/2008 6:27 PM, Enrico Marocco wrote:
> Lakshminath Dondeti wrote:
>>> It's difficult to write a charter without actually designing the
>>> solution.
>> This is an interesting opinion.  May I translate that to mean that there
>> is already a solution in the minds of the people who wrote the charter?
> 
> Nope. Who has been following the p2pi list for the last five months
> probably knows that there are three different approaches (solutions?)
> floating around: the "sorting oracle" (described in a SIGCOMM paper
> authored by folks from TU-Berlin, a variant of which is IDIPS), P4P
> (soon to be published as I-D and, IIRC, described in another SIGCOMM
> paper), and Stanislav's proposal (discussed in Dublin and on the list:
> http://www.ietf.org/mail-archive/web/p2pi/current/msg00508.html). Who
> wrote the charter had all those approaches clear in mind and took
> special care that none of them got ruled out.
> 
>> Why then would we bother with the proposed requirements effort, writing
>> down a problem statement and all the rest?  Why not put an RFC number on
>> the solution?
>>
>> It also makes me wonder what your opinion on the following from 2418.
>>
>> " - Is the proposed work plan an open IETF effort or is it an attempt
>>        to "bless" non-IETF technology where the effect of input from IETF
>>        participants may be limited?"
> 
> I don't know Lisa's opinion, but am sure that this is not the case here.
> 
_______________________________________________
p2pi mailing list
p2pi@ietf.org
https://www.ietf.org/mailman/listinfo/p2pi