Re: [p2pi] discussing P2PI-related standardization in Dublin
"Peterson, Jon" <jon.peterson@neustar.biz> Mon, 09 June 2008 20:40 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 50F853A682B; Mon, 9 Jun 2008 13:40:24 -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 34A1F3A6825; Mon, 9 Jun 2008 13:40:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.042
X-Spam-Level:
X-Spam-Status: No, score=-2.042 tagged_above=-999 required=5 tests=[AWL=0.558, BAYES_00=-2.599]
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 hDrrjVJQcOJt; Mon, 9 Jun 2008 13:40:20 -0700 (PDT)
Received: from neustar.com (ns6.neustar.com [156.154.16.88]) by core3.amsl.com (Postfix) with ESMTP id 170633A69A7; Mon, 9 Jun 2008 13:40:08 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; d=neustar.biz; s=neustarbiz; c=simple/simple; q=dns; t=1213044025; x=1213130425; h=From:Date:Subject:Message-ID:Content-class:Content-Type:Content-Transfer-Encod ing; b=dwJdtCD7x5eUJxKhjhn/Y6XcQI/GknfglX1+ReXMjdEcsCwS41wZl92FRGTw85A8AVaEqhp5FnqLiw aOrylcMw==
Received: from ([10.31.13.50]) by stihiron2.va.neustar.com with ESMTP id 5202732.8481427; Mon, 09 Jun 2008 16:40:09 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 09 Jun 2008 16:40:07 -0400
Message-ID: <C80ADC57CB3BB64B94A9954A816306C50C323F@STNTEXCH11.cis.neustar.com>
In-Reply-To: <6E1603B0-7116-45F9-A510-DC5F9040298B@nokia.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: discussing P2PI-related standardization in Dublin
thread-index: AcjH43bffDGFH0n+Rgau+bxH0sE75ACi40yQ
References: <22F6A875-B548-4C65-AB68-B88E526CCA33@nokia.com> <6E1603B0-7116-45F9-A510-DC5F9040298B@nokia.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: TSV Area <tsv-area@ietf.org>
Cc: p2pi@ietf.org, iab@iab.org, p2prg@irtf.org, "IESG ((E-mail))" <iesg@ietf.org>, P2PSIP Mailing List <p2psip@ietf.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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: p2pi-bounces@ietf.org
Errors-To: p2pi-bounces@ietf.org
The proposal for the ALTO BoF (which roughly covers (3)) is now in the BoF tracker. You can read about it at its home page: http://alto.tilab.com/ ALTO proposes to explore a slightly broader space than merely P2P file-sharing applications, since discovery of nearby peers has equal applicability to many real-time communications protocols (for example, the discovery of a TURN server to assist the establishment of a VoIP session). Although RAI proposes to sponsor a BoF on this subject, we're not yet persuaded that RAI would be the optimal home for any ongoing work efforts related to this space - we hope that discussions surrounding the BoF could elucidate the proper division of labor and approach to this problem. I do believe this work effort is sufficiently distinct from the transport issues discussed in (1) and (2) of Lars' original mail to merit a separate effort. I do, however, whole-heartedly support TSV taking on (1) and (2) in a forum like TANA. Jon Peterson NeuStar, Inc. -----Original Message----- From: iesg-bounces@iesg.org [mailto:iesg-bounces@iesg.org] On Behalf Of Lars Eggert Sent: Friday, June 06, 2008 7:41 AM To: TSV Area Cc: p2prg@irtf.org; iab@iab.org IAB; p2pi@ietf.org; IESG ((E-mail)); P2PSIP Mailing List Subject: Re: discussing P2PI-related standardization in Dublin Hi, 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. 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
- [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