IETF Logo Mail Archive

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

"Stanislav Shalunov" <shalunov@bittorrent.com> Wed, 18 June 2008 04:04 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 4DEC33A68E8; Tue, 17 Jun 2008 21:04:44 -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 46AC53A68E8 for <p2pi@core3.amsl.com>; Tue, 17 Jun 2008 21:04:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 5A6AB6j5RoVX for <p2pi@core3.amsl.com>; Tue, 17 Jun 2008 21:04:42 -0700 (PDT)
Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.28]) by core3.amsl.com (Postfix) with ESMTP id 32F9F3A68C5 for <p2pi@ietf.org>; Tue, 17 Jun 2008 21:04:42 -0700 (PDT)
Received: by yw-out-2324.google.com with SMTP id 3so39771ywj.49 for <p2pi@ietf.org>; Tue, 17 Jun 2008 21:05:26 -0700 (PDT)
Received: by 10.151.108.10 with SMTP id k10mr259418ybm.113.1213761926152; Tue, 17 Jun 2008 21:05:26 -0700 (PDT)
Received: by 10.150.196.13 with HTTP; Tue, 17 Jun 2008 21:05:26 -0700 (PDT)
Message-ID: <dfa4ab960806172105x281bd219yde99a1c5e143d0a5@mail.gmail.com>
Date: Tue, 17 Jun 2008 21:05:26 -0700
From: Stanislav Shalunov <shalunov@bittorrent.com>
To: Henning Schulzrinne <hgs@cs.columbia.edu>
In-Reply-To: <D1435946-50BF-4472-A8B4-5233E9430781@cs.columbia.edu>
MIME-Version: 1.0
Content-Disposition: inline
References: <22F6A875-B548-4C65-AB68-B88E526CCA33@nokia.com> <6E1603B0-7116-45F9-A510-DC5F9040298B@nokia.com> <C80ADC57CB3BB64B94A9954A816306C50C323F@STNTEXCH11.cis.neustar.com> <48516BE2.2080901@telecomitalia.it> <A8AE7698-69ED-47AF-94D1-29AA4F60B7C8@nokia.com> <48541F91.1010306@telecomitalia.it> <3083CE1C-A219-4DB6-BAEC-E74DC3FD9C46@nokia.com> <D1435946-50BF-4472-A8B4-5233E9430781@cs.columbia.edu>
X-Google-Sender-Auth: 1752b164c45fd55d
Cc: 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 Tue, Jun 17, 2008 at 7:29 PM, Henning Schulzrinne
<hgs@cs.columbia.edu> wrote:
> "Your current charge for priority X is Y currency units/byte, valid
> until time T."
>
> "You have used B bytes out of L bytes for priority X."
>
> "Your max. rate for priority X is S bits/second."

It might also be interesting to know the differences in provider costs
between different destinations.

> Given that TCP throughput is inversely proportional to RTT, one would
> indeed expect a correlation.

The small differences in Internet RTTs are drowned out by the huge
extra delay indiced by TCP, and so wouldn't matter even in random or
periodic loss model that this statement implies.

In reality, of course, TCP throughput is related to bottleneck bitrate.

-- 
Stanislav Shalunov
http://shlang.com/
_______________________________________________
p2pi mailing list
p2pi@ietf.org
https://www.ietf.org/mailman/listinfo/p2pi

v2.39.1 | Report a Bug | By Email | System Status