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

Enrico Marocco <enrico.marocco@telecomitalia.it> Sat, 11 October 2008 01:26 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 550953A6B02; Fri, 10 Oct 2008 18:26:47 -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 53DEA3A6A62; Fri, 10 Oct 2008 18:26:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.178
X-Spam-Level:
X-Spam-Status: No, score=-0.178 tagged_above=-999 required=5 tests=[AWL=0.541, 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 Qiwd2PY7vrNs; Fri, 10 Oct 2008 18:26:44 -0700 (PDT)
Received: from maile.telecomitalia.it (maile.telecomitalia.it [156.54.233.31]) by core3.amsl.com (Postfix) with ESMTP id 04F953A69C6; Fri, 10 Oct 2008 18:26:43 -0700 (PDT)
Received: from ptpxch008ba020.idc.cww.telecomitalia.it ([156.54.240.51]) by maile.telecomitalia.it with Microsoft SMTPSVC(6.0.3790.1830); Sat, 11 Oct 2008 03:27:29 +0200
Received: from ptpxch005ba020.idc.cww.telecomitalia.it ([156.54.240.44]) by ptpxch008ba020.idc.cww.telecomitalia.it with Microsoft SMTPSVC(6.0.3790.1830); Sat, 11 Oct 2008 03:27:29 +0200
Received: from [172.16.82.10] ([163.162.180.246]) by ptpxch005ba020.idc.cww.telecomitalia.it over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Sat, 11 Oct 2008 03:27:28 +0200
Message-ID: <48F000FD.5000302@telecomitalia.it>
Date: Sat, 11 Oct 2008 03:27:25 +0200
From: Enrico Marocco <enrico.marocco@telecomitalia.it>
User-Agent: Mozilla-Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
To: Lakshminath Dondeti <ldondeti@qualcomm.com>
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>
In-Reply-To: <48EFD2BC.8050706@qualcomm.com>
X-Enigmail-Version: 0.95.0
X-OriginalArrivalTime: 11 Oct 2008 01:27:28.0343 (UTC) FILETIME=[86095670:01C92B40]
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-Type: multipart/mixed; boundary="===============1884836521=="
Sender: p2pi-bounces@ietf.org
Errors-To: p2pi-bounces@ietf.org

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.

-- 
Ciao,
Enrico
_______________________________________________
p2pi mailing list
p2pi@ietf.org
https://www.ietf.org/mailman/listinfo/p2pi