Re: [p2pi] Refining the ALTO problem statement [Was: Re: discussing P2PI-related standardization in Dublin]
Enrico Marocco <enrico.marocco@telecomitalia.it> Fri, 13 June 2008 19:43 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 6A49E3A691B; Fri, 13 Jun 2008 12:43:46 -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 3E8F83A691B for <p2pi@core3.amsl.com>; Fri, 13 Jun 2008 12:43:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.678
X-Spam-Level: *
X-Spam-Status: No, score=1.678 tagged_above=-999 required=5 tests=[AWL=-0.799, BAYES_00=-2.599, DATE_IN_FUTURE_24_48=3.196, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
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 3h4ZBZXGugam for <p2pi@core3.amsl.com>; Fri, 13 Jun 2008 12:43:44 -0700 (PDT)
Received: from maill.telecomitalia.it (maill.telecomitalia.it [217.169.121.52]) by core3.amsl.com (Postfix) with ESMTP id 7A1543A67A7 for <p2pi@ietf.org>; Fri, 13 Jun 2008 12:43:43 -0700 (PDT)
Received: from ptpxch009rm001.idc.cww.telecomitalia.it ([156.54.205.171]) by maill.telecomitalia.it with Microsoft SMTPSVC(6.0.3790.1830); Fri, 13 Jun 2008 21:44:14 +0200
Received: from grfhub703rm001.griffon.local ([10.19.3.10]) by ptpxch009rm001.idc.cww.telecomitalia.it with Microsoft SMTPSVC(6.0.3790.1830); Fri, 13 Jun 2008 21:44:14 +0200
Received: from [172.16.82.18] (163.162.180.246) by smtp.telecomitalia.it (10.19.3.42) with Microsoft SMTP Server (TLS) id 8.1.263.0; Fri, 13 Jun 2008 21:44:13 +0200
Message-ID: <48541F91.1010306@telecomitalia.it>
Date: Sat, 14 Jun 2008 21:44:17 +0200
From: Enrico Marocco <enrico.marocco@telecomitalia.it>
User-Agent: Mozilla-Thunderbird 2.0.0.14 (X11/20080509)
MIME-Version: 1.0
To: Lars Eggert <lars.eggert@nokia.com>
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>
In-Reply-To: <A8AE7698-69ED-47AF-94D1-29AA4F60B7C8@nokia.com>
X-OriginalArrivalTime: 13 Jun 2008 19:44:14.0437 (UTC) FILETIME=[DBF46950:01C8CD8D]
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: multipart/mixed; boundary="===============1735960400=="
Sender: p2pi-bounces@ietf.org
Errors-To: p2pi-bounces@ietf.org
Lars Eggert wrote:
> I have a few comments about the kinds of information that the oracle
> might provide to the app.
Lars, thanks for your comments.
> These are all OK, except for the bit about "bandwidth constraints".
> The available bandwidth along a path changes very rapidly, on
> timescales roughly O(RTT), because bandwidth consumption is regulated
> by the congestion control loops of the flows sharing a path. This
> pretty much guarantees that any such information an oracle could
> maintain will be stale by the time that an oracle can provide it to an
> application. So this information is unlikely to be useful to an app;
> and I can even construct cases where using this stale information
> leads to traffic oscillations, which is problematic.
>
> Modulo this concern about stuff that varies on short timescales, a
> simple mechanism that lets an app query an oracle about the things in
> the two bullets above would be useful.
Ok.
> I'm MUCH less convinced of the usefulness of the shopping list of
> things in the following bullets. For a lot of the things below, it's
> unclear to me why an application would want them and where an oracle
> would get them from. I don't think they should be part of any
> standardization effort at this time. (Looking at them from a research
> perspective is fine.)
>
>> * Support for cost and charging information for application so that
>> applications can make appropriate trade-offs;
>
> Can you be a bit more explicit about whose costs this is about? Who is
> paying whom, on what timescales and based on what resources?
Sure. This was one bullet point that was made in Prof. Schulzrinne's
paper. I quote the text from the paper:
Cost-of-bandwidth information
Relying on cooperative applications to be “nice” is probably
insufficient unless there is an incentive. There are at least three
possibilities, namely either volume limiting, rate limiting or
volume-based charging. For example, a network could offer a tiered
tariff that allows unlimited bandwidth within the same AS, 100 kb/s
rate-limited but unlimited prioritized DiffServ to anywhere and
volume-limited bulk traffic to any AS. There are several ways to
convey this information to applications, allowing them to make
appropriate trade-offs. For example, a network could provide an
information service with a list of service descriptors, similar to
the RSVP TSpec. Alternatively, a protocol such as GIST could discover
the cost of particular destination. The service classes may change
over time. For example, a network may offer "midnight specials" when
the network is idle during off-hours, encouraging bulk downloads
during that time.
>> * Capabilities and characteristics of peers (i.e., last hop
>> bandwidth,
>> etc.);
>
> The bandwidth example is IMO again problematic (and it's not a peer
> characteristic, it's a path characteristic.)
Yes, you are right in characterizing this as a path characteristic.
> Also, why would an oracle
> know anything about the capabilities or characteristics of the peers?
> Are the peers supposed to register with the oracle? That goes far
> beyond what I thought this BOF was about.
No, we are not suggesting that peers register with the oracle. This is
more along the point of trying to generate some discussion. What if a
peer is willing to publish its capabilities, either for other peers or
for an oracle. Is this something that is worth considering, if not for
a standardization aspect, at least as a research problem?
>> * Network policies;
>
> Such as?
Along the same line as mentioned above in the "Cost-of-bandwidth"
information.
>> + Type(s) of information that is provided to the oracle for
>> rendering an
>> equitable decision:
>> * List of peer candidate IP addresses;
>> * Parameter to optimize (cost, delay, ...);
>
> Why is it useful to query the oracle for delay? An app can get a
> relatively accurate and more importantly timely RTT sample by sending
> a few packets to a peer. That practice causes no issues for operators,
> since the traffic volume is so low.
Well, the use case I had in mind here was the selection of media relays
in real-time communication systems, when the list of candidate peers may
have hundreds or thousands of elements (think of Skype). In such a
case, provided the oracle can elaborate lists and not on single
instances only, a one query would replace tons of RTT measurements.
On a side note, is it possible for RTT to be small on a high latency
link one hop away when compared to a slightly higher RTT on low latency
links six hops away? That is, the time it takes for a peer to download
a large content from the peer with the lower RTT is actually higher than
the time it takes to do the same from the peer with higher RTT.
--
Ciao,
Enrico
_______________________________________________ p2pi mailing list p2pi@ietf.org https://www.ietf.org/mailman/listinfo/p2pi
- [p2pi] discussing P2PI-related standardization in… Lars Eggert
- Re: [p2pi] discussing P2PI-related standardizatio… Lars Eggert
- Re: [p2pi] discussing P2PI-related standardizatio… Vijay K. Gurbani
- Re: [p2pi] discussing P2PI-related standardizatio… Peterson, Jon
- Re: [p2pi] discussing P2PI-related standardizatio… Livingood, Jason
- [p2pi] Refining the ALTO problem statement [Was: … Enrico Marocco
- Re: [p2pi] Refining the ALTO problem statement [W… stefano previdi
- Re: [p2pi] Refining the ALTO problem statement [W… John Leslie
- Re: [p2pi] Refining the ALTO problem statement [W… Vijay K. Gurbani
- Re: [p2pi] Refining the ALTO problem statement [W… Lars Eggert
- Re: [p2pi] Refining the ALTO problem statement [W… Lars Eggert
- Re: [p2pi] discussing P2PI-related standardizatio… Lars Eggert
- Re: [p2pi] Refining the ALTO problem statement [W… Enrico Marocco
- Re: [p2pi] Refining the ALTO problem statement John Leslie
- Re: [p2pi] discussing P2PI-related standardizatio… Richard Bennett
- Re: [p2pi] discussing P2PI-related standardizatio… Lars Eggert
- Re: [p2pi] Refining the ALTO problem statement [W… Lars Eggert
- Re: [p2pi] Refining the ALTO problem statement Lars Eggert
- Re: [p2pi] Refining the ALTO problem statement [W… stefano previdi
- Re: [p2pi] Refining the ALTO problem statement Spencer Dawkins
- Re: [p2pi] Refining the ALTO problem statement John Leslie
- Re: [p2pi] Refining the ALTO problem statement John Leslie
- Re: [p2pi] Refining the ALTO problem statement Spencer Dawkins
- Re: [p2pi] Refining the ALTO problem statement [W… Henning Schulzrinne
- Re: [p2pi] Refining the ALTO problem statement [W… Stanislav Shalunov
- Re: [p2pi] Refining the ALTO problem statement [W… Lars Eggert
- Re: [p2pi] Refining the ALTO problem statement Lars Eggert
- Re: [p2pi] Refining the ALTO problem statement Spencer Dawkins
- Re: [p2pi] Refining the ALTO problem statement John Leslie
- Re: [p2pi] Refining the ALTO problem statement Robert Snively
- Re: [p2pi] Refining the ALTO problem statement Stanislav Shalunov
- Re: [p2pi] Refining the ALTO problem statement Laird Popkin
- Re: [p2pi] Refining the ALTO problem statement stefano previdi
- Re: [p2pi] Refining the ALTO problem statement Stanislav Shalunov
- Re: [p2pi] Refining the ALTO problem statement Lars Eggert