Re: [p2pi] Thoughts on how IETF standards can help P2P/ISPs

I certainly understand why it's somewhere between hard and impossible to give precise congestion status in all cases, due to VPN's, etc.. That being said, even getting less precise guidance, and only in the more common cases, would help us make better decisions for large numbers of users. For example, being told when we're causing congestion of home consumer internet connections with single-NAT networks would help us "play nicely" for a large number of users.

- Laird Popkin, CTO, Pando Networks
  mobile: 646/465-0570

----- Original Message -----
From: "Nicholas Weaver" <nweaver@ICSI.Berkeley.EDU>
To: "Joe Touch" <touch@ISI.EDU>
Cc: "Nicholas Weaver" <nweaver@ICSI.Berkeley.EDU>, "Laird Popkin" <laird@pando.com>, ramit@pando.com, p2pi@ietf.org, p4pwg@yahoogroups.com
Sent: Monday, June 2, 2008 1:51:12 PM (GMT-0500) America/New_York
Subject: Re: [p2pi] Thoughts on how IETF standards can help P2P/ISPs

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