Re: [p2pi] discussing P2PI-related standardization in Dublin
Richard Bennett <richard@bennett.com> Sat, 14 June 2008 00:16 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 1F8A73A69F7; Fri, 13 Jun 2008 17:16:06 -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 8B3913A6A3B for <p2pi@core3.amsl.com>; Fri, 13 Jun 2008 17:16:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.457
X-Spam-Level:
X-Spam-Status: No, score=-1.457 tagged_above=-999 required=5 tests=[AWL=-0.485, BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, MISSING_HEADERS=1.292]
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 G2R+Ew3VLXvl for <p2pi@core3.amsl.com>; Fri, 13 Jun 2008 17:16:03 -0700 (PDT)
Received: from outbound-mail-146.bluehost.com (outbound-mail-146.bluehost.com [67.222.38.36]) by core3.amsl.com (Postfix) with SMTP id 35B563A69F7 for <p2pi@ietf.org>; Fri, 13 Jun 2008 17:16:03 -0700 (PDT)
Received: (qmail 14353 invoked by uid 0); 14 Jun 2008 00:16:34 -0000
Received: from unknown (HELO host46.hostmonster.com) (74.220.202.46) by outboundproxy5.bluehost.com with SMTP; 14 Jun 2008 00:16:34 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=bennett.com; h=Received:Message-ID:Date:From:Organization:User-Agent:MIME-Version:CC:Subject:References:In-Reply-To:Content-Type:X-Identified-User:DomainKey-Status; b=JWkPrjZ3vhXWtLMzVxYyAdT+wjiIQopkthTSH9a6fuqvzfT44o3GKHPp0Y+YmiZZygRASq7CW8MT6GJ8rUt1cLATwqw3SOsbXOz/BTmErCGU+0it+XrhmOzK0IpJSNsM;
Received: from adsl-69-106-235-168.dsl.pltn13.pacbell.net ([69.106.235.168] helo=[192.168.1.2]) by host46.hostmonster.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from <richard@bennett.com>) id 1K7JRa-0000dX-88; Fri, 13 Jun 2008 18:16:34 -0600
Message-ID: <48530DDB.9020707@bennett.com>
Date: Fri, 13 Jun 2008 17:16:27 -0700
From: Richard Bennett <richard@bennett.com>
Organization: Network Strategies
User-Agent: Thunderbird 2.0.0.14 (X11/20080501)
MIME-Version: 1.0
References: <22F6A875-B548-4C65-AB68-B88E526CCA33@nokia.com> <6E1603B0-7116-45F9-A510-DC5F9040298B@nokia.com> <14F37DBB-BCF0-43C9-90D0-A8B7D4A9FD36@nokia.com>
In-Reply-To: <14F37DBB-BCF0-43C9-90D0-A8B7D4A9FD36@nokia.com>
X-Identified-User: {842:host46.hostmonster.com:bennett1:bennett.com} {sentby:smtp auth 69.106.235.168 authed with richard@bennett.com}
DomainKey-Status: no signature
Cc: P2PSIP Mailing List <p2psip@ietf.org>, p2pi@ietf.org, "iab@iab.org IAB" <iab@iab.org>, TSV Area <tsv-area@ietf.org>, "IESG ((E-mail))" <iesg@ietf.org>, p2prg@irtf.org
Subject: Re: [p2pi] discussing P2PI-related standardization in Dublin
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="===============0335405322=="
Sender: p2pi-bounces@ietf.org
Errors-To: p2pi-bounces@ietf.org
Do we have a date for the proposed BOF in Dublin? RB Lars Eggert wrote: > Hi, > > On 2008-6-6, at 17:40, ext Lars Eggert wrote: > >> related to the work item below, I've just heard that some folks had >> already been discussing the submission of a more targeted BOF >> proposal. Depending on the details of that proposal (which I haven't >> seen yet), work item (3) might be subsumed by it. >> > > this BOF proposal has now materialized in form of ALTO (http://alto.tilab.com/ > ), a BOF proposal targeted at APP and RAI. > > It's hence somewhat likely that we may have a TANA BOF in TSV that > focuses on the work items (1) and (2) from my original email, and a > second ALTO BOF hosted by APP and RAI. > > (Note: this email is *not* an IESG approval of either the TANA or ALTO > BOF - those will come from the responsible ADs if and when they come.) > > ALTO is currently scoped a bit more broadly than the TANA work item > (3) was, and some of the broader proposals in the ALTO space could > lead to significant transport issues. A fraction of the ALTO > proponents argues to exchange information related to end-to-end > performance (bandwidth, RTT, congestion, transfer time estimates, > etc.) through the oracle, for example. > > I'd like to ask transport folks to participate in the discussion on > ALTO on the p2pi@ietf.org mailing list, in order to discuss the > transport implications of the various ALTO ideas. > > >> On 2008-6-6, at 15:58, Lars Eggert wrote: >> >>> (3) A mechanism that lets an application that can >>> transfer data from or to several potential peers (i.e., >>> servers, caches, end systems) select a subset of peers >>> for efficient transmission in a way that is aligned with >>> the dynamic interconnection structure of the network >>> operators that provide connectivity to those peers. >>> Application designers, network equipment vendors and >>> network operators will need to collaborate on this work >>> item to define what kinds of dynamic interconnection >>> information is useful to applications, how to obtain it, >>> and how to provide it to applications, resulting in a >>> generic mechanism that is broadly applicable to many >>> current and future applications. This work item has >>> obvious interactions with the IETF's Application, Routing >>> and Operations areas. In order to make this effort more >>> manageable, it may make sense to work out the >>> requirements for such a solution first, before discussing >>> individual proposals or breaking up the work into pieces >>> for specification in different areas or WGs. >>> > > Lars > _______________________________________________ > p2pi mailing list > p2pi@ietf.org > https://www.ietf.org/mailman/listinfo/p2pi > -- Richard Bennett
_______________________________________________ p2pi mailing list p2pi@ietf.org https://www.ietf.org/mailman/listinfo/p2pi
- [p2pi] discussing P2PI-related standardization in… Lars Eggert
- Re: [p2pi] discussing P2PI-related standardizatio… Lars Eggert
- Re: [p2pi] discussing P2PI-related standardizatio… Vijay K. Gurbani
- Re: [p2pi] discussing P2PI-related standardizatio… Peterson, Jon
- Re: [p2pi] discussing P2PI-related standardizatio… Livingood, Jason
- [p2pi] Refining the ALTO problem statement [Was: … Enrico Marocco
- Re: [p2pi] Refining the ALTO problem statement [W… stefano previdi
- Re: [p2pi] Refining the ALTO problem statement [W… John Leslie
- Re: [p2pi] Refining the ALTO problem statement [W… Vijay K. Gurbani
- Re: [p2pi] Refining the ALTO problem statement [W… Lars Eggert
- Re: [p2pi] Refining the ALTO problem statement [W… Lars Eggert
- Re: [p2pi] discussing P2PI-related standardizatio… Lars Eggert
- Re: [p2pi] Refining the ALTO problem statement [W… Enrico Marocco
- Re: [p2pi] Refining the ALTO problem statement John Leslie
- Re: [p2pi] discussing P2PI-related standardizatio… Richard Bennett
- Re: [p2pi] discussing P2PI-related standardizatio… Lars Eggert
- Re: [p2pi] Refining the ALTO problem statement [W… Lars Eggert
- Re: [p2pi] Refining the ALTO problem statement Lars Eggert
- Re: [p2pi] Refining the ALTO problem statement [W… stefano previdi
- Re: [p2pi] Refining the ALTO problem statement Spencer Dawkins
- Re: [p2pi] Refining the ALTO problem statement John Leslie
- Re: [p2pi] Refining the ALTO problem statement John Leslie
- Re: [p2pi] Refining the ALTO problem statement Spencer Dawkins
- Re: [p2pi] Refining the ALTO problem statement [W… Henning Schulzrinne
- Re: [p2pi] Refining the ALTO problem statement [W… Stanislav Shalunov
- Re: [p2pi] Refining the ALTO problem statement [W… Lars Eggert
- Re: [p2pi] Refining the ALTO problem statement Lars Eggert
- Re: [p2pi] Refining the ALTO problem statement Spencer Dawkins
- Re: [p2pi] Refining the ALTO problem statement John Leslie
- Re: [p2pi] Refining the ALTO problem statement Robert Snively
- Re: [p2pi] Refining the ALTO problem statement Stanislav Shalunov
- Re: [p2pi] Refining the ALTO problem statement Laird Popkin
- Re: [p2pi] Refining the ALTO problem statement stefano previdi
- Re: [p2pi] Refining the ALTO problem statement Stanislav Shalunov
- Re: [p2pi] Refining the ALTO problem statement Lars Eggert