Re: [p2pi] Refining the ALTO problem statement

"Spencer Dawkins" <spencer@wonderhamster.org> Mon, 16 June 2008 18:15 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 52E1A3A69F2; Mon, 16 Jun 2008 11:15:55 -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 8CC4A3A69F2 for <p2pi@core3.amsl.com>; Mon, 16 Jun 2008 11:15:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.395
X-Spam-Level:
X-Spam-Status: No, score=-2.395 tagged_above=-999 required=5 tests=[AWL=0.203, BAYES_00=-2.599, STOX_REPLY_TYPE=0.001]
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 ywl8LOzuoQr3 for <p2pi@core3.amsl.com>; Mon, 16 Jun 2008 11:15:53 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.197]) by core3.amsl.com (Postfix) with ESMTP id 845213A69E7 for <p2pi@ietf.org>; Mon, 16 Jun 2008 11:15:53 -0700 (PDT)
Received: from s73602 (cpe-72-190-0-23.tx.res.rr.com [72.190.0.23]) by mrelay.perfora.net (node=mrus1) with ESMTP (Nemesis) id 0MKpCa-1K8JFk3zCw-0004Mb; Mon, 16 Jun 2008 14:16:30 -0400
Message-ID: <01fd01c8cfdd$3dd8a770$6401a8c0@china.huawei.com>
From: Spencer Dawkins <spencer@wonderhamster.org>
To: p2pi@ietf.org
References: <7335188A-BA0A-48E6-9D6B-9E4F6F09A4C6@nokia.com> <00b601c8cfb5$3aa68180$6401a8c0@china.huawei.com> <20080616173953.GF3759@verdi>
Date: Mon, 16 Jun 2008 13:17:28 -0500
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Provags-ID: V01U2FsdGVkX1+ze6d9paMVdv8tB7VQlfYJLwFT5ZpYXUT6rx8 NZBGXVPdzSl6E+naQDZtTZOP2Gz8/DS8xl1Bi+WUnFqP0ORkLS ZoK9l85wLtCP5ZS3wkHA3CoX4HHU4QzjWvLYR+LAg8=
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-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: p2pi-bounces@ietf.org
Errors-To: p2pi-bounces@ietf.org

Hi, John,

>> My understanding of what Lars is concerned about, is the idea of using
>> an oracle to provide guidance about path characteristics on a timescale
>> of less than many, many RTTs. He's concerned that a transmitter can
>> respond to "good news" about a path from an oracle more quickly than
>> the oracle can recognize that a transmitter has rapidly ramped up its
>> transmit rate and start telling senders what it's seeing.
>
>   For a number of reasons, oracles _could_ be in a better position to
> know path characteristics. Congestion along a path tends to be 
> concentrated
> at relatively few points along the path. Peers know what they're seeing
> (instantaneously) over the whole path, but generally lack any 
> understanding
> about subpaths.

I agree that oracles could be in a better position to know path 
characteristics.

What I thought Lars was concerned about was not what the oracle could know, 
but how quickly the oracle could share this knowledge with transmitters. If 
someone told Lars that we expect the oracle to adjust its suggestions every 
30 minutes, he'd probably be happier than if someone told Lars that we 
expect the oracle to adjust its suggestions every 30 milliseconds... and I'm 
not sure that Lars knows which is more representative of what people are 
thinking.

Thanks,

Spencer 


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