[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [alto] Pitfalls for ISP-friendly P2P Design



Interesting. I agree that P2P traffic management differs among ISP's. Some broadband operators may care much about the link cost, while the transit providers have no such issue as long as the traffic is somewhat symmetrical. But, I don't think P4P/ALTO is limited to solve the inter-domain traffic issues only.

I find the following interesting: "...One might expect the median ratio of average download rate to be 1; i.e., for each peer in a swarm, some nearby peers will be slower, but others will faster. Instead, the median ratio is 0.15. This is because most BitTorrent peers from popular swarms in our trace come from the United States, while most capacity comes from comparatively high bandwidth peers in Europe...."

What does this mean? Does it imply that the content is in some remote locations? No wonder the locality schemes won't work. 

I wonder if the similar study can be done in other locations, such as China and Europe...

Thanks!

- Ping

On Fri, Oct 23, 2009 at 5:23 PM, Salman Abdul Baset <sa2086 at columbia.edu> wrote:
A paper in this year's HotNets.
http://conferences.sigcomm.org/hotnets/2009/papers/hotnets2009-final115.pdf

The paper argues that in practice the benefits of such design may be limited due to:
(1) conflicting interests of ISP.
 -What is good for one ISP is not always good for the other ISP.
(2) locality aware traffic may not work for long-tail content.

I am curious what folks on this list have to say about this paper.

Thanks
Salman


On Thu, 22 Oct 2009, rfc-editor at rfc-editor.org wrote:


A new Request for Comments is now available in online RFC libraries.


      RFC 5693

      Title:      Application-Layer Traffic Optimization (ALTO) Problem
                  Statement
      Author:     J. Seedorf, E. Burger
      Status:     Informational
      Date:       October 2009
      Mailbox:    jan.seedorf at nw.neclab.eu,
                  eburger at standardstrack.com
      Pages:      14
      Characters: 34234
      Updates/Obsoletes/SeeAlso:   None

      I-D Tag:    draft-ietf-alto-problem-statement-04.txt

      URL:        http://www.rfc-editor.org/rfc/rfc5693.txt

Distributed applications -- such as file sharing, real-time
communication, and live and on-demand media streaming -- prevalent on
the Internet use a significant amount of network resources.  Such
applications often transfer large amounts of data through connections
established between nodes distributed across the Internet with little
knowledge of the underlying network topology.  Some applications are
so designed that they choose a random subset of peers from a larger
set with which to exchange data.  Absent any topology information
guiding such choices, or acting on suboptimal or local information
obtained from measurements and statistics, these applications often
make less than desirable choices.

This document discusses issues related to an information-sharing
service that enables applications to perform better-than-random peer
selection.  This memo provides information for the Internet community.

This document is a product of the Application-Layer Traffic Optimization Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
 http://www.ietf.org/mailman/listinfo/ietf-announce
 http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute


_______________________________________________
alto mailing list
alto at ietf.org
https://www.ietf.org/mailman/listinfo/alto


_______________________________________________
alto mailing list
alto at ietf.org
https://www.ietf.org/mailman/listinfo/alto


Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.