[p2pi] Thoughts on how IETF standards can help P2P/ISPs
Laird Popkin <laird@pando.com> Mon, 02 June 2008 16:08 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 9D8613A6CA3; Mon, 2 Jun 2008 09:08:45 -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 ED6CA3A69D9 for <p2pi@core3.amsl.com>; Mon, 2 Jun 2008 09:08:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.965
X-Spam-Level:
X-Spam-Status: No, score=-9.965 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, HABEAS_ACCREDITED_COI=-8, IP_NOT_FRIENDLY=0.334, J_CHICKENPOX_13=0.6]
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 pzn6sK6IegtS for <p2pi@core3.amsl.com>; Mon, 2 Jun 2008 09:08:43 -0700 (PDT)
Received: from dkny.pando.com (dkny.pando.com [67.99.55.163]) by core3.amsl.com (Postfix) with ESMTP id 58A763A6CAA for <p2pi@ietf.org>; Mon, 2 Jun 2008 09:06:10 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by dkny.pando.com (Postfix) with ESMTP id 87DD2E10C51; Mon, 2 Jun 2008 12:06:07 -0400 (EDT)
X-Virus-Scanned: amavisd-new at
Received: from dkny.pando.com ([127.0.0.1]) by localhost (dkny.pando.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w9hsmfiNlFFJ; Mon, 2 Jun 2008 12:06:06 -0400 (EDT)
Received: from dkny.pando.com (dkny.pando.com [10.10.60.11]) by dkny.pando.com (Postfix) with ESMTP id EC91AE10C50; Mon, 2 Jun 2008 12:06:06 -0400 (EDT)
Date: Mon, 02 Jun 2008 12:06:06 -0400
From: Laird Popkin <laird@pando.com>
To: p2pi@ietf.org, p4pwg@yahoogroups.com
Message-ID: <1865369468.307061212422766942.JavaMail.root@dkny.pando.com>
In-Reply-To: <443690410.306941212422172782.JavaMail.root@dkny.pando.com>
MIME-Version: 1.0
X-Originating-IP: [10.10.20.73]
Cc: ramit@pando.com
Subject: [p2pi] Thoughts on how IETF standards can help P2P/ISPs
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
As we discussed last week at the IETF P2Pi Workshop, here are a list of some of the ways that IETF standards can potentially help P2P applications make better network decisions, and thus help ISPs. This isn't a complete list, but I hope that it's at least a useful starting point for a discussion. - Expose more information about TCP streams. For example, expose whether the stream is congested. Currently some p2p applications use a variety of techniques to attempt to guess whether a user's internet connection is congested (e.g. monitoring ping times), and measures stream throughput which could be viewed as a very rough measure of congestion, but it would be more accurate and efficient if TCP told the application when a stream was congested. Even better would be to get some indication of where the congestion occurred. For example, if the congestion is in the 'last mile', or the other peer's 'last mile', or somewhere in between, different responses would be appropriate. For example, if my internet connection is fine, but the peer's connection is congested, I should slow down transfers from that peer, and pull more from other peers. This is, of course, easier said than done. - Expose some measure of 'communications cost' so that p2p apps could select the lowest cost available data sources. (This is what the P4P protocol does, for example). If using this guidance benefits both P2Ps and ISPs, it is a win-win. This is a fairly broad area that might include a number of steps/messages/protocols in order to address service location, mapping IPs to location, and "cost". The P4PWG is researching this area, and while it feels a little early to propose a standard, it's certainly an area (IMO) that could benefit from attention. - ISP's could expose usage metrics. For example, if a user has a link that is capable of 1 Mbps, has a monthly transfer capacity of 500 GB, and has used 350 GB so far, then the application can make better choices, and application users could make informed choices. If the ISP could tell applications when the user's internet connection is congested, that would be extremely helpful. - Allow applications to tag some traffic as 'not time sensitive' so that ISPs can manage bulk traffic as lower priority than time-sensitive traffic. There would need to be a benefit to the application for doing so, such as excluding such traffic from ISP capacity limits. - Laird Popkin, CTO, Pando Networks mobile: 646/465-0570 _______________________________________________ p2pi mailing list p2pi@ietf.org https://www.ietf.org/mailman/listinfo/p2pi
- [p2pi] Thoughts on how IETF standards can help P2… Laird Popkin
- Re: [p2pi] Thoughts on how IETF standards can hel… Nicholas Weaver
- Re: [p2pi] Thoughts on how IETF standards can hel… Salman Abdul Baset
- Re: [p2pi] Thoughts on how IETF standards can hel… Joe Touch
- Re: [p2pi] Thoughts on how IETF standards can hel… Nicholas Weaver
- Re: [p2pi] Thoughts on how IETF standards can hel… Laird Popkin
- Re: [p2pi] Thoughts on how IETF standards can hel… Joe Touch
- Re: [p2pi] Thoughts on how IETF standards can hel… Enrico Marocco
- Re: [p2pi] Thoughts on how IETF standards can hel… Ted Hardie
- Re: [p2pi] Thoughts on how IETF standards can hel… Song Haibin
- Re: [p2pi] Thoughts on how IETF standards can hel… Joe Touch
- Re: [p2pi] Thoughts on how IETF standards can hel… Enrico Marocco
- Re: [p2pi] Thoughts on how IETF standards can hel… Vijay K. Gurbani
- Re: [p2pi] Thoughts on how IETF standards can hel… Wei Gengyu
- Re: [p2pi] Thoughts on how IETF standards can hel… Enrico Marocco
- Re: [p2pi] Thoughts on how IETF standards can hel… stefano previdi