Re: [p2pi] Thoughts on how IETF standards can help P2P/ISPs
Nicholas Weaver <nweaver@ICSI.Berkeley.EDU> Mon, 02 June 2008 17:55 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 DBB2C3A6B32; Mon, 2 Jun 2008 10:55:35 -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 172543A6B32 for <p2pi@core3.amsl.com>; Mon, 2 Jun 2008 10:55:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.139
X-Spam-Level:
X-Spam-Status: No, score=-6.139 tagged_above=-999 required=5 tests=[AWL=0.460, 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 Vi5QH0vey8BY for <p2pi@core3.amsl.com>; Mon, 2 Jun 2008 10:55:34 -0700 (PDT)
Received: from fruitcake.ICSI.Berkeley.EDU (fruitcake.ICSI.Berkeley.EDU [192.150.186.11]) by core3.amsl.com (Postfix) with ESMTP id 8750228C1D9 for <p2pi@ietf.org>; Mon, 2 Jun 2008 10:51:17 -0700 (PDT)
Received: from [IPv6:::1] (fruitcake [192.150.186.11]) by fruitcake.ICSI.Berkeley.EDU (8.12.11.20060614/8.12.11) with ESMTP id m52HpD6Q017153; Mon, 2 Jun 2008 10:51:13 -0700 (PDT)
Message-Id: <2E865AA6-EED7-416F-BB69-16F912197E59@icsi.berkeley.edu>
From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
To: Joe Touch <touch@ISI.EDU>
In-Reply-To: <48442FD5.7020407@isi.edu>
Mime-Version: 1.0 (Apple Message framework v924)
Date: Mon, 02 Jun 2008 10:51:12 -0700
References: <1865369468.307061212422766942.JavaMail.root@dkny.pando.com> <48442FD5.7020407@isi.edu>
X-Mailer: Apple Mail (2.924)
Cc: p2pi@ietf.org, ramit@pando.com, Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>, p4pwg@yahoogroups.com
Subject: Re: [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
On Jun 2, 2008, at 10:37 AM, Joe Touch wrote: > > >> 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. > > This is not feasible for a number of reasons, including the use of > tunnels and VPNs. It's possible to know whether the end systems are > loaded (applications can tell each other), but path limits are hard > to pin down. It's more useful to just try a few peers and see what > works than to assume this kind of information is (or ever will be) > available. Bulk data P2P can actually tell this if the TCP access API is suitable, by looking for correlations. If its just one flow that is seeing congestion, assume it is the other side. If multiple flows are seeing congestion, then the problem probably is at your end. _______________________________________________ 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