Re: [p2pi] WG Review: Application-Layer Traffic Optimization (alto)
Lakshminath Dondeti <ldondeti@qualcomm.com> Fri, 10 October 2008 15:09 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 BA62C28C163; Fri, 10 Oct 2008 08:09:59 -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 D0C4028C118; Fri, 10 Oct 2008 08:09:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.963
X-Spam-Level:
X-Spam-Status: No, score=-104.963 tagged_above=-999 required=5 tests=[AWL=1.636, 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 cAAfkHae1I6c; Fri, 10 Oct 2008 08:09:51 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by core3.amsl.com (Postfix) with ESMTP id B183928C163; Fri, 10 Oct 2008 08:09:51 -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=1223651438; x=1255187438; 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<48EF706C.9050508@qualcomm.com>|Date:=20Fr i,=2010=20Oct=202008=2008:10:36=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:=20Richard=20Barnes=20<rbarnes@bbn.com>,=20"p2pi@ ietf.org"=20<p2pi@ietf.org>,=0D=0A=20=20=20=20=20=20=20 =20"'iesg@ietf.org'"=20<iesg@ietf.org>,=20ietf@ietf.org |Subject:=20Re:=20[p2pi]=20WG=20Review:=20Application-Lay er=20Traffic=20Optimization=20(alto)|References:=20<20081 006203532.B1D673A68AF@core3.amsl.com>=09<BE82361A0E26874D BC2ED1BA244866B9276373BA@NALASEXMB08.na.qualcomm.com>=09< 48EEB19C.4000303@bbn.com>=20<48EEE549.1080208@qualcomm.co m>=20<48EF477E.4080708@telecomitalia.it>|In-Reply-To:=20< 48EF477E.4080708@telecomitalia.it>|Content-Type:=20text/p lain=3B=20charset=3DISO-8859-15=3B=20format=3Dflowed |Content-Transfer-Encoding:=207bit|X-IronPort-AV:=20E=3DM cAfee=3Bi=3D"5300,2777,5402"=3B=20a=3D"10589960"; bh=nHQ4ocCjG2vQzXOM2k/yxH6OIzd48vQSBYPnbCiagis=; b=iscgiaQv/8MwjShKjun9Kh9rA8TMk+NEION83OHTrP3vKLJ7K/ANj3kW EUl9pnDSuhLaT2pLXnpfu6xH66/r7DCsYSVcA72K7PtyGvjCxb4bqCuuN LavPNAFlV2A8blNf5AV8Ci2AEMG2mnDlDrMVHkEKFYdtjfL/C05oDJeNN A=;
X-IronPort-AV: E=McAfee;i="5300,2777,5402"; a="10589960"
Received: from pdmz-ns-mip.qualcomm.com (HELO numenor.qualcomm.com) ([199.106.114.10]) by wolverine01.qualcomm.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 10 Oct 2008 08:10:38 -0700
Received: from msgtransport02.qualcomm.com (msgtransport02.qualcomm.com [129.46.61.151]) by numenor.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id m9AFAbkp029675 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 10 Oct 2008 08:10:38 -0700
Received: from [10.50.68.73] (qconnect-10-50-68-73.qualcomm.com [10.50.68.73]) by msgtransport02.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id m9AFAbRs011403 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 10 Oct 2008 08:10:37 -0700
Message-ID: <48EF706C.9050508@qualcomm.com>
Date: Fri, 10 Oct 2008 08:10:36 -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>
In-Reply-To: <48EF477E.4080708@telecomitalia.it>
Cc: Richard Barnes <rbarnes@bbn.com>, "p2pi@ietf.org" <p2pi@ietf.org>, "'iesg@ietf.org'" <iesg@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
Hi Enrico, Vijay, Thank you for the summary of what transpired after the Dublin meeting. I appreciate you taking the time. My reading at the BoF was that there were some concerns about this work being done in haste without clearly understanding what it is that we want to do and what it is that we need to do to address this particular problem space (there were even suggestions to move some of the work to the IRTF). My perception and my understanding of some of the dissenting opinions was that some of those need to be worked out before creating a working group. We have been in situations where working groups have been created in haste to address important and urgent problems, but then people disagree so much in working groups that some such working groups never made any real progress or had to be shut down (folks, please don't try to guess which WG(s) and try to explain the individual situations; thanks). Surely, we don't want that to happen here. Some of the disagreements here in this thread now, and the intent of some of the folks to whitewash the issues raised do seem troublesome. It would be great if we could rather focus on trying to understand all aspects of the problem, have the charter reflect the correct level of scope (too wide or too narrow are problematic as we know), and move forward. thanks, Lakshminath On 10/10/2008 5:15 AM, Enrico Marocco wrote: > Lakshminath Dondeti wrote: >> The minutes (http://www.ietf.org/proceedings/08jul/minutes/alto.txt) say >> this: >> >> +++++++++++++++ >> Many people agreed that this is important work for the IETF, also some >> (less) people hummed against. Hum was inconclusive - some of the "no" >> hums were (in Jon's words) vehement. >> +++++++++++++++ >> >> Given that there was no consensus, it would have been nice if the >> sponsoring AD(s) or the IESG explained what's going on, but then >> transparency, it appears, is not really a goal in this case. If the >> idea was to just go forward anyway, we really wasted 3, may be 6 months. >> The half measures are a waste of everyone's time. > > Lakshminath, the objections raised during the BoF in Dublin were on very > specific issues, namely the "general service discovery problem" > supposedly addressed by the charter, a too broad scope in terms of > information exchanged between ALTO clients and ALTO servers, and the > connection between traffic localization and optimization someone seemed > to see implied in the problem statement. During the weeks following the > meeting, people who had expressed concerns at the mic and on the list > constructively contributed to the discussion and the group converged on > a charter the current version is a slight variant of. For this reason, > and for the amount of interest shown in Dublin -- we called > inconclusive the hum on the charter, but interest in the problem was > made pretty clear by what we heard at the mic, by the number of > contributors, and by the number of people in the room -- we managed to > convince our sponsoring AD (and transitively the IESG) to send it out > for IETF-wide review. If the community identifies new serious issues or > considers the old ones not completely addressed, probably a new BoF will > be the best way to sort them out. > > Of course I'm only speaking for myself, not certainly on behalf of Lisa > nor the IESG. > _______________________________________________ p2pi mailing list p2pi@ietf.org https://www.ietf.org/mailman/listinfo/p2pi
- Re: [p2pi] WG Review: Application-Layer Traffic O… Narayanan, Vidya
- [p2pi] WG Review: Application-Layer Traffic Optim… IESG Secretary
- Re: [p2pi] WG Review: Application-Layer Traffic O… Sam Hartman
- Re: [p2pi] WG Review: Application-Layer Traffic O… Richard Barnes
- Re: [p2pi] WG Review: Application-Layer Traffic O… Daniel Park
- Re: [p2pi] WG Review: Application-Layer Traffic O… Philip Levis
- Re: [p2pi] WG Review: Application-Layer Traffic O… Lakshminath Dondeti
- Re: [p2pi] WG Review: Application-Layer Traffic O… Narayanan, Vidya
- Re: [p2pi] WG Review: Application-Layer Traffic O… stefano previdi
- Re: [p2pi] WG Review: Application-Layer Traffic O… stefano previdi
- Re: [p2pi] WG Review: Application-Layer Traffic O… Marshall Eubanks
- Re: [p2pi] WG Review: Application-Layer Traffic O… Marshall Eubanks
- Re: [p2pi] WG Review: Application-Layer Traffic O… Enrico Marocco
- Re: [p2pi] WG Review: Application-Layer Traffic O… Bruce Davie
- Re: [p2pi] WG Review: Application-Layer Traffic O… Vijay K. Gurbani
- Re: [p2pi] WG Review: Application-Layer Traffic O… Lakshminath Dondeti
- Re: [p2pi] WG Review: Application-Layer Traffic O… Vijay K. Gurbani
- Re: [p2pi] WG Review: Application-Layer Traffic O… Vijay K. Gurbani
- Re: [p2pi] WG Review: Application-Layer Traffic O… Lisa Dusseault
- Re: [p2pi] WG Review: Application-Layer Traffic O… Laird Popkin
- Re: [p2pi] WG Review: Application-Layer Traffic O… Alissa Cooper
- Re: [p2pi] WG Review: Application-Layer Traffic O… Narayanan, Vidya
- Re: [p2pi] WG Review: Application-Layer Traffic O… Narayanan, Vidya
- Re: [p2pi] WG Review: Application-Layer Traffic O… Vijay K. Gurbani
- Re: [p2pi] WG Review: Application-Layer Traffic O… Marshall Eubanks
- Re: [p2pi] WG Review: Application-Layer Traffic O… Lakshminath Dondeti
- Re: [p2pi] WG Review: Application-Layer Traffic O… Enrico Marocco
- Re: [p2pi] WG Review: Application-Layer Traffic O… Lakshminath Dondeti
- Re: [p2pi] WG Review: Application-Layer Traffic O… Narayanan, Vidya
- Re: [p2pi] WG Review: Application-Layer Traffic O… Martin Stiemerling
- Re: [p2pi] WG Review: Application-Layer Traffic O… Jan Seedorf
- Re: [p2pi] WG Review: Application-Layer Traffic O… Jan Seedorf
- Re: [p2pi] WG Review: Application-Layer Traffic O… Vijay K. Gurbani
- Re: [p2pi] WG Review: Application-Layer Traffic O… Song Haibin
- Re: [p2pi] WG Review: Application-Layer Traffic O… Lars Eggert
- Re: [p2pi] WG Review: Application-Layer Traffic O… Lars Eggert
- Re: [p2pi] WG Review: Application-Layer Traffic O… Laird Popkin
- Re: [p2pi] WG Review: Application-Layer Traffic O… Nicholas Weaver
- Re: [p2pi] WG Review: Application-Layer Traffic O… Ye WANG
- Re: [p2pi] WG Review: Application-Layer Traffic O… Philip Levis
- Re: [p2pi] WG Review: Application-Layer Traffic O… Narayanan, Vidya
- Re: [p2pi] WG Review: Application-Layer Traffic O… Song Haibin
- Re: [p2pi] WG Review: Application-Layer Traffic O… Narayanan, Vidya
- Re: [p2pi] WG Review: Application-Layer Traffic O… Vijay K. Gurbani
- Re: [p2pi] WG Review: Application-Layer Traffic O… Lisa Dusseault
- Re: [p2pi] WG Review: Application-Layer Traffic O… Laird Popkin
- Re: [p2pi] WG Review: Application-Layer Traffic O… Narayanan, Vidya
- Re: [p2pi] WG Review: Application-Layer Traffic O… Das, Saumitra
- Re: [p2pi] WG Review: Application-Layer Traffic O… Woundy, Richard
- Re: [p2pi] WG Review: Application-Layer Traffic O… Narayanan, Vidya
- Re: [p2pi] WG Review: Application-Layer Traffic O… Vijay K. Gurbani
- Re: [p2pi] WG Review: Application-Layer Traffic O… Narayanan, Vidya
- Re: [p2pi] WG Review: Application-Layer Traffic O… Enrico Marocco
- Re: [p2pi] WG Review: Application-Layer Traffic O… toby.moncaster
- Re: [p2pi] WG Review: Application-Layer Traffic O… Laird Popkin
- Re: [p2pi] WG Review: Application-Layer Traffic O… Karl Auerbach
- Re: [p2pi] WG Review: Application-Layer Traffic O… Pekka Savola
- Re: [p2pi] WG Review: Application-Layer Traffic O… Nicholas Weaver
- Re: [p2pi] WG Review: Application-Layer Traffic O… Vijay K. Gurbani
- Re: [p2pi] WG Review: Application-Layer Traffic O… Nicholas Weaver
- Re: [p2pi] WG Review: Application-Layer Traffic O… Das, Saumitra
- Re: [p2pi] WG Review: Application-Layer Traffic O… Stanislav Shalunov
- Re: [p2pi] WG Review: Application-Layer Traffic O… Michael J. Freedman
- Re: [p2pi] WG Review: Application-Layer Traffic O… Dean Anderson
- Re: [p2pi] WG Review: Application-Layer Traffic O… Narayanan, Vidya
- Re: [p2pi] WG Review: Application-Layer Traffic O… Yu-Shun Wang
- Re: [p2pi] WG Review: Application-Layer Traffic O… Woundy, Richard
- Re: [p2pi] WG Review: Application-Layer Traffic O… Nicholas Weaver
- Re: [p2pi] WG Review: Application-Layer Traffic O… Woundy, Richard
- Re: [p2pi] WG Review: Application-Layer Traffic O… Narayanan, Vidya
- Re: [p2pi] WG Review: Application-Layer Traffic O… Yu-Shun Wang