Re: [p2pi] Refining the ALTO problem statement [Was: Re: discussing P2PI-related standardization in Dublin]

Lars Eggert <lars.eggert@nokia.com> Fri, 13 June 2008 16:12 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 75FD13A6924; Fri, 13 Jun 2008 09:12:37 -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 C84A03A6924 for <p2pi@core3.amsl.com>; Fri, 13 Jun 2008 09:12:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.477
X-Spam-Level:
X-Spam-Status: No, score=-6.477 tagged_above=-999 required=5 tests=[AWL=0.122, 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 9vhaD3TnQk1z for <p2pi@core3.amsl.com>; Fri, 13 Jun 2008 09:12:35 -0700 (PDT)
Received: from mgw-mx06.nokia.com (smtp.nokia.com [192.100.122.233]) by core3.amsl.com (Postfix) with ESMTP id AB6303A6826 for <p2pi@ietf.org>; Fri, 13 Jun 2008 09:12:34 -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 m5DGD1RN010958; Fri, 13 Jun 2008 19:13:03 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 13 Jun 2008 19:13:03 +0300
Received: from net-92.nrpn.net ([10.241.184.208]) by esebh102.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Fri, 13 Jun 2008 19:13:02 +0300
Message-Id: <4E2CFB2D-A2E2-432E-82B2-0B32500EFA9B@nokia.com>
From: Lars Eggert <lars.eggert@nokia.com>
To: ext John Leslie <john@jlc.net>
In-Reply-To: <20080613150058.GA3759@verdi>
Mime-Version: 1.0 (Apple Message framework v924)
Date: Fri, 13 Jun 2008 19:12:57 +0300
References: <22F6A875-B548-4C65-AB68-B88E526CCA33@nokia.com> <6E1603B0-7116-45F9-A510-DC5F9040298B@nokia.com> <C80ADC57CB3BB64B94A9954A816306C50C323F@STNTEXCH11.cis.neustar.com> <48516BE2.2080901@telecomitalia.it> <20080613150058.GA3759@verdi>
X-Mailer: Apple Mail (2.924)
X-OriginalArrivalTime: 13 Jun 2008 16:13:02.0789 (UTC) FILETIME=[5B105F50:01C8CD70]
X-Nokia-AV: Clean
Cc: "p2pi@ietf.org" <p2pi@ietf.org>
Subject: Re: [p2pi] Refining the ALTO problem statement [Was: Re: 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

On 2008-6-13, at 18:00, ext John Leslie wrote:
>   In the second case, an estimate of how long the transfer _would_
> take is very useful information, and we should have a way of passing
> that back. (Users will typically abort transfers that aren't making
> enough progress; and giving them information to abort sooner would be
> a good thing.)

There is NO way for the oracle to figure this out - this depends  
entirely on the current load along the path, which is changing on  
short timescales under the control of the end-to-end congestion  
control loop.

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