Re: [p2pi] Refining the ALTO problem statement

Lars Eggert <lars.eggert@nokia.com> Fri, 27 June 2008 15:19 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 3FF2A3A6B30; Fri, 27 Jun 2008 08:19:31 -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 D6DED3A6B30 for <p2pi@core3.amsl.com>; Fri, 27 Jun 2008 08:19:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.535
X-Spam-Level:
X-Spam-Status: No, score=-6.535 tagged_above=-999 required=5 tests=[AWL=0.064, 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 7N8oQt-XSloX for <p2pi@core3.amsl.com>; Fri, 27 Jun 2008 08:19:29 -0700 (PDT)
Received: from mgw-mx06.nokia.com (smtp.nokia.com [192.100.122.233]) by core3.amsl.com (Postfix) with ESMTP id 5A64F3A6903 for <p2pi@ietf.org>; Fri, 27 Jun 2008 08:19:29 -0700 (PDT)
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213]) by mgw-mx06.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id m5RFJJAX032342; Fri, 27 Jun 2008 18:19:29 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 27 Jun 2008 18:10:45 +0300
Received: from net-99.nrpn.net ([10.241.184.208]) by esebh102.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Fri, 27 Jun 2008 18:10:44 +0300
Message-Id: <77D6EDD8-779B-4887-93A6-19E4E8953334@nokia.com>
From: Lars Eggert <lars.eggert@nokia.com>
To: "ext Vijay K. Gurbani" <vkg@alcatel-lucent.com>
In-Reply-To: <4864FC12.5040207@alcatel-lucent.com>
Mime-Version: 1.0 (Apple Message framework v924)
Date: Fri, 27 Jun 2008 18:10:39 +0300
References: <762072025.443831214577059088.JavaMail.root@dkny.pando.com> <4864FC12.5040207@alcatel-lucent.com>
X-Mailer: Apple Mail (2.924)
X-OriginalArrivalTime: 27 Jun 2008 15:10:45.0428 (UTC) FILETIME=[F934D740:01C8D867]
X-Nokia-AV: Clean
Cc: p2pi@ietf.org
Subject: Re: [p2pi] Refining the ALTO problem statement
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: p2pi-bounces@ietf.org
Errors-To: p2pi-bounces@ietf.org

Hi,

On 2008-6-27, at 17:41, ext Vijay K. Gurbani wrote:
> Laird Popkin wrote:
>> LP: Thanks, this is very helpful. I wasn't clear on the distinction
>> between ALTO and TANA BOF's - the descriptions in the email archives
>> seem to overlap somewhat. Is there a list of which items from the
>> P2Pi Workshop are ALTO and which are TANA?
>
> Laird: I believe that figuring out what things go on the ALTO list
> and what things go on the TANA list will be one of the
> things to be done at the BoFs in Dublin.  So far, we have the
> high level characterization that Lars had posted to the p2pi
> mailing list shortly after the MIT workshop (please see
> http://www.ietf.org/mail-archive/web/p2pi/current/msg00068.html)
> From that email, (3) is deemed to be within the purview of
> ALTO and (1) TANA.

Exactly.

>  (2) could conceivably be split up as
> a set of guideline documents, some applicable to TANA and
> others to ALTO.

I think the current plan is to discuss (2) during TANA, but that  
doesn't necessarily mean that any follow-up will need to only happen  
in whatever comes out of the TANA BOF.

>> Is there a TANA BOF meeting scheduled? If both TANA and ALTO are on
>> the agenda in Dublin, that'd be convenient. :-)
>
> Both the BoFs have been approved by their respective ADs, and are
> now with the agenda director, waiting to match time slots that
> minimize overlaps with other WGs and AD availability.

Yup. Scheduling this will be a mess. The secretariat is currently  
working out things.

Ideally, we'd schedule TSVAREA first, because it has an overview talk  
by Stas on how BitTorrent transports data, which not everyone in the  
IETF community is very familiar with, and which could provide some  
background knowledge to the wider community before they go off to  
participate in TANA and ALTO. Those two BOFs obviously MUST NOT  
conflict.

Lars
_______________________________________________
p2pi mailing list
p2pi@ietf.org
https://www.ietf.org/mailman/listinfo/p2pi