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

>-----Original Message-----
>From: p2pi-bounces@ietf.org [mailto:p2pi-bounces@ietf.org] On Behalf Of Ted
>Hardie
>Sent: Tuesday, June 03, 2008 7:06 AM
>To: Enrico Marocco; Laird Popkin
>Cc: ramit@pando.com; p2pi@ietf.org; p4pwg@yahoogroups.com
>Subject: Re: [p2pi] Thoughts on how IETF standards can help P2P/ISPs
>
>At 3:15 PM -0700 6/2/08, Enrico Marocco wrote:
>>It seems to me that this turned out to be a two-sided problem.  On the
>>one hand, it is clear that applications on the endpoints are in the
>>worst position to make optimal network decisions; a first part of the
>>solution should thus consist of a mechanism to defer such decisions to
>>external entities
>
>Of course you can recast this  as "So we should make sure that
>there are mechanisms that allow them to make more optimal decisions.
>The facilities which provide this information need not be controlled
>by the ISPs, but might be third party services which indicate
>cost/topology/congestion or some profile mix of the three."
>
>To my way of thinking, that makes it easier to consider the API
>design, as it is not so much an API that says "What's the best
>choice right now?"  but "What's the best X (flow pattern, topology,
>price)".  The second set of questions is sufficiently more modular
>that it is both easier to get right and, at least in my opinion,
>more interesting.
>Just  my two cents,
>Ted

I think it depends on whether the P2P application or the party that provides
peer selection information service makes the final choice. IMO, the peer
selection information service should provide information to help the p2p
application to determine best paths or peers, but not itself makes the final
choice.

-Song Haibin

_______________________________________________
p2pi mailing list
p2pi@ietf.org
https://www.ietf.org/mailman/listinfo/p2pi