Re: [p2pi] WG Review: Application-Layer Traffic Optimization (alto)
Enrico Marocco <enrico.marocco@telecomitalia.it> Sun, 19 October 2008 17:22 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 DF3C33A6805;
Sun, 19 Oct 2008 10:22: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 D70403A6805;
Sun, 19 Oct 2008 10:22:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.448
X-Spam-Level:
X-Spam-Status: No, score=-0.448 tagged_above=-999 required=5 tests=[AWL=0.271,
BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
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 v6rMhSRc67fc; Sun, 19 Oct 2008 10:22:27 -0700 (PDT)
Received: from maile.telecomitalia.it (maile.telecomitalia.it [156.54.233.31])
by core3.amsl.com (Postfix) with ESMTP id 8B4993A67B2;
Sun, 19 Oct 2008 10:22:26 -0700 (PDT)
Received: from ptpxch010ba020.idc.cww.telecomitalia.it ([156.54.240.53]) by
maile.telecomitalia.it with Microsoft SMTPSVC(6.0.3790.1830);
Sun, 19 Oct 2008 19:23:12 +0200
Received: from ptpxch004ba020.idc.cww.telecomitalia.it ([156.54.240.43]) by
ptpxch010ba020.idc.cww.telecomitalia.it with Microsoft
SMTPSVC(6.0.3790.1830); Sun, 19 Oct 2008 19:23:12 +0200
Received: from [172.16.82.10] ([163.162.180.246]) by
ptpxch004ba020.idc.cww.telecomitalia.it over TLS secured
channel with Microsoft SMTPSVC(6.0.3790.1830);
Sun, 19 Oct 2008 19:23:11 +0200
Message-ID: <48FB6CFD.1070505@telecomitalia.it>
Date: Sun, 19 Oct 2008 19:23:09 +0200
From: Enrico Marocco <enrico.marocco@telecomitalia.it>
User-Agent: Mozilla-Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
To: "Narayanan, Vidya" <vidyan@qualcomm.com>
References: <20081006203532.B1D673A68AF@core3.amsl.com><BE82361A0E26874DBC2ED1BA244866B9276373BA@NALASEXMB08.na.qualcomm.com><48EFA1B7.7010508@alcatel-lucent.com><BE82361A0E26874DBC2ED1BA244866B92763750C@NALASEXMB08.na.qualcomm.com><48F36E15.2000408@alcatel-lucent.com><BE82361A0E26874DBC2ED1BA244866B927637717@NALASEXMB08.na.qualcomm.com><48F60A4F.3010604@alcatel-lucent.com><ca722a9e0810151139q29705f8bm9e02ab5eb0dd27ec@mail.gmail.com> <BE82361A0E26874DBC2ED1BA244866B9276377F6@NALASEXMB08.na.qualcomm.com> <74CCBBDF76102846AFA7B29F3A98D3F6028962CF@PACDCEXCMB06.cable.comcast.com> <BE82361A0E26874DBC2ED1BA244866B92763795B@NALASEXMB08.na.qualcomm.com> <48F9044C.2050905@alcatel-lucent.com>
<BE82361A0E26874DBC2ED1BA244866B927637985@NALASEXMB08.na.qualcomm.com>
In-Reply-To: <BE82361A0E26874DBC2ED1BA244866B927637985@NALASEXMB08.na.qualcomm.com>
X-Enigmail-Version: 0.95.0
X-OriginalArrivalTime: 19 Oct 2008 17:23:11.0775 (UTC)
FILETIME=[5CB0AAF0:01C9320F]
Cc: "p2pi@ietf.org" <p2pi@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-Type: multipart/mixed; boundary="===============2035033653=="
Sender: p2pi-bounces@ietf.org
Errors-To: p2pi-bounces@ietf.org
Narayanan, Vidya wrote: >>> With respect to process, I think this one takes the cake among >>> abominations. Having been at the IETF long enough and having >>> participated in several BoFs, I'm quite familiar with RFC2418 and >>> the process. Here we have an effort that started with a >>> closed/gated workshop outside the IETF, >> Actually, this is not so. The workshop *was* sponsored by IETF; >> the RAI area, to be more precise (please see >> http://www.ietf.org/mail-archive/web/ietf-announce/current/msg >> 04758.html). > > My point is that this was a closed effort - it was not a meeting that > was open to all for attendence. The fact that the RAI ADs decided to > do this doesn't automatically make it "IETF sponsored". Not to > mention that the topics covered by this workshop or the scope of it > was not really open to discussion at the IETF. All of this makes it > sqauarely an effort outside the IETF and let's not try to pretend it > was somehow as open as other IETF efforts. This is simply not true. The P2PI workshop was open to all (including via jabber) and its main goal, as I read it, was to put together people interested in addressing the issues P2P traffic poses for Internet infrastructures. After that, two BOFs had been organized, in the very same way BOFs are usually organized: some people get together, draft a problem statement, set a mailing list up, add an entry in the BOF page, involve the community, discuss, ask a meeting slot during an official meeting, discuss, draft a charter, discuss, discuss... In a word, as described in draft-narten-successful-bof. Unfortunately it isn't possible to measure how much open an effort is, but if you accept the number of contributions and contributors (as per 3978) as a somewhat meaningful indicator, for ALTO you can count 561 messages posted on the list by 67 different authors (from 6/9, when the first BOF was announced, to 9/30, when LC began) and 6 I-Ds co-signed by 19 people (Authors and Contributors). Now, if you consider that no one of such contributors have complained about feeling excluded and instead all have agreed to move forward with the proposed charter (in fact they have contributed to the proposed charter), I wouldn't say that it has been a closed effort. -- Ciao, Enrico
_______________________________________________ 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… Pekka Savola
- Re: [p2pi] WG Review: Application-Layer Traffic O… Karl Auerbach
- 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