Re: [p2pi] discussing P2PI-related standardization in Dublin

Lars Eggert <lars.eggert@nokia.com> Fri, 06 June 2008 14:41 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 33ED628C1C7; Fri, 6 Jun 2008 07:41:17 -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 ECD8B28C19D; Fri, 6 Jun 2008 07:41:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.443
X-Spam-Level:
X-Spam-Status: No, score=-6.443 tagged_above=-999 required=5 tests=[AWL=0.156, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 pRWBqO7lT46s; Fri, 6 Jun 2008 07:41:14 -0700 (PDT)
Received: from mgw-mx03.nokia.com (smtp.nokia.com [192.100.122.230]) by core3.amsl.com (Postfix) with ESMTP id 7F95728C17A; Fri, 6 Jun 2008 07:41:14 -0700 (PDT)
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145]) by mgw-mx03.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id m56Ef9Xp015794; Fri, 6 Jun 2008 17:41:21 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 6 Jun 2008 17:40:42 +0300
Received: from [195.37.70.145] ([10.241.184.208]) by esebh102.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Fri, 6 Jun 2008 17:40:41 +0300
From: Lars Eggert <lars.eggert@nokia.com>
To: TSV Area <tsv-area@ietf.org>
In-Reply-To: <22F6A875-B548-4C65-AB68-B88E526CCA33@nokia.com>
References: <22F6A875-B548-4C65-AB68-B88E526CCA33@nokia.com>
Message-Id: <6E1603B0-7116-45F9-A510-DC5F9040298B@nokia.com>
Mime-Version: 1.0 (Apple Message framework v924)
Date: Fri, 06 Jun 2008 16:40:36 +0200
X-Mailer: Apple Mail (2.924)
X-OriginalArrivalTime: 06 Jun 2008 14:40:42.0158 (UTC) FILETIME=[4BB2ECE0:01C8C7E3]
X-Nokia-AV: Clean
Cc: p2prg@irtf.org, "iab@iab.org IAB" <iab@iab.org>, p2pi@ietf.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
Reply-To: TSV Area <tsv-area@ietf.org>
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

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